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
We write metadata to tiff and zarr but don't test what's written inside cpx. The approach to date has been to test on the cpx-python side where it's simpler to find and integrate standard reference reader implementations with the test code - for example, we can just pip install tifffile.
However it's better to catch these errors upstream if we can.
So this issue is really about finding candidate reference reader implementations and integrating them into our testing inside cpx.
There are a lot of possible approaches here, including using python.
for reference, see acquire-project/cpx#131
The text was updated successfully, but these errors were encountered:
nclack
changed the title
add tests that check written files represent metadata as expected
add tests that check zarr is written as expected
Mar 27, 2023
On acquire-project/cpx#125 and acquire-project/cpx#135, I ran into a bunch of issues around how chunking was handled. There are probably a family of checks that would be nice to have:
We write metadata to tiff and zarr but don't test what's written inside cpx. The approach to date has been to test on the cpx-python side where it's simpler to find and integrate standard reference reader implementations with the test code - for example, we can just
pip install tifffile
.However it's better to catch these errors upstream if we can.
So this issue is really about finding candidate reference reader implementations and integrating them into our testing inside cpx.
There are a lot of possible approaches here, including using python.
for reference, see acquire-project/cpx#131
The text was updated successfully, but these errors were encountered: