Skip to content
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

failing to show remote datasets in BDV when the viewsetups use non-identity view transforms #19

Closed
xulman opened this issue Apr 25, 2023 · 3 comments

Comments

@xulman
Copy link
Member

xulman commented Apr 25, 2023

....simply when, e.g., a dataset consists of four channels each being displayed translated/rotated/scaled w.r.t. to some common reference frame

One can download a test dataset, unzip, a point BDV to the 807191f5-.../0/export.xml file to understand what the dataset looks like. It should look like this:
Screenshot_20230425_182237
when zoomed-out a little, and displayed using the Fuse mode on.

➡️
The issue comes when accessing this dataset using any option from the menu Fiji -> Plugins -> HPC DataStore -> BigDataViewer, which means to access the data remotely via the DS server itself, in this regime the opening fails. The error is the following.
Screenshot_20230425_182725

Worth noticing is that the JSON listing from alfeios, where this dataset is also installed, shows nulls for transformations and viewRegistration fields.

@xulman
Copy link
Member Author

xulman commented Apr 25, 2023

but when I request a full image (Fiji -> Plugins -> HPC DataStore -> Read full image), it works well... even portions of it.. even writing it... so pixels fetching seems to be okay..

the issue seems to have its root in how the metadata for locally created "SPIM Object" is constructed

@xulman
Copy link
Member Author

xulman commented May 18, 2023

update, this problem seems to be on the client side actually

the error report is not coming from the server but is produced by the client, either in DataStore or in BDVlegacy viewing regime

a it seems to be because the dataset is time-lapse 297->420, that is a time-lapse with the first timepoint not starting at 0

@xulman
Copy link
Member Author

xulman commented Jun 9, 2023

sooo,

@xulman xulman closed this as completed Jun 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant