cannot reproduce ImageSolver with Distortion Correction checked generates error

J

Jkcolli

Well-known member
PixInsight Version: PI-macosx-x64-1.9.2-20241228-c, build 1632, released 24-12-28



Computer: Mac mini

OS: macOS Sequoia Version15.1.2

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
 

Attachments

  • Process Control window showing Error.png
    Process Control window showing Error.png
    264.8 KB · Views: 60
  • ImageSolver window.png
    ImageSolver window.png
    131.3 KB · Views: 55
Last edited:
I cannot reproduce this problem. Besides what Nico has said, which is probably the cause of this problem, can you please upload an image where this can be reproduced?
 
PixInsight Version: PI-macosx-x64-1.9.2-20241228-c, build 1632, released 24-12-28

Computer: Macmini 2018

OS: macOS Sequoia Version15.2

Processor: 3.2GHz 6-Core Intel Corei7
Graphics: Intel UHD Graphics 630 1536MB
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.
Then the ImageSolver window closes.

Note: This error only occurs if Distortion Correction is selected.(The error occurred in 1.9.0, 1.9.1 with PixInsight crashing and in 1.9.2 just ImageSolver quits and PixInsight stays open.

This error did not occur in ver 1.8.9.3.

This error is not specific to a particular image file. The error occurs on all images I have tried.

Image Solver script:

I believe this error occurs around line 2575 in the ImageSolver script
I have attached a screenshot of that area of the code.(ImageSolver code.png)
Note: This error does not occur on my PC using the same image files. It only occurs on my Mac computer.

GAIA setup:

I am not using any external hard drives.

All image files, GAIA database files and PixInsight are on my Mac hard drive.

I have created folders in the Mac Documents folder for the GAIA DR3 database files.

I have attached a screenshot showing the setup on my Mac hard drive.(GAIA Database setup.png)

As you can from the GAIA preferences window, I believe the correct DR3 files are being used.


Logfile:

I have attached a log file that shows running ImageSolver with Distortion Correction checked
(log with DistCorr.txt) and the corresponding Error.

I have attached another log file that shows running ImageSolver with Distortion Correction unchecked (log no DistCorr.txt) that has no errors.
I believe in both cases GAIA files are being used and you can from the GAIA path that the correct GAIA files are being used.

RA, DEC:

I solved the image file with ASTAP and the RA and DEC are very close to what is in the meta data of the image file

Image File RA 21:1:48.314 DEC 68:11:48.33

ASTAP RA 21:1:48.3 DEC 68:11:40

Image file.

On Google Drive: (Iris Int.xisf)

Iris Int.xisf

drive.google.com drive.google.com
 

Attachments

  • ImageSolver code.png
    ImageSolver code.png
    73 KB · Views: 28
  • log with DistCorr.txt
    log with DistCorr.txt
    22.2 KB · Views: 23
  • log no DistCorr.txt
    log no DistCorr.txt
    16.3 KB · Views: 17
  • GAIA DR3 setup.jpg
    GAIA DR3 setup.jpg
    269.3 KB · Views: 26
  • ImageSolver window.png
    ImageSolver window.png
    131.3 KB · Views: 27
Last edited:
Solves perfectly well here on my Mac running Monterey, with and without distortion correction.

Is your Mac running Time Machine? It is worth adding the PI Swap directory and the location of the Various Database files (Gaia and Mars) from the Time Machine setup.
 
Fred:
This error only occurs on my Mac. ImageSolver works fine on my Windows 10 PC.

Chris:
I am running Time Machine. I am not sure what you mean by adding the PI Swap directory and the databases from the Time Machine setup? Are you asking where they are in Time Machine?

Jack
 
I think Chris is suggesting that you should add any file or folder that PixInsight accesses during operation (e.g. image files; Gaia and MARS database files) to the Time Machine backup "excluded files" list.
 
I have attached a screenshot of the Time Machine Exclude directories.
I re-installed PixInsight 1.9.2

I still have the problem.

Jack
 

Attachments

  • Time Machine Exclude.png
    Time Machine Exclude.png
    65.4 KB · Views: 25
Jkcolli said:
I have attached a screenshot of the Time Machine Exclude directories.
I re-installed PixInsight 1.9.2

I still have the problem.

Jack
Click to expand...
Did you try simply disabling Time Machine completely, just to be sure that some important folder being used by PI isn't still being synced? Also, make sure you don't have any folders that are synced to iCloud (which tends to cause more problems with PI on Macs than Time Machine).
 
OK. I agree that on closer examination file sync issues are unlikely to be causing this.
From the log it looks as though the initial solution is fine (which is the stage at which all the catalogue access will be performed); the error seems to occur immediately at the start of the iterative distortion correction phase. The fact that this works on other systems makes it unlikely that this is a code error. It looks more like a hardware fault, of a hardware compatibility issue.
 
fredvanner said:
OK. I agree that on closer examination file sync issues are unlikely to be causing this.
From the log it looks as though the initial solution is fine (which is the stage at which all the catalogue access will be performed); the error seems to occur immediately at the start of the iterative distortion correction phase. The fact that this works on other systems makes it unlikely that this is a code error. It looks more like a hardware fault, of a hardware compatibility issue.
Click to expand...

I noticed that in both threads the problem occurs with a Mac with only 16GB of RAM. I don't know if this is relevant?
 
fredvanner said:
… the error seems to occur immediately at the start of the iterative distortion correction phase.
Click to expand...
Some of those *Abort* errors are a function of the OP hitting *cancel* hence my question as to what console error messages appear when trying to solve the image from message #7 manually.
 
nico1038 said:
I noticed that in both threads the problem occurs with a Mac with only 16GB of RAM. I don't know if this is relevant?
Click to expand...
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.
 
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...

Yes, it is very clearly related to distortion correction.
The message shown here in post #1 is exactly the same as yours, as Fred said it fails at the start of the iterative distortion correction phase
 
nico1038 said:
Yes, it is very clearly related to distortion correction.
The message shown here in post #1 is exactly the same as yours, as Fred said it fails at the start of the iterative distortion correction phase
Click to expand...
It's good to see I can continue using PI 1.9.2. Next step is to try and figure out why Distortion Correction is causing failure when checked or if some settings within distortion correction need changing to allow it to work. Happy to see some progress forward.
 
01blueglide said:
It's good to see I can continue using PI 1.9.2. Next step is to try and figure out why Distortion Correction is causing failure when checked or if some settings within distortion correction need changing to allow it to work. Happy to see some progress forward.
Click to expand...
Maybe I missed this above... do you only see the problem when ImageSolver runs at the end of WBPP, or does it also occur when you try solving the masters that WBPP created?
 
cloudbait said:
Maybe I missed this above... do you only see the problem when ImageSolver runs at the end of WBPP, or does it also occur when you try solving the masters that WBPP created?
Click to expand...
Both...if Distortion Correction is ticked (with default settings in distortion correction) plate solving fails. I unticked it and Image solver worked. I have not re-run a complete data set yet with Astrometric Solution in the WBPP pipeline yet. Getting ready to re-run M1 data set that I was using yesterday when trying out PI 1.9.2. Image Solver worked on M1 master that had been produced with PI 1.8.9-3.
 
01blueglide said:
Both...if Distortion Correction is ticked (with default settings in distortion correction) plate solving fails. I unticked it and Image solver worked. I have not re-run a complete data set yet with Astrometric Solution in the WBPP pipeline yet. Getting ready to re-run M1 data set that I was using yesterday when trying out PI 1.9.2. Image Solver worked on M1 master that had been produced with PI 1.8.9-3.
Click to expand...
Ok... that's "good" because it should be a lot easier to track down if all you have to do is make adjustments to ImageSolver, without having to go through the whole WBPP sequence repeatedly!
 
You must log in or register to reply here.
Back
Top