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 normally use another program for stacking/calibration but thought I'd give App a go but I get a warning the the fits file seems to be corrupt or incomplete, it does load in the other program though.
APP uses the latest version of the NASA nom.tam.fits java library.
If APP indicates that the fits file is corrupt or incomplete, it will mean that these fits frames aren't correctly created according to NASA Fits conventions.
I know that files from Nebulosity for instance are badly created and could give these errors. I have reported this to the NASA developers of the library to see if we can fix these errors as soon as possible.
Can you share the source of your fits files? Which capture program or camera software? If you could send me a couple (wetransfer, dropbox,..), I can send them to NASA to have a look as well.
Both load fine on my system. (windows 7 pro, intel icore 930, 18GB mem)
Maybe, the error is not directly related to FITS reading, but relates to Operating System reading of the fits files. Are these files read from an external device for instance?
Maybe it's best if you can share your Operating System, hardware (cpu cores, memory) and details of the harddisk partition on which these files reside?
In the mean time, I shall do some more testing on MacOS & Linux as well.
In 6) INTEGRATE, set the composition model to "full" if you haven't done so already. Most likely this is the cause of the problem. Let me know if it runs then 😉
(in the next APP version, full composition mode will be forced with a mosaic).
Well I have been having a few problems with the pc lately so probably that could be the cause. Not a problem as I can stack elsewhere.
Â
Â
Â
Maybe it's still usefull for me to know your system configuration. Can you share your OS, CPUs, memory and the filesystem (NTFS, exFAT...) of the partition on which the files are that gave problems?
I can't get past the (4)register step, as thats where the error is.
Okay, share with me the settings in 3) and 4) that you currently have and I'll give you recommendations on the settings.
I understand you are trying to make a mosaic, it's important to have enough stars detected in 3) and set registration mode to mosaic in 4) combined with enabling dynamic distortion correction.
depending on the amount of overlap between the frames, you need to increase the scale stop. For only 10% it needs be at least 10, for 15% overlap most of the times 8 is enough. So less overlap is higher scale stop.
Hi Tony, have you adjusted the amount of memory APP can use?
You can let APP use more memory with the Top Left CFG button. The out of memory is probably due to APP only using 2GB while trying to make a big mosaic...
How much RAM memory do you have and how big is the mosaic?Â
Well I have been having a few problems with the pc lately so probably that could be the cause. Not a problem as I can stack elsewhere.
Â
Â
Â
Maybe it's still usefull for me to know your system configuration. Can you share your OS, CPUs, memory and the filesystem (NTFS, exFAT...) of the partition on which the files are that gave problems?
Hi Tony, have you adjusted the amount of memory APP can use?
You can let APP use more memory with the Top Left CFG button. The out of memory is probably due to APP only using 2GB while trying to make a big mosaic...
How much RAM memory do you have and how big is the mosaic?Â
Hi Tony, have you adjusted the amount of memory APP can use?
You can let APP use more memory with the Top Left CFG button. The out of memory is probably due to APP only using 2GB while trying to make a big mosaic...
How much RAM memory do you have and how big is the mosaic?Â
ah ok, will look. 8gbram and its 4 panels.
Â
Ok, let APP use 6-7GB. The next time you start APP it can use this amount and will remember this setting. So restart APP to apply it.
Was having trouble getting all 4 panels to register because when I went into integration it was only showing that I had 2 lights to stack, but I changed the pattern recognition to triangles and it seems to have worked.
Hi Tony, have you adjusted the amount of memory APP can use?
You can let APP use more memory with the Top Left CFG button. The out of memory is probably due to APP only using 2GB while trying to make a big mosaic...
How much RAM memory do you have and how big is the mosaic?Â
ah ok, will look. 8gbram and its 4 panels.
Â
Ok, let APP use 6-7GB. The next time you start APP it can use this amount and will remember this setting. So restart APP to apply it.
Was having trouble getting all 4 panels to register because when I went into integration it was only showing that I had 2 lights to stack, but I changed the pattern recognition to triangles and it seems to have worked.
That should mean you have quite a low star count after 3) analyse stars. You can try to increase this by lowering the detect above noise kappa 😉 and increasing the limit of numbers of stars.
Did you use any form of distortion correction in PI?
If so, this could well be the cause, PI uses thin plates for distortion correction and this will actually do more harm than good for the geometrics of your data. So you will need to recreate these panels in APP if you still have the original calibrated frames.
If you didn't use distortion correction in PI, it could be usefull if I can have a peek at the panels? Possibly do some testing to verify why it fails. One reason could be severe coma in the corners of your frames?
How much stars are counted in the panels? And how many star pairs are found in the registration? This is shown in the registration RMS column at the bottom.
Did you use any form of distortion correction in PI?
If so, this could well be the cause, PI uses thin plates for distortion correction and this will actually do more harm than good for the geometrics of your data. So you will need to recreate these panels in APP if you still have the original calibrated frames.
If you didn't use distortion correction in PI, it could be usefull if I can have a peek at the panels? Possibly do some testing to verify why it fails. One reason could be severe coma in the corners of your frames?
How much stars are counted in the panels? And how many star pairs are found in the registration? This is shown in the registration RMS column at the bottom.
(If you can, recreate the panels in APP)
Kind regards,
Mabula
Will look when home later, but as for coma in the corners the swirly bit in the mosaic is nowhere near any corner, but I have finished the mosaic now without errors.
And I can't stack in app as it doesnt read my fits headers, as mentioned in another post.
Did you use any form of distortion correction in PI?
If so, this could well be the cause, PI uses thin plates for distortion correction and this will actually do more harm than good for the geometrics of your data. So you will need to recreate these panels in APP if you still have the original calibrated frames.
If you didn't use distortion correction in PI, it could be usefull if I can have a peek at the panels? Possibly do some testing to verify why it fails. One reason could be severe coma in the corners of your frames?
How much stars are counted in the panels? And how many star pairs are found in the registration? This is shown in the registration RMS column at the bottom.
(If you can, recreate the panels in APP)
Kind regards,
Mabula
Will look when home later, but as for coma in the corners the swirly bit in the mosaic is nowhere near any corner, but I have finished the mosaic now without errors.
And I can't stack in app as it doesnt read my fits headers, as mentioned in another post.
Hi Tony,
Yes, the swirly bit was probably due to unstable distortion correction due to a low star count.
Regarding your FITS problem, I can't reproduce it, but I am in direct contact with the FITS library developers (from NASA) and I will deliver the next version of APP with an updated FITS library. I can't guarantee at the moment that this will solve the problem on your system, but it might.
I'll be uploading the new installers probably tomorrow.
![20170611 143620[1]](https://i0.wp.com/www.astropixelprocessor.com/wp-content/uploads/wpforo/attachments/109/95-201706111436201.jpg?ssl=1 "20170611 143620[1]")
![20170611 185355[1]](https://i0.wp.com/www.astropixelprocessor.com/wp-content/uploads/wpforo/attachments/109/102-201706111853551.jpg?ssl=1 "20170611 185355[1]")
![20170611 185500[1]](https://i0.wp.com/www.astropixelprocessor.com/wp-content/uploads/wpforo/attachments/109/104-201706111855001.jpg?ssl=1 "20170611 185500[1]")
![IMG 20170611 WA0021[1]](https://i0.wp.com/www.astropixelprocessor.com/wp-content/uploads/wpforo/attachments/109/108-IMG-20170611-WA00211.jpeg?ssl=1 "IMG 20170611 WA0021[1]")
