Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

converter: large records timeout after 220 seconds #788

Open
GraemeWatt opened this issue Apr 26, 2024 · 0 comments
Open

converter: large records timeout after 220 seconds #788

GraemeWatt opened this issue Apr 26, 2024 · 0 comments
Labels
complexity: high priority: medium type: bug Indicates an unexpected problem or unintended behaviour

Comments

@GraemeWatt
Copy link
Member

I'm creating this issue to keep track of which records timeout after 220 seconds due to the conversion taking longer than this limit.

  1. https://www.hepdata.net/record/ins1740909?version=2

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, #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:

docker run -v $PWD:$PWD -w $PWD --rm -it hepdata/hepdata-converter-ws hepdata-converter -o yoda -r ATLAS_2019_I1740909 -d 10.17182/hepdata.89321.v2 HEPData-ins1740909-v2 HEPData-ins1740909-v2-yoda.yoda

The -o option can be one of yoda, yoda1, csv, root, yaml. The -r option should be omitted unless converting to the yoda or yoda1 format.

@GraemeWatt GraemeWatt added type: bug Indicates an unexpected problem or unintended behaviour priority: medium complexity: high labels Apr 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
complexity: high priority: medium type: bug Indicates an unexpected problem or unintended behaviour
Projects
Status: To do
Development

No branches or pull requests

1 participant