-
Notifications
You must be signed in to change notification settings - Fork 4
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
Issues related to napari-mm3 installation #38
Comments
Hi, Unfortunately it sounds like these are issues with your javabridge installation, so you may be better served by asking on the javabridge repository or StackOverflow. What format is your raw data in? Right now we do rely on Bioformats (which needs javabridge) to convert all file formats other than .nd2 or tiff, but if you can convert your data to one of these formats you should not need it. |
Thank you very much! |
Can you share the stack trace for the error you got? (i.e. which line specifically caused the IndexError). Make sure that you have "image_source" set to "Bioformats/other" in the Compile widget. The widget expects the tiff files to have a format ending in t000xy00c0.tiff with the time point t, FOV xy and color channel c. If you want, you can share a sample of your raw data with me and I can try to reproduce the error. |
Thank you very much!I tried reinstall my python and napari-mm3 can be called successfully. |
Can you share the full stack trace you get? (including initial 'AttributeError') |
We had a similar bug to what you describe a few months ago but it should be resolved in the most recent version of the code - make sure you are pulling the current version from Github (git clone https://github.com/junlabucsd/napari-mm3.git), not downloading from PyPI or napari-hub. |
Thank you very much! |
Sorry that you're still having trouble! Yes, it's been tested on Windows 10 (64 bit). Can you share the errors you get? |
After installtion of napari-mm3, i encountered two difficulties.
I am here to ask for your help, thank you very much!!!
The text was updated successfully, but these errors were encountered: