/
2.3 Typical SEAMCAT workflow

2.3 Typical SEAMCAT workflow

When using SEAMCAT for a compatibility analysis, a typical workflowwould be asfollows:

  1. Create or update a simulation workspace;
  2. Set the simulation control parameters (number of events, debug mode or not);
  3. Run a simulation;
  4. Analyse the event generation results, modify the input scenario if necessary and re-run the event generation;
  5. Perform one or more interference calculation runs;
  6. Generate a simulation report.

 

Figure 21: Typical work flow when using SEAMCAT

In addition to these basic steps futher ones may be useful for different purposes:

  • Save workspace as an XML compliant file for later (repeated) work or for sharing with other users;
  • Create or update elements in the equipment library for repeatedly used equipment types;
  • Import a library;
  • Use of batch job, to serialise your work;
  • Share your workspace with others;
  • Use of an Event Processing Plugin for advanced scenario specific calculations.


Related content

2.6 Batch operation
2.6 Batch operation
More like this
14.2.3 Packages
14.2.3 Packages
More like this
2.4.1 Scenario workspace
2.4.1 Scenario workspace
More like this
11.1 Event processing concept
11.1 Event processing concept
More like this
2.2 Welcome to SEAMCAT window
2.2 Welcome to SEAMCAT window
More like this
Quick Start in SEAMCAT
Quick Start in SEAMCAT
More like this