search

DeepSkyForge / GraXpert4PixInsight

Support for PixInsight GraXpert plugin.
1 stars 0 forks source link

Exit error code 2. #2

Closed Stephen2615 closed 2 months ago

Stephen2615 commented 2 months ago

I get this when trying to run the new GraXpert Process in PI. It fails and produces an error which is not much use. I am running PI ver 1.8.9-2 build 1601 if that helps.

GraXpert: Processing view: GraXpert_background_extraction_clone Writing image: w=3552 h=2406 n=3 RGB Float32 Mode denoising Status: Exit error code 2 3.439 s

It looks like it is doing something when there is a preview but I can't see anything happening. A pop up says AI denoising in progress, please wait but that is as far as it seems to go.

Increasing the Batch size doesn't do anything and its produces this.

GraXpert: Processing view: GraXpert_background_extraction_clone Writing image: w=3552 h=2406 n=3 RGB Float32 Mode denoising graxpert C:/Users/chime/AppData/Local/Temp/PixInsight.xisf -cli --command denoising -strength 1 -batch_size 16 2024-04-23 10:13:26,635 MainProcess root ERROR usage: graxpert [-h] [-ai_version [AI_VERSION]] 2024-04-23 10:13:26,636 MainProcess root ERROR [-correction [{Subtraction,Division}]] 2024-04-23 10:13:26,636 MainProcess root ERROR [-smoothing [SMOOTHING]] 2024-04-23 10:13:26,636 MainProcess root ERROR [-preferences_file [PREFERENCES_FILE]] [-output [OUTPUT]] 2024-04-23 10:13:26,637 MainProcess root ERROR [-bg] [-cli] [-v] 2024-04-23 10:13:26,637 MainProcess root ERROR filename 2024-04-23 10:13:26,637 MainProcess root ERROR graxpert: error: unrecognized arguments: --command denoising -strength 1 -batch_size 16 Status: Exit error code 2 4.675 s

DeepSkyForge commented 2 months ago

Sorry for late answer. I was on travel. Error message "graxpert: error: unrecognized arguments: --command denoising -strength 1" indicates that Process launched old GraXpert version 2.x. Could you ensure you have only 1 install of GraXpert and you have last GraXpert 3.0.0 or higher version? Please do no change batch size. Keep default value 4.

Stephen2615 commented 2 months ago

Thanks. That solved that problem. Considering there is a conflict with the two versions, it would have been helpful if the ver 3 installer has detected and removed any previous version.

DeepSkyForge commented 2 months ago

When I did the migration on windows version 3 has cancelled and replaced version 2 but maybe in some case it doesn't work. Anyway, thanks for your feedback. I close the issue. I'll write done a FAQ with common problems found by users and how to fix them.