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
{{ message }}
Repository navigation
Add feature flag that allows users to interpolate the primary dimension. #30
This is related to #29. There is a single costly EE RPC call that we make that may not be essential. Right now, we need to access all the system:time_start properties from each image in the collection, which is slow. If instead, we read the first and last (few) values and interpolated the rest, we could save time in the EE backend and avoid the biggest bottleneck for Xee. The tradeoff would be that the interpolated values may differ from the actual values, which would definitely cause data errors.
A good scenario seems to be that we add this capability behind a feature flag (name TBD). For users that understand their data well and know that this is safe, they will get a faster means of opening data. For datasets that are hard to interpolate time (or another primary dimension), users have a fallback.
Once this feature flag exists, we'd also need to rely on the fallback for slicing image ids in _slice_collection().
I believe it is still opened. However, there is a risk of this feature violating correctness. If we interpolate an image that is not actually there, it would be worse than waiting more for the original dataset registration. For this to be closed, we'd need to include a fallback if one or more images were missing.
@jdbcode would be the best person to coordinate with on this contribution.
Activity
Xee performance: Improving benchmarks.
Xee performance: Improving benchmarks.
Xee performance: Improving benchmarks.
Tweezky66 commentedon Jun 28, 2026
Hi @alxmrs! Is this still opened? If yes i would like to work on it
alxmrs commentedon Jun 28, 2026
I believe it is still opened. However, there is a risk of this feature violating correctness. If we interpolate an image that is not actually there, it would be worse than waiting more for the original dataset registration. For this to be closed, we'd need to include a fallback if one or more images were missing.
@jdbcode would be the best person to coordinate with on this contribution.