Ok, is this error raised during install check / nest test, or is this raised during one of your own simulations?
I think one of the possible causes of that error is that you have too many neurons on a single node. Could you start by trying a small proof of concept simulation, perhaps one of the nest examples, or something similarly simple.
Thanks for the comments, especially about not specifying the path for DCMAKE_INSTALL_PREFIX---I didn't know that. As you said, I did not need to source nest vars or specify NEST's path in venv's site-packages, cool!
Robin: "could you compare the versions of cython in the build log with that given by pip show cython?"
Yes, I did. I had a problem before and that's why I had to specify the full path for cython. But that is now resolved and cmake picks up the current version of python without specifying the full path. Currently, Cmake --version = 3.30.4, Cython is 3.0.11, and Python is 3.9.7.
Robin: "Try again WITHOUT specifying any paths yourself: If your venv is active, they should be the first ones to be detected"
Just tried this (with no DCMAKE_INSTALL_PREFIX). The HPC-based simulation crashes with the same issue.
```
[<node-id>.nemo.privat:03381] Set MCA parameter "orte_base_help_aggregate" to 0 to see all help / error messages
python: <path-to-extracted-tarball>/nest-simulator-3.8/nestkernel/connector_base.h:405: size_t nest::Connector<ConnectionT>::send(size_t, size_t, const std::vector<nest::ConnectorModel*>&, nest::Event&) [with ConnectionT = nest::tsodyks2_synapse<nest::TargetIdentifierPtrRport>; size_t = long unsigned int]: Assertion `lcid + lcid_offset < C_.size()' failed.
```
I don't fully get why NEST here refers to code in <path-to-extracted-tarball>. This is not new, it also shows up in the previous crash dump. But this suggests that there's perhaps some build issue with cmake, right?
_______________________________________________
NEST Users mailing list -- users@nest-simulator.org
To unsubscribe send an email to users-leave@nest-simulator.org