erelson
commented
12 years ago A few updates...
It seems that the easiest way to do a list in the config files is to have the user do a comma-delimited list.
The .h5m data files tend to be handled differently depending on the user. I keep a few copies, and I don't worry about having every cooling step/isotope combination's photon source stored. On the other hand, Elliott has been keeping a separate .h5m data file for each case/run, and using these for visualization. For now I think I will implement Elliott's approach.
My experience over the past few months has been that I (almost) always want to set up more than one photon transport problem (e.g. looking at the dose after several different cooling times). This involves the setup of multiple directories - e.g. modifying and copying r2s.cfg files, copying photon inputs, running r2s_step2.py several times. At some point, automating this would be logical.
To do this, I am thinking of an optional script akin to r2s_step1/2.py. This script would be optionally run by r2s_step1.py, or could be run separately*. Script will take (minimal) input from the r2s.cfg file.
For now I'll go with the script name r2s_step2setup.py. (Not a great name, naming is the hardest problem in computer science, right?)
Anticipated features of r2s_step2setup.py:
Anticipated modifications to the r2s.cfg file:
Anticipated modifications to r2s_step1.py:
_case: user starts off with some cooling steps of interest, and later wants to investigate specific isotopes. *_This has to be done sequentially due to accessing data in .h5m, I think.