iraf 2.16 does not understand VO tables from ds9
Robert Janusz wrote on Apr 09, 2012
Small example:
and now:
But let's continue:
Once again:
So there is a problem with VO tables.
ds9: image server: M67 ; catalog gsc 2.1 ; save as VO table: ds9.xmland now:
ecl> tinfo ds9.xml
FITSIO status = 261: illegal TFORM format code
Error: binary table TFORM code is blank (ffbnfm).
Failed to write binary table header keywords (ffphbn)But let's continue:
ecl> tinfo ds9.xml
ERROR: Abnormal termination of child process 'bin$x_nttools.e'Once again:
ecl> tinfo ds9.xml
can't open ds9.xml
Warning: column found in line 11 that was not defined in first rowSo there is a problem with VO tables.
Mike Fitzpatrick wrote on Apr 09, 2012
I'm not quite sure how it is you produced the ds9.xml file, would you mind either emailing it to me directly or putting it in the anonftp at ftp://iraf.noao.edu ? Thanks.
Robert Janusz wrote on Apr 09, 2012
OK, in DS9:
(1) Analysis | Image Servers | SAO-DSS | Object: M67
(2) Analysis | Catalogs | Optical GSC 2.1
(3) [Catalog Tool:] File | Save | VOTable: ds9.xmlMike Fitzpatrick wrote on Apr 09, 2012
Looking at the problem now ....
Mike Fitzpatrick wrote on Apr 09, 2012
The problem is that the votable uses 'unsignedByte' as a FIELD type and this isn't recognized in the FITS conversion code. This is one of those bug fixes that would update all the binaries (which I'll do for the next general update), if you'd like a simple update to the NTTOOLS and VO package binaries then please just let me know what platform you're on and I'll put them in the support directory.
Robert Janusz wrote on Apr 09, 2012
IRAF installed today still does not read the ds9's xml:
tinfo ds9.xml
can't open ds9.xml
Warning: column found in line 11 that was not defined in first rowMike Fitzpatrick wrote on Apr 09, 2012
You're probably still using the (corrupted) cache file from earlier, try doing a
The file should then be readable with the latest binaries.
fcache initThe file should then be readable with the latest binaries.
Robert Janusz wrote on Apr 09, 2012
How to explain this (v2.16):
and now:
and now:
So do we have some kind of "tinfo" conflict?
vocl> tinfo http://iraf.noao.edu/votest/usno-b.xml
# http://iraf.noao.edu/votest/usno-b.xml
65 rows written to table
16 columns defined
188 header parameters written to table
215 records allocated for header parameters
16 space allocated for column descriptors
table type: fits
vocl> and now:
vocl> tables
+------------------------------------------------------------+
| Space Telescope Tables Package |
| TABLES Version 3.15 |
| |
| Space Telescope Science Institute, Baltimore, Maryland |
| Copyright (C) 2003 Association of Universities for |
| Research in Astronomy, Inc.(AURA) |
| See stsdas$copyright.stsdas for terms of use. |
| For help, send e-mail to help@stsci.edu |
+------------------------------------------------------------+
fitsio tbplot tobsolete ttools
tables> tinfo http://iraf.noao.edu/votest/usno-b.xml
# http://iraf.noao.edu/votest/usno-b.xml
65 rows written to table
16 columns defined
188 header parameters written to table
215 records allocated for header parameters
16 space allocated for column descriptors
table type: fits
tables> ttools
gtedit tabkey tcreate tiimage tprint tstat
gtpar tabpar tdelete tinfo tproduct ttranspose
imtab taextract tdiffer tintegrate tproject tunits
keypar tainsert tdump titable tquery tupar
keyselect tcalc tedit tjoin tread tximage
keytab tchcol texpand tlcol trebin txtable
parkey tcheck thedit tlinear tscopy
partab tchsize thistogram tmatch tselect
tabim tcopy thselect tmerge tsort
ttools> tinfo http://iraf.noao.edu/votest/usno-b.xml
can't open http:iraf.noao.edu/votest/usno-b.xml
Warning: Table `http:iraf.noao.edu/votest/usno-b.xml' does not exist or cannot be opened.
ttools> and now:
ttools> bye
fitsio tbplot tobsolete ttools
tables> tinfo http://iraf.noao.edu/votest/usno-b.xml
# http://iraf.noao.edu/votest/usno-b.xml
65 rows written to table
16 columns defined
188 header parameters written to table
215 records allocated for header parameters
16 space allocated for column descriptors
table type: fits
tables> So do we have some kind of "tinfo" conflict?
Mike Fitzpatrick wrote on Apr 09, 2012
The STSDAS/TABLES packages from STScI are linked against v2.14 and so are 32-bit only and don't understand the new VOTables and such. If you don't explicitly load TABLES, you use the NTTOOLS version of TABLES.TTOOLS that is a fully integrated part of v2.16 (i.e. 64-bit and VO support).
You can always do a "cl> which tinfo" to find out which version will be used or just explicitly load NTTOOLS is there is some chance for confusion.
You can always do a "cl> which tinfo" to find out which version will be used or just explicitly load NTTOOLS is there is some chance for confusion.
Last post on Apr 09, 2012