# Ferret Version 5.3 and Version 5.4 Release Notes

## New in Version 5.3

- Alpha-level support for string variables
- Support for non-Gregorian calendar axes
- Output from Unix shell commands may be captured in Ferret
- New automatically defined symbols for date and time
- New pseudo-variables reveal grid cell bounds
- SHOW AXIS (and SHOW GRID/[axis]) enhanced
- SHOW GRID, SET GRID, DEFINE GRID/LIKE= and SET VAR/GRID= can take expressions as arguments
- Immediate mode (grave accent) expressions formatting
- Nearest coordinate regridding transformation @NRST
- Ferret symbols (e.g. "($symbol)") used inside REPEAT loops are now re-translated at each repetition of the loop
- Multi-line commands (continuation lines)
- The length of the command buffer is increased to 2048 characters
- New immediate mode RETURN arguments: RETURN=DSET, DSETNUM, DSETPATH, BAD
- Up to 99 arguments for GO commands using either $nn or ($nn) syntax
- New transformation @EVNT ("event mask")
- Added SET VARIABLE/NAME=
- NetCDF time axes encoded as year 0000 or 0001 are automatically flagged as modulo
- Ability to animate on the fly
- FLOWLINE command draws continuous flowlines from vector components
- Step function plots
- New PLOT qualifiers /VLOG and /HLOG set log axis for plots.
- Ability to read "delimited" files (e.g. Excel spreadsheet outputs)
- Enhanced ability to associate time series files into a MC (multi-CDF) data set
- Performance of netCDF "SAVE/APPEND ..." greatly increased for large file output
- Support for command files created by Windows (embedded CR characters)
- More external functions utility calls may be made during custom axis creation
- New functions ZAXREPLACE_AVG and ZAXREPLACE_BIN
- Arguments to EOF functions changed

## New in Version 5.4

- Support for string variables
- Strides can be applied across the "branch point" of a modulo variable
- Nesting of GO files no longer limited to 10 deep.
- New qualifiers EXIT/LOOP, EXIT/SCRIPT, EXIT/PROMPT, EXIT/PROGRAM
- New qualifier /AXES for DEFINE VIEW
- Control of dashed lines with PLOT/DASH=
- Doubled the default memory to 6.4 Mwords
- Plotting is no longer limited by a fixed plot memory buffer
- New plot qualifier /AXES[=top,bottom,left,right] turns plotting of individual axes off and on
- New PLOT/SYMBOL=DOT
- New functions COMPRESS_BY compress data according to a mask
- Modified heading output of LIST command
- New qualifier: LIST/WIDTH=columns
- Allow SET DATA/TITLE= for NetCDF, DODS datasets

## Bug Fixes in Version 5.3

- Buffer size increase allows STAT to handle larger summaries
- Allow External functions using FORTRAN complex variables
- Bug fix in EF framework: didn't handle custom axes if EF had more than one argument
- Ferret does not crash if a segmentation fault occurs within an external function
- Distinct axes that were dynamic and irregular were not always recognized as different
- Permutation error when multiple variables of differing shape are written at once
- SAVE used on a subset of an irregular axis did not write cell boundaries into the output file
- MODE VERIFY output is suppressed for lines skipped due to IF-THEN-ELSE
- Scaling bugs fixed in scripts polytube.jnl and polymark.jnl
- Auto-labelling of axes improved when many digits are needed (e.g. scale from 1020 to 1021)
- Allow filenames to include commas (if name is enclosed in quotations) (needed for DODS constrained URLs)
- Limit on string lengths fixed (e.g. long DODS filenames)
- Bug fixed in the journal script right_axis_plot.jnl
- EOF functions had inconsistency in treatment of bad-data flags.
- DEFINE AXIS/FROM failed to check if n=1
- DEFINE AXIS where n=1 gave bogus box limits
- SAMPLEXY function works on fields with modulo axes.
- The length of the buffer for the LEVELS qualifier (i.e. for SHADE or CONTOUR) has been increased from 80 to 1028 characters.
- Mixed regridding gx=sst and y=lo:hi:del could ignore the lo:hi:del
- STAT command applied to values all greater than 1.E34
- Allow British spelling "metre"
- Detect extra colon in "i=1:5:2:"
- SCAT2GRIDGAUSS* and SCAT2GRIDLAPLACE* functions allow input to be function of both time and the spatial dimension not being gridded, e.g. SCAT2GRIDGAUSS_XY grids in XY a function of time and/or depth.
- Bug related to region information left after a REPEAT loop

## Bug Fixes in Version 5.4

- PLOT+ command "list yaxis" now says "YORG+" (instead of "XORG="
- Negative times improperly formatted on output
- Data set names may begin with digits
- Strings sent to PLOT+ label commands via "LABEL" may contain single quotes
- No longer output documentation on data set for, e.g., let fcn = SIN(T[gt=tax]/10); plot t[g=fcn]
- SET VAR/NAME= allowed duplicate variable names
- VECTOR plotting improved for curvilinear coordinate plots. VECTOR/LENGTH works.
- Plotting bug in version 5.33 fixed: first two points weren't connected
- Contour levels bug: In the sequence SHADE var; CONTOUR/OVER/LEV var levels weren't properly set by SHADE command
- Fix format problem when listing negative subscripts on modulo axes
- LET VAR2 = VAR1[d={this is limited to less than 40 characters}]
- Line plot bug where first point in a line plot was left off, and where plot/vs gave a connecting line without /LINE

## Improved error messages

- During axis definition "unknown axis units" is replaced by "units are not subject to auto-conversion"
- Improved error message for unknown function "LET b = UNKNOWN(a)"
- Remove annoying warning about unknown axis units during FFTA and other dynamic axes
- When user doesn't specify limits on ABSTRACT axis say NOTE: Check for unspecified limits on an ABSTRACT axis instead of NOTE: You can use SET MEMORY/SIZE=xxx to increase memory
- Longer dataset name allowed for commands such as LET Var2=var1[d=data_set_name]

## New Features and Enhancements:

### Alpha-level support for string variables

> NOTE: See significant additions to capabilities in V5.4

### Support for non-Gregorian calendar axes

> The NetCDF conventions document discusses and defines usage for different calendar axes. See:
> http://www.cgd.ucar.edu/cms/eaton/netcdf/merge_current.html#cal

> The NetCDF conventions recommend that the calendar be specified by the attribute calendar which is assigned to the time coordinate variable. These conventions for calendars are implemented in Ferret version 5.3 The calendars defined are: Gregorian (the default), noleap (365 day years), Julian (every four years is leap year), 360day (years are 360 days divided into 30-day months). These calendars are compatible with the Udunits standard which has slightly different naming conventions.
> NetCDF files use the attribute time:calendar when there is a non-Gregorian calendar associated with a data set, i.e.
> `time:calendar=noleap`

> `Example:` Define a calendar axis, regrid an existing variable to this axis:
> `yes? DEFINE AXIS/CALENDAR=360DAY/T="15-JAN-1982":"15-DEC-1985":30/UNITS=days tmodel`
> `yes? LET twind = uwnd[GT=tmodel@NRST]`

> When regridding from one calendar axis to another the length of a year is assumed to be constant, therefore the regridding calculates a scale factor based on the length of a second in each calendar, computed from the number of seconds per year for the calendars.

###
Output from Unix shell commands may be captured in Ferret

As with this example.

`yes? let a = {system:"ls"}`
`yes? list a`
`{SYSTEM:"ls"}`
`1 / 1:"TutorialModels98.zip"`
`2 / 2:"ferret.jnl"`
`3 / 3:"movies.zip"`
`4 / 4:"movies1.zip"`
`5 / 5:"movies2.zip"`
`6 / 6:"movies3.zip"`
`7 / 7:"roseent8054c_timelocked2.exe"`
`8 / 8:"tutorial.zip"`

### New automatically defined symbols for date and time

- ($SESSION_DATE)
- ($SESSION_TIME)

### New pseudo-variables reveal grid cell bounds

> XBOXLO, XBOXHI, YBOXLO, ... reveal the grid cell lower and upper bounds explicitly

### SHOW AXIS (and SHOW GRID/[axis]) enhanced

> enhanced to show lower bound of each grid cell

SHOW GRID, SET GRID, DEFINE GRID/LIKE= and SET VAR/GRID= can take expressions as arguments

### Immediate mode (grave accent) expressions formatting

> These may be formatted with w=width or zw=zero-filled width. For example

> `yes? SAY Answer: `5.3,w=8``
> `Answer: 5.3`
> `yes? SAY Answer: `5.3,zw=8``
> `Answer: 000005.3`

### Nearest coordinate regridding transformation @NRST

> Nearest coordinate regridding VAR[GX=newaxis@NRST] chooses the value from the source axis coordinate closest to the destination axis. If source coordinates above and below are equally close to a destination coordinate the value at the lower coordinate will be chosen. (This is most useful for regridding between axes whose coordinate values are very close, though not exactly matched -- e.g. between equally and unequally spaced monthly time axes.)

### Ferret symbols (e.g. "($symbol)") that are used inside of REPEAT loops are now re-translated at each repetition of the loop

### Multi-line commands (continuation lines)

> Command lines ending with back slash are regarded as incomplete -- a special prompt is given to indicate that the next line is a continuation .

> Example:
> `yes? let a = 123 + 456 + \`
> `...? 789`
> `yes? list a`
> `123 + 456 + 789`
> `1368.`

The length of the command buffer is increased to 2048 characters

### New immediate mode RETURN arguments

- RETURN=DSET, DSETNUM, DSETPATH to recover data set information from an expression
- RETURN=BAD to recover the missing value flag from an expression

### Up to 99 arguments for Go commands using either $nn or ($nn) syntax

The syntax $nn (nn may be 1 through 99) is equivalent to to ($nn), however the parentheses enclosed form is generally preferred as it avoids ambiguities:

- `XSEQUENCE($1)` will be misinterpreted whereas `XSEQUENCE(($1))` is clear
- `($1)2.dat` will substitute argument 1 as a prefix to `"2.dat"` and `($12).dat` will substitute argument 12 as a prefix to `".dat"`. Specifying `$12.dat` is equivalent to `($12).dat` but is less clear.

### New transformation @EVNT ("event mask")`.`

This transformation locates "events" in data. An event is the occurrence of a particular value. The output steps up by a value of 1 for each event, starting from a value of zero. (If the variable takes on exactly the value of the event trigger the +1 step occurs on that point. If it crosses the value, either ascending or descending, the step occurs on the first point after the crossing.)

For example, if you wanted to know the maximum value of the second wave, where (say) rising above a magnitude of 0.1 in variable "ht" represented the onset of a wave, then

`yes? let wave2_mask = IF ht[T=@evnt:0.1] EQ 2 THEN 1`

`is a mask for the second wave, only. The maximum waveheight may be found with`

`yes? let wave2_ht = wave2_mask * ht`
`yes? let wave2_max_ht = wave2_ht[T=@max]`

Note that @EVNT can be used together with @LOC and @WEQ to determine the location when an event occurs and the value of other variables as the event occurs, respectively. Since there may be missing values in the data, and since the instant at which the event occurs may lie immediately before the step in value for the event mask, the following expression is a general solution.

`yes? let event_mask = my_var[t=@evnt:<value>]`
`yes? let event_n = IF ABS(MISSING(event_mask[L=@SBX],event_mask)-n) LE 0.67 THEN`
`my_var`

So that
`event_n[t=@loc:<value>] is the time at which event "n" occurs`
and
`event_n[t=@weq:<value>] is the integrating kernel (see @WEQ)`

### Added SET VARIABLE/NAME=

> This is effectively a RENAME command -- applies to all classes of variables (not pseudo-variables). Useful for "repairing" variables whose definitions are inadequate as-is but whose variable names are significant. A common application of this is in creating output netCDF files in which contain modified versions of variables from input files.

NetCDF time axes encoded as year 0000 or 0001 are automatically flagged as modulo

### Ability to animate on the fly

> `REPEAT/ANIMATE[/LOOP=n]`
> is used to start an animation sequence. Given LOOP=n, the animation sequence will repeat n times.

> Example:
> `yes? set data coads_climatology`
> `yes? repeat/l=1:12/animate/loop=5 (shade sst; go fland)`

> Known bug/feature: It is necessary to execute some other plot before animating. Otherwise, the first time through the animation, the graphics window remains blank. This restriction will be lifted in the official V5.3 release.

> NOTE: In order to properly display on SGI's, it is necessary to have backing store enabled for the Xserver.

### FLOWLINE command draws "flowlines" from vector components

> (in beta versions this was named STREAKLINE). A new qualifier to the VECTOR command VECTOR/FLOWLINE (alias FLOWLINE) draws continuous flowlines from the vector components U and V. The qualifier /DENSITY controls the number of lines drawn. There is also a 4-argument form of this command for drawing flowlines in curvilinear coordinates. Note that Ferret does not compute a stream function, but draws a pathline integration of a 2-dimensional instantaneous flow field. In a 3-dimensional flow field the plots are only useful as a qualitative visualization tool.

> Example:
> `yes? USE coads_climatology`
> `yes? SET REGION/x=150e:130w/y=40s:50n/l=6`
> `yes? FLOW/DENSITY=4 uwnd,vwnd`

> The underlying algorithm is used with permission from the GrADS program. Our thanks to COLA, the Center for Ocean-Land-Atmosphere Studies, for access to this technique.

### Step function plots

> PLOT/STEP and PLOT/STEP=connected
> These qualifiers give a plot style that is consistent with grid cell interpretation of data. Especially useful for time series to show the span of each time bin.

### New PLOT qualifiers /VLOG and /HLOG set log axes for plots.

/VLOG sets a vertical log axis, /HLOG sets a horizontal log axis. If /VLIMITS or /HLIMITS is specified, they should be in data units (not log10 axis units). If the axis is a depth axis, an inverse log axis is drawn.

Note that setting axtype with a PPLUS call before the plot call will not result in a log plot, though making an axtype setting with PLOT/SET_UP still works as in previous versions.

new syntax:
`yes? PLOT/VLOG/VLIMITS=10:1000 my_ fcn ! plots a function on a log axis`

replaces older syntax:
yes? ppl axtype 1, 3
yes? PLOT/VLIMITS=1:3 my_fcn ! This will NOT produce a log plot, as the
! PLOT command resets the status of the axes.

yes? PLOT/SET_UP/vlimits=1:3 my_fcn ! These commands duplicates the new syntax.
yes? ppl axtype, 1, 3
yes? ppl plot

### Ability to read "delimited" files (e.g. Excel spreadsheet outputs)

> `SET DATA/FORMAT=DELIMITED[/DELIMITERS=][/TYPE=][/VAR=] filename`

> initializes a file of mixed numerical, string, and date fields. If the data types are not specified the file will be analyzed automatically to determine data types. Using delimited files, the number of variables that can be read from a single file is increased from 20 to 100.

> /DELIMITER - list of field delimiters. Default is tab or comma e.g. /DELIM="X,\t,\,"
> special characters include

> > - \b - blank
> > - \t - tab
> > - \n - newline
> > - \nnn - decimal value from ASCII table

> /TYPE is the list of data types of the fields. Field types may be any of

> > - "-" - skipped
> > - NUMERIC
> > - TEXT
> > - LATITUDE - e.g. 87S or 21.5N (interpreted as negative or positive, respectively)
> > - LONGITUDE - e.g. 160W or 30E (interpreted as negative or positive, respectively)
> > - DATE - e.g. mm/dd/yy or mm/dd/yyyy or yyyy-mm-dd or yyyymmdd - value returned is days from 1-jan-1900 (consistent with the DAYS1900 function)
> > EURODATE - e.g. dd/mm/yy or dd/mm/yyyy or yyyy-mm-dd TIME - e.g. hh:mm or hh:mm:ss.s

### Enhanced ability to associate time series files into a MC (multi-CDF) data set

> Previous to version 5.2 Ferret performs sanity checking on an MC data set by comparing the time coordinates with those found in the data files as the data are read. In version 5.3 and higher no sanity checks are performed. This means that the MC descriptor mechanism can be used to associate into time series groups of files that are not internally self documenting with respect to time, however, it also shifts an additional burden onto the user of carefully checking the validity of the STEPFILE records in the descriptor files. Also note there is enhanced documentation of MC descriptors in the Users Guide, Chapter 10 sec 4.

Performance of netCDF "SAVE/APPEND ..." greatly increased for large file output

Support for command files created by Windows (embedded CR characters)

> Files written by Windows software have embedded carriage return characters. Journal files with this formatting can now be read by Ferret.

### External functions utility calls may be made during custom axis creation

- ef_get_one_val can be called to obtain constant values during custom axis creation
- ef_get_string can be called to obtain a string value during custom axis creation

New functions ZAXREPLACE_AVG and ZAXREPLACE_BIN

> These functions are similar to ZAXREPLACE but use other regridding methods to replace a Z axis

> ZAXREPLACE_AVG(V,ZVALS,ZAX)
> Use weighted averaging to convert between alternative monotonic Z axes. The weighting is done according to the portion of the source box that lies within the destination grid cell.

> ZAXREPLACE_BIN(V,ZVALS,ZAX)
> Use unweighted averaging to convert between alternative monotonic Z axes. The function finds the source points within each destination box and averages them.

Arguments to EOF functions changed.

The second argument in previous versions has been removed. This argument had the functions scale and return only EOF spatial and time functions up to a given percent variance explained. However this didn't save much computation. The functions now return all the EOF's.

         yes?  SHOW FUNCTION eof_*
         EOF_SPACE(A,frac_timeser)
             Compute EOF spacial fields from XYT field
             A: Variable in x,y,t; may be fcn of z
             frac_timeser: Use only those time series with this fraction valid data
         EOF_STAT(A,frac_timeser)
             EOF statistics from XYT field. j=1:#EOFs, j=2:%variation,j=3:eigenvalues
             A: Variable in x,y,t; may be fcn of z
             frac_timeser: Use only those time series with this fraction valid data
         EOF_TFUNC(A,frac_timeser)
             Compute EOF time functions from XYT field.
             A: Variable in x,y,t; may be fcn of z
             frac_timeser: Use only those time series with this fraction valid data

Support for string variables

yes? LET a = {"s1","s2", ,"s3"}
yes? LIST a
yes? SAVE/CLOBBER/FILE=test_string.cdf/HEADING=enhanced a[i=2:4]
yes? LIST a[i=@shf]

- Strings in an array may be variable length
- The syntax {"a","b","c"} denotes an array of strings. Two commas in a row denotes a null (missing value) string. Single and double quoted strings are both allowed.
- Algebraic operations:

- Logical operators EQ, LT, LE, ... These operators are case-insensitive (functions will be provided later that are case-sensitive and include UPCASE, DNCASE)
- @SHF
- IF cond THEN string_array1 ELSE string_array2
- Concatenation with "+": a = "good" + "bye"
- SAMPLE* functions may take string or numerical arrays as arguments
- Regridding with @ASN, @XACT, @NRST

- Input and output to netCDF files. In the file the string axis is the fastest moving dimension and all strings are the same length (equal to the maximum length of the strings being written). Extra character spaces are padded with nulls. If variable length strings are written out, then when read back they will again be variable length.
- Function SPAWN executes a Unix system command and returns the result in a string array.
- The syntax "SPAWN:"command" allows the output of a Unix command to be mixed with other strings. For example,
LET a = {"first.nc", SPAWN:"ls *.nc","last.nc"}
- Internally all variables now have data types
- Grave accents around a scalar string variable return the string
- (alpha) can create external functions where arguments may be either string or float -- e.g. "var" in SAMPLEI(var, indices)
- (alpha) functions can return strings (e.g. SPAWN)

Strides can be applied across the "branch point" of a modulo variable

> Strides can be applied across the "branch point" of a modulo variable without loss of efficiency for netCDF data set, as long as the stride is an integer fraction of the modulo length* (the number of points on the axis)

Nesting of GO files is no longer limited to 10 deep.

> Ferret now supports up to 200 deep, but typically you will limited to fewer by Unix itself.

New qualifiers EXIT/LOOP, EXIT/SCRIPT, EXIT/PROMPT, EXIT/PROGRAM

> `EXIT/LOOP exit from current repeat loop`
> `EXIT/SCRIPT exit from current script`
> `EXIT/PROMPT exit to Ferret prompt`
> `EXIT/PROGRAM exit program completely`

> "QUIT" in a command file is an alias for EXIT without a qualifier. It will exit the current script, or the program if you are at the Ferret prompt.

New option for defining viewports, DEFINE VIEW/AXES

> Here the user's limits are interpreted as the normalized positions of the plot axes rather than of the entire viewport. For example:

> > `yes? DEFINE VIEWPORT/AXES/XLIM=0.5:1/YLIM=0:0.5 lrax`
> > `yes? SET VIEW lrax`
> > `yes? PLOT/VS/LINE/I=1:314 i*cos(i/20),i*sin(i/20); pause`
> > `yes? PLOT/VS/LINE/NOYADJUST/I=1:314 i*cos(i/20),i*sin(i/20)`

- Can change PPL ORIGIN and PPL AXLEN only after SET VIEW is issued
- Use new qualifier PLOT/NOYADJUST to avoid resetting the Y origin -- relevant during PLOT commands that require extra room for a large key block under the axes or for viewports that lie close to the bottom of the window where there may not be much room below the Y axis

Doubled the default memory to 6.4 Mwords

> Recall that you can always change the memory at startup with the -memsize option, or during a Ferret session with the SET MEMORY command.

Plotting is no longer limited by a fixed plot memory buffer.

> Memory for plotting is allocated as needed. Previously there was a fixed memory buffer used for plotting.

Control of dashed lines with PLOT/DASH[=dn1,up1,dn2,up2]

> This allows use of all the color and thickness controls available with the PLOT qualifiers and control over the dash characteristics using the arguments as in the PPLUS "LINE" command: DOWN1, UP1, DOWN2, UP2 in inches.

> Example:
> `plot/dash/i=1:1000 sin(62.8*i)`
> `plot/over/dash=(0.4,0.1,0.4,0.1)/color=red/thick/i=1:1000 sin(62.8*(i+10) )`
> `plot/over/dash=(0.1,0.1,0.04,0.05)/color=blue/thick=1/i=1:1000 sin(62.8*(i+20) )`

New plot qualifier /AXES[=top,bottom,left,right]

> For all plot commands, turns plotting of individual axes off and on. This replaces the use of the "PPL AXSET" command. The syntax is

> PLOT/AXES[=top,bottom,left,right] where the arguments are 1 to turn the axis on and 0 to turn it off. For example:

> CONTOUR/AXES=0,1,1,0 sst ! Plots the bottom and left axes only

New PLOT/SYMBOL=DOT

> Makes a dot at each point. This implements the GKS "dot" polymarker, which uses the smallest dot that can be represented on the display device (Note the dots may not show up well on all devices).

New functions COMPRESS*_BY compress data according to a mask

> COMPRESSI_BY (var, mask), COMPRESSJ_BY (var, mask), COMPRESSK_BY (var, mask), COMPRESSL_BY (var, mask)

> Compress variable "dat" along its I (or J, K, or L) axis using the (multi-dimensional) mask supplied in the second argument.
> For example:

> `yes? LET mask = {1,,1,,1} + 0*L[l=101:102] + 0*K[k=10:11]`
> `yes? LIST mask`
> `{1,,1,,1} + 0*L[L=101:102] + 0*K[K=10:11]`
> `1 2 3 4 5`
> `1 2 3 4 5`
> `---- L:101 T: 101`
> `10 / 10: 1.000 .... 1.000 .... 1.000`
> `11 / 11: 1.000 .... 1.000 .... 1.000`
> `---- L:102 T: 102`
> `10 / 10: 1.000 .... 1.000 .... 1.000`
> `11 / 11: 1.000 .... 1.000 .... 1.000`

> `yes? LIST compressi_by({11,22,33,44,55},mask)`
> `COMPRESSI_BY({11,22,33,44,55},MASK)`
> `1 2 3 4 5`
> `1 2 3 4 5`
> `---- L:101 T: 101`
> `10 / 10: 11.00 33.00 55.00 .... ....`
> `11 / 11: 11.00 33.00 55.00 .... ....`
> `---- L:102 T: 102`
> `10 / 10: 11.00 33.00 55.00 .... ....`
> `11 / 11: 11.00 33.00 55.00 .... ....`

Modified heading output of LIST command

> New lines list the file name and path, and complete information on the subset of the data being listed. See the next section on LIST/WIDTH for an example.

New qualifier: LIST/WIDTH=columns

> For multi-column output, controls the width of the listing on the page, for example:

> `yes? USE coads_climatology`
> `yes? LIST/L=1/WIDTH=50/Y=0:4 sst`
> `VARIABLE : SEA SURFACE TEMPERATURE (Deg C)`
> `DATA SET : COADS Monthly Climatology (1946-1989)`
> `FILENAME : coads_climatology.des`
> `FILEPATH : /home/ja9/tmap/fer_dsets/descr/`
> `SUBSET : 180 by 2 points (LONGITUDE-LATITUDE)`
> `TIME : 16-JAN 06:00`
> `... listing every 36th point`
> `21E 93E 165E 123W 51W`
> `1 37 73 109 145`
> `3N / 47: .... 28.30 29.04 25.36 27.49`
> `1N / 46: .... 28.29 29.12 24.82 27.49`

> `yes? LIST/L=1/WIDTH=80/Y=0:4 sst`
> `VARIABLE : SEA SURFACE TEMPERATURE (Deg C)`
> `DATA SET : COADS Monthly Climatology (1946-1989)`
> `FILENAME : coads_climatology.des`
> `FILEPATH : /home/ja9/tmap/fer_dsets/descr/`
> `SUBSET : 180 by 2 points (LONGITUDE-LATITUDE)`
> `TIME : 16-JAN 06:00`
> `... listing every 18th point`
> `21E 57E 93E 129E 165E 159W 123W 87W 51W 15W`
> `1 19 37 55 73 91 109 127 145 163`
> `3N / 47: .... 27.42 28.30 28.10 29.04 27.30 25.36 27.08 27.49 27.90`
> `1N / 46: .... 27.67 28.29 28.48 29.12 26.62 24.82 25.82 27.49 27.41`

Allow the qualifier /TITLE for DODS or NetCDF datasets

> SET DATA/TITLE associates a title with a dataset (previously not allowd for these file types.)