- NEST Users - NEST Initiative Mail

Problems after ubuntu installed nest-3.0 built on Aug 24 2021
by Ing Jyh Tsang 31 Aug '21

31 Aug '21

Hi, After my ubuntu upgraded nest. Whenever I run a program it does not seems to identify the nest module. For example, running the twoneuron.py example gives: Traceback (most recent call last): File "twoneurons.py", line 43, in <module> import nest.voltage_trace ModuleNotFoundError: No module named 'nest.voltage_trace' Please solution for this? I tried remove and reinstalling and did not work. I did not try building it. Thanks, Inton

2 4

AttributeError: module 'nest' has no attribute 'SetKernelStatus'
by Alberto 31 Aug '21

31 Aug '21

Hi, suddenly, I am starting having this error. I have both PyNN and Nest installed. If it's more related to the PyNN community, I will forward this message to them, but at this moment I don't know if it's more related to Nest or PyNN side. Maybe some of you have met a similar issue. >>> import pyNN.nest as sim Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/home/alberto/.local/lib/python3.8/site-packages/pyNN/nest/__init__.py", line 18, in <module> from . import simulator File "/home/alberto/.local/lib/python3.8/site-packages/pyNN/nest/simulator.py", line 261, in <module> state = _State() # a Singleton, so only a single instance ever exists File "/home/alberto/.local/lib/python3.8/site-packages/pyNN/nest/simulator.py", line 58, in __init__ self.spike_precision = "off_grid" File "/home/alberto/.local/lib/python3.8/site-packages/pyNN/nest/simulator.py", line 114, in _set_spike_precision nest.SetKernelStatus({'off_grid_spiking': True}) AttributeError: module 'nest' has no attribute 'SetKernelStatus' Thanks, Alberto

3 4

Open NEST Developer Video Conference Monday 30 August 2021 11:30 CEST (UTC+2)
by Dennis Terhorst 30 Aug '21

30 Aug '21

Dear NEST Users & Developers! I would like to invite you to our next fortnightly Open NEST Developer Video Conference, today Monday 30 August, 11.30-12.30 CEST (UTC+2). As usual, in the Project team round, a contact person of each team will give a short statement summarizing ongoing work in the team and cross-cutting points that need discussion among the teams. The remainder of the meeting we would go into a more in-depth discussion of topics that came up on the mailing list or that are suggested by the teams. Agenda * Welcome * Review of NEST User Mailing List * Project team round * In-depth discussion (optional) The agenda for this meeting is also available online, see https://github.com/nest/nest-simulator/wiki/2021-08-30-Open-NEST-Developer-… Looking forward to seeing 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

1 0

ISAV'21: In Situ Infrastructures for Enabling Extreme-scale Analysis and Visualization
by Tom Vierjahn 19 Aug '21

19 Aug '21

Dear all, for our in situ workshop at this year’s Supercomputing (https://vis.lbl.gov/events/ISAV2021/) we are still looking for submissions. So, if you are doing work on visualizing or analysing the results of a NEST simulation while it is running, you might consider submitting, quickly. The deadline will be extended to August 27. Please, find the CfP below. Cheers, Tom Vierjahn -- Tom Vierjahn Professor of Computer Science Dept. Business Studies and Information Technology Westphalian University of Applied Sciences Bocholt, Germany -- ISAV 2021: In Situ Infrastructures for Enabling Extreme-scale Analysis and Visualization # Workshop Theme The considerable interest in the HPC community regarding in situ analysis and visualization is due to several factors. First is an I/O cost savings, where data is analyzed/visualized while being generated, without first storing to a file system. Second is the potential for increased accuracy, where fine temporal sampling of transient analysis might expose some complex behavior missed in coarse temporal sampling. Third is the ability to use all available resources, CPUs and accelerators, in the computation of analysis products. The workshop brings together researchers, developers and practitioners from industry, academia, and government laboratories developing, applying, and deploying in situ methods in extreme-scale, high performance computing. The goal is to present research findings, lessons learned, and insights related to developing and applying in situ methods and infrastructure across a range of science and engineering applications in HPC environments; to discuss topics like opportunities presented by new architectures, existing infrastructure needs, requirements, and gaps, and experiences to foster and enable in situ analysis and visualization; to serve as a “center of gravity” for researchers, practitioners, and users/consumers of in situ methods and infrastructure in the HPC space. # Participation/Call for Papers We invite two types of submissions to ISAV 2021: (1) short, 4-page (+references) papers that present research results, that identify opportunities or challenges, and that present case studies/best practices for in situ methods/infrastructure in the areas of data management, analysis and visualization; (2) lightning presentation submissions, consisting of a 1- or 2-page (+references) submission, for a brief oral presentation at the workshop. Short papers will appear in the workshop proceedings and authors will be invited to give an oral presentation of 15 to 20 minutes; lightning round submissions invited to present at the workshop will have author names and titles included as part of the proceedings. Submissions of both types are welcome that fall within one or more areas of interest. Areas of interest for ISAV include, but are not limited to: - In situ infrastructures: Novel designs for systems and libraries; Opportunities; Gaps - System resources, hardware, and emerging architectures: Enabling Hardware; Hardware and architectures that provide opportunities for In situ processing, such as burst buffers, staging computations on I/O nodes, sharing cores within a node for both simulation and in situ processing; Efficient use of heterogeneous architectures. - Methods/algorithms: Best practices; Analysis: Feature detection, statistical methods, temporal methods, geometric and topological methods; Visualization: information visualization, scientific visualization, time-varying methods; Data reduction/compression. - Case Studies and Data Sources: Examples/case studies of solving a specific science challenge with in situ methods/infrastructure; In situ methods/systems applied to data from simulations and/or experiments/observations. - Simulation and Workflows: Integration, data modeling, software-engineering; Resilience: error detection, fault recovery; Workflows for supporting complex in situ processing pipelines. - Requirements and Usability: Reproducibility, provenance and metadata; Using in situ to enable rapid and flexible post-processing; Simplified access to extreme heterogeneous resources.

1 0

Mailing list hick-up
by Jochen Martin Eppler 19 Aug '21

19 Aug '21

Hi all! During an upgrade of the Mailman system today, some of you were affected by a small hick-up that caused your subscription to be suspended (not cancelled). Meanwhile, I've re-enabled all of you and you should be able to receive mails again just fine. Sorry for any confusion caused by this. Cheers, Jochen! -- Dr. Jochen Martin Eppler Phone: +49(2461)61-96653 ---------------------------------- Simulation Laboratory Neuroscience Jülich Supercomputing Centre Institute for Advanced Simulation ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------ 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), Dr. Astrid Lambrecht, Prof. Dr. Frauke Melchior ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------

1 0

test
by Jochen Martin Eppler 19 Aug '21

19 Aug '21

Please ignore -- Dr. Jochen Martin Eppler Phone: +49(2461)61-96653 ---------------------------------- Simulation Laboratory Neuroscience Jülich Supercomputing Centre Institute for Advanced Simulation ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------ 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), Dr. Astrid Lambrecht, Prof. Dr. Frauke Melchior ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------

1 0

Test
by Jochen Martin Eppler 19 Aug '21

19 Aug '21

Please ignore! -- Dr. Jochen Martin Eppler Phone: +49(2461)61-96653 ---------------------------------- Simulation Laboratory Neuroscience Jülich Supercomputing Centre Institute for Advanced Simulation ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------ 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), Dr. Astrid Lambrecht, Prof. Dr. Frauke Melchior ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------

1 0

Open NEST Developer Video Conference Monday 16 August 2021 11:30 CEST (UTC+2)
by Dennis Terhorst 16 Aug '21

16 Aug '21

Dear NEST Users & Developers! I would like to invite you to our next fortnightly Open NEST Developer Video Conference, today Monday 16 August, 11.30-12.30 CEST (UTC+2). As usual, in the Project team round, a contact person of each team will give a short statement summarizing ongoing work in the team and cross-cutting points that need discussion among the teams. The remainder of the meeting we would go into a more in-depth discussion of topics that came up on the mailing list or that are suggested by the teams. Agenda * Welcome * Review of NEST User Mailing List * Project team round The agenda for this meeting is also available online, see https://github.com/nest/nest-simulator/wiki/2021-08-16-Open-NEST-Developer-… Looking forward to seeing 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

1 0

Re: libnestutil BlockVector Implementation
by Håkon Mørk 10 Aug '21

10 Aug '21

Hi Itaru, The problem we had with std::vector was how it allocates memory. When the memory allocated for a vector is full, its capacity is increased by allocating a bigger chunk of memory (commonly with double the capacity of the original vector), and all elements are moved to the new allocation. We observed that when connections are all put in one big vector, and the number of connections in the vector becomes large, memory consumption from vector growth becomes problematic. We therefore created a new container, BlockVector, to keep memory consumption under control and avoid moving the elements when increasing the capacity. The BlockVector achieves this by allocating an entire block of a fixed size every time the capacity has to be increased. The BlockVector therefore becomes a vector of vectors, where the entire size of each new block, which is a new vector in the vector of vectors, is allocated only once when the block is created. Some benchmarks were done during the review of the PR, https://github.com/nest/nest-simulator/pull/1047 You can find the benchmarks here: https://github.com/nest/nest-simulator/files/2505835/Bench_214_sq_db70dcc1e… Note that BlockVector was called "Seque" at the time. Best, Håkon ________________________________ From: Itaru Kitayama <itaru.kitayama(a)gmail.com> Sent: 10 August 2021 05:51 To: NEST User Mailing List <users(a)nest-simulator.org> Subject: [NEST Users] libnestutil BlockVector Implementation Hello Håkon, As you implemented, an instance of BlockVector is a vector of vectors but allows users to specify with one index. As I am having a few problems with mapping BlockVetors to the device memory, I am simply wondering as to why we can't just use std::vector< value_type >? If you guys observed significant performance improvements with BlockVectors in the past, would you mind pointing me to the papers or notes? Thanks, Itaru. _______________________________________________ NEST Users mailing list -- users(a)nest-simulator.org To unsubscribe send an email to users-leave(a)nest-simulator.org

2 2

Re: Filip Blaštík - Noise generation after stimuation problem
by Hans Ekkehard Plesser 10 Aug '21

10 Aug '21

Hello Filip, I am not quite sure I understand your problem description. You write that "... after the simulation the Nodes top reacting to the noise input and become stuck on the refresh Voltage ...". But in the figure you show, the neurons have V_M ≈ -75 mV ≈ E_L for the first 30 ms, which would correspond to neurons only receiving noise input during this time and afterward seem to spike at roughly 20 ms intervals. It does seem curious that they seem to have a more or less constant membrane potential of ≈ -65 mV between the phases with spiking. So one question is what happens around 30 ms? The other question is why the "locking" to -65 mV. Could you send the full simulation script leading to the figure you included? Or even better, a minimal version of it, i.e., a complete, runnable script producing a figure with the effect you showed, but with as few layers and as few neurons per layer as possible? Best regards, Hans Ekkehard -- Prof. Dr. Hans Ekkehard Plesser Head, Department of Data Science 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<mailto:hans.ekkehard.plesser@nmbu.no> Home http://arken.nmbu.no/~plesser On 26/07/2021, 14:28, "Filip Blastik" <filipblastik(a)gmail.com<mailto:filipblastik@gmail.com>> wrote: To whom it may concern, I am writing regarding the problem with giving my topology network noise after simulation with the signal. The network is oscillating with noise generator which is created as single layer which provides noise for other nodes (which consist of layers). I stimulate my network with stronger signal(another different layer) and after the simulation the Nodes stop reacting to the noise input and become stuck on refresh Voltage and its for longer periods than refractory period. The model is derivation of Hill-Tononi example network. The Nest is running on Ubuntu 20.04 , Conda/Spyder The nest is version v2.20.1 To visualize the problem here are the images which illustrate the problem [cid:image001.png@01D78DC3.D2D6F180] [cid:image002.png@01D78DC3.D2D6F180] Here is the snippet of the code with the connections and layer setups Best regards Bc. Filip Blaštík

1 0

2025

2024

2023

2022

2021

2020

2019

NEST Users