The usage of cdsskymatch
is
stilts <stilts-flags> cdsskymatch ifmt=<in-format> istream=true|false icmd=<cmds> ocmd=<cmds> omode=out|meta|stats|count|checksum|cgi|discard|topcat|samp|plastic|tosql|gui out=<out-table> ofmt=<out-format> ra=<expr> dec=<expr> radius=<value/arcsec> cdstable=<value> find=all|best|best-remote|each|each-dist blocksize=<int-value> maxrec=<int-value> compress=true|false serviceurl=<url-value> usemoc=true|false presort=true|false fixcols=none|dups|all suffixin=<label> suffixremote=<label> [in=]<table>If you don't have the
stilts
script installed,
write "java -jar stilts.jar
" instead of
"stilts
" - see Section 3.
The available <stilts-flags>
are listed
in Section 2.1.
For programmatic invocation,
the Task class for this
command is uk.ac.starlink.ttools.task.CdsUploadSkyMatch
.
Parameter values are assigned on the command line as explained in Section 2.3. They are as follows:
blocksize = <int-value>
(Integer)
At time of writing, the maximum upload size is 100Mb (about 3Mrow; this does not depend on the width of your table), and the maximum return size is 2Mrow.
Large blocksizes tend to be good (up to a point) for reducing the total amount of time a large xmatch operation takes, but they can make it harder to see the job progressing. There is also the danger (for ALL-type find modes) of exceeding the return size limit, which will result in truncation of the returned result.
[Default: 50000
]
cdstable = <value>
(String)
II/246/out
"
for the 2MASS Point Source Catalogue)
or "simbad
" to indicate SIMBAD data.
See for instance the TAPVizieR table searching facility at
http://tapvizier.u-strasbg.fr/adql/
to find VizieR catalogue identifiers.
compress = true|false
(Boolean)
gzip
",
see RFC 2616).
This does not guarantee that compression will happen
but if the service honours this request it may result in
a smaller amount of network traffic
at the expense of more processing on the server and client.
[Default: true
]
dec = <expr>
(String)
find = all|best|best-remote|each|each-dist
(UserFindMode)
all
: All matchesbest
: Matched rows, best remote row for each input rowbest-remote
: Matched rows, best input row for each remote roweach
: One row per input row, contains best remote match or blankeach-dist
: One row per input row, column giving distance only for best matchall
mode
is symmetric between the two tables.
Note also that there is a bug in
best-remote
matching.
If the match is done in multiple blocks,
it's possible for a remote table row to appear matched against
one local table row per uploaded block,
rather than just once for the whole result.
If you're worried about that, set
blocksize
>=
rowCount.
This may be fixed in a future release.
[Default: all
]
fixcols = none|dups|all
(Fixer)
none
: columns are not renameddups
: columns which would otherwise have duplicate names in the output will be renamed to indicate which table they came fromall
: all columns will be renamed to indicate which table they came fromsuffix*
parameters.
[Default: dups
]
icmd = <cmds>
(ProcessingStep[])
in
,
before any other processing has taken place.
The value of this parameter is one or more of the filter
commands described in Section 6.1.
If more than one is given, they must be separated by
semicolon characters (";").
This parameter can be repeated multiple times on the same
command line to build up a list of processing steps.
The sequence of commands given in this way
defines the processing pipeline which is performed on the table.
Commands may alternatively be supplied in an external file,
by using the indirection character '@
'.
Thus a value of "@filename
"
causes the file filename
to be read for a list
of filter commands to execute. The commands in the file
may be separated by newline characters and/or semicolons,
and lines which are blank or which start with a
'#
' character are ignored.
A backslash character '\
' at the end of a line
joins it with the following line.
ifmt = <in-format>
(String)
in
.
The known formats are listed in Section 5.1.1.
This flag can be used if you know what format your
table is in.
If it has the special value
(auto)
(the default),
then an attempt will be
made to detect the format of the table automatically.
This cannot always be done correctly however, in which case
the program will exit with an error explaining which
formats were attempted.
This parameter is ignored for scheme-specified tables.
[Default: (auto)
]
in = <table>
(StarTable)
-
",
meaning standard input.
In this case the input format must be given explicitly
using the ifmt
parameter.
Note that not all formats can be streamed in this way.:<scheme-name>:<scheme-args>
.<
" character at the start,
or a "|
" character at the end
("<syscmd
" or
"syscmd|
").
This executes the given pipeline and reads from its
standard output.
This will probably only work on unix-like systems.istream = true|false
(Boolean)
in
parameter
will be read as a stream.
It is necessary to give the
ifmt
parameter
in this case.
Depending on the required operations and processing mode,
this may cause the read to fail (sometimes it is necessary
to read the table more than once).
It is not normally necessary to set this flag;
in most cases the data will be streamed automatically
if that is the best thing to do.
However it can sometimes result in less resource usage when
processing large files in certain formats (such as VOTable).
This parameter is ignored for scheme-specified tables.
[Default: false
]
maxrec = <int-value>
(Integer)
[Default: -1
]
ocmd = <cmds>
(ProcessingStep[])
Commands may alternatively be supplied in an external file,
by using the indirection character '@
'.
Thus a value of "@filename
"
causes the file filename
to be read for a list
of filter commands to execute. The commands in the file
may be separated by newline characters and/or semicolons,
and lines which are blank or which start with a
'#
' character are ignored.
A backslash character '\
' at the end of a line
joins it with the following line.
ofmt = <out-format>
(String)
(auto)
"
(the default),
then the output filename will be
examined to try to guess what sort of file is required
usually by looking at the extension.
If it's not obvious from the filename what output format is
intended, an error will result.
This parameter must only be given if
omode
has its default value of "out
".
[Default: (auto)
]
omode = out|meta|stats|count|checksum|cgi|discard|topcat|samp|plastic|tosql|gui
(ProcessingMode)
out
, which means that
the result will be written as a new table to disk or elsewhere,
as determined by the out
and ofmt
parameters.
However, there are other possibilities, which correspond
to uses to which a table can be put other than outputting it,
such as displaying metadata, calculating statistics,
or populating a table in an SQL database.
For some values of this parameter, additional parameters
(<mode-args>
)
are required to determine the exact behaviour.
Possible values are
out
meta
stats
count
checksum
cgi
discard
topcat
samp
plastic
tosql
gui
help=omode
flag
or see Section 6.4 for more information.
[Default: out
]
out = <out-table>
(TableConsumer)
This parameter must only be given if
omode
has its default value of "out
".
[Default: -
]
presort = true|false
(Boolean)
Note this will have a couple of other side effects that may be undesirable: it will read all the input rows into the task at once, which may make it harder to assess progress, and it will affect the order of the rows in the output table.
It is probably only worth setting true for rather large (multi-million-row?) multi-block matches, where both local and remote catalogues are spread over a significant fraction of the sky. But feel free to experiment.
[Default: false
]
ra = <expr>
(String)
radius = <value/arcsec>
(Double)
serviceurl = <url-value>
(URL)
[Default: http://cdsxmatch.u-strasbg.fr/xmatch/api/v1/sync
]
suffixin = <label>
(String)
fixcols
parameter
is set so that input columns are renamed for insertion into
the output table, this parameter determines how the
renaming is done.
It gives a suffix which is appended to all renamed columns
from the input table.
[Default: _in
]
suffixremote = <label>
(String)
fixcols
parameter
is set so that input columns are renamed for insertion into
the output table, this parameter determines how the
renaming is done.
It gives a suffix which is appended to all renamed columns
from the CDS result table.
[Default: _cds
]
usemoc = true|false
(Boolean)
[Default: true
]