sim_runner issueshttps://gitlab.cern.ch/cta-unige/sim_runner/-/issues2022-04-08T16:18:46+02:00https://gitlab.cern.ch/cta-unige/sim_runner/-/issues/48create configs on the fly2022-04-08T16:18:46+02:00Georgios Gerasimos Voutsinascreate configs on the flyFor the current (or future) MC productions we have hundreds of directories with Corsika files. Creating sim_telarray
configs for all these directories is painful. This issue addresses this problem. This issue could be addressed by a scr...For the current (or future) MC productions we have hundreds of directories with Corsika files. Creating sim_telarray
configs for all these directories is painful. This issue addresses this problem. This issue could be addressed by a script that will parse through the Corsika directories trees, will create corresponding simtel directories and will place the relevant config file inside each simtel directory.Georgios Gerasimos VoutsinasGeorgios Gerasimos Voutsinashttps://gitlab.cern.ch/cta-unige/sim_runner/-/issues/47clean up jobs2022-04-07T19:27:35+02:00Georgios Gerasimos Voutsinasclean up jobs### Summary
<!--- Summarize the new feature you would like to add concisely -->
<!--- and describe the actual behavior -->
When running the corsika production with the temporary storage option enabled. i.e. writing the output temporary a...### Summary
<!--- Summarize the new feature you would like to add concisely -->
<!--- and describe the actual behavior -->
When running the corsika production with the temporary storage option enabled. i.e. writing the output temporary at the servers, in case the job is cancelled the temporary directories are not cleaned up. That's expected, since sim_runner can't know the fate of the job. Cancellation of the job can happen either by the user or by the system, if the running time of the job surpasses the limit. In case of failed or successful jobs, the cleanup works fine.
### What is the expected correct behavior?
<!--- What you should see instead -->
Sim_runner should be able to produce jobs that run in all servers, look for directories based on a user-defined pattern, and delete those directories.
### Relevant logs and/or screenshots
<!--- Paste any relevant logs - please use code blocks (```) to format -->
<!--- console output, logs, and code as it's very hard to read otherwise -->
<!--- ### Possible fixes -->
<!--- If you can, provide a code snippet which may implement the requested feature -->Georgios Gerasimos VoutsinasGeorgios Gerasimos Voutsinashttps://gitlab.cern.ch/cta-unige/sim_runner/-/issues/45Prepare PyPI release2022-03-17T11:57:40+01:00Mykhailo DalchenkoPrepare PyPI release### Summary
<!--- Summarize the new feature you would like to add concisely -->
<!--- and describe the actual behavior -->
Since 0.2, sim_runner must be released on PyPi
Required configuration modifications and CI jobs must be prepared.### Summary
<!--- Summarize the new feature you would like to add concisely -->
<!--- and describe the actual behavior -->
Since 0.2, sim_runner must be released on PyPi
Required configuration modifications and CI jobs must be prepared.Release 0.2Mykhailo DalchenkoMykhailo Dalchenkohttps://gitlab.cern.ch/cta-unige/sim_runner/-/issues/44Documentation update2022-03-18T10:48:08+01:00Mykhailo DalchenkoDocumentation update### Summary
<!--- Summarize what you would like to discuss -->
<!--- and what is the actual behavior -->
In view of numerous functionality upgrades, the documentation should receive a proper update too.
### What is the expected correct...### Summary
<!--- Summarize what you would like to discuss -->
<!--- and what is the actual behavior -->
In view of numerous functionality upgrades, the documentation should receive a proper update too.
### What is the expected correct behavior?
<!--- What you should see instead -->
Correct, clear and up to date documentation
### Relevant logs and/or screenshots
<!--- Paste any relevant logs - please use code blocks (```) to format -->
<!--- console output, logs, and code as it's very hard to read otherwise -->Release 0.2Georgios Gerasimos VoutsinasGeorgios Gerasimos Voutsinashttps://gitlab.cern.ch/cta-unige/sim_runner/-/issues/43Scan parameters with float as a step2022-03-17T11:53:52+01:00Georgios Gerasimos VoutsinasScan parameters with float as a step### Summary
<!--- Summarize the new feature you would like to add concisely -->
<!--- and describe the actual behavior -->
Currently the scan_parameter process can scan a parameter from an inital to a final value using an integer step.
T...### Summary
<!--- Summarize the new feature you would like to add concisely -->
<!--- and describe the actual behavior -->
Currently the scan_parameter process can scan a parameter from an inital to a final value using an integer step.
The function used is range. This doesn't allow us to scan values using a floating step, as it is required e.g. in telescope transmission scanning
<!--- ### Possible fixes -->
<!--- If you can, provide a code snippet which may implement the requested feature -->
I would propose to replace range with numpy.linspace: for example something like
scan_parameters = np.linspace(config['process']['parameter_scan']['initial'],
config['process']['parameter_scan']['final'],
config['process']['parameter_scan']['number_of_points'],endpoint=False)
instead of
scan_parameters = range(config['process']['parameter_scan']['initial'],
config['process']['parameter_scan']['final'] + 1, # include final value
config['process']['parameter_scan']['scan']Release 0.2Georgios Gerasimos VoutsinasGeorgios Gerasimos Voutsinas