https:///weradocs/rad5uv.shtml Last update:

WERA HF Radar Software - Combine Radial Components (Beam Forming)

rad5uv

Program expects 'FMRADG' header code, otherwise exits (handles Beam Forming files only).
Look here for a complete list of header codes.

Program looks for files containing names of .RAD files to be combined:
/home/wera/etc/Ranam1.dat,
/home/wera/etc/Ranam2.dat, ...,
/home/wera/etc/Ranam10.dat
e.g.

/home/wera/etc/Ranam1.dat : /home/wera/data/Torres/20003341355_TOR.RAD
/home/wera/etc/Ranam2.dat : /home/wera/data/Penas/20003341405_PEN.RAD
Note, that if data from more than two sites (radial components) are available, the 2-dim value is calculated by an overdetermined system of equations using the accuracy of the radial components as a weight to the least-squares solution.

The program reads following values from PARAM_UV.CFG (VMS) / params.cfg (Linux):

C	Maximum number of RanamX.dat files in NST
C
        NST             =  2            !Number of WERA sites (radial files)

        VARX            =  1.5          !Variance of radial comp must be less [m/s]
        SIG_CUT         =  0.5          !Accuracy of 2-dim current must be less
        !
        MAX_CUR         =  4.0          !Maximum 2-dim current allowed [m/s]
        MAX_GDOP        =  5.0          !Maximum GDOP allowed

C	Name and size (NX, NY) of Grid File
C
C	Values used to generate Gijon_grid_60_60.asc :
C	Spacing [km] 1.0
C	Upper left corner: LAT 44 5.8  LON -5 -52.0
C
	NX              = 60
	NY              = 60
	GRID_NAME	= '/home/wera/etc/Gijon_grid_60_60.asc'

C	Name of Watt File
C
	WATT		= .TRUE.		!.true. = process Watt file
C	WATT		= .FALSE.		!.true. = process Watt file
	WATT_NAME	= '/home/wera/etc/Gijon_watt_60_60.asc'

	UV_DIR          = '/home/wera/data/uv/'  !Directory for 2-dim .UV
	ASC_DIR         = '/home/wera/data/asc/' !Directory for 2-dim .ASC
        !
	CODE 		= 'gij' 	!Code in 2-dim current file
	!
	!To generate a GDOP file, run rad5uv once with WRITE_GDOP = .TRUE.
	WRITE_GDOP	= .FALSE.	!.true. = write GDOP file
C	WRITE_GDOP	= .TRUE.	!.true. = write GDOP file
C	Name of GDOP File
	GDOP_NAME	= '/home/wera/etc/Gijon_GDOP_60_60.dat'
	!
	INTER		= .TRUE.	!.true. = interpol
C	INTER		= .FALSE.	!.true. = interpol
C	LIE		= .TRUE.	!.true. = extrapol
	LIE		= .FALSE.	!.true. = extrapol
C	TRIANG		= .TRUE.	!.true. = Triangle-Interpolation
	TRIANG		= .FALSE.	!.true. = Triangle-Interpolation

MAX_CUR:     Always used.
             Sets the 2-dim current to 'gap' when the absolute value is
             larger than MAX_CUR.
MAX_GDOP:    Always used.
             Limit the increase of error due to geometry between the radar
             sites to MAX_GDOP.
VARX:        Always used.
             Limit the variance of an averaged radial component to VARX. If a
             value greater than VARX is found, set radial component to 'gap'.
SIG_CUT:     Always used.
             Limit the accuracy of 2-dim current to SIG_CUT. If a value 
             greater than SIG_CUT is found, set 2-dim current to 'gap'.

INTER:       Interpol current field using available radial components
LIE:         Extrapolate current field using available radial components
TRIANG:      Extrapolate current field from center to the edges where no
             radial components are available.

For Linux the directory strings must end with '/'

WATT_NAME can be used to force the current speed at selected grid points to ZERO. This is especially usefull, when interpolation / extrapolation near to wadden areas is enabled. The logical WATT can be used to enable WATT_NAME to be processed by rad5uv. For further remarks look at Make_Grid. There may be many other parameters defined in the /home/wera/etc/params.cfg file, which are required for other programs. These are ignored by rad5uv.

Two versions of the resulting 2-dim current file are written:

1. Formatted in ASC_DIR:  <time_code>_<CODE>.cur_asc
[2. Unformatted in UV_DIR: <time_code>_<CODE>.cur_uv] ... only if WRITE_UV = .true. in rad5uv.F

<time_code> is taken from the first .RAD file e.g. in Ranam1.dat
and has the form yyyydddhhmm:  year,day_in_year,hour,minute
            e.g. 20003341355   Year 2000, Day 334, Hour 13, Minute 55
The following box shows a typical output generated by rad5uv:

wera@ifmpc143:~/Fortran > rad5uv
 Input from /home/wera/etc/Ranam1.dat
 Input from /home/wera/etc/Ranam2.dat
 Combining Radails from: /home/wera/data/examples/20022972340_koo.rad
 Combining Radails from: /home/wera/data/examples/20022972350_kna.rad
 *** Interpol...
 Result in: /home/wera/data/asc/20022972340_Oah.cur_asc

Here is the data formats of the output (.cur_asc) file.

Compilation from source:
Linux:

Source is in rad5uv.F
Compilation and linking with '. do_rad5uv.sh'

After passing the input radial files via RanamNN.dat, call with
> rad5uv

VMS:

Source is in rad5uv.F
Compilation and linking with @rad5uv

After passing the input radial files via RanamNN.dat, call with
$ run rad5uv


Comments to: gurgel@ifm.uni-hamburg.de (Klaus-Werner Gurgel)