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

List of metadata for pineappl grids #64

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from
Draft

Conversation

comane
Copy link
Member

@comane comane commented Feb 27, 2024

This PR adds some docs regarding the metadata keys that one should add to a PineAPPl grid after having runned MATRIX.
@t7phy, @achiefa please have a look and feel free to change stuff.

@felixhekhorn
Copy link
Contributor

It seems github has some problems with PRs and is not updating at the moment and it is Friday evening, so you are spared for now - but on Monday morning I will write a loooong list of complaints

Copy link
Contributor

@felixhekhorn felixhekhorn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

use one of the available interfaces (including the CLI) to do so.


- **Optimize and scale:** apply the built-in optimization and rescaled by a factor if needed to go e.g. from pb to fb.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that is useless

  • don't tell me what the pineappl interface does
  • you may want to write "since MATRIX is not doing the optimazation yet, remember to do it here" and then you should complain with MATRIX
  • you may want to write "MATRIX outputs by default in fb, so remember to rescale"


- **Optimize and scale:** apply the built-in optimization and rescaled by a factor if needed to go e.g. from pb to fb.

- **Delete keys:** delete `y_label_unit`, `xlabel` and `x_label-tex`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

deleting keys is wrong, we need those! you may want to overwrite ...

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no, these keys have to be deleted! Pineappl uses x1_label, x1_label_tex, x1_unit, y_label, y_label_tex, y_unit, so keys like 'x_label', 'x_label_tex', 'x_unit_label' and 'y_label_unit' indeed have to be deleted and new keys with correct names have to be manually set. this wrong labelling of keys is a typo in matrix.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fine, but then you realize that precisely such information should be in the docs

- value
- comment
* - y-unit
- pb/GeV
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that is useless - this information is grid dependent

- pb/GeV
-
* - y-label
- differential x-sec
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this does not follow our convention

- differential x-sec
-
* - lumi_id_types
- pdg_mc_ids
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

again you want to write "since MATRIX is not doing this by default, remember to add it" and then complain with MATRIX

@comane comane marked this pull request as draft March 4, 2024 12:22
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

Successfully merging this pull request may close these issues.

3 participants