On Jan 25, 2011, at 6:32 AM, Serge Correia wrote:
> Thanks, the task autoastrom seems to work now with the command line (at least it goes through without errors) :
>
>
> However in Gaia the task does not complete and ends up with an error :
>
> --I Iteration 10...
> --I Matching position lists...
> --I Matched 96 objects between catalogues.
> --I Wrote GaiaAutoAstSolutionPos1.ASC to disk, storing matched objects.
> --I Running ASTROM to generate astrometric solution.
> --I Wrote GaiaAutoAstSolution5.fits to disk, keeping FITS headers.
> --I ASTROM determined a 6-parameter fit.
> --I RMS of current fit: 0.52497 arcseconds.
> --I Difference to previous RMS: 0.00000 arcseconds.
> --I Updated WCS of objects in detected object catalogue.
> after#90137 (bgexec): can't unset "::visibilityState(.gaia1.shelp.l3)": no such element in array
> while executing
> "unset ::visibilityState(.gaia1.shelp.l3)"
>
>
The fit fails for me if I let it use the default RA/Dec centre values when I pop up the "Simple Auto Astrometry" widget but works fine if I check "Initial WCS from image". I think there might be some corruption of parameters when passing the explicit ra,dec values to the autoastrom command line tool.
I do get the same answer as you though so autoastrom is working in gaia in your example. I have no idea what the visibilityState() error is complaining about.
>
>
> Additionally, both at the end of the task run in Gaia and when I try to search and plot the 2MASS catalog in Gaia (Data-Servers-->Catalogs) in order to check the astrometric solution of the image (written by the task run from the command line) I got the following error :
>
> Error: wrong # args: should be ".gaia1.image.imagef.canvas create oval coords ?arg arg ...?"
I also don't get that error. Once autoastrom completes GAIA automatically overlays the star positions on the image using the output catalogue.
Luca will test the namaka build (I'm using the current dev version) to see if he can reproduce the problem.
--
Tim Jenness
|