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
I have been using my QSI640 CCD camera and APP for years.
My camera doesn't produce any kind of "blooming" in the stars, but now, using APP V1.083.2 MacOS, I have an artifact in some of the stars that is similar to "blooming" (only 3 or 4 stars in the whole field, and they are not brilliant stars).
I am using the same parameters with APP since years ago, and this is the first time this happen to me. My individual frames doesn't have this artifact, it only appears when I use the integration with APP.
Do you know what can be happening?
I attach an example
Regards
Jose
I have tried with old versions of APP (V.1.082 and V.1.079) and the star blooming also appears, so it is not related to the version of APP.
This is incredible, it is the first time that happens to me. I have already seen all my individual frames and the blooming is not there, I have no idea about what is happening.
And it only appears with 3 or 4 stars, look at my attached files:
Dear Jose,
That is a strange artefact indeed. It looks to me like something of a "glitch" with the sensor, blooming would be something all around the star. However, if it's not in the subs, then that is strange as well. Could you upload like 10 lights and your master calibration frames to our server for analysis?
First of all, thank you very much for your help.
I have already uploaded my masters, lights and the integration result in the folder "skysurvey-starBloomArtefact"
Definitely these artifacts are not a "glitch" of my CCD camera, because as I have already said, they are not in the individual frames, but what is more, I have processed another set of lights from the same night (29th-30th January 2022_Leo Triplet) and the result is completely clean, there are not any artifacts in that integration. This only happen with my Cone nebula (29th-30th January 2022_Cone nebula).
Looking forward to hearing from you
Regards
Jose
Yes indeed, like I said, it's how it looks like. But if it's not in the subs, that seems unlikely. I'll have a look at the data, please allow for up to a day.
Or just for up to an hour. 😉 I analyzed the data and it's caused by the BPM! This is really odd and I've notified Mabula immediately as, to my knowledge, a BPM should never have a negative influence on data. Thanks a lot for sharing! If you leave out the creation of the BPM it should work.
Yeeeees, you are right, it's the BPM, in fact if you change the BPM parameters, the size of the artifacts also changes.
Incredible, it's the first time I see this, and I have processed a lot of photos.
If you find out something else about this, let me know, please
Regards
Jose
Will do for sure!
You might get rid of it changing the automatic parameters with manual ones, like I think you already tried. Still, first time I've seen it. 😉
In the end I have processed my Cone nebula photo changing my usual BPM parameters (hot pixels kappa=4.0), and I haven't had any problem.
Anyway it is really strange because it is the only time I have had problems using the BPM in APP.
Here you have my result; I haven't touched the stars:
https://www.flickr.com/photos/jachimeno/51964411145/in/dateposted-public/
Regards
Jose
Great and thanks for letting us know, we have the data and Mabula will look at it as to why it did that. Might be that we can improve the algorithm there, but it is indeed rare.
