I've just commenced on the long journey of learning how to drive PI.
I have a range of questions - which I may bore everyone with at some stages.
For starters, I have an odd experience.
Raw images when displayed in PI have a dark spot near the centre of all bright stars. In especially bright stars, this covers up to a third of the star.
I had thought it was a result of the minimum/maximum clipping process when calibrating images but its there in uncalibrated images too.
This is very odd - I haven't seen this with Maxim.
I'm using Maxim to capture from a couple of cameras (one KAF8300 based like your QSI) and the processing in PI I have never seen that.
Rick
can I ask you to check something for me please? If you open an image you have taken in Maxim that displays normally in PI and open the FITS header, can you tell me what you have recorded for the BZERO field.
Recently, I changed my default setting in Maxim to Save Date in Unsigned Format. I did this as the PI forums suggested that saving the data in signed format sets the range of ADU from 32768 to 65,000. This in turn causes dramas for flat fields.
Looking at my images, the unsigned setting results in this odd appearance while the signed data looks fine.
My FITS files have BZERO=32768.0 and BSCALE=1.0 which means the data values are interpreted as unsigned 16-bit integers. I do not have the "Save Data in Unsigned Format" box ticked in Maxim. It seems do something other than what you'd expect...
You should be able to edit the FITS headers in your files to correct them. I think the data should be fine.
My FITS files have BZERO=32768.0 and BSCALE=1.0 which means the data values are interpreted as unsigned 16-bit integers. I do not have the "Save Data in Unsigned Format" box ticked in Maxim. It seems do something other than what you'd expect...
Cheers,
Rick.
Mmmmmmm - thats very helpful Rick. Thanks
Do you calibrate in PI?
I've been using the Batch Preprocessing script and can't get rid of a heavy gradient in blue. I had hoped that the signed/unsigned switch would do the trick.
I've been using the Batch Preprocessing script and can't get rid of a heavy gradient in blue. I had hoped that the signed/unsigned switch would do the trick.
When I first started using PI, I used to calibrate in Maxim. After that, I switched to calibrating in PI using ImageCalibration and ImageIntegration. These days I calibrate in PI using BPP.
I've not had problems with gradients apart from the usual ones from imaging under light polluted skies...
If so, when you open your stacked LRGB files three windows will open. The bottom window (first to open) is the one with all your data in it, the other two are the high and low pass rejected data.
I don't know what what constitutes as cutoff data for either low or high passes, but it should be in the post processing area somewhere, i believe it is the Sigma Low and Sigma High values under Image Integration (under Lights).
Mine are set to 4.00 and 3.00 respectively.
Maybe check them and make sure the values arn't funky.
I have seen something similar on my shots using PI to stack. I then ran the data through DSS to stack and it was fine
Pete is having the problem with unstacked raw subs. Looks like Maxim with the "Save Data in Unsigned Format" option enabled writes the data in unsigned 16-bit but doesn't set BZERO in the FITS header as other applications would expect (the Maxim help file vaguely alludes to this).
PI thinks the data is 16-bit signed and so the values in the brighter areas of the image (with the most significant bit set) look like negative numbers and hence stars have dark cores.
I've noticed all sorts of weird stuff happen when you transfer FITS files between different image processing apps. The PI guys argue, usually convincingly, that they are right and everybody else is wrong The basic problem is that the FITS file standards aren't complete and there is freedom to interpret them in different ways.
One example is the coordinate origin of images. I think that Maxim and CCDStack assume an upper left corner origin. PI defaults to lower left corner, but you can change this in the FITS Format preferences.
A bigger problem is that the FITS standard doesn't specify the black and white points for floating point values. PI assumes a black point of 0 and a white point of 1 but other apps use different ranges. Once again, PI lets you change this if you need to.
There is a situation that I haven't been able to determine why, where MaximDL will automatically save a Screen Stretched image. Opening it in PI will give a completely overstretched image right down to the black star centres exactly like yours. If you take the image back to Maxim, open the screen stretch box, adjust the pointers to zero and maximum values, ie. unstretch it, and save it, PI will treat it as normal.
There is a situation that I haven't been able to determine why, where MaximDL will automatically save a Screen Stretched image. Opening it in PI will give a completely overstretched image right down to the black star centres exactly like yours. If you take the image back to Maxim, open the screen stretch box, adjust the pointers to zero and maximum values, ie. unstretch it, and save it, PI will treat it as normal.