UPDATE FROM MABULA
I have had a very rough 2 months unfortunately health wise. I was struck 3x in a row with bacterial infections. The second infection occurred after a routine hospital checkup and I became very sick. I had to rest and take a lot of antibiotics. Once I was recovering and restarting work 1 month ago, I again became sick. The infection was not yet gone, so even more antibiotics and rest was needed. Needless to say, it took a lot of my energy and I needed a lot of rest.
Finally, the infection is really gone and my energy is coming back step-by-step now and I have started work again. I am terribly sorry to have kept you waiting for support. I will address all outstanding questions and e-mails step-by step and will be on the forum daily from today.
APP 2.0.0-beta47 will come soon as well, a lot of work was already completed before I became very ill, so the release is also nearly ready for you. Beta47 will be much faster actually. Many workflows will be more than 2x faster, mosaics can even be 10x faster than before because registration really received a major boost... all compared to beta46. Before I release it, I will make sure that everything is working properly and then I will release it.
Hi all (and Mabula @mabula-admin)
The recommendation is to generate >20 darks of 600 sec at room temperature (see here).
I had to replace my camera after a defect, and have now sessions of 2 different cameras, but exact same type, so the FIT-Header show the same equipment tag. The cameras are ZWO ASI2600MC, so modern Sony sensors.
I want to integrate the sessions in one run, so not the 2 stage approach.
- Is it possible to assign individual BPMs to the sessions? I don’t find a possibility to do this.
- What is better: assign no BPM and let APP generate the BPM for this integration from the sessions‘ darks? I have master darks (of 40 darks) per session and dither every 2nd frame. I have ca. 40-80 frames per session. (And flats and master bias)
- Or generate one BPM from darks of both cameras? This probably eliminates too many bad pixels?!
- Or must I do a 2 stage integration?
Thank you and best regards.
Michael
Hi all, hi Mabula.
I tested a lot, measured the linear APP stacks in PixInsight (FWHM, Eccentricity and stars) and came to the following conclusion:
- Note: I need / want to integrate in one step, because I drizzle and want to have all dither positions in the integration.
- For two different cameras, it is best to disable BPM (in 2) Calibrate), and still use Integrate „automatic“ in 6) Integrate
Compared to stacking with „on the fly generated BPM“ (from the Darks of the sessions)
- FWHM is equal to slightly better with disabled BPM
- Eccentricity is slightly better
- Number of stars is significantly higher (3% on M13, M31, 20% on M27)
SNR and MAD is not comparable, if stacking/rejection is so different. But both indicate excellent stacks (I was in La Palma 😉
I checked also the rejection maps ... look good. - My setup and acquisition:
- OSC camera (ASI2600MC Air)
>100 frames, and dither every 2nd frame
- good Master Darks (50 frames), plus Master Bias and Master Flats - With less frames, and less or no dither ... your mileage may vary.
Addendum: I tested also for sessions of the exact same camera ... and even here disabled BPM results in slightly cleaner stacks.
@mabula-admin Do you see flaws in this analysis?
Best regards.
Michael
