From Liyun.Wang.1@gsfc.nasa.gov Tue Nov 18 16:40:50 2003 Date: Fri, 20 Dec 1996 16:03:19 -0500 From: Liyun Wang Reply-To: sumer-soft@esa.nascom.nasa.gov To: SUMER software list Subject: SUMER-SOFT: SUMER Software Update Dear SUMER software contributors: Claude and I have been reorganizing our SUMER software (especially the contributed software from several users) structures for better performance and management. We would like to inform you what we have done and will do. First of all, there is a good news: We now have a WEB http server running on SUMAN1. This means that we now have the GSFC version of SUMER home page. The URL of SUMER home page at GSFC is: http://sumerwww.nascom.nasa.gov/. Currently the SUMER home page at GSFC appears the same as that at IAS except that the FITS database application does not function. One can also write his/her own home page to be served by this server. If you have any question on how to make a home page of your own, please let me know. Now the SUMER contributed software: As of now, all SUMER contributed software is written directly by the contributor to directory SCIENCE:[SOFTWARE.contributor], where "contributor" is the login name of the contributor. We are going to change the way contributed software is updated or added. The contribution software previously in SCIENCE:[SOFTWARE] as well as the software and data in SAVE$DISK:[CALIBRATION]=DRA3:[CALIBRATION] will be moved to locations defined by logical variables CONTRIB and CALIBRATION, respectively. This change will apply to the following SUMER machines: SUMOP1, SUMOP2, SUMAN1, SUMAN2, SUMAN3, SIRIUS, and ERIDAN. All software saved in CONTRIB becomes part of SUMER analysis software and is mirrored to the SolarSoftWare (SSW) tree (appeared as $SSW/soho/sumer/contrib) to be used by anyone in the solar physics community. To cope with the change, you may need to modify your own configuration and program files in the following way: change any occurrence of: to: ------------------------- --- SCIENCE:[SOFTWARE.contributor]*.* CONTRIB:[contributor]*.* SAVE$DISK:[CALIBRATION.subdir...]*.* CALIBRATION:[subdir...]*.* SAVE$DISK:[CALIBRATION]*.* CALIBRATION:[000000]*.* DRA3:[CALIBRATION.subdir...]*.* CALIBRATION:[subdir...]*.* DRA3:[CALIBRATION]*.* CALIBRATION:[000000]*.* SUMOP1$DRA3:[CALIBRATION.subdir...]*.* CALIBRATION:[subdir...]*.* You should no longer (and will not be able to) write your contribution directly to directory SCIENCE:[SOFTWARE...]. Instead, this is what you need to do: 1. Create a directory named MYCONTRIB *under your home directory*, if you don't have one yet. This is the directory where you put all your "matured" stuff for the SUMER contribution software, and this is the *only* directory (and its subdirectories, if any) that will be searched for during update. 2. If you've already made contribution (i.e., you already have stuffs in SCIENCE:[SOFTWARE] directory), copy your stuff back to your MYCONTRIB directory. Make sure that your MYCONTRIB directory contains your latest version of your contribution. 3. Please make sure that you modify your configuration and source code so that the new logical variables CONTRIB and CALIBRATION are properly referred, as we suggested above. 4. You will need to run a utility program called PUBLISH to get your stuff copied/updated to the official CONTRIB directory. You need to contact me or Claude to get access to the PUBLISH command. 5. Each time when you feel ready after you have added/modified and *fully* tested your software (under your MYCONTRIB directory), you can invoke the PUBLISH (without any argument) command to trigger a mechanism to copy your stuff to the official CONTRIB directory; this may take a couple of minutes depending on how much stuff you have contributed. If you develop/test your code under your MYCONTRIB directory, make sure that you make a cleanup at all levels of this directory tree before you invoke the PUBLISH command. Please note that it is contributor's full responsibility to make sure that his/her part of software works under the designated environment and does not affect other contributor's program. Since your contribution may be used by anyone who receives the SSW, portability of your software is an important issue. If your code depends on one or more files in a directory in CONTRIB or CALIBRATION, you should not hardwire directory/file names in your code; instead you should define logical names (i.e., environment variables) pointing to the directory in CONTRIB or CALIBRATION and use our GETENV and CONCAT_DIR routines to specify the file. For example, Klaus' TL_SUMER package may require an IDL save file named TL_SPECTRUM.RST. If we define a logical name called TL_SUMER on SUMER system pointing to CONTRIB:[WILHELM.TL], then the IDL save file can be referred to as concat_dir(getenv('TL_SUMER'), 'tl_spectrum.rst') and this specification will be system independent as long as TL_SUMER is properly defined in the system that runs that package. (On UNIX system where SSW tree is available, TL_SUMER should then be defined as $SSW/soho/sumer/contrib/wilhelm/tl.) I have some useful tips regarding how to make your code more portable and I will post them later on. If you have any problem or question, please contact us via email at Liyun.Wang@gsfc.nasa.gov or MAUREL@sirius.medoc-ias.u-psud.fr. Merry Christmas and a Happy New Year! Liyun -- ================================================================== Liyun Wang | FAX: 301-286-0264 G1 Building 26, SOHO EAF | Voice: 301-286-3126 NASA, GSFC, Code 682.3 | Liyun.Wang.1@gsfc.nasa.gov Greenbelt, MD 20771 | http://orpheus.nascom.nasa.gov/~lwang ==================================================================