Rocket I

Page maintained by
Reine Gill

This is the release notes file for the ISDAT version 2.8.0, released 
on Dec 11, 2001. 

         This file contains:
           - release notes,
           - accessibility
           - installation notes,
           - Other READMEs and information.
           - contact information
           - acknowledgments
         To be found below.

                       Release notes for ISDAT v2.8.0

The November Wec data meeting was as always a productive week and
together with the work the weeks after it has produced some great

     - As the latest release of Ted showed some problems with
       HK data, the HouseKeeping module in 2.8.0 now is independent
       of Ted. This is not necessarily a permanent solution, though
       it may possibly be so, depending on the feedback of users. 
       You can plot the spacecraft potential from the logical instrument 
       hkeep->efw->data->ew0sppot. CAVEAT: the signal is time shifted 
       with a 10 sec delay. This is under investigation. 
     - The DWP module now has built in FFT functionality. Read the
       server/Wec/Dwp/README file for more information.
     - The Ephemeris module now uses the Fortran maglib that provides
       magnetic coordinates as well as other physical coordinate
       systems, see installation notes below and server/Wec/Eph/README.eph.
     - The Staff module is now configured though the isdat.server
       file. Read server/Wec/Staff/README_STAFF for more information.
     - Efw timing is now corrected for the group delay in the L and M
       filters. This is a change of policy to facilitate comparisons
       mainly with STAFF data.
     - The Isdat WEC server now uses a new version of Ted, the
       common unpacking routines.
     - Igr as usual contains many updates and bug fixes. A major
       update of the online help has been done.
     - ... and some other small changes, upgrades and fixes.
The overall status of the Isdat package is good. Most of the now known
problem are platform specific and thus does not block the whole
program. Probably some newer version of solaris os is the most stable
platform for running the Isdat dbh for now. Linux is also to consider a
stable platform even though there are some minor problem reports for the
moment, these will certainly be resolved in the next release.

One major problem with the CSDS module is index generation. The server
crashes when processing large amounts of cdf files. For the moment 
the best thing to do if you think about using the CSDS module probably
is to choose a smaller set of interesting cdf files. But please go ahead 
and experiment, if you manage to process >1000 cdf files I would like to 
get a note about it. 

A still remaining limitation to the WEC server is that it is
impossible to plot WEC data over NM/BM telemetry boundaries. 
This will be the main target for release 2.9.

There are no known issues regarding the Isdat kernel.

                        Accessibility of ISDAT v2.8.0

This release of Isdat contains the Wec server with all its instrument 
submodules (and of course the clients). This means that there are some 
restrictions on the accessibility of ISDAT v2.8.0 in principle you
should be a CoI on the instrument module you are interested in, 
in order to retrieve it, or otherwise have obtained the permission from 
the relevant PI. There are two major distribution channels for Isdat. 
The Isdat CVS server at:

and the different Isdat ftp sites:

Isdat releases without restricted code are distributed through:

But since this is not the case with isdat-2-8-0 it is not available at this 
site. To retrieve your copy from cvs you need a cvs account. This is manly for
Isdat developers. If you belong to this group you will find useful information 
in the cvs howto:

To retrieve you copy from ftp you need a password. To get this email
Anders Eriksson at IRFU ( (as I goes for a five weeks

                    Installation Notes for ISDAT v2.8.0

To build and install ISDAT please follow these steps:

1) Unzip and untar the "isdat-2-8-0.tar.gz" file in the directory you wish 
   the ISDAT installation to reside. To retrieve from cvs, do a:
   cvs co -r isdat-2-8-0 wec 
   or if you already have a checked out copy of Isdat:
   cvs update -r isdat-2-8-0
2) If you would like to call you isdat installation something else
   this is the time to rename it.

3) cd into the isdat_root directory.

4) Edit the file my_isdat_profile found in the scripts sub directory so the 
   variable ISDAT_HOME is correct. Then source this file.
5) cd to $ISDAT_HOME/config/cf 
   For new installations, copy site.def_DEFAULT to site.def and edit it
   to suit your needs. If you have a existing installation, compare
   your site.def to site.def_DEFAULT. there are some new stuff you
   might want to include in you existing file. Look through the macro
   variables in this file and change "NO" to "YES" if you would like 
   to have that particular resource in your Isdat build. Typical things to 
   configure are cdf, matlab, idl, gcc. If you enable a resource please set the
   paths to that resource correctly. 
   - To make use of the newly included Ephemeris maglib you must set
     HasFortran to YES (the default setting) and make sure you have
     a Fortran compiler in you system.
   - You do not have to uncomment HasGcc2 for Linux it will use gcc any way 
     (But read Linux specific information below).
   - IF YOU DO NOT HAVE CDF please remove the $ISDAT_HOME/server/Csds directory
     or rename $ISDAT_HOME/server/Csds/Init.c to something else.
   - If you build on sun and enables any special resource use the rows that are
     comment away instead of the existing ones (for idl see below).
6)   Linux specific issues.
     If you only have the gnu c compiler, gcc. You may need to edit the top of 
     $ISDAT_HOME/config/imake/makefile.ini, CC = cc should be CC = gcc.
     Soft links will also solve the above problem.
     Sun specific issues.
     The Idl API interface does currently not work correctly on Sun 64 bits 
8) cd to $ISDAT_HOME.

9) Type "make isdat" at the shell prompt.

You should see lots of build information being sent to the screen. The time to 
complete the full isdat build depends on your system, typically about 10 - 20 
min. Remember that all executables are linked to $ISDAT_HOME/bin. There is no 
"install" procedure so you may want to create system wide links to these 
binaries or at least update your PATH environment variable (source 
my_isdat_profile from one of your startup files).

If your installation does not build please go back check that the ISDAT_HOME 
variable and the $ISDAT_HOME/config/cf/site.def file is set correctly. Copy 
$ISDAT_HOME/Makefile.ini to $ISDAT_HOME/Makefile and repeat the installation 
procedure from step 4 above. You May also check the Isdat build howto:
were some additional problems are addressed.

At this point if still are unable to build the isdat system or if something in 
the installation process is unclear please contact

To run the Isdat server you can use the provided script:
It keeps the server running if it crashes. Edit it to 
source the right my_isdat_profile before using it.

ISDAT v2.8.0 should build without major modifications on all systems supported 
by itools v6.3. Empirically verified builds on:

	- Sun sparc/i386 solaris v2.5-2.8 using gcc or SUNWspro cc,
	- HP-UX 10.20. (HP-UX 11.0 will work if one sets 
	  IMAKECPP=/usr/ccs/lbin/cpp and BOOTSTRAPCFLAGS="-Dhpux")
	- Linux/redhat 7.0 with lesstif 0.92
                        Other sources of information
ISDAT/WEC module specific information is contained in the different text files 
in the Wec directory, for your convenience listed here:

Information on different ISDAT issues can be found in the "doc" directory in the
ISDAT installation root. For more general information on the ISDAT system see:

                            Contact Information

Please send bug reports, successful build reports on systems not mentioned 
here or any inquires related to the ISDAT system to "". All 
feed-back is kindly appreciated, thank you :-)    
Thanks to all ISDAT/WEC users who  helped with bug reports, source code 
contributions, advice and suggestions. It is your contributions which to put
back momentum to ISDAT/WEC development which it so desperately needed after
the Cluster I disaster. Special thanks to Simon Walker for his great
work in integrating the Fortran maglib into the Wec ephemeris module.
This provides many new coordinate systems and has given the Igr plots
a new fresh touch. Finally thanks to all other members of the Wec data 
team who are now the working engine behind the Isdat system.

Date:	011212
Author:	Tobias Eriksson,