15th Feb 2024: Astro Pixel Processor 2.0.0-beta29 released - macOS native File Chooser, macOS CMD-Q fixed, read-only Fits on network fixed and other bug fixes
7th December 2023: added payment option Alipay to purchase Astro Pixel Processor from China, Hong Kong, Macau, Taiwan, Korea, Japan and other countries where Alipay is used.
Hello
i have started using APP and love it. My question is using data shot over several nights. I can not seem to understand how i can know which files are the master darks/bias/flats/lights.
Now i add all the lights/darks etc for each night in session 1, 2 ,3..
This takes up alot of processing time. Am i not able to take the master files from 1,2,3 and when i add 4 (lights, darks, etc) to it so the total amount of images are 3 (masters) and not 100plus.
Any help would be great
So, darks don't have to be taken each night. You can just load them all together and create a master-dark and BPM. Bias, same thing, load those and create a master-bias.
Then I would clear the data and start loading in the sessions and the flats for those sessions. Load in the masters you created and you should be fine. It is also possible to do this all at once, but to keep it simple for now try the above.
ok, i think i got it, I still need to load all my light frames for each session. there is no master light.
No, the "master light" would be the end-result, the integration. To get that, you first need to calibrate all those lights with the master calibration frames.
I have a followup question, I recently did a multi night session as well, and I have a rotator. I made a mistake and didn't load my previous night image into NINA for proper alignment and plate solve. The bottom of the image just seems a little bit off, I'm curious if this is just a staking artifact, or if not, is there a best practices to get them to align. I'm also planning on adding more HA Data, but I'll remember to load a previous image to get the right angle and plate solve solution.
@thextra10th All the edges are a bit off. This is caused by dithering or by drift of the telescope during imaging. Both introduce slight offsets of the frames with respect to each other and the edges show where less data was added. Normally you crop the images just at or slightly inside those edges to get rid of them. This is completely normal and expected behavior.
@wvreeven ok, thank you I new I could crop, and I do dither, but because I forgot to load a previous nights image into nina ( even though I saved the sequence with target position information) I though I messed up a little bit. Thank you and have a great day
