It did take a long time to have the work finished on this and it will have a major performance boost of 30-50% over 2.0.0-beta39 from calibration to integration. We extensively optimized many critical parts of APP. All has been tested to guarantee correct optimizations. Drizzle and image resampling is much faster for instance, those modules have been completely rewritten. Much less memory usage. LNC 2.0 will be released which works much better and faster than LNC in it's current state. And more, all will be added to the release notes in the coming weeks...
Update on the 2.0.0 release & the full manual
We are getting close to the 2.0.0 stable release and the full manual. The manual will soon become available on the website and also in PDF format. Both versions will be identical and once released, will start to follow the APP release cycle and thus will stay up-to-date to the latest APP version.
Once 2.0.0 is released, the price for APP will increase. Owner's license holders will not need to pay an upgrade fee to use 2.0.0, neither do Renter's license holders.
I've been trying to integrate some images from last year with images from this year of a galaxy M100. I've always used the same camera and telescope but sometimes change between light pollution filters. After adding all corresponding Light, Flat DarkFlat, and Dark frames I'm currently getting a blank black screen with no data after integration. I've tried stacking multiple times but with no luck. When I integrate data from two consecutive nights on other targets it does integrate successfully. I'm running the latest version of AstroPixel Processor version 1.079. Here's a screenshot of APP right after integration.
I strongly suspect that something has gone badly wrong during your integration.  I think it strange/very wrong that in the FITS header all the background and dispersion fields are showing zero values while all the noise reduction fields are showing Infinity values!  I am not a statistician but to get an infinity level of noise reduction I think every pixel would have to have the same value, eg zero / black, which is what you seem to be seeing in the viewer.  The only way to get such a result that I can think of is if your calibration frames exactly matched your lights such that the calibrated light was entirely smooth.
I guess if you repeat your processing and end up with the same result then APP or your data has a fault.  If it works OK then maybe it is a user error or some transient fault.
Mike
Â
This post was modified 6 years ago 4 times by mestutters
Thanks for the prompt reply. Unfortunately, I tried integrating the files 3 times and final integration remains blank/ black screen. The histogram shows that it appears to have almost no data. However, when I inspect all lights and calibration frames, they appear to be in good order. Most settings in APP are set on automatic.
Any other thought about what this could be? Would it be possible I can upload the files for someone to test/verify?
I guess Mabula will need to take a look but to make progress in the meantime you might wish to try processing your lights from last year separately from your latest lights.  You can then combine the two sets of results by reloading the channel integrations as lights and running through the APP workflow once again.
Maybe while doing this, one set of lights may show this blank integration problem which would help narrow down the problem area.
Mmm, yes this is difficult to analyze like this. Would you be able to upload the files that are causing this issue? You can send them to our server and use login/password: appuser. Please create a directory named "javrolijk-blackintegration".
Working on it now. What strikes me already are the darkflats of 5.53 seconds, the signal isn't there. While the 8.25 seconds does produce a nice bias-noise pattern.
So I've left out the darkflats, seems they may be the cause somehow. Not sure why, but given the strange 5.53 seconds data, something during capturing or processing via the software you used...? The following I got as a result, combining both sessions; The flats might also be a bit ineffective, so those might need improvement.
So I've left out the darkflats, seems they may be the cause somehow. Not sure why, but given the strange 5.53 seconds data, something during capturing or processing via the software you used...? The following I got as a result, combining both sessions; The flats might also be a bit ineffective, so those might need improvement.
Vincent,
Many thanks for the support you've provided. I'll verify my flats and darkflats during another session.
@javrolijk I've just had this very issue this morning after stacking lights, darks, flats and dark flats. Never happened before. Will look at leaving the dark flats out and see what happens
I'm also experiencing this same issue. ZWO ASI071MC Pro. Removing the darks allow the final stacked image to appear, but at the sacrifice of having no darks applied. My darks and lights have the same gain and offset.
