- NEST Users - NEST Initiative Mail

Open NEST Developer Video Conference Monday 19 August 2019 11.30 CEST (UTC+2)
by Hans Ekkehard Plesser 19 Aug '19

19 Aug '19

Dear NEST Developers! I would like to invite you to our next bi-weekly Open NEST Developer Video Conference tomorrow Monday 19 August, 11.30-12.30 CEST (UTC+2). See below for information about how to log into the meeting. The agenda for this meeting is also available online https://github.com/nest/nest-simulator/wiki/2019-08-19-Open-NEST-Developer-… • Welcome • Review of NEST User Mailing List • Review of open Github Pull Request • Review of open Github Issues See you soon! Hans Ekkehard Plesser ------------------ Log-in information ------------------ We use a virtual conference room provided by DFN (Deutsches Forschungsnetz). You can use the web client to connect. We however encourage everyone to use a headset for better audio quality or even a proper video conferencing system (see below) or software when available. Web client * Visit https://conf.dfn.de/webapp/conference/97938800 * Enter your name and allow your browser to use camera and microphone * The conference does not need a PIN to join, just click join and you're in. In case you see a dfnconf logo and the phrase "Auf den Meetingveranstalter warten", just be patient, the meeting host needs to join first (a voice will tell you). VC system/software How to log in with a video conferencing system, depends on you VC system or software. - Using the H.323 protocol (eg Polycom): vc.dfn.net##97938800 or 194.95.240.2##97938800 - Using the SIP protocol:97938800@vc.dfn.de - By telephone: +49-30-200-97938800 For those who do not have a video conference system or suitable software, Polycom provides a pretty good free app for iOS and Android, so you can join from your tablet (Polycom RealPresence Mobile, available from AppStore/PlayStore). Note that firewalls may interfere with videoconferencing in various and sometimes confusing ways. For more technical information on logging in from various VC systems, please see http://vcc.zih.tu-dresden.de/index.php?linkid=1.1.3.4 -- Prof. Dr. Hans Ekkehard Plesser Head, Data Science Section Faculty of Science and Technology Norwegian University of Life Sciences PO Box 5003, 1432 Aas, Norway Phone +47 6723 1560 Email hans.ekkehard.plesser(a)nmbu.no Home http://arken.nmbu.no/~plesser _______________________________________________ NEST Users mailing list -- users(a)nest-simulator.org To unsubscribe send an email to users-leave(a)nest-simulator.org

1 0

NEST 2.18.0 (and 2.16.0) now available in NeuroFedora
by Ankur Sinha 13 Aug '19

13 Aug '19

Hello, On behalf of the NeuroFedora team, I'm happy to report that NEST 2.18.0 and 2.16.0 are both available for use on Fedora. Information on using NEST on NeuroFedora is documented here: https://docs.fedoraproject.org/en-US/neurofedora/nest/ Here are a few quick FAQs for your convenience: Q. How do I use NEST on NeuroFedora? A. It only takes two steps to install NEST using `dnf` (the default package manager): - Download and run (optionally install) a "live" Fedora Workstation image from https://getfedora.org - Install NEST 2.18.0: Run `sudo dnf install python3-nest` in a terminal. Q. How do I use version 2.16.0? A. 2.16.0 is provided as a "module". To install the 2.16.0 version: - Download and run (optionally install) a "live" Fedora Workstation image from https://getfedora.org - Install NEST 2.16.0: Run `sudo dnf module install nest:2.16.0` in a terminal. Please note that only one version of NEST can be installed at once. Q. Does NEST in NeuroFedora include MPI support? A. Yes---variants built with both MPICH and OpenMPI are available to use. Q. Does NEST in NeuroFedora include libneurosim/MUSIC/CSA support? A. Not all of them yet. - libneurosim: Yes - MUSIC: No (under review: https://pagure.io/neuro-sig/NeuroFedora/issue/28) - CSA: No (WIP: https://pagure.io/neuro-sig/NeuroFedora/issue/33) Q. Where do I get help? A. The NeuroFedora team maintains multiple communication channels for support and general discussion: https://docs.fedoraproject.org/en-US/neurofedora/communicating/ Q. What other tools does NeuroFedora provide? A. The complete list includes neuron, auryn, PyLEMS, NineML and lots more: https://src.fedoraproject.org/group/neuro-sig Fedora also includes more software that is not specific to computational neuroscience---such as productivity and development tools, a variety of desktop environments, server and container focussed editions, and other science related software: - https://getfedora.org/ - https://labs.fedoraproject.org/ - https://spins.fedoraproject.org/ Q. How can I help? A. The NeuroFedora team is made up of volunteers that believe in Free Software and Open Science. Information on how you can join us and help is summarised here: https://docs.fedoraproject.org/en-US/neurofedora/contributing/ -- Thanks, Regards, Ankur Sinha (He / Him / His) | https://ankursinha.in PhD candidate in computational neuroscience at UH Biocomputation | http://biocomputation.herts.ac.uk/ Free/Open source community volunteer at the Fedora project | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London

1 0

Error running tutorial notebook
by Filip Vercruysse 05 Aug '19

05 Aug '19

(CNS2019_NEST) Filips-MacBook-Pro:CNS2019_NEST_Tutorial filip$ jupyter-notebook [I 11:01:50.427 NotebookApp] The port 8888 is already in use, trying another port. [I 11:01:50.439 NotebookApp] Serving notebooks from local directory: /Users/filip/Desktop/Research/Conferences/CNS Barcelona/NEST tutorial/CNS2019_NEST_Tutorial [I 11:01:50.439 NotebookApp] The Jupyter Notebook is running at: [I 11:01:50.439 NotebookApp] http://localhost:8889/?token=f4b50440467ee8d87607f84e947be0022dbd7aa394a0b4… [I 11:01:50.439 NotebookApp] Use Control-C to stop this server and shut down all kernels (twice to skip confirmation). [C 11:01:50.445 NotebookApp] To access the notebook, open this file in a browser: file:///Users/filip/Library/Jupyter/runtime/nbserver-31158-open.html Or copy and paste one of these URLs: http://localhost:8889/?token=f4b50440467ee8d87607f84e947be0022dbd7aa394a0b4… [I 11:01:57.768 NotebookApp] Kernel started: 103ab68f-95af-4961-8f9d-3756f2192fd2 [I 11:01:58.401 NotebookApp] Adapting to protocol v5.1 for kernel 103ab68f-95af-4961-8f9d-3756f2192fd2 [INFO] [2019.7.13 11:2:4 /usr/local/miniconda/conda-bld/nest-simulator_1562094389587/work/nestkernel/rng_manager.cpp:217 @ Network::create_rngs_] : Creating default RNGs [INFO] [2019.7.13 11:2:4 /usr/local/miniconda/conda-bld/nest-simulator_1562094389587/work/nestkernel/rng_manager.cpp:260 @ Network::create_grng_] : Creating new default global RNG Assertion failed: (out != NULL), function execute, file /usr/local/miniconda/conda-bld/nest-simulator_1562094389587/work/sli/sli_io.cc, line 422. [Filips-MacBook-Pro:31166] *** Process received signal *** [Filips-MacBook-Pro:31166] Signal: Abort trap: 6 (6) [Filips-MacBook-Pro:31166] Signal code: (0) [Filips-MacBook-Pro:31166] [ 0] 0 libsystem_platform.dylib 0x00007fff791bfb3d _sigtramp + 29 [Filips-MacBook-Pro:31166] [ 1] 0 ??? 0x0000000000000001 0x0 + 1 [Filips-MacBook-Pro:31166] [ 2] 0 libsystem_c.dylib 0x00007fff7907e1c9 abort + 127 [Filips-MacBook-Pro:31166] [ 3] 0 libsystem_c.dylib 0x00007fff79046868 basename_r + 0 [Filips-MacBook-Pro:31166] [ 4] 0 libsli.dylib 0x0000000110a01077 _ZNK18StrSStreamFunction7executeEP14SLIInterpreter + 759 [Filips-MacBook-Pro:31166] [ 5] 0 libsli.dylib 0x00000001109edb2e _ZN13FunctionDatum7executeEP14SLIInterpreter + 446 [Filips-MacBook-Pro:31166] [ 6] 0 libsli.dylib 0x00000001109ebe42 _ZN14SLIInterpreter8execute_Em + 466 [Filips-MacBook-Pro:31166] [ 7] 0 libsli.dylib 0x00000001109ebc58 _ZN14SLIInterpreter7startupEv + 40 [Filips-MacBook-Pro:31166] [ 8] 0 libnest.dylib 0x0000000110031ffa _Z11neststartupPiPPPcR14SLIInterpreterNSt3__112basic_stringIcNS5_11char_traitsIcEENS5_9allocatorIcEEEE + 3306 [Filips-MacBook-Pro:31166] [ 9] 0 pynestkernel.so 0x000000010ffd5cb8 _ZL42__pyx_pw_12pynestkernel_10NESTEngine_5initP7_objectS0_S0_ + 3464 [Filips-MacBook-Pro:31166] [10] 0 python 0x00000001025a948a _PyCFunction_FastCallDict + 362 [Filips-MacBook-Pro:31166] [11] 0 python 0x000000010268042f call_function + 143 [Filips-MacBook-Pro:31166] [12] 0 python 0x000000010267dfc2 _PyEval_EvalFrameDefault + 46802 [Filips-MacBook-Pro:31166] [13] 0 python 0x00000001026807ec fast_function + 188 [Filips-MacBook-Pro:31166] [14] 0 python 0x000000010268048c call_function + 236 [Filips-MacBook-Pro:31166] [15] 0 python 0x000000010267dfc2 _PyEval_EvalFrameDefault + 46802 [Filips-MacBook-Pro:31166] [16] 0 python 0x0000000102671729 _PyEval_EvalCodeWithName + 425 [Filips-MacBook-Pro:31166] [17] 0 python 0x000000010266bf99 builtin_exec + 345 [Filips-MacBook-Pro:31166] [18] 0 python 0x00000001025a8dd2 PyCFunction_Call + 66 [Filips-MacBook-Pro:31166] [19] 0 python 0x000000010267e2b2 _PyEval_EvalFrameDefault + 47554 [Filips-MacBook-Pro:31166] [20] 0 python 0x0000000102671729 _PyEval_EvalCodeWithName + 425 [Filips-MacBook-Pro:31166] [21] 0 python 0x000000010268089a fast_function + 362 [Filips-MacBook-Pro:31166] [22] 0 python 0x000000010268048c call_function + 236 [Filips-MacBook-Pro:31166] [23] 0 python 0x000000010267dfc2 _PyEval_EvalFrameDefault + 46802 [Filips-MacBook-Pro:31166] [24] 0 python 0x00000001026807ec fast_function + 188 [Filips-MacBook-Pro:31166] [25] 0 python 0x000000010268048c call_function + 236 [Filips-MacBook-Pro:31166] [26] 0 python 0x000000010267dfc2 _PyEval_EvalFrameDefault + 46802 [Filips-MacBook-Pro:31166] [27] 0 python 0x00000001026807ec fast_function + 188 [Filips-MacBook-Pro:31166] [28] 0 python 0x000000010268048c call_function + 236 [Filips-MacBook-Pro:31166] [29] 0 python 0x000000010267dfc2 _PyEval_EvalFrameDefault + 46802 [Filips-MacBook-Pro:31166] *** End of error message *** [I 11:02:06.763 NotebookApp] KernelRestarter: restarting kernel (1/5), keep random ports WARNING:root:kernel 103ab68f-95af-4961-8f9d-3756f2192fd2 restarted [I 11:03:57.801 NotebookApp] Saving file at /part1_NEST/0_hello_world.ipynb

2 2

Open NEST Developer Video Conference Monday 5 August 2019 11.30 CEST (UTC+2)
by Hans Ekkehard Plesser 05 Aug '19

05 Aug '19

Dear NEST Developers! I would like to invite you to our next bi-weekly Open NEST Developer Video Conference tomorrow Monday 5 August, 11.30-12.30 CEST (UTC+2). See below for information about how to log into the meeting. The agenda for this meeting is also available online https://github.com/nest/nest-simulator/wiki/2019-08-05-Open-NEST-Developer-… • Welcome • Review of NEST User Mailing List • Review of open Github Pull Request • Review of open Github Issues See you soon! Hans Ekkehard Plesser ------------------ Log-in information ------------------ We use a virtual conference room provided by DFN (Deutsches Forschungsnetz). You can use the web client to connect. We however encourage everyone to use a headset for better audio quality or even a proper video conferencing system (see below) or software when available. Web client * Visit https://conf.dfn.de/webapp/conference/97938800 * Enter your name and allow your browser to use camera and microphone * The conference does not need a PIN to join, just click join and you're in. In case you see a dfnconf logo and the phrase "Auf den Meetingveranstalter warten", just be patient, the meeting host needs to join first (a voice will tell you). VC system/software How to log in with a video conferencing system, depends on you VC system or software. - Using the H.323 protocol (eg Polycom): vc.dfn.net##97938800 or 194.95.240.2##97938800 - Using the SIP protocol:97938800@vc.dfn.de - By telephone: +49-30-200-97938800 For those who do not have a video conference system or suitable software, Polycom provides a pretty good free app for iOS and Android, so you can join from your tablet (Polycom RealPresence Mobile, available from AppStore/PlayStore). Note that firewalls may interfere with videoconferencing in various and sometimes confusing ways. For more technical information on logging in from various VC systems, please see http://vcc.zih.tu-dresden.de/index.php?linkid=1.1.3.4 -- Prof. Dr. Hans Ekkehard Plesser Head, Data Science Section Faculty of Science and Technology Norwegian University of Life Sciences PO Box 5003, 1432 Aas, Norway Phone +47 6723 1560 Email hans.ekkehard.plesser(a)nmbu.no Home http://arken.nmbu.no/~plesser

1 0

[stdp_dopamine] Different concentrations for different number of threads
by Guilherme Miotto 22 Jul '19

22 Jul '19

Hi everyone, I'm getting strangely different results if I use stdp_dopamine_synapse with more than 1 local thread. For instance, the mini-code bellow creates a connection with an initial non-zero DA concentration and at t=1000 ms a spike arrives at the volume transmitter. If I run it with one thread I get an initial decay on the DA concentration and then a bump at t=1000 ms. Which is the expected behavior. But if I run the same thing with 2 threads, then I get just the decay. As if the spike hasn't arrived at the volume transmitter. Is this the expected behavior or is it maybe a bug? Best, Gui [image: Screenshot from 2019-06-25 18-32-58.png] [image: 1thread.png] [image: 2threads.png]

2 2

Open NEST Developer Video Conference Monday 22 June 2019 11.30 CEST (UTC+2)
by Dennis Terhorst 21 Jul '19

21 Jul '19

Dear NEST Developers! I would like to invite you to our next bi-weekly Open NEST Developer Video Conference tomorrow Monday 22 June, 11.30-12.30 CEST (UTC+2). See below for information about how to log into the meeting. The agenda for this meeting is also available online https://github.com/nest/nest-simulator/wiki/2019-07-22-Open-NEST-Developer-… 1. Welcome 2. Review of NEST User Mailing List <https://www.nest-simulator.org/mailinglist/hyperkitty/list/users@nest-simul…> 3. Review of open Github Pull Request <https://github.com/nest/nest-simulator/pulls> 4. Review of open Github Issues <https://github.com/nest/nest-simulator/issues> See you soon! best, Dennis Terhorst ------------------ Log-in information ------------------ We use a virtual conference room provided by DFN (Deutsches Forschungsnetz). You can use the web client to connect. We however encourage everyone to use a headset for better audio quality or even a proper video conferencing system (see below) or software when available. *Web client* * Visit https://conf.dfn.de/webapp/conference/97938800 * Enter your name and allow your browser to use camera and microphone * The conference *does not need a PIN* to join, just click *join* and you're in. In case you see a dfnconf logo and the phrase "Auf den Meetingveranstalter warten", just be patient, the meeting host needs to join first (a voice will tell you). *VC system/software* How to log in with a video conferencing system, depends on you VC system or software. - Using the H.323 protocol (eg Polycom): vc.dfn.net##97938800 or 194.95.240.2##97938800 - Using the SIP protocol:97938800@vc.dfn.de - By telephone: +49-30-200-97938800 For those who do not have a video conference system or suitable software, Polycom provides a pretty good free app for iOS and Android, so you can join from your tablet (Polycom RealPresence Mobile, available from AppStore/PlayStore). Note that firewalls may interfere with videoconferencing in various and sometimes confusing ways. For more technical information on logging in from various VC systems, please see http://vcc.zih.tu-dresden.de/index.php?linkid=1.1.3.4 -- Dipl.-Phys. Dennis Terhorst Coordinator Software Development Institute of Neuroscience and Medicine (INM-6) Computational and Systems Neuroscience & Theoretical Neuroscience, Institute for Advanced Simulation (IAS-6) Jülich Research Centre, Member of the Helmholz Association and JARA 52425 Jülich, Germany Building 15.22 Room 4004 Phone +49 2461 61-85062 Fax +49 2461 61- 9460 d.terhorst(a)fz-juelich.de

1 0

Record weights of synapses
by deluca.1665541＠studenti.uniroma1.it 15 Jul '19

15 Jul '19

Hello everyone! I need to take track of the weight of a set of synapses through time. I know that there already is a device to do that implemented in nest. According to its documentation, the 'weight recorder' should be created and, then, specified in a synapse model through the command: wr = nest.Create('weight_recorder') nest.CopyModel('stdp_synapse', 'model_name', {'weight_recorder': wr}) nest.Connect(..., syn_spec = 'model_name') The problem is that my synapses have weights distributed by a uniform distribution defined as: 'weight': {"distribution": "uniform", "low": w_min, "high": w_max} but whenever I try to set this in CopyModel I get the following error: terminate called without an active exception [q035:13577] *** Process received signal *** [q035:13577] Signal: Aborted (6) [q035:13577] Signal code: (-6) [q035:13577] [ 0] /lib64/libpthread.so.0(+0xf370)[0x2b4ae83d4370] [q035:13577] [ 1] /lib64/libc.so.6(gsignal+0x37)[0x2b4ae8d1f1d7] [q035:13577] [ 2] /lib64/libc.so.6(abort+0x148)[0x2b4ae8d208c8] [q035:13577] [ 3] /lib64/libstdc++.so.6(_ZN9__gnu_cxx27__verbose_terminate_handlerEv+0x165)[0x2b4b3cb049d5] [q035:13577] [ 4] /lib64/libstdc++.so.6(+0x5e946)[0x2b4b3cb02946] [q035:13577] [ 5] /lib64/libstdc++.so.6(+0x5e973)[0x2b4b3cb02973] [q035:13577] [ 6] /opt/NEST-nesters/lib64/python2.7/site-packages/nest/../../../libnestkernel.so(+0x85edc)[0x2b4b3b2eeedc] [q035:13577] [ 7] /lib64/libgomp.so.1(GOMP_parallel+0x3f)[0x2b4b3cdbb08f] [q035:13577] [ 8] /opt/NEST-nesters/lib64/python2.7/site-packages/nest/../../../libnestkernel.so(_ZN4nest12ModelManager21set_synapse_defaults_EmRK12lockPTRDatumI10DictionaryXadL_ZN14SLIInterpreter14DictionarytypeEEEE+0x65)[0x2b4b3b2eaae5] [q035:13577] [ 9] /opt/NEST-nesters/lib64/python2.7/site-packages/nest/../../../libnestkernel.so(_ZN4nest12ModelManager10copy_modelE4NameS1_12lockPTRDatumI10DictionaryXadL_ZN14SLIInterpreter14DictionarytypeEEEE+0x2bd)[0x2b4b3b2ecfdd] [q035:13577] [10] /opt/NEST-nesters/lib64/python2.7/site-packages/nest/../../../libnestkernel.so(_ZNK4nest10NestModule23CopyModel_l_l_DFunction7executeEP14SLIInterpreter+0x112)[0x2b4b3b2f93f2] [q035:13577] [11] /opt/NEST-nesters/lib64/python2.7/site-packages/nest/../../../libsli.so(_ZN13FunctionDatum7executeEP14SLIInterpreter+0x123)[0x2b4b3bf70473] [q035:13577] [12] /opt/NEST-nesters/lib64/python2.7/site-packages/nest/../../../libsli.so(_ZN14SLIInterpreter8execute_Em+0x312)[0x2b4b3bf6d382] [q035:13577] [13] /opt/NEST-nesters/lib64/python2.7/site-packages/nest/../../../libsli.so(_ZN14SLIInterpreter7executeERKSs+0x128)[0x2b4b3bf6d8a8] [q035:13577] [14] /opt/NEST-nesters/lib64/python2.7/site-packages/nest/pynestkernel.so(+0x23cf5)[0x2b4b3a160cf5] [q035:13577] [15] /lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x6d62)[0x2b4ae80dea62] [q035:13577] [16] /lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x67bd)[0x2b4ae80de4bd] [q035:13577] [17] /lib64/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7ed)[0x2b4ae80e0e3d] [q035:13577] [18] /lib64/libpython2.7.so.1.0(+0x7088d)[0x2b4ae806a88d] [q035:13577] [19] /lib64/libpython2.7.so.1.0(PyObject_Call+0x43)[0x2b4ae80458e3] [q035:13577] [20] /lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x17fd)[0x2b4ae80d94fd] [q035:13577] [21] /lib64/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7ed)[0x2b4ae80e0e3d] [q035:13577] [22] /lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x663c)[0x2b4ae80de33c] [q035:13577] [23] /lib64/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7ed)[0x2b4ae80e0e3d] [q035:13577] [24] /lib64/libpython2.7.so.1.0(PyEval_EvalCode+0x32)[0x2b4ae80e0f42] [q035:13577] [25] /lib64/libpython2.7.so.1.0(+0x10037f)[0x2b4ae80fa37f] [q035:13577] [26] /lib64/libpython2.7.so.1.0(PyRun_InteractiveOneFlags+0x150)[0x2b4ae80fc430] [q035:13577] [27] /lib64/libpython2.7.so.1.0(PyRun_InteractiveLoopFlags+0x5e)[0x2b4ae80fc61e] [q035:13577] [28] /lib64/libpython2.7.so.1.0(PyRun_AnyFileExFlags+0x3e)[0x2b4ae80fccae] [q035:13577] [29] /lib64/libpython2.7.so.1.0(Py_Main+0xc9f)[0x2b4ae810d91f] [q035:13577] *** End of error message *** Annullato (core dumped) Can somebody help me? Thank you! Chiara

3 3

Recording from synapses
by Guilherme Miotto 08 Jul '19

08 Jul '19

Hi everyone, Is there a generic way of recording from connections? I know that for weights we can use a weight_recorder, but what about other parameters? For instance, right now I would like to record the dopamine concentration (aka "n") from stdp_dopamine_synapse connections. Is this possible? Best, -- Gui Miotto

2 1

Open NEST Developer Video Conference Monday 8 June 2019 11.30 CEST (UTC+2)
by Dennis Terhorst 08 Jul '19

08 Jul '19

Dear NEST Developers! I would like to invite you to our next bi-weekly Open NEST Developer Video Conference today Monday 8 June, 11.30-12.30 CEST (UTC+2). See below for information about how to log into the meeting. The agenda for this meeting is also available online https://github.com/nest/nest-simulator/wiki/2019-07-08-Open-NEST-Developer-… 1. Welcome * /release celebration/ for *nest-2.18.0 <https://github.com/nest/nest-simulator/releases/tag/v2.18.0>* 2. Review of NEST User Mailing List <https://www.nest-simulator.org/mailinglist/hyperkitty/list/users@nest-simul…> 3. Discussion about #1195 CMAKE_INSTALL_PREFIX /usr/local <https://github.com/nest/nest-simulator/issues/1195> 4. Review of open Github Pull Request <https://github.com/nest/nest-simulator/pulls> 5. Review of open Github Issues <https://github.com/nest/nest-simulator/issues> See you soon! best, Dennis Terhorst ------------------ Log-in information ------------------ We use a virtual conference room provided by DFN (Deutsches Forschungsnetz). You can use the web client to connect. We however encourage everyone to use a headset for better audio quality or even a proper video conferencing system (see below) or software when available. *Web client* * Visit https://conf.dfn.de/webapp * Enter your name and allow your browser to use camera and microphone * Click green video-call button to open the call panel * In the "Search to call" box at the top right enter *97938800* and connect * The conference does not need a PIN to join, just click *join* and you're in. In case you see a dfnconf logo and the phrase "Auf den Meetingveranstalter warten", just be patient, the meeting host needs to join first (a voice will tell you). *VC system/software* How to log in with a video conferencing system, depends on you VC system or software. - Using the H.323 protocol (eg Polycom): vc.dfn.net##97938800 or 194.95.240.2##97938800 - Using the SIP protocol:97938800@vc.dfn.de - By telephone: +49-30-200-97938800 For those who do not have a video conference system or suitable software, Polycom provides a pretty good free app for iOS and Android, so you can join from your tablet (Polycom RealPresence Mobile, available from AppStore/PlayStore). Note that firewalls may interfere with videoconferencing in various and sometimes confusing ways. For more technical information on logging in from various VC systems, please see http://vcc.zih.tu-dresden.de/index.php?linkid=1.1.3.4 -- Dipl.-Phys. Dennis Terhorst Coordinator Software Development Institute of Neuroscience and Medicine (INM-6) Computational and Systems Neuroscience & Theoretical Neuroscience, Institute for Advanced Simulation (IAS-6) Jülich Research Centre, Member of the Helmholz Association and JARA 52425 Jülich, Germany Building 15.22 Room 4004 Phone +49 2461 61-85062 Fax +49 2461 61- 9460 d.terhorst(a)fz-juelich.de

2 1

NEST 2.18.0 released
by Hans Ekkehard Plesser 04 Jul '19

04 Jul '19

Dear NEST Users! It is a great pleasure to announce the release of NEST 2.18.0, which provides a number of new neuron and plasticity models and additional functionality. It improves memory allocation and performance during network construction. It includes a number of bug fixes and is the first release that can be installed via aptitude and in a Conda environment directly from conda-forge. For details, please see the change log at https://github.com/nest/nest-simulator/releases. NEST 2.18.0 is the result of 116 pull-requests (1128 commits) by 31 developers since NEST 2.16.0 which was released on 2018-08-21. Enjoy! Hans Ekkehard Plesser President, The NEST Initiative -- Prof. Dr. Hans Ekkehard Plesser Head, Data Science Section Faculty of Science and Technology Norwegian University of Life Sciences PO Box 5003, 1432 Aas, Norway Phone +47 6723 1560 Email hans.ekkehard.plesser(a)nmbu.no Home http://arken.nmbu.no/~plesser

1 0

Create new neuron module
by tschoepe＠techfak.uni-bielefeld.de 02 Jul '19

02 Jul '19

Dear All, I am relatively new to nest and want to implement a new neuron model. I've worked a lot with SpiNNaker previously. I am a research assistant and PhD student at the Technical Faculty in Bielefeld, Germany. Currently, I am trying to implement a new neuron model into nest. Because I want to use this model later on in the neurorbotics platform (NRP) I directly installed the NRP and I am using the nest version installed together with the NRP. I followed the instructions at: https://nest.github.io/nest-simulator/extension_modules I am able to install mymodule and to run the neuron model pif_psc_alpha coming with it. Now I tried to extend mymodule with a new neuron model. To achieve that I copied the iaf_psc_exp model's cpp and h file, renamed them to iaf_psc_exp_semd and changed them according to pif_psc_alpha. I was able to include the model into the nest library and run a short example script. Unfortunately, the iaf_psc_exp_semd model doesn't react to any stimulation with spikes. The membrane potential always stays at E_L. When I use the same python script but with the iad_psc_exp model I see a clear change in the membrane potential. Could someone check the files I've created for the new iaf_psc_exp_semd model to see what is wrong/missing? Thanks a lot and best regards, Thorben Schoepe First file: /* * iaf_psc_exp_semd.h * * This file is part of NEST. * * Copyright (C) 2004 The NEST Initiative * * NEST is free software: you can redistribute it and/or modify * it under the terms of the GNU General Public License as published by * the Free Software Foundation, either version 2 of the License, or * (at your option) any later version. * * NEST is distributed in the hope that it will be useful, * but WITHOUT ANY WARRANTY; without even the implied warranty of * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the * GNU General Public License for more details. * * You should have received a copy of the GNU General Public License * along with NEST. If not, see <http://www.gnu.org/licenses/>. * */ #ifndef IAF_PSC_EXP_SEMD_H #define IAF_PSC_EXP_SEMD_H // Includes from nestkernel: #include "archiving_node.h" #include "connection.h" #include "event.h" #include "nest_types.h" #include "recordables_map.h" #include "ring_buffer.h" #include "universal_data_logger.h" // Includes from sli: #include "dictdatum.h" namespace mynest { /* BeginDocumentation Name: iaf_psc_exp - Leaky integrate-and-fire neuron model with exponential PSCs. Description: iaf_psc_expp is an implementation of a leaky integrate-and-fire model with exponential shaped postsynaptic currents (PSCs) according to [1]. Thus, postsynaptic currents have an infinitely short rise time. The threshold crossing is followed by an absolute refractory period (t_ref) during which the membrane potential is clamped to the resting potential and spiking is prohibited. The linear subthresold dynamics is integrated by the Exact Integration scheme [2]. The neuron dynamics is solved on the time grid given by the computation step size. Incoming as well as emitted spikes are forced to that grid. An additional state variable and the corresponding differential equation represents a piecewise constant external current. The general framework for the consistent formulation of systems with neuron like dynamics interacting by point events is described in [2]. A flow chart can be found in [3]. Remarks: The present implementation uses individual variables for the components of the state vector and the non-zero matrix elements of the propagator. Because the propagator is a lower triangular matrix no full matrix multiplication needs to be carried out and the computation can be done "in place" i.e. no temporary state vector object is required. The template support of recent C++ compilers enables a more succinct formulation without loss of runtime performance already at minimal optimization levels. A future version of iaf_psc_exp will probably address the problem of efficient usage of appropriate vector and matrix objects. Parameters: The following parameters can be set in the status dictionary. E_L double - Resting membrane potential in mV. C_m double - Capacity of the membrane in pF tau_m double - Membrane time constant in ms. tau_syn_ex double - Time constant of postsynaptic excitatory currents in ms tau_syn_in double - Time constant of postsynaptic inhibitory currents in ms t_ref double - Duration of refractory period (V_m = V_reset) in ms. V_m double - Membrane potential in mV V_th double - Spike threshold in mV. V_reset double - Reset membrane potential after a spike in mV. I_e double - Constant input current in pA. t_spike double - Point in time of last spike in ms. Remarks: If tau_m is very close to tau_syn_ex or tau_syn_in, the model will numerically behave as if tau_m is equal to tau_syn_ex or tau_syn_in, respectively, to avoid numerical instabilities. For details, please see IAF_Neruons_Singularity.ipynb in the NEST source code (docs/model_details). iaf_psc_exp can handle current input in two ways: Current input through receptor_type 0 are handled as stepwise constant current input as in other iaf models, i.e., this current directly enters the membrane potential equation. Current input through receptor_type 1, in contrast, is filtered through an exponential kernel with the time constant of the excitatory synapse, tau_syn_ex. For an example application, see [4]. References: [1] Misha Tsodyks, Asher Uziel, and Henry Markram (2000) Synchrony Generation in Recurrent Networks with Frequency-Dependent Synapses, The Journal of Neuroscience, 2000, Vol. 20 RC50 p. 1-5 [2] Rotter S & Diesmann M (1999) Exact simulation of time-invariant linear systems with applications to neuronal modeling. Biologial Cybernetics 81:381-402. [3] Diesmann M, Gewaltig M-O, Rotter S, & Aertsen A (2001) State space analysis of synchronous spiking in cortical neural networks. Neurocomputing 38-40:565-571. [4] Schuecker J, Diesmann M, Helias M (2015) Modulated escape from a metastable state driven by colored noise. Physical Review E 92:052119 Sends: SpikeEvent Receives: SpikeEvent, CurrentEvent, DataLoggingRequest SeeAlso: iaf_psc_exp_ps FirstVersion: March 2006 Author: Moritz Helias */ /** * Leaky integrate-and-fire neuron with exponential PSCs. */ class iaf_psc_exp_semd : public nest::Archiving_Node { public: iaf_psc_exp_semd(); iaf_psc_exp_semd( const iaf_psc_exp_semd& ); /** * Import sets of overloaded virtual functions. * @see Technical Issues / Virtual Functions: Overriding, Overloading, and * Hiding */ using nest::Node::handle; using nest::Node::handles_test_event; nest::port send_test_event( Node&, nest::port, nest::synindex, bool ); void handle( nest::SpikeEvent& ); void handle( nest::CurrentEvent& ); void handle( nest::DataLoggingRequest& ); nest::port handles_test_event( nest::SpikeEvent&, nest::port ); nest::port handles_test_event( nest::CurrentEvent&, nest::port ); nest::port handles_test_event( nest::DataLoggingRequest&, nest::port ); void get_status( DictionaryDatum& ) const; void set_status( const DictionaryDatum& ); private: void init_state_( const Node& proto ); void init_buffers_(); void calibrate(); void update(nest::Time const&, const long, const long ); // The next two classes need to be friends to access the State_ class/member friend class nest::RecordablesMap< iaf_psc_exp_semd >; friend class nest::UniversalDataLogger< iaf_psc_exp_semd >; // ---------------------------------------------------------------- /** * Independent parameters of the model. */ struct Parameters_ { /** Membrane time constant in ms. */ double Tau_; /** Membrane capacitance in pF. */ double C_; /** Refractory period in ms. */ double t_ref_; /** Resting potential in mV. */ double E_L_; /** External current in pA */ double I_e_; /** Threshold, RELATIVE TO RESTING POTENTAIL(!). I.e. the real threshold is (E_L_+Theta_). */ double Theta_; /** reset value of the membrane potential */ double V_reset_; /** Time constant of excitatory synaptic current in ms. */ double tau_ex_; /** Time constant of inhibitory synaptic current in ms. */ double tau_in_; Parameters_(); //!< Sets default parameter values void get( DictionaryDatum& ) const; //!< Store current values in dictionary /** Set values from dictionary. * @returns Change in reversal potential E_L, to be passed to State_::set() */ double set( const DictionaryDatum& ); }; // ---------------------------------------------------------------- /** * State variables of the model. */ struct State_ { // state variables //! synaptic stepwise constant input current, variable 0 double i_0_; double i_1_; //!< presynaptic stepwise constant input current double i_syn_ex_; //!< postsynaptic current for exc. inputs, variable 1 double i_syn_in_; //!< postsynaptic current for inh. inputs, variable 1 double V_m_; //!< membrane potential, variable 2 //! absolute refractory counter (no membrane potential propagation) int r_ref_; State_(); //!< Default initialization void get( DictionaryDatum&, const Parameters_& ) const; /** Set values from dictionary. * @param dictionary to take data from * @param current parameters * @param Change in reversal potential E_L specified by this dict */ void set( const DictionaryDatum&, const Parameters_&, const double ); }; // ---------------------------------------------------------------- /** * Buffers of the model. */ struct Buffers_ { Buffers_( iaf_psc_exp_semd& ); Buffers_( const Buffers_&, iaf_psc_exp_semd& ); /** buffers and sums up incoming spikes/currents */ nest::RingBuffer spikes_ex_; nest::RingBuffer spikes_in_; std::vector< nest::RingBuffer > currents_; //! Logger for all analog data nest::UniversalDataLogger< iaf_psc_exp_semd > logger_; }; // ---------------------------------------------------------------- /** * Internal variables of the model. */ struct Variables_ { /** Amplitude of the synaptic current. This value is chosen such that a post-synaptic potential with weight one has an amplitude of 1 mV. @note mog - I assume this, not checked. */ // double PSCInitialValue_; // time evolution operator double P20_; double P11ex_; double P11in_; double P21ex_; double P21in_; double P22_; double weighted_spikes_ex_; double weighted_spikes_in_; int RefractoryCounts_; }; // Access functions for UniversalDataLogger ------------------------------- //! Read out the real membrane potential inline double get_V_m_() const { return S_.V_m_ + P_.E_L_; } inline double get_weighted_spikes_ex_() const { return V_.weighted_spikes_ex_; } inline double get_weighted_spikes_in_() const { return V_.weighted_spikes_in_; } inline double get_I_syn_ex_() const { return S_.i_syn_ex_; } inline double get_I_syn_in_() const { return S_.i_syn_in_; } // ---------------------------------------------------------------- /** * @defgroup iaf_psc_exp_data * Instances of private data structures for the different types * of data pertaining to the model. * @note The order of definitions is important for speed. * @{ */ Parameters_ P_; State_ S_; Variables_ V_; Buffers_ B_; /** @} */ //! Mapping of recordables names to access functions static nest::RecordablesMap< iaf_psc_exp_semd > recordablesMap_; }; inline nest::port mynest::iaf_psc_exp_semd::send_test_event( Node& target, nest::port receptor_type, nest::synindex, bool ) { nest::SpikeEvent e; e.set_sender( *this ); return target.handles_test_event( e, receptor_type ); } inline nest::port mynest::iaf_psc_exp_semd::handles_test_event( nest::SpikeEvent&, nest::port receptor_type ) { if ( receptor_type != 0 ) throw nest::UnknownReceptorType( receptor_type, get_name() ); return 0; } inline nest::port mynest::iaf_psc_exp_semd::handles_test_event( nest::CurrentEvent&, nest::port receptor_type ) { if ( receptor_type == 0 ) return 0; else if ( receptor_type == 1 ) return 1; else throw nest::UnknownReceptorType( receptor_type, get_name() ); } inline nest::port mynest::iaf_psc_exp_semd::handles_test_event( nest::DataLoggingRequest& dlr, nest::port receptor_type ) { if ( receptor_type != 0 ) throw nest::UnknownReceptorType( receptor_type, get_name() ); return B_.logger_.connect_logging_device( dlr, recordablesMap_ ); } inline void iaf_psc_exp_semd::get_status( DictionaryDatum& d ) const { P_.get( d ); S_.get( d, P_ ); Archiving_Node::get_status( d ); ( *d )[ nest::names::recordables ] = recordablesMap_.get_list(); } inline void iaf_psc_exp_semd::set_status( const DictionaryDatum& d ) { Parameters_ ptmp = P_; // temporary copy in case of errors const double delta_EL = ptmp.set( d ); // throws if BadProperty State_ stmp = S_; // temporary copy in case of errors stmp.set( d, ptmp, delta_EL ); // throws if BadProperty // We now know that (ptmp, stmp) are consistent. We do not // write them back to (P_, S_) before we are also sure that // the properties to be set in the parent class are internally // consistent. Archiving_Node::set_status( d ); // if we get here, temporaries contain consistent set of properties P_ = ptmp; S_ = stmp; } } // namespace #endif // IAF_PSC_EXP_SEMD_H Second file: /* * iaf_psc_exp_semd.cpp * * This file is part of NEST. * * Copyright (C) 2004 The NEST Initiative * * NEST is free software: you can redistribute it and/or modify * it under the terms of the GNU General Public License as published by * the Free Software Foundation, either version 2 of the License, or * (at your option) any later version. * * NEST is distributed in the hope that it will be useful, * but WITHOUT ANY WARRANTY; without even the implied warranty of * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the * GNU General Public License for more details. * * You should have received a copy of the GNU General Public License * along with NEST. If not, see <http://www.gnu.org/licenses/>. * */ #include "iaf_psc_exp_semd.h" // C++ includes: #include <limits> // Includes from libnestutil: #include "numerics.h" #include "propagator_stability.h" // Includes from nestkernel: #include "event_delivery_manager_impl.h" #include "exceptions.h" #include "kernel_manager.h" #include "universal_data_logger_impl.h" // Includes from sli: #include "dict.h" #include "dictutils.h" #include "doubledatum.h" #include "integerdatum.h" #include "lockptrdatum.h" using namespace nest; /* ---------------------------------------------------------------- * Recordables map * ---------------------------------------------------------------- */ nest::RecordablesMap< mynest::iaf_psc_exp_semd > mynest::iaf_psc_exp_semd::recordablesMap_; namespace nest { // Override the create() method with one call to RecordablesMap::insert_() // for each quantity to be recorded. template <> void RecordablesMap< mynest::iaf_psc_exp_semd >::create() { // use standard names whereever you can for consistency! insert_( names::V_m, &mynest::iaf_psc_exp_semd::get_V_m_ ); insert_( names::weighted_spikes_ex, &mynest::iaf_psc_exp_semd::get_weighted_spikes_ex_ ); insert_( names::weighted_spikes_in, &mynest::iaf_psc_exp_semd::get_weighted_spikes_in_ ); insert_( names::I_syn_ex, &mynest::iaf_psc_exp_semd::get_I_syn_ex_ ); insert_( names::I_syn_in, &mynest::iaf_psc_exp_semd::get_I_syn_in_ ); } } /* ---------------------------------------------------------------- * Default constructors defining default parameters and state * ---------------------------------------------------------------- */ mynest::iaf_psc_exp_semd::Parameters_::Parameters_() : Tau_( 10.0 ) // in ms , C_( 250.0 ) // in pF , t_ref_( 2.0 ) // in ms , E_L_( -70.0 ) // in mV , I_e_( 0.0 ) // in pA , Theta_( -55.0 - E_L_ ) // relative E_L_ , V_reset_( -70.0 - E_L_ ) // in mV , tau_ex_( 2.0 ) // in ms , tau_in_( 2.0 ) // in ms { } mynest::iaf_psc_exp_semd::State_::State_() : i_0_( 0.0 ) , i_syn_ex_( 0.0 ) , i_syn_in_( 0.0 ) , V_m_( 0.0 ) , r_ref_( 0 ) { } /* ---------------------------------------------------------------- * Parameter and state extractions and manipulation functions * ---------------------------------------------------------------- */ void mynest::iaf_psc_exp_semd::Parameters_::get( DictionaryDatum& d ) const { def< double >( d, names::E_L, E_L_ ); // resting potential def< double >( d, names::I_e, I_e_ ); def< double >( d, names::V_th, Theta_ + E_L_ ); // threshold value def< double >( d, names::V_reset, V_reset_ + E_L_ ); def< double >( d, names::C_m, C_ ); def< double >( d, names::tau_m, Tau_ ); def< double >( d, names::tau_syn_ex, tau_ex_ ); def< double >( d, names::tau_syn_in, tau_in_ ); def< double >( d, names::t_ref, t_ref_ ); } double mynest::iaf_psc_exp_semd::Parameters_::set( const DictionaryDatum& d ) { // if E_L_ is changed, we need to adjust all variables defined relative to // E_L_ const double ELold = E_L_; updateValue< double >( d, names::E_L, E_L_ ); const double delta_EL = E_L_ - ELold; if ( updateValue< double >( d, names::V_reset, V_reset_ ) ) V_reset_ -= E_L_; else V_reset_ -= delta_EL; if ( updateValue< double >( d, names::V_th, Theta_ ) ) Theta_ -= E_L_; else Theta_ -= delta_EL; updateValue< double >( d, names::I_e, I_e_ ); updateValue< double >( d, names::C_m, C_ ); updateValue< double >( d, names::tau_m, Tau_ ); updateValue< double >( d, names::tau_syn_ex, tau_ex_ ); updateValue< double >( d, names::tau_syn_in, tau_in_ ); updateValue< double >( d, names::t_ref, t_ref_ ); if ( V_reset_ >= Theta_ ) throw nest::BadProperty( "Reset potential must be smaller than threshold." ); if ( C_ <= 0 ) throw nest::BadProperty( "Capacitance must be strictly positive." ); if ( Tau_ <= 0 || tau_ex_ <= 0 || tau_in_ <= 0 ) throw nest::BadProperty( "Membrane and synapse time constants must be strictly positive." ); if ( t_ref_ < 0 ) throw nest::BadProperty( "Refractory time must not be negative." ); return delta_EL; } void mynest::iaf_psc_exp_semd::State_::get( DictionaryDatum& d, const Parameters_& p ) const { def< double >( d, names::V_m, V_m_ + p.E_L_ ); // Membrane potential } void mynest::iaf_psc_exp_semd::State_::set( const DictionaryDatum& d, const Parameters_& p, double delta_EL ) { if ( updateValue< double >( d, names::V_m, V_m_ ) ) V_m_ -= p.E_L_; else V_m_ -= delta_EL; } mynest::iaf_psc_exp_semd::Buffers_::Buffers_( iaf_psc_exp_semd& n ) : logger_( n ) { } mynest::iaf_psc_exp_semd::Buffers_::Buffers_( const Buffers_&, iaf_psc_exp_semd& n ) : logger_( n ) { } /* ---------------------------------------------------------------- * Default and copy constructor for node * ---------------------------------------------------------------- */ mynest::iaf_psc_exp_semd::iaf_psc_exp_semd() : Archiving_Node() , P_() , S_() , B_( *this ) { recordablesMap_.create(); } mynest::iaf_psc_exp_semd::iaf_psc_exp_semd( const iaf_psc_exp_semd& n ) : Archiving_Node( n ) , P_( n.P_ ) , S_( n.S_ ) , B_( n.B_, *this ) { } /* ---------------------------------------------------------------- * Node initialization functions * ---------------------------------------------------------------- */ void mynest::iaf_psc_exp_semd::init_state_( const Node& proto ) { const iaf_psc_exp_semd& pr = downcast< iaf_psc_exp_semd >( proto ); S_ = pr.S_; } void mynest::iaf_psc_exp_semd::init_buffers_() { B_.spikes_ex_.clear(); // includes resize B_.spikes_in_.clear(); // includes resize B_.currents_.clear(); // includes resize B_.logger_.reset(); Archiving_Node::clear_history(); } void mynest::iaf_psc_exp_semd::calibrate() { B_.currents_.resize( 2 ); // ensures initialization in case mm connected after Simulate B_.logger_.init(); const double h = Time::get_resolution().get_ms(); // numbering of state vaiables: i_0 = 0, i_syn_ = 1, V_m_ = 2 // commented out propagators: forward Euler // needed to exactly reproduce Tsodyks network // these P are independent V_.P11ex_ = std::exp( -h / P_.tau_ex_ ); // P11ex_ = 1.0-h/tau_ex_; V_.P11in_ = std::exp( -h / P_.tau_in_ ); // P11in_ = 1.0-h/tau_in_; V_.P22_ = std::exp( -h / P_.Tau_ ); // P22_ = 1.0-h/Tau_; // these are determined according to a numeric stability criterion V_.P21ex_ = propagator_32( P_.tau_ex_, P_.Tau_, P_.C_, h ); V_.P21in_ = propagator_32( P_.tau_in_, P_.Tau_, P_.C_, h ); // P21ex_ = h/C_; // P21in_ = h/C_; V_.P20_ = P_.Tau_ / P_.C_ * ( 1.0 - V_.P22_ ); // P20_ = h/C_; // TauR specifies the length of the absolute refractory period as // a double in ms. The grid based iaf_psc_exp can only handle refractory // periods that are integer multiples of the computation step size (h). // To ensure consistency with the overall simulation scheme such conversion // should be carried out via objects of class nest::Time. The conversion // requires 2 steps: // 1. A time object r is constructed defining representation of // TauR in tics. This representation is then converted to computation // time steps again by a strategy defined by class nest::Time. // 2. The refractory time in units of steps is read out get_steps(), a // member function of class nest::Time. // // Choosing a TauR that is not an integer multiple of the computation time // step h will leed to accurate (up to the resolution h) and self-consistent // results. However, a neuron model capable of operating with real valued // spike time may exhibit a different effective refractory time. V_.RefractoryCounts_ = Time( Time::ms( P_.t_ref_ ) ).get_steps(); // since t_ref_ >= 0, this can only fail in error assert( V_.RefractoryCounts_ >= 0 ); } void mynest::iaf_psc_exp_semd::update( const Time& origin, const long from, const long to ) { assert( to >= 0 && ( delay ) from < kernel().connection_manager.get_min_delay() ); assert( from < to ); // evolve from timestep 'from' to timestep 'to' with steps of h each for ( long lag = from; lag < to; ++lag ) { if ( S_.r_ref_ == 0 ) // neuron not refractory, so evolve V S_.V_m_ = S_.V_m_ * V_.P22_ + S_.i_syn_ex_ * V_.P21ex_ // membrane potential equals membrane potential times exponetial decay plus postsynpatic excitatory/inhibitory currents time numerical stability factor plus new input current times exponential decay + S_.i_syn_in_ * V_.P21in_ + ( P_.I_e_ + S_.i_0_ ) * V_.P20_; // S_.V_m : membrane potential else // V_.P22 : membrane potential decay { // S_.i_syn_ex / S_.i_syn_in : excitatory / inhibitory postsynaptic current } // V_.P21in / V_.P21ex : numeric stability criterion parameter // P_.I_e : static input current { // S_.i_0_ : presynaptic input current this timestep } // S_.i_1_ : presynaptic input current next timestep { } --S_.r_ref_; // neuron is absolute refractory // exponential decaying PSCs S_.i_syn_ex_ *= V_.P11ex_; S_.i_syn_in_ *= V_.P11in_; // add evolution of presynaptic input current S_.i_syn_ex_ += ( 1. - V_.P11ex_ ) * S_.i_1_; // the spikes arriving at T+1 have an immediate effect on the state of the // neuron V_.weighted_spikes_ex_ = B_.spikes_ex_.get_value( lag ); V_.weighted_spikes_in_ = B_.spikes_in_.get_value( lag ); S_.i_syn_ex_ += V_.weighted_spikes_ex_; S_.i_syn_in_ += V_.weighted_spikes_in_; if ( S_.V_m_ >= P_.Theta_ ) // threshold crossing { S_.r_ref_ = V_.RefractoryCounts_; S_.V_m_ = P_.V_reset_; set_spiketime( Time::step( origin.get_steps() + lag + 1 ) ); SpikeEvent se; kernel().event_delivery_manager.send( *this, se, lag ); } // set new input current S_.i_0_ = B_.currents_[ 0 ].get_value( lag ); S_.i_1_ = B_.currents_[ 1 ].get_value( lag ); // log state data B_.logger_.record_data( origin.get_steps() + lag ); } } void mynest::iaf_psc_exp_semd::handle( SpikeEvent& e ) { assert( e.get_delay() > 0 ); if ( e.get_weight() >= 0.0 ) B_.spikes_ex_.add_value( e.get_rel_delivery_steps( kernel().simulation_manager.get_slice_origin() ), e.get_weight() * e.get_multiplicity() ); else B_.spikes_in_.add_value( e.get_rel_delivery_steps( kernel().simulation_manager.get_slice_origin() ), e.get_weight() * e.get_multiplicity() ); } void mynest::iaf_psc_exp_semd::handle( CurrentEvent& e ) { assert( e.get_delay() > 0 ); const double c = e.get_current(); const double w = e.get_weight(); // add weighted current; HEP 2002-10-04 if ( 0 == e.get_rport() ) { B_.currents_[ 0 ].add_value( e.get_rel_delivery_steps( kernel().simulation_manager.get_slice_origin() ), w * c ); } if ( 1 == e.get_rport() ) { B_.currents_[ 1 ].add_value( e.get_rel_delivery_steps( kernel().simulation_manager.get_slice_origin() ), w * c ); } } void mynest::iaf_psc_exp_semd::handle( DataLoggingRequest& e ) { B_.logger_.handle( e ); }

2 2

Installation of Nest Simulator with csa
by yannicknodem＠gmail.com 27 Jun '19

27 Jun '19

Hi, I try to install csa package with libneurosim to use with nest simulator. The installation of libneurosim with python support take place without any issues. When I try to install csa with these commands: ./autogen.sh ./configure ./configure --prefix=$HOME/opt/csa --with-libneurosim=$HOME/opt/libneurosim make The installation fails at the make step with these output errors: _/home/yannick/Downloads/csa-master/libpycsa/pycsa.cpp:189: undefined reference to PyGILState_Ensure' /home/yannick/Downloads/csa-master/libpycsa/pycsa.cpp:190: undefined reference to PyList_New' /home/yannick/Downloads/csa-master/libpycsa/pycsa.cpp:197: undefined reference to PyObject_CallFunctionObjArgs' /home/yannick/Downloads/csa-master/libpycsa/pycsa.cpp:198: undefined reference to PyList_SetItem' /home/yannick/Downloads/csa-master/libpycsa/pycsa.cpp:202: undefined reference to PyLong_FromLong' /home/yannick/Downloads/csa-master/libpycsa/pycsa.cpp:202: undefined reference to PyObject_CallFunctionObjArgs' /home/yannick/Downloads/csa-master/libpycsa/pycsa.cpp:209: undefined reference to PyGILState_Release' .libs/libpycsa_la-pycsa.o: In function error(std::_cxx11::basic_string<char, std::char_traits, std::allocator >)': /home/yannick/Downloads/csa-master/libpycsa/pycsa.cpp:53: undefined reference to PyGILState_Release' .libs/libpycsa_la-pycsa.o: In function PyCSA::PyCSAGenerator::setMask(std::vector<ConnectionGenerator::Mask, std::allocatorConnectionGenerator::Mask >&, int)': /home/yannick/Downloads/csa-master/libpycsa/pycsa.cpp:214: undefined reference to `PyGILState_Release' collect2: error: ld returned 1 exit status Makefile:444: recipe for target 'libpycsa.la' failed make[2]: *** [libpycsa.la] Error 1 make[2]: Leaving directory '/home/yannick/Downloads/csa-master/libpycsa' Makefile:420: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/home/yannick/Downloads/csa-master' Makefile:350: recipe for target 'all' failed make: *** [all] Error 2 I work on ubuntu 18.04 with python 3.7.3 Thank you

1 1

Open NEST Developer *real* Conference Monday 24-25 June 2019
by Dennis Terhorst 21 Jun '19

21 Jun '19

Dear NEST Developers! Our next meeting will be the _real_ Open NEST User and Developer Conference (non-video!) in Ås, Norway. This will of course replace the usual video meeting. Looking forward to seeing you all there! best, Dennis Terhorst -- Dipl.-Phys. Dennis Terhorst Coordinator Software Development Institute of Neuroscience and Medicine (INM-6) Computational and Systems Neuroscience & Theoretical Neuroscience, Institute for Advanced Simulation (IAS-6) Jülich Research Centre, Member of the Helmholz Association and JARA 52425 Jülich, Germany Building 15.22 Room 4004 Phone +49 2461 61-85062 Fax +49 2461 61- 9460 d.terhorst(a)fz-juelich.de

1 0

Options for plotting simulated data
by TOM BUGNON 21 Jun '19

21 Jun '19

Hi all, I was wondering if the community had any suggestions of toolboxes to plot the output of simulations (ideally in python) and make publication-quality figures. I am mostly thinking of eg spike rasterplots or heatmaps (time x variable) with large datasets. Ideally in such a way that those can be aligned with other figures easily (spike histograms, LFP, you name it) This is a very general problem that I suppose a lot of us have been confronted with, and I actually haven't found so far a good solution: -matplotlib (python) is robust and can handle large datasets but looks bad and is a nightmare to deal with when trying to make figures with multiple subplots of specific sizes etc - altair (python) looked promising and versatile but is actually struggling with large datasets - The existing projects for (analysis and) visualization of neural data that I have checked (elephant spykes etc) are either quite specific/limited or not very active. Additionally they are focused on real ePhys data: either multiunit spike data or single neuron continuous data, while simulations provide both. Happy to get any suggestions and share some code ! Thanks, Tom

2 1

AdEx gap junctions
by domenico.guarino＠cnrs.fr 19 Jun '19

19 Jun '19

Hello, from the NEST docs(https://www.nest-simulator.org/simulations-with-gap-junctions/), I see that only the cell model 'hh_psc_alpha_gap' can use gap junctions. Is it true? If true, are there any plans (or hacks) to have it also for the AdEx model? Thanks!

3 2

Nest installation
by gerlach.mi＠gmx.de 13 Jun '19

13 Jun '19

Hello, I am using Anaconda on a Mac OS X platform. I installed nest using homebrew by following the instructions on this page: https://nest-simulator.readthedocs.io/en/latest/installation/mac_install.ht… After finishing the installation, IPython first could not find the nest module, so I manually copied the nest folder that was created in /Users/name/opt/nest/lib/python3.7/site-packages/nest into /anaconda/lib/python3.7/site-packages/nest Now IPython can import the nest module, but returns an error message when I try to run a basic nest example: "module 'nest' has no attribute 'Create' ". I am sorry for failing at a very basic level here, but I tried for quite some time and could not get it running despite trying different instructions. I would greatly appreciate it if anyone could help me or give me a hint into the right direction, thanks in advance!

4 8

Where are the archive questions?
by Abolfazl Ziaeemehr 12 Jun '19

12 Jun '19

I remember before the new mailing list I had access to the archived questions and some times by digging into them I could find some answers to simple questions. Now I can not find them. Thank you let me know if there are still available. One more silly question. Do we have access to synaptic current in iaf psc alpha model. We can simply plot the post synaptic potential for two couple neuron (in tutorial <https://nest-simulator.readthedocs.io/en/latest/tutorials/pynest_tutorial/p…>), how about the I_syn? Excuse me if seems easy, and thanks for guide.

2 1

parallel computing on a shared cluster
by Jimmy Mulder 03 Jun '19

03 Jun '19

Hi everyone, For my masters thesis I'm using (py)NEST for the first time. I have some questions about parallel computing. first a short intro to give you the context: My research group has access to 4 clusters; 2 with a focus on RAM/CPU on 2 with focus on GPU. These are shared systems; resources are dynamically allocated depending on the number of users doing calculations. The way these clusters are set up allows me to simply set "local_num_threads" to a value of 10, and if no one else is using it the cluster manager will say I get 1000% CPU power, and the speed will increase about 8-fold as expected. (in case you find that number confusing: the manager rates 1 core as 100%, so 56 cores translates to 5600% CPU power) However, problems start to occur when others are using the cluster as well. I might get 500% CPU power one moment, and just 300% the next. At this point it is actually FASTER to only request 1 thread and get the full 100% power. I'm guessing this is due to the architecture; something with nodes A and B waiting on node C which has been temporarily allocated to my colleague? *So, the questions:* 1. Does NEST prefer CPU or GPU? Is it RAM intensive? I couldn't find this on your website, or anywhere really. Are there ballpark numbers for the memory required for 10^9 connections? 2. Am I abusing the "local_num_threads" mechanic by applying it to a cluster like this? Why is 1 thread sometimes faster than 10 threads? 3. Would switching to MPI help? 4. If so: the documentation says I need to run $NEST_SOURCE_DIR/configure -- with-mpi, but there is no "configure" folder or command to be found anywhere, and this line fails. What and where is this "configure"? Any help would be greatly appreciated. Thank you for your time. Kind regards, Jimmy Mulder

2 1

Open NEST Developer Video Conference Monday 3 June 2019 11.30 CET (UTC+2)
by Dennis Terhorst 02 Jun '19

02 Jun '19

Dear NEST Developers! I would like to invite you to our next bi-weekly Open NEST Developer Video Conference tomorrow Monday 3 June, 11.30-12.30 CET (UTC+2). This is the substitute for the postponed meeting from last week and the missing meeting next week (pentecost). See below for information about how to log into the meeting. The agenda for this meeting is also available online https://github.com/nest/nest-simulator/wiki/2019-06-03-Open-NEST-Developer-… 1. Welcome 2. New features in NEST3 / current developments 3. Review of NEST User Mailing List <https://www.nest-simulator.org/mailinglist/postorius/lists/users.nest-simul…> 4. Review of open Github Pull Request <https://github.com/nest/nest-simulator/pulls> 5. Review of open Github Issues <https://github.com/nest/nest-simulator/issues> See you soon! best, Dennis Terhorst ------------------ Log-in information ------------------ We use a virtual conference room provided by DFN (Deutsches Forschungsnetz). You can use the web client to connect. We however encourage everyone to use a headset for better audio quality or even a proper video conferencing system (see below) or software when available. *Web client* * Visit https://conf.dfn.de/webapp * Enter your name and allow your browser to use camera and microphone * Click green video-call button to open the call panel * In the "Search to call" box at the top right enter *97938800* and connect * The conference does not need a PIN to join, just click *join* and you're in. In case you see a dfnconf logo and the phrase "Auf den Meetingveranstalter warten", just be patient, the meeting host needs to join first (a voice will tell you). *VC system/software* How to log in with a video conferencing system, depends on you VC system or software. - Using the H.323 protocol (eg Polycom): vc.dfn.net##97938800 or 194.95.240.2##97938800 - Using the SIP protocol:97938800@vc.dfn.de - By telephone: +49-30-200-97938800 For those who do not have a video conference system or suitable software, Polycom provides a pretty good free app for iOS and Android, so you can join from your tablet (Polycom RealPresence Mobile, available from AppStore/PlayStore). Note that firewalls may interfere with videoconferencing in various and sometimes confusing ways. For more technical information on logging in from various VC systems, please see http://vcc.zih.tu-dresden.de/index.php?linkid=1.1.3.4 -- Dipl.-Phys. Dennis Terhorst Coordinator Software Development Institute of Neuroscience and Medicine (INM-6) Computational and Systems Neuroscience & Theoretical Neuroscience, Institute for Advanced Simulation (IAS-6) Jülich Research Centre, Member of the Helmholz Association and JARA 52425 Jülich, Germany Building 15.22 Room 4004 Phone +49 2461 61-85062 Fax +49 2461 61- 9460 d.terhorst(a)fz-juelich.de

1 0

Open NEST Developer Video Conference Monday 27 May 2019 -- POSTPONED
by Dennis Terhorst 27 May '19

27 May '19

Dear NEST Developers! our next bi-weekly Open NEST Developer Video Conference would be today. However, due to many participants not being available and the next meeting falling on Pentecost Monday we decided to do one meeting on the out-of-phase Monday June 3rd. Monday 3 June, 11.30-12.30 CET (UTC+2). (note: out-of-phase) An invitation to that meeting will be sent separately. best, Dennis Terhorst -- Dipl.-Phys. Dennis Terhorst Coordinator Software Development Institute of Neuroscience and Medicine (INM-6) Computational and Systems Neuroscience & Theoretical Neuroscience, Institute for Advanced Simulation (IAS-6) Jülich Research Centre, Member of the Helmholz Association and JARA 52425 Jülich, Germany Building 15.22 Room 4004 Phone +49 2461 61-85062 Fax +49 2461 61- 9460 d.terhorst(a)fz-juelich.de

1 0

Passing options to recording backends via Python
by Simon Oehrl 23 May '19

23 May '19

Hello everyone, I am currently working on a custom recording backend based on the nestio branch of this fork: https://github.com/jougs/nest-simulator/. I want the user to be able to customize the behavior of my backend from their python code. I can see that the RecordingBackend class has the virtual functions set_status() and get_status() that would enable such a thing and I see that other recording backends implement them accordingly. However, I haven't found an example yet how to get access to the recording backend to call these functions. Can anyone give me hint on how to do that? Kind regards Simon

1 0

Fwd: Re: Nest Neuron Modelling - Tonic Neuron Input and Synaptic Weight Normalization
by Abigail Morrison 20 May '19

20 May '19

Dear Benedikt > 1) Are there any implementations for tonic neuron input, that means an > additional Neuron input channel that mulitplies with all synaptic inputs? We don't have an implementation that does this, but I don't see any reason why you can't make your own. The most effective way to do this is using NESTML, then you don't have to worry about C++ or numerics. A brief description of NESTML with links to publications and Github is here: https://www.fz-juelich.de/ias/jsc/EN/Expertise/SimLab/slns/research/nestml/… we are happy to support you in using this. > > 2) Can synaptic weights be normalized, in particular keeping the sum of > all inputs of a single neuron equal to 1? This is tricky. We did implement something close to this for a paper: https://www.frontiersin.org/articles/10.3389/fncom.2010.00160/full but we did not merge the infrastructure changes with master, because we felt it wasn't general enough. Making a general version would be a large, complicated job. As a workaround, you could consider running your simulation in small time segments, and after each segment you can read-out, sum and normalise the incoming weights for each neuron 'manually' from your simulation script. For a small network this will work fine, but it won't scale. All the best, Abigail -- Prof. Dr. Abigail Morrison IAS-6 / INM-6 / SimLab Neuroscience Jülich Research Center & Institute of Cognitive Neuroscience Ruhr-University Bochum http://www.fz-juelich.de/inm/inm-6 http://www.fz-juelich.de/ias/jsc/slns http://www.ikn.psy.ruhr-uni-bochum.de Office: +49 2461 61-9805 Fax # : +49 2461 61-9460 ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------ Forschungszentrum Juelich GmbH 52425 Juelich Sitz der Gesellschaft: Juelich Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 Vorsitzender des Aufsichtsrats: MinDir Volker Rieke Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender), Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt, Prof. Dr. Sebastian M. Schmidt ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------

1 0

PhD scholarship within Data Science and Computational Neuroscience at the Norwegian University of Life Sciences (NMBU)
by Kristin Tøndel 15 May '19

15 May '19

The Faculty of Science and Technology at the Norwegian University of Life Sciences (NMBU) has a vacant 3-year PhD-position related to Data Science and Computational Neuroscience: https://www.jobbnorge.no/en/available-jobs/job/168816/phd-scholarship-withi… Please share with your network. Best regards, Kristin Tøndel

1 0

Open NEST Developer Video Conference Monday 13 May 2019 11.30 CET (UTC+2)
by Dennis Terhorst 13 May '19

13 May '19

Dear NEST Developers! I would like to invite you to our next bi-weekly Open NEST Developer Video Conference today Monday 13 May, 11.30-12.30 CET (UTC+2). See below for information about how to log into the meeting. The agenda for this meeting is also available online https://github.com/nest/nest-simulator/wiki/2019-05-13-Open-NEST-Developer-… 1. Welcome 2. NEST Initiative web services 3. Review of NEST User Mailing List <https://www.nest-simulator.org/mailinglist/postorius/lists/users.nest-simul…> 4. Review of open Github Pull Request <https://github.com/nest/nest-simulator/pulls> 5. Review of open Github Issues <https://github.com/nest/nest-simulator/issues> See you soon! best, Dennis Terhorst ------------------ Log-in information ------------------ We use a virtual conference room provided by DFN (Deutsches Forschungsnetz). You can use the web client to connect. We however encourage everyone to use a headset for better audio quality or even a proper video conferencing system (see below) or software when available. *Web client* * Visit https://conf.dfn.de/webapp * Enter your name and allow your browser to use camera and microphone * Click green video-call button to open the call panel * In the "Search to call" box at the top right enter *97938800* and connect * The conference does not need a PIN to join, just click *join* and you're in. In case you see a dfnconf logo and the phrase "Auf den Meetingveranstalter warten", just be patient, the meeting host needs to join first (a voice will tell you). *VC system/software* How to log in with a video conferencing system, depends on you VC system or software. - Using the H.323 protocol (eg Polycom): vc.dfn.net##97938800 or 194.95.240.2##97938800 - Using the SIP protocol:97938800@vc.dfn.de - By telephone: +49-30-200-97938800 For those who do not have a video conference system or suitable software, Polycom provides a pretty good free app for iOS and Android, so you can join from your tablet (Polycom RealPresence Mobile, available from AppStore/PlayStore). Note that firewalls may interfere with videoconferencing in various and sometimes confusing ways. For more technical information on logging in from various VC systems, please see http://vcc.zih.tu-dresden.de/index.php?linkid=1.1.3.4 -- Dipl.-Phys. Dennis Terhorst Coordinator Software Development Institute of Neuroscience and Medicine (INM-6) Computational and Systems Neuroscience & Theoretical Neuroscience, Institute for Advanced Simulation (IAS-6) Jülich Research Centre, Member of the Helmholz Association and JARA 52425 Jülich, Germany Building 15.22 Room 4004 Phone +49 2461 61-85062 Fax +49 2461 61- 9460 d.terhorst(a)fz-juelich.de

1 0

Nest Neuron Modelling - Tonic Neuron Input and Synaptic Weight Normalization
by Benedikt Feldotto 08 May '19

08 May '19

Dear all, I am wondering about two specific neuron characteristics to be modelled in Nest. Since I did not really find documentation I want to ask about those features here: 1) Are there any implementations for tonic neuron input, that means an additional Neuron input channel that mulitplies with all synaptic inputs? 2) Can synaptic weights be normalized, in particular keeping the sum of all inputs of a single neuron equal to 1? On top, information on having those features modelled in PyNN would be a plus. Thank you very much in advance for any hints where to look, possible solutions, or developer support on how to implement these features! Best Regards, Benedikt

1 0

2025

2024

2023

2022

2021

2020

2019

NEST Users