We are very sensitive to the fact that switching to Java for the data visualization
platform will impact folks who have done a lot of custom scripting for SeaDAS
in IDL. We are exploring the use of a Java-IDL bridge to allow the power of IDL
to be accessed from a Java-based SeaDAS. However, if your scripts manipulate
the existing IDL-based SeaDAS functions, you will probably need to modify them.
While BEAM is written in Java, scripting for it need not necessarily be Java.
The current BEAM allows scripting
are the current options. There will eventually be a scripting console
similar to the SeaDAS 'User Defined Function [mband_cmd]' (there is a similar
band manipulation function in BEAM, but it is not as full featured as the SeaDAS
To ease the transition, we intend to provide users with examples of how to replicate
operations that were done in IDL with the new version of SeaDAS.
In addition, were are reorganizing the structure and installation of the existing
SeaDAS 6.x line to allow users to maintain their SeaDAS 6.x installation (and thus
the IDL GUI version) but still be able to keep updated with changes to the data
processing code. So, users can have the advantage of improvements to the science
processing code, without the need to immediately switch to the SeaDAS 7 line
...once SeaDAS 7 is released, of course