Skip to content
Snippets Groups Projects
Commit b1d3ab78 authored by Athanasios Karmas's avatar Athanasios Karmas
Browse files

Update README.md

parent f82f30c0
No related branches found
No related tags found
No related merge requests found
...@@ -42,11 +42,16 @@ https://docs.arbor-sim.org/en/stable/tutorial/single_cell_model.html ...@@ -42,11 +42,16 @@ https://docs.arbor-sim.org/en/stable/tutorial/single_cell_model.html
https://neuron.yale.edu/neuron/static/docs/neuronpython/firststeps.html https://neuron.yale.edu/neuron/static/docs/neuronpython/firststeps.html
https://nest-simulator.readthedocs.io/en/nest-2.20.1/auto_examples/one_neuron.html https://nest-simulator.readthedocs.io/en/nest-2.20.1/auto_examples/one_neuron.html
- After fixing any potential errors for shared libraries (info [1](https://github.com/cdr/code-server/issues/766), [2](https://gcc.gnu.org/onlinedocs/libstdc++/manual/abi.html), [3](https://serverkurma.com/linux/how-to-install-and-update-gcc-on-centos-7/)) - (Potentially) fix any potential errors for shared libraries (info [1](https://github.com/cdr/code-server/issues/766), [2](https://gcc.gnu.org/onlinedocs/libstdc++/manual/abi.html), [3](https://serverkurma.com/linux/how-to-install-and-update-gcc-on-centos-7/))
- We move on to zip the **"$SPACK_ROOT"** and the **~/.spack** folders of the build environment and transfer them to CSCS Object Storage (currently, in the future it will be a shared NFS drive)
## Delivery of the software binaries
**This methodology will change, and the delivery will be be implemented via Gitlab CI and use of the shared NFS drive**
- After build is complete, we move on to zip the **"$SPACK_ROOT"** and the **~/.spack** folders of the build environment and transfer them to CSCS Object Storage (currently, in the future it will be a shared NFS drive)
- The artifacts that were built can now be used from the Collaboratory running containers to load and run the available simulation tools - The artifacts that were built can now be used from the Collaboratory running containers to load and run the available simulation tools
## Loading software in the Collaboratory Lab containers ## Activating software in the Collaboratory Lab containers
- Currently to load the pre-built simulation tools in the Collaboratory Lab containers refer to **Quickstart** at the beggining of this file (currently the Object Storage at CSCS is used to download the pre-built software as a stop-gap measure until a shared NFS drive is available). - Currently to load the pre-built simulation tools in the Collaboratory Lab containers refer to **Quickstart** at the beggining of this file (currently the Object Storage at CSCS is used to download the pre-built software as a stop-gap measure until a shared NFS drive is available).
- This process will change in the future as all simulation tools will be available in the Collaboratory running containers from a shared NFS drive - This process will change in the future as all simulation tools will be available in the Collaboratory running containers from a shared NFS drive
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment