Hi-I have been trying to upload some of my own images-taken with ZWO 183 mono, G filter and calibrated in pixinsight-the files are 80MB and when I use the wizard I keep getting the message “you can’t upload files of this type”. I modified the TELESCOP name in the FITS header to match my aavso telescope name, and modified the FILTER name to “G”, but it hasn’t made any difference. not sure where to go from here.
Are they to big? You could try binning 4x4 while imaging to see if that fits.
Ray
That file size looks unusually large for a 5496×3672 camera. I wonder if Pixinsight is doing something strange. What is the file size when it comes from the came before processing?
The file size should be around 40MB for a 16-bit FITS image.
Beware of PixInsight - instead of giving an 16-bit integer, it will have destroyed the data by converting it to 32-bit floating point AND crushing it to 0.0 and 1.0 , instead of using the 65536 range which can be represented in 32-bit floating point without data loss.
When it converts to 32-bit floating point, it doubles the file size.
Work with some other software (I’m biased as I use MaxIm DL Pro and work for the company), but anything else should give you a proper 16-bit integer image.
Good luck,
Colin
1 Like
the raw files are binned 1x1 which for this camera are supposed to be 12 bit; I tried uploading the raw file (40MB) through the wizard, and the same error message was generated even though the drop box confirmed a 40MB size. Additionally I tried compressing the processed file (which the drop box confirmed to be 80MB) to a 40MB zip file and the wizard wouldn’t upload that either. If the limit on uploads is 100MB size I’ve been assuming these would be small enough.
Wondering if cropping the files would help?
Anyway thanks for the input.
Do you have the ORIGINAL light frame from whatever software acquired the image?
Usually these made-in-China cameras fake the data into a 4 bit shifted image from 12 bit to 16-bit format. So it will be 16-bit, however multiplied by 16 so it looks like max pixel value is 65535 instead of 4096. FITS normally uses 16-bit. ASCOM normally uses 16-bit. So your file size should be approximately H x V x 2 bytes for 16-bit and some header data.
Yes-that actually worked; I previously had tried to upload the raw images from a thumb drive and the wizard would not allow that. Not sure why that is, but they all went in fine after they were saved to my desktop.
Now will have to work on getting them calibrated via another method, it seems. Thanks!