# File: ${IRIS_CONFIG}UfToIris.conf
# Contains configuration information for the UF-to-IRIS format conversion
# program.  UfToIris will generate a syntax error
# for unrecognized commands, as well as commands with not enough args,
# and invalid args, including number out of the valid range.

# Turn logging on, choices are FILE or TERM or BOTH or NONE.
LOG NONE
#APPEND_TO_LOG

# Uncomment this for logging of more than just errors.
# VERBOSE

# Here is a sitename mapping table.  List all the expected UF sitenames,
# followed by the IRIS sitename to convert it to.  This is followed by the 
# local timezone in minutes west of UT, the local TZ name, then the flag
# LOCAL or UTC to indicate which type of time to record. 
# Note that all UF data is recorded
# using Universal Time, so this offset will be added to the UF times when
# converting to IRIS times, when appropriate.  Note that the wildcards
# "*" and "?" can be used in UF sitenames.  Also some UF convertors produce
# sites that are 8-character space padded, and some produce null terminated
# sitenames.  You need to specify the correct text here, which is easy
# to do when quoting the string.

SITE "Cheju"    "Cheju"    -540  KST  LOCAL
SITE "Dong-Hae" "Dong-Hae" -540  KST  LOCAL
SITE "Pusan"    "Pusan"    -540  KST  LOCAL
SITE "Tallinn " "Test"      120  EET  UTC


# Here is a taskname mapping table.  List the UF sitename, followed by
# the scan type, followed by the fixed angle for the first sweep, followed
# by the task name, followed by an optional calibration reflectivity at
# 1 km.  Note that this task name is also used for the RAW
# product name.  Again, wildcards and trailing spaces are allowed in the
# UF sitename.

TASK "Cheju"    PPI 0.05 PPI_VOL -35.0
TASK "Dong-Hae" PPI 0.16 PPI_VOL -35.0
TASK "Pusan"    PPI 0.09 PPI_VOL -35.0

# Here is a data type mapping table.  List the UF 2-character data type,
# followed by the IRIS 6-chacter data type.  This table is searched 
# first so it can override the default UF types.  For any new type, 
# the UF scale factor is set to 100.  For a list of the valid IRIS 
# data types, see the source for sdata_name6() in libs/user/DataNames.c

# After the IRIS data type are an arbitrary scale factor and offset.
# This is used to adjust scale.  The UF value is multiplied by the
# scale then the offset is added to determine the IRIS value.  The
# scale cannot be 0.  This is not the same as the UF scale factor,
# which is simply the resolution of the UF data.

# Setting a data to IRIS "Null" will cause the system to not convert
# that data.

#DATA  DZ  dBZ   1.0  0.0
#DATA  US  User 10.0 70.0
#DATA  SW  Null  1.0  0.0

# This command indicates that the following commands only apply
# to the specified device.  Numbers are origin 1, 0 means all
# devices.  This allows support for different configuration 
# for different inputs.

# DEVICE_NUMBER 1

# The fixed angle is the nominal elevation angle for a sweep.
# It should remain constant for a whole sweep, but some
# converters do not fill this number in correctly.  In that
# case specify the maximum change in degrees allowed between
# successive rays within a sweep.

# FIXED_ANGLE_CHANGE 0.2

# IRIS only supports fixed wave length radars.
# It should remain constant for a whole volume, but some
# converters do not fill this number in correctly.  In that
# case you can override the file's wave length by setting 
# it here, units are cm.

# WAVE_LENGTH_OVERRIDE 10.28

# IRIS expects all the UF sweeps to be consecutive numbers
# starting from 1.  If there are some sweeps which are not
# compatible with the others, either because they contain
# different data, or because they are at a different PRF,
# you can list here the sweeps to skip.  Only the last 
# SWEEP_SKIP line is used.  Sweep numbers beyond those 
# skipped will be decremented when converted to IRIS.  
# A maximum of 40 sweeps can be read from the UF file, and
# the skip list maximum size is also 40.  If you have a
# UF file which does not start at sweep 1, you can read 
# it if you specify here to skip all the earlier sweeps.

# SWEEP_SKIP 1 2 3 4 9 10 11 

# WSR-88D data has different bin spacings for different data
# types within the same ray.  This flag allows that by 
# replicating bins to match the finest spacing found.  To work
# correctly the spacings must be integer multiples of each other.
# ALLOW_MIXED_BIN_SPACING

# Some UF files are missing the velocity data from the last
# ray of the first sweep.  This is a problem because IRIS expects
# all data types in all rays.  This command allows you to
# tell the converter to skip all rays which do not contain
# a specified data type.  It will give up after 100 such
# rays so do not use this to filter out entire sweeps which
# are missing a data type.  In that case use the SWEEP_SKIP 
# command above, which is applied first.  Only the last 
# RAY_REQUIRES line is used.
# RAY_REQUIRES  VR