MesoNet: Brian2CUDA bring-up

CUDA setup first, tiny example first. not dragging the entire network into compiler-error land yet

failure: the Brian2CUDA example did not compile in the current environment. The October 15 entry frames CUDA/environment setup as the next debugging target; it does not show a successful accelerated run.

diagnostic record to recover: exact compiler error, Python package versions, NVIDIA driver/toolkit versions, chosen backend and minimal example command. A present GPU is not evidence that a Brian2 simulation is running on it.

proposed test sequence: compile an unchanged example; compare its output with the existing backend; then move the project model over with the same timestep, seeds and recorded inputs. Add custom operations only after the baseline works.

open question: do the later custom event pathways and Python-side NetworkOperation behavior remain compatible with the intended accelerated mode? That must be tested independently of installing the package.

References saved in this journal section

• https://brian2cuda.readthedocs.io/en/latest/introduction/install.html
• https://brian2cuda.readthedocs.io/en/latest/introduction/install.html#testing-your-installation
• https://brian.discourse.group/t/brian2cuda-testing/923
• https://github.com/blizzard-labs/NMCtests
• https://www.digitalocean.com/community/tutorials/nohup-command-in-linux

Brian2CUDA build failure

CPU process monitor