Tabbed layout for Xamin results added to Xamin version 5.0

Xamin version 5.0 introduces the tabbed layout for grid formatted query results. This new output format replaces the current multi-window grid output. All new queries will be added to one main panel and each can be displayed by clicking its associated tab (figure 1). Tabs are labeled with the query number and mousing over the tab will display the more descriptive table name. Grids can be separated from the panel with a drag gesture, typically by clicking on the associated tab and dragging it to the desktop (figure 2). Tabs cannot be dragged back to the main panel.

figure 1

figure 2

Query visualization introduced with Xamin version 5.0

An interactive visualization component using the AladinLite data visualizer developed at the Centre de Données astronomiques de Strasbourg (CDS) has been added to Xamin grid queries. This new feature allows users to select regions visually and to display the location of observations and targets against images of the HEASARC archive holding. User can also select an area within the Aladin widow to transfer coordinates to the Xamin window for a new query.

Positional grid-formatted queries will trigger the associated region and query results to be displayed in the Aliadin Lite window (figure 1). Results will be  shown as markers on the image.

Selecting a row in the results grid highlights the element in the Aladin window and vice-versa. (1, 2). Users can immediately determine the identity of interesting objects, or pick out objects with special non-spatial characteristics. The bar below the image window (3) shows the title of the associated grid. Clicking the Aladin icon (4) on the desktop will redisplay the Aladin window and bring it to the forefront. Clicking the Update icon (5) will replace the markers in the Aladin window with currently displayed query results. Clicking the Restore icon (6) will return the Aladin window to the initial state of the displayed query results.

Different background image data can be selected from a list of missions (figure 2).

A shift-click in the Aladin window (figure 3) will encircle the clicked position (1) and transfer the center coordinates and radius of the enclosed circle to the Xamin window (2) in quick preparation for a new query.

figure 1

AladinLite Window displayed in Xamin showing image base layer selections

figure 2

figure 3

The State of Xamin and Browse

You may have noticed that a few problems have plagued the Browse and Xamin services over the last week. We have resolved many issues but anticipate that a few may still be pop up. We appreciate your patience as we implement this government mandated transition from http to https. Feel free to contact us if you have problems via the Browse Feedback form or Bug reports and Feature requests page under the Xamin Help menu.

Xamin Batch Interface issues

A new version of the jar file used for the Xamin command line interface has been released. The older version contains a URL that is no longer valid and queries using this jar file will fail.

There are two ways to fix this:

  • Users can download a new version of Xamin’s users.jar file
  • Users can use the existing users.jar but need to specify the environment variable XAMIN_CLI_URL to point to https://heasarc.gsfc.nasa.gov/xamin/cli

If you have questions please let us know. We apologize for the inconvenience.

Xamin update August 2016

For this Xamin update we have reinstated the Product Explorer for Grid queries and added bibliography table options.

  • The Product Explorer allows users to see and select the kinds of products associated with query results displayed as a grid. Look for the Product Explorer button in the top toolbar of grid table results. Documentation can be found on our Xamin Web Guide
  • Xamin now accepts two new arguments at run time:

       bibbase=xxx

    can be used to point to a table you want to use as your base zzbib table. In principle this can be a user table (but you need to log in separately).

       bibext=xxx

    can be used to point to a table you want to use to supplement the zzbib table. I.e., if you want to use mybib as your base bibliography table use

    http://heasarc.gsfc.nasa.gov/xamin?bibbase=mybib

    This assumes (but does not check) that a table mybib exists.

The Xamin Command Line Interface (CLI) and Data Products

We recently reviewed how data products are handled in the Xamin Command Line Interface and feel that some information on how to download data products might be helpful. (For help getting set up to use the CLI interface see our documentation.)

Let’s start with an example. The following command will return table results from the suzamaster table for object cen a:

java -jar users.jar table=suzamaster position="cen a" fields=name,ra,dec

The output is:

name |ra |dec |exposure
Cen A |13 25 28.68|-43 01 03.7|64675.90000
CENTAURUS_A|13 25 21.86|-43 04 19.2|62432.80000
CENTAURUS_A|13 25 19.73|-43 04 07.7|51278.70000
CENTAURUS_A|13 25 18.74|-43 03 53.6|55944.20000
CENTAURUS A|13 25 27.60|-43 01 09.0| -99.00000
CENTAURUS A|13 25 27.60|-43 01 09.0| -99.00000
Number of rows: 6
Number of columns: 4
—- Messages —-
Info: Search Radius
Search radius: 10′ from suzamaster

Info: Name resolution
Position cen a corresponds to J2000 decimal coordinates:201.365063 -43.019112
—————–

If you want to list the data products for each row add the parameter “products” to the command:

java -jar users.jar table=suzamaster position=”cen a” fields=name,ra,dec products

The output for this command is:

name |ra |dec |exposure
Cen A |13 25 28.68|-43 01 03.7|64675.90000

# Product suzaku.obs: Observation Directory
> /FTP/suzaku/data/obs/1/100005010/

# Product link.suzaxislog: Suzaku XIS Configuration Log
> query?table=suzaxislog&constraint=obsid=100005010

CENTAURUS_A|13 25 21.86|-43 04 19.2|62432.80000

# Product suzaku.obs: Observation Directory
> /FTP/suzaku/data/obs/7/704018010/

# Product link.suzaxislog: Suzaku XIS Configuration Log
> query?table=suzaxislog&constraint=obsid=704018010

CENTAURUS_A|13 25 19.73|-43 04 07.7|51278.70000

# Product suzaku.obs: Observation Directory
> /FTP/suzaku/data/obs/7/704018020/

# Product link.suzaxislog: Suzaku XIS Configuration Log
> query?table=suzaxislog&constraint=obsid=704018020

CENTAURUS_A|13 25 18.74|-43 03 53.6|55944.20000

# Product suzaku.obs: Observation Directory
> /FTP/suzaku/data/obs/7/704018030/

# Product link.suzaxislog: Suzaku XIS Configuration Log
> query?table=suzaxislog&constraint=obsid=704018030

CENTAURUS A|13 25 27.60|-43 01 09.0| -99.00000
CENTAURUS A|13 25 27.60|-43 01 09.0| -99.00000

Number of rows: 6
Number of columns: 8

—- Messages —-
Info: Search Radius
Search radius: 10′ from suzamaster

Info: Name resolution
Position cen a corresponds to J2000 decimal coordinates:201.365063 -43.019112
—————–

As you can see, if data products are available then product names and partial URLs strings are listed below each row of the table results. These URL strings can used with a command line data transfer tool (eg. wget, curl) to download data from the HEASARC server.

In this example there are two types of URLs – one type is used to download data products (eg., > /FTP/suzaku/data/obs/7/704018030/) and the other type (eg., > query?table=suzaxislog&constraint=obsid=100005010) is used to display data from related tables.

For data product downloads an example of a wget command for Unix type machines would be:

wget -q -nH -r -l0 -c -N -np -R ‘index*’ -erobots=off –-retr-symlinks –cut-dirs=1 http://heasarc.gsfc.nasa.gov/FTP/suzaku/data/obs/1//100005010/

If you are interested in what each of the wget options does take a look at this recent blog post.

If you would like to download data products at the same time that you run the java command the following Unix shell script example should work:

#!/bin/sh
java -jar users.jar table=swiftxrlog position=ngc4626 products | \
grep '>' | \
sort | \
uniq | \
sed -e "s/ > \/FTP/wget -q -nH --cut-dirs=6 -r -l0 -c -N -np -R 'index*' -erobots=off --retr-symlinks http\:\/\/heasarc.gsfc.nasa.gov\/FTP/" | \
sh

The URL string for Link Products (e.g., link.suzaxislog) can be used to view Xamin catalog results for related tables. An example of this type of command is:

wget -O suzaxislog_results “http://heasarc.gsfc.nasa.gov/xamin/query?table=ascamaster&radius=60&position=22+02+43.2,42+16+48″

The output is a list of rows from the ascamaster table for object cen a.

We will be creating a post soon with download instructions for users who may not have access to all the commands (eg, sed) used in our example shell script.

Xamin Data Products Download Commands

In addition to the option to download data products as a tar file Xamin will display a list of separate download commands. Users can then transfer individual data files from the command line or create a download script.

These download commands are listed under the Wget Commands Tab of the Products Cart as seen in this screen grab:

wgetcommands

wget is a very useful command with many, many options and it took some time to determine which options were needed to traverse the complicated HEASARC data products directory structure to find and transfer the products.

The following is one of the wget commands listed in the Products Cart.

wget -q -nH -r -l0 -c -N -np -R 'index*' -erobots=off --retr-symlinks --cut-dirs=7 http://heasarc.gsfc.nasa.gov/FTP/chandra/data/science/ao01/cat5//1828/primary/acisf01828_001N004_fov1.fits.gz

We thought some of our users might be interested in knowing exactly what these options do. We used GNU Wget online manual for most of our research.

-q: quiet mode, no output is displayed

-nH: directories created on the user’s system will not be named using the HEASARC host name

-r -10: directories will be searched recursively up to 10 levels down

-c: files only partially downloaded from a previous execution will continue to to downloaded

-N: a file will not be downloaded if a local file of the same name exists and is newer

-np: the search will not ascend up to the parent directory during recursion

-R ‘index*’: unnecessary files will not be downloaded

-erobots=off: do not observe directives from the robots.text file that might prevent downloads

–retr-symlinks: symbolic links are traversed and the pointed-to files are retrieved

–cut-dirs=N: skip N number of the components in the URL directory structure when the directory structure is created on user’s system