Throughout the simulation, we need to store different kind of data.
If the data is only used to coordinate the execution, store temporary states, or keeps track of changed settings in a file, then store this information in the /tmp folder, ideally in our own sub-folder, to avoid naming conflicts /tmp/bugmark_simulation
If we require the data to exist after a simulation run ends, or inbetween runs, then we should store the information in files outside of /tmp (which might be purged at any time) and outside of the application folder. Andy uses for this kind of data the ~/trial folder and a sub-folder for different trial runs. the ~/trial folder should hold our settings and data we produce and need. Settings files should be read-only.
Throughout the simulation, we need to store different kind of data.
If the data is only used to coordinate the execution, store temporary states, or keeps track of changed settings in a file, then store this information in the
/tmp
folder, ideally in our own sub-folder, to avoid naming conflicts/tmp/bugmark_simulation
If we require the data to exist after a simulation run ends, or inbetween runs, then we should store the information in files outside of
/tmp
(which might be purged at any time) and outside of the application folder. Andy uses for this kind of data the~/trial
folder and a sub-folder for different trial runs. the~/trial
folder should hold our settings and data we produce and need. Settings files should beread-only
.