-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
consistency of MAGIC and MAGIC+LST1 scripts #44
Comments
I think at first we need to ask Alessio if the scripts under scripts/mars are still used or will be updated or not - as far as I remember the scripts have not yet been updated to be used in a ctapipe v0.12 environment. |
very likely this is still the case. I tried to use one and had to modify the imports and some class names (see PR #43 ) |
Regarding the script
does lst-chain use more or less the std DL1 format from ctapipe? I guess they still have something custom. Btw I wrote
the scripts in scripts/mars have another purpose, e.g. create the files needed to perform the image comparison starting from star/superstar files. For the scripts/magic folder, I guess that since most things are now implemented in the MAGIC-LST pipeline, we do not need them anymore. Anyway, let me have a look and then I can open a PR for the cleanup. |
About DL1/DL2 format in lst-chain, this PR cta-observatory/cta-lstchain#972 was opened just few mins ago. |
And just now I see #45 , so it is going already in the direction described above. |
Hi @aleberti,
Yes sorry, there is a typo in my comment, I meant scripts/magic, not scripts/mars. And I'm fine to change the combined analysis pipeline to use the std DL1 format if it is possible. |
The scripts for MAGIC-only analysis (starting from MARS Y MC files) in scripts/magic and the ones for LST1+MAGIC analysis in scripts/lst1_magic are very much different and produce also differieng outputs (the way how different telescopes are written, the keys in H5 files where the parameters are stored, etc.) we should aim at standarizing them - probably best to fix them to the LST-like style
The text was updated successfully, but these errors were encountered: