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.
Getting a Java error when trying to register. I am running the Trial.
This exact same data works perfectly in PixInsight.
I can't attach a txt file so here is the console:
22:35:34 - 4) REGISTER: starting... 22:35:34 - 4) REGISTER: reference frame found: Helix Nebula_600sec_1x1__frame4-2.fit 22:35:34 - 4) REGISTER: normal registration mode 22:35:34 - 4) REGISTER: created pattern recognition descriptors of the reference frame 22:35:34 - 4) REGISTER: all 2-View registration tasks are created 22:35:34 - 4) REGISTER: frame Helix Nebula_600sec_1x1__frame1.fit of type light 2 B D F BPM CA STAR REG can't be registered 22:35:34 - 4) REGISTER: frame Helix Nebula_600sec_1x1__frame2.fit of type light 12 B D F BPM CA STAR REG can't be registered 22:35:34 - 4) REGISTER: frame Helix Nebula_600sec_1x1__frame3.fit of type light 15 B D F BPM CA STAR REG can't be registered 22:35:34 - 4) REGISTER: frame Helix Nebula_600sec_1x1__frame4.fit of type light 18 B D F BPM CA STAR REG can't be registered 22:35:34 - 4) REGISTER: frame Helix Nebula_600sec_1x1__frame5.fit of type light 21 B D F BPM CA STAR REG can't be registered 22:35:34 - 4) REGISTER: frame Helix Nebula_600sec_1x1__frame6.fit of type light 24 B D F BPM CA STAR REG can't be registered 22:35:34 - 4) REGISTER: frame Helix Nebula_600sec_1x1__frame7.fit of type light 26 B D F BPM CA STAR REG can't be registered 22:35:34 - 4) REGISTER: frame Helix Nebula_600sec_1x1__frame8.fit of type light 28 B D F BPM CA STAR REG can't be registered 22:35:34 - 4) REGISTER: frame Helix Nebula_600sec_1x1__frame9.fit of type light 30 B D F BPM CA STAR REG can't be registered 22:35:34 - 4) REGISTER: frame Helix Nebula_600sec_1x1__frame10.fit of type light 4 B D F BPM CA STAR REG can't be registered 22:35:34 - 4) REGISTER: frame Helix Nebula_600sec_1x1__frame11.fit of type light 6 B D F BPM CA STAR REG can't be registered 22:35:34 - 4) REGISTER: frame Helix Nebula_600sec_1x1__frame12.fit of type light 8 B D F BPM CA STAR REG can't be registered 22:35:34 - 4) REGISTER: frame Helix Nebula_600sec_1x1__frame2-1.fit of type light 9 B D F BPM CA STAR REG can't be registered 22:35:34 - 4) REGISTER: frame Helix Nebula_600sec_1x1__frame2-2.fit of type light 10 B D F BPM CA STAR REG can't be registered 22:35:34 - 4) REGISTER: frame Helix Nebula_600sec_1x1__frame3-1.fit of type light 13 B D F BPM CA STAR REG can't be registered 22:35:34 - 4) REGISTER: frame Helix Nebula_600sec_1x1__frame4-1.fit of type light 16 B D F BPM CA STAR REG can't be registered 22:35:34 - 4) REGISTER: frame Helix Nebula_600sec_1x1__frame5-1.fit of type light 19 B D F BPM CA STAR REG can't be registered 22:35:34 - 4) REGISTER: frame Helix Nebula_600sec_1x1__frame6-1.fit of type light 22 B D F BPM CA STAR REG can't be registered 22:35:34 - 4) REGISTER: initial number of accepted star pairs for frame Helix Nebula_600sec_1x1__frame2-3.fit = 0 22:35:34 - 4) REGISTER: initial number of accepted star pairs for frame Helix Nebula_600sec_1x1__frame3-2.fit = 8 22:35:34 - 4) REGISTER: can't register this frame, less than 5 starpairs found 22:35:34 - 4) REGISTER: number of accepted star pairs after removing duplicates for frame Helix Nebula_600sec_1x1__frame3-2.fit = 8 22:35:34 - 4) REGISTER: number of accepted star pairs after removing false positives for frame Helix Nebula_600sec_1x1__frame3-2.fit = 8 22:35:34 - 4) REGISTER: start expansion of registration hypothesis for frame Helix Nebula_600sec_1x1__frame3-2.fit 22:35:34 - Best Registration Hypothesis: frame Helix Nebula_600sec_1x1__frame3-2.fit no DDC performing RANSAC on # 8 pairs 22:35:34 - 4) REGISTER: 2-View registration of frame Helix Nebula_600sec_1x1__frame1-1.fit encountered an execution exception 22:35:35 - Best Registration Hypothesis: frame Helix Nebula_600sec_1x1__frame3-2.fit no DDC after RANSAC # 7 pairs 22:35:35 - Best Registration Hypothesis: frame Helix Nebula_600sec_1x1__frame3-2.fit start actual hypothesis expansion 22:35:35 - Best Registration Hypothesis: frame Helix Nebula_600sec_1x1__frame3-2.fit initial RMS 0.053 on 7 star pairs 22:35:35 - Best Registration Hypothesis: frame Helix Nebula_600sec_1x1__frame3-2.fit safe margin 3.612 RANSAC Margin 1.000 22:35:35 - Best Registration Hypothesis: frame Helix Nebula_600sec_1x1__frame3-2.fit performing RANSAC on 8 pairs 22:35:35 - Best Registration Hypothesis: frame Helix Nebula_600sec_1x1__frame3-2.fit number of pairs 8 after RANSAC 22:35:35 - Best Registration Hypothesis: frame Helix Nebula_600sec_1x1__frame3-2.fit number of pairs before 7 number of pairs after 8 RMS 0.06 DDC model noUndistortionModel 22:35:35 - Best Registration Hypothesis: frame Helix Nebula_600sec_1x1__frame3-2.fit safe margin 3.387 RANSAC Margin 1.000 22:35:35 - Best Registration Hypothesis: frame Helix Nebula_600sec_1x1__frame3-2.fit performing RANSAC on 8 pairs 22:35:35 - Best Registration Hypothesis: frame Helix Nebula_600sec_1x1__frame3-2.fit number of pairs 8 after RANSAC 22:35:35 - Best Registration Hypothesis: frame Helix Nebula_600sec_1x1__frame3-2.fit number of pairs before 8 number of pairs after 8 RMS 0.06 DDC model noUndistortionModel 22:35:35 - Best Registration Hypothesis: frame Helix Nebula_600sec_1x1__frame3-2.fit finished with number of pairs 8 RMS 0.06 22:35:35 - 4) REGISTER: finished expansion of registration hypothesis for frame Helix Nebula_600sec_1x1__frame3-2.fit 22:35:35 - 4) REGISTER: number of final star pairs for frame Helix Nebula_600sec_1x1__frame3-2.fit = 8 22:35:38 - 4) REGISTER: 2-View registration results of frame Helix Nebula_600sec_1x1__frame2-3.fit received 22:35:38 - 4) REGISTER: 2-View registration results of frame Helix Nebula_600sec_1x1__frame3-2.fit received 22:35:38 - 4) REGISTER: 2-View registration of frame Helix Nebula_600sec_1x1__frame5-2.fit encountered an execution exception 22:35:39 - 4) REGISTER: frame Helix Nebula_600sec_1x1__frame6-2.fit of type light 23 B D F BPM CA STAR REG can't be registered 22:35:39 - 4) REGISTER: frame Helix Nebula_600sec_1x1__frame7-1.fit of type light 25 B D F BPM CA STAR REG can't be registered 22:35:39 - 4) REGISTER: frame Helix Nebula_600sec_1x1__frame8-1.fit of type light 27 B D F BPM CA STAR REG can't be registered 22:35:39 - 4) REGISTER: frame Helix Nebula_600sec_1x1__frame9-1.fit of type light 29 B D F BPM CA STAR REG can't be registered 22:35:39 - 4) REGISTER: frame Helix Nebula_600sec_1x1__frame10-1.fit of type light 3 B D F BPM CA STAR REG can't be registered 22:35:39 - 4) REGISTER: frame Helix Nebula_600sec_1x1__frame11-1.fit of type light 5 B D F BPM CA STAR REG can't be registered 22:35:39 - 4) REGISTER: frame Helix Nebula_600sec_1x1__frame12-1.fit of type light 7 B D F BPM CA STAR REG can't be registered 22:35:39 - 4) REGISTER: frame 32000 Flat_1.58sec_1x1__frame1.fit of type flat 1 B BPM can't be registered 22:35:39 - 4) REGISTER: frame 32000 Flat_1.58sec_1x1__frame2.fit of type flat 12 B BPM can't be registered 22:35:39 - 4) REGISTER: frame 32000 Flat_1.58sec_1x1__frame3.fit of type flat 15 B BPM can't be registered 22:35:39 - 4) REGISTER: frame 32000 Flat_1.58sec_1x1__frame4.fit of type flat 16 B BPM can't be registered 22:35:39 - 4) REGISTER: frame 32000 Flat_1.58sec_1x1__frame5.fit of type flat 17 B BPM can't be registered 22:35:39 - 4) REGISTER: frame 32000 Flat_1.58sec_1x1__frame6.fit of type flat 18 B BPM can't be registered 22:35:39 - 4) REGISTER: frame 32000 Flat_1.58sec_1x1__frame7.fit of type flat 19 B BPM can't be registered 22:35:39 - 4) REGISTER: frame 32000 Flat_1.58sec_1x1__frame8.fit of type flat 20 B BPM can't be registered 22:35:39 - 4) REGISTER: frame 32000 Flat_1.58sec_1x1__frame9.fit of type flat 21 B BPM can't be registered 22:35:39 - 4) REGISTER: frame 32000 Flat_1.58sec_1x1__frame10.fit of type flat 2 B BPM can't be registered 22:35:39 - 4) REGISTER: frame 32000 Flat_1.58sec_1x1__frame11.fit of type flat 3 B BPM can't be registered 22:35:39 - 4) REGISTER: frame 32000 Flat_1.58sec_1x1__frame12.fit of type flat 4 B BPM can't be registered 22:35:39 - 4) REGISTER: frame 32000 Flat_1.58sec_1x1__frame13.fit of type flat 5 B BPM can't be registered 22:35:39 - 4) REGISTER: frame 32000 Flat_1.58sec_1x1__frame14.fit of type flat 6 B BPM can't be registered 22:35:39 - 4) REGISTER: frame 32000 Flat_1.58sec_1x1__frame15.fit of type flat 7 B BPM can't be registered 22:35:39 - 4) REGISTER: frame 32000 Flat_1.58sec_1x1__frame16.fit of type flat 8 B BPM can't be registered 22:35:39 - 4) REGISTER: frame 32000 Flat_1.58sec_1x1__frame17.fit of type flat 9 B BPM can't be registered 22:35:39 - 4) REGISTER: frame 32000 Flat_1.58sec_1x1__frame18.fit of type flat 10 B BPM can't be registered 22:35:39 - 4) REGISTER: frame 32000 Flat_1.58sec_1x1__frame19.fit of type flat 11 B BPM can't be registered 22:35:39 - 4) REGISTER: frame 32000 Flat_1.58sec_1x1__frame20.fit of type flat 13 B BPM can't be registered 22:35:39 - 4) REGISTER: frame 32000 Flat_1.58sec_1x1__frame21.fit of type flat 14 B BPM can't be registered 22:35:39 - 4) REGISTER: frame Target 1_600sec_1x1__frame1.fit of type dark 1 B can't be registered 22:35:39 - 4) REGISTER: frame Target 1_600sec_1x1__frame2.fit of type dark 12 B can't be registered 22:35:39 - 4) REGISTER: frame Target 1_600sec_1x1__frame3.fit of type dark 15 B can't be registered 22:35:39 - 4) REGISTER: frame Target 1_600sec_1x1__frame4.fit of type dark 16 B can't be registered 22:35:39 - 4) REGISTER: frame Target 1_600sec_1x1__frame5.fit of type dark 17 B can't be registered 22:35:39 - 4) REGISTER: frame Target 1_600sec_1x1__frame6.fit of type dark 18 B can't be registered 22:35:39 - 4) REGISTER: frame Target 1_600sec_1x1__frame7.fit of type dark 19 B can't be registered 22:35:39 - 4) REGISTER: frame Target 1_600sec_1x1__frame8.fit of type dark 20 B can't be registered 22:35:39 - 4) REGISTER: frame Target 1_600sec_1x1__frame9.fit of type dark 21 B can't be registered 22:35:39 - 4) REGISTER: frame Target 1_600sec_1x1__frame10.fit of type dark 2 B can't be registered 22:35:39 - 4) REGISTER: frame Target 1_600sec_1x1__frame11.fit of type dark 3 B can't be registered 22:35:39 - 4) REGISTER: frame Target 1_600sec_1x1__frame12.fit of type dark 4 B can't be registered 22:35:39 - 4) REGISTER: frame Target 1_600sec_1x1__frame13.fit of type dark 5 B can't be registered 22:35:39 - 4) REGISTER: frame Target 1_600sec_1x1__frame14.fit of type dark 6 B can't be registered 22:35:39 - 4) REGISTER: frame Target 1_600sec_1x1__frame15.fit of type dark 7 B can't be registered 22:35:39 - 4) REGISTER: frame Target 1_600sec_1x1__frame16.fit of type dark 8 B can't be registered 22:35:39 - 4) REGISTER: frame Target 1_600sec_1x1__frame17.fit of type dark 9 B can't be registered 22:35:39 - 4) REGISTER: frame Target 1_600sec_1x1__frame18.fit of type dark 10 B can't be registered 22:35:39 - 4) REGISTER: frame Target 1_600sec_1x1__frame19.fit of type dark 11 B can't be registered 22:35:39 - 4) REGISTER: frame Target 1_600sec_1x1__frame20.fit of type dark 13 B can't be registered 22:35:39 - 4) REGISTER: frame Target 1_600sec_1x1__frame21.fit of type dark 14 B can't be registered 22:35:39 - 4) REGISTER: frame 32000 Bias_0sec_1x1__frame1.fit of type bias 1 can't be registered 22:35:39 - 4) REGISTER: frame 32000 Bias_0sec_1x1__frame2.fit of type bias 12 can't be registered 22:35:39 - 4) REGISTER: frame 32000 Bias_0sec_1x1__frame3.fit of type bias 15 can't be registered 22:35:39 - 4) REGISTER: frame 32000 Bias_0sec_1x1__frame4.fit of type bias 16 can't be registered 22:35:39 - 4) REGISTER: frame 32000 Bias_0sec_1x1__frame5.fit of type bias 17 can't be registered 22:35:39 - 4) REGISTER: frame 32000 Bias_0sec_1x1__frame6.fit of type bias 18 can't be registered 22:35:39 - 4) REGISTER: frame 32000 Bias_0sec_1x1__frame7.fit of type bias 19 can't be registered 22:35:39 - 4) REGISTER: frame 32000 Bias_0sec_1x1__frame8.fit of type bias 20 can't be registered 22:35:39 - 4) REGISTER: frame 32000 Bias_0sec_1x1__frame9.fit of type bias 21 can't be registered 22:35:39 - 4) REGISTER: frame 32000 Bias_0sec_1x1__frame10.fit of type bias 2 can't be registered 22:35:39 - 4) REGISTER: frame 32000 Bias_0sec_1x1__frame11.fit of type bias 3 can't be registered 22:35:39 - 4) REGISTER: frame 32000 Bias_0sec_1x1__frame12.fit of type bias 4 can't be registered 22:35:39 - 4) REGISTER: frame 32000 Bias_0sec_1x1__frame13.fit of type bias 5 can't be registered 22:35:39 - 4) REGISTER: frame 32000 Bias_0sec_1x1__frame14.fit of type bias 6 can't be registered 22:35:39 - 4) REGISTER: frame 32000 Bias_0sec_1x1__frame15.fit of type bias 7 can't be registered 22:35:39 - 4) REGISTER: frame 32000 Bias_0sec_1x1__frame16.fit of type bias 8 can't be registered 22:35:39 - 4) REGISTER: frame 32000 Bias_0sec_1x1__frame17.fit of type bias 9 can't be registered 22:35:39 - 4) REGISTER: frame 32000 Bias_0sec_1x1__frame18.fit of type bias 10 can't be registered 22:35:39 - 4) REGISTER: frame 32000 Bias_0sec_1x1__frame19.fit of type bias 11 can't be registered 22:35:39 - 4) REGISTER: frame 32000 Bias_0sec_1x1__frame20.fit of type bias 13 can't be registered 22:35:39 - 4) REGISTER: frame 32000 Bias_0sec_1x1__frame21.fit of type bias 14 can't be registered 22:35:39 - 4) REGISTER: frame BPM-Celestron_Nightscape-3326x2504.fits of type bad pixel map 1 can't be registered 22:35:39 - 4) REGISTER: frame MF-ISO_gain_0.0-exp_1.58s-21subs-Celestron_Nightscape-NR-1xbl-avg.fits of type master flat 1 can't be registered 22:35:39 - 4) REGISTER: frame MD-ISO_gain_0.0-exp_600.0s-21subs-Celestron_Nightscape-NR-avg.fits of type master dark 1 can't be registered 22:35:39 - 4) REGISTER: frame MB-ISO_gain_0.0-exp_0.0s-21subs-Celestron_Nightscape-NR-avg.fits of type master bias 1 can't be registered 22:35:39 - 4) REGISTER: calculating final projective registration model parameters of frame Helix Nebula_600sec_1x1__frame3-2.fit 22:35:39 - 4) REGISTER: calculating final projective registration model parameters of frame Helix Nebula_600sec_1x1__frame4-2.fit 22:35:39 - 4) REGISTER: calculating adjusted quality score, star density and relative FWHM for frame Helix Nebula_600sec_1x1__frame3-2.fit 22:35:39 - 4) REGISTER: calculating adjusted quality score, star density and relative FWHM for frame Helix Nebula_600sec_1x1__frame4-2.fit 22:35:39 - 4) REGISTER: received all results 22:35:39 - FRAME DETAILS UPDATER: starting... 22:35:39 - FRAME DETAILS UPDATER: no new frames to add 22:35:39 - FRAME DETAILS UPDATER: rebuilding all frame details... 22:35:39 - FRAME DETAILS UPDATER: checking if frames were identified earlier... 22:35:39 - FRAME DETAILS UPDATER: adding frame marks... 22:35:39 - FRAME DETAILS UPDATER: updated succesfully
My apologies for this inconvenience, luckily, there is a good explanation for the error that you receive and why registration initially fails.
Thank you for sharing the console output and showing us a screenshot, that really helps. I have enabled the option to post .txt attachments in the forum as well.
To be able to register your images, APP needs to detect stars in 3) analyse stars. As you can see in your screenshot, in the bottom frame list panel, there is a column "#stars and star density", which shows "N/A" for all frames. This means that with the current settings in 3), APP finds no stars in your data. The solution is to lower the
detect above noise level kappa value in 3) ANALYSE STARS
If you lower it to 10-20 from the default value of 80, APP really should start to detect stars. And then registration should simply work.
The java error will be gone in APP's next release and the next release will also automatically determine this kappa value for your data. So then it should just simply work.
Thank you for sharing this error.
Kind regards,
Mabula
p.s.
More information on this problem can be found in the release notes of the current version 1.055:
IMPROVED, star analysis, detection of stars has been improved significantly for high quality/SNR frames with lots of nebulosity, the old method didn't work optimally. (triggered by testing on high quality frames of the Wide-field Infrared Survey Explorer (WISE) that images in mid infrared bandpasses, pointed to me by Judy Schmidt).
ADJUSTED, star analysis, the detect above noise kappa setting now has a range of 6 - 250. A value of 80 now corresponds, more or less, to the old value of 8. The reason for this is, that APP now uses Multi-Resolution Support Gaussian noise for dispersion calculation in the starmap. Previously APP used the root of the variance (standard deviation) for the dispersion, which was subject to outliers from the stars themselves. The data is flatfielded using a 9x9 median filtered plane that is subtracted from the data to find the stars. The gaussian noise is then calculated from this flat-fielded data. For high quality data, you can now find lots more stars by lowering the kappa value. Only lower the kappa value from the initial 80 value, if APP detects little stars and registration fails. Normally, you won't need more stars then 2500-5000 per frame for mosaics and 1000-2500 for regular registration.
And the release notes of the upcoming version 1.056:
IMPROVED, star analysis, I have made some significant and needed changes in the star analysis module in version 1.055. Unfortunately, the required kappa value, for the detect above noise level setting, to detect for instance 1000 stars in an image had a much larger spread for different data. So the kappa value of 80 was too low for some data, detecting 1000s of stars already and for other data, it was much too high, detecting no stars at all. So now I have altered the detection settings. You can now set a lower limit on the amount of stars you wish to detect, then the kappa value will be automatically adjusted to find the desired amount of stars. If you disable this function, then you can still set the kappa value yourself. So this new function is called automatic minimum #stars target and will now be the preferred way to get a good star count automatically for your data. If the function is enabled, you'll see in the console if the kappa is adjusted, and the original kappa slider will show the adjustments as well, so it will show you the required kappa value. To make sure that all images are analysed with the same kappa value, which is needed for a comparable quality calculation value, this automatic setting finds the required kappa for the first light frame that you analyse and will use that for the remaining frames.
IMPROVED, star analysis, I have also added the option to restrict the amount of stars found in the images. This is very usefull and will actually help with registering high quality data that is just full of stars. This function is called: automatic maximum #stars target. It's value cannot be lower than 2x the automatic minimum #stars target value.
IMPROVED, star analysis, as a side benefit of the above 2 changes, the actual star analysis per frame will be a bit quicker for some datasets. It won't be slower and you won't need to fiddle with the kappa value yourself.
FIXED, registration, if star analysis only found very little stars in a frame (less than 12) a null pointer exception would be thrown in registration, due to a boolean that was not set in reporting back registration status internally. This is fixed, the null pointer exception/java error is gone. Was triggered by several users in version 1.055 due to the change in the detect above noise level kappa values and calculation of the dispersion of the data. Screenshot of the particular error that was triggered.
So this error will be a thing of the past and in version 1.056, APP will automatically set the right kappa value in detect above noise level for you.
