TRANSIENT: An Overview

Page 1 of 10

AutoTransient: An Overview
The AutoTransient tool automates the “mechanical” parts of an analysis of transient phenomena with HIFREQ and FFTSES. It runs both programs in turn, using the computation frequencies recommended by FFTSES to run HIFREQ, until user-defined termination criteria are met. It also builds the FFTSES computation databases from the resulting HIFREQ databases (F21 files).

Technical Highlights     

The TRANSIENT program carries out the standard steps of a HIFREQ-FFTSES transient study automatically. Starting from template FFTSES and HIFREQ files (generated with CDEGS Input Toolbox, or any other editor), the program runs the Forward FFTSES and finds the first set of recommended computation frequencies. After running HIFREQ at those frequencies and building the FFTSES
Input Databases, the program runs the Inverse FFTSES and deduces the next set of recommended frequencies. This last step is repeated until the termination criteria are met.
You can choose to stop the program once there are no more recommended frequencies, when a specified amount of time has elapsed, or when a specified number of cycles of the above procedure have been carried out.
When running HIFREQ, you can choose to run all recommended frequencies, or to run only one frequency at a time. This last method, which would be very cumbersome to do manually, gives a lot of flexibility since many electrical properties (resistivities, permeabilities, etc…) can be varied as a function of frequency. The program allows you to specify frequency-dependent soil characteristics
through a simple dialog. With a little bit of programming effort, You can specify a frequency-dependence for any non-geometrical quantity defined in the HIFREQ template file.
The program performs basic data cross-validation between HIFREQ and FFTSES, to help avoid the most common data entry problems in a transient analysis.
You can interrupt the analysis at any time, then restart it where you left off.

Documentation Road Map
Access the following topics for more information.

Getting Started: Provides an overview of the process automated by the AutoTransient program, and describes a simple, typical, AutoTransient session.
Samples & Walkthroughs: Briefly describes the sample files that ship with the program.
Working With Projects and Scenarios: Shows you how to work with AutoTransient Projects and Scenarios.
Advanced Tasks: Describes some of the more advanced features of the program.

Getting Help
You can get help in several ways in AutoTransient. First, you can use the Help | Contents menu item to load this help file. Second, you can get context sensitive help from almost anywhere in the program by pressing the F1 key. This will bring up a help topic describing the part of the program that currently has the focus. Finally, many screens expose a Help button that load a help topic describing the
screen as a whole.
You can also go to the SES Web site at www.sestech.com. A simple way to access the SES web site while using AutoTransient is to select the Help | SES Web Site menu item.
You can get help on how to use the help system itself by pressing the F1 key when viewing the help file.

Getting Support
The following menu items are available to help you contact SES’ support staff quickly and efficiently:
Help | Contact SES Support: Starts a wizard that allows you to attach some files from your current AutoTransient project to an email message sent to SES’ support staff. See The Contact SES Support Dialog for details.
Help | SES Software Downloads: Directs you to the software download area of SES’ Web Site. This area contains the latest updates to the software that are available for download.
You can contact us by phone or fax using the coordinates available on our Web site at http://www.sestech.com/SES/coordinates.asp.

The Transient Study Process
Conceptually, the analysis of transient phenomena with HIFREQ and FFTSES involves the following steps:
1.
2.
3.
4.
5.

The conductor network being modelled is described in HIFREQ. This is typically done using Input Toolbox or SESCAD.
The characteristics of the surge (in the time-domain) is defined in FFTSES, using Input Toolbox.
The surge is decomposed in the frequency domain, by running FFTSES in "Forward" mode.
HIFREQ is run at all required frequencies.
The computation results of HIFREQ are collected, and FFTSES is run in "Inverse" mode to deduce the time-domain behavior.

In principle, Step 4 could require running HIFREQ at all frequencies defined in the Fourier Transform operation (FFTSES), typically 212 to 216 runs. This would require a very long time to run. In practice, only a subset of those frequencies are run. The FFTSES program suggests the frequencies that should be run, based on the shape of the input surge, and on the response of the conductor network. This is
an iterative process where the response of the network becomes progressively better defined as more and more frequency are run, until no significant improvements are noticed. This expands the last three steps of the above procedure into the following:
1.
2.
3.
4.
5.

The surge is decomposed in the frequency domain, by running FFTSES in "Forward" mode.
FFTSES analyses the shape of the surge in the frequency-domain, and suggests an initial set of frequencies (the recommended frequencies) at which HIFREQ should be run.
HIFREQ is run at the recommended frequencies.
The computation results of HIFREQ are collected, and FFTSES is run in "Inverse" mode to deduce the time-domain behavior. At the same time, FFTSES analyses the response of the network, and suggests new computation frequencies, if necessary.
If some new computation frequencies are recommended in the previous step, the process returns to Step 3; otherwise, the analysis ends.

It is this last procedure that the AutoTransient program automates.

Notes
You should be familiar with the HIFREQ and FFTSES programs before you can use AutoTransient. Consult the user's manual of those programs for more details.

A Typical Transient Session
This section outlines what can be done with AutoTransient and how to get started with the program. This is illustrated using the "Pole" sample Transient project, located under "Examples\Tools\AutoTransient\Pole" in your SESSoftware installation folder.
The main steps of a typical Transient session are summarized below:    

Starting AutoTransient. This includes opening an existing project file or creating a new one.
Specifying Input Data. Very little data needs to be specified in AutoTransient: most of the data is specified in the HIFREQ and FFTSES template files, created outside AutoTransient.
Processing the Data. This step carries out the computations, and produces several databases and (optionally) plots.
Ending a AutoTransient session.

Starting AutoTransient
To start the program, simply double-click the AutoTransient icon in your SES Software Program Group. The following screen should appear.

This screen displays general information about the AutoTransient project that is currently open. Initially, there is no project open, and you are prompted to create or open one.

The Open Project Dialog
The Open Project dialog is shown in the figures below. This dialog allows you to open an existing project (either from a list of recently used projects or by browsing to a Transient project file), or to create a new one.
In this case, the name and path of the project file should be provided, as well as the name and path of the first scenario of the project. The program suggests default values for these fields. The full path to the HIFREQ and FFTSES template files should also be provided.

file://C:\Users\aivanov\AppData\Local\Temp\~hhFD54.htm

13/02/2016

To save a project. It also contains all the computation results. The program runs HIFREQ at the recommended frequencies. plots.F05 FT_RunN.6 ft. . as well as plots and output files generated while processing the scenario. Samples & Walkthroughs Several samples are available in the folder "Examples\Tools\AutoTransient" in your SESSoftware installation folder. several messages appear on the Transient main screen to inform you of the progress and on the status of the operation.F27 FT_Forward[_M]. plots.e.htm 13/02/2016 . Files and Folders in a Project Several files and folders are created in a typical AutoTransient session. for instance.).tnt.F21 Purpose The FFTSES input file used in the Forward FFT operation. The extra data specified in Transient concerns information that is specific to a Transient analysis.. this folder contains the following files: File FT_Forward. A single project can be open at a given time. (See The Processing Options Dialog.F09 FT_Forward. FOP 200: The potential and current leads are parallel to each other. See The AutoTransient Scenario File for a detailed description of the contents of this file. several output and database files are created. it is recommended to use the default structure as much as possible.F21). A project is simply a collection of related scenarios. ‘My First Scenario’ and ‘My Second Scenario’.F07 FT_Forward. The template file for the FFTSES engineering program. output and result files for scenario ‘My Second Scenario’. Impulse Impedance: Simulates an impulse impedance measurement on a small (20 ft by 20 ft) grid. .F05 FT_Forward.tnt" (located under "Examples\Tools\AutoTransient\Pole" in your SESSoftware installation folder. to open the "Pole" sample. Plots of the desired quantities (GPR. A scenario defines all the data required to carry a complete transient study using HIFREQ and FFTSES. When several files are created. Sample Files The following sample Transient projects are available: Pole: Computes the transient response of a lightning rod. or an animation of those results as a function of time. Results Folder After a successful AutoTransient run. all result files (databases.) can also be created. a project must be created (or an existing one must be open).) are stored in the Results subfolder. The computation database file for the Forward FFT run of the FFTSES engineering program. but with current and potential leads of 200 ft. Note: It is possible to use a different kind of folder structure as the one described below. In particular. the Results folder contains files that can be used to produce plots and reports of the computation results (the FFTSES computation database files. the data not specified in the HIFREQ and FFTSES template files). Scripting: Illustrates the use of scripting code in a HIFREQ template file. you will be prompted to save changes to this last project and the project will be closed before opening the new one. Potential 40: Considers the case where the potential lead is very short (40 ft). or (for the soil model) through the use of a dialog. in the case where you run out of disk space on the drive containing a project.. and deduces the next set of recommended frequencies..f05 ft_Scenario Name. namely the specification of frequency-dependent soil properties and the use of scripting code in the HIFREQ template file. When the processing is finished. Advanced Features: Illustrates some of the more advanced features of AutoTransient. Folder Structure The figure below shows the folders that are created in a project called ‘My Project’ containing two scenarios.. This could be useful. you can review the computation results with GrServer or Output Toolbox (for the HIFREQ results at a single frequency). It can also contain the FFTSES and HIFREQ input files automatically generated by AutoTransient at every cycle of the run. use File | Exit. and also which scenario is currently the Active Scenario. Scenario File The scenario file (*. or to compute the transient response at points or segments that were not initially specified in the FFTSES template file (FT_*. and orthogonal to the current lead. Ending a Transient Session To quit the application and terminate the AutoTransient session. Contains the list of recommended computation frequencies obtained from an analysis of the frequency spectrum of the input surge defined in the FFTSES template file. and contains all input data specific to AutoTransient (i. if you attempt to create a new project or open an existing one while a project is currently open. usually in Input Toolbox and/or SESCAD.) In addition. The program will optionally prompt to save the project before terminating. The command syntax for those files is documented in the file Command. etc.tns) is the only file located in the root folder of the scenario.   Frequency-Dependent Soil: Illustrates the specification of a frequency-dependent soil model. The FFTSES input file used in the nth run of the Inverse FFT operation. using different measurement configurations. output and result files for scenario ‘My First Scenario’. The computation database file for the nth Inverse file://C:\Users\aivanov\AppData\Local\Temp\~hhFD54. It defines the location of all important files and folders for the scenario. SESCAD). Distance 200: This is similar to the base scenario. This topic describes those files and folders for the case where the default folder structure of projects and scenarios is used. select File | Open Project. with Output Toolbox for FFTSES to examine the results for a range of points or segments as function of time or frequency. To open an existing project. This can be used to plot the transient input surge that was used in the run.TRANSIENT: An Overview Page 2 of 10 For example.) Specification of the output and plot files that should be kept at the end of the analysis. Contains all input. Corner: The current injection is in a corner. In particular. The data should be loaded and displayed. Specifying Input Data Most of the data that is required in a Transient analysis is specified in the HIFREQ and FFTSES template files. electromagnetic fields.f05 Purpose The template file for the HIFREQ engineering program. Therefore.) Data defining the number of frequencies that should be carried out in each HIFREQ run. This file summarizes the calculations made. with a current lead of 200 ft and a potential lead of 125. This brings up a file browser that allows you to select an existing project file (with extension "TNT").tnt) stores the information regarding the scenarios that are part of a project. The list below describes the purpose of these two files. use the Existing tab. and that is meaningless to HIFREQ and FFTSES individually. (See The File Management Options Dialog. While the programs are running. namely:    The program runs FFTSES in Forward mode. FT_*. File hi_Scenario Name.F30 FT_RunN. Before anything can be done with AutoTransient. AutoTransient automatically runs HIFREQ at all those frequencies. This includes:    Data controlling under which conditions the analysis is considered complete. Contains all input. About Projects and Scenarios The data used in a AutoTransient session is organized into Projects and Scenarios. Processing the Data To begin the transient analysis. See The AutoTransient Project File for details. and browse to the file "Pole. select File | Save Project. This file is required when carrying out the inverse FFT operation. The list below summarizes the main points illustrated in each of the samples. In greater detail. These files must be created and edited outside Transient. it is possible to specify some HIFREQ input data that varies as a function of the computation frequency. including all FFTSES and HIFREQ databases. with very long current and potential leads (6000 ft). all result files (databases. The program runs FFTSES in Inverse mode. Templates Folder The FFTSES and HIFREQ template files for a scenario are located in the "Templates" sub-folder of the scenario folder. and 200 ft long. Contains plots of the time-domain input surge signal and of its frequency spectrum. This carries out the procedure described in the topic The Transient Study Process. select Project | Process. and the corresponding output files. either by using scripting. or using one of several input data processors from SES (Input Toolbox. or with FFT21Data to view the spatial distribution of the results at a given time..F8*).chm located in your AutoTransient installation folder. (See The Processing Options Dialog. and displays any relevant error or warning messages. at right angle to each other. This is the AutoTransient project file for the project. Note that several sample projects are available in the folder ‘Examples\Tools\AutoTransient’ in your AutoTransient installation directory. The AutoTransient Project File The AutoTransient project file (*. These folders contain the following files: Folder My Project My First Scenario My Second Scenario Files My Project. Nevertheless. The latter are stored in the Results and History sub-folders of the scenario... they are distinguished by the number M. You can modify those files by hand.F21 FT_Forward.      Base: Base scenario. See About Projects and Scenarios for more details on the notion of Projects and Scenarios in AutoTransient. Output file for the Forward FFT run for FFTSES. with the current and potential leads orthogonal. Contains the frequency spectrum of the input surge defined in the FFTSES template file. Files and Folders in a Scenario The scenario folder contains all the input files needed to carry out a specific AutoTransient study. After each step.) are stored in the Results subfolder.

Click OK to confirm.F8* FT_RunN.). This last option is useful when you want to examine small design variations. In greater detail. i.     To define general scenario properties. through a list of recently open projects. When several files are created. Opening an Existing Project To open an existing AutoTransient project:   Select File | Open Project.e. Remarks The newly created scenario automatically becomes the Active Scenario. those that are based on the largest number of computation frequencies. without having to recompute the current distribution in the network. The FFTSES Input Databases computed in the last step of the processing. When a project contains a single scenario. Normally.F30 HI_RunN. Otherwise. In addition to those files. which can be edited at all times using the Project Properties dialog. select Project | Edit Scenario File Management Options . these frequencies are run in the (n+1)th cycle. to make sure that not too much computation effort is lost. only one of them can be processed. or a text editor to prepare a HIFREQ and a FFTSES input file (F05). The database and output files are produced using the usual naming conventions for CDEGS files. Select Project | Delete Scenarios. or for any other reason. Processing a Scenario Once the data for a scenario is specified. the original files are not used directly. You can elect to delete all output files generated in the last cycle to prevent this situation. Note: The 'JobID' for the scenario is the ‘Scenario Name’ and the selected location for the scenario is used as 'Working Directory'. the files in this folder can help determine the source of the problem. The program begins the AutoTransient process. Note also that this operation cannot be undone (even if the scenario files are not deleted) in the sense that it is currently impossible to import a scenario in a project. Making a Scenario the Active Scenario The Active Scenario of a project is the only scenario that can be run.. for instance. the analysis can begin. etc.f21. by default some of the files that contain rarely used or redundant information are not kept. and will be needed at Step 3. In the Define Template Files dialog. 2. Importing Template Files into a Scenario It is sometimes convenient to change the template files associated to a scenario. 4. default scenario or to create a copy of an existing scenario of the project. Creating a New Project To create a new AutoTransient project: 1. With minor exceptions. you can choose to share or copy the template files of that scenario instead of browsing to a new file. These files represent the "best" results obtained so far in the analysis. You can do this by importing new template files into the scenario. If the new scenario is based on an existing scenario of the project.F8* HI_RunN. Select Project | New Scenario. When a run terminates abnormally (because of a program error). specify a template file for either FFTSES or HIFREQ. Remarks This command is available only when there are at least two scenarios in a project. This can prevent the process to restart successfully. 4. Adding a Scenario to a Project It is possible to have several different scenarios in an AutoTransient project. This file can be used to re-run the case more quickly. i. This file can be used to create plots and reports of the response of the network at any of the frequencies that were run in the cycle. you are prompted to save any open project (if necessary) before creating the new project. Once the processing has stopped. The new project is created under the filename ‘Project Name’.tns where ‘Project Name’ and ‘Scenario Name’ are the provided names of the project and scenario. specify at which point to restart the processing. 2. you may want to remove scenarios from a project. the program creates the requested database and plot files. In the Stop Processing Options dialog. This is typically used to regroup cases that are related in some ways. it can be advantageous to restrict the number of frequencies that are computed in each HIFREQ run. You are prompted for the location and name of the project as well as for the name and location of the first scenario of this project. The exception is the Description of the scenarios.. to easily study the same conductor network under different energizations. The scenarios can share data with each other. Output file for the nth Inverse FFT run for FFTSES. Assuming the processing is not interrupted. Select Project | Start Processing. all frequencies remaining in the current HIFREQ run will be processed before the program stops the processing. select the desired scenario and click OK. Select File | New Project. a transient study can require a substantial amount of time. You can browse to any valid FFTSES/HIFREQ file. or when an explicit Stop Processing command is issued. they are distinguished by the number M. Select Project | Activate Scenario. See The AutoTransient History File for a detailed description of the contents of this file. the Define Template Files dialog prompts you to specify the HIFREQ and FFTSES template files for the scenario. 3. the Define Template Files dialog prompts you to specify the HIFREQ and FFTSES template files for the first scenario of the project. In the Select Active Scenario dialog. and make sure to activate that scenario. Work Folder The Work folder contains temporary files that are created and destroyed while AutoTransient processes a scenario.F05 HI_RunN. making it possible. When opening a project that contains several scenarios. and overwrite any existing file in the Templates folder. Remarks Since only one project can be open at a given time. and displays any relevant error or warning messages. or to wait until the end of the current processing cycle. The HIFREQ computation database file computed in the nth AutoTransient cycle. See The Processing Options Dialog for details. SESCAD.F07 FT_Scenario Name. History Folder The History folder contains files that are required to help restart an AutoTransient run. To specify the Processing Options.F09 Page 3 of 10 FFT run of the FFTSES engineering program.F27.OR Select a recently opened project file directly from the File menu. Output file for the nth cycle run for HIFREQThis file summarizes the calculations made. Click OK to confirm. It is not unusual to have to interrupt a study in order to free the computer for other activities. 2. In the Restart Options dialog.F07 FT_RunN. or for both programs. This can be used to plot the transient response of the network when only the frequencies included up to the nth cycle are included. HI_Scenario Name.HIS Purpose The frequency spectrum file for the input signal used in the scenario. When selecting the first option. This behavior can be customized. perhaps because they contain erroneous data. Press the Ctrl or Shift keys to select several scenarios. Editing a Scenario Most of the data of an AutoTransient scenario can be edited only when the scenario is the Active Scenario. In the Delete Scenarios Dialog select the scenarios to delete. The HIFREQ computation databases for all processing cycles. Once the Scenario name and location are defined. respectively. 2. The program issues several messages indicating the progress of the calculations.F05. the scenario is always active. Stopping and Restarting a Scenario When dealing with a large conductor network. the database file for FFTSES is produced in the scenario directory under the name ft_'Scenario Name'. file://C:\Users\aivanov\AppData\Local\Temp\~hhFD54. 2. 3. you have to provide a unique name for the new scenario. with a few additional options. The files specified at Step 3 are copied to the Templates folder of the scenario. use Project | Edit Scenario Processing Options . Note that these files need not be all present in the Results folder. the data that controls under which conditions the processing of the scenario should stop. Restarting a scenario is similar to processing the scenario for the first time. For example. the program should take very little time to stop processing the scenario.e. the Active Scenario is the only one that can be edited. These files are to be used as templates by AutoTransient.htm 13/02/2016 . Plot files showing the frequency and time-domain response of the network after the nth run of the Inverse FFT operation. The name of the Active Scenario is displayed in the Project Summary section of the main screen of AutoTransient. Open the project containing the scenario to restart.. 3. To add a new scenario to a project: 1. Once the Scenario and Project names are defined. This file summarizes the processing history of the scenario. You can browse to any valid FFTSES/HIFREQ file. specify whether to stop immediately. use Project | Edit Soil Model . You can browse to any valid FFTSES/HIFREQ file. this folder contains the following files: File FT_Scenario Name. To make a scenario the Active Scenario: 1. To define the files that the program should keep at the end of each processing cycle. this folder should normally be empty. The resulting screen offers three different ways to open a project: through a standard file browser. Almost all commands in AutoTransient target the active scenario. the last of the "RunN" files is copied under the standard JobID for the scenario (e. should it be interrupted for any reason. use Project | Properties.F09 FT_RunN. To do this. Use Input Toolbox.tnt and the scenario under the filename ‘Scenario Name’. The HIFREQ "Current Recovery" file computed in the nth AutoTransient cycle. simply select Project | Start Processing. the output files of the program can be left in a corrupted state. AutoTransient simplifies this process by allowing you to stop and restart a run with minimal loss of data and time. When the option to stop immediately is selected. Input database files for the (n+1)th Inverse FFT run of the FFTSES engineering program.F27 FT_RunN[_M]. The FFTSES input surge frequency spectrum file used in the nth run of the Inverse FFT operation. and as a brand new project. and places them in the Results folder for the scenario. Proceed as follows to edit the various types of data required in AutoTransient. Either way. 2. At the end of a successful run. This file summarizes the calculations made.F21 HS_Scenario Name. Select Project | Import Templates in Scenario. Select whether to delete all files and folders for the selected scenarios. Select Project | Stop Processing. To stop a running scenario: 1. These files can be used to obtain quickly the response of the network at points or segments that were not initially defined in the FFTSES template file.F33 HI_RunN. This file lists the recommended computation frequencies based on an analysis of the frequency response of the network after the nth run of the Inverse FFT operation.g. Leave the field blank if you want to keep the existing template file for a program. . Deleting Scenarios from a Project Occasionally. To import a template file into a scenario: 1. Remarks It is not possible to delete the active scenario. The HIFREQ input file used in the nth AutoTransient cycle. you can save the project and exit the program. and stops processing only when the termination conditions are met.F21 HI_RunN. and displays any relevant error or warning messages. You have the choice to create a brand new. 2. and click OK. The Active Scenario Many projects will contain only a single scenario. Remarks Since it is often preferable to delete the output files created in the last processing cycle (when the processing is stopped immediately). This scenario is called the Active Scenario. 3. To delete scenarios from a project: 1. To restart a scenario: 1. Click OK.TRANSIENT: An Overview FT_RunN. 3. To view or specify the frequency-dependent characteristics of the soil model. FT_Scenario Name. The selected template files are imported in the project. See The File Management Options Dialog for more details.

DisplayFrequency The frequency in string form. using the file created at Step 1 as the HIFREQ template file. allowing you to define which of the existing computation results to use in the current processing session. check the Define a frequency-dependent soil model option. as well as the location of the FFTSES and HIFREQ template files for the scenario. To do this.) Specify a file for the other template file.       File: Regroups functions related to opening and saving of project files. Select a Layer to modify. Options: Regroups functions that allow you to define program-level options. Edit Soil Model: Loads the Define Soil Model dialog.               Start Processing: Starts (or restarts) processing the current scenario. Activate Scenario: Activates a scenario of a project. adding or removing scenarios in a project. View FFTSES Forward Output File: View the FFTSES Output file (F09 file) for the Forward operation. Currently. View/Plot HIFREQ Results: View or plot the HIFREQ computation results. adding or removing scenarios in a project. In the New Scenario Dialog. RunN. New Scenario: Creates a new scenario. In the Reference Scenario section. that allows you to define the name and location of the new project and of its first scenario. permittivity. Click OK. 7. or processing a scenario of a project. The main difference between this value and the Frequency property is that the latter never reaches 0 while the DisplayFrequency does. The properties (resistance. This command is only available when there are several scenarios in a project. In AutoTransient. Remarks When using a frequency-dependent soil.  Work Folder: Opens the 'Work' folder for the active scenario.  With MultiPad: Use the MultiPad text editor to edit the file.TRANSIENT: An Overview Page 4 of 10 Remarks This restart option can also be used to compute the desired quantities at different observation points or segments than were initially specified in the FFTSES template input file. the frequencies computed in HIFREQ for one input surge are also suitable for a different input surge. Import Templates in Scenario: Imports a FFTSES template file or a HIFREQ template file (or both) in the active scenario. When some scripting code is detected in the HIFREQ template file. Usually. allowing you to control which FFTSES and HIFREQ output files to keep in each iteration cycle of the processing of the active scenario. This loads the Define Template Files dialog. The AutoTransient Menu Bar The menu bar gives access to all the functions of the program. Prepare a HIFREQ input file (F05) containing the desired scripting code. Edit Processing Options: Loads the Processing Options dialog. such as setting project options. The Tools Menu The Tools Menu regroups functions that give access to various utilities to edit or view the template files of the active scenario. define its Thickness . In the Define Soil Model dialog. View FFTSES Inverse Output File: View the FFTSES Output file (F09 file) for the last Inverse operation preserved in the Results folder. AngularFrequency The angular frequency (2πf) corresponding to the above frequency. 2. the program executes the specified script. View/Plot FFTSES Forward Results: View or plot the FFTSES computation results extracted from the computation database (F21) for the Forward run. This command loads the New Project dialog. Save Project: Saves the currently loaded project and all of its scenarios. The use of scripting in an input file follows the same rules as in the SESScript program. .  Results Folder: Opens the 'Results' folder for the active scenario. Electromagnetics Calculator: Launches the Electromagnetics Calculator. 2. the program automatically switches to computing only one frequency at a time. or processing a scenario of a project. You can do this by specifying the characteristics at several values of the frequency. This command can also be accessed through the Open Project button on the toolbar. The Project Summary region: Gives summary information about the project that is currently loaded and its active scenario. and click OK. and permeability) of the soil are known to vary to some extent as a function of frequency. The Messages region: Displays detailed messages about the state of the program. then the Start Processing command should be used. permittivity.htm 13/02/2016 . 2.. as well as the number of frequencies to run in each iteration cycle. and the status bar provides summary information about the last operation carried out in the program. The resulting file is used as input file for HIFREQ for that computation frequency. This command can also be accessed through the New Project button on the toolbar. (This is also done automatically whenever the Start Processing function is invoked. This command loads the Open Project dialog. the scenario that used to share the data behaves as an ordinary scenario. The electrical characteristics (resistivity. View/Plot FFTSES Inverse Results: View or plot the FFTSES computation results. If the layer is frequency-dependent. using the FileView file viewer.  With FFT21Data: Use the FFT21Data utility to view or plot the results.) Clear Messages: Clears the Messages section of the main screen. inductance) of lumped impedances. If a modified project is currently loaded. permittivity and permeability. the decision to share data must be made when creating a new scenario: there is no way to share data when a scenario is already created. the normal template file diagnostics are turned off. The File Menu The File Menu regroups functions related to opening and saving of project files. and evolves independently of the reference scenario. (This is also done automatically whenever the Start Processing function is invoked. It is divided into four areas:     The Menu Bar: Gives access to all the functionality of the program. This is not available currently. 8. To break the data sharing connection between two scenarios: 1. Check the Frequency Dependent option if the selected layer is to made frequency-dependent. and permeability) of the soil. e. This file is read from the History folder. 9. and other support options. You can. or field quantities to compute. or the computation results.g.  With Output Toolbox: Use CDEGS' Output Toolbox to view or plot the results. or to stop immediately. Notes:   Use of this feature requires some programming knowledge. Open Project: Opens an existing project. Resume Processing: Resumes a processing session that was previously paused with Pause Processing. You have the option (with the Stop Processing Options dialog) to wait until the current processing cycle is complete before stopping. If a modified project is currently loaded. segments. allowing to define a name and location for the scenario. This file is read from the Results folder.  With Input Toolbox: Use CDEGS' Input Toolbox to edit the file. Click OK to confirm the changes.  With Output Toolbox: Use CDEGS' Output Toolbox to view or plot the results. This command can also be accessed through the Save Project button on the toolbar. file://C:\Users\aivanov\AppData\Local\Temp\~hhFD54. the program automatically runs only one frequency at a time in the HIFREQ runs.. You can also do this by simply closing the main screen. In the resulting Define Template Files dialog. the Restart Options dialog is shown. allowing you to control which FFTSES and HIFREQ output files to keep by default in each iteration cycle of the processing of a scenario. Specifying Frequency-Dependent Soil Parameters The electrical characteristics (resistivity.  AutoTransient Installation Folder: Opens the installation folder of the program. allowing you to select the scenario of the current project that should be activated. This loads the New Scenario dialog. providing the computation frequency through the "AutoTransient" object. although this is considerably less useful. Pause Processing: Pauses the current processing session. Remarks When breaking the data sharing connection. Break Data Sharing: Breaks the data sharing connection of this scenario with its source scenario.  Scenario Folder: Opens the folder containing the scenario file for the active scenario.          Edit HIFREQ Template File: Edits the HIFREQ Template file. as extracted from the computation database (F21) for the last Inverse run preserved in the Results folder. The View Menu The View Menu regroups functions that control the visibility of some interface elements. It also prompts you to provide the location of an FFTSES and a HIFREQ template file for the scenario. break the data sharing connection between two scenarios at any time.) Messages: Controls whether the Messages section of the main screen is visible or not. Edit FFTSES Template File:  With Input Toolbox: Use CDEGS' Input Toolbox to edit the file. using the FileView file viewer. you will be prompted to save before opening the new project.  Project Folder: Opens the folder containing the project file. enter those quantities for all frequencies for which you have data. allowing you to define the default processing options. a small tool that allows you to compute the propagation characteristics of electromagnetic waves as a function of frequency in a medium of known resistivity. Exit: Exits the program. If this is not the first time the scenario is run. otherwise leave it cleared. These settings apply by default to all new scenarios created in Transient. These settings are used to determine under which conditions the processing should terminate. Project: Regroups functions related to project management. This command can also be accessed through the Start Processing button Stop Processing: Stops the current processing session. 2. Sharing the computation databases in this case can greatly reduce the required computation time. you will be prompted to save before opening the new project. as extracted from the computation database (F21) for the last run. This is particularly useful to examine the effects of different input surge signals on the response of the same conductor network. Delete Scenarios: Deletes some scenarios from the project. permittivity. specify the Scenario File Location. and adds it to the project. The Frequency is prevented to reach zero (the minimum value is 10-6) to avoid possible problems that could occur in the script at f=0. the program interpolates and extrapolates the rest. Edit File Management Options: Loads the File Management Options dialog. The Program Output region: Shows the output of the HIFREQ and FFTSES programs when processing a scenario. you can account for this effect by specifying a soil model for which the characteristics of selected layers are dependent on the computation frequency.  With GrServer: Use the GrServer utility to view or plot the results. select the Based on Existing Scenario option. This loads the Delete Scenarios dialog. using the FileView file viewer. The Options Menu The Options Menu regroups functions that allow you to define program-level default settings. To share data between two scenarios: 1. Select Project | Edit Soil Model. The AutoTransient Main Screen This screen is the starting point for all operations in the AutoTransient program. allowing you to to define a frequency-dependent soil model in HIFREQ. Examples include:      The electrical characteristics (resistivity. Browse: Opens a Windows Explorer in one of the active scenario's important folders. which allows you to select the project file to open by either browsing to it. Use this dialog to view or edit descriptions of the various files in the project. freeing program resources for other applications. View HIFREQ Output File: View the HIFREQ Output file (F09 file) for the last run preserved in the Results folder. From this point on. If a modified project is currently loaded.  With Output Toolbox: Use CDEGS' Output Toolbox to view or plot the results. select the option Share template file from scenario "Scenario Name" for either the HIFREQ Template File or the FFTSES Template File. If the selected layer is the Top layer of a two-layer soil model. For every computation frequency. allowing you to select the scenario(s) to delete. the toolbar gives a quicker way to access some important functions of the program. 3. and permeability for the layer.  With FFT21Data: Use the FFT21Data utility to view or plot the results. and select the scenario with which to share data in the drop-down menu. File Management Options: Loads the File Management Options dialog. since this would generate a scenario identical to the reference scenario. on the toolbar. The data sharing connection is broken automatically (after a warning message) when deleting the scenario that acts as the source of the data. (It is not possible to share both files. This command can also be accessed through the Stop Processing button on the toolbar. Repeat Steps 4 to 7 for all layers of the soil model. the FFTSES template should first be modified to define the new points. These settings are used to determine under which conditions the processing should terminate.   Processing Options: Loads the Processing Options dialog. Remarks The AutoTransient scripting object has the following properties: Property Name Description Frequency The computation frequency (in Hz) for the run. In addition. Tools: Regroups functions that give access to various utilities to edit or view the template files of the active scenario. Help: Gives access to the program's help file. To specify a frequency-dependent soil model: 1.    Clear Program Output: Clears the Program Output section of the main screen. Select the desired Soil Type. Moreover. The strength of the ENERGIZATIONs. You can also select to create a brand new project with this command. This feature can also be used to share the same input signal information (FFTSES template file) for two different conductor networks. allowing you to define the processing options for the active scenario.  With SESCAD: Use SESCAD to edit the file. One addition is the "AutoTransient" object which can be accessed through the script and that defines the computation frequency. Click OK in the resulting message window. although they can be overridden using the commands of the Project menu. Enter the resistivity. This loads the Activate Scenario dialog. such as setting project options. you will be prompted to save before creating the new project. RunNumber Identifies the run number.      New Project: Creates a new project. Properties: Loads the Project Properties dialog. View: Controls the visibility of some interface elements. Sharing Data Between Scenarios It is possible to share the HIFREQ computation databases between different scenarios of a project. Create a new project or a new scenario. 3. Using Scripting in AutoTransient You can use scripting code to specify several quantities in the HIFREQ input file as a function of frequency. however.  With MultiPad: Use the MultiPad text editor to edit the file.  Templates Folder: Opens the 'Templates' folder for the active scenario. and permeability) of conductors. This command is only available when there are several scenarios in a project. allowing you to specify the location of the desired template file(s). It is not possible to delete the active scenario of a project. Select Project | Break Data Sharing. for display purposes. or the computation results. as well as the number of frequencies to run in each iteration cycle. See Sharing Data Between Scenarios for more details. Refer to that program's documentation for more details. The properties of the Context object of SESScript can also be used in the scripting code. 5. or picking it from a list of recently open projects. 4. permittivity. Select Project | New Scenario. This number appears in the JobID for the run. The Project Menu The Project Menu regroups functions related to project management.  History Folder: Opens the 'History' folder for the active scenario. 6. To use scripting code in a scenario: 1. the necessary files are copied from the reference scenario to the scenario that shares the data. This is not available currently. Recent Projects: Opens the project file for one of the most recently used projects.

but its files are still available on disk. The Electromagnetics Calculator The Electromagnetics Calculator tool (Tools | Electromagnetics Calculator) is a simple tool that allows you to calculate the propagation characteristics of an electrical medium as a function of its electrical parameters and of the frequency.TRANSIENT: An Overview Page 5 of 10 The Help Menu The Help Menu regroups functions that give access to the program's help file. These files should be prepared before attempting to create a new AutoTransient project. The default for this file is to keep the last file only. using a standard file browser (on the Existing tab). Contact SES Support: Starts the Contact SES Support wizard. Remarks Once this dialog is closed. These files should be prepared before attempting to create a new Transient scenario. it will be created. something that is useful to know when defining the segmentation of the conductor network in HIFREQ. First File Only: Keep only the file produced in the first run. (on the Recent tab) To create a brand new project.. The default is to keep none of those files. The default for these files is to keep the last file only. If the folder doesn't exist. Scenario File Location: Full path to a folder that is to contain the scenario file. File Types Type of File Description The FFTSES Input file. In addition to using the File Selectors to specify the filename..  Based On Existing Scenario: Allows you to select one the project’s existing scenarios as a reference. The Forward FFTSES Output file (F09). In this case. The HIFREQ Computation Database (F21) file. This name is used to identify all the files produced by the program for this scenario. The File Management Options Dialog The File Management Options Dialog allows you to select which of the HIFREQ and FFTSES output files to keep at the end of an AutoTransient analysis. Remarks You cannot delete the active scenario of a project. The data of the default scenario is as specified in the program default settings. it will be created. The default is to keep the first of those files. Remarks Once this dialog is closed. They can be overridden for the active scenario using Project | Edit Scenario File Management Options. you should modify the Project File Location only after you defined the Project Name. When creating a new project. select the scenario(s) to be deleted from the list. Similarly. you can elect to either share or copy the template file of the reference scenario (specified in the New Scenario dialog). The default for this file is to keep the first file only. The default for this file is to keep the last file only. Use this option when you want to create a new scenario that represents a small design variation on an existing scenario. Click on the Browse button (…) to browse to an existing folder. and the group velocity (∂ω/∂k). One of these quantities should be specified. This wizard allows you to send a support request to SES via email. This makes it easier to find the project files subsequently. The Inverse FFTSES Output file (F09). The program can compute these quantities as a function of frequency. it will be created.  Wavelength: Propagation wavelength. Delete all files and folders for the selected scenarios: Select this option if you want to delete all scenario files from disk. The default is to keep all files of this type. in meters. The filenames must be specified explicitly. While this is not recommended. The HIFREQ Output file (F09). both the HIFREQ and FFTSES template files must be specified explicitly. both the HIFREQ and FFTSES template files must again be specified.  Frequency: Computation frequency. you should modify the Scenario File Location last. SES Web Site: Opens the home page of the SES Web site in your default Web browser. and shows its index. and easily attach important files from your project to the message. Last File Only: Keep only the file produced in the last run. or to create a new one. Importing Template Files When importing template files. These adjustments establish a standard structure for the project folders. You can also copy one or both template files from the reference scenario. Regular updates to the program will be posted at this location. When creating a new scenario. The FFTSES Spectrum Scaling (F07) file. or can compute the frequency needed to reach a specified wavelength. When sharing a template file. Scenario File Location: Full path to a folder that is to contain the scenario file. you can import only an FFTSES Template file. the Scenario File Location is also adjusted whenever you change the Project File Location to make sure that the scenario file is located in a sub-folder of the project folder. About AutoTransient: Shows general program information. In addition to the wavelength. Propagation Constants: Computed propagation characteristics of the medium. To select a project file from a list of recently used projects. The settings defined in this case apply by default to all new scenarios. you will be prompted to specify the path to template files for FFTSES and HIFREQ. since any change to the other fields of the screen automatically modify the Scenario File Location. This folder will also contain all other files created by the program. the program automatically adjusts the Scenario File Location field to make sure the scenario file is located in a folder with the same name as the scenario. The default for this file is to keep the last file only. The Activate Scenario Dialog The Activate Scenario Dialog (which can be accessed with Project | Activate Scenario) allows you to select a new active scenario. this tool calculates the wavenumber (k). The default for this file is to keep the first file only. If you chose to do so. Similarly. The Open Project Dialog The Open Project Dialog (Open | Project) allows you to open an existing project. this dialog allows you to change the active scenario. by browsing to the desired file (click on the . a HIFREQ Template file. relative to that of the vacuum. If you chose to do so. since changing the Scenario Name automatically modifies this field.       Content: Loads the program's help file. (on the New tab) Remarks See The New Project Dialog for details on how to specify data on the New tab. The Define Template Files Dialog This dialog is used in three different contexts: 1. Creating a New Project When creating a new project.htm 13/02/2016 . The FFTSES Animation (F85) file. the changes made to the template files are not propagated to any other scenario. file://C:\Users\aivanov\AppData\Local\Temp\~hhFD54. Using the File Selector The File Selector allows you to select a filename either from a list of recent files (through the drop-down menu). or by typing the filename directly. SES Downloads: Opens the Downloads page of the SES Web site in your default Web browser. To use the dialog. using their respective File Selector.  Default: A default scenario is created. you will be prompted to specify the path to template files for FFTSES and HIFREQ. The default for this file is to keep the first file only. Creating a New Scenario When creating a new scenario of a project. not both. you can use a different structure for the scenario folders. Click on the Browse button (…) to browse to an existing folder. Properties of Propagation Medium: Defines the electrical properties of the medium. (Note that all such files are kept as part of the processing history). Reference Scenario: Allows you to define a scenario to be used as reference when creating the new one. The Inverse FFTSES Computation Database (F21) file. The behavior of the dialog differs according to the context. The default for this file is to keep the last file only. and click OK. The default is to keep the last of those files. When importing a FFTSES or HIFREQ template file (or both) in an existing scenario. While this is not recommended. when you type something in the Scenario Name field. The default is to keep all files of this type.  Resistivity: Resistivity of the medium. The HIFREQ Current Recovery (F33) file. The Delete Scenario Dialog The Delete Scenario Dialog (which can be accessed with Project | Delete Scenarios) allows you to delete one or more scenarios from a project. The Forward FFTSES Plot Files. The default for this file is to keep the first file only. In particular. 2. The default is to keep none of those files. This adjustment helps establish a standard structure for the scenario folders. If the folder doesn't exist. This folder will also contain all other files created by the program. The default for this file is to keep the last file only. The following information must be provided:    Scenario Name: Desired name of the scenario. Index: Loads the program's help file. See Sharing Data Between Scenarios for an overview of data sharing in AutoTransient. the program automatically adjusts the Scenario File Location field to make sure the scenario file is located in a folder with the same name as the scenario. or both. The HIFREQ Conductor Segment Information (F17) file. This dialog can be used in one of three ways:    To browse to an existing project file. relative to that of the vacuum. the attenuation constant (α). Remarks This tool is completely independent: none of the data specified here is used anywhere else in AutoTransient. The default for this file is to keep the last file only. the changes made to the file are automatically reflected in all scenarios using that file. None: Do not keep any files of this type. Scenario Name: Desired name of the first scenario of the project. button). This command can also be accessed through the Help button on the toolbar. This name is used to identify all files produced by the program for this scenario. For each of the available types of files. or if you intend to share data with this scenario. You will be warned if you try and delete a scenario that is the source of data shared with other scenarios of the project. Finally. and other support options. To use the dialog. The Inverse FFTSES Plot Files. The following information must be provided:     Project Name: Desired name of the project. using their respective File Selector. you should modify the Scenario File Location last. the program automatically adjusts the Project File Location field to make sure the project file is located in a folder with the same name as the project. The Forward FFTSES Recommended Frequencies (F27) file. Remarks Most of the commands in AutoTransient (including the commands controlling the processing of a scenario) apply only to the active scenario of a project. and click OK. The default is to keep all files of this type. select a scenario from the list. it can calculate the propagation wavelength in a medium. 3. To select the files to keep by default when processing a scenario (Options | Default File Management Options). If the folder doesn't exist. You can only share either the FFTSES or the HIFREQ template file.  Relative Permittivity: Permittivity of the medium. you can use a different structure for the project folders. and shows its table of contents. Frequency and Wavelength: Computation frequency and wavelength of propagation in the medium. Usage Notes When you type something in the Scenario Name field. in Ω-m. The HIFREQ Input file. The new scenario becomes a copy of the selected reference scenario. When this option is not selected.  Relative Permeability: Permeability of the medium. Click on the Browse button (…) to browse to an existing folder. This dialog can be used in two different contexts:   To select the files to keep when processing the active scenario (Project | Edit Scenario File Management Options). the scenario is removed from the project. The New Project Dialog Use this screen to create a new project. the other is computed. The Inverse FFTSES Recommended Frequencies (F27) file. Generally. Usage Notes When you type something in the Project Name field. the phase velocity (ω/k). an AutoTransient analysis can generate one file of each type for each iteration of the procedure (corresponding to one or more computation frequencies). The settings defined in this case apply only to the active scenario. you can select one of the options below:     All Files: Keep all files of this type generated during the entire process. The FFTSES Input Databases (F81-F84) files. The HIFREQ Plot files (F22-F23). General Behavior The OK button in the dialog becomes available only when all necessary filenames have been defined and point to existing files. Project File Location: Full path to a folder that is to contain the project file. in Hz. The New Scenario Dialog Use this screen to create a new scenario. In a multi-scenario project. The Forward FFTSES Computation Database (F21) file.

Soil Type: Selects the soil model. Resistivity: Defines the resistivity of the layer. permittivity. To avoid this problem. This is the safest restart option to use. To avoid this problem. Consult the topics Diagnostics . you can easily specify the same value for several cells by selecting the desired cells and typing the value. Frequency: For a frequency-dependent layer. Make sure to browse to a valid HIFREQ F05 file generated by one of the dedicated SES editor programs (Input Toolbox or SESCAD). Comments can be attached to the project as a whole. and to attach descriptions/comments to those files. The Restart Options Dialog The Restart Options Dialog is automatically invoked by the program when the Start Processing command is used and the program detects the presence of some output files from a previous run in the History folder. a value of 1 is used. This normally happens as a result of selecting the wrong type of file when browsing for a template file. the program may have to wait a very long time before stopping. This can result in corrupted output files and can make it difficult to restart the analysis. It could also happen when modifying a template file by hand. Diagnostics . Nothing to Extract: Nothing was requested to be extracted from the FFTSES input databases in the FFTSES template file. Input Diagnostics in AutoTransient The HIFREQ and FFTSES template files that can be used in AutoTransient are subject to some constraints that do not normally apply when those programs are used by themselves.TRANSIENT: An Overview Page 6 of 10 The Processing Options Dialog The Processing Options Dialog allows you to control the way in which the individual cycles of the iteration are carried out in an AutoTransient analysis. By default. The following options are available in this dialog: Define a frequency-dependent soil model: Instructs the program to use a frequency-dependent soil model. permittivity. the number of frequencies computed in any given HIFREQ run does not exceed a value specified in Maximum Number of Frequencies. FFTSES Syntax Error: Syntax errors were found in the FFTSES template file. If not specified.. This is applicable only to the Top layer of a Two Layer soil. Diagnostics . When this option is not checked. The settings defined in this case apply by default to all new scenarios.Air and Earth .. When running a single frequency at a time. and also to describe various aspect of the input data. however. To avoid this problem. It could also happen when modifying a template file by hand. using 3 cycles yields decent results. only a few frequencies are lost. Diagnostics . and attempts to restart the processing by using all HIFREQ computation database (F21) files found in the History folder of the scenario. For the frequency-dependent case.   Use all the HIFREQ Computation Database Files present in the History folder: When this option is used.. but you cannot modify them. You can easily specify a range of linearly spaced frequencies by using the Fill Cells feature of the data grid. Invalid Script: The HIFREQ template file contains invalid scripting code. the program ignores the information contained in the History file. Right-click the grid and select Fill Cells to use this feature. a value of 1 is used. It can be used to view the path of the project and scenario files that are part of the project. valid output files (in the Results and History folders). The following options are available: Ignore all existing files and restart from scratch: Restarts the processing from scratch. Note that when using a frequency-dependent soil model. The main disadvantage of this approach is that it can create a very large number of files. This has the same effect as starting the processing the first time. which means that the program will carry out as many iteration cycles as is necessary to meet the other conditions. or it is found too late (after too many unrecognized commands). To define the default processing options to use when processing a scenario (Options | Default Processing Options). This dialog allows you to control the behavior of the program under such conditions. in per-unit. When this option is selected. Note. However. permittivity.) may not work correctly when using this option. When extrapolating the values at frequencies below the specified range. This means that the FFTSES command is not found in the file at all. rather than trying to append to them.Air. Diagnostics . and permeability of the layer. The program cannot process a scenario until a valid HIFREQ template file is specified. If not specified. Thickness: Defines the thickness of the layer. Likewise. This analysis of the template files is triggered whenever a template file is imported into a scenario. It can also report more fundamental problems that would affect those files whether they are used in AutoTransient or not.No Conductors in HIFREQ Template File Description A file imported as a HIFREQ template file does not contain any CONDUCTOR commands.Invalid HIFREQ Template File Description A file imported as a HIFREQ template file was not recognized as a valid SICL command file for HIFREQ. Frequency Dependent: Controls whether or not the characteristics of the selected layer are frequency-dependent. all other options are unavailable. when extrapolating the values at frequencies above the specified range.    There are no more recommended frequencies: The processing stops as soon as FFTSES no longer recommends any new computation frequencies. No Energization Defined: No energization was defined in the HIFREQ template file. which can become somewhat difficult to manage.No Energizations in HIFREQ Template File Description A file imported as a HIFREQ template file does not contain any ENERGIZATION (BUSS) commands.   Stop processing only after the current processing cycle has completed: The processing stops only after the end of the current processing cycle. and permeability of the layer should be specified for at least two frequencies in the table. No Conductors Defined: No conductors were defined in the HIFREQ template file. Use only the HIFREQ Computation Database Files that were computed in this scenario: When this option is used. The following time has elapsed: Specifies the maximum amount of time (in hours) that the processing should run. This option should be used when the processing fails to restart when using one of the other options. This normally happens as a result of selecting the wrong file when browsing for a template file. The Project Properties Dialog The Project Properties Dialog allows you to view or edit some basic properties of a project and of its scenarios.. Also. Uniform (two regions with homogeneous characteristics .. Layer Data: Regroups the data defining a single layer of the soil model. Check this option to specify the characteristics as a function of frequency. it becomes possible to modify many network parameters as a function of frequency. Make sure to browse to a valid FFTSES F05 file generated by Input Toolbox. When this option is not selected. To avoid this problem. The settings defined in this case apply only to the active scenario. In the current version.Invalid FFTSES Template File Description A file imported as a FFTSES template file was not recognized as a valid SICL command file for FFTSES. Restricted Frequency Mode. in per-unit.separated by two horizontal planes. Stop processing immediately: The processing stops immediately. You can choose to make any layer(s) frequency-dependent and leave the others frequency-independent. Nothing Selected to Build Database: Nothing was selected in the FFTSES template file to build the FFTSES Input Databases from the HIFREQ Computation Databases.   Run all recommended frequencies: When this option is selected. Permeability: Defines the permeability of the layer relative to the permeability of the vacuum. Multiple Energizations: Multiple energizations were defined in the HIFREQ template file. Note When specifying a frequency-dependent soil model or when specifying a script file for the HIFREQ template file. you can view the characteristics of the soil model defined in the file. that some of the more advanced features of AutoTransient (Data Sharing. the program automatically runs only one frequency at a time.. This normally happens as a result of selecting the wrong type of file when browsing for a template file. Note that you are warned in Input Toolbox when trying to save a HIFREQ file that doesn't contain any conductors. 2. Invalid FFTSES Template File: The file that was specified as a FFTSES template is not recognized as a valid FFTSES input file.        Layer: Selects the layer whose properties are to be viewed or edited. The program cannot process a scenario until a HIFREQ template file containing some conductors is specified. The processing will stop at the end of the first complete cycle after the specified time has elapsed. This means that the HIFREQ command is not found in the file at all. The Stop Processing Options Dialog The Stop Processing Options Dialog is automatically invoked by the program when you stop a run before its normal completion conditions have been reached. Delete all output files produced in the last processing cycle: Use this option to delete all output files that were produced in the interrupted cycle. Run the Forward FFTSES operation: Instructs the program to run the Forward FFTSES operation. This normally happens as a result of selecting the wrong file when browsing for a template file. If the run must be interrupted. Repairable? No. and results in well-defined. Terminate processing when at least one of the following conditions are met: Regroups the settings that control the conditions under which the processing of a scenario is considered complete.Energization Not Set to 1 in HIFREQ Template File for more details on the restrictions regarding energization in AutoTransient.. No Energized Conductors Defined: No energized conductors were defined in the HIFREQ template file. This corresponds to the way a "manual" transient analysis with HIFREQ and FFTSES is normally done. In many practical cases. Make sure to browse to a valid HIFREQ F05 file generated by one of the dedicated SES editor programs (Input Toolbox or SESCAD). to each of the scenarios. You can modify those settings in order to meet other requirements. This option should be used when the data affecting the Forward FFT operation in the FFTSES template file was modified since the scenario processing was stopped. either Infinite (an infinite medium with homogeneous characteristics). regardless of the state of the computations. The following options are available. Permittivity: Defines the permittivity of the layer relative to the permittivity of the vacuum. permittivity and permeability of selected layers of the soil model used in HIFREQ. and also the conditions under which the analysis is considered to be complete. this is always selected. Repairable? No. and can "repair" the problem in some cases. These extra constraints are necessary to guarantee a successful transient study. They can be overridden for the active scenario using Project | Edit Scenario Processing Options.F8*) from scratch. Run a maximum number of frequencies at a time: When this option is selected.Multiple Energizations in HIFREQ Template File and Diagnostics . Insufficient Accuracy: The computation accuracy in the HIFREQ template file is insufficient for a Transient study. The following lists show the various problems that are detected by AutoTransient. Repairable? No. in Ohm-m. This gives the program the time to properly complete all operations. specifies the frequency at which one set of resistivity. this option is not selected. or Two Layer (three regions with homogeneous characteristics . AutoTransient detects and reports whenever those constraints are not satisfied. the program uses the information contained in the History file to restart the processing in an identical state as when it was last stopped. These comments are transmitted to the HIFREQ and FFTSES input files. or it is found too late (after too many unrecognized commands). The program cannot process a scenario until a valid FFTSES template file is specified. HIFREQ Database Files: Regroups the options that control which HIFREQ computation database files from the History folder are to be used when restarting. Top and Bottom . This mode can be useful to import into the Active Scenario some HIFREQ F21 files that were generated in a different scenario or outside AutoTransient altogether. This helps prevent the data corruption that can occur when the option Stop processing immediately is selected.. Make sure to browse to a valid HIFREQ F05 file generated by one of the dedicated SES editor programs (Input Toolbox or SESCAD). . The following number of processing cycles was carried out: Specifies the maximum number of iteration cycles that should be carried out. in meters or feet. Run Frequency Determination: Determines how the computation frequencies recommended by FFTSES are distributed amongst HIFREQ runs in each iteration cycle. the processing is automatically set to run a single frequency at a time. Remarks The frequencies can be specified in any order. The program initializes the options in this screen based on the contents of the History folder.separated by an infinite plane). Extract-Determine Consistency: The quantities that were requested to be extracted from the FFTSES input databases in the FFTSES template file are inconsistent with the quantities that are requested to be computed (in the HIFREQ template file). the program uses the value for the lowest specified frequency. all frequencies recommended by FFTSES in an iteration cycle are computed in a single HIFREQ run. This option is selected by default (and disabled) if those files are missing from the History folder. Remarks There are two main advantages to running a maximum number of frequencies at a time: 1. Repairable? No. and cannot be modified. The Soil Model Dialog The Soil Model Dialog (which can be invoked using Project | Edit Soil Model) can be used to specify frequency-dependent values for the resistivity. Fatal Errors        Invalid HIFREQ Template File: The file that was specified as a HIFREQ template is not recognized as a valid HIFREQ input file. file://C:\Users\aivanov\AppData\Local\Temp\~hhFD54. The initial values are chosen to minimize the run-time necessary to complete the run.. Multiple Extract: More than one quantities were requested to be extracted from the FFTSES input databases in the FFTSES template file. a value should be specified for each of the frequencies defined in the table.htm 13/02/2016 . This option is not available if the History file of the scenario cannot be found or is corrupted. This dialog can be used in two different contexts:   To define the processing options for the active scenario (Project | Edit Scenario Processing Options). It is not necessary to specify frequencies over the entire frequency range for the analysis: the program will interpolate and extrapolate frequencies as needed. Repairable Errors          HIFREQ Syntax Error: Syntax errors were found in the HIFREQ template file. the resistivity. this is not selected. The program cannot process a scenario until a HIFREQ template file containing at least one energization is specified. a single value can be specified for the resistivity. and can reduce computation time somewhat. Rebuild the FFTSES Input Databases: Instructs the program to rebuild the FFTSES Input Databases (FT_*. the program uses the value for the highest specified frequency. Energization Not Set to 1: The value of the energization is not 1 + j 0.. In this case. By default. and permeability is specified. Multiple Energized Conductors: Multiple energized conductors were defined in the HIFREQ template file. It allows to define whether or not the program should wait until the current processing cycle is complete before stopping the run. You can choose to use this setting even when the files are present in the History folder when you suspect that some of these files may be corrupted (perhaps because an earlier run gave an error message to that effect).

Repairable? Yes.GENERAL Section The GENERAL Section of the AutoTransient Project File stores general identification settings for the project. Make sure to specify a single energized conductor in the HIFREQ template file. meaning that all specified energizations end-up having the same shape in the time domain. FFTSES refuses to run under those circumstances. Diagnostics . as the currents are always computed. Repairable? No.TRANSIENT: An Overview Page 7 of 10 Diagnostics . in order to speed up the runs. The program can "repair" this problem by removing all energizations but the first. To avoid this problem. It is preferable to define the amplitude of the surge in FFTSES. since there is nothing to compute.. To avoid this problem.No Database Selection in FFTSES Template File Description A file imported as a FFTSES template file does not contain any selection of data to be exported from the HIFREQ database(s). GPR or Longitudinal Current) or a valid range of both Profile Numbers and Point Numbers (if the requested quantity is a field-type quantity computed at various points in space.Syntax Error in FFTSES Template File Description A file imported as a FFTSES template file contains syntax errors such as unrecognized commands. since the default accuracy settings in HIFREQ are normally adequate. To avoid this problem. Note that this error can also occur while processing a scenario if the script generates a run-time error only for some frequencies (but not for the zero frequency. This situation is unlikely to occur in practice. To avoid this problem. Repairable? Yes.. and corrected. and either a valid range of Segment Numbers (if the requested quantity belongs to the conductor segments. Nevertheless.No Energizations in HIFREQ Template File Description The quantities that were requested to be extracted from the FFTSES input databases in the FFTSES template file are inconsistent with the quantities that are requested to be computed (in the HIFREQ template file). Note that you should normally request only one quantity (profile. It is preferable to extract a single quantity (observation point or segment) at a time. the FFTSES Input Databases cannot be constructed by AutoTransient. you should let the program do this only when you are aware of the error and know that removing the command will be harmless. you can safely ignore this problem if your model requires two or more energizations that have the same time-domain shape.. Make sure to specify a single unit energization in the HIFREQ template file. The simplest way to change those settings is through the "Repair" mechanism of AutoTransient.Invalid Script Code in HIFREQ Template File Description A file imported as a HIFREQ template file contains scripting code that either does not compile. This is because of the scaling of the energization(s) carried out by the program: FFTSES rescales all energizations in the same way as a function of frequency.. Note that the results obtained in this way may not be very reliable. you can safely ignore this problem if your model requires two or more energizations that have the same time-domain shape. Note that it is normally preferable to edit the file yourself. Make sure to specify a single quantity to be extracted. Note that it is not necessary to requested any conductor currents in HIFREQ. AutoTransient Project File .No EXTRACT in FFTSES Template File Description No computation quantities are requested to be extracted from the FFTSES input databases during the inverse FFTSES operation. or segment) at a time. To avoid this problem. Make sure to request the same quantities in both programs. Repairable? No. GPR or Longitudinal Current) or a range containing a single profile and a single point (if the requested quantity is a field-type quantity computed at various points in space. To avoid this problem. When this condition is detected. especially at high frequencies. points.Insufficient Accuracy in HIFREQ Template File Description The accuracy settings in a file imported as a HIFREQ template file are insufficient for a typical transient study.. Repairable? No. This screen can be accessed by Computations -> Inverse-FFT -> Extract From Database -> Database Management. or from different ones. Repairable? Yes. Diagnostics . To avoid this problem. The program must be able to execute the script successfully before processing a scenario. It is recommended to use a single ENERGIZATION in a HIFREQ template file. Diagnostics . Make sure to specify a single energization in the HIFREQ template file. The program can repair this problem by allowing you to select the desired computation results directly from within AutoTransient. This normally happens when the imported HIFREQ template file was edited manually. This normally happens when the imported FFTSES template file was edited manually. The scripting code should be reviewed. This situation is unlikely to occur in practice. since removing all but the first energization is probably not the desired solution to this problem in most cases. Repairable? Yes and no! The program can "repair" a template file containing syntax errors by removing the commands that are in error.Multiple Energizations in HIFREQ Template File Description A file imported as a HIFREQ template file contains multiple ENERGIZATION (BUSS) commands.g. Executing this script (once the errors it contains have been removed) should generate a correct HIFREQ file.. This problem can easily occur since Input Toolbox does not validate that some data is specified.Syntax Error in HIFREQ Template File Description A file imported as a HIFREQ template file contains syntax errors such as unrecognized commands. meaning that all specified energizations end-up having the same shape in the time domain. and the location of the scenario file for each scenario. or segments to a single value. Note that it is not necessary to specify anything in the FFTSES Database Creation section of the FFTSES Database Managament screen. since removing the energization from all but the first energized conductor is probably not the desired solution to this problem in most cases.g. This is because of the scaling of the energization(s) carried out by the program: FFTSES rescales all energizations in the same way as a function of frequency. It could happen if the accuracy settings were explicitly specified to be lower than the default values. You should make sure to specify some data in the Desired Computation Results section of the FFTSES Database Managament screen in Input Toolbox.. Imaginary Part = 0) energization in HIFREQ. This can be done in the Characteristics screen in SESCAD. To avoid this problem. This should not happen very often. Diagnostics .. Repairable? Yes. Consult the topic Multiple EXTRACT Commands in FFTSES Template File for more details. This is normally due to an attempt to specify the amplitude of a surge directly in the HIFREQ file.g. As a result.Non Unit Energization Value in HIFREQ Template File Description A file imported as a HIFREQ template file contains conductors that are energized with an energization whose strength is not set to 1. It is normally named <Project Name>.. to verify that the results are correct. Make sure to browse to a HIFREQ F05 file generated by one of the dedicated SES editor programs (Input Toolbox or SESCAD).. e. Use the default accuracy settings (or better) in the HIFREQ template file. but this is normally not a good idea.. You should specify both the Entity Being Processed. Diagnostics .. and to use a unit (Real Part = 1.. This can be done in the Computations screen for the Inverse FFTSES option in Input Toolbox. This is repaired by transforming the HIFREQ template file to request all quantities that are selected to be extracted in FFTSES. This problem should normally not happen unless you explicitly decided to use the advanced "Scripting" feature of AutoTransient. To avoid this problem.No Energized Conductor in HIFREQ Template File Description A file imported as a HIFREQ template file contains at least one valid ENERGIZATION command. The program cannot process a scenario until a HIFREQ template file containing at least one energized conductor is specified. Repairable? Yes. Make sure to browse to a FFTSES F05 file generated by Input Toolbox.Multiple EXTRACT Commands in FFTSES Template File Description A file imported as a FFTSES template file contains several EXTRACT commands.g.htm 13/02/2016 . e. Make sure to specify a quantity to be extracted. The program can "repair" this problem by removing the energization code from all conductors but the first energized conductor. To avoid this problem. and by restricting the range of profiles. Note that you can choose to keep the accuracy settings defined in the file. Note that it is normally preferable to edit the file yourself. or invalid data types in a valid command.Multiple Energized Conductors in HIFREQ Template File Description A file imported as a HIFREQ template file contains multiple conductors that are energized either from the same bus. e. point.. Repairable? Yes and no! The program can "repair" a template file containing syntax errors by removing the commands that are in error. you should let the program do this only when you are aware of the error and know that removing the command will be harmless. Repairable? Yes.. Repairable? Yes. e. The program can repair this problem by replacing the energization by a unit energization. SCENARIOS Defines the number of scenarios in the project. which is used to assess whether the script is correct or not). This can make FFTSES recommend a very large number of frequencies during the inverse operation. A file containing pure script code should normally be available in the Work folder of the active scenario to help you with the debugging. Scalar Potential or Electric Fields). in the You should be careful to select a value that is selected to be computed in the HIFREQ template file. Nevertheless. The program cannot process a scenario until a FFTSES template file containing at least one EXTRACT command is specified.TNT... To avoid this problem.. Diagnostics . but it is not applied to any conductor. it is recommended to always do a "confirmation" run using higher accuracy settings. and a range containing a single segment number (if the requested quantity belongs to the conductor segments. You should specify both the Entity Being Processed.... Scalar Potential or Electric Fields). Diagnostics .. since AutoTransient automatically manages the HIFREQ computation databases... Diagnostics . Diagnostics . Diagnostics . Make sure define the Energization Code of the conductor that should be energized to 1 (or to the index of the appropriate ENERGIZATION command). The AutoTransient Project File The AutoTransient Project File stores the locations of the scenario files for the various scenarios in a project. but this is normally not a good idea. Sections Name Description GENERAL Contains general identification settings. the program offers you a choice of accuracy settings. Diagnostics . This can be done in the Computations screen for the Inverse FFTSES option in Input Toolbox. equal to the value initially specified for the start of the range.. file://C:\Users\aivanov\AppData\Local\Temp\~hhFD54. or generates run-time errors. To avoid this problem. and can unnecessarily lengthen the run-time. and in the System screen's Conductor data grid in Input Toolbox. or invalid data types in a valid command. It is recommended to use a single energized conductor in a HIFREQ template file.. When using lower accuracy. The program "repairs" the problem by eliminating all EXTRACT requests but the first.

TEMPLATEDATA Section The TEMPLATEDATA Section of the AutoTransient Scenario File stores data extracted from the FFTSES/HIFREQ template files. Distances are expressed in meters. and cannot be modified in the program's user interface. This value must be 'TNT . AutoTransient Scenario File . Sub-Sections Name Description Cycle Contains data controlling the processing of the scenario. This should be an integer between 1 and Count. the only supported value is 1. When specified.DESCRIPTION Section The DESCRIPTION Section of the AutoTransient Scenario File contains text descriptions of various aspects of the scenario. Settings Name Soil Type Description Integer value defining the type of the soil model. then the string must be placed inside quotes. AutoTransient Scenario File . it should be the name of a scenario that is part of the project containing this scenario (excluding this scenario). relative to the folder containing the scenario file for this scenario. Three values are allowed:    0: Infinite. If the specified name doesn't satisfy this condition. The soil model consists of a single region of uniform electrical properties filling the entire space. 3: MetricCM. AutoTransient Scenario File . The HIFREQ Template file and computation database files (*. Description Description of the project. if not specified. Currently. and radii in centimeters. The layer that is defined for a given value of N depends on the value of the SoilType setting:    N = 0 Defines the infinite medium for the Infinite soil model.GENERAL Section The GENERAL Section of the AutoTransient Scenario File stores general identification settings for the scenario. SOIL Contains information about the initial soil data found in the HIFREQ template file and/or the user-defined frequency-dependent soil model. FileManagement Defines which output files should be kept during the processing of the scenario. 2: HIFREQ. separated at Z = 0. Remarks All descriptions can extend over several lines. or that is to replace data from those templates. 1. Here. AutoTransient Scenario File .htm 13/02/2016 . then the string must be placed inside quotes. AutoTransient Scenario File . N=1. Active Index of the active scenario of the project. relative to the folder containing the scenario file. This must be valid as a component of a filename. Four values are allowed:  Units    2: Metric. This is used only when the Customized setting is True. Sections Name Description GENERAL Contains general identification settings. Settings Name Description IsHIFREQScript Boolean value (T = True. Settings Name Description Customized Boolean value (T = True. AutoTransient Project File . This value must be 'TNT . Scenario Description of the scenario. the extra scenarios are not loaded. AutoTransient Scenario File . N = 2 Defines the bottom layer for a two-Layer soil model. file://C:\Users\aivanov\AppData\Local\Temp\~hhFD54. non-default values. the folder containing the files required to restart this scenario). This is read from the HIFREQ template file. 1: FFTSES.. relative to the folder containing the scenario file for this scenario. the top layer and the bottom layer. History Path of the History folder (i.) Project Description of the project containing this scenario.. Filename Fully qualified filename of the scenario file (i. FFTSESRelative Filename of the FFTSES template file. Settings Name Description SharedScenario Name of the scenario with which this scenario shares data. as this value is recalculated every time the scenario file is loaded.TEMPLATEDATA\GENERAL Section The GENERAL sub-section of the TEMPLATEDATA section of the AutoTransient Scenario File contains general settings extracted from the template files. The AutoTransient Scenario File The AutoTransient Scenario File stores all the settings necessary to run an AutoTransient scenario. The default value is False. 2) Description SOIL LAYER-type section containing the data for a single layer of the soil model. relative to the folder containing the scenario file for this scenario.SCENARIOS Section The SCENARIOS Section of the AutoTransient Project File stores information regarding the scenarios of the project. In this case. HIFREQ Description of the HIFREQ template file used in the scenario. Currently. This must be an integer greater than zero. relative to the folder containing the scenario file for this scenario. Integer value defining the system of units used when reading/writing the scenario file. FFTSES Description of the FFTSES template file used in the scenario. CUSTOM SOIL MODEL-type section containing the user-defined. If this character string includes quotes or extends over several lines. relative to the Templates folder. anything else = False) controlling whether the Custom Soil (True) or the Initial Soil (False) should be used when processing the scenario. the folder containing temporary run files while processing this scenario). (Only the first 20 characters of this value are used.Count.e. ScenarioN Path name of the scenario file for scenario N.DATA Section The DATA Section of the AutoTransient Scenario File stores the user-defined data for the scenario. Both distances and radii are expressed in meters.SOIL Section The SOIL sub-section of the TEMPLATEDATA section of the AutoTransient Scenario File contains information about the initial soil data found in the HIFREQ template file and/or the user-defined frequency-dependent soil model. This is used for cross-checks only. Settings Name Description Count Number of scenarios in the project. while the top layer has a finite thickness. the scenario doesn't share any data. This must be valid as a component of a filename. or the air layer for a Uniform or a two-Layer soil model. Settings Name Description ID Uniquely identifies an AutoTransient Scenario File. TEMPLATEDATA Stores data extracted from the FFTSES/HIFREQ template files. the air layer. frequency-dependent soil model. any quotes (") in the string must be replaced by double-quotes (""). as this data is re-read from the HIFREQ template file every time the scenario is loaded. anything else = False) recording whether or not the HIFREQ file contains scripting code. This is used to identify plots. relative to the folder containing the project file. AutoTransient Scenario File . Settings Name Description RunID Defines the RunID for the scenario. HIFREQOriginal Fully qualified filename of the last HIFREQ file that was imported in the scenario. reports and output files produced by the program. AutoTransient Scenario File . This is the default. relative to the Templates folder.Scenario'. 4: British.Project'. If this is empty. DESCRIPTION Contains a detailed description of the scenario. the folder containing the template files). The FFTSES Template file is shared. any quotes (") in the string must be replaced by double-quotes (""). If any description string includes quotes or extends over several lines. or that is to replace data from those templates. FFTSESOriginal Fully qualified filename of the last FFTSES file that was imported in the scenario. Sub-Sections Name Description GENERAL General settings extracted from the template files.FILES Section The FILES Section of the AutoTransient Scenario File stores the locations of the important files that are part of the scenario. Results Path of the Results folder (i. Version Integer value identifying the version of the file format used when writing the file. the data sharing is not operational. Name Alphanumeric string identifying the name of the project.e. This is used for cross-checking purposes only. Both distances and radii are expressed in feet..    Remarks For the data sharing to be in effect. SHARING Stores information related to data sharing between this scenario and other scenarios of the same project. Integer value defining the type of data sharing between this scenario and the scenario identified by SharedScenario. The air and the bottom layer are of infinite thickness.e. 2: Two-Layer. This is automatically set to the name of the scenario. and radii in inches. 5: Inch-Radius.e.e. the folder containing the result files obtained by processing this scenario).SOIL MODEL Section Type The SOIL MODEL type of section stores information about a frequency-dependent or frequency independent soil model. The soil model consists of two semi-infinite regions of different uniform electrical properties (typically the air and the earth). Sub-Sections Name LAYERN (N = 0. the only supported value is 1. FILES Defines the important files that are part of the scenario. 1: Uniform. Remarks If there are more scenario file paths specified than are indicated by Count. In this case.F21) are shared. Version Integer value identifying the version of the file format used when writing the file.. The soil model consists of three horizontal regions of different uniform electrical properties. Soil Description of the soil model used in the scenario. Name Alphanumeric string identifying the name of the scenario.TRANSIENT: An Overview Page 8 of 10 Settings Name Description ID Uniquely identifies an AutoTransient Project File. Sub-Sections Name Description INITIAL SOIL MODEL-type section containing the data initially read from the HIFREQ template file. No data is shared. Three values are allowed: SharingMode 0: None.SHARING Section The SHARING Section of the AutoTransient Scenario File stores information related to data sharing between the scenario and other scenarios of the same project. Distances are expressed in feet. HIFREQRelative Filename of the HIFREQ template file. Work Path of the Work folder (i. AutoTransient Scenario File . both the SharedScenario and the SharingMode must be set to correct. Templates Path of the Templates folder (i. DATA Root section for the user-specified data of the scenario. N = 1 Defines the earth layer for a Uniform soil model. this file). or the top layer for a two-Layer soil model. Settings Name Description ParentProject Filename of the project file of the AutoTransient project containing this scenario.

 4: After Extract. at several frequencies. Here. When set to True. MaximumRunTime Positive real number defining the maximum amount of time (in hours) that the processing of the scenario is allowed to take. two values are supported: 1: Original file format. 3: None. A HIFREQ run was just completed and the computation results from the HIFREQ computation database were added to the FFTSES input database. KeepMode14 The HIFREQ Plot files (F22-F23). Keep the files produced in all runs. the values at the smallest specified frequency are used if the computation frequency is smaller than all specified frequencies. the computation results from the HIFREQ computation database were not added to the FFTSES input database. The default is to keep all files of this type. The AutoTransient History File The AutoTransient History File stores information that helps to restart the processing of a scenario. The set of recommended frequencies at every cycle of iteration is split among several HIFREQ runs. If a computation frequency is outside the range for which the electrical properties are defined. See the File Information Format topic for details about the value of these settings. The processing hasn't started yet. Currently. This is always used when writing the file. The default for this file is to keep the first file only. this is ignored.  3: After HIFREQ. the MaximumRunTime setting defines the maximum amount of time that the processing is allowed to run. The default is to keep none of those files. Four values are allowed:  KeepModeN (N = 1:17)    0: Last.STEP Section file://C:\Users\aivanov\AppData\Local\Temp\~hhFD54. NumberOfFrequencies Maximum number of frequencies that can be specified in a HIFREQ run. The default is 3. and is always True TerminationNumberOfCycles Boolean value (T = True. this is set to 1. Resistivity Non-negative real value defining the resistivity (in Ohm-m) of the medium at the specified Frequency. Sections Name Description GENERAL Contains general identification settings. for the case that the data is frequency-independent. N = 1:Count. The default is 48 hours. The default value is False. Sub-Sections Name Description FrequencyIndependent ELECTRICAL MEDIUM-type section containing the data for a layer. this is set to 1. KeepMode9 The Forward FFTSES Output file (F09). Permittivity Non-negative real value defining the relative permittivity (with respect to the permittivity of the vacuum) of the medium at the specified Frequency.htm 13/02/2016 . anything else = False) controlling whether or not to stop the processing after a specified number of complete iteration cycles. permittivity. This is used only when the TerminationRunTime setting is set to True. AutoTransient History File . The default value is 0. State  2: In HIFREQ. The default for this file is to keep the last file only. Do not keep any files of this type. KeepMode7 The Forward FFTSES Recommended Frequencies (F27) file.) as a separator for the FILES setting. The default is to keep all files of this type. anything else = False) controlling whether or not to stop the processing once specified accuracy has been reached. KeepMode1 The Inverse FFTSES Computation Database (F21) file. NumberOfCycles Positive integer defining the maximum number of iteration cycles to carry out during the processing of the scenario.0MHz and 1. Two values are allowed: FrequencyMode 0: Regular.his". TerminationCovergence Boolean value (T = True.01. The default for this file is to keep the first file only. FrequencyDependent ELECTRICAL MEDIUM COLLECTION-type section containing the data for a layer at several frequencies. at a single frequency. (This is the normal end-point of a complete iteration cycle). FILES Stores information about various files that are important to the processing history. 1: First.CYCLE Section The CYCLE sub-section of the DATA section of the AutoTransient Scenario File contains data controlling the processing of the scenario. The default is to keep the last of those files. AutoTransient Scenario File . This is used when the FrequencyMode is set to 1. Integer value identifying the state of the processing when it was interrupted. KeepMode2 The Forward FFTSES Computation Database (F21) file. Settings Name Description FFTTemplate Contains data about the FFTSES template file used in the processing. KeepMode12 The HIFREQ Current Recovery (F33) file. F84 Contains data about the FFTSES Configuration Input Database file used in the processing. The default value is False. KeepMode5 The FFTSES Animation (F85) file. KeepMode15 The HIFREQ Conductor Segment Information (F17) file. KeepMode4 The FFTSES Input Databases (F81-F84) files. This was replaced by a pipe (|) in the current version (since a semi-colon can be used legally in a filename. this setting would show: '1000000|1200000'. AutoTransient Scenario File . The frequency values need not be ordered. the program stops when there are no more STEPS to read. F83 Contains data about the FFTSES Magnetic Field Input Database file used in the processing. AutoTransient Scenario File . The default value varies with the file type. The default for this file is to keep the last file only. KeepMode10 The HIFREQ Input file. The default for this file is to keep the last file only. A HIFREQ run was just completed. This version differs from the current one by using a semi-colon (. The default is to keep all files of this type. but have not been processed yet. for the case that the data is frequency-dependent. KeepMode8 The Inverse FFTSES Output file (F09). RecommendedFrequencies Lists the recommended frequencies that have not yet been processed in the current processing cycle. An Inverse FFTSES run was just completed. Size Positive real number defining the size (height) of the layer. Only the Forward FFTSES operation was completed. This is ignored if the properties of the medium are frequency-independent. The default for this file is to keep the last file only. It is normally named "hs_<Scenario Name>. File Types KeepMode Value Description KeepMode0 The FFTSES Input file. This is used only for the top layer of a two-layer soil model. If not specified. so that each HIFREQ run contains at most a specified maximum number of frequencies. Sub-Sections Name Description FrequencyN ELECTRICAL MEDIUM-type section containing the electrical properties for a medium. TerminationRunTime Boolean value (T = True. Remarks The information stored in this section is used to detect modifications to those files by external programs. used in the Beta version of the program. Integer value identifying the version of the file format used when writing the file. A single HIFREQ run containing all frequencies recommended by FFTSES is carried out in each cycle of the iteration. (Note that all such files are kept as part of the processing history). 1: Restricted. seven values are allowed:  0: Undefined.TERMINATION Section The TERMINATION sub-section of the CYCLE section of the AutoTransient Scenario File contains data that determine the circumstances under which the processing should terminate. The default for this file is to keep the last file only. the NumberOfCycles setting defines the maximum number of cycles to carry out. AutoTransient Scenario File .History'.  6: Complete. AutoTransient Scenario File .FILEMANAGEMENT Section The FILEMANAGEMENT sub-section of the DATA section of the AutoTransient Scenario File contains data that defines which output files should be kept during the processing of the scenario. KeepMode11 The HIFREQ Computation Database (F21) file.SOIL LAYER Section Type The SOIL LAYER type of section stores information about a single frequency-dependent or frequency independent layer (or region) of a soil model. F81 Contains data about the FFTSES Scalar Potential Input Database file used in the processing. Settings Name Description Integer value defining which files to keep for file type N. This is the default value. Here. Settings Name Description Frequency Non-negative real value defining the frequency (in Hz) for which the electrical properties of the medium are defined.SOIL ELECTRICAL MEDIUM COLLECTION Section Type The SOIL ELECTRICAL MEDIUM COLLECTION type of section stores information about the electrical properties of a single layer (or region) of a soil model. In this case. or else the processing state is unknown (perhaps due to an error). The default for these files is to keep the last file only. F07 Contains data about the FFTSES Spectrum scaling file used in the processing. Keep only the file produced in the first run. KeepMode3 The FFTSES Spectrum Scaling (F07) file. Currently.2MHz were recommended by FFTSES. anything else = False) controlling whether or not to stop the processing after a specified amount of time has elapsed. F80 Contains data about the FFTSES Computation Control Database file used in the processing.  5: After Inverse. ConvergenceAccuracy Positive real number that defines the desired target accuracy (in per unit) when TerminationConvergence is set to True. A HIFREQ run was underway. this setting is ignored and is always set to False. This is a series of pipe-separated non-negative real values. at a single frequency. Remarks The program interpolates the resistivity. Settings Name Description IsFrequencyDependent Boolean value (T = True. anything else = False) defining whether or not the processing should stop when the program runs out of recommended frequencies. and permeability values linearly between the specified values. this setting is ignored. The default for this file is to keep the first file only. and the values specified at the largest frequency are used if the computation frequency is larger than all specified frequencies. STEPS\N Contains information about each iteration (step) of the process. When reading the file. F82 Contains data about the FFTSES Electric Field Input Database file used in the processing. in which case the default value is 1. Settings Name Description Integer value that defines how the computation frequencies are distributed among the HIFREQ runs. Keep only the file produced in the last run. 1: After Forward. The default is to keep none of those files.SOIL ELECTRICAL MEDIUM Section Type The SOIL ELECTRICAL MEDIUM type of section stores information about the electrical properties of a single layer (or region) of a soil model.)  2: Current file format. if the frequencies 1. N should run from 1 to the actual number of steps completed. everything else = False) that determines whether the electrical properties of the layer are frequency-dependent or not. and to estimate the progress of the iterative process. Settings Name Description Count Non-negative integer defining the number of frequencies for which the electrical properties of the medium are defined. KeepMode16 The Forward FFTSES Plot Files.TRANSIENT: An Overview Page 9 of 10 AutoTransient Scenario File . KeepMode6 The Inverse FFTSES Recommended Frequencies (F27) file. The processing was completed. or the moment a gap is encountered in the sequence AutoTransient History File . KeepMode17 The Inverse FFTSES Plot Files. Settings Name Description TerminationRecommendedFrequency Boolean value (T = True. Currently. Permeability Non-negative real value defining the relative permeability (with respect to the permeability of the vacuum) of the medium at the specified Frequency. If not specified. This is used only when the TerminationNumberOfCycles setting is set to True. The default for this file is to keep the first file only. Currently. For example. The default value is False. This value must be 'TNT . HIFREQTemplate Contains data about the HIFREQ template file used in the processing. The default is to keep the first of those files. 2: All. This is specified in the units of distance defined in the GENERAL section of the TEMPLATEDATA. Settings Name ID Version Description Uniquely identifies an AutoTransient History File. When set to True.   Sub-Sections Name Description TERMINATION Defines the conditions that determine the circumstances under which the processing should terminate. The default for this file is to keep the last file only.FILES Section The FILES Section of the AutoTransient History File stores information about various files that are important to the processing history. the NumberOfFrequencies setting defines the maximum number of frequencies for each run.GENERAL Section The GENERAL Section of the AutoTransient History File stores general identification settings for the file.   AutoTransient History File . KeepMode13 The HIFREQ Output file (F09). Currently.

separated by pipe (|) symbols. This is the default setting.Recent Files Several folders of the AutoTransient registry settings store information about recently used files.Top Level Folders Name Description Options Contains default settings for the program. This is ignored if ShowDetails is False. Error Error messages. The last number of this setting represents the fraction of the screen height devoted to the Program Output section.MESSAGES Folder The MESSAGES folder in the AutoTransient registry settings contains preferences for the Messages section of the main screen. The default is False.. This setting is True by default for all but the 'Trace' message type. MessagesVisible Boolean value (T = True. The default value is 'Date and Time'. This is used for internal cross-checks only. This is not used currently.  1: Descending. DetailsFraction Positive real number specifying the height of the Details portion of the Messages section of the main screen. StartTime EndTime Date and Time at which the processing of the step ended. The default value is True. Note that. AutoTransient Registry Settings . everything else = False) recording whether the Messages section of the main screen is visible. AutoTransient History File . This structure is similar to that used in the AutoTransient Project and Scenario files) The AutoTransient settings can be found at "HKEY_CURRENT_USER\Software\VB and VBA program Settings\AutoTransient".Settings Folder The Settings folder of the AutoTransient registry settings stores configuration information for the Open Project window.exe utility that ships with Windows. The default is True. and False for the InfoSelected other columns. This is identical in structure to the DATA section of a Transient Scenario file. etc. these settings have the following structure. ProcessOnImport Boolean value (T = True. Fields Field Description Filename Filename of the file.   Message Types The following types of messages can be displayed.File Information Setting The File Information setting of the AutoTransient History File stores information about a file. Once the maximum number is reached. depending on your Windows configuration. They should add-up to 1. TimeStamp Date and time at which the message was generated. this setting would show: '1000000|1200000'. SelectConfiguration Window configuration of the Activate Scenario and Delete Scenarios screens. These values are in one-to-one correspondence with the message information items described in the Message Information Items section. OpenProjectWidth Non-negative real number defining the width (in Twips) of the Open Project screen. Sub-Folders Name Description FFTTemplates Recent file list containing the fully qualified paths of the most recent files imported as FFTSES templates. Integer value controlling the sort direction of the messages in the list. Message Information Items The following types of information items are available when displaying messages. TypeSelected Pipe (|) separated list containing six Boolean values (T = True. The values for the columns that are not selected (as per ColumnWidth the InfoSelected setting) are ignored. HelpFile Fully qualified path of the help file containing the help topic associated with the message (if any). Settings Key Description LastPath Identifies the last folder path in which a project was open or created. IsFinished Boolean value (T = True. file://C:\Users\aivanov\AppData\Local\Temp\~hhFD54. The messages are not sorted. Message Type Description Information General information messages. Currently. Frequencies Lists the frequencies that were processed in the step. Information Item Description Code Integer code identifying the message. These values are in one-to-one correspondence with the types of messages described in the Message Types section. 2000. and the default setting defined in the Options menu. Sub-Folders Name Description MESSAGES Contains preferences for the Messages section of the main screen. MessageType Type of the message.. The allowed values are: SortDirection -1: None. AutoTransient . AutoTransient Registry Settings . HelpID Integer defining a help topic containing more detailed information about the message. Description The body of the message. Warning Warning messages. for example the RegEdit. everything else = False) controlling whether the Details portion of the Messages section of the main screen is visible or not. everything else = False) recording whether the option to "Start processing as soon as the Import operation completes" is selected in the Import Templates screen. PropertiesConfiguration Window configuration of the Properties screen. ShowDetails Boolean value (T = True. Remarks The most recent file in the list is associated to the setting N = 0. In all cases. The data consists of 3 fields.TRANSIENT: An Overview Page 10 of 10 The STEP Section of the AutoTransient History File contains information about a specific iteration step of the process. Settings Key Description Pipe (|) separated list containing seven positive real numbers. MM Two-digit abbreviation of the month (1-12). HashCode Hashed value of the contents of the file. While it is not recommended to do so. the second is associated to the setting N = 1. . AutoTransient Registry Settings . These numbers define the width of the columns in the message list. The messages are sorted in ascending order. MainConfiguration Window configuration of the main screen of the program. Settings Name Description RunNumber Positive integer identifying the run number.. This is a series of pipe-separated non-negative real values.PATHS Folder The PATHS folder in the AutoTransient registry settings stores information about recently used paths and files. and defines the default values to use for this data when not explicitly specified in a scenario. SortedColumn Non-negative integer identifying the column that is sorted in the message list. as a fraction of the total width of the list. the earlier messages are removed from memory as newer messages are generated. OpenProjectHeight Non-negative real number defining the height (in Twips) of the Open Project screen. Settings Key Description Errors This setting is used for internal consistency checks only. Recent Projects Recent file list containing the fully qualified paths of the recently open or created project files. These values are in one-to-one correspondence with the message information items described in the Message Information Items. This setting is True by default for the 'Message Type' and 'Message' columns. The settings are stored in a Key . HIFREQDatabase File Information about the HIFREQ computation database file (F21) for the step. PATHS Contains recently used paths and filenames. The default value is 100. 1. AutoTransient Registry Settings . everything else = False) recording whether the corresponding column is visible in the message list.Options Folder The Options folder in the AutoTransient registry settings stores most of the AutoTransient options. This should be reported to SES. Internal Check Failure Reports the failure of an internal consistency check. it can be modified only for the 'Date and Time' and 'Message Code' columns. Date and Time at which the processing of the step started. This can be useful for troubleshooting. PROCESSING Stores default settings controlling the processing of a scenario. everything else = False) recording whether the corresponding type of message should be displayed. in the registry terminology). The messages are sorted in descending order.. The last number in the setting represents the fraction of the width of the screen occupied by the tree. See the Date Format topic for details on the format used for dates.0MHz and 1. if the frequencies 1. Registry Settings . Settings Stores configuration settings for the Open Project window. OpenProjectFolderBrowseWidth Non-negative real number defining the width (in Twips) of the Browse for Folder window used in the Open Project screen. AutoTransient Registry Settings .Date Format The following format is used for dates in Transient files: #YYYY-MM-DD HH:mm:SS# YYYY Four-digit value of the year. relative to the History folder. Trace Provides information on the internal state of the program. This can be useful for troubleshooting. 6:32:00 AM is: #2000-01-01 06:32:00#. Pipe (|) separated list containing seven Boolean values (T = True. Source Identifies the source of the message in the code.) Filename of the Nth recent file.2MHz were processed. anything else = False) indicating whether the processing of the step is complete. it is possible to edit these registry settings with the help of standard registry editors. as defined mainly in the Options menu. this may require administrator or power-user privileges. as a fraction of the height of the Messages section. HIFREQTemplates Recent file list containing the fully qualified paths of the most recent files imported as HIFREQ templates. Settings Key Description N (N = 0. Progress Special information message announcing progress on some operation. MaxMessages Positive integer specifying the maximum number of messages that can be displayed simultaneously. The AutoTransient Registry Settings AutoTransient stores some global settings in the Windows Registry. The last number in the setting represents the fraction of the width of the screen occupied by the list.htm 13/02/2016 . 0: Ascending. This includes the size of most of the program's windows. Settings Key Description OpenProjectFolderBrowseHeight Non-negative real number defining the height (in Twips) of the Browse for Folder window used in the Open Project screen. ModificationDate Last modification date of the file as recorded by the program.Value format in nested folders of the registry (hives. For example. and the remaining ones are normalized to 1. DD Day of the month (1-31) HH Hour of the day (0-23) mm Number of minutes elapsed in the hour (0-59) SS Number of seconds elapsed in the current minute (0-59) Example The date format for January 1. This value is ignored if the SortDirection is set to 'None'.