2023-03-15: APP 2.0.0-beta14 has been released !
IMPROVED FRAME LIST, sorting on column header click and you can move the columns now which will be preserved between restarts.
We are very close now to releasing APP 2.0.0 stable with a complete printable manual...
Astro Pixel Processor Windows 64-bit
Astro Pixel Processor macOS Intel 64-bit
Astro Pixel Processor macOS Apple M Silicon 64-bit
Astro Pixel Processor Linux DEB 64-bit
Astro Pixel Processor Linux RPM 64-bit
Hello,
please have a look. I calibrated as usual, cmos 6200mm same temp, same gain, same offset for all calibration frames and get ok for Ha, but not for red:
uncalibrated:
calibrated:
Ha looks normal, Red absolutlely not, easily seen.
any ideas?
this is how the flats look like:
the stretch on red seem very strong...
the exposure times on the flats are for red 0,2 secs, Ha ca. 3 sec (done by autoflat aid in APT)
could this cause that?
stefan
22 hours and no ideas here, ok...
since I had 2 days lost due to this before I continue, since pixinsight worked on it with all calibrationframes without any problem!
I suppose the "again - error" in APT claimming my mono files are RGGB written in the files header could have caused this, for this was the only thing I set in the WBP scripts in PI to mono my hand. If this is so, someone should have a look into it in APP, for a hint in the header should not be able to destroy the entire stack, should it?
e.
APP does look at the header to determine what the files are, if the header provides the wrong information then APP will do the wrong thing, this then should be fixed at the data acquisition stage indeed.
APP does look at the header to determine what the files are, if the header provides the wrong information then APP will do the wrong thing, this then should be fixed at the data acquisition stage indeed.
That is one option, yet not the most customer friendly. Taking a look at Pixinsight's Weighted Batch Preprocessing
tool shows that there are better options for cases where a lot of data like this happens to exist. Instead of having to convert each single frame - and with the Masters it even did not work- and wasting lots of time and nerves one just pushes a buttom and it works in WBPP. Your response does not help here at all, does it only state the plain obvious
Well the issue originates from somewhere else, so of course it doesn't help in APP itself. We can try to accommodate that, but usually we try to contact the other developer that can issue a fix. I will discuss this with Mabula though.
Well the issue originates from somewhere else, so of course it doesn't help in APP itself. We can try to accommodate that, but usually we try to contact the other developer that can issue a fix. I will discuss this with Mabula though.
That will not change anything. Note what I said above and the cause is also not clear, since an old version of APT was used for certain reasons on an old pc for other reasons. I bet there is a reason why in Pixinsight you can easily set it. For transparency. So that you see if someting is wrong, no matter why (!). You seem to be a bit selfreferential. Try to see the needs of the customer first and maybe a bit faster - and not that point of view of APP-developers...
