Reimplement hera datasets #2175
Conversation
| import yaml | ||
|
|
||
| @dataclass | ||
| class commondata: |
There was a problem hiding this comment.
If the filters share similar or even identical parts, you can consider to place it in the filter_utils folder and store common parts there. For ex:
from nnpdf_data.filter_utils.hera import commondata
|
hi @peterkrack on top of the checks, make sure to change the process_type to one of these https://github.com/NNPDF/nnpdf/blob/master/validphys2/src/validphys/process_options.py (there should be some DIS types available) and change the kinematic files to use the variables listed there (which to 1st approximation means changing k1, k2, to x,Q or the other way around). You might need to change Q to Q2 in the kinematic files as well. |
…rtainties from systematics, moved class commondata to utils module.
…o make the tests pass.
|
Hi @peterkrack what is the status of this? |
|
Hi @peterkrack, sorry to bother you again, what is the status of this? |
|
Hi @peterkrack could you include in this PR data-theory comparisons and xq kinematic coverage plots? Thanks |
| @@ -123,5 +126,8 @@ implemented_observables: | |||
| legacy: | |||
| data_uncertainties: | |||
| - uncertainties_legacy_EP-SIGMARED.yaml | |||
| reimplemented: | |||
| data_uncertainties: | |||
There was a problem hiding this comment.
Instead of a variant called "reimplemented" this should be the standard dataset, so put this in data uncertainties.
Also, if the legacy and new uncertainties are numerically equal, you can remove the legacy uncertainties.yml file and make the legacy variant point to your new file. This will facilitate cleaning up legacy variants later.
Added rawdata and filter.py script for HERA dataset.
Checks of reimplemented data are still missing.