-
Notifications
You must be signed in to change notification settings - Fork 2
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
Pineparser for compatibility with new theories #63
base: main
Are you sure you want to change the base?
Conversation
…y depend on dataset spec and not C++
…Spec and load it with pineappl_reader. Still needs more testing, especially does not support shifts and normalization yet
Hi @comane ,
I am working with theory 270. I have manually added this FK table:
and this compound file (using the old way):
Here is the content of the compound file:
When I
It looks like it is messing up with both the prefix and the suffix. It is due to the fact that the old format had the following naming convention for FK tables:
|
For the record, is this PR relying on the old compound files to link commondata and FK tables or is it expecting the info to be stored in the yamldb folder of the theory, like nnpdf does currently? |
Can you try adding the
I don't think that this PR supports compounds yet |
Sure thing. I have just tried
I have also removed the compound file I had initially added. It gives me the following error:
It appears to complain about the absence of the compound file and the metadata file. The metadata file makes sense since I am using an old commondata implementation with a new FK table. I will implement the metadata or try with a dataset which has it already implemented and come back to you. I am confused about the compound error though. |
Hi @comane ,
But if I add another dataset to be contaminated, the vp-setupfit steps bugs out:
I have then the following error:
I have similar problems with validphys runcards. |
I have no idea what the problem can be to be honest |
I think I understand the issue. The contamination itself is not the issue, the new FK tables do not work in a closure test. This runcard produces a bug for instance:
The bug disappears if I comment out the closure test key. |
validphys2/src/validphys/loader.py
Outdated
|
||
# use different file name for the FK table if the commondata is new | ||
if new_commondata: | ||
fkpath = tuple([theopath/ 'fastkernel' / (f'{setname}.pineappl.lz4')]) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This does not work for double differential measurements, i.e. ATLAS_1JET_13TEV_DIF
which is a double differential measurement in |y| and pT, to make it work one could extract the file names from the <DATASET>_<OBS>_metadata.yaml
file. I suggest moving the loading of the .yaml
file from the next if
clause to this one.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In my case the dataset name is ATLAS_1JET_13TEV_DIF_PT-Y
but the names of the FK files are ATLAS_1JET_13TEV_DIF_PT-Y_BIN#.pineappl.lz4
Yes, exactly. As I had already commented in the description above, this PR still not supports the filtering of closure test data when using the new pine parser. |
This reverts commit 06d9c50.
The scope of this PR is to allow SIMUnet to use new theories generated with pineappl.
Example on how to use this for the moment:
from
theory_700/fast_kernel
copy NMC_NC_NOTFIXED_P_EM-SIGMARED.pineappl.lz4 into theory_270/fast_kernelfrom nnpdf_data/new_commondata/NMC_NC_NOTFIXED_P copy the metadata.yaml as
NMC_NC_NOTFIXED_P_EM-SIGMARED_metadata.yaml
intotheory_700/fast_kernel
copy
DATA_NMC.dat
intoDATA_NMC_NC_NOTFIXED_P_EM-SIGMARED.dat
withindata/commondata
Note: make sure that in the metadata.yaml file you change the name of the fktable to the name of the pineappl grid.
Now, it should be possible to run a fit with the following dataset_inputs:
TODO