Using templates

Creating a template
Organizing templates
Applying a template
Live viewing templates
What is imported from a template
Missing files from templates
See also

Creating a template

To create a template from an existing EV file for future use.

Click on the File menu
Point to Save Template
Click on either Copy to New Template or Copy to New Live Viewing Template (refer to the using live viewing templates page for details)

This opens the user-specified templates folders, if it exists. Otherwise the default templates folder opens for you to save the template.

Organizing templates

Organize your templates in templates folders. Echoview automatically scans this directory for templates when you create a new EV file from templates.

For live viewing templates, use the live viewing template folder instead.

Applying a template

You can only apply a template while creating an EV file. The new EV file imports the setup from the template.

Click on the File menu
Click New From Template...

If any templates exist in the templates folder, Echoview displays the New EV file dialog box to select a template. Otherwise, choose an existing EV file to serve as a template.

Alternatively, use the New command interface Action.

Note that if the template is being used (e.g., another Echoview session is saving changes to it) you need to wait for the processes on it to complete before you can use that template to create a new EV file.

Live viewing templates

Refer to the using live viewing templates page.

What is imported from a template

Echoview imports these objects, variables and settings into a new EV file from the template.

Object/Setting	What is copied
Template workspace files	Workspace files are created and saved when Creating a template and template live viewing files. The template workspace file is used when creating a new EV file from a template.
Filesets	Filesets are created in the new EV file as they appear in the template. The Fileset Properties dialog box settings allow you to choose how to derive raw variables. Echosounder data files are not inherited.
ECS files	The ECS file specified under the Calibration section of the Filesets window. Note: Fileset or SourceCal settings (and to a lesser extent LocalCal) may affect multiple EV files or multiple variables. For more information refer to Echoview Calibration Supplement files.
Raw variable definitions	All raw variable definitions are copied, but remain unavailable until data files are added which contain raw variables of the same name. The name of a variable is as it appears in the Raw Variables section of the Filesets window in the template.
Virtual variable definitions	All virtual variable definitions are copied, but remain unavailable until raw variables of the same name as each operand are made available by adding appropriate data files. The name of a variable is as it appears on the Dataflow window in the template.
Variable properties	All variable properties associated with raw and virtual variables in the template are copied to the new EV file with the associated variable definition.
EV file properties	All EV File properties are copied to the new EV file.
Lines	All editable lines and virtual lines are copied to the new EV file. All points are copied for editable lines. Lines that are dependent on another variable will remain unavailable until the required variable is made available by adding appropriate data files e.g. a virtual line created with the line operator Maximum Sv line pick will become available when the required variable is added. Note: The visibility of lines on echograms is set on the Lines page of the Variable properties dialog box for each acoustic variable.
Regions	Region definitions are not copied to the new EV file.
Scenes	All scenes are copied to the new EV file.
3D objects	3D objects are copied to the new EV file. However, 3D Regions associated with 3D schools are not supported.
Dataflow objects	The layout of objects in the Dataflow window are copied to the new EV file.
Sticky Notes	Sticky notes in the Dataflow window are copied to the new EV file.
Platform	Platforms are copied to the new EV file. Transducer and Media variables remember their linked platform. Platforms remember their raw variable source sand any variable attached to the platform.

Missing files from templates

The use of EV File page Save file locations relative to the EV File together with templates that use ECS files or Code operator Python files can encounter missing file messages. New EV files based on the template will not find expected files ECS or Python files, unless they are copied to the template folder.