2017 03 20 Open NEST Developer Video Conference

previous | list | next

Agenda

1. Welcome
2. NEST 2.12.0 Issues
   • #683
     • new connector model
     • need template argument for functions
       • C++11 or work-around with C++98
       • debian stable not officially supports C++11, at the moment
     • need to find a good way to link to the new model from the NEST homepage
     • looking forward to the coming pull-request
   • #382, #684
     • Homebrew issues with python/cython
3. Subnet-Removal Hackathon Report
   • subnet free nest available, in heplesser/nest-simulator
   • removal of SiblingContainers is ongoing
   • discussed the removal of global spike detector. simplifies code very much
   • everything that will go away has deprecation warnings
   • NEST i/o
     • using parallel i/o to write output in a binary format, then use a python tool to convert to legacy formats.
     • work-in-progress
     • expect a pull request soon
4. Vera++ Conformity
   • ci tests includes 3 static checkers: cppcheck, clang-format (or pop8 for python), vera++
   • not instead of ! is compilant with C++ standard also in case of operator not() definition
   • big PR for fixing all {} on separate lines is comming, reviewers welcome
     • already tried merging to various forks, usually only few conflicts
   • NOTE: remember to run extras/check_code_style.sh before starting a PR
5. Permitting C++11 constructs
   • workaround exists
   • C++11 support is not under our control on many systems
     • could define a reference distribution and then look for solutions for non-supported machines
   • C++11 for the basic simulator architecture
6. Travis setup, see also #682

   • minor issue, but currently undefined versions in CI
     

   • currently only specified by "ubuntu xx" standard.
     

   • docker container is being set up by @ldepuu
     

   • also considering to change to a staggered CI system to save resources, basically just requires changes to build.sh script
7. Help for users : nest.helpdesk() vs. web-page vs. ipython ?help
   • currently fork() is done on SLI level and breaks in MPI-enabled nest
   • nest.helpdesk() is used and necessary for workshops
   • probably a solution on python level is better
8. Review of NEST User Mailing List
   • couple of problems with not clean build/ directories after the release
   • handled all messages
9. Review of open Github Pull Request -skipped-
10. Review of open Github Issues -skipped-