Especially recommended for iTelescope.net members for more compatibility with iTelescope.net calibrated data.
Astro Pixel Processor and iTelescope.net celebrate a new Partnership!
Annoying grid in final integration
I am trying to figure out what I am doing wrong. I have run multiple integration session by now an every time I see an annoying grid popping up in PI. I forced RGGB and different integration settings including now a "as is" session without using bias or dark frames.
Integration 4+ hours via 600 sec subs via ZWO ASI071MC
Please help? What am I doing possibly wrong?
UHC-S lights (RGB/OSC), Ha (via same OSC) and initially Darks and Bias files.
Initially I started with the defaults for multi-channel / filter processing.
Shown picture was a "St-avg-19800.0s-NR-x_2.0_1.0_dr-hat-full-eq-add-sc_BWMV_nor-AAD-RL-noMBB-Ha_UHC-S_4thLNC_it3" but UHC-S and Ha "as is" have the same grid phenomenon.
Regarding "PI", this was only used to do a quick check via the autostretch function.
AvisFS Fit viewer shows...
JUST TO BE SURE (so I can cancel one issue out), for this ZWO ASI071MC (latest version APP) I should "force debayer" (RGGB in my case) right???
Max upload file size 30MB... my subs are 31MB per sub.
You can upload the data to our server. Log in with appuser as the username and password. Please create a folder with your name on it first. Will that work for you?
Not sure, I would say APP should recognize this camera so leaving it at default settings should work. MC is color already so if it doesn't do this automatically and comes out gray, you need to enable "force CFA" and select the correct pattern.
So I downloaded 2 files (as a start), I think you need to give it these settings for the H-alpha;
Then the mosaic pattern vanishes. APP indeed doesn't recognize it as having a bayer pattern.
Sorry to Piggyback on this thread, but I just wanted to chime in and say that APP also doesn't recognise my Qhy163c properly either. I have to check the 'Force Bayer CFA' box as well, and then choose the BGGR pattern (as supported doesn't work).
It would be great if a future release would fix this, so I don't have to 'forget' to do it every time 😅
Vincent can you tag Mabula to add this as a fix please?
@xiga Did you verify that the FITS file contains a property for the Bayer matrix to apply? If that property isn't there then APP (or any other application for that matter) cannot know the Bayer matrix to apply.
Yes, that's what I meant. 😉 APP doesn't know what to do if that name isn't given.