#!/bin/csh -f 
#
# HESSI Environment Variable Setup File
# 
# The complete list of HESSI environment variables necessary for 
# running the HESSI software are in this file, which is originally 
# located at $SSW/hessi/setup/setup.hessi_env.  Do NOT edit this 
# original file.
#
# Users should copy this file to their local $SSW/site/setup directory 
# (and/or $HOME directory on Unix) and edit it as described below (below the
# dashed line) for their site.  When you run SSW IDL, the $SSW/site/setup 
# version will override the $SSW/hessi/setup version.
#
# The $SSW/site/setup files are not overwritten when you do an SSW update.
#
# Three environment variables must be defined elsewhere before this file
# is executed:
#   SSW - should point to the root of your ssw tree, e.g. c:\ssw
#   HESSI_PATH - should point to $SSW\hessi or $SSW\hessi\release
#   SSWDB  - should point to your SSWDB root directory
#            Note: As of Sept, 2001, SSWDB is not being used. It doesn't matter
#            what it is set to.
#   On Unix, they should be defined in your .login file prior to the
#      execution of the SSW setup file.
#   On Windows, they should be defined in your $SSW/site/setup/sswidl.bat
#
# Modifications:
#   8-Dec-2000, Kim Tolbert to show commented-out examples.
#   13-jun-2001, jmm, jimm@ssl.berkeley.edu, with final
#          versions of archive directories
#   20-Jun-2001, Kim Tolbert.  Define SSW_HESSI to HESSI_PATH, change order of
#     setenv's and add comments so user can easily edit this file for their 
#     site-specific setup.
#   10-Apr-2002, Kim Tolbert.  Added HSI_DATA_USER and HSI_USE_SIM

#-------------------------------------------------------------------------------------

# EDIT the following line to point to the root of the directory 
# containing the HESSI level 0 data files
setenv HSI_DATA_ARCHIVE /hessi_data/test_data 

# EDIT the following line to point to a local directory where level 0 data
# files will automatically be copied if necessary.  If HSI_DATA_ARCHIVE points
# to a local directory (not an NFS-mounted file system), then HSI_DATA_ARCHIVE
# and HSI_DATA_USER can point to the same directory.
setenv HSI_DATA_USER ""

# REMOVE the following lines  (since the paths are relative,
# they will be defined correctly in the $SSW/hessi/setup version).
setenv SSW_HESSI                $HESSI_PATH
setenv SSWDB_HESSI              $SSW_HESSI/dbase
setenv HSI_FILEDB_ARCHIVE       $SSW/hessi/dbase
setenv HSI_FLARE_LIST_ARCHIVE   $SSW/hessi/dbase
setenv HSI_CLK_DELTA_DIR        $SSW/hessi/dbase
setenv HSI_GRID                 $SSWDB_HESSI/grid_resp
setenv HSI_SPEC                 $SSWDB_HESSI/spec_resp
setenv HSI_GEN                  $SSWDB_HESSI
setenv HSI_SOH                  $SSWDB_HESSI/soh
setenv HSI_SIMS                 $SSWDB_HESSI/sims
setenv HSI_ASPECT               $SSWDB_HESSI/aspect
setenv HSI_CATALOG_ARCHIVE      $SSWDB/hessi
setenv HSI_DOC			$SSW/hessi/doc
setenv HSI_USE_SIM              false

# UNCOMMENT the following line and EDIT to point to where the 
# synoptic data should be stored.  Or you may prefer to define
# USER_SYNOP_DATA in your personal IDL startup file.  If left
# undefined, synoptic data will be stored in your working directory.
#setenv USER_SYNOP_DATA /hessi_data/synoptic