You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NMXReducedData keeps pixel id coordinate and there are >1e6 pixels
so it could carry relatively large data (>GB) in the end.
Therefore we would like to compress the large-size Dataset when we save it into h5 or nexus file.
The compression option is now hard-coded, but it makes saving very slow.
Some advanced users, i.e. IDS might want to turn it off when they have to debug the workflow.
Therefore we should
Find the optimal compression options comparing the advantages between speed and size of the output.
Make it possible to lower the compression option, with the optimal compression by default.
Document about compression in the workflow user-guide.
The text was updated successfully, but these errors were encountered:
NMXReducedData
keeps pixel id coordinate and there are >1e6 pixelsso it could carry relatively large data (>GB) in the end.
Therefore we would like to compress the large-size
Dataset
when we save it intoh5
ornexus
file.The compression option is now hard-coded, but it makes saving very slow.
Some advanced users, i.e. IDS might want to turn it off when they have to debug the workflow.
Therefore we should
The text was updated successfully, but these errors were encountered: