The process for running all MTA pipelines is essentially the same. Below we will outline this process and then follow this with sample runs for each pipeline.

Requirements

• ASCDS environment setup: see setup instructions
• IDL 5.0 or greater: see setup instructions

Procedure

1. Define items needed for running the pipeline

   {working directory} = Directory in which to run the pipeline
   {input directory} = Directory containing input data
   {output directory} = Direct to place monitoring output
   {report directory} = Directory in which to build the MTA report tree.
   {root} = Tag name for pipeline run.

   {pipeline template} = Name of pipeline template to be run.
   

   mta_monitor_static.ped = Generic monitor pipe.
   mta_monitor_state.ped = State dependent mnemonic pipeline.

2. Reset the environment variable for report directory to the desired location.
   
   • setenv MTA_REPORT_DIR {report directory}

3. Prepare directories
   
   • cd {working directory}
     If they don't exist,
   • mkdir -p {input directory}
   • mkdir -p {output directory}
   • mkdir -p {report directory}
   
   NOTE: These directories DO NOT HAVE to be together. It is assumed in these instructions that the input data is in a location the user does not want the pipeline to access directly (i.e. a storage area).
   Also, it is most likely that the REPORT directory is in some central location not related to the run directories.

4. Prepare inputs
   
   • Copy the files you want to monitor to the input directory, if necessary
     cp {input files} {input directory}

   • Make a list of files to monitor
     cd {input directory}
     ls *.fits > {root}_dat.lis
     cd {working directory}

   • OPTION: use "pset" to change any pipeline/tool parameters from their defaults.

5. Run the pipeline
   
   • pbuilder.pl -i {input directory} -o {output directory} -r {root} -t {pipeline template} > {output directory}/{root}.ped
     
   • pctr -prof {output directory}/{root}.ped -show

   pbuilder.pl fills in the pipeline template with run specifics.
   pctr executes the pipeline.

NOTE: There is a nifty script (flt_run_pipe) that reduces steps 3 and 4 to a single command.
flt_run_pipe -i {input directory} -o {output directory} -r {root} -t {pipeline template name}
You may find that preferable.

Congratulations on a (hopefully) successfull pipeline run.

Viewing the output

The pipeline produces an HTML directory tree with summary pages for each file monitored. To view this tree:

Using your Web brouser, choose "Open File" to load {report directory}/mta_days.html

Pick a day... any day (not "dayall") to get a page in outline form that
self-updates every 100 seconds.

When a link becomes active... you may browse the results

---

Samples

SIB Monitoring pipeline (mta_monitor_sib.ped) Updated  [12/31/2002]

Event Monitoring pipeline (mta_monitor_events.ped) Updated  [12/31/2002]

Gratings Monitoring pipeline (mta_monitor_gratings.ped) Updated  [12/31/2002]

ACIS CCD Monitoring Tools/pipeline Updated  [12/31/2002]

ACIS CTI Monitoring Pipeline(mta_monitor_cti.ped) Updated  [12/31/2002]

Static pipeline (mta_monitor_static.ped)

State dependent pipeline (mta_monitor_state.ped)

Gradient Monitoring pipeline (mta_monitor_grad.ped)

Trendings Analysis pipeline (mta_monitor_trends.ped)

ACA Monitoring pipeline (mta_monitor_aca.ped)

Raw Monitoring pipeline (mta_monitor_raw.ped)

COMP Monitoring Pipeline(mta_monitor_comps.ped)

---

Back