Comments (19)
Hi guys, sorry for stepping in, I have a naive question, why in the op plots the last grid points (bottom right corner) are not a triangular matrix... I see they contain small values, but they shouldn't be there at all no?
It's a relevant question, and you have to add that last row is also empty, but we have answers for this (and at least the second one you should know, since you implemented yourself):
- it's not triangular because of interpolation, you need at least that many points (
interpolation_degree + 1
) - last row is empty, because the PDF it's constrained to be 0 at z=1
f(z=1) = 0
, thus it is completely independent from the input (nevertheless it's nice to have square operators, and it's not a huge waste to add one line, while it would be harder to maintain to have a rectangular operator and having to add one point manually to the output PDF)
from eko.
Please, can you add some details and how to reproduce?
from eko.
@alecandido Since we found the problem and changed the colormap, I think we can close this issue, right?
from eko.
I think so as well :)
Maybe last thing is: check how they look like in evolution space (in principle should be much easier, since you should only have relevant elements for S.S, S.g, g.S, g.g, T3.T3, V3.V3, ...
, and not the full square).
from eko.
Maybe last thing is: check how they look like in evolution space (in principle should be much easier, since you should only have relevant elements for
S.S, S.g, g.S, g.g, T3.T3, V3.V3, ...
, and not the full square).
Most likely it won't happen, because the operator is computed before in flavor space. A possible solution is to introduce some kind of tolerance when checking the absolute maximum, and ignore operators that have all elements below.
from eko.
Maybe last thing is: check how they look like in evolution space (in principle should be much easier, since you should only have relevant elements for
S.S, S.g, g.S, g.g, T3.T3, V3.V3, ...
, and not the full square).Most likely it won't happen, because the operator is computed before in flavor space. A possible solution is to introduce some kind of tolerance when checking the absolute maximum, and ignore operators that have all elements below.
Problem is that I noticed now that plots.py only plots on pid labels. So first I need to change this
from eko.
Ok, good to have found out.
from eko.
Ok, good to have found out.
Now the plots in evolution basis should be available. However, I found another bug. When you run sandbox in flavor_basis it will not work. Speaking to @felixhekhorn, he said that it is related to how the caching is done and that it is a known bug. So, should I close this issue @alecandido?
from eko.
Thank you very much for your progresses @andreab1997, about the two points:
- before closing the issue, I'd like to see the plots in evolution basis, if they are fine I'd be happy to actually close (for the sake of speed, and by the way reporting, can you post a PDF in a comment in this issue, please?)
- concerning the
flavor_basis
I don't perfectly remember the issue, but I've an idea, and I agree that is a completely decoupled problem, so, if ever, we'll open a separate issue
from eko.
Yes, I post here the PDF with the plot in ev.basis
off080e_tedfbed.pdf
from eko.
You see that some are not worth to plot, like V3.V
:
because it's fully non-singlet and non-diagonal, but also V.g
:
that looks much smoother, it's still not worth, if you look at the scale.
So I would filter them out putting a threshold, maybe at 10^-8
.
Moreover, try to translate the names according to the map in basis_rotations
, since these flavors code we made up ourselves and are little understandable to anyone else (at the moment they are not even present in the docs...).
from eko.
You see that some are not worth to plot, like
V3.V
:because it's fully non-singlet and non-diagonal, but also
V.g
:that looks much smoother, it's still not worth, if you look at the scale.
So I would filter them out putting a threshold, maybe at
10^-8
. Moreover, try to translate the names according to the map inbasis_rotations
, since these flavors code we made up ourselves and are little understandable to anyone else (at the moment they are not even present in the docs...).
Yes, sorry you had already mentioned the threshold stuff. Anyway, now it should work. I'm posting the new pdf.
off080e_tedfbed.pdf
from eko.
Yes, sorry you had already mentioned the threshold stuff. Anyway, now it should work. I'm posting the new pdf.
Don't mind, that's exactly how the old plots looked like, and it's perfectly recovered.
Thank you for your effort, I think we can close!
from eko.
Hi guys, sorry for stepping in, I have a naive question, why in the op plots the last grid points (bottom right corner) are not a triangular matrix... I see they contain small values, but they shouldn't be there at all no?
If not too much, it will be nice to rescale the axes in the range [x_min, 1] instead of the grid binning
from eko.
Hi guys, sorry for stepping in
don't mind, as a core developer you can step in any time ;-)
, I have a naive question, why in the op plots the last grid points (bottom right corner) are not a triangular matrix... I see they contain small values, but they shouldn't be there at all no?
now the behaviour at the border of the grid, is exactly as we defined the interpolation - i.e. in esp. at the top border of the grid the top, say 4, polynomials are active, since those are the 4 nearest (given polynomial degree 3)
from eko.
If not too much, it will be nice to rescale the axes in the range [x_min, 1] instead of the grid binning
I guess you are speaking of relabeling the axes (that's feasible) with z values (I keep calling z, you know why), but bins are bins (those are matrix entries), so I would keep the binning explicit (even in the relabeled variable)
from eko.
This has been solved right?
from eko.
I guess so. @andreab1997?
from eko.
I guess so. @andreab1997?
Yes, it is solved.
from eko.
Related Issues (20)
- Typo in docs HOT 2
- `evolve_pdfs` doesn't produce correct LHAPDF grids
- Is `matching_order` correctly determined? HOT 8
- On the backwards-compatibility or future-proofing of ekos HOT 15
- Remove photon and top from LHAPDF grid if they are not active HOT 5
- seemingly infinite error loop when running evolve_pdfs
- infinite error loop running evolve_pdfs HOT 5
- Packaging for rust
- Release for py 3.12 HOT 1
- Update `eko.io.dictlike` HOT 2
- Add a_Qg^3
- Version being saved as 0.0.0 HOT 3
- Couplings method is called with array instead of float
- Publish Rust crates HOT 5
- Update N3LO P_gq with newer results. HOT 1
- Define MSRV HOT 2
- Segmentation fault when running benchmark after rustification HOT 10
- Clarify `genpdf` usage HOT 2
- Oxidation roadmap
- Fix maturin deployment to PyPI HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from eko.