-
Notifications
You must be signed in to change notification settings - Fork 45
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
bug in saving precomputed meshes: unexpected keyword argument 'fuse' #600
Comments
Hi Greg, so sorry I missed this until now! I just pushed a fix that should be in the next release. |
william-silversmith
added
bug
The code is not performing according to the design or a design flaw is seriously impacting users.
meshes
Pertains to mesh objects or IO services.
labels
Jul 1, 2024
william-silversmith
added a commit
that referenced
this issue
Jul 3, 2024
* wip: zarr download implementation * feat: janky, but zarr image downloads work for non-timeseries * feat: support label argument and faster fill_missing * fix: support multiple fast fill bg colors * feat: support basic commit_info * feat: render zarr metadata and upload with commit_info * fix: throw some default values in there * feat: make axis mapping more general * wip: zarr image upload * fix: uploads not quite working, but are writing to disk * fix: write out chunks metadata correctly * fix: not working yet, but getting closer * fix: don't compress metadata on disk Zarr can't find those files with an extension. * fix: zarr can't decode metadata without filters being present as a key * fix: chunk size spatial dimensions were inverted * fix: handle 5d chunk sizes * feat: clear up cv vs zarr chunk size * fix: handle missing .zarray files * feat: add zarr, zarr2, and zarr3 to allowed formats * fix: convert to list * fix: convert to micrometers for zarr * fix: incorrect use of add_scale * feat: vol.mesh.save supports sharded meshes Resolves #600 * fix: add cache_locking to n5 * fix+test: cross-format transfers are not supported (yet?) * fix: n5 format can accept an info * feat: add commit_info for n5 * feat: add exists and delete for zarr * wip: zarr download implementation * feat: janky, but zarr image downloads work for non-timeseries * feat: support label argument and faster fill_missing * fix: support multiple fast fill bg colors * feat: support basic commit_info * feat: render zarr metadata and upload with commit_info * fix: throw some default values in there * feat: make axis mapping more general * wip: zarr image upload * fix: uploads not quite working, but are writing to disk * fix: write out chunks metadata correctly * fix: not working yet, but getting closer * fix: don't compress metadata on disk Zarr can't find those files with an extension. * fix: zarr can't decode metadata without filters being present as a key * fix: chunk size spatial dimensions were inverted * fix: handle 5d chunk sizes * feat: clear up cv vs zarr chunk size * fix: handle missing .zarray files * feat: add zarr, zarr2, and zarr3 to allowed formats * fix: convert to list * fix: convert to micrometers for zarr * fix: incorrect use of add_scale * feat: add commit_info for n5 * feat: add exists and delete for zarr * feat: add function for cross format transfers * feat: add transfer_to across formats * fix: enable cross format transfers * feat: add transfer_by_rerendering to zarr * fix: ensure encodings are reasonable * fix: progress bar * docs: remove erroneous comment * fix: transfer_by_rerendering not respecting bbox * feat: add method for getting the time resolution in seconds * feat: more comprehensive units * fix: more general logic for spatial resolution in nm * feat: add error for multi-channel * feat: support multiple channels * feat: add some time related functions * fix: better support for multiple channels * fix: bounding box and negative indicies * fix: more issue in downloading 3-channel images * fix: ensure time is sliced with correct offset
Thanks @william-silversmith ! |
The next release is out! Should be fixed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi @william-silversmith. Hope all is good! I'm seeing a new (to me) error with cloudvolume 8.25.0 although
8.24.2
also gives this for @schlegelp.This is from R but the python code should be obvious:
gives
The text was updated successfully, but these errors were encountered: