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.
I ran an integration on C/2017 K2 yesterday and the result was not what I expected. Sort of the obverse of deep sky stacker's "register stars and register comet" mode, APP produced L, R, G, and B integrations with both the stars and the comet trailed!
I am reasonably sure that this is due to how I interleaved the exposures. Not wanting to end up with big time offsets between the various channels, I had it swap filters with every sub, so the data comprised endless repeats of LRLGLB. When APP prompted me about using timestamp metadata, I clicked "Yes", so the file list window sorted by time, interleaving the channels exactly as shot. I had to click on just about every frame to register the comet -- no big whoop, really. But when I was done I had four streaky integrations.
I tried again, unchecking everything but 14 of the luminance frames, and the comet looks just fine. For that I wound up having to click on about every other frame to register (I clicked "Yes" for "use metadata timestamp" again).
I'm not complaining, or even sure that this is a bug -- it might just be that using timestamp metadata is the wrong choice for this situation. It is, I suppose, somewhat less convenient to select the frames and do the registration four times instead of one. This is more of a "Hmm, interesting behavior" sort of message.
Â
Â
BTW I ran it again, loading only one channel. With timestamp metadata on, I get streaks, without, I get a comet. This is with 2.0.0-beta2.
Hi Rick @rickwayne,
Thank you very much for reporting this behaviour 😉
It sounds like APP is having difficulties on your comet data to detect the comet properly... probably best if i can have a look at your dataset to see what happens exactly and why... and then properly fix it if needed 😉
Can you upload the dataset here?
https://upload.astropixelprocessor.com/
username: upload
password: upload
Please make a folder like RickWayne-Comet-issue and let me know once uploaded 😉
Mabula
OK, done. RickWayneStreakyComet.
Thanks!
