-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add a --overwrite-if-different
#207
Comments
mh? how would that work? you copy the ekos in any case and then generate the op card and then check the new generated against the one inside the eko? is this what you are suggesting? just to remind you that we were briefly thinking in the past about checking if two (NNPDF) theories are compatible (eko- or grid-wise), but then decided that the check would be too complex ... |
Yes. Exactly this. If the theory and operator card inside the eko are the same, the eko will be.
Yes, yes, I do link. I mean, not me me, the clever anoymous user. |
I guess that should be doable ... however, I'd say let's restrict to bit-by-bit-equality (else it will be complicated again) and this would neglect different card version of course for that we need the opcard - cc #202 |
The operator card is always inside the eko and needs to be generated even if not written down to create the new eko. But anyway, in #202 you already convinced me about keeping the opcard and removing only the template. |
There are certain situations where we might not be sure whether an eko can be reused or not (for instance, if one tries to create both theories 40_000_000 and 41_000_000, many ekos will be the same for NLO and NNLO grids, but some won't due to new channels, different scales, etc).
The clever user might copy all ekos from one folder into the other, thinking they are hacking the system... however all sort of problems will arise.
Ideally
pineko
will look at the theory and operator inside the eko and realize when the resulting product would be exactly the same and when it won't.The text was updated successfully, but these errors were encountered: