Data Status

Header Body-ED
NASA GSFC: GALEX
Galaxy Evolution Explorer
 

This website is kept for archival purposes only and is no longer updated.

Site Home Page

Helpdesk

Targets

Tools

Data

Instrument & Calibration

Science

Documents

Cycle 6 Information

GALEX Project at Caltech

OBSERVATION FAQs

GALEX's orbital and observational constraints limit observations of most targets to a couple of "seasons" a year.  You can use the Visibility Tool to determine when these periods are, and to give you an idea when observations are possible.  The actual schedule is determined and uploaded a week or two ahead of the planned observations.  Status of completed observations can be found HERE.

  1. If your target was a previous Cycle snap or ToO target, it will not be observed (unless it was accepted again in a current proposal).
  2. If your target was accepted in a previous Cycle Standard or Legacy proposal, but was not observed (or did not get all the FUV time requested) see preceding paragraph.  GI data is delivered once a month to MAST. 
  3. Imaging data should be processed through the pipeline and available through MAST within 60 days of observation (grism data takes longer).  We (galexhelp) will notify you by email you when your data is available at MAST and your 6 month proprietary period begins.  It is our intent to notify you again shortly before the proprietary period ends.  The short proprietary period was mandated by HQ when the GALEX GI program was approved
  4. The entire Science Operations Group is tiny and already overworked, and we can't afford to hire anyone more to do that unless we cut the (already skimpy) GI grants.  The observations may not be obtained even when planned, due to e.g., solar weather, missing a ground station dump, or a detector shutdown.  We'd rather tell you when we know you have some data.

HOW CAN I FIND OUT THE STATUS OF A GI OBSERVATION?

The observational status files are the latest information we have.
We post both total mission (not including AIS) and GI-program-only status files. GI status files should be updated every week or so, and are generally about a week behind the observations.

Starting at the Site Home page, click on “Observation Status Files” (near bottom), which will take you to:
http://galexgi.gsfc.nasa.gov/archive/galex/MissionStatus/index.html

You can choose your format under "GI Observations - Recent Observations and Cumulative Exposures."   The .csv file usually downloads as Excel, but that will depend on your host computer applications.  The .txt  file is best for a quick look, so click on that.  It contains two separate tables.

The top table tells you what was observed in the latest interval (should be weekly), ordered by satellite eclipse number.  The bottom table tells you the status of each target.  Lately they have been sorted by target name (far right column).  The target name is constructed as  GI(cycle#)_(program#)(target#)_(yourtargetname)

HOW CAN I TELL WHAT OBSERVATIONS ARE CURRENTLY IN THE LONG-TERM GALEX PLAN, AND THE STATUS OF EACH PLANNED OBSERVATION?

You can see what is in the mission plan and determine its status by using either of two methods:

Method 1:

Use the Target Search tool: click on Tools on the sidebar, and
then on Target Obs. and Search Tool (TOAST), which takes you to

http://sherpa.caltech.edu/gips/tools/toast.html

Method 2: (does not show AIS observations):

On the status files page,

http://galexgi.gsfc.nasa.gov/archive/galex/MissionStatus/index.html

look at "All Observations..."

If you know your target’s name (GI target, say), you can just search for it by name. Target names are constructed as
(Surveyname)_(program#)(target#)_(yourtargetname)

For GI targets, the names are constructed as: (GI)(cycle#)_(program#)(target#)_(yourtargetname) , i.e. they are part of the “GI Survey”

Table column explanations are given here.   (link to All Obs status explanation)

As an example,

6073 CDFS_10 DIS d 52.90000 -27.37000 30000 23 24565 22886

indicates that the Deep Imaging Survey (DIS) field with the name CDFS_10, and with the unique GALEX planning number 6073, is in the mission plan to be observed for 23 visits totaling 30000 sec;  that it has so far been observed for 24565 sec with the NUV detector and for 22886 sec with the FUV detector.   The “d” indicates an imaging observation (“g” would be grism),

Another example,

24220 GI4_012001_PG1216p069 GII d 184.83708 6.64400 30000 11 13847 13847

indicates that in (GI imaging survey GII) the GI program 4-012, target 1, which the GI called PG1216p069, and which is in the GALEX planning database as object 23220, is planned for at least 30000sec of direct imaging.  So far, 11 visits have resulted in collecting 13847 sec of both FUV and NUV integration.

And a third,

3430 MISDR1_24209_0503 MIS d 155.58358 2.99449 -999 3 1167 1167

Object_id 3430, which was in the MIS as field MISDR1_24209_0503, was pointed at the target for 1167 sec in both FUV and NUV, but it is now considered too bright to be safely observed (the -999 indicates that it tripped an automatic detector shutdown and it will not be scheduled for any further observations.).

where you enter the coordinates of the object in question. Default is a cone search with angular diameter the size of the GALEX Field-of-View (1.2 degrees). Using the advanced option allows you to search for only certain surveys,  or in a user-selected area of the sky (rectangular area or larger cone search).  

HOW CAN I TELL WHEN A TARGET WILL BE OBSERVED?

GALEX's orbital and observational constraints limit observations of most targets to a couple of "seasons" a year.  You can use the Visibility Tool to determine when these periods are, and to give you an idea when observations are possible.  The actual schedule is determined and uploaded a week or two ahead of the planned observations.

You can see when your targets could be observed (i.e. when it is possible for GALEX to point at them), by using the visibility tool.

Click on "tools" on the sidebar, then on “Visibility Tool.”  This will take you to:

http://sherpa.caltech.edu/gips/tools/gmosvis.html

Enter the target coordinates, click “submit” and in a short time a visibility plot will appear. The default is to plot visibilities for the upcoming proposal cycle, but other times may be examined (e.g. current observing cycle) using the Advanced button.

HOW DO I KNOW WHEN MY GI TARGET WAS OBSERVED?

We (galexhelp) will notify you when your GI target has been observed, as soon as we receive an updated status file letting us know that the observation was successfully obtained, downloaded, and processed through the pipeline. 

HOW LONG A DELAY SHOULD BE EXPECTED BETWEEN OBSERVATION OF A TARGET AND ITS AVAILABILITY IN MAST?

Imaging data should be processed through the pipeline and available through MAST within 30 days of observation (grism data takes longer).  Part of this delay is because GI data is shipped from Caltech to MAST and staged by MAST once a month.  We (galexhelp) will notify you by email you when your data is available at MAST and your 6 month proprietary period begins.  It is our intent to notify you again shortly before the proprietary period ends.

You can check the status of planned GI observations using the Observational Status Files (link to Obs. Status files).  

WHAT IS THE PROPRIETARY PERIOD FOR GALEX OBSERVATIONS?

PI team data has no proprietary period.  However, the data is delivered to MAST in major data releases (GALEX Releases, or GRs) similar to those used by the SDSS.  The current plan is for yearly GRs, but this is strongly dependent on mission funding.

GI data has a proprietary period of 6 months from the date that the data is made available to the GI.  The (short) proprietary period was mandated by HQ at the time the GALEX GI program was approved and funded.  

If a GI observation contains more than one orbit of exposure time, the data delivery will include both individual observations (orbits, eclipses) and co-adds.  Each new observation will result in a new, deeper, coadded image.   Both individual observations and co-adds will become public after the 6 month proprietary time from the original delivery to MAST.

DO GI TARGETS CARRY-OVER FROM ONE CYCLE TO THE NEXT?

If your target is a Snap or ToO target, it will not be carried over – it will not be observed beyond the end of the Cycle for which it was accepted

If your target was accepted in a previous cycle Standard or Legacy proposal, but was not observed (or did not get all the FUV time requested), it will be carried over into the next cycle, and will remain in the GALEX mission plan until observations are complete. GI data is delivered once a month to MAST.   Note that there may be nearly a year’s delay before the target can be observed again, depending on its Visibility.

HOW TO GET MY PROPRIETARY GI DATA FROM MAST

This information is emailed to each GI, by the helpdesk, when the GI data is available at MAST.

    1. Obtain the username and password for your GALEX GI data, if you have not already done so.(To get your login and password call the GALEXGI helpdesk at 301 286 5689 or email - (galexhelp@heasarc.gsfc.nasa.gov)

    2. Open a terminal window or an ftp application:

    3. The following instructions are for typing in a terminal window. FTP applications will have a more sophisticated method of doing this:

    FTP-ing FILES FROM MAST

    ftp

     to galex.stsci.edu, login with your username and your password, and you will be in your GI data area

    bin

     to be sure to transfer the files as binaries

    ls

     will tell you all the files

    cd 

     foldername to change directories (folders)

    ls 

     will list the files

    ls - l

     will tell you their size

    get

     GI4_063001_mytarget-name-nd-intbgsub.fits.gz will get one file

    mget *

     will get all files, one at a time

     

4. When you are finished, type exit (or quit your ftp application).

5. A list of the different types of directories (folders) and filenames, and what they contain, may be found at:

http://galex.stsci.edu/GR4/?page=ddfaq (click here)

and/or at

http://www.galex.caltech.edu/researcher/techdocs.html (click here)

Generally speaking, each program will have a subdirectory for each field (target).  Under that will be directories for imaging (d) or grism (g) observations.   Under that will be separate folders for each visit (orbit), if the observations are longer than one orbit.  There will also be a folder for the latest co-add of the data.  If there is only one visit (orbit), no folder will be present for co-adds.

 

 

 


Responsible NASA Official: Susan G. Neff
Curator:
J.D. Myers

NASA Privacy, Security, Notices