/usr/share/doc/rsl/whats_new.html is in librsl-doc 1.43-1.2build1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 | <!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="GENERATOR" content="Mozilla/4.7 [en] (X11; U; Linux 2.2.12 i686) [Netscape]">
</head>
<body>
<a href="index.html"><img SRC="rsl.gif" height=100 width=100></a>
<hr>
<br>
<br>
<h1>
What's new?</h1>
<h2> Version 1.43:</h2>
Mostly bug fixes. See <a href="../CHANGES">CHANGES</a>.
<h2>
Version 1.42: Bug fix.</h2>
Changed scale_factor used for storing differential phase (PH) in UF from 100 to
10. The usual scale factor of 100 caused values over 327.67 to become negative
when converted to short integer.
<h2>
Version 1.41 supports WSR-88D Level II Build 12 format.</h2>
<h2>
Version 1.39 supports WSR-88D Level II Build 10 format.</h2>
<h2>
Version 1.34 supports WSR-88D Level II Build 8 format.</h2>
RSL can read both the old and new WSR-88D Level II data format.
<h2>
Version 1.33 supports WSR-88D Level II Build 5 format.</h2>
RSL can read both the old and new WSR-88D Level II data format.
<h2>
Version 1.25 release (what's new since v1.24).</h2>
Merged changes from version 1.24.1. Also, HDF routines are back
as not having them in the library caused more problems than it was worth.
But, the most significant change is that the entire package is configured
by the <b>configure</b> script (provided). Building the package is
done in two steps. This is a dramatic improvment over previous releases.
<h2>
Version 1.24.1 release (what's new since v1.24).</h2>
Removed the HDF component. Those routines are now part of gvs, where
they belong. However, basic support in <a href="RSL_anyformat_to_radar.html">RSL_anyformat_to_radar</a>
will exist for HDF -- it will still recognize an HDF file and call
<a href="RSL_hdf_to_radar.html">RSL_hdf_to_radar</a>.
RSL_hdf_to_radar is located in gvs/gvslib. To configure HDF into
RSL, specify <b>-DHAVE_TSDIS_TOOLKIT</b> in the Makefile.
<p>Added project[24] to the <a href="RSL_radar_header_struct.html">radar->h</a>
structure.
<h2>
Version 1.23 release (what's new since v1.18).</h2>
RSL now accpets the EDGE format.
KDP definition changed. It now normalizes the value based on the
radar wavelength. A bug in the RADTEC ingest routine was removed.
Other than that, mostly bug fixes that were very minor. Added <a href="RSL_color_table.html">RSL_set_color_table</a>
and <a href="RSL_color_table.html">RSL_get_color_table</a>. These
routines permit better user control of the color table.
<h2>
Version 1.18 release (what's new since v1.15).</h2>
This version adds the RADTEC format ingest routine. See <a href="RSL_radtec_to_radar.html">RSL_radtec_to_radar</a>.
RADTEC requires the use of the PKWARE Data Compression Library, available
from PKWARE, Inc., http://www.pkware.com. Also made several minor
bug fixes and the image generation was enhanced to allow generation of
images out to the range specified. Previously, image pixels
were 1km, now they are range/radius.
<h2>
Version 1.15 release (what's new since v1.14).</h2>
This version adds the RAPIC format ingest routine. See
<a href="RSL_rapic_to_radar.html">RSL_rapic_to_radar</a>.
A data truncation bug was fixed in the UF ingest. This bug only affects
the velocity data. The Lassen ingest no longer depends on (radar->h.name),
for calibration of Gunn Point data. It is now done based on time
periods of the data. Please see the <a href="CHANGES">CHANGES</a>
file for more information.
<h2>
Version 1.14 release (what's new since v1.11).</h2>
This version continues the minor bug fixes to the HDF component.
Additionally, it includes calibration for the Gunn Point radar, in Lassen
format. The distinction of Gunn Point data from other lassen
data is done by assumming the radar name (radar->h.name) is 'Gunn_Pt'.
Please see the <a href="CHANGES">CHANGES</a> file for more information.
<h2>
Version 1.11 release (what's new since v1.8).</h2>
Version 1.9 represented a bug fix to the HDF component. Version 1.10
represented a minor
<br>upgrade, mostly to the HDF component, but, other areas were modified
and that's why it is called an upgrade rather than a bug fix. Version
1.11 represents a minor bug fix release from v1.10. It only affects
the
<br>HDF components. Please see the <a href="CHANGES">CHANGES</a>
file for more detailed information regarding what changed.
<p>In version 1.10, ZDR color tables were modifed and a first draft of
the South Africa data format ingest routine was added.
<br>
<h2>
Version 1.8 release (what's new since v1.7).</h2>
Added <a href="RSL_read_these_sweeps.html">RSL_read_these_sweeps</a>.
Specify specific sweep numbers for ingest. This drastically speeds
up ingest, if you're only interested in the first or first couple of sweeps.
For example, making base scans images.
<p>Added <a href="RSL_load_color_table.html">RSL_load_zdr_color_table</a>.
<p>More HDF mods; more warning messages.
<p>The TRMM Office has fixed several bugs in the TSDIS toolkit. For proper
HDF creation, that conforming to TSDIS HDF specifications, you will need
toolkit 4.5r1.1. Toolkit 4.5r1.1 is an unofficial release; the TRMM office
will pass this out upon request.
<br>
<h2>
Version 1.7 release (what's new since v1.6).</h2>
This version fixes the lat/lon signs. Also, lat/lon are added to
each ray for UF when extended headers are available in SIGMET files.
Also, the HDF component has changed. This affects RSL_radar_to_hdf
and RSL_hdf_to_radar.
<h2>
Version 1.6 release (what's new since v1.5).</h2>
This version of RSL will work with TSDIS toolkit 4.5r1. UF now has
lat/lon stored for each ray, suitable for moving platforms. Also,
the wsr88d code does not default to KMLB.
<h2>
Version 1.5 release (what's new since v1.4).</h2>
The HDF component has changed again. This version of RSL will work with
toolkit 4.0 or toolkit 4.0.1. Version 4.0.1 is an un-official release of
the TSDIS toolkit. This version removes the temporary files created during
level 1 processing. There was only one file that changed, the file may
be obtained from the TRMM Office, upon request.
<p>One minor consistancy check was added to the wsr88d ingest; it checks
that the number of bins in a ray is reasonable. This problem usually manifests
itself from bad input files.
<h2>
Version 1.4 release (what's new since v1.0).</h2>
The HDF component is in a state of flux. The <a href="http://tsdis/tsdis/tsdistk.html">TSDIS
toolkit</a> keeps changing -- the interface keeps changing. The TSDIS toolkit
is, in the TRMM Office opinion, not stable. Their latest release is 4.0
and it has fixed many problems. One minor problem remains for level 1 processing:
temporary config files are not removed when the toolkit is closed.
<p>RSL is incorporated into a larger package called GVBOX. The latest version
of GVBOX is 1.1. GVBOX is a complete ground validation system to generate
TRMM GV products on pentium PCs running Linux. GVBOX is available on CDROM.
<p>RSL is now LGPL-ed.
<p>Added the routine <a href="RSL_select_fields.html">RSL_select_fields</a>
to reduce memory requirements upon reading data. This works very nicely
for LASSEN data where the number of fields is large, however, only 2 or
3 are needed.
<h2>
Version 1.0 release (what's new since v0.45).</h2>
Version 1.0 marks the jump from the previous stable version, version 0.45.
A few very minor bugs were encountered and repaired. But, the bulk of this
transisition is improved documentation with the addition of a Users Guide.
Additionally, the SIGMET ingest was repaired and can now read version 2
files, HDF I/O was added and the LASSEN ingest modified to read version
1.4 files. Version 1.4 LASSEN files were used during the MCTEX experiment.
Other than that, no major modifications were made. Technically, version
1.0 is a minor upgrade to RSL 0.45. But, due to the witnessed stability
of RSL, it was decided to call it version 1.0.
<br>
<h2>
Can read compressed files automatically (new since v0.41)</h2>
Transparent, to all ingest routines the capability of filtering the input
data file through the GNU gzip program for decompressing the file has been
added. This feature does not appear to slow the I/O time and, in some cases,
especially on 486 pc's, improves overall throughput time. Two generic,
internal routines, have been added: <b>compress_pipe</b> and <b>uncompress_pipe</b>.
Each routine takes a <b>FILE *</b> and redirects it through <b>gzip</b>.
Each routine returns a new <b>FILE *</b>. Wsr88d files occupy 1/10 the
disk space when compressed and the TRMM Office plans to compress wsr88d
files to CDROM and 8mm tape for overall throughput savings for the production
system. It will no longer be necessary to decompress the data before processing
level 1.
<p>Similiarly, UF output can be saved using the gzip filter. The new routine
added is <a href="RSL_radar_to_uf.html">RSL_radar_to_uf_gzip</a> which
utilizes the gzip compression filter.
<h2>
Can read stdin (new since v0.39)</h2>
A new routine is provided called <a href="RSL_uf_to_radar.html">RSL_uf_to_radar_fp</a>
which takes an open file descriptor and returns a radar pointer. That file
pointer can be <b>stdin</b>. This special interface syntax, for the UF
ingest, is an exception to the interfaces that the other ingest routines
have. All other ingest routines, including <a href="RSL_uf_to_radar.html">RSL_uf_to_radar</a>,
have been modified to read stdin when the input filename is NULL. The complete
list of routines is: <a href="RSL_wsr88d_to_radar.html">RSL_wsr88d_to_radar</a>,
<a href="RSL_nsig_to_radar.html">RSL_nsig_to_radar</a>,
<a href="RSL_lassen_to_radar.html">RSL_lassen_to_radar</a>,
<a href="RSL_uf_to_radar.html">RSL_uf_to_radar</a>,
<a href="RSL_mcgill_to_radar.html">RSL_mcgill_to_radar</a>
and <a href="RSL_toga_to_radar.html">RSL_toga_to_radar</a>. The only routine
that will not accept stdin will be <a href="RSL_anyformat_to_radar.html">RSL_anyformat_to_radar</a>.
That routine will not be able to handle reading stdin because it needs
to read the first few bytes of the file to determine which ingest routine
to call. If you plan to make a filter program, you'll just have to know
what file format you expect: UF, nsig, wsr88d, etc.
<br>
<br>
</body>
</html>
|