Swap `Q0` and `nf0` for `Qref` and `nfref`
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
Research direction
Start in src/yadism/runner.py around line 121, where Q0 and nf0 build the atlas for the structure functions. Check whether anything else reads these names, including the alphas interface used through eko, before renaming them to Qref and nfref. Done when the references are renamed consistently and the existing tests still pass.
Written by the indexing model from the issue text.
Description
I believe the only relevant appearance of Q0 and nf0 is here:
https://github.com/NNPDF/yadism/blob/072fc9ecd5f2496fbb5b21c143673fe7232f3ff7/src/yadism/runner.py#L121
where we use them to construct the atlas for the structure functions (i.e. how many light flavors per Q2). However, this is only needed to provide a reference point (since the class requires that), but I think we never compute any paths, i.e. any reference will do.
I suggest to use Qref and nfref instead, which you may need for alphas, if you use the interface through yadism to eko. The core functionality of yadism is of course independent of $\alpha_s$ and its configuration.
- Dominant language
- Python
- Stars
- 11
- Forks
- 2
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 6
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from NNPDF/yadism
-
Add TMC documentationPossibly taken @jekoorn claimed this 23 days ago. Opendocumentation
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
NNPDF/yadism#386 · 2 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Maintainers usually reply within 1 day
-
rtd is broken due to sphinxcontrib-details-directivePossibly taken @ashishsoni-ai claimed this 33 days ago. Opendependencies documentation
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
NNPDF/yadism#378 · 2 comments ·
Maintainers usually reply within 1 day
-
physics
Difficulty 5/5 Over a week Newbie friendliness 8/100
NNPDF/yadism#354 · 1 comment ·
Maintainers usually reply within 1 day
-
Fix pydocstyleOpendocumentation good first issue
Difficulty 3/5 1-2 days Newbie friendliness 45/100
NNPDF/yadism#263 · 3 comments ·
Maintainers usually reply within 1 day
Similar issues
-
Layout accepts a step threshold of 0 or less, then in-toto-verify crashes with StopIterationPossibly taken @BahaaMattar claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
needs discussion
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
openfga/openfga.dev#1436 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
usb-device-hid: MouseInterface reports bInterfaceProtocol 1 (keyboard) instead of 2Possibly taken @Duhan07 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
micropython/micropython-lib#1176 ·