cannot reproduce ImageSolver with Distortion Correction checked generates error

I am experiencing exactly the same issue on both my Macs when using large images. Both Macs have 16gb of Ram. The first Mac is an iMac with Monterrey 4GHz quad core I7. The second is 2019 MacBook Pro with Sequoia 15.2, 2.3 GHz 8 core I9. If distortion correction is checked, error. If distortion correction is unchecked then the plate solve works but takes significantly longer than the previous version of PI. I have the entire Gaia set and it's in a separate directory. Tried both local xpsd server and online server.
As Jkcolli, if I reduce my image size to 1197x798, plate solve works with distortion correction. My native size image size is 9576x6388.

Plate solving has always worked on both machines with PI 1.8 versions and earlier.

Jon

View attachment 25561
Yep
 
So I just installed PI 1.9.2 version 1633 with the roll back of QT released today. I'm still experiancing the same issue. Plate solving with distortion correction fails with an error at the same point prior to accessing the Gaia catalogs. If I significantly downsize the image like in the previous post, plate solve works with distortion correction checked.
Plate solving does work on my normal size image if distortion correction is unchecked.

Jon
 
Hi Jon,

As noted many times before, we cannot reproduce any of these problems. Can you please upload an image where this issue can be reproduced?
 
Hi Jon,

Thank you for uploading the image. Solved perfectly with ImageSolver 6.3.1, default parameters, PixInsight 1.9.2 Lockhart builds 1632 and 1633:

Code:
==================================================================================================
Creation time ............ 2025-01-03 20:33:41 UTC
Creation software ........ PixInsight 1.9.2 / ImageSolver 6.3.1 (macOS)
Reference catalog ........ Gaia DR3
Linear transformation matrix (world[ra,dec] = matrix * image[x,y]):
 -1.77182954e-04  -2.28126868e-07  +8.49060045e-01
 +2.36710664e-07  -1.77302638e-04  +5.65152363e-01
WCS transformation ....... DDM thin plate spline
Control points ........... 42773
Spline lengths ........... l:3881 b:3864 X:3966 Y:3916
Surface residuals ........ l:0.268 px b:0.259 px X:0.113 as Y:0.098 as
Projection ............... Gnomonic
Projection origin ........ [4787.884000 3193.893287] px -> [RA: 22 51 28.225  Dec: +57 51 13.53]
Resolution ............... 0.638 arcsec/px
Rotation ................. 0.056 deg
Reference system ......... ICRS
Observation start time ... 2024-06-12 08:54:40 UTC
Observation end time ..... 2024-08-08 06:00:20 UTC
Geodetic coordinates .....  88 47 03 W  30 23 59 N  0 m
Focal distance ........... 1212.23 mm
Pixel size ............... 3.75 um
Field of view ............ 1d 41' 50.2" x 1d 7' 56.0"
Image center ............. RA: 22 51 28.226  Dec: +57 51 13.53  ex: -0.000542 px  ey: -0.032715 px
Image bounds:
   top-left .............. RA: 22 57 56.064  Dec: +58 24 24.04  ex: -1.200147 px  ey: -1.210312 px
   top-right ............. RA: 22 45 00.986  Dec: +58 24 32.46  ex: +1.111574 px  ey: -1.383116 px
   bottom-left ........... RA: 22 57 43.461  Dec: +57 16 42.26  ex: -1.124058 px  ey: +0.188444 px
   bottom-right .......... RA: 22 45 12.282  Dec: +57 16 49.97  ex: +1.250267 px  ey: +0.163858 px
==================================================================================================

This has been on an old machine: MacBook Pro 15" 2018, 2.9 GHz 6-Core Intel Core i9, 32 GB 2400 MHz DDR4, Sonoma 14.7.1 (23H222).

Definitely, this problem cannot be reproduced under normal working conditions. I am sorry for the trouble you are experiencing, but there is nothing we can do unless we can reproduce at least one of the errors you are reporting.
 
@Juan Conejero , is having 16GB of dram normal working conditions? the requirements page says so. i think most of the people having this problem have 16GB of dram. you just reported 32GB.
 
We consider 16 GB under reasonable limits for practical image processing requirements. See the System Requirements page, RAM section, which we have updated today.

However, the problem reported here cannot be caused by insufficient memory. That does not make any sense because thin plate splines have small memory requirements in the range of several megabytes at most. The new DDM surface splines require more memory than the old traditional splines, but only several hundred kilobytes more. This cannot make any practical difference.

To be honest, I have no idea of what's happening here. All of the images uploaded for testing can be solved perfectly on all platforms, on all machines, all the time. Zero issues.

We have managed to get access to two Mac machines with 16 GB and 8 GB of RAM, and will make tests on them.
 
This is strange, this same image on the first try, error. Then I tried a second time without making any changes and it resolved after 4 iterations, that's with a lot of Mac OS beach ball.

Mac mini M1 16GB RAM
PI 1.9.2 1632

Downloading the new version now.
 
We consider 16 GB under reasonable limits for practical image processing requirements. See the System Requirements page, RAM section, which we have updated today.

However, the problem reported here cannot be caused by insufficient memory. That does not make any sense because thin plate splines have small memory requirements in the range of several megabytes at most. The new DDM surface splines require more memory than the old traditional splines, but only several hundred kilobytes more. This cannot make any practical difference.

To be honest, I have no idea of what's happening here. All of the images uploaded for testing can be solved perfectly on all platforms, on all machines, all the time. Zero issues.

We have managed to get access to two Mac machines with 16 GB and 8 GB of RAM, and will make tests on them.

well i did mention this in another thread - there was some sort of memory issue in PhotometricMosaic that only manifested on macs and with lower-memory machines. the only solution there was to reduce the number of control points. given that the Javascript engine is a common component it seems like it could be related. in that situation it really didn't look like a traditional memory exhaustion problem.
 
This is strange, this same image on the first try, error. Then I tried a second time without making any changes and it resolved after 4 iterations, that's with a lot of Mac OS beach ball.

Mac mini M1 16GB RAM
PI 1.9.2 1632

Downloading the new version now.

I have a 32BG RAM and 192GB RAM Mac's. Having other applications open such as Photoshop with several frames caused memory problems on the 32 GB RAM machine. Could it be that despite it is a 16 GB RAM Mac, a significant amount of memory is being used up by other applications and far less is available for PI?
 
I have a 32BG RAM and 192GB RAM Mac's. Having other applications open such as Photoshop with several frames caused memory problems on the 32 GB RAM machine. Could it be that despite it is a 16 GB RAM Mac, a significant amount of memory is being used up by other applications and far less is available for PI?
@Hab, I dont think so. On my machines I didnt have anything else open except the normal finder and mail. Maybe I'll reboot, close mail and try several times. I have always used Mac's with PI without issue, even my lower end and older iMac from late 2015 has worked flawlessly for the most part with large projects of up to 50gb in size. So, I don't think its a memory issue. Maybe like @pfile mentioned its more related to javascript.

Jon
 
  • Like
Reactions: Hab
Hi Jon,

Thank you for uploading the image. Solved perfectly with ImageSolver 6.3.1, default parameters, PixInsight 1.9.2 Lockhart builds 1632 and 1633:

Code:
==================================================================================================
Creation time ............ 2025-01-03 20:33:41 UTC
Creation software ........ PixInsight 1.9.2 / ImageSolver 6.3.1 (macOS)
Reference catalog ........ Gaia DR3
Linear transformation matrix (world[ra,dec] = matrix * image[x,y]):
 -1.77182954e-04  -2.28126868e-07  +8.49060045e-01
 +2.36710664e-07  -1.77302638e-04  +5.65152363e-01
WCS transformation ....... DDM thin plate spline
Control points ........... 42773
Spline lengths ........... l:3881 b:3864 X:3966 Y:3916
Surface residuals ........ l:0.268 px b:0.259 px X:0.113 as Y:0.098 as
Projection ............... Gnomonic
Projection origin ........ [4787.884000 3193.893287] px -> [RA: 22 51 28.225  Dec: +57 51 13.53]
Resolution ............... 0.638 arcsec/px
Rotation ................. 0.056 deg
Reference system ......... ICRS
Observation start time ... 2024-06-12 08:54:40 UTC
Observation end time ..... 2024-08-08 06:00:20 UTC
Geodetic coordinates .....  88 47 03 W  30 23 59 N  0 m
Focal distance ........... 1212.23 mm
Pixel size ............... 3.75 um
Field of view ............ 1d 41' 50.2" x 1d 7' 56.0"
Image center ............. RA: 22 51 28.226  Dec: +57 51 13.53  ex: -0.000542 px  ey: -0.032715 px
Image bounds:
   top-left .............. RA: 22 57 56.064  Dec: +58 24 24.04  ex: -1.200147 px  ey: -1.210312 px
   top-right ............. RA: 22 45 00.986  Dec: +58 24 32.46  ex: +1.111574 px  ey: -1.383116 px
   bottom-left ........... RA: 22 57 43.461  Dec: +57 16 42.26  ex: -1.124058 px  ey: +0.188444 px
   bottom-right .......... RA: 22 45 12.282  Dec: +57 16 49.97  ex: +1.250267 px  ey: +0.163858 px
==================================================================================================

This has been on an old machine: MacBook Pro 15" 2018, 2.9 GHz 6-Core Intel Core i9, 32 GB 2400 MHz DDR4, Sonoma 14.7.1 (23H222).

Definitely, this problem cannot be reproduced under normal working conditions. I am sorry for the trouble you are experiencing, but there is nothing we can do unless we can reproduce at least one of the errors you are reporting.
Hi Juan,
Thanks for checking it out. That older machine has more memory than my 2019 MacBook Pro but as you mentioned, memory shouldn't be an issue with using the new DDM thin plate spline. Hopefully you will be able to try it out on a 16gb machine.

Jon
 
We have already made a few tests with a 16 GB MacBook Pro. ImageSolver works without problems with default parameters. We'll continue testing tomorrow, but IMO this is a machine-specific problem. More information as soon as we can perform more tests.
 
Well that might narrow things down a bit.

Do you know what your image size was?

I believe the other computers having trouble were not M1 Macs.

Jack
 
Back
Top