[visad] update to VisAD library

To correct a few issues with the new Units work, the visad.jar file
has been updated today.  Here is a summary of the changes:

visad/Unit.java  revision 1.37  date: 2009/04/30 15:47:03   author: steve
 Corrected testing for equality between effectively identical units
 (i.e., ScaledUnit-s with unity scaling, OffsetUnit-s with zero offset,
 and DerivedUnit-s with one BaseUnit).


visad/ScaledUnit.java  revision 1.32  date: 2009/04/30 15:47:03   author: steve
 Corrected testing for equality between effectively identical units
 (i.e., ScaledUnit-s with unity scaling, OffsetUnit-s with zero offset,
 and DerivedUnit-s with one BaseUnit).


visad/OffsetUnit.java  revision 1.30  date: 2009/04/30 15:47:03   author: steve
 Corrected testing for equality between effectively identical units
 (i.e., ScaledUnit-s with unity scaling, OffsetUnit-s with zero offset,
 and DerivedUnit-s with one BaseUnit).


visad/LogarithmicUnit.java  revision 1.3  date: 2009/04/30 15:47:03
author: steve
 Corrected testing for equality between effectively identical units
 (i.e., ScaledUnit-s with unity scaling, OffsetUnit-s with zero offset,
 and DerivedUnit-s with one BaseUnit).


visad/Factor.java  revision 1.11  date: 2009/04/30 15:47:03   author: steve
 Corrected testing for equality between effectively identical units
 (i.e., ScaledUnit-s with unity scaling, OffsetUnit-s with zero offset,
 and DerivedUnit-s with one BaseUnit).


visad/DerivedUnit.java  revision 1.33  date: 2009/04/30 15:47:03   author: steve
 Corrected testing for equality between effectively identical units
 (i.e., ScaledUnit-s with unity scaling, OffsetUnit-s with zero offset,
 and DerivedUnit-s with one BaseUnit).


visad/BaseUnit.java  revision 1.27  date: 2009/04/30 15:47:03   author: steve
 Corrected testing for equality between effectively identical units
 (i.e., ScaledUnit-s with unity scaling, OffsetUnit-s with zero offset,
 and DerivedUnit-s with one BaseUnit).


visad/util/ThreadManager.java  revision 1.2  date: 2009/04/28 18:55:53
  author: jeffmc
 If the thread manager is only running 1 thread, i.e., sequentially,
then run the runnables in the calling thread. This minizes the
possbility of side effects due to the threading




-- 
Tom Whittaker
University of Wisconsin-Madison
Space Science & Engineering Center (SSEC)
Cooperative Institute for Meteorological Satellite Studies (CIMSS)
1225 W. Dayton Street
Madison, WI  53706  USA
ph: +1 608 262 2759