›

Fasttrack Following Fail

Michael Lewis
in PixInsight
I've been happily following along with the Fasttrack videos. I've diverged a bit by running 481 light frames through WBPP just to see how long it would take. I've gotten to the Image Solver video and I've run into a conflict I can't seem to solve.

I'm using the same light frame as the one used in the video; 000001_2022_02_19_02_32_09Z_c_cc_d    .

I checked that I have all of the same settings in the script interface. I do, except the "Optimize only" Option does not exist.

I start the script and it runs. There are some discrepancies in the information in the process console like "Searching for optimal magnitude limit. Target: 17366 Stars" is different from that in the video.

The process console gets to two lines of green text, that vary from the video;
* Using an automatically calculated limit magnitude of 16.98.
* Using the automatically selected GaiaDR3_XPSD catalog.

Then has the same seed parameters as the video.

It eventually fails at

Catalog Gaia DR3 (XSPD): 53627 objects. (A different value from the video)
The next line is all red text:  ***Error: Error: StarAlignment. sensitivity( ):   numeric value out of range:  -1.

I've done as careful an analysis of the information I have as I can. When evaluating a software problem I generally start with the big red letters. I just don't know how to influence the StarAlignment. sensitivity.

All advice most welcome, and thanks in advance.

Comments

  • BlockHeadBlockHead
    Michael,

    This doesn't make sense. The "-1" parameter was valid in an earlier version of Pixinsight. Now the parameter has been changed to be 0 to 1. I do not know how you are able to do this. You are basically telling me you are using a new version of ImageSolver and an older version of PixInsight (StarAlignment). 

    I agree that ImageSolver uses StarAlignment as part of its working. I also agree with the error that "-1" is not a valid value. 

    This seems like the kind of error you need to post to the official PI forum. 
    However, we should verify you are using 1.8.9-2 and ImageSolver 6.1. 

    -the Blockhead
  • Michael Lewis
    I can verify I’m using PI version 1.8.9-2 and ImageSolver 6.1.  I plan to take this to the PI forum as advised, but I’ll add detail now and post the solution when I have one.

    Since your post, Blockhead, I’ve tried a repair reinstall and a remove and reinstall. Neither has changed any of the conditions.


  • Michael Lewis
    I found a solution, but not the cause of the problem.

    Another poster on the PixInsight Forum posted a similar result with the ImageSolver script with the same error message. The discussion never got to the point of diagnosing the problem, but the original poster posted that he found resetting the tool (the counterclockwise circular arrow at the bottom left corner of the script) resolved the issue. I did as he reported and the script works for me now. Still I wish I knew the cause of the problem.

    Now on to the next lesson for me!
  • BlockHeadBlockHead
    Yeah... "rebooting" in one form or another is always a good thing to try.
    -the Blockhead
Sign In or Register to comment.