Skip to content
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

Compatibility for current MC version (12.10.2020) #69

Open
l-althueser opened this issue Oct 12, 2020 · 2 comments
Open

Compatibility for current MC version (12.10.2020) #69

l-althueser opened this issue Oct 12, 2020 · 2 comments

Comments

@l-althueser
Copy link
Member

PR 230 in the MC repo will break compatibility with the processing scripts. Current workaround is to delete all related options from both python files.
We have to decide how to move forward - we probably need a logic so that 1T simulations are not affected (if we would just drop the options in all files ..). @ramirezdiego what do you think?

@ramirezdiego
Copy link
Contributor

I agree with deleting all the electric field options, stating in the README file that one would need a previous version of the processing scripts for the XENON1T full chain (field values are also fetched by the patch scripts from the G4 output file, right? But these haven't been used in a while...).
In addition to that, I was thinking about just moving the processing/montecarlo folder to its own repo in the XENONnT page and do a massive cleanup, maybe constraining it to nT simulations chain. It's probably a lot of copy-pasting, but I was thinking it could help other users understand and maintain these files. You're the expert on this, so feel free to tell me if that's not a good idea.

@l-althueser
Copy link
Member Author

See this branch for a workaround: https://github.com/XENON1T/processing/tree/no_efield

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants