sim_runner merge requestshttps://gitlab.cern.ch/cta-unige/sim_runner/-/merge_requests2021-12-14T13:54:34+01:00https://gitlab.cern.ch/cta-unige/sim_runner/-/merge_requests/33Feature/37 extend corsika support2021-12-14T13:54:34+01:00Georgios Gerasimos VoutsinasFeature/37 extend corsika supportCloses #37Closes #37Georgios Gerasimos VoutsinasGeorgios Gerasimos Voutsinashttps://gitlab.cern.ch/cta-unige/sim_runner/-/merge_requests/31adding process parameter_card2021-12-06T15:38:03+01:00Georgios Gerasimos Voutsinasadding process parameter_cardhttps://gitlab.cern.ch/cta-unige/sim_runner/-/merge_requests/30Draft: Resolve "Implement 2 dimensional parameter scanning"2021-10-14T12:00:13+02:00Georgios Gerasimos VoutsinasDraft: Resolve "Implement 2 dimensional parameter scanning"Closes #35Closes #35Georgios Gerasimos VoutsinasGeorgios Gerasimos Voutsinashttps://gitlab.cern.ch/cta-unige/sim_runner/-/merge_requests/29adding .git at the end of the url of the configuration repo so it can run to ...2021-10-06T10:53:16+02:00Georgios Gerasimos Voutsinasadding .git at the end of the url of the configuration repo so it can run to all linux machinesadding .git at the end of the url of the configuration repo so it can run to all linux machinesadding .git at the end of the url of the configuration repo so it can run to all linux machineshttps://gitlab.cern.ch/cta-unige/sim_runner/-/merge_requests/28Feature/lst processing2021-04-01T11:50:50+02:00Mykhailo DalchenkoFeature/lst processing## Description
<!--- Describe your changes in detail -->
Implement the DL1 processing with the lstchain.
Requires lstchain 0.7 extended with certain bugfixes, exact version to be provided soon (possibly 0.7.1)
## Related Issue
<!--- T...## Description
<!--- Describe your changes in detail -->
Implement the DL1 processing with the lstchain.
Requires lstchain 0.7 extended with certain bugfixes, exact version to be provided soon (possibly 0.7.1)
## Related Issue
<!--- This project only accepts pull requests related to open issues -->
<!--- If suggesting a new feature or change, please discuss it in an issue first -->
<!--- If fixing a bug, there should be an issue describing it with steps to reproduce -->
<!--- If addressing multiple issues, comment on their relation if needed -->
<!--- Please link issues accordgin to the automation rules: -->
<!--- https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically -->
First step of #30
## How Has This Been Tested?
<!--- Please describe in detail how you tested your changes. -->
<!--- Include details of your testing environment, and the tests you ran to -->
<!--- see how your change affects other areas of the code, etc. -->
Manually tested on LaPalma.
Automated tests fail due to installation issues in docker. To be resolved later (by providing a new Docker image).
This will be implemented in a separate MR prior to releasing of next version of sim_runner.
## Types of changes
<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
- [x] Breaking change (fix or feature that would cause existing functionality to change)
## Checklist:
<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
- [x] My code follows the code style of this project.
- [x] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [x] I have read the **CONTRIBUTING** document.
- [ ] I have added tests to cover my changes.
- [ ] All new and existing tests passed.RC-0.3Mykhailo DalchenkoMykhailo Dalchenkohttps://gitlab.cern.ch/cta-unige/sim_runner/-/merge_requests/40python script that parses Corsika directories and creates configs on the fly ...2022-04-08T16:18:45+02:00Georgios Gerasimos Voutsinaspython script that parses Corsika directories and creates configs on the fly + config templateIt addresses issue #48
In the current (and possibly future) MC production the only modifications we have to do in the config files is the input/output paths and the telescope pointings. The proposed script parses the corsika directorie...It addresses issue #48
In the current (and possibly future) MC production the only modifications we have to do in the config files is the input/output paths and the telescope pointings. The proposed script parses the corsika directories, grep the directory names and creates simtel directories. It then edits a proposed config template, adding the relevant input and output paths. Currently, the direction of shower generation in Corsika is stated in the directory name. The script reads the pointing from the name, and modifies the pointing inside the config file for the simtel simulation. Finally the config is copied in the relevant directory that will host the simtel files.Georgios Gerasimos VoutsinasGeorgios Gerasimos Voutsinashttps://gitlab.cern.ch/cta-unige/sim_runner/-/merge_requests/39Fix bug with wrapper script getting only the latest job inputs update2022-03-22T13:53:21+01:00Mykhailo DalchenkoFix bug with wrapper script getting only the latest job inputs update## Description
<!--- Describe your changes in detail -->
Fix wrapper scripts creation for multiple jobs
## Related Issue
<!--- This project only accepts pull requests related to open issues -->
<!--- If suggesting a new feature or change...## Description
<!--- Describe your changes in detail -->
Fix wrapper scripts creation for multiple jobs
## Related Issue
<!--- This project only accepts pull requests related to open issues -->
<!--- If suggesting a new feature or change, please discuss it in an issue first -->
<!--- If fixing a bug, there should be an issue describing it with steps to reproduce -->
<!--- If addressing multiple issues, comment on their relation if needed -->
<!--- Please link issues accordgin to the automation rules: -->
<!--- https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically -->
#46
## How Has This Been Tested?
<!--- Please describe in detail how you tested your changes. -->
<!--- Include details of your testing environment, and the tests you ran to -->
<!--- see how your change affects other areas of the code, etc. -->
<!--- ## Screenshots (if appropriate): -->
Tested manually on HTCondor-driven cluster at CERN
## Types of changes
<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
- [x] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
## Checklist:
<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
- [x] My code follows the code style of this project.
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [x] I have read the **CONTRIBUTING** document.
- [ ] I have added tests to cover my changes.
- [x] All new and existing tests passed.Release 0.2Mykhailo DalchenkoMykhailo Dalchenkohttps://gitlab.cern.ch/cta-unige/sim_runner/-/merge_requests/38Fix the htcondor submission for sim_telarray2022-03-18T19:06:25+01:00Mykhailo DalchenkoFix the htcondor submission for sim_telarrayworkaround to push without breaking hidden referencesworkaround to push without breaking hidden referenceshttps://gitlab.cern.ch/cta-unige/sim_runner/-/merge_requests/37Feature/htcondor support2022-03-21T10:04:25+01:00Mykhailo DalchenkoFeature/htcondor support## Description
<!--- Describe your changes in detail -->
Added support of HTCondor submission system, for sim_telarray stage only at the moment
The functionality still needs to be tested on a real production system.
Also implement local...## Description
<!--- Describe your changes in detail -->
Added support of HTCondor submission system, for sim_telarray stage only at the moment
The functionality still needs to be tested on a real production system.
Also implement local (non-versioned) configuration usage
## Related Issue
<!--- This project only accepts pull requests related to open issues -->
<!--- If suggesting a new feature or change, please discuss it in an issue first -->
<!--- If fixing a bug, there should be an issue describing it with steps to reproduce -->
<!--- If addressing multiple issues, comment on their relation if needed -->
<!--- Please link issues accordgin to the automation rules: -->
<!--- https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically -->
Closes #41
## How Has This Been Tested?
<!--- Please describe in detail how you tested your changes. -->
<!--- Include details of your testing environment, and the tests you ran to -->
<!--- see how your change affects other areas of the code, etc. -->
Tested with partial autotest coverage.
<!--- ## Screenshots (if appropriate): -->
## Types of changes
<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
## Checklist:
<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
- [x] My code follows the code style of this project.
- [x] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [x] I have read the **CONTRIBUTING** document.
- [x] I have added tests to cover my changes.
- [x] All new and existing tests passed.Mykhailo DalchenkoMykhailo Dalchenkohttps://gitlab.cern.ch/cta-unige/sim_runner/-/merge_requests/36temporary storage2022-12-08T15:20:10+01:00Georgios Gerasimos Voutsinastemporary storageThe main goal of this merge request is to address issue #42
So while running corsika parameter_card process, corsika will temporarily store the files and logs at the scratch space in computing nodes and automatically move them to fefs o...The main goal of this merge request is to address issue #42
So while running corsika parameter_card process, corsika will temporarily store the files and logs at the scratch space in computing nodes and automatically move them to fefs once the job is finished. An automatic cleanup of the scratch space occurs.
The merge request also addresses some smaller issues that were encountered during xmas period, when the production was started. The issues were corrected on spot, but were not propagated to the repository. The main is the creation of a jobs directory for corsika jobs.
Closes #42Georgios Gerasimos VoutsinasGeorgios Gerasimos Voutsinashttps://gitlab.cern.ch/cta-unige/sim_runner/-/merge_requests/35restructuring the way data are stored in corsika parameter_card2022-02-21T16:00:21+01:00Georgios Gerasimos Voutsinasrestructuring the way data are stored in corsika parameter_cardRestructuring the way data are stored when running corsika parameter_card.
It follows Misha's example directory tree.
However: it doesn't create the run directory which stores the .job files. The reason is that those
files are created i...Restructuring the way data are stored when running corsika parameter_card.
It follows Misha's example directory tree.
However: it doesn't create the run directory which stores the .job files. The reason is that those
files are created in another function, and storing them inside their node directory, will add some more complexity.
Do we really want them?
Closed #40Georgios Gerasimos VoutsinasGeorgios Gerasimos Voutsinashttps://gitlab.cern.ch/cta-unige/sim_runner/-/merge_requests/34Feature/38 for mc production2021-12-13T16:01:38+01:00Georgios Gerasimos VoutsinasFeature/38 for mc productionCloses #37
Closes #38Closes #37
Closes #38Georgios Gerasimos VoutsinasGeorgios Gerasimos Voutsinashttps://gitlab.cern.ch/cta-unige/sim_runner/-/merge_requests/32Update pyproject.toml2021-10-27T14:11:36+02:00Mykhailo DalchenkoUpdate pyproject.toml## Description
<!--- Describe your changes in detail -->
Fix the `pillow` version to avoid issues during installation in the CI container.
## Related Issue
<!--- This project only accepts pull requests related to open issues -->
<!--- I...## Description
<!--- Describe your changes in detail -->
Fix the `pillow` version to avoid issues during installation in the CI container.
## Related Issue
<!--- This project only accepts pull requests related to open issues -->
<!--- If suggesting a new feature or change, please discuss it in an issue first -->
<!--- If fixing a bug, there should be an issue describing it with steps to reproduce -->
<!--- If addressing multiple issues, comment on their relation if needed -->
<!--- Please link issues accordgin to the automation rules: -->
<!--- https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically -->
#36
## How Has This Been Tested?
<!--- Please describe in detail how you tested your changes. -->
<!--- Include details of your testing environment, and the tests you ran to -->
<!--- see how your change affects other areas of the code, etc. -->
CI passes
<!--- ## Screenshots (if appropriate): -->
## Types of changes
<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
- [x] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
## Checklist:
<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
- [x] My code follows the code style of this project.
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [x] I have read the **CONTRIBUTING** document.
- [ ] I have added tests to cover my changes.
- [x] All new and existing tests passed.Mykhailo DalchenkoMykhailo Dalchenkohttps://gitlab.cern.ch/cta-unige/sim_runner/-/merge_requests/27Add a possibility to run DL1 conversion2021-04-01T12:55:50+02:00Mykhailo DalchenkoAdd a possibility to run DL1 conversion## Description
<!--- Describe your changes in detail -->
So far added DL1 conversion in local submission mode
## Related Issue
<!--- This project only accepts pull requests related to open issues -->
<!--- If suggesting a new feature or ...## Description
<!--- Describe your changes in detail -->
So far added DL1 conversion in local submission mode
## Related Issue
<!--- This project only accepts pull requests related to open issues -->
<!--- If suggesting a new feature or change, please discuss it in an issue first -->
<!--- If fixing a bug, there should be an issue describing it with steps to reproduce -->
<!--- If addressing multiple issues, comment on their relation if needed -->
<!--- Please link issues accordgin to the automation rules: -->
<!--- https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically -->
Relates to #30, fixes #33
## How Has This Been Tested?
<!--- Please describe in detail how you tested your changes. -->
<!--- Include details of your testing environment, and the tests you ran to -->
<!--- see how your change affects other areas of the code, etc. -->
For the moment only tested dry running locally
<!--- ## Screenshots (if appropriate): -->
## Types of changes
<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
## Checklist:
<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
- [x] My code follows the code style of this project.
- [x] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [x] I have read the **CONTRIBUTING** document.
- [ ] I have added tests to cover my changes.
- [ ] All new and existing tests passed.Mykhailo DalchenkoMykhailo Dalchenkohttps://gitlab.cern.ch/cta-unige/sim_runner/-/merge_requests/26add light_emission production type2021-10-06T16:51:06+02:00Andrii Nagaiadd light_emission production type## Description
<!--- Describe your changes in detail -->
Provide required fixes to integrate light emission package
## Related Issue
<!--- This project only accepts pull requests related to open issues -->
<!--- If suggesting a new feat...## Description
<!--- Describe your changes in detail -->
Provide required fixes to integrate light emission package
## Related Issue
<!--- This project only accepts pull requests related to open issues -->
<!--- If suggesting a new feature or change, please discuss it in an issue first -->
<!--- If fixing a bug, there should be an issue describing it with steps to reproduce -->
<!--- If addressing multiple issues, comment on their relation if needed -->
<!--- Please link issues accordgin to the automation rules: -->
<!--- https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically -->
Closes #28
## How Has This Been Tested?
<!--- Please describe in detail how you tested your changes. -->
<!--- Include details of your testing environment, and the tests you ran to -->
<!--- see how your change affects other areas of the code, etc. -->
Personal run on yggdrasil
<!--- ## Screenshots (if appropriate): -->
## Types of changes
<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
## Checklist:
<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
- [x] My code follows the code style of this project.
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [ ] I have read the **CONTRIBUTING** document.
- [ ] I have added tests to cover my changes.
- [ ] All new and existing tests passed.https://gitlab.cern.ch/cta-unige/sim_runner/-/merge_requests/25Adding user name and timestamp to log name2020-10-22T14:19:12+02:00Mykhailo DalchenkoAdding user name and timestamp to log name## Description
<!--- Describe your changes in detail -->
Add username and timestamp to log file, which is now:
`/tmp/sim_runner_<username>_<timestamp>.log`
## Related Issue
<!--- This project only accepts pull requests related to open i...## Description
<!--- Describe your changes in detail -->
Add username and timestamp to log file, which is now:
`/tmp/sim_runner_<username>_<timestamp>.log`
## Related Issue
<!--- This project only accepts pull requests related to open issues -->
<!--- If suggesting a new feature or change, please discuss it in an issue first -->
<!--- If fixing a bug, there should be an issue describing it with steps to reproduce -->
<!--- If addressing multiple issues, comment on their relation if needed -->
<!--- Please link issues accordgin to the automation rules: -->
<!--- https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically -->
## How Has This Been Tested?
<!--- Please describe in detail how you tested your changes. -->
<!--- Include details of your testing environment, and the tests you ran to -->
<!--- see how your change affects other areas of the code, etc. -->
Manually
<!--- ## Screenshots (if appropriate): -->
## Types of changes
<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
## Checklist:
<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
- [x] My code follows the code style of this project.
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [x] I have read the **CONTRIBUTING** document.
- [ ] I have added tests to cover my changes.
- [x] All new and existing tests passed.Mykhailo DalchenkoMykhailo Dalchenkohttps://gitlab.cern.ch/cta-unige/sim_runner/-/merge_requests/24Fix output file names in test script2020-10-21T16:39:09+02:00Mykhailo DalchenkoFix output file names in test script## Description
<!--- Describe your changes in detail -->
Fix test job templates in testing script
## Related Issue
<!--- This project only accepts pull requests related to open issues -->
<!--- If suggesting a new feature or change, plea...## Description
<!--- Describe your changes in detail -->
Fix test job templates in testing script
## Related Issue
<!--- This project only accepts pull requests related to open issues -->
<!--- If suggesting a new feature or change, please discuss it in an issue first -->
<!--- If fixing a bug, there should be an issue describing it with steps to reproduce -->
<!--- If addressing multiple issues, comment on their relation if needed -->
<!--- Please link issues accordgin to the automation rules: -->
<!--- https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically -->
Fixes #27
## How Has This Been Tested?
<!--- Please describe in detail how you tested your changes. -->
<!--- Include details of your testing environment, and the tests you ran to -->
<!--- see how your change affects other areas of the code, etc. -->
CI
<!--- ## Screenshots (if appropriate): -->
## Types of changes
<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
- [x] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
## Checklist:
<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
- [x] My code follows the code style of this project.
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [x] I have read the **CONTRIBUTING** document.
- [ ] I have added tests to cover my changes.
- [x] All new and existing tests passed.Mykhailo DalchenkoMykhailo Dalchenkohttps://gitlab.cern.ch/cta-unige/sim_runner/-/merge_requests/23Fix output file name determination from input file name2020-10-21T15:54:17+02:00Mykhailo DalchenkoFix output file name determination from input file name## Description
<!--- Describe your changes in detail -->
Bug fix for miscalculation output file names based on input file names
## Related Issue
<!--- This project only accepts pull requests related to open issues -->
<!--- If suggesting...## Description
<!--- Describe your changes in detail -->
Bug fix for miscalculation output file names based on input file names
## Related Issue
<!--- This project only accepts pull requests related to open issues -->
<!--- If suggesting a new feature or change, please discuss it in an issue first -->
<!--- If fixing a bug, there should be an issue describing it with steps to reproduce -->
<!--- If addressing multiple issues, comment on their relation if needed -->
<!--- Please link issues accordgin to the automation rules: -->
<!--- https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically -->
Fixes #26
## How Has This Been Tested?
<!--- Please describe in detail how you tested your changes. -->
<!--- Include details of your testing environment, and the tests you ran to -->
<!--- see how your change affects other areas of the code, etc. -->
<!--- ## Screenshots (if appropriate): -->
Trivial bugfix, CI to follow
## Types of changes
<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
- [x] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
## Checklist:
<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
- [x] My code follows the code style of this project.
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [x] I have read the **CONTRIBUTING** document.
- [ ] I have added tests to cover my changes.
- [x] All new and existing tests passed.Luis David Medina MirandaLuis David Medina Mirandahttps://gitlab.cern.ch/cta-unige/sim_runner/-/merge_requests/22Implement a possibility to provide a job template file as an optional parameter2020-10-08T11:13:36+02:00Mykhailo DalchenkoImplement a possibility to provide a job template file as an optional parameter## Description
<!--- Describe your changes in detail -->
Job template file can be passed as an optional parameter of the toml config
## Related Issue
<!--- This project only accepts pull requests related to open issues -->
<!--- If sugge...## Description
<!--- Describe your changes in detail -->
Job template file can be passed as an optional parameter of the toml config
## Related Issue
<!--- This project only accepts pull requests related to open issues -->
<!--- If suggesting a new feature or change, please discuss it in an issue first -->
<!--- If fixing a bug, there should be an issue describing it with steps to reproduce -->
<!--- If addressing multiple issues, comment on their relation if needed -->
<!--- Please link issues accordgin to the automation rules: -->
<!--- https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically -->
Closes #25
## How Has This Been Tested?
<!--- Please describe in detail how you tested your changes. -->
<!--- Include details of your testing environment, and the tests you ran to -->
<!--- see how your change affects other areas of the code, etc. -->
<!--- ## Screenshots (if appropriate): -->
## Types of changes
<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
## Checklist:
<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
- [x] My code follows the code style of this project.
- [x] My change requires a change to the documentation.
- [x] I have updated the documentation accordingly.
- [x] I have read the **CONTRIBUTING** document.
- [x] I have added tests to cover my changes.
- [x] All new and existing tests passed.Mykhailo DalchenkoMykhailo Dalchenkohttps://gitlab.cern.ch/cta-unige/sim_runner/-/merge_requests/21Feature/corsika support2020-10-08T10:22:18+02:00Mykhailo DalchenkoFeature/corsika support## Description
<!--- Describe your changes in detail -->
Implement CORSIKA support.
Main configuration is offloaded to the corsika-config repository, current test config is good for corsika-6X only
Note: the configuration layout has be...## Description
<!--- Describe your changes in detail -->
Implement CORSIKA support.
Main configuration is offloaded to the corsika-config repository, current test config is good for corsika-6X only
Note: the configuration layout has been changed and sim_telarray running requires updated configurations - see examples
## Related Issue
<!--- This project only accepts pull requests related to open issues -->
<!--- If suggesting a new feature or change, please discuss it in an issue first -->
<!--- If fixing a bug, there should be an issue describing it with steps to reproduce -->
<!--- If addressing multiple issues, comment on their relation if needed -->
<!--- Please link issues accordgin to the automation rules: -->
<!--- https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically -->
#24
## How Has This Been Tested?
<!--- Please describe in detail how you tested your changes. -->
<!--- Include details of your testing environment, and the tests you ran to -->
<!--- see how your change affects other areas of the code, etc. -->
Tested in CI (dry running)
<!--- ## Screenshots (if appropriate): -->
## Types of changes
<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
- [x] Breaking change (fix or feature that would cause existing functionality to change)
## Checklist:
<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
- [x] My code follows the code style of this project.
- [x] My change requires a change to the documentation.
- [x] I have updated the documentation accordingly.
- [x] I have read the **CONTRIBUTING** document.
- [x] I have added tests to cover my changes.
- [x] All new and existing tests passed.rc-0.2