GraXpert 2.0 and PixInsight Script

0.00 schmelly #... · view views · 1 like
Ok Bob, I have read the thread in context again and begin to understand. First, to clarify: the GraXpert packages we provide in different versions all contain GraXpert as a standalone package with it's own user interface. That is, none of these packages relies on PixInsight or other tools to be usable. The integration of PixInsight is also part of this standalone package and is probably not relevant in this discussion. What did change from 2.0.2 to 2.2.0 is 1) the way we package GraXpert: until 2.0.2, GraXpert is basically a self extracting archive. During startup, the actual program is extracted to a temporary folder and executed from that folder afterwards. Drawbacks: slow startup time and antimalware engine have flagged the Graxpert-win64.exe as malware often Since 2.1.0, GraXpert is packaged as an .msi installer. That is, 1) you double click the downloaded .msi file. A dialog should open with which you install GraXpert to a location of your liking and 2) start the actual standalone version from that choosen location (there should be a graxpert.exe in that target location after the installation). For your convenience an entry in the Windows start menu is beeing created to ease the startup. Expected advantages: quicker startup time and hopefully less hits from antimalware engines. and 2) hopefully additional improvements regarding the ui, less bugs etc. Now to your situation Bob: the screenshot you posted indicates that the download of the .msi file did not complete at all. So, a) you need to confirm the download in your browser or b) some antimalware software on your computer blocks downloading .msi files (in this case: here we are again, yay). From outside it's hard to tell why the download does not complete. I hope this clarifies what you can and should expect after a successful download of GraXpert >= 2.1.0 and after a successful installation? Best regards David Edited ... Like

0.00

#...

· 1 like

Ok Bob, I have read the thread in context again and begin to understand.

First, to clarify: the GraXpert packages we provide in different versions all contain GraXpert as a standalone package with it's own user interface. That is, none of these packages relies on PixInsight or other tools to be usable. The integration of PixInsight is also part of this standalone package and is probably not relevant in this discussion.

What did change from 2.0.2 to 2.2.0 is 1) the way we package GraXpert:

until 2.0.2, GraXpert is basically a self extracting archive. During startup, the actual program is extracted to a temporary folder and executed from that folder afterwards. Drawbacks: slow startup time and antimalware engine have flagged the Graxpert-win64.exe as malware often
Since 2.1.0, GraXpert is packaged as an .msi installer. That is, 1) you double click the downloaded .msi file. A dialog should open with which you install GraXpert to a location of your liking and 2) start the actual standalone version from that choosen location (there should be a graxpert.exe in that target location after the installation). For your convenience an entry in the Windows start menu is beeing created to ease the startup. Expected advantages: quicker startup time and hopefully less hits from antimalware engines.

and 2) hopefully additional improvements regarding the ui, less bugs etc.

Now to your situation Bob: the screenshot you posted indicates that the download of the .msi file did not complete at all. So, a) you need to confirm the download in your browser or b) some antimalware software on your computer blocks downloading .msi files (in this case: here we are again, yay). From outside it's hard to tell why the download does not complete.

I hope this clarifies what you can and should expect after a successful download of GraXpert >= 2.1.0 and after a successful installation?

Best regards
David

Edited ...

6.08 Bob Lockwood #... · view views
Update, For some reason my windows 11 is not allowing me to download GraXpert. However, it did download on my windows 10. Looking forward to seeing it work. Like

0.00 Troy Bodrero #... · view views
I'm unable to get the installer to do anything. I'm on Windows 11, when I try to run the installer my icon spins for a second and then nothing happens. Any ideas? Troy Like

7.76 andrea tasselli #... · view views
Check it has actually installed. Like

0.00 Troy Bodrero #... · view views
It does not appear so. I have 2 windows 11 machines, it installed fine on the other one. Like

7.76 andrea tasselli #... · view views
This has a lot more to do with Windows 11 itself than anything to do with the program but you may want to check that it downloads fine and the installer isn't corrupted along the way. Also check the premissions with the .msi installer are permitting the installation itself. Like

0.00 Troy Bodrero #... · view views
Probably. I ran it from the cmd line and created a log. Can you take a look and give me your thoughts?graexpert.zip Like

0.00 Troy Bodrero #... · view views
I rebooted again, ran it from the command line. We are all good. Thanks for listening to me! Like

7.76 andrea tasselli #... · view views
Troy Bodrero: I rebooted again, ran it from the command line. We are all good. Thanks for listening to me! Great news! I had quick peep at the log file and apparently you were running two instances of the installer which were thus fighting for the required resources (and not going anywhere). Like

9.03 Jerry Yesavage #... · view views
Rainy days and I thought I would finally install all this but got this error: Just downloaded today and reads 2.2.2, not 2.2.0... too recent....? Oh, and this is todays version of PI also... Fixed by hitting wrench and auto setting path to software.... But, I wonder with how AI works if this should be run BEFORE the AI in BlurX and those products or after.... each is expecting relatively raw images? Edited ... Like

9.03

Jerry Yesavage

#...

Rainy days and I thought I would finally install all this but got this error:

Just downloaded today and reads 2.2.2, not 2.2.0... too recent....? Oh, and this is todays version of PI also...
Fixed by hitting wrench and auto setting path to software....

But, I wonder with how AI works if this should be run BEFORE the AI in BlurX and those products or after.... each is expecting relatively raw images?

Edited ...

2.11 Mau_Bard #... · view views · 2 likes
Hi @Frank Sackenheim, just wanted to inform you that after the upgrade to PI latest build, released 19.1.2024, the GraXpert PI script is no more working. This is the PI build And this is the console error message.Processing script file: C:/Program Files/PixInsight/src/scripts/Toolbox/Graxpert.js*** Error: Signature verification failed for 'GraXpert': Invalid code signature: C:/Program Files/PixInsight/src/scripts/Toolbox/Graxpert.js Thanks again for this great tool that you and your team developed, and its constant improvement - we are all grateful to you for this generous initiative! Ciao, Mau Like

2.11

Mau_Bard

#...

· 2 likes

Hi @Frank Sackenheim, just wanted to inform you that after the upgrade to PI latest build, released 19.1.2024, the GraXpert PI script is no more working.

This is the PI build

And this is the console error message.Processing script file: C:/Program Files/PixInsight/src/scripts/Toolbox/Graxpert.js*** Error: Signature verification failed for 'GraXpert': Invalid code signature: C:/Program Files/PixInsight/src/scripts/Toolbox/Graxpert.js
Thanks again for this great tool that you and your team developed, and its constant improvement - we are all grateful to you for this generous initiative!

Ciao, Mau

0.00 Mike Strieber #... · view views · 1 like
Hi @Frank Sackenheim, just wanted to inform you that after the upgrade to PI latest build, released 19.1.2024, the GraXpert PI script is no more working. This is the PI build And this is the console error message.Processing script file: C:/Program Files/PixInsight/src/scripts/Toolbox/Graxpert.js*** Error: Signature verification failed for 'GraXpert': Invalid code signature: C:/Program Files/PixInsight/src/scripts/Toolbox/Graxpert.js Thanks again for this great tool that you and your team developed, and its constant improvement - we are all grateful to you for this generous initiative! Ciao, Mau *I have the same issue. Like

0.00

Mike Strieber

#...

· 1 like

Hi @Frank Sackenheim, just wanted to inform you that after the upgrade to PI latest build, released 19.1.2024, the GraXpert PI script is no more working.

This is the PI build

And this is the console error message.Processing script file: C:/Program Files/PixInsight/src/scripts/Toolbox/Graxpert.js*** Error: Signature verification failed for 'GraXpert': Invalid code signature: C:/Program Files/PixInsight/src/scripts/Toolbox/Graxpert.js
Thanks again for this great tool that you and your team developed, and its constant improvement - we are all grateful to you for this generous initiative!

Ciao, Mau

*I have the same issue.

0.00 abaxworld5000 #... · view views · 1 like
Mike Strieber: Hi @Frank Sackenheim, just wanted to inform you that after the upgrade to PI latest build, released 19.1.2024, the GraXpert PI script is no more working. This is the PI build And this is the console error message.Processing script file: C:/Program Files/PixInsight/src/scripts/Toolbox/Graxpert.js*** Error: Signature verification failed for 'GraXpert': Invalid code signature: C:/Program Files/PixInsight/src/scripts/Toolbox/Graxpert.js Thanks again for this great tool that you and your team developed, and its constant improvement - we are all grateful to you for this generous initiative! Ciao, Mau *I have the same issue. Same problem in macOS, should not upgrade until it's fixed Like

0.00

abaxworld5000

#...

· 1 like

Mike Strieber:
Hi @Frank Sackenheim, just wanted to inform you that after the upgrade to PI latest build, released 19.1.2024, the GraXpert PI script is no more working.

This is the PI build

And this is the console error message.Processing script file: C:/Program Files/PixInsight/src/scripts/Toolbox/Graxpert.js*** Error: Signature verification failed for 'GraXpert': Invalid code signature: C:/Program Files/PixInsight/src/scripts/Toolbox/Graxpert.js
Thanks again for this great tool that you and your team developed, and its constant improvement - we are all grateful to you for this generous initiative!

Ciao, Mau

*I have the same issue.

Same problem in macOS, should not upgrade until it's fixed

9.03 Jerry Yesavage #... · view views
Looks like a Mac problem. My Windows version seems to be working after I did the wrench number. Have not used this much before was on the sidelines but fixing up the system under rain clouds. Does it matter how you use it in relation to other AI programs? On the Xterminator series they want to be run first as their AI training is done on the untouched raw FITS images. Not sure if it matters for the GraXpert? I have some images in mid analysis and maybe I have one with a good gradient to test different orders of application. I do not have GradientXterminator. Like

9.03

Jerry Yesavage

#...

Looks like a Mac problem. My Windows version seems to be working after I did the wrench number.

Have not used this much before was on the sidelines but fixing up the system under rain clouds.

Does it matter how you use it in relation to other AI programs? On the Xterminator series they want to be run first as their AI training is done on the untouched raw FITS images. Not sure if it matters for the GraXpert? I have some images in mid analysis and maybe I have one with a good gradient to test different orders of application. I do not have GradientXterminator.

0.00 pterodyne #... · view views
No longer working on Linux either after the update. In my case I had to do a fresh install, but it no longer appears in scripts. Before I just had to make sure the repository had a trailing slash to make it work (which could be true for all OS, not sure). Like

0.00 abaxworld5000 #... · view views · 1 like
Jerry Yesavage: Looks like a Mac problem. My Windows version seems to be working after I did the wrench number. Have not used this much before was on the sidelines but fixing up the system under rain clouds. Does it matter how you use it in relation to other AI programs? On the Xterminator series they want to be run first as their AI training is done on the untouched raw FITS images. Not sure if it matters for the GraXpert? I have some images in mid analysis and maybe I have one with a good gradient to test different orders of application. I do not have GradientXterminator. Mike Strieber gave " C:/Program Files/PixInsight/src/scripts/Toolbox/Graxpert.js" file location, that's not a macOS or Linux directory, so seems the bug is affecting all the OS. Edited ... Like

0.00

abaxworld5000

#...

· 1 like

Jerry Yesavage:
Looks like a Mac problem. My Windows version seems to be working after I did the wrench number.

Have not used this much before was on the sidelines but fixing up the system under rain clouds.

Does it matter how you use it in relation to other AI programs? On the Xterminator series they want to be run first as their AI training is done on the untouched raw FITS images. Not sure if it matters for the GraXpert? I have some images in mid analysis and maybe I have one with a good gradient to test different orders of application. I do not have GradientXterminator.

Mike Strieber gave " C:/Program Files/PixInsight/src/scripts/Toolbox/Graxpert.js" file location, that's not a macOS or Linux directory, so seems the bug is affecting all the OS.

Edited ...

0.00 pterodyne #... · view views
Ok, I reset updates in PI and re added the repository. now it shows under toolbox, but getting the same error as everyone else:run --execute-mode=auto "/opt/PixInsight/src/scripts/Toolbox/Graxpert.js"Processing script file: /opt/PixInsight/src/scripts/Toolbox/Graxpert.js*** Error: Signature verification failed for 'GraXpert': Invalid code signature: /opt/PixInsight/src/scripts/Toolbox/Graxpert.js Edited ... Like

0.00

pterodyne

#...

Ok, I reset updates in PI and re added the repository. now it shows under toolbox, but getting the same error as everyone else:run --execute-mode=auto "/opt/PixInsight/src/scripts/Toolbox/Graxpert.js"Processing script file: /opt/PixInsight/src/scripts/Toolbox/Graxpert.js*** Error: Signature verification failed for 'GraXpert': Invalid code signature: /opt/PixInsight/src/scripts/Toolbox/Graxpert.js

Edited ...

3.61 Jeffery Richards #... · view views
[url=/users/mstrieber/]Mike Strieber[/url]=14px gave " C:/Program Files/PixInsight/src/scripts/Toolbox/Graxpert.js" file location, that's not a macOS or Linux directory, so seems the bug is affecting all the OS. Same issue on my Win11 machine. Like

2.11 Mau_Bard #... · view views
Hi @Frank Sackenheim, just wanted to inform you that after the upgrade to PI latest build, released 19.1.2024, the GraXpert PI script is no more working. This is the PI build And this is the console error message.Processing script file: C:/Program Files/PixInsight/src/scripts/Toolbox/Graxpert.js*** Error: Signature verification failed for 'GraXpert': Invalid code signature: C:/Program Files/PixInsight/src/scripts/Toolbox/Graxpert.js Thanks again for this great tool that you and your team developed, and its constant improvement - we are all grateful to you for this generous initiative! Ciao, Mau I am unfortunately a layman as regards PI script programming, but I suspect that with certain release upgrades the programmer has to register the script to PI anew. This script, if I have well understood it, is simply a bridge handing over to GraXpert the exported image and importing back in PI the corrected one. Let's see what the team answers. In the meantime, the workaround is that one can use GraXpert exporting and importing manually the images. Let me specify that the standalone GraXpert, also the recent 2.2.2 upgrade, works perfectly well, it is certainly not an issue with the program itself. Edited ... Like

2.11

Mau_Bard

#...

Hi @Frank Sackenheim, just wanted to inform you that after the upgrade to PI latest build, released 19.1.2024, the GraXpert PI script is no more working.

This is the PI build

And this is the console error message.Processing script file: C:/Program Files/PixInsight/src/scripts/Toolbox/Graxpert.js*** Error: Signature verification failed for 'GraXpert': Invalid code signature: C:/Program Files/PixInsight/src/scripts/Toolbox/Graxpert.js
Thanks again for this great tool that you and your team developed, and its constant improvement - we are all grateful to you for this generous initiative!

Ciao, Mau

I am unfortunately a layman as regards PI script programming, but I suspect that with certain release upgrades the programmer has to register the script to PI anew. This script, if I have well understood it, is simply a bridge handing over to GraXpert the exported image and importing back in PI the corrected one. Let's see what the team answers. In the meantime, the workaround is that one can use GraXpert exporting and importing manually the images.

Let me specify that the standalone GraXpert, also the recent 2.2.2 upgrade, works perfectly well, it is certainly not an issue with the program itself.

Edited ...

2.11 Mau_Bard #... · view views · 1 like
The problem has just been fixed by the developers. I have just received the PI repository update, and the whole Toolbox suite, including the GraXpert invoke script one, has been updated and works now perfectly. A big thank you to the GraXpert creators, who released so swiftly a fix! Edited ... Like

9.85 Fritz #... · view views · 2 likes
PI upgrades appear to be buggy lately. The latest upgrade is a bug fix already, indroducing new problems. Seems to be a wise idea to wait some time before upgrading. Thank you for the warning on GraXpert. A workaround I found in the PI forum: Rename or delete Graxpert.xsgn in the src\scripts\Toolbox folder to disable signature checking. CS Fritz Like

0.00 Mike Strieber #... · view views · 2 likes
"A workaround I found in the PI forum: Rename or delete Graxpert.xsgn in the src\scripts\Toolbox folder to disable signature checking." This worked for me. Like

2.11 Mau_Bard #... · view views
Fritz: PI upgrades appear to be buggy lately. The latest upgrade is a bug fix already, indroducing new problems. Seems to be a wise idea to wait some time before upgrading. Thank you for the warning on GraXpert. A workaround I found in the PI forum: Rename or delete Graxpert.xsgn in the src\scripts\Toolbox folder to disable signature checking. CS Fritz Great workaround, good to know for the future! in this specific case, the repository version has been just updated and works fine. Like

2.11

Mau_Bard

#...

Fritz:
PI upgrades appear to be buggy lately. The latest upgrade is a bug fix already, indroducing new problems. Seems to be a wise idea to wait some time before upgrading. Thank you for the warning on GraXpert. A workaround I found in the PI forum: Rename or delete Graxpert.xsgn in the src\scripts\Toolbox folder to disable signature checking.

CS Fritz

Great workaround, good to know for the future!
in this specific case, the repository version has been just updated and works fine.

9.03 Jerry Yesavage #... · view views
Seems OK in my Windows system. Like

0.00 Steven James #... · view views
Hello - since the latest update I receive the following error message in PixInsight when trying to run GraXpert: --------- run --execute-mode=auto "C:/Program Files/PixInsight/src/scripts/Toolbox/Graxpert.js" Processing script file: C:/Program Files/PixInsight/src/scripts/Toolbox/Graxpert.js *** Error: Signature verification failed for 'GraXpert': Invalid code signature: C:/Program Files/PixInsight/src/scripts/Toolbox/Graxpert.js --------- GraXpert 2.2.2 is installed. Am running Windows 11. Package information for Toolbox shows as: Package type : Script Title : PixInsight Utility scripts Repository : https://www.ideviceapps.de/PixInsight/Utilities/ File name : 20240121-PixInsightToolbox-Package.zip Release date : 2024-01-21 00:00:00 Install date : 2024-01-22 04:08:02 Any help would be greatly appreciated. Thanks. Like

0.00

Steven James

#...

Hello - since the latest update I receive the following error message in PixInsight when trying to run GraXpert:

---------

run --execute-mode=auto "C:/Program Files/PixInsight/src/scripts/Toolbox/Graxpert.js"

Processing script file: C:/Program Files/PixInsight/src/scripts/Toolbox/Graxpert.js
*** Error: Signature verification failed for 'GraXpert': Invalid code signature: C:/Program Files/PixInsight/src/scripts/Toolbox/Graxpert.js

---------

GraXpert 2.2.2 is installed. Am running Windows 11.

Package information for Toolbox shows as:

Package type : Script
Title        : PixInsight Utility scripts
Repository   : https://www.ideviceapps.de/PixInsight/Utilities/
File name    : 20240121-PixInsightToolbox-Package.zip
Release date : 2024-01-21 00:00:00
Install date : 2024-01-22 04:08:02

Any help would be greatly appreciated. Thanks.

	Distinct awarded users	Total awarded images
Image of the day
Top picks
Top pick nominations

	Image of the day	Top pick	Top pick nominations	Total submitted
Deep sky
Solar system
Extremely wide field
Star trails
Northern lights
Noctilucent clouds
Landscape

	Image of the day	Top pick	Top pick nominations	Total submitted
Backyard
Traveller
Own remote observatory
Amateur hosting facility
Public amaeteur data
Professional, scientific grade data
Mix of multiple sources
Other
Unknown

Image Index:

Contribution Index (beta):

GraXpert 2.0 and PixInsight Script Steffen Hirtle GraXpert · Frank Sackenheim · ... · 153 · 10954 · 15

Image Index:

Contribution Index (beta):

GraXpert 2.0 and PixInsight Script Steffen Hirtle GraXpert · Frank Sackenheim · ... · 153 · 10954 · 15

Sorry

Sorry

Sorry :-(

Sorry

Sorry

Sorry

Sorry :-(

Sorry

Sorry

Sorry

Sorry :-(

Sorry

Sorry

Sorry

Sorry :-(

Sorry

Sorry

Sorry

Sorry :-(

Sorry

Sorry

Sorry

Sorry :-(

Sorry

Sorry

Sorry

Sorry :-(

Sorry

Sorry

Sorry

Sorry :-(

Sorry

Sorry

Sorry

Sorry :-(

Sorry

Sorry

Sorry

Sorry :-(

Sorry

Sorry

Sorry

Sorry :-(

Sorry

Sorry

Sorry

Sorry :-(

Sorry

Sorry

Sorry

Sorry :-(

Sorry

Sorry

Sorry

Sorry :-(

Sorry

Sorry

Sorry

Sorry :-(

Sorry

Sorry

Sorry

Sorry :-(

Sorry

Sorry

Sorry

Sorry :-(

Sorry

Sorry

Sorry

Sorry :-(

Sorry

Sorry

Sorry

Sorry :-(

Sorry

Sorry