Black Friday & Cyber Monday Sales on Renter's & Owner's licenses - sale will end on the 1st of December 2020 at 12:00 UTC
16 November 2020 - Wouter van Reeven has officially joined the Astro Pixel Processor Team as a moderator on our forum, welcome Wouter 🙂 !
30 July 2020 - APP 1.083-beta1 has been released introducing Comet processing! This 1st beta has comet registration. The stable release will also include special comet integration modes.
9 July 2020 - New and updated video tutorial using APP 1.081: Complete LRGB Tutorial of NGC292, The Small Magellanic Cloud by Christian Sasse (iTelescope.net) and Mabula Haverkamp
2019 September: Astro Pixel Processor and iTelescope.net celebrate a new Partnership!
Posibility to define when frames will be rejected wthout stopping process
I would like to know and/or suggest wether it would be possible to (pre)define when
the to be processed images will be rejected. ( ej. if analisis fails and or if starcount less
then and or ..... )
I mean to say that if in the process somewhere a frame will be halting the workflow
with an error message, this frame ( or frames ) will be thrown out of the selection and
the process will continue.
This ( when you put in a lot of frames ) would enable the integration to continue
without the worst frames and not halt with an error message.
Just an idea maybe??
Yes that may be an interesting way to make that part easier indeed, I'll discuss it with Mabula. If you right-click on the analysed list, you can sort it, I think something like "best to worse" will group them on 1 end of the list.. might already make it easier now.
If that would be interesting, then: when frames are rejected due to their quality and/or
other criteria, then it would not make sense to also register these rejected frames, normalize these
rejected frames etc.
For example when I configure in Integration to integrate ie. 500 out of 2000 frames then
I'd like to see that only 500 / 2000 will be registered after analizing, 500/2000 normalized etc.
That will greatly speedup this kind of processing ( at the moment I am using an ASI224MC
to capture frames of 0,5 to 2 seconds, and many of them )
I hope this makes sense!
Thanks for your feedback!
In the next version there is at least a way to skip steps. So when you register or normalize frames, you can save them and next time tell APP to skip the previous steps so it doesn’t perform jobs twice. So slowly Mabula is integrating more flexibility in the workflow and your (and others) suggestions will be taken into account. Thanks for posting!
I think the issue for registering only 500 etc, is that APP has no idea which 500 are the best to do that on. The separate steps give APP a good idea of the quality of the data.
Going through all of these steps, it seems as if analizing the stars is the step
where the most relevant information is obtained to reject frames or not.
That is to say, if I analyze a bunch of frames ( like 1000 or 2000 ), in the resulting
list with quality estimation etc. I sort on quality or starshape or whatever, then
according to my criteria I select those frames that have to go out.
Then with right button I deselect these frames and push the clear button in the load
Then the not wanted frames are deleted from the framelist and I can continue.
So, my interest woud be to be able to pre-define some criteria in order to
automatically eliminate the frames analized from the list that son't comply my criteria.
Not sure if I explain myself, but evenso, I hope to see more options implemented to
make APP even more complete!
Thanks for your patience with me 🙂
I was about to create my own RFC for this when I saw it - yes this is a helpful idea. With the huge file sizes of my ASI2600 I now like to set a long integration running (maybe 2-400 frames) and then come back o refine the processing a second time (delete really bad frames, set rejection criteria etc) before doing a second integration run for my "final" image.
I would love APP to be able to "deselect registration errors" on files (the code logic would look something like:
if ignore_reg_errors && registration_failed=true then
keep processing like normal"
Yeah it might be interesting as a setting maybe, I've asked Mabula his thoughts on it.
edit: And had some feedback. Basically it's not something you would have to do, if you stack along the bad frames with the quality integration setting, those frames will have almost no impact (if they are limited in number) but do contribute in reducing the overall noise. If you still want to inspect, you can do so by sorting on quality yourself in the list, making a graph even if you want and then remove those (sorting makes it pretty fast to identify anyway).
Thank you Vincent, the pointreally is to be able to define what you
want to inlcude into the integration and what not!
At the moment the whole process will stop if there are some bad frames
between the rest ( which can be many frames! ).
If you walk away you loose a lot of time where the process would have been
able to continue without these frames.
That is why I ask for this option!