Home
Search
News
Facts
Science
Instrument
Data/Software
The RHESSI Team
Public Outreach
Presentations
Messages
Related Sites

 

Other RHESSI
Web Sites

Step #6           Adding More Instruments to an existing SSW Installation

Updated 30-May-2018, Kim Tolbert


Note: Here we assume the top directory of your SSW tree is C:\ssw. If yours is different substitute yours for C:\ssw.

There are three parts to adding an instrument or package to your SSW setup.  First you need to copy the branches for that instrument or package from the remote SSW server to your machine vis SSW_UPGRADE. Second, you need to tell SSWIDL to include those branches in the IDL PATH. And third, you need to ensure that the new branch is included for updates when you update SSW.

  1. To add the instrument or package branches to your SSW installation, type (in SSWIDL):

    ssw_upgrade, /xxx, /loud, /spawn, /passive

    where xxx is the name name of the instrument or package to add (e.g. spex or xray or vobs or hmi or ...).

  2. To tell SSWIDL to include those branches in your IDL path (and to run any startup file needed by the instrument/package), you also need to modify your SSW_INSTR definition to include the new instrument. This is usually done in the .bat file that you use to start SSWIDL (e.g. C:/ssw/site/setup/sswidl.bat).

  3. Running ssw_upgrade will install the software for the selected branch of SSW on your Windows system, but will not add it to the branches to be updated when you do your normal SSW updates (either manually running daily.bat or in your scheduled update job).  To ensure that the new package stays up to date, you should add the stanza from the C:\ssw\site\mirror\ssw_upgrade.mirror for the new package to the file C:\ssw\site\setup\ssw_install.pkg.

EXAMPLE:

For instance, to add the spex package, you could do the following:

In an SSWIDL session, type the following command:

ssw_upgrade, /spex, /loud, /spawn, /passive

When it finishes, find the stanza in C:\ssw\site\mirror\ssw_upgrade.mirror for the spex package and cut and paste it into C:\ssw\site\setup\ssw_install.pkg

#
package=_solarsoft_packages_spex
comment=ssw_upgrade__solarsoft\packages\spex
site=sohoftp.nascom.nasa.gov
remote_user=anonymous
remote_password=windows@lmsal.com
remote_dir=/solarsoft/packages/spex/
local_dir=C:\ssw\packages\spex
mode_copy=true
passive_ftp=true
use_timelocal=false
max_delete_files=99%
max_delete_dirs=99%
update_log=
compress_patt=
force_times=yes
exclude_patt=[:\?]

NOTES:

  • You might want to put the name of a log file in the 'update_log=' line to see the result of updating this branch.
  • Because of a glitch on Windows, the last package in the ssw_install.pgk file doesn't get mirrored.  Our workaround is to duplicate the last package in the file.

In your C:\ssw\site\setup\sswidl.bat file, add spex to the definition of SSW_INSTR to look something like:

set SSW_INSTR=hessi spex xray

If you want to get the compressed tar file for a package (faster than using mirror to download the package file by file),  Use anonymous ftp (or in a browser, use ftp://sohoftp.nascom.nasa.gov/solarsoft/offline/swmaint/tar/ ) to copy the tar.Z file of interest in binary mode to your desktop or any temporary location. (You can delete it when you've extracted the contents.)  Extract everything to the directory the instrument/package belongs in. You may need to create the directory for the new instrument/package. Usually the tar file name indicates the directory structure for SSW. For example, ssw_packages_spex.tar.Z should be extracted to the C:\ssw\packages directory. If you don't have the packages directory, you should create it first. Create a new stanza in the ssw_install.pkg file similar to the example above.


 

Return

 

Link to NASA Home Page

Responsible NASA Official:  Gordon D. Holman

Web Design:  Merrick Berg, Brian Dennis, Gordon Holman, & Gilbert Prevost

Heliophysics Science Division
NASA/Goddard Space Flight Center
Laboratory for Solar Physics/ Code 671
Greenbelt, MD, 20771, USA
Gordon.D.Holman@nasa.gov

Link to NASA/Goddard Home Page

+ NASA Privacy Statement, Disclaimer, and Accessibility Certification

This site last updated November 10, 2008.