read tcf

read_tcf

The read_tcf module is specifically designed to create models and animations of data that changes over time. This type of data can result from water table elevation and/or chemical measurements taken at discrete times or output from Groundwater simulations or other 3D time-domain simulations.

The read_tcf module creates a field using a Time Control File (.TCF) to specify the date/time, field and corresponding data component to read (in netCDF, Field or UCD format), for each time step of a time_data field. All file types specified in the TCF file must be the same (e.g. all netCDF or all UCD). The same file can be repeated, specifying different data components to represent different time steps of the output.

read_tcf effectively includes internal interpolation between appropriate pairs of the files/data_components specified in the TCF file. Its internal structure only requires reading two successive time steps rather than the complete listing of time steps normally represented in a time_data field.

Module Input Ports

  • Date [Number] Accepts a date

Module Output Ports

  • Start Date [Number] Outputs the starting date
  • End Date [Number] Outputs the ending date
  • Date [Number] Output date
  • OutputĀ Field [Field] Outputs the data field
  • TCF File

    TCF File Format and Example The listing below is the full contents of the Time Control File control_tce_cdf.tcf. Blank lines or any lines beginning with a ā€œ#ā€ are ignored. Valid lines representing time steps must be in order of ascending time and consisting of: a) a date and/or time in Windows standard format b) a file name with an absolute path or just the filename (if the data files are in the same directory as the TCF file). This is not a true relative path (..\file.cdf and subdir\file.cdf don’t work, but file.cdf does), but gives some of the relative path abilities.

Subsections of read tcf

TCF File Format and Example

The listing below is the full contents of the Time Control File control_tce_cdf.tcf. Blank lines or any lines beginning with a “#” are ignored. Valid lines representing time steps must be in order of ascending time and consisting of:

a) a date and/or time in Windows standard format

b) a file name with an absolute path or just the filename (if the data files are in the same directory as the TCF file). This is not a true relative path (..\file.cdf and subdir\file.cdf don’t work, but file.cdf does), but gives some of the relative path abilities.

c) the data component to use for that time step. (You can specify -1 in the third column, which causes ALL the data components to pass through.)

NOTE: These three items on each line must be separated with a comma “,”.

This file contains the list of control commands for the

TCE time data in netCDF format.

The format is a date/time, then the file, then the nodal data component.

The END on the last line is optional.

Each line MUST be comma delimited

(since spaces can exist in the time and filename)

6/1/1990 12:00 AM, $XP_PATH<0>/data/netcdf/time_data/tce_01.cdf, 0

12/1/1990, $XP_PATH<0>/data/netcdf/time_data/tce_02.cdf, 0

2/1/1991, $XP_PATH<0>/data/netcdf/time_data/tce_03.cdf, 0

5/1/1991, $XP_PATH<0>/data/netcdf/time_data/tce_04.cdf, 0

8/1/1991, $XP_PATH<0>/data/netcdf/time_data/tce_05.cdf, 0

11/1/1991, $XP_PATH<0>/data/netcdf/time_data/tce_06.cdf, 0

3/1/1992, $XP_PATH<0>/data/netcdf/time_data/tce_07.cdf, 0

6/1/1992, $XP_PATH<0>/data/netcdf/time_data/tce_08.cdf, 0

10/1/1992, $XP_PATH<0>/data/netcdf/time_data/tce_09.cdf, 0

3/1/1993, $XP_PATH<0>/data/netcdf/time_data/tce_10.cdf, 0

4/1/1993, $XP_PATH<0>/data/netcdf/time_data/tce_11.cdf, 0

8/1/1993, $XP_PATH<0>/data/netcdf/time_data/tce_12.cdf, 0

12/1/1993, $XP_PATH<0>/data/netcdf/time_data/tce_13.cdf, 0

3/1/1994, $XP_PATH<0>/data/netcdf/time_data/tce_14.cdf, 0

6/1/1994, $XP_PATH<0>/data/netcdf/time_data/tce_15.cdf, 0

9/1/1994, $XP_PATH<0>/data/netcdf/time_data/tce_16.cdf, 0

11/1/1994, $XP_PATH<0>/data/netcdf/time_data/tce_17.cdf, 0

3/1/1995, $XP_PATH<0>/data/netcdf/time_data/tce_18.cdf, 0

5/1/1995, $XP_PATH<0>/data/netcdf/time_data/tce_19.cdf, 0

8/1/1995, $XP_PATH<0>/data/netcdf/time_data/tce_20.cdf, 0

10/1/1995, $XP_PATH<0>/data/netcdf/time_data/tce_21.cdf, 0

1/1/1996, $XP_PATH<0>/data/netcdf/time_data/tce_22.cdf, 0

5/1/1996, $XP_PATH<0>/data/netcdf/time_data/tce_23.cdf, 0

9/1/1996, $XP_PATH<0>/data/netcdf/time_data/tce_24.cdf, 0

11/1/1996, $XP_PATH<0>/data/netcdf/time_data/tce_25.cdf, 0

12/1/1996, $XP_PATH<0>/data/netcdf/time_data/tce_26.cdf, 0

3/1/1997 12:00 AM, $XP_PATH<0>/data/netcdf/time_data/tce_27.cdf, 0

6/1/1997, $XP_PATH<0>/data/netcdf/time_data/tce_28.cdf, 0

9/1/1997, $XP_PATH<0>/data/netcdf/time_data/tce_29.cdf, 0

12/1/1997, $XP_PATH<0>/data/netcdf/time_data/tce_30.cdf, 0

3/1/1998, $XP_PATH<0>/data/netcdf/time_data/tce_31.cdf, 0

6/1/1998, $XP_PATH<0>/data/netcdf/time_data/tce_32.cdf, 0

9/1/1998, $XP_PATH<0>/data/netcdf/time_data/tce_33.cdf, 0

11/1/1998, $XP_PATH<0>/data/netcdf/time_data/tce_34.cdf, 0

5/1/1999, $XP_PATH<0>/data/netcdf/time_data/tce_35.cdf, 0

10/1/1999, $XP_PATH<0>/data/netcdf/time_data/tce_36.cdf, 0

3/1/2000, $XP_PATH<0>/data/netcdf/time_data/tce_37.cdf, 0

7/1/2000, $XP_PATH<0>/data/netcdf/time_data/tce_38.cdf, 0

11/1/2000, $XP_PATH<0>/data/netcdf/time_data/tce_39.cdf, 0

3/1/2001, $XP_PATH<0>/data/netcdf/time_data/tce_40.cdf, 0

5/1/2001, $XP_PATH<0>/data/netcdf/time_data/tce_41.cdf, 0

10/1/2001, $XP_PATH<0>/data/netcdf/time_data/tce_42.cdf, 0

END