Restoring Previous Versions of RHESSI Software
Daily software tar files are available for the RHESSI software on ftp://grasshopper.gsfc.nasa.gov/pub/outgoing/hessi_tar/. From these tar files you can restore a HESSI SSW software tree from the date of your choice. However, please be aware that much of the software from earlier dates will not work anymore due to changes in the data archive files. The early tar files are available anyway, for experienced users who may want to extract particular modules.
For each day there are three tar files:
hessi_yyyymmdd.tar.Z
contains $SSW/hessi/idl
hessi_dbase_yyyymmdd.tar.Z
contains $SSW/hessi/dbase
ssw_other_yyyymmdd.tar.Z
contains $SSW/gen/idl, $SSW/packages/xray,
$SSW/packages/spex, and $SSW/packages/goes
When a release is created (by promoting test files out of the atest directory), the files for the day of the release are renamed by prepending arel_xx (where xx is the release number) to the file name. For example, the Release 8.1 files are named:
arel_81_hessi_20040319.tar.Z
arel_81_hessi_dbase_20040319.tar.Z
arel_81_ssw_other_20040319.tar.Z
Listed below are instructions for restoring the software tree from one of these sets of tar files, first general instructions, and then more specific examples for Unix and Windows. We're assuming that you want to leave your current ssw installation as is, and restore the tar files into a separate, new ssw installation, e.g. /disk/ssw_rel_81 for Unix or C:\ssw_rel_81 for Windows. You can then choose which ssw installation to use by changing the definition of $SSW. Inspecting the output from the pr_path command after you enter SSW IDL will tell you which version of ssw you're using. (Of course you also have the option to delete your entire current ssw directory, and replace it with the restored version.)
Depending on how old your restored version is, you may need to copy the current filedb files to your hessi dbase directory. The filedb files contain a cross-reference between time intervals and data archive file names. The older filedb file may refer to data archive files that no longer exist.
Note that this restore procedure only overwrites modules with modules contained in the tar files. Any modules installed in SSW after the tar file was created will be in the tree, but presumably won't be called.
If you only want to restore particular modules, you can copy the tar file of interest to your computer, and extract single files. For example:
Unix:
gunzip -v hessi_20040319.tar.Z
tar -xvf hessi_20040319.tar ./aspect/pt/hsi_as_wascii.proWindows:
Open tar.Z file in WinZip or equivalent and extract a module.
General Instructions for Restoring Software Tree from Tar Files:
1. Using the SSW installation form create a new ssw installation on your computer in a new directory. Include at least hessi, spex, xray and goes (gen is always included).
2. Define $SSW to point to the new ssw location
3. Copy the three tar files corresponding to the date of the software you want to restore to your computer using anonymous ftp in binary mode.
4. Delete the hessi atest directory and its contents: $SSW/hessi/idl/atest
5. Uncompress and untar the three tar files to the correct directories as follows
6. Follow the usual instructions for copying setup.hessi_env to $SSW/site/setup and editing it
7. Unix only: re-source the ssw setup file
8. If the data archive files pointed to by this restored version of the filedb files no longer exist, ftp the current filedb files to $SSW/hessi/dbase. You can copy all of them or just the files corresponding to the months you need for Level 0 files (hsi_filedb_yyyymm.fits) and Observing Summary files (hsi_obssumm_filedb_yyyymm.fits).
UNIX example, assuming the (new) release installation will be in /disk/ssw_rel_81.
Step 1. On the ssw installation form, select new installation, set the explicit path to /disk/ssw_rel_81, select at least hessi, spex, xray, and goes, and click Generate Script. Follow the instructions to download and run the script.
Step 2.
setenv SSW /disk/ssw_rel_81
To make this definition of SSW persist after you log out, change the file that
defines SSW (.login, .cshrc, or equivalent)
Step 3.
cd $HOME
ftp grasshopper.gsfc.nasa.gov
anonymous
kim@
cd pub/outgoing/hessi_tar
binary
mget *20040319*
quit
Step 4.
rm -R /disk/ssw_rel_81/hessi/idl/atest
Step 5.
gunzip -v *20040319*
cd /disk/ssw_rel_81; tar -xvf $HOME/arel_81_ssw_other_20040319.tar
cd /disk/ssw_rel_81/hessi/idl; tar -xvf $HOME/arel_81_hessi_20040319.tar
cd /disk/ssw_rel_81/hessi/dbase; tar -xvf
$HOME/arel_81_hessi_dbase_20040319.tar
Step 6. Copy /disk/ssw_rel_81/hessi/setup/setup.hessi_env to /disk/ssw_rel_81/site/setup, and edit it
Step 7.
source $SSW/gen/setup/setup.ssw /quiet
Step 8. Copy current filedb files if necessary
Windows example, assuming the (new) release installation will be in C:\ssw_rel_81.
Step 1. On the ssw installation form, select new installation, set the explicit path to C:/ssw_rel_81, select at least hessi, spex, xray, and goes, and click Generate Script. Follow the instructions to download and run the script.
Step 2. In the .bat file that you use to start SSW IDL, change the
definition of SSW. The new line will look like:
set SSW=C:\ssw_rel_81
Step 3. Using your ftp program, connect to grasshopper.gsfc.nasa.gov via anonymous, cd to pub/outgoing/hessi_tar and retrieve the three files you want to your desktop (or anywhere).
Step 4. Navigate to C:\ssw_rel_81\hessi\idl and delete the atest directory and its contents.
Step 5. Using WINZIP, or an equivalent program, open each of the three tar.Z files
you copied in step 2,
answer 'YES' to the question 'Decompress and Open File?', and extract all the
contents to the location specified above in the general instructions for Step 4.
Be sure to set the following before extracting:
Select all files
Enable Overwrite existing files
Enable Use Folder Names
Step 6. Copy C:\ssw_rel_81\hessi\setup\setup.hessi_env to C:\ssw_rel_81\site\setup and edit it
Skip Step 7.
Step 8. Copy current filedb files if necessary