-
Notifications
You must be signed in to change notification settings - Fork 10
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
Bump bioformats2raw version from 0.2 to 0.4 #13
Comments
writing directly to s3 leads to a super long error log, which does happen when saving locally. Here's the end of the error log
|
@BioinfoTongLI : can you include the command you used? (i.e. is --entrypoint-url involved?) |
Not using |
If you were accessing this via
with webatlas being the bucket. Adding the bucket to the front of the entrypoint ("webatlas.cog.sanger.ac.uk") is virtual-hosted-style as opposed to path-style: https://docs.aws.amazon.com/AmazonS3/latest/userguide/VirtualHosting.html#path-style-access So perhaps try setting |
Still seeing the same
Afaik, this |
I assume then that we will need to start using our own s3filesystem. See https://imagesc.zulipchat.com/#narrow/stream/212929-general/topic/ome-zarr.20basics.3A.20writing.20.20to.20s3/near/281819192 for a related conversation. Would be good to know how much time/space uploading directly will get you to know how important it is to prioritize this. |
I see - it is currently not the most urgent task. nextflow can do the push and works fine with our CEPH storage. The cost is that we need to duplicate the data before the push. Tho, this might be an issue when it comes to the real atlas dataset (100 + whole embryo images). Let's priotize this in the next milestone. |
Indeed it's Ceph's rados gateway. Note: Uploading from bioformats2raw should work like this for you:
Keep in mind that uploading straight to S3 will slow down the process, because uploading is slower than disk I/O. But, like you said, won't duplicate the data and you won't have to copy it afterwards... so it's up to you! |
Thanks @prete! Interestingly your syntax works.... @joshmoore worth an issue to glencoe? |
My best guess is that |
All seems to be working fine. Closing this for now. Reopen if needed. |
bump the tif-to-zarr conversion from 0.2 to the latest stable version (0.4.0).
currently using this image (https://hub.docker.com/layers/bioformats2raw/openmicroscopy/bioformats2raw/0.4.0/images/sha256-29e650dca4610898d2c5d7639c350f172d3f4d0d0aea7078454b76e10245b0c7?context=explore)
Vitessce works with this version as well.
Tho, the conversion is currently only done locally. Use this option to write directly to s3.
glencoesoftware/bioformats2raw#89
The text was updated successfully, but these errors were encountered: