Re: 1.5.369 crashes on wipe
Posted: Wed Oct 09, 2019 8:37 am
Hi Ivo,
I'll do my best to explain my process! FYI, my virtual memory is set to 'automatically manage paging file size' and currently allocated size is 5120MB.
I note that the log file from my last failed attempt shows details for files loaded, compose, crop, bin, develop - then nothing else shown in the log after that? I'm presuming that's because the subsequent wipe process didn't complete successfully?
Fits files are created with APP calibration and integration, same process I've always used, nothing different. The files used on my last attempt (as in log below) had been only processed for light pollution in APP because they were very 'dirty' (hence the 'lpc' suffix shown in the file name), but I've also tried with the original integration sets (several times!) with absolutely no processing whatsoever and I still get the same result in 1.5.369 - as mentioned, same files, same process, works fine in 1.4.352.
Here's the log for my last attempt:
-----------------------------------------------------------
StarTools 1.5.369
Tue Oct 08 15:34:56 2019
-----------------------------------------------------------
Loading luminance channel data
File loaded in LRGB module [D:\IMAGES\M31 Andromeda Galaxy\Further attempt with new cal files 08.10.19\St-avg-1800.0s-MWC_1_3.0_4-x_1.0_LZ3-NS-full-qua-add-sc_BWMV_nor-AAD-RL-noMBB-Lum-lpc.fits].
Loading red channel data
File loaded in LRGB module [D:\IMAGES\M31 Andromeda Galaxy\Further attempt with new cal files 08.10.19\St-avg-4500.0s-MWC_1_3.0_4-x_1.0_LZ3-NS-full-qua-add-sc_BWMV_nor-AAD-RL-noMBB-Red-lpc.fits].
Loading green channel data
File loaded in LRGB module [D:\IMAGES\M31 Andromeda Galaxy\Further attempt with new cal files 08.10.19\St-avg-4500.0s-MWC_1_3.0_4-x_1.0_LZ3-NS-full-qua-add-sc_BWMV_nor-AAD-RL-noMBB-Green-lpc.fits].
Loading blue channel data
File loaded in LRGB module [D:\IMAGES\M31 Andromeda Galaxy\Further attempt with new cal files 08.10.19\St-avg-4500.0s-MWC_1_3.0_4-x_1.0_LZ3-NS-full-qua-add-sc_BWMV_nor-AAD-RL-noMBB-Blue-lpc.fits].
--- Compose
Parameter [Luminance, Color] set to [L, RGB]
Parameter [Color Ch. Interpolation] set to [On]
Parameter [Lum Total Exposure] set to [0h20m (20m) (1200s)]
Parameter [Blue Total Exposure] set to [1h00m (60m) (3600s)]
Parameter [Green Total Exposure] set to [1h00m (60m) (3600s)]
Parameter [Red Total Exposure] set to [1h00m (60m) (3600s)]
Image size is 5524 x 3695
Type of Data: Linear, was not Bayered, or was Bayered + white balanced
--- Crop
Parameter [X1] set to [68 pixels]
Parameter [Y1] set to [75 pixels]
Parameter [X2] set to [5463 pixels (-61)]
Parameter [Y2] set to [3619 pixels (-76)]
Image size is 5395 x 3544
--- Bin
Parameter [Scale] set to [(scale/noise reduction 70.71%)/(200.00%)/(+1.00 bits)]
Image size is 3814 x 2505
--- Develop
Parameter [White Calibration] set to [Use Stars]
Parameter [Gamma] set to [1.00]
Parameter [Skyglow] set to [0 %]
Parameter [Digital Development] set to [91.53 %]
Parameter [Blue Luminance Contrib.] set to [100 %]
Parameter [Green Luminance Contrib.] set to [100 %]
Parameter [Red Luminance Contrib.] set to [100 %]
Parameter [Dark Anomaly Headroom] set to [5 %]
Parameter [Dark Anomaly Filter] set to [10.7 pixels]
Following on from this, this is my exact same process - copied from v 1.4.352 log because that works! - of my WIPE process leading up to the crash using 1.5.369. Not sure if this may be slightly different from the log 1.5.369 would produce, but at least it shows my process:
--- Wipe
Parameter [Mode] set to [Correct Color & Brightness]
Parameter [Temporary AutoDev] set to [Yes]
Parameter [Precision] set to [256 x 256 pixels]
Parameter [Dark Anomaly Filter] set to [8 pixels]
Parameter [Drop Off Point] set to [100 %]
Parameter [Corner Aggressiveness] set to [100 %]
Parameter [Aggressiveness] set to [85 %]
After adjusting the aggressiveness from the default 75% to 85% it seems OK. After that I've adjusted the dark anomaly filter up to 8 pixels, and on several occasions it's crashed at that point. But on the majority of occasions it happens once I've further adjusted the aggressiveness to another setting again (higher or lower than the previous 85%) …..
Hope this helps? Would it help if I was to send you my data files for you to try? (they may not be the best, but they're all my work so I'm proud of them!!).
Many thanks for your assistance, much appreciated!
Richard
I'll do my best to explain my process! FYI, my virtual memory is set to 'automatically manage paging file size' and currently allocated size is 5120MB.
I note that the log file from my last failed attempt shows details for files loaded, compose, crop, bin, develop - then nothing else shown in the log after that? I'm presuming that's because the subsequent wipe process didn't complete successfully?
Fits files are created with APP calibration and integration, same process I've always used, nothing different. The files used on my last attempt (as in log below) had been only processed for light pollution in APP because they were very 'dirty' (hence the 'lpc' suffix shown in the file name), but I've also tried with the original integration sets (several times!) with absolutely no processing whatsoever and I still get the same result in 1.5.369 - as mentioned, same files, same process, works fine in 1.4.352.
Here's the log for my last attempt:
-----------------------------------------------------------
StarTools 1.5.369
Tue Oct 08 15:34:56 2019
-----------------------------------------------------------
Loading luminance channel data
File loaded in LRGB module [D:\IMAGES\M31 Andromeda Galaxy\Further attempt with new cal files 08.10.19\St-avg-1800.0s-MWC_1_3.0_4-x_1.0_LZ3-NS-full-qua-add-sc_BWMV_nor-AAD-RL-noMBB-Lum-lpc.fits].
Loading red channel data
File loaded in LRGB module [D:\IMAGES\M31 Andromeda Galaxy\Further attempt with new cal files 08.10.19\St-avg-4500.0s-MWC_1_3.0_4-x_1.0_LZ3-NS-full-qua-add-sc_BWMV_nor-AAD-RL-noMBB-Red-lpc.fits].
Loading green channel data
File loaded in LRGB module [D:\IMAGES\M31 Andromeda Galaxy\Further attempt with new cal files 08.10.19\St-avg-4500.0s-MWC_1_3.0_4-x_1.0_LZ3-NS-full-qua-add-sc_BWMV_nor-AAD-RL-noMBB-Green-lpc.fits].
Loading blue channel data
File loaded in LRGB module [D:\IMAGES\M31 Andromeda Galaxy\Further attempt with new cal files 08.10.19\St-avg-4500.0s-MWC_1_3.0_4-x_1.0_LZ3-NS-full-qua-add-sc_BWMV_nor-AAD-RL-noMBB-Blue-lpc.fits].
--- Compose
Parameter [Luminance, Color] set to [L, RGB]
Parameter [Color Ch. Interpolation] set to [On]
Parameter [Lum Total Exposure] set to [0h20m (20m) (1200s)]
Parameter [Blue Total Exposure] set to [1h00m (60m) (3600s)]
Parameter [Green Total Exposure] set to [1h00m (60m) (3600s)]
Parameter [Red Total Exposure] set to [1h00m (60m) (3600s)]
Image size is 5524 x 3695
Type of Data: Linear, was not Bayered, or was Bayered + white balanced
--- Crop
Parameter [X1] set to [68 pixels]
Parameter [Y1] set to [75 pixels]
Parameter [X2] set to [5463 pixels (-61)]
Parameter [Y2] set to [3619 pixels (-76)]
Image size is 5395 x 3544
--- Bin
Parameter [Scale] set to [(scale/noise reduction 70.71%)/(200.00%)/(+1.00 bits)]
Image size is 3814 x 2505
--- Develop
Parameter [White Calibration] set to [Use Stars]
Parameter [Gamma] set to [1.00]
Parameter [Skyglow] set to [0 %]
Parameter [Digital Development] set to [91.53 %]
Parameter [Blue Luminance Contrib.] set to [100 %]
Parameter [Green Luminance Contrib.] set to [100 %]
Parameter [Red Luminance Contrib.] set to [100 %]
Parameter [Dark Anomaly Headroom] set to [5 %]
Parameter [Dark Anomaly Filter] set to [10.7 pixels]
Following on from this, this is my exact same process - copied from v 1.4.352 log because that works! - of my WIPE process leading up to the crash using 1.5.369. Not sure if this may be slightly different from the log 1.5.369 would produce, but at least it shows my process:
--- Wipe
Parameter [Mode] set to [Correct Color & Brightness]
Parameter [Temporary AutoDev] set to [Yes]
Parameter [Precision] set to [256 x 256 pixels]
Parameter [Dark Anomaly Filter] set to [8 pixels]
Parameter [Drop Off Point] set to [100 %]
Parameter [Corner Aggressiveness] set to [100 %]
Parameter [Aggressiveness] set to [85 %]
After adjusting the aggressiveness from the default 75% to 85% it seems OK. After that I've adjusted the dark anomaly filter up to 8 pixels, and on several occasions it's crashed at that point. But on the majority of occasions it happens once I've further adjusted the aggressiveness to another setting again (higher or lower than the previous 85%) …..
Hope this helps? Would it help if I was to send you my data files for you to try? (they may not be the best, but they're all my work so I'm proud of them!!).
Many thanks for your assistance, much appreciated!
Richard