It seems like a request to Zenodo is triggered each time a new exam is processed when declaring an atlas from Zenodo via enum.
Currently, we use this dirty workaround in epitome:
https://github.com/neuronflow/epitome/commit/99278e66acaece81737b424d730bab74f7253340
We want to avoid repetitive requests; instead, download the atlas once and then use it. Ideally, we can support parallel processing.
Also diagnose if the same issue is also present for other Zenodo assets?
It seems like a request to Zenodo is triggered each time a new exam is processed when declaring an atlas from Zenodo via enum.
Currently, we use this dirty workaround in epitome:
https://github.com/neuronflow/epitome/commit/99278e66acaece81737b424d730bab74f7253340
We want to avoid repetitive requests; instead, download the atlas once and then use it. Ideally, we can support parallel processing.
Also diagnose if the same issue is also present for other Zenodo assets?