The hepdata-converter package should be made more efficient (for example, by resolving HEPData/hepdata-converter#50, HEPData/hepdata-converter#51, HEPData/hepdata-converter#52, HEPData/hepdata#563). A workaround is for a user to run the conversion offline using the provided Docker image hepdata/hepdata-converter-ws where the hepdata-converter package (docs) is provided with all dependencies. For example, after clicking "Download All" then "YAML with resource files" to download the original directory HEPData-ins1740909-v2, conversion to the yoda format can be performed with:
I'm creating this issue to keep track of which records timeout after 220 seconds due to the conversion taking longer than this limit.
The
hepdata-converter
package should be made more efficient (for example, by resolving HEPData/hepdata-converter#50, HEPData/hepdata-converter#51, HEPData/hepdata-converter#52, HEPData/hepdata#563). A workaround is for a user to run the conversion offline using the provided Docker imagehepdata/hepdata-converter-ws
where thehepdata-converter
package (docs) is provided with all dependencies. For example, after clicking "Download All" then "YAML with resource files" to download the original directoryHEPData-ins1740909-v2
, conversion to theyoda
format can be performed with:The
-o
option can be one ofyoda, yoda1, csv, root, yaml
. The-r
option should be omitted unless converting to theyoda
oryoda1
format.