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_multi_tcf The read_multi_tcf module is one of a limited set of Time_Data modules. These modules are 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.
time_value The time_value module is used to parse a TVF file consisting of dates, values, and (optional) labels. The starting and end dates are read from the file and the controls can be used to interpolate the values to the date and time of interest. 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 Current Date and Time Label [String] Resulting string for the output date Current Date and Time Value [Number] Resulting value for the output date TVF File Format
time horizon The time horizon module allows you to extract a surface from a set of time-based surfaces. The time for the extracted surface can be any time between the start and end of the surface set. It will interpolate between adjacent known times.
time_loop General Module Function The time_loop module is one of a limited set of Time_Data modules. These modules are 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.
Subsections of Time
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 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
read_multi_tcf
The read_multi_tcf module is one of a limited set of Time_Data modules. These modules are 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_multi_tcf module creates a field using one or more Time Control Files (.TCF). Click here for an example of a TCF fileand a description of the format.
The read_multi_tcf module creates a mesh grid with the interpolated data from a user specifed number of TCF files (n). It outputs the first data component from the first (n-1) TCF files and all of the time interpolated data components from the nth TCF file.
For example, if you were trying to create a time animation of the union of 3 analytes (e.g. Benzene, Toluene & Xylene), read_multi_tcf allows you to select all three separate TCF files. Only the first data component from Benzene.tcf (nominally the concentration of benzene) is output as the new first data component. The first data component from Toluene.tcf (nominally the concentration of toluene) is output as the new second data component. All of the data components from Xylene.tcf are then output (typically xylene, confidence_xylene, uncertainty_xylene, Geo_Layer, Material_ID, Elevation, etc.). This allows you to explode layers and do other typical subsetting and processing operations on the output of this module.
The TCF files should be created using identical grids with date ranges that overlap the time period of interest.
read_multi_tcf effectively includes an inter_time_step module internally in that it performs the 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.
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 multi 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
time_value
The time_value module is used to parse a TVF file consisting of dates, values, and (optional) labels. The starting and end dates are read from the file and the controls can be used to interpolate the values to the date and time of interest.
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
- Current Date and Time Label [String] Resulting string for the output date
- Current Date and Time Value [Number] Resulting value for the output date
TVF files provide a way to generate a time varying numeric and option string (label). The file is similar to the TCFÂ file, but does not reference info
Subsections of time value
TVF files provide a way to generate a time varying numeric and option string (label). The file is similar to the TCFÂ file, but does not reference information in external files.
The file consists of two or more rows, each having 2 or 3 columns of information. The columns must contain:
- Date and/or time in Windows standard format
- A numeric (float) value (required)
- A string consisting of one or more words. These need not be in quotes. Everything on the row after the numeric value will be used. (optional)
Dates must be in order from earliest to latest and not repeating. Only the label column is optional.
time horizon
The time horizon module allows you to extract a surface from a set of time-based surfaces. The time for the extracted surface can be any time between the start and end of the surface set. It will interpolate between adjacent known times.
time_loop
General Module Function
The time_loop module is one of a limited set of Time_Data modules. These modules are 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 time_loop module allows you to loop through a series of times or specify a time for interpolation from a time field.