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 Dalchenko