Manager and Automation Workflows

Application Version Manager: How to use the Application Version Manager

The new Application Version Manager in Sesam 2011 keeps track of installed installed Sesam programs. It detects and sets the latest version to default.

The user can set other versions to default if the Auto update is disabled. To do this, simply disable Auto update, then select the version to be default and click Set as default.

If Auto update is enabled again, the manual overrides are lost.

GeniE and HydroD use the AVM to find applications being started from these programs. If both 32 and 64 bit versions of an application are installed, the 64 bit version is preferred.

For Sesam Explorer, the list of applications is created at the time of installing Sesam Explorer.

On Windows 7, if new application versions are installed later, Sesam Explorer should be reinstalled (repair) to update the list of applications, or the configuration file <SesamExplorerInstallationFolder>\config\Sesam.config can be updated manually.

On Windows XP and Vista the list of applications in <SesamExplorerInstallationFolder>\config\Sesam.config must be updated manually. An updated template is found in the \Utilities folder under the root folder of the DVD, named Sesam32.config for the 32bit platform and Sesam64.config for the 64 bit platform.

The file must be copied into <SesamExplorerInstallationFolder>\config? and renamed to Sesam.config. This will probably require administrative privileges on your computer.

Back to top

Manager: How to install Manager for use with Sesam 2011 installation

From the Sesam 2011 Installation guide, chapter 5.2 Sesam Manager configuration:

Furthermore, replacing the Sesam.ini with the AVM means that it is no longer possible to use the Sesam Manager on Win 7 without special provisions. If using the Sesam Manager from the Sesam 2008 DVD release, you must edit the application paths to the individual Sesam applications to apply the versions from the Sesam 2011 DVD Release.

This is done by using menu Options | Programs | Executable... where you may set paths to individual applications. This must be done before creating/opening a project, and the settings will then be applied to all new projects. Old projects must be updated one by one as explained below. Note that the old Sesam Manager is not delivered on this DVD.

From 2011 the Sesam executable files are stored in separate folders while Manager is based on having all files in one Sesam\bin folder. Hence you need to tell Manager where to find the .exe-files. Manager uses two files, Manager.dat and "Project".jnl where the program executable for each program can be set. These files control where Manager can find the program executables. Managers use of the two files are explained in the user manual section 4.2.

The attached zip file includes the set_EXE.JNL file, which is a sample Manager journal file to set program executables. Either run the file interactively in Manager or add the command to run it in the beginning of another journal file, e.g.: @set_EXE.JNL

The file must be run each time a new project is started in Manager. Once the project has been saved, the updated settings are remembered.

You will need to eXtract the SACWD32.dll, DFROM.dll and Manager.exe files, which are included in the file, to these (default) locations:

C:\Program Files (x86)\DNVS\Sesam\bin\SACWD32.dll

C:\Program Files (x86)\DNVS\Sesam\bin\DFORM.dll C:\Program Files (x86)\DNVS\Sesam\bin\Manager.exe

The also includes the Manager User Manual and the installation files. Please see the attached document.

Back to top

Running GeniE through command prompt

The following command below works for starting and exiting GeniE through command prompt.

C:\Program Files\DNVS\GeniE\ Program\GeniEr top2 /new /com=input.js /exit

Please also see GeniE User manual Vol 1 chapter 4.1 for more details and pictorial representation.

Back to top

Send a command to the operating system from a Sesam journal file (DOS Windows)

For classic Sesam you may send a command to the operating system ( DOS Windows) from a Sesam journal file by typing a ! before the command. E.g. ! copy FileA FileB ! C:"Program Files"\DNVS\Sesam\Bin\Installjac.exe Remenber to quote blanks in DOS. E.g. "Program Files" Can be used in Manager to start a non supported program

Back to top

Sesam Manager (6.2-01): Shortcuts

The following keyboard shortcuts exist in Sesam Manager:

F5 - Run job
Ctrl + F5 - Run selected activity
Ctrl + N - New job
Ctrl + 1 - New GeniE job
Ctrl + 2 - New DeepC job
Ctrl + 3 - New HydroD job
Ctrl + O - Open job 
Ctrl + Shift + O - Open list of existing jobs
Ctrl + S - Save current job
Ctrl + Shift + S - Save all jobs
Ctrl + J - Import JS
Ctrl + M - Import XML
Ctrl + P - Import ZIP
Ctrl + L - Import JNL
Ctrl + Shift + J - Export JS
Ctrl + Shift + M - Export XML
Ctrl + Shift + P - Export ZIP
View:
Ctrl + R - Reset Layout
F11 - Full window
Tools:
Alt + A - Start Application Version Manager
Alt + S - Sync Application Version Manager
Alt + L - Translate JNL
Ctrl + T - Save activity as template

Back to top

Sesam Manager (6.2-03): "System.Xml root element is missing" error when starting Sesam Manager

The following error may occur when starting Sesam Manager:

Application information
Product: Sesam Manager
Version: 6.2.3.0
Location: C:\Program Files (x86)\DNVS\Sesam Manager V6.2-03\Bin\DNVS.Sesam.Manager.Win.exe

System information
OS version: Microsoft Windows NT 6.1.7601 Service Pack 1
Processor count: 8
Working set: 33320960
Is 64-bit process: False
Is 64-bit operating system: True
Has shutdown started: False
CurrentDirectory: C:\Program Files (x86)\DNVS\Sesam Manager V6.2-03\Bin
 
Exception information
Source: Autofac
Message: An exception was thrown while invoking the constructor 'Void .ctor(DNVS.Sesam.Manager.Model.IApplicationPreferences, DNVS.Sesam.Manager.Common.IEventAggregator)' on type 'OptionsService'.
followed by a stack trace and then:
Source: System.Xml
Message: Root element is missing.
This error indicates that one of the xml files used by Sesam Manager has been corrupted.
The file in question is %appdata%\DNVS\SesamManager\DNVS_SesamManager.xml
If the DNVS_SesamManager.xml file is empty, please delete it and restart Sesam Manager.
If the xml is not empty, you may either 
1. Delete the file, but this will also remove your customized settings and recent job history.
2. Send us the file, and we can investigate further.

Back to top

Sesam Manager (All Versions): Program crash when opening

On January 2018, Microsoft has released some Windows updates which have been know to cause crash on Sesam Manager and several software from different companies. These updates were later removed from the update history and replaced by fixed versions so users performing updates now should not experience any issue. To fix this, the broken versions must be uninstalled and replaced by the fixed versions.

Further information on the problematic versions of Windows Updates can be found on the links below:

There are several suggestions for fixing the issue among them: direct download of a replacement file or (probably safer) removal and re-installation of the problematic updates (uninstall KB4055532 and reinstall it; uninstall KB4055002 and install KB 4074880).

Back to top

Sesam Manager (From All to 6.1-02): Jacket 4 Leg Comprehensive example does not run

The Jacket 4 Leg comprehensive example will not run in Sesam Manager versions 6.1-02 and lower, in which the LoadFilePath and LoadFilePrefix fields are not available. The main .js file in the example has references to these fields and therefore an error occurs when running the example.

The workaround is to use a later version of Sesam Manager or to edit the file Jacket_4Leg_Comprehensive_SMinput.js and comment or delete the 4 command lines that make reference to these fields:

Sestra_static_springed_model.LoadFilePath = "_repository";
Sestra_static_springed_model.LoadFilePrefix = "Static";
...

Sestra_eigenvalue.LoadFilePath = "_repository";
Sestra_eigenvalue.LoadFilePrefix = "Eigenvalue";

Back to top

Sesam Manager: Use of Prewad and Prefem in Sesam Manager

Taking Prewad as an example to show how to start it from Sesam Manager.

The programs which are not listed in Sesam applications are started using the 'General' activity.

Properties setting:

CommandLineArguments: If you want to start a new calculation, input: /sta=new

If you want to read existing jnl file, input: /sta=new /com-file=PREWAD_in.jnl (your file name)

Name: Name of your Activity ProgramName: Give the path of your .exe file here.

Then run your job.

You may find more information about commands in the.

Notice that some of these programs, like Prefem and Preframe will be included in Sesam Manager 6.2.

Back to top

Splitting and Combining Workspaces in Sesam Wind Manager

In Sesam Wind Manager, you can run two or more workspaces at different PCs and combine them to get the report from all DLCs. However, as Sesam Wind Manager recognizes each analysis by their UniqueID, you must make sure they are consistent between workspaces. If you have not created the workspace yet, you can follow these steps:

Create and setup a new workspace with all the DLCs in one of the PCs

Save and copy the workspace into other PCs. As an example, we will run it in two workspaces, A and B. Each workspace can be in different PCs.

In each workspace, run different parts of the job. For example, first 3 DLCs in Workspace A, and remaining DLCs in Workspace B.

Observe that in both the workspace folder (File > Explore Current Workspace) you have the analysis folders (one for each DLC) .

Close workspace A Copy the analysis folders in workspace B to workspace A. In this case, we want to combine workspace B into A (A as main). You will see other DLCs are now marked as completed.

After this, generate FLS or ULS result reports as you would do it normally to get maximum utilization between all combined DLCs.

If you already finished the job without preparing the workspace as shown above (i.e., you already have different workspaces with different DLCs), you need to follow these steps to make Sesam Wind Manager recognize the UniqueIDs of the DLCs:

As an example, we have workspace A and workspace B as shown below. Both jobs are already completed separately.

Observe that in the workspace folder (File > Explore Current Workspace), in addition to the analysis folders, you also have an XML file. We will use this XML file to copy the UniqueIDs.

  1. Copy the analysis folders in workspace B to workspace A. In this case, we want to combine workspace B into A (A as main).
  2. Open the XML files of workspace A and B in any text editor. It is better to close the workspaces first to avoid conflicts.
  3. Copy the elements (data) between` <WaveWindCombination> and </WaveWindCombination> tags from Workspace B's XML to Workspace A's XML. This is the data of the Wave/Wind table's DLC in Sesam Wind Manager.
  4. Save Workspace A's XML.
  5. Open Workspace A in Sesam Wind Manager. If done correctly, you would see the finished DLCs from workspace B are copied to workspace A, including the results.
  6. After this, it is the same as before.

Note: You do not need to copy any R#.SIN file as they are not used for the report and can be quite large

Back to top