Annotation script

[mschuster]

Andres,
FYI: maybe I have an old version of your script, but in my installed version v1.11 I am getting an error on line 1597 when I select 'Generate Overlay'. A fix seems easy by making 'currentItem' a function parameter.
Thanks,
Mike

[mschuster]

Feature request: Log number of catalog objects whose coordinates actually lie within the bounds of the image. The current logged catalog sizes are sometimes a fair bit larger than the actual number of objects visible (example, 547 PGC's logged but only 169 visible).
Thanks,
Mike

[Andres.Pozo]

Feature request: Log number of catalog objects whose coordinates actually lie within the bounds of the image. The current logged catalog sizes are sometimes a fair bit larger than the actual number of objects visible (example, 547 PGC's logged but only 169 visible).

FYI: maybe I have an old version of your script, but in my installed version v1.11 I am getting an error on line 1597 when I select 'Generate Overlay'. A fix seems easy by making 'currentItem' a function parameter.

I have fixed the bug and implemented the feature. They will be available the next time that I release a new version.
Thanks for your feedback.

[dgruber]

That´s true, a real masterpiece. Franz(iii)

[Yuriy Toropin]

It looks like really great!

Unfortunately, sometimes ImageSolver fails on widefield shots...
Example is here, surrounding of the Cats Paw in Scorpius, it is solved by Astrometry.net (see comments on Flickr), but unfortunately I can't solve it with ImageSolver...
Direct link to 100% resolution, lens with 105mm focus, pixel size is  6.05um x 6.05um...

Any ideas/advices how to handle it?

Thanks a lot,
   Yuriy

[Andres.Pozo]

It looks like really great!

Unfortunately, sometimes ImageSolver fails on widefield shots...
Example is here, surrounding of the Cats Paw in Scorpius, it is solved by Astrometry.net (see comments on Flickr), but unfortunately I can't solve it with ImageSolver...
Direct link to 100% resolution, lens with 105mm focus, pixel size is  6.05um x 6.05um...

Any ideas/advices how to handle it?

Thanks a lot,
   Yuriy

The image gets solved without problems using these parameters as starting point:

• RA: 17h 0' 0"
• Dec: 36º 0' 0" S
• Focal: 105mm
• Pixel size: 6.03
• Local Catalog, limit magnitude 8
• Star sensitivity: -1

Code: [Select]

Image Plate Solver script version 1.6
===============================================================================
Referentiation Matrix (Gnomonic projection = Matrix * Coords[x,y]):
        -0.003305025416     -0.000073618119     +4.452665516961
        +0.000074914137     -0.003304354484     +6.314173055633
        +0.000000000000     +0.000000000000     +1.000000000000
Resolution ........ 11.900 arcsec/pix
Rotation .......... 1.293 deg
Focal ............. 104.52 mm
Pixel size ........ 6.03 um
Field of view ..... 8d 36' 3.5" x 12d 47' 56.4"
Image center ...... RA: 17 13 04.984  Dec: -36 17 39.74
Image bounds:
   top-left ....... RA: 17 33 25.458  Dec: -29 55 18.11
   top-right ...... RA: 16 54 04.586  Dec: -29 44 34.37
   bottom-left .... RA: 17 35 31.303  Dec: -42 37 26.17
   bottom-right ... RA: 16 49 11.382  Dec: -42 24 51.84
===============================================================================


[Yuriy Toropin]

Thanks a lot, Andres!
It works for me with these parameters also. Cool!
...
Looks like the major difference is "limit magnitude 8" vs "limit magnitude 12" set by default...
Any mnemonic rule which limit magnitude should be used?

Thanks a lot again,
   Yuriy

PS: it will be great if the latest version of script will be available in the first post of the theme so it will be really easy to find them. Or - have I missed something?

[pfile]

by the way i had the idea to use the astrometry.net code to solve images and then use the solution provided by that program to drive the annotation script. i have not had time to really understand why it does not work, but the problem would seem to be with solve-field itself. the FITS file it produces with the solution in the header has been mirrored on one axis and needless to say if you annotate the original image with this solution the results are incorrect. anyway, at some point i'll get some free time and look at it.

[Andres.Pozo]

PS: it will be great if the latest version of script will be available in the first post of the theme so it will be really easy to find them. Or - have I missed something?

When I have a little time I will start a new thread with the instructions and tips and i will ask Juan to pin it. Anyway, the last version is available through the update system.

[Yuriy Toropin]

It will be great, thanks a lot, Andres!

[emidai]

The image gets solved without problems using these parameters as starting point:

• RA: 17h 0' 0"
• Dec: 36º 0' 0" S
• Focal: 105mm
• Pixel size: 6.03
• Local Catalog, limit magnitude 8
• Star sensitivity: -1

Hello, I have a question.
The parameters of Dec and RA, what object you chose? or,  is there any program that computes these coordinates of the center?

Thanks

[Andres.Pozo]

Hello, I have a question.
The parameters of Dec and RA, what object you chose? or,  is there any program that computes these coordinates of the center?

Thanks

The script computes the exact coordinates of the center. It is not a blind solver so you have to input in the dialog a starting point, the more near the center the better. These starting coordinates can be got from the telescope coordinates in the FITS header, with the "search" dialog or with whichever method you could.
When you take a photo you usually know what are you pointing at. You only have to find the coordinates using the wikipedia, wikisky, StarryNight or any other source.

[marekc]

I have been trying to get the Image Solver script to work on an image of the Leo Triplet, but the script fails, unfortunately.

I have put in the coordinates of M65, and the focal length and pixel size of my imaging system. It can't seem to `find an initial set of putative star pair matches'. Do I need to input the exact coordinates of the center of my frame?

I'm probably making some sort of simple mistake, but I'm not sure what it is. Does it matter if my image is linear or stretched? I don't think I have a mirror-flip in my image, either.

- Marek

[marekc]

Got it!

I used the coordinates of a star close to the center of my FOV. (I got the coordinates and the exact epoch from SkySafari Pro 3 on my iPad.) That allowed ImageSolver to plate-solve my image quite nicely. The Annotation script then overlaid the data sets, and it looks quite nice!

Thank you very much for such a nice script!

- Marek

[oldwexi]

Hi Andres!
The GSC2.3 catalog at Vizier has a field called "Class". Its either 0 or 3. (0 for stellar and 3 for nonstellar)
Is there a possibility to imbedd the access to this catalog in the annotation script?
The advantage i see is that it would enable to notate galaxies which are much weaker than those in the PGC catalogue
by using the Class 3 data of the GSC2.3 catalogue.

We produced an image of the ComaCluster where there are many galaxies between Mag19 and 20.
I could only notate a part of them. I downloaded the area from the GSC2.3 catalog into Excel
and could annotate the fainter galaxies. But, despite the excel file covers the whole area,
the annotation annotes only a triangel in the upper middle part of the image. Probably user error...

Using the comfort of annotation with GSC2.3 for the faint galaxies instead of my manual download, convert
and error in handling would be great.

Thanks again for such a wonderful script already!!

Aloha
Gerald