Author Topic: Image Solver issue ....  (Read 5344 times)

Offline Komet

  • Newcomer
  • Posts: 36
Image Solver issue ....
« on: 2013 April 30 09:06:32 »
I have been trying to get Image Solving working but it always fails ....

The image Co-ordinates are correct.

The pixel size is correct

The focal length is correct.

The image is not cropped in any way. It is full frame. There is no drift on the subs so there is no loss of the full image.

I get this ....

*** Error: Unable to find an initial set of putative star pair matches
<* failed *>
*** Error: The image could not be aligned with the reference star field
*** The image could not be solved.
This is usually because the initial parameters are too far from the real metadata of the image

If I try to use a single subexposure I get this .....

Files/PixInsight/src/scripts/AdP/ImageSolver.js
*** Error [222]: C:/Program Files/PixInsight/src/scripts/AdP/WCSmetadata.jsh, line 287: TypeError: DMSangle.FromString(...) is null

Any ideas please. Thanks

Offline Andres.Pozo

  • PTeam Member
  • PixInsight Padawan
  • ****
  • Posts: 927
Re: Image Solver issue ....
« Reply #1 on: 2013 April 30 10:09:12 »
I need both images to be able to diagnose the problem.

Offline Komet

  • Newcomer
  • Posts: 36
Re: Image Solver issue ....
« Reply #2 on: 2013 April 30 10:22:51 »
Hi Andres .....

https://dl.dropboxusercontent.com/u/34779111/PI_Solve.zip

Image is of NGC7023

Pixel scale 1.33
FL: 1000mm
Pixel size 6.45 micron
1x1 (both images)

Lum.fit is a stack of 28 images ... the single sub is typical. I guide using an OAG so there is no drift. Lum.fit is full frame

Cheers

Offline Andres.Pozo

  • PTeam Member
  • PixInsight Padawan
  • ****
  • Posts: 927
Re: Image Solver issue ....
« Reply #3 on: 2013 April 30 10:45:56 »
Lum.fit solves without problems:
Code: [Select]
Image Plate Solver script version 2.0
===============================================================================
Referentiation Matrix (Gnomonic projection = Matrix * Coords[x,y]):
          +7.54919e-006          -0.0003699           +0.186724
           -0.000370237       -7.61661e-006            +0.26164
                     +0                  +0                  +1
Resolution ........ 1.333 arcsec/pix
Rotation .......... -88.800 deg (flipped)
Focal ............. 998.41 mm
Pixel size ........ 6.45 um
Field of view ..... 30' 54.9" x 23' 3.2"
Image center ...... RA: 21 01 35.313  Dec: +68 09 57.10
Image bounds:
   top-left ....... RA: 21 03 37.192  Dec: +68 25 36.22
   top-right ...... RA: 21 03 41.192  Dec: +67 54 40.66
   bottom-left .... RA: 20 59 26.621  Dec: +68 25 07.44
   bottom-right ... RA: 20 59 36.181  Dec: +67 54 12.51
===============================================================================

The other image has an unusual format in the OBJCTRA and OBJCTDEC keywords.

Offline Komet

  • Newcomer
  • Posts: 36
Re: Image Solver issue ....
« Reply #4 on: 2013 April 30 11:10:37 »
Still can't get Lum.,fit to solve ... I will persevere ...

The other image has an unusual format in the OBJCTRA and OBJCTDEC keywords.

Can you tell me why it is unusual?

Ta

Offline Andres.Pozo

  • PTeam Member
  • PixInsight Padawan
  • ****
  • Posts: 927
Re: Image Solver issue ....
« Reply #5 on: 2013 April 30 11:43:24 »
Still can't get Lum.,fit to solve ... I will persevere ...

It is VERY important to choose a good value for the "Limit magnitude" parameter. A value too low extracts too few stars from the catalog.

Quote
The other image has an unusual format in the OBJCTRA and OBJCTDEC keywords.

Can you tell me why it is unusual?
These keywords don't appear in the FITS standard. The only place where I have seen them defined is in the SBFITSEXT standard from SBIG (http://archive.sbig.com/pdffiles/SBFITSEXT_1r0.pdf). This standard is used by MaximDL and other capture packages. The format for these keywords is ’12 24 23.123’ (HH MM SS.SSS) using a space as the separator. Your image uses ":" as the separator.

Offline Komet

  • Newcomer
  • Posts: 36
Re: Image Solver issue ....
« Reply #6 on: 2013 April 30 16:09:46 »
Quote
These keywords don't appear in the FITS standard. The only place where I have seen them defined is in the SBFITSEXT standard from SBIG (http://archive.sbig.com/pdffiles/SBFITSEXT_1r0.pdf). This standard is used by MaximDL and other capture packages. The format for these keywords is ’12 24 23.123’ (HH MM SS.SSS) using a space as the separator. Your image uses ":" as the separator.

Thanks - I will pass that on to the capture software developers.

Offline georg.viehoever

  • PTeam Member
  • PixInsight Jedi Master
  • ******
  • Posts: 2132
Re: Image Solver issue ....
« Reply #7 on: 2013 May 01 03:15:06 »
...Thanks - I will pass that on to the capture software developers.
Which software did you use to capture your images?
Georg (6 inch Newton, unmodified Canon EOS40D+80D, unguided EQ5 mount)

Offline Komet

  • Newcomer
  • Posts: 36
Re: Image Solver issue ....
« Reply #8 on: 2013 May 01 04:25:33 »
Sequence Generator Pro from http://www.mainsequencesoftware.com/

I did get the stacked image to solve -  ;)

Addendum  - I can use that image and the settings to solve it and it will still fail. Retstart PI and then it will solve OK ... doesn't happen often but that does happen.  odd.
« Last Edit: 2013 May 01 05:05:40 by Komet »