Re-examine iterations in integral for "exact"
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by locating the iterate-exact evolution integral and its current fixed subdivision in steps of ev_op_iteration over ln(a_s). Compare subdivisions in ln(a_s), a_s, and fixed step sizes, as suggested in the issue, and study how their results converge. The issue gives no file or test names; done means selecting a converged reference method and measuring how fewer steps affect accuracy and numerical stability.
Written by the indexing model from the issue text.
Description
We should study the subdivision of the evolution integral for "iterate-exact". The current algorithm is a fixed subdivision irrespective of the evolution length with ev_op_iteration steps in $\ln(a_s)$. This might not be the best way and Marco Bonvini pretty much confirmed this. He suggested to compare different methods until they converge, which one can then consider as the reference "truth" and then subsequently reduce the number of steps and measure the distance to that reference.
Other viable options are subdivisions in $a_s$ and/or a fixed step size.
The problem is becoming quickly a bit messy with all the different options ... still to be more numerically stable, we should do it at some point. The current implementation is the naive one, which we choose back in the days.
- Dominant language
- Python
- Stars
- 13
- Forks
- 9
- Avg merge
- 6d 16h
- Merged PRs (30d)
- 3
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/eko
-
rust
Difficulty 3/5 1-2 days Newbie friendliness 55/100
Maintainers usually reply within 1 day
-
physics
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
benchmarks
Difficulty 3/5 1-2 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
-
benchmarks rust
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
-
rust
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
mozilla-ai/cq#601 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
intcomma returns exponential notation for large floatsPossibly taken @Omarinho12345 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
python-humanize/humanize#521 ·
Maintainers usually reply within 1 day
-
LUCJ pass manager raises NoEdgeBetweenNodes when an edge is bad for two two-qubit gatesPossibly taken @hat-im claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
opensubtitlescom: provider rejects pt-PT even though its own converter maps itPossibly taken @paulo-0308 claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Diaoul/subliminal#1405 ·