Propagate montecarlo uncertainty from fastnlo grids

Open
#130 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
data

Research direction

Start by finding the pinefarm code that generates or processes fastNLO grids, then check how it invokes external commands and attaches grid metadata. The issue suggests running fnlo-tk-yodaout on downloaded grids and parsing its per-bin statistical uncertainties. Done means those uncertainties are preserved as metadata in the generated grid; the issue does not name a specific file or test.

Written by the indexing model from the issue text.

Description

In the fastnlo grid that we download from plougshare, at least for the dijet data, the MC uncertainties are already included, e.g.,

~$ fnlo-tk-yodaout applfast-cms-dijets-v2-fc-fnlo-arxiv-1705.02628-xsec000.tab.gz NNPDF40_nnlo_as_01180 ST NNLO

#=================================================================================
 # Relative statistical uncertainties (ST)
 #---------------------------------------------------------------------------------
 # bin      cross_section           lower_uncertainty       upper_uncertainty
 #---------------------------------------------------------------------------------
    1       1.17712104601E+03      -8.93967724580E-03       8.93967724580E-03
    2       5.88123036467E+02      -7.37521019135E-03       7.37521019135E-03
    3       3.06752769868E+02      -8.68429710285E-03       8.68429710285E-03
    4       1.65291105626E+02      -6.68794255972E-03       6.68794255972E-03
    5       8.94284730323E+01      -9.92508174274E-03       9.92508174274E-03
    6       4.92202483062E+01      -7.94142733975E-03       7.94142733975E-03
    7       2.92246985763E+01      -1.37335993342E-02       1.37335993342E-02
    8       1.61952732333E+01      -1.20941659544E-02       1.20941659544E-02
    9       9.50513815304E+00      -7.51627623106E-03       7.51627623106E-03
   10       5.59814170314E+00      -8.88502884738E-03       8.88502884738E-03
.
.
.

This information should be propagated to the grid. If not directly by pineappl (not sure whether it can be added, @Radonirinaunimi?) the pinefarm script should run the command above, parse the uncertainty and add it to the grid as metadata.

I think we will need to take it into account if we want to go towards the pt tail. For this grid for instance, already for the 10th bin the MC uncertainty on the NNLO coefficient is about 30%:

 ##################################################################################
 # fnlo-tk-yodaout: Evaluating uncertainties
 ##################################################################################
 #=================================================================================
 # Relative statistical uncertainties (ST)
 #---------------------------------------------------------------------------------
 # bin      cross_section           lower_uncertainty       upper_uncertainty
 #---------------------------------------------------------------------------------
    1       3.71518823259E+01      -2.82864000000E-01       2.82864000000E-01
    2       2.36089186045E+01      -1.83394100000E-01       1.83394100000E-01
    3       1.37816639030E+01      -1.93069790000E-01       1.93069790000E-01
    4       9.54858780265E+00      -1.15584010000E-01       1.15584010000E-01
    5       4.71713438802E+00      -1.88037690000E-01       1.88037690000E-01
    6       2.14050531455E+00      -1.82440820000E-01       1.82440820000E-01
    7       2.57801390436E+00      -1.55641770000E-01       1.55641770000E-01
    8       8.61484910806E-01      -2.27279070000E-01       2.27279070000E-01
    9       6.06435811476E-01      -1.17713530000E-01       1.17713530000E-01
   10       3.65014957690E-01      -1.36194550000E-01       1.36194550000E-01
   11       2.61725375041E-01      -8.91347580000E-02       8.91347580000E-02
   12       1.43491842804E-01      -8.24604230000E-02       8.24604230000E-02
   13       9.55372317654E-02      -7.67335580000E-02       7.67335580000E-02
   14       4.35619442853E-02      -1.42809410000E-01       1.42809410000E-01

cc @andrpie @enocera

Dominant language
Python
Stars
1
Forks
0
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NNPDF/pinefarm

All issues in NNPDF/pinefarm

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.