p20518467
/
InfiniTensor
forked from jiuyuan/InfiniTensor
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
35 Commits 70 Branches 0 Tags 141 MiB
C++ 76.3%
Cuda 18%
Python 4.3%
CMake 1.1%
Shell 0.1%
Go to file
zhengly123 8f67a5cc76
Add: ConvTransposed (#33) 
* Add: convTransposed2d operator

* Fix: IT_ASSERT namespace

* Add: nullptr check in as for Ref

* Fix: conv transpose operator and kernel

* Fix: makes PerfEngine singleton

* Add: ConvTransposed test

* Fix: rebase to master (PerfRecord shared_ptr)

* Revert: Ref with nullptr check

Co-authored-by: Liyan Zheng <liyan-zheng@outlook.com>
 		2022-09-19 15:05:39 +08:00
.github/workflows Add: clang format check github action 2022-08-09 17:58:12 +08:00
3rd-party add code for backtrace (#21) 2022-09-01 20:30:12 +08:00
include Add: ConvTransposed (#33) 2022-09-19 15:05:39 +08:00
proto Tensor serialization (#25) 2022-09-13 11:27:41 +08:00
src Add: ConvTransposed (#33) 2022-09-19 15:05:39 +08:00
test Add: ConvTransposed (#33) 2022-09-19 15:05:39 +08:00
.clang-format Add: graph, tensor, and operator 2022-07-31 21:44:03 +08:00
.cmake-format.json Add: graph, tensor, and operator 2022-07-31 21:44:03 +08:00
.gitignore Fix: PerfRecord in shared pointers (#31) 2022-09-18 20:27:18 +08:00
.gitmodules add code for backtrace (#21) 2022-09-01 20:30:12 +08:00
CMakeLists.txt Fix NNet tests after migration (#27) 2022-09-13 15:17:22 +08:00
LICENSE Initial commit 2022-07-27 22:40:23 +08:00
README.md Add contributor guide 2022-09-13 14:19:07 +08:00

README.md

InfiniTensor

Compilation on Lotus

# Enter the root of InfiniTensor
source test/script/env_lotus.sh 
mkdir build && cd build
cmake .. && make -j 12

Contributor Guide

InfiniTensor development is based on the pull request on Github. Before requesting for merging, a PR should satisfy the following requirements

  1. Pass all tests.
    1. Currently, CI on Github only checks code format. Script test/script/clang_format_inplace.sh is for formatting all code.
    2. Contributors should run ctest manually and copy its output to the PR. Use fenced code blocks (triple backquotes, i.e., ```) to avoid referencing in Github. Otherwise, # in the output is interpreted as a Github reference. Do not directly paste the ctest output in commit messages either for the same reason.
  2. Receive at least one approval from reviewers.
  3. PR title should be concise since it is going to be the commit message in the main branch after merging and squashing.