Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add 'what's new' docs for 3.5 #2838

Merged
merged 2 commits into from
Jun 29, 2023

Conversation

jessica-mitchell
Copy link
Contributor

This PR adds docs for version 3.5 of NEST
it highlights

  • NEST SONATA
  • new model: spike_train_injector
  • new hpc docs
  • run notebooks from pynest examples

@jessica-mitchell jessica-mitchell added this to the NEST 3.5 milestone Jun 23, 2023
@jessica-mitchell jessica-mitchell added S: High Should be handled next T: Maintenance Work to keep up the quality of the code and documentation. labels Jun 23, 2023
@jessica-mitchell
Copy link
Contributor Author

Copy link
Contributor

@gtrensch gtrensch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me!

doc/htmldoc/whats_new/v3.5/index.rst Outdated Show resolved Hide resolved
Copy link
Contributor

@terhorstd terhorstd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice! Thanks for the nice summary!
🚀

@terhorstd terhorstd added the I: No breaking change Previously written code will work as before, no one should note anything changing (aside the fix) label Jun 29, 2023
@terhorstd terhorstd merged commit 1a1f32e into nest:master Jun 29, 2023
heplesser added a commit that referenced this pull request Jul 3, 2023
@jessica-mitchell jessica-mitchell deleted the docs-whatsnew-3.5 branch September 13, 2024 20:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
I: No breaking change Previously written code will work as before, no one should note anything changing (aside the fix) S: High Should be handled next T: Maintenance Work to keep up the quality of the code and documentation.
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

3 participants