-
Notifications
You must be signed in to change notification settings - Fork 1
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
16 bit Tiffs are generating black thumbnails #466
Comments
File path: |
The images come from a new microscope and with new tools which export the images to 16-bit TIFFs. The tiff contains outlier pixel ( perhaps caused by X-rays ) for example 1632 value with a median of the image at 151. The range preserving approach of pytools.convert will not work with this. A similar issue was previous encountered with 16-bit tiff exported from FIBSEM images. For this the 16-bit were preserved I the OME ZARR, but the intensity was windows with a MAD algorithm when viewing. |
The command line from convert_3d_mrc_to_tiff was run on 4 sample input 16-bit tiff files. The conversion looked good. And Bryan said "those look good to me". This can address this issue. However, it raises the question if these 16-bit TIFF need to be processed with this separate conversion, or if all can be run through the IMOD newstack command. |
#468 should close this |
Hedwig URL : https://hedwig.niaid.nih.gov/sessions/U2Vzc2lvbjozMTQ0/samples#N4IgygpgzlCWD2A7AMrKAXWiDmIBcoAagKIBKYAkgPIBy+ATADQiECCyAqsfqAIYyxsiCABMw6XgDNJAMVgAbdBABO+ANogO9QgC8AxvXkA3AEYBrAFoAHEwAlS8vfIBCjxDVMAreAA8AsjoAigC8IAC6zFawcooq6hEgUBDyEHpKIgAqAJ5W0PHMSbzKegAW4spYuHggIMxGsBAA7tm5+AAMzEUQMUrKUGAl8I2I+OjKAK4QBfDKmDjivEo8iTPoAMIVvQgj1cj86BxWIosQACIntSuzp7DKqZhI+CCn0HoQiCKVIAC+v99AA==
Please note that the 2D pipeline was updated formerly to support 16 bit files therefore these files should have
A sample 16 bit files can be found in the Hedwig Teams channel: https://nih.sharepoint.com/:f:/r/sites/NIAID-NCATSCollaboration/Shared%20Documents/Hedwig%20V2/Sample%2016bit%20Files?csf=1&web=1&e=JO3RWJ
The text was updated successfully, but these errors were encountered: