Convert from YAML format to YODA #5
Labels
Comments
|
After considering multiple options I decided to use yoda python package which comes together with compiled yoda libraries (even considering all problems which it may cause for deployment). The basic export to |
|
Yes, the approach should be the same as the ROOT export: choose the YODA object based on the data type. If there are two independent variables then use a |
|
Yes, I saw yoda export from current HEPData, but as we are trying to improve ROOT files to provide the most suitable objects representing stored data, I thought that the same effort should be made for yoda exports. My question was rather about whether it would break some compatibility for the tools designed for yoda exports from the old HEPData (and possibly Rivet toolkit). |
|
I finished YAML -> YODA conversion. here's sample output file (below). There is one question I have though - are there any specific requirements for Path element / title? There is also another thing I would like to mention - Yoda Scatter3D (python bindings) can not be used at this moment, because yoda.core.Pont3D has a bug (or at least all the symptoms point to this conclusion). The problem is that during construction of the object (code below) following error happens: Also another design problem / issue is that yoda.core.Point3D accepts only x and y coordinate in constructor, which seems odd given that it's point in 3 dimensional space. Can you give any comments on this one @GraemeWatt ? YODA Output file |
|
With yoda.core.Point3D being fixed this is the new output. I still don't have a definite feedback how to construct path in case I won't have all necessary information to do that from the base YAML file? (or will I? @eamonnmag any comments on that?) |
|
So, most can be. But is 'independent variable number' and identifier or is it just the number of variables @GraemeWatt ?
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Of the current HepData export formats, a conversion to the YODA format should be implemented in the new system. This format is needed by the Rivet toolkit. Currently, only total uncertainties are supported in the YODA format, which should be computed from the sum in quadrature of the individual uncertainties. This might change in the future, but for the moment we still need the separate CSV export to provide the complete breakdown of multiple uncertainties in a simple plain-text format.
The text was updated successfully, but these errors were encountered: