cannot reproduce ImageSolver with Distortion Correction checked generates error

Just to consolidate what @cloudbait says above, can you confirm that running the ImageSolver script stand-alone (not in WBPP) with distortion correction selected is always failing (for any image).
 
01blueglide said:
That was the problem in my case. Can't speak for Jkcoli.
Click to expand...
You have probably specified it somewhere, but could you repeat here the exact spec of your system (i.e. exactly which processor, which version and build of the OS, how much memory). If we can establish some common system feature for this (clearly system-dependent) fault we may make some progress.
 
I have attached a screenshot of where the failure occurs. It on line 2575 in the ImageSolver script.
I don't understand the syntax
Does anyone understand what ReferSpline does?
 
fredvanner said:
You have probably specified it somewhere, but could you repeat here the exact spec of your system (i.e. exactly which processor, which version and build of the OS, how much memory). If we can establish some common system feature for this (clearly system-dependent) fault we may make some progress.
Click to expand...
Top of the discussion. As usual these days, this is a Mac problem.
 
fredvanner said:
You have probably specified it somewhere, but could you repeat here the exact spec of your system (i.e. exactly which processor, which version and build of the OS, how much memory). If we can establish some common system feature for this (clearly system-dependent) fault we may make some progress.
Click to expand...
2019 Mac Book Pro. 2.3 GHz 8-Core Intel Core i9. 16 GB 2667 MHz DDR4 MacOS Sequoia 15.2
 
jkcolli Computer:

Computer: Mac mini

OS: macOS Sequoia Version15.2

Processor: 3.2GHz 6-Core Intel Corei7

Memory: 16 GB 2667MHz DDR4
 
Jkcolli said:
jkcolli Computer:

Computer: Mac mini

OS: macOS Sequoia Version15.2

Processor: 3.2GHz 6-Core Intel Corei7

Memory: 16 GB 2667MHz DDR4
Click to expand...
I do think the small amount of memory may be a consideration (even though it meets the minimum requirements, it is certainly less than recommended). MacOS should handle assigning virtual memory automatically and transparently, but I seem to recall some past issues where that didn't seem to be working as expected.
 
cloudbait said:
I do think the small amount of memory may be a consideration (even though it meets the minimum requirements, it is certainly less than recommended). MacOS should handle assigning virtual memory automatically and transparently, but I seem to recall some past issues where that didn't seem to be working as expected.
Click to expand...
I'd be curious to hear from the developers if distortion correction is a very memory intensive process compared to other PI processes. I have never experienced performance problems due to memory with other PI projects. I don't know why distortion correction would be memory intensive.
 
01blueglide said:
I'd be curious to hear from the developers if distortion correction is a very memory intensive process compared to other PI processes. I have never experienced performance problems due to memory with other PI projects. I don't know why distortion correction would be memory intensive.
Click to expand...
It's a good question. I'll note that one of the things that has been steadily changed with each release involves the complexity of image solutions.
 
OK..I re-ran my M1 data set in PI 1.9.2 without astrometric solution in the WBPP pipeline (since I can't untick distortion correction in WBPP settings) and it generated a master XSIF file which I successfully used Image Solver manually to solve after unticking distortion correction.
 
First light (M31) with my new ASI2600MC Pro Duo camera, and WBPP's Astrometric Solution failed. I'm running 1.9.2 on a 2019 MacBook Pro.

I made Image Solver work just now by unchecking Distortion Correction.
 
Jkcolli said:
PixInsight Version: PI-macosx-x64-1.9.2-20241228-c, build 1632, released 24-12-28



Computer: Mac mini

OS: macOS Sequoia Version15.1.1

Processor: 3.2GHz 6-Core Intel Corei7

Memory: 16 GB 2667MHz DDR4



In Pixinsight. 1.9.2, if Distortion Correction is checked in ImageSolver script, and Error is generated as seen in the Process Console window.

The ImageSolver window the closes.



I have tried this on several images and it always crashes at the same spot in the Imagesolver processing. I have attached a screenshot of the Process Console showing where it crashes.



I have tried all of the Distortion Correction Radial Basis function choices and they all result in the error.



I have attached screenshots of the Process Console showing the Error and the ImageSolver window.

Any ideas?



Jack
Click to expand...
Similar issues
 
We cannot reproduce the problems reported here on our working and testing machines on any supported platform, including up-to-date macOS 14 and 15, with any of our test data sets.

Please provide a data set where this issue can be reproduced so we can try to reproduce it on our machines, which is necessary to understand and fix any non-trivial bug. If a problem cannot be reproduced, it is a machine-specific issue out of our control.
 
Juan
I included this is Post #4 but it was at the very bottom.

Below is the link to an image file.

Iris Int.xisf

drive.google.com drive.google.com

1. I have been troubleshooting this problem and found that the Error is occurring with the ReferSpline call in the WCSmetadata.jsh file.

2. It appears to only go through the first for loop two times before crashing. p1.length = 1164, p2.length =1164.

3. Do your Macs have more than 16GBytes of memory? I not sure that it matters since my understanding is less memory only slows down processing because Swap files may need to be used.

Thanks for your help
Jack
 
01blueglide said:
OK...small breakthrough...I'm the OP from the other thread mentioned here. I re-installed PI 1.9.2 and tried using Image Solver without Distortion Correction checked (Its on by default)....Image Solver worked and several frames I tried solved properly.
Click to expand...
Same here..
 
Juan Conejero said:
We cannot reproduce the problems reported here on our working and testing machines on any supported platform, including up-to-date macOS 14 and 15, with any of our test data sets.

Please provide a data set where this issue can be reproduced so we can try to reproduce it on our machines, which is necessary to understand and fix any non-trivial bug. If a problem cannot be reproduced, it is a machine-specific issue out of our control.
Click to expand...
I am having the same issues as many on the forum. When I uncheck distortion correction, image solver works. I too am running a Mac and I know I need a new one with more RAM. Do you think the lack of RAM could possibly have anything to do with the issues. Is 1.9.2 more memory intensive than the prior versions? I didn't have issues until the new update.
 
Juan
I have uploaded a cropped version of the original image I put on Google drive. This file is 1420x1420 and ImageSolver with DistortionCorrection checked works with this cropped version. If I make the crop slightly larger then ImageCorrection fails.

Iris IntCrop1420x1420.xisf

drive.google.com drive.google.com

Jack
 
You must log in or register to reply here.
Back
Top