-
Notifications
You must be signed in to change notification settings - Fork 371
2021 04 26 Open NEST Developer Video Conference
Dennis Terhorst edited this page Apr 26, 2021
·
10 revisions
- Welcome
- Review of NEST User Mailing List
- Project team round
- In-depth discussion
- NEST Documentation Style Guide (#1986)
- Single vs double quotes for Python strings? See also this discussion
- Which well-established style guide to build on? See also this discussion
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.
- Models / NESTML
- STDP test-case started at NEST Hackathon, revealed some bugs that are being worked on
- preparations for NESTML 4.0 release
- PyNEST
- MPI enabled version of NEST-Server was added
- Kernel
- Installation
- worked on issues of @helveg at the Hackathon, changes in Python installation, working on PR#1959 which will close a number of open issues.
- discussion started to clean up
cmake
andmake
targets to smoothen installation workflow with different environments
- Infrastructure
- transition of nest-extension-module repository to github-actions
- looking into larger build pipelines between the different NEST-related repositories
- Documentation
- discussion about error messages
- worked on PRs
- developer space now moved (#1995)
- nest server docs improved (#2022)
- RNG docs
- style guides (see in-depth discussion)
- EBRAINS
- discussion for EBRAINS High-level support team (HLST) contact person of NEST Simulator
- invitation for talk about NEST on ICEI infrastructure (contact @heplesser)
- currently ongoing ANDA Course can provide feed-back about usage of EBRAINS resources soon. (preliminary: works but slow and few resources)
- (Feature) Random number generation
- Closed Project.
- (Feature) Automated Testing
- no updates
- (Feature) Extension Module System
- no updates
NEST Documentation Style Guide (#1986)
- made some general style decisions for documentation (will be included in the style guide)
- do not use contractions
- punctuation: ", for example," with commas, …
- always use
sec_
/fig_
/… reference prefixes - …
- started discussion will be continued in separate meeting focusing on NEST documentation first
NEST Homepage: www.nest-simulator.org
NEST Initiative: www.nest-initiative.org