John Rainnie's CDS/EIS Co-Observations Pages

Introduction

For each CDS observation (since the launch of Hinode in Nov 2006) check whether EIS was observing at the same time and within the same FOV. For those observations which intersect in time and FOV, compile a list and populate a webpage with that list (possibly with a pointing image). In this way, CDS or EIS observers will be easily able to identify corresponding observations made by the other instrument.

Method

Use the CDS headcat array of structures (created at RAL, daily) as the reference data set.

Since the 2 datasets are on different machines, we need to think about the best way of doing this. I propose to exploit the CDS headcat (IDL) save files. These are updated every day as new CDS FITS files are brought to RAL, on the solar machine. These files are organised into years, and contain arrays of structures - representing the FITS file headers. They contain the required information (time and FOV) for each CDS raster observation.

However, the actual job will run on the hinode-ops machine, where the EIS data resides. So the first challenge is to transfer the CDS headcat files there, and configure the headcat software to access them. No mean feat!

CDS Headcat Files and Software

1. Location of CDS Headcat files

The CDS headcat files exist on the solar machine;

/sohos1/cds/soft/lrg_data/headcat/cds_header_cat.06
/sohos1/cds/soft/lrg_data/headcat/cds_header_cat.07
/sohos1/cds/soft/lrg_data/headcat/cds_header_cat.08
/sohos1/cds/soft/lrg_data/headcat/cds_header_cat.09
and may be accessed by running the IDL routine headcat.pro. For example, to access observations from 2009;
IDL> headcat , cds_cat , year = 2009
where cds_cat is an array of structures.

2. Transferring CDS headcat files to hinode-ops

I have written a perl script on my account on hinode-ops ( ~/bin/update_headcat_cds.pl) that copies over from solar (using scp) the files listed above (in "Location of CDS Headcat Files"), and saves them in a directory ~/headcat. Note that if these files already exist there, they will be deleted first before copying them over from solar.

Until I figure out some clever way of packaging the required files into a directory, we pull these files individually, so I'll be asked for the password to the solar machine for each file (presently 4).

3. Running the CDS headcat software on hinode-ops

In order to run the CDS headcat software on hinode-ops I've had to;

  1. set an environment variable in my personal idlstart.pro file, viz;
    SETENV,'CDS_HEAD_CAT=$HOME/headcat_cds'
  2. Copy an out-of-date version of "headcat.pro" to my home directory. It only went up to year 2007 (using an awful CASE statement) so I modified it to include 2008 and 2009. Also, to make sure this version is called, I added to (the bottom) of my personal idlstart.pro file the line;
    .compile $HOME/headcat

4. Status

This has been completed successfully, as is evident from the fact that I can run the software on hinode-ops, and that a comparison of the headcat structures obtained on both machines reveals that they are identical.

EIS Headcat Files and Software

1. EIS Headcat files Environment Variable

As for the CDS version, I put this in my personal idlstart.pro file;
SETENV,'EIS_HEAD_CAT=$HOME/headcat_eis'
which points to the EIS headcat files.

2. Construction of EIS Headcat files

This is a biggie! See here.

3. Location of EIS Headcat files

The EIS headcat files exist on the hinode-ops machine;

/users/jrainnie/headcat_eis/eis_header_cat.06
/users/jrainnie/headcat_eis/eis_header_cat.07
/users/jrainnie/headcat_eis/eis_header_cat.08
/users/jrainnie/headcat_eis/eis_header_cat.09
and may be accessed by running the IDL routine eis_headcat.pro. For example, to access observations from 2009;
IDL> eis_headcat , eis_cat , year = 2009
where eis_cat is an array of structures.

4. Status

This has been completed successfully.

Setup

Created by John Rainnie on 26-Aug-2008