Skip to content

2021 11 08 Open NEST Developer Video Conference

Dennis Terhorst edited this page Nov 8, 2021 · 6 revisions

previous | list | next

Agenda

  1. Welcome
    • NEST Conference 2022
  2. Review of NEST User Mailing List
  3. Project team round
  4. In-depth discussion
    • t.b.a.

NEST Conference 2022

         Juni          
  So Mo Di Mi Do Fr Sa  
            1  2  3  4  
   5 X6X 7  8  9 10 11  <<<<<< LIVE HACKATHON
  12 13 14 15-16-17 18  <<< release week
  19>20-21-22 23 24<25  <<<<<<  SAVE THE DATE -- NEST Conference 2022
  26x27x28x29x30xxxxxx       

Mailing list

Project team round

Here we discuss topics that need broader attention, for example questions that came up but are outside a single project's scope, larger planned changes/PRs that affect all teams or pending work that is blocked by external factors.

  1. Models / NESTML
    • how to proceed with #1895 – change to extension module
    • non-linear NMDA channels, math allows to compute activation trace on the pre-synaptic side, share traces via SecondaryEvents, looking for experts.
  2. PyNEST
    • nothing to report
  3. Kernel
    • fixing in-memory representation of spacial information (PR in progress)
  4. Installation
    • looking into new issues, some deep, some for hackathon
  5. Infrastructure
    • nothing to report
  6. Documentation
    • nothing to report
  7. EBRAINS
    • nothing to report
  8. (Feature) Automated Testing
    • nothing to report
  9. (Feature) Extension Module System
    • nothing to report

In-depth discussion

PyNN and NEST 3

  • NEST-3 support was merged to PyNN main branch, will become part of next release
  • major point was removal of ResetNetwork() from the NEST API, now workaround by concatenating runs into one long run
    • problematic point is the leakage of information into subsequent runs
    • ResetNetwork() also did not protect against leakage of information, thus it was removed
      • manually resetting buffers, RNGs, etc. needs to be very exactly specified
    • better solution would be to run in different sub-processes
Clone this wiki locally