fixed MosaicByCoordinates Error after PixInsight 1.8.9-2 Upgrade

[aranous]

After updating to PixInsight 1.8.9-2, I'm getting an error running MosaicByCoordinates:

Aligning '/Users/ranous/Astro Processing/sh2-101 mosaic/master/masterLight_BIN-1_6252x4176_EXPOSURE-600.00s_FILTER-Ha_mono_PANEL-10_(3).xisf'

Reading image:
/Users/ranous/Astro Processing/sh2-101 mosaic/master/masterLight_BIN-1_6252x4176_EXPOSURE-600.00s_FILTER-Ha_mono_PANEL-10_(3).xisf
Loading image: w=6252 h=4176 n=1 Gray Float32
31 image properties
132 FITS keyword(s) extracted
* Loaded astrometric solution:
Creation time ............ 2023-08-15 23:00:11 UTC
Creation software ........ PixInsight 1.8.9-2 / ImageSolver 6.0 (macOS)
Reference catalog ........ Gaia DR3
Linear transformation matrix (world[ra,dec] = matrix * image[x,y]):
-3.64070671e-04 -6.37231057e-06 +1.15116849e+00
+6.32775163e-06 -3.64220709e-04 +7.40612014e-01
WCS transformation ....... Thin plate spline
Control points ........... 19479
Spline lengths ........... l:2082 b:2036 X:2100 Y:2074
Spline residuals ......... l:0.169 px b:0.160 px X:0.202 as Y:0.151 as
Projection ............... Gnomonic
Projection origin ........ [3125.395741 2087.714189] px -> [RA: 20 13 44.248 Dec: +39 11 23.12]
Resolution ............... 1.311 arcsec/px
Rotation ................. 0.987 deg
Reference system ......... ICRS
Observation start time ... 2023-08-07 09:20:48 UTC
Observation end time ..... 2023-08-07 09:30:48 UTC
Geodetic coordinates ..... 122 14 28 W 37 29 08 N 10 m
Focal distance ........... 591.52 mm
Pixel size ............... 3.76 um
Field of view ............ 2d 16' 37.1" x 1d 31' 15.2"
Image center ............. RA: 20 13 44.248 Dec: +39 11 23.12 ex: -0.018925 px ey: -0.010508 px
Image bounds:
top-left .............. RA: 20 19 43.554 Dec: +39 55 06.98 ex: -0.174959 px ey: -0.138187 px
top-right ............. RA: 20 07 53.054 Dec: +39 57 30.57 ex: +0.131257 px ey: -0.147454 px
bottom-left ........... RA: 20 19 27.893 Dec: +38 24 10.63 ex: -0.040618 px ey: +0.346058 px
bottom-right .......... RA: 20 07 52.340 Dec: +38 26 31.84 ex: +0.233701 px ey: +0.132571 px


Fast image warping
Loading control points...
Loaded 19479 control points (metadata version 1.2).
Target area: [193,0,6498,4269]
Reprojecting image: (100%)
Saving keywords...
Saving properties...
** Warning [162]: /Applications/PixInsight/src/scripts/AdP/WCSmetadata.jsh, line 1336: reference to undefined property this.ref_I_G_linear
TypeError: this.ref_I_G_linear is undefined
**********************
Error: TypeError: resWindow is null
Process aborted!!

I'm running this on an M1 Max MacBook Pro. I'm processing a 10 panel mosaic and MosaicByCoordinates is processing the panels as a set of files, not views. I tried processing just a pair of panels with the same error, so it doesn't appear to be a lack of resources issue. I also tried processing the pair as views instead of files with the same error.

 

[Zaph]

I am also getting this error, on a Windows installation (i7, lots of disk and ram).
Just doing a 2-panel mosaic, have used calculate to make sure the resolution is correct. Tried both files and views (like @aranous ) and I get the same error every time.
I did this same step yesterdaay before the upgrade with no issues, then upgraded to 1.8.9-2 and cannot get it to work.

 

[CProulx]

Same problem here with a 2 panels mosaic on a Mac Mini M2 Pro...

 

[Juan Conejero]

Bug confirmed, thank you for reporting it.

I am working to get this fixed ASAP. Sorry for the trouble.

 

[ngc1535]

Yeah... same issue here. Looking forward to this fix.
-adam

 

[MLM3]

Just found this post - same error. Glad to know it's not me since this is my 1st attempt at a mosaic

 

[Juan Conejero]

This bug has been fixed. The fix will be included in a new version of PixInsight 1.8.9-2, which we'll release next week.

If the task you are performing is urgent, you can download the fixed version of the MosaicByCoordinates script from our GitLab open-source repositories. The folder you have to download is this one:

src/scripts/AdP · master · PixInsight / PJSR · GitLab

PixInsight JavaScript Runtime

gitlab.com

Let me know if you need help to do this in case you need it.

 

[ngc1535]

This bug has been fixed. The fix will be included in a new version of PixInsight 1.8.9-2, which we'll release next week.

If the task you are performing is urgent, you can download the fixed version of the MosaicByCoordinates script from our GitLab open-source repositories. The folder you have to download is this one:

src/scripts/AdP · master · PixInsight / PJSR · GitLab

PixInsight JavaScript Runtime

gitlab.com

Let me know if you need help to do this in case you need it.

It IS urgent actually. I am tasked to give a presentation for the Telescope Live community.
THANK YOU. This helps me get back on track!!

-adam

 

[rbohart]

This bug has been fixed. The fix will be included in a new version of PixInsight 1.8.9-2, which we'll release next week.

If the task you are performing is urgent, you can download the fixed version of the MosaicByCoordinates script from our GitLab open-source repositories. The folder you have to download is this one:

src/scripts/AdP · master · PixInsight / PJSR · GitLab

PixInsight JavaScript Runtime

gitlab.com

Let me know if you need help to do this in case you need it.

Thanks for the quick response to those of us that have the issue!

 

[danoid]

Glad I wasn't imagining things, just imaging (large) things...
Waiting for fix.

 

[ngc1535]

UPDATE:

Answering my own question. Yes, you need to update the entire folder. Juan did not state all the dependencies... so (I guess) just doing a full-on clobber of everything covers the necessary adjusted files. It did work. Thanks!


Hi again,

I believe I did things correctly. I grabbed the MBC javascript and replaced the file I found in my Pixinsight installation (windows) in the .../src/scripts/ADP directory.

I still have the error though... here is the result:


Processing script file: C:/Program Files/PixInsight/src/scripts/AdP/MosaicByCoordinates.js

* Code signature verified:

script-id : MosaicByCoordinates

developer-id : PTeam

timestamp : 2023-08-14T10:44:31.640Z

Loading files metadata...

Loading control points...

Loaded 21213 control points (metadata version 1.2).

Metadata of 'windowanel1_RGB' OK.

Loading control points...

Loaded 19793 control points (metadata version 1.2).

Metadata of 'windowanel2_RGB' OK.



Optimizing the center and area of the mosaic:

Center:[287.180015,-37.512751] Dist=42.449226px Width=17297, Height=7776

Center:[287.180016,-37.512739] Dist=14.122274px Width=17289, Height=7720

Center:[287.180017,-37.512736] Dist=4.698319px Width=17287, Height=7701

Center:[287.180017,-37.512734] Dist=1.563089px Width=17286, Height=7695

Center:[287.180017,-37.512734] Dist=0.520029px Width=17286, Height=7693

Center:[287.180017,-37.512734] Dist=0.173012px Width=17286, Height=7692



----------------------

Aligning 'windowanel1_RGB'



Fast image warping

Loading control points...

Loaded 21213 control points (metadata version 1.2).

Target area: [0,0,9718,6584]

Reprojecting image: (100%)

Saving keywords...

Saving properties...

** Warning [162]: C:/Program Files/PixInsight/src/scripts/AdP/WCSmetadata.jsh, line 1336: reference to undefined property this.ref_I_G_linear

TypeError: this.ref_I_G_linear is undefined

**********************

Error: TypeError: resWindow is null



Process finished with 1 errors.

windowanel1_RGB:

TypeError: resWindow is null

Perhaps I also need to update the WCSmetadata.jsh file?

-adam

 

[ngc1535]

OK... back to Mosaic by Coordinates.
After running this script the XPIXSZ, YPIXSZ and FOCALLEN values all double.
I am not even certain these are maintained or not any longer... but some 3rd party scripts use these values (e.g. Photometric Mosaic).
The doubling of both values maintains the plate scale... so no problem. But... maybe this is a bug?

-adam

 

[arny]

downloading and copying the full path src/script/AdP into the programfiles/pixinsight path and restarting PI did the job - MosaicbyCoordinates works again!
Thanks for the quick fix!

 

[Steve Dingeldein]

This bug has been fixed. The fix will be included in a new version of PixInsight 1.8.9-2, which we'll release next week.

If the task you are performing is urgent, you can download the fixed version of the MosaicByCoordinates script from our GitLab open-source repositories. The folder you have to download is this one:

src/scripts/AdP · master · PixInsight / PJSR · GitLab

PixInsight JavaScript Runtime

gitlab.com

Let me know if you need help to do this in case you need it.

Edit: I think I figured it out. Thanks for all your work. LOVE PI.

 

[MLM3]

This bug has been fixed. The fix will be included in a new version of PixInsight 1.8.9-2, which we'll release next week.

Juan, when will the update to 1.8.9-2 build 1573 be released? Next week is here and almost gone !
Thanks.

 

[AstrGerdt]

I am not from the PI team so what I write is by no means official, just my private opinion.

But trying to push a release won't help any of us. Yes, there are problems with the current release. Yes, they need to be fixed.
But as was shown in the past versions, the pi team is working very professional and if they find they need more time for it, they probably have a valid reason for it. Pushing a release just leads to more unwanted mistakes.

CS Gerrit

 

[MLM3]

I am not from the PI team so what I write is by no means official, just my private opinion.

But trying to push a release won't help any of us. Yes, there are problems with the current release. Yes, they need to be fixed.
But as was shown in the past versions, the pi team is working very professional and if they find they need more time for it, they probably have a valid reason for it. Pushing a release just leads to more unwanted mistakes.

CS Gerrit

Gerrit I'm not trying to push a release but I did not find your answer helpful in anyway, but as you say it's just your private opinion.

Juan wrote that an update would be released next week, and since that deadline has passed I was simply asking for an update.

 

[cloudbait]

Gerrit I'm not trying to push a release but I did not find your answer helpful in anyway, but as you say it's just your private opinion.

Juan wrote that an update would be released next week, and since that deadline has passed I was simply asking for an update.

Last I heard was that he was aiming for this Saturday, and that's now pushed to Monday.

 

[MLM3]

Chris - thank you. I decided to hold off a mosaic project that's at the stage of assembly until the scripts are fixed.
I have huge admiration for the PI team, and especially that they support all major computer platforms.

 

[Rob Foster]

Thank you Juan for the quickfix not to mention your tireless efforts making this great product better- it worked for me as well and MosaicByCoordinates now working again. For others trying to do this, I selected "Download this directory" from the download icon:

On my Mac, I deleted the AdP folder from the path: Applications\Pixinsight\src\scripts, then cut pasted the new AdP into the folder. Restarted PI. Still got the warning about the large image size, but the Script worked like a charm!

Many thanks again,
Rob Foster