NEST Users February 2022

users@nest-simulator.org

15 participants
14 discussions

WOIV'22: Extended Deadline -- 6th International Workshop on In Situ Visualization

by Tom Vierjahn

Hi all, we have extended the submission deadline for WOIV’22 until March 7. And we have added a 3rd submission type: lightning presentations (2 to 4 pages, published via Zenodo). Please find the updated CfP below and on the webpage https://woiv.gitlab.io Cheers, Tom ----- # WOIV'22: 6th International Workshop on In Situ Visualization * Held in conjunction with ISC 2022 * Hamburg, Germany, June 2, 2022 ## Scope Large-scale HPC simulations with their inherent I/O bottleneck have made in situ visualization an essential approach for data analysis, although the idea of in situ visualization dates back to the golden era of coprocessing in the 1990s. In situ coupling of analysis and visualization to a live simulation circumvents writing raw data to disk for post-mortem analysis – an approach that is already inefficient for today’s very large simulation codes. Instead, with in situ visualization, data abstracts are generated that provide a much higher level of expressiveness per byte. Therefore, more details can be computed and stored for later analysis, providing more insight than traditional methods. We encourage contributed talks on methods and workflows that have been used for large-scale parallel visualization, with a particular focus on the in situ case. Presentations on codes that closely couple numerical methods and visualization are particularly welcome. Speakers should detail if and how the application drove abstractions or other kinds of data reductions and how these interacted with the expressiveness and flexibility of the visualization for exploratory analysis. Presentations on codes that closely couple numerical methods and visualization are particularly welcome. Speakers should detail frameworks used and data reductions applied. They should also indicate how these impacted the flexibility of the visualization for exploratory analysis. Of particular interest to WOIV and its attendees are recent developments for in situ libraries and software. Submissions documenting recent additions to existing in situ software or new in situ platforms are highly encouraged. WOIV is an excellent place to connect providers of in situ solutions with potential customers. For the submissions we are not only looking for success stories, but are also particularly interested in those experiments that started with a certain goal or idea in mind, but later got shattered by reality or insufficient hardware/software. Areas of interest for WOIV include, but are not limited to: * Techniques and paradigms for in situ visualization. * Algorithms relevant to in situ visualization. These could include algorithms empowered by in situ visualization or algorithms that overcome limitations of in situ visualization. * Systems and software implementing in situ visualization. These include both general purpose and bespoke implementations. This also includes updates to existing software as well as new software. * Workflow management. * Use of in situ visualization for application science or other examples of using in situ visualization. * Performance studies of in situ systems. Comparisons between in situ systems or techniques or comparisons between in situ and alternatives (such as post hoc) are particularly encouraged. * The impact of hardware changes on in situ visualization. * The online visualization of experimental data. * Reports of in situ visualization failures. * Emerging issues with in situ visualization. ## Submissions We accept submissions of short papers (6 to 8 pages), full papers (10 to 12 pages) and lightning presentations (2 to 4 pages) in Springer single column LNCS style. Please find LaTeX and Word templates at https://woiv.gitlab.io/woiv22/template. `Submissions are exclusively handled via EasyChair: https://woiv.gitlab.io/woiv22/submit. The review process is single or double blind, we leave it to the discretion of the authors whether they want to disclose their identity in their submissions. All submissions will be peer-reviewed by experts in the field, and will be evaluated according to relevance to the workshop theme, technical soundness, thoroughness of success/failure comparison, and impactfulness of method/results. Accepted short and full papers will appear as post-conference workshop proceedings in the Springer Lecture Notes in Computer Science (LNCS) series; lightning presentations will be published via Zenodo. The submitted versions will be made available to workshop participants during ISC. ## Important Dates * Submission deadline (extended): March 7, 2022, anywhere on earth * Notification of acceptance: April 15, 2022 * Final presentation slides due: May 10, 2012, anywhere on earth (subject to change) * Workshop: June 2, 2022 * Camera-ready version due: July 1, 2022 (subject to change, extrapolated from previous years) ## Chairs * Peter Messmer, NVIDIA * Tom Vierjahn, Westphalian University of Applied Sciences, Bocholt, Germany ## Steering Committee * Steffen Frey, University of Groningen, The Netherlands * Kenneth Moreland, Oak Ridge National Laboratory, USA * Thomas Theussl, KAUST, Saudi Arabia * Guido Reina, University of Stuttgart, Germany * Tom Vierjahn, Westphalian University of Applied Sciences, Bocholt, Germany ## Website, Venue, Registration * Website: https://woiv.gitlab.io * Submission system: https://woiv.gitlab.io/woiv22/submit * Template: https://woiv.gitlab.io/woiv22/template * Venue: https://www.isc-hpc.com (ISC 2022) * Workshop registration: https://woiv.gitlab.io/woiv22/register ## Contact E-Mail: woiv(a)googlegroups.com

2 years, 10 months

Open NEST Developer Video Conference Monday February 14 2022 11:30 CET (UTC+1)

by Dennis Terhorst

Dear NEST Users & Developers! I would like to invite you to our next fortnightly Open NEST Developer Video Conference, today Monday February 14, 11.30-12.30 CET (UTC+1). Feel free to join the meeting also just to bring your own questions for direct discussion in the in-depth section. 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 The agenda for this meeting is also available online, see https://github.com/nest/nest-simulator/wiki/2022-02-14-Open-NEST-Developer-… Looking forward to seeing you soon! Cheers, 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

2 years, 10 months

Webinar Invitation: ""Embodied Large Scale Spiking Neural Networks in the Neurorobotics Platform"

by Benedikt Feldotto

Dear all, NEST is a powerful tool to simulate biologically derived spiking Neural Networks. Besides the ever improving model details, learning paradigms and computational complexity, there are two complementary components necessary in order to simulate a (full) biologically plausible mammalian brain: Running simulations at large scale and embodying the brain simulation in a (virtual) body. In frame of the Fenix Infrastructure Webinar series I am going to present "Embodied large scale spiking neural networks in the Neurorobotics Platform" with a focus on the deployment on High Performance Computing Infrastructure next week Thursday. The presentation showcases the joint work of developers from NEST and the Neurorobotics Platform, the CSCS Swiss National Supercomputing centre and researchers in the RoboBrain project. Check out the details and registration at: https://fenix-ri.eu/events/14th-fenix-infrastructure-webinar-ebrains-servic… Looking forward to see you there, Benedikt -- Benedikt Feldotto M.Sc. Research Assistant Human Brain Project - Neurorobotics Technical University of Munich Department of Informatics Chair of Robotics, Artificial Intelligence and Real-Time Systems Room HB 2.02.20 Parkring 13 D-85748 Garching b. München Tel.: +49 89 289 17628 Mail: feldotto(a)in.tum.de https://www6.in.tum.de/en/people/benedikt-feldotto-msc/ www.neurorobotics.net

2 years, 10 months

Synapse labels and connection rules

by Barna Zajzon

Dear NEST community, When trying to pass a `synapse_label` parameter in the syn_spec dictionary, in conjunction with the `one_to_one` rule and node ids passed as arrays, I get the following error with NEST 3.0: File "/home/zbarni/code/projects/lif_sorn_seqlearn/lif-sorn-nest-implementation/remote/test_nestml_multith.py", line 29, in <module> nest.Connect([1], [2], conn_spec={'rule': 'one_to_one'}, syn_spec={'synapse_model': 'static_synapse_lbl', 'synapse_label': 1}) File "/home/zbarni/software/installed/miniconda3/envs/del-lif-sorn-nestml-check_py390/lib/python3.9/site-packages/nest/ll_api.py", line 228, in stack_checker_func return f(*args, **kwargs) File "/home/zbarni/software/installed/miniconda3/envs/del-lif-sorn-nestml-check_py390/lib/python3.9/site-packages/nest/lib/hl_api_connections.py", line 255, in Connect connect_arrays(pre, post, weights, delays, synapse_model, syn_param_keys, syn_param_values) File "pynestkernel.pyx", line 360, in pynestkernel.NESTEngine.connect_arrays nest.lib.hl_api_exceptions.TypeMismatch: TypeMismatch in SLI function connect_arrays It works when using the `all_to_all` rule. Is this the expected behavior or for some reason it's not possible to use synapse_label and the one_to_one rule (yet)? Thank you, Barna

2 years, 10 months

2024

2023

2022

2021

2020

2019

NEST Users February 2022