Feature/mechanisms unit tests (#96)
These tests are intended to test the sanity of the `modcc` generated code for the individual mechanisms. The don't have any physical background. Potentially optimized CPU-targeted mechanisms generated in the build are compared with unoptimized mechanisms generated from the reference modules. * Add generic unit tests for individual mechanisms. * Make unit tests exercise potential problems with aliased indexes (point processes). * Ensure unit tests correspond to multiple low level vector operations. * Ensure unit tests run with voltage, current and indices initialized with varying values. * Refactor CMake code for module compilation to reduce cut-and-paste code and build complexity.
Showing
- CMakeLists.txt 3 additions, 3 deletionsCMakeLists.txt
- mechanisms/BuildModules.cmake 40 additions, 0 deletionsmechanisms/BuildModules.cmake
- mechanisms/CMakeLists.txt 24 additions, 67 deletionsmechanisms/CMakeLists.txt
- modcc/cprinter.cpp 9 additions, 4 deletionsmodcc/cprinter.cpp
- modcc/cudaprinter.cpp 12 additions, 7 deletionsmodcc/cudaprinter.cpp
- modcc/modcc.cpp 45 additions, 67 deletionsmodcc/modcc.cpp
- modcc/options.hpp 49 additions, 0 deletionsmodcc/options.hpp
- src/util/cycle.hpp 10 additions, 0 deletionssrc/util/cycle.hpp
- tests/unit/CMakeLists.txt 20 additions, 1 deletiontests/unit/CMakeLists.txt
- tests/unit/test_cycle.cpp 14 additions, 0 deletionstests/unit/test_cycle.cpp
- tests/unit/test_mechanisms.cpp 169 additions, 1 deletiontests/unit/test_mechanisms.cpp
- tests/unit/test_synapses.cpp 0 additions, 1 deletiontests/unit/test_synapses.cpp
Please register or sign in to comment