WikiPrint - from Polar Technologies

MSE Batch plugin user notes

10 Sept, 2010


The MSE Batch plugin runs the MSE (Management Strategy Evaluator) in batch mode from a command file. The command file runs the MSE changing input harvest rule parameters for each iteration and outputting data file.

MSE parameters available through the command file.

  1. Number of MSE simulations
  2. End Year
  3. Assessment and Implementation error
  4. Primary Production forcing functions
  5. Primary Production forcing function variation
  6. Fleet Control types
  7. Harvest rules

How to run

still to do Load the MSE batch plugin interface from the MSE in the navigation tree Load a command file hit the run button

MSE Batch iterations

The MSE Batch loops over Forcing Functions, Fleet Control types and Harvest Rules running the MSE for each set of parameters from the command file. Parameters not set by the command file will be left at the values loaded by the current Ecosim model.

Sample loops structure

  For each Forcing Function 
    For each Fleet Control
      For each Harvest Rule 

        MSE run...

      next Harvest Rule
    next Fleet Control
  next Forcing Function

Command file format

The command file is a CSV (coma separated values) file that contains tags. A tag is a predefined string of text that appears at the start of the line and is used to identify the line as valid input for the MSE module. After the data part of the tag there must be a least one empty entry to mark the end of the valid data. All data that appears after the empty entry will be ignored. For example

Control_File_Version,1.0,,,ignored comments,,,

Lines in the command file that do not contain a recognized tag will be ignored. A command file can have any number of lines that are not valid inputs as long as they don't start with a valid tag, these could include comments and user notes. The order of the tags in the file is not important.





Model_Name,C:\EwE\Some model.ewemdb,,,










Output_Directory,C:\EwE data,,






  1. Forcing function index for the currently load Ecosim model. See "Time dynamics (Ecoism)>Forcing function" in the EwE interface for the currently loaded forcing functions and indexes.
  2. Name of the forcing function. This is just used a check and a warning will be posted if the name in the model and command file do not match.
  3. Ecosim group index to apply the forcing function to. If the Group index does not match a primary producer group in Ecosim the MSE Batch will post an error and will not run.