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.
Hello,
if I'm lucky tomorrow I'll be able to capture comet C/2017 K2 as it passes M10. Can I also capture here with a mono in RGB, and then stack that? Since the comet is moving, I have concerns here. I have only ever captured comets with an OSC. So it would be the first time with a mono.
In such a case, does it make sense to always record in R, G, B, R, G, B, R, G, B, etc.? Usually I always record several shots from one filter, but here I would have to switch through the RGB filters, wouldn't I?
Or can I easily take 10 x 60 sec. red, 10 x 60 sec. green, 10 x 60 sec. blue?
Or better 1 x 60 sec. red, 1 x 60 sec. green, 1 x 60 sec. blue and start again?
What makes sense here so that APP gets a good image from all the data?
Thank you!
I think that's possible, however it will depend on the relative movement the comet has in your FOV. That will dictate how much it moves in between shots. If you're able to calculate that speed (or if it's known) and calculate how fast it moves over your pixels, it can tell you if that's possible or that you get misalignment on the comet itself. Wouter has notified Mabula so if he answers he may have some idea about it as well.
I tried to shoot comet c/2022 E3 ZTF in mono last night. I registered them in the comet mode. However I can not normalize the LRGB files so I can't open them in combine RGB. Is there a solution?
