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 am really unsure what this is from, and the only thing I could think of is having the offset wrong. Somehow, I shot a few frames at offset of 1, instead of 50. However, the same gain was used. This is the only difference. What is worse, is that this is 27 hours worth of data, which could be pointless now.
Is there any way I can resolve this? Each image can open up individually, no problem.
Here is an image(sorry for the bad quality, I should have done a screenshot.
You shouldn't change offsets, it's something you can play around with of course, but usually a sensor has its own offset that people like to use (many times this information can be found online). Pick a nice offset (it depends, but usually I see them at 40-50) and stick with that for all exposures of your sensor. If you have images with a different offset, you need calibration files with that same offset as well. An offset of 1 is not ok though, that will likely have a huge amount black pixels and black pixels (meaning no signal at all) can never be properly calibrated.
@vincent-mod
Yeah huge mistake on my part. For osme reason my program reset and I had not even noticed that it chnaged the offset value. Is there a way I can see the offset value in APP to remove those frames??
It's usually (if your capture program added that information) found in the Fits header. If you load your image, you can look at the console window (on the left of the image window with the very small arrows). It's not mentioned in the table unfortunately.
ps. I would advice to remove those from the list, but never delete them just in case. 😉
Would it be possible to have this dialog generate a sound? Same as when an integration finishes? Nice feature when integrations that can take hours are interrupted.
I just walked away from a 500+ frame integration, only to come back two hours later to find it had stopped early on in the "Analyze Stars" step because of this dialog. Be nice to know earlier if there's a problem. Maybe a different sound for success vs. problem. But the same "I'm done" bell would be fine also.
Thanks.
Would it be possible to have this dialog generate a sound? Same as when an integration finishes? Nice feature when integrations that can take hours are interrupted.
I just walked away from a 500+ frame integration, only to come back two hours later to find it had stopped early on in the "Analyze Stars" step because of this dialog. Be nice to know earlier if there's a problem. Maybe a different sound for success vs. problem. But the same "I'm done" bell would be fine also.
Thanks.
Hi @timshea,
Thank you very much for your suggestion. We will add an option to the CFG menu that enables you to choose between APP stopping or continuing when encountering problems. I have added here that it should make a sound when stopping 😉
Mabula
Hi all,
APP 2.0.0-beta35 has a new option called Continue on ERRORS without warnings, please check it out:
- IMPROVED continue on ERRORS without warnings
We have added a new option to the LICENSE & SETTINGS menu called continue on ERRORS without warnings. If you enable this, APP will continue processing despite possible errors on some of the light frames after steps 3) Analyse Stars, 4) Register or 5) Normalize. For instance, if you load light frames and would directly go to 6) INTEGRATE and click on integrate, APP would simply continue processing despite possible errors and it would produce an integrated result of your light frames from the frames that actually pass the steps 3), 4) and 5) without errors. Please note, the errors in this case mean regular data problems that prevent APP from processing your data normally and successfully. If an actual bug in our code occurs, APP will still stop and report the bug to the user. Please see the below screenshots, it shows the new setting in the LICENSE & SETTINGS menu, and the warning messages after 3) Analyse Stars, 4) Register or 5) Normalize will show information about this setting in the warning message, so the user can disable it if so wished.
@mabula-admin I've been away from the forums for a while due to illness, but I'm back now & wanted to say thank you for responding! I love Astro Pixel Processor, and recommend it frequently.
