General Module Function
The read_lines module is used to visualize a series of points with data connected by lines. read_lines accepts three different file formats, with the CSV file format the lines are connected by boring ID, with the ELF (EVS Line File) format each line is made by defining the points that make up the line, and with the SAD (Strike and Dip) file format, there is a choice to connect each sample by ID or by Data Value.
Module Input Ports
read_lines has one input port that receives the Z-Scale factor
Module Output Ports
read_lines has three output ports:
The leftmost grey-beige port outputs the Z-Scale factor
The center (blue-black) port outputs a field comprised of lines with all defined data components.
The rightmost (red) port outputs a geometry that can be input to the Viewer for rendering.
Module Control Panel
The control panel of read_lines is shown in the figure above. The Load ELF\CSV\SAD File button opens a File Browser which lists the *.elf, *.sad, and *.csv files that are present in the current directory shown in the directory window. The format of each of these files is described in the help section.
Note that this module will not begin running until a valid file has been selected.
Log nodal data – This toggle sets the nodal data values to the log value of the input node data.
Log cell data – This toggle sets the cell data values to the log value of the input cell data.
Clip Min – This is only active if either Log processing for nodal or cell data is selected and sets the minimum value for each data value so that they can be correctly processed.
Data Component – This slider controls which data value to color the lines by.
SAD files connect by ID – If a *.sad file has been read the lines will be connected by ID.
SAD files connect by Data – If a *.sad file has been read the lines will be connected by the data component.
EVS line files contain horizontal and vertical coordinates, which describe the 3-D locations and values of properties of a system. Line files must be in ASCII format and can be delimited by commas, spaces, or tabs. They must have an .elf suffix to be selected in the file browsers of EVS modules. Each line of the EVS line file contain the coordinate data for one sampling location and up to 300 (columns of) property values. There are no computational restrictions on the number of lines that can be included in a file.
EVS Line Files
EVS Line Files consist of file tags that delineate the various sections of the file(s) and data (coordinates, nodal and/or cell data). The file tags are discussed below followed by portions of a few example files.
FILE TAGS:
The file tags for the ASCII file formats (shown in Bold Italics) are discussed below with a representative example. They are given in the appropriate order. If you need assistance creating software to write these file formats, please contact support@ctech.com.
COORD_UNITS "ft"
Defines the coordinate units for the file. These should be consistent in X, Y, and Z.
NUM__DATA 7 1
Number of nodal data components followed by the number of cell data components.
NODE_DATA_DEF 0 "TOTHC" "log_ppm"
NODE_DATA_DEF specifies the definition of a nodal data component. The second value is the data component number, the third is the name, and the 4th is the units.
CELL_DATA_DEF 0 "Indicator" "Discreet Unit"
Definition of cell data. Same options as NODE_DATA_DEF
LINE 12 1
Beginning of a line segment is followed on the same line by the cell data values.
Following this line should be the points making up the line in the following format:
X, Y, Z coordinates followed by nodal data values.
64718.310547 37500.000000 -1250.000000 1 -1250.000000
63447.014587 35101.682129 -2000.000000 2 -2000.000000
CLOSED
This flag is used at the end of a line definition to indicate the end of the line should be connected to the beginning of the line.
END
Marks the end of the data section of the file. (Allows us to put a password on .eff files)