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
This may be specific to this particular dataset, but for Kasthuri/ac4/em, .available_mips (through CloudVolume) gives hierarchy levels [0, 1, 2, 3], but on the BossDB API site and with intern (via .available_resolutions), it says num hierarchy levels is 1. However, downsampling with resolution=1 / mips=1 is still possible on intern and CloudVolume. Is there a way to standardize hierarchy levels across API site/CloudVolume/possible downsampling resolutions?
The text was updated successfully, but these errors were encountered:
This might just be a bookkeeping mismatch — great find btw! We might want to pass downsample-level boss API calls through to cvdb to check the underlying filesystem...
This may be specific to this particular dataset, but for
Kasthuri/ac4/em
,.available_mips
(through CloudVolume) gives hierarchy levels [0, 1, 2, 3], but on the BossDB API site and with intern (via.available_resolutions
), it says num hierarchy levels is 1. However, downsampling with resolution=1 / mips=1 is still possible on intern and CloudVolume. Is there a way to standardize hierarchy levels across API site/CloudVolume/possible downsampling resolutions?The text was updated successfully, but these errors were encountered: