Functions for running a multi-stock and/or multi-fleet Management Strategy Evaluation (closed-loop simulation) for a specified operating model
SimulateMOM(MOM = MSEtool::Albacore_TwoFleet, parallel = TRUE, silent = FALSE) ProjectMOM( multiHist = NULL, MPs = NA, parallel = FALSE, silent = FALSE, checkMPs = TRUE, dropHist = TRUE ) multiMSE( MOM = MSEtool::Albacore_TwoFleet, MPs = list(list(c("AvC", "DCAC"), c("FMSYref", "curE"))), Hist = FALSE, silent = FALSE, parallel = TRUE, checkMPs = TRUE, dropHist = TRUE )
A multi-fleet multi-stock operating model (class 'MOM')
Logical or a named list. Should MPs be run using parallel processing? See Details for more information.
Should messages be printed out to the console?
An Historical Simulation object (class
A matrix of methods (nstock x nfleet) (character string) of class MP
Logical. Check if the specified MPs exist and can be run on
Logical. Drop the (very large)
multiHist object from the returned
multiHist object can be (re-)created using
SimulateMOM or kept in
Should model stop after historical simulations? Returns a list containing all historical data
Functions return objects of class
SimulateMOM - An object of class
ProjectMOM - An object of class
multiMSE - An object of class
For most MPs, running in parallel can actually lead to an increase in computation time, due to the overhead in sending the
information over to the cores. Consequently, by default the MPs will not be run in parallel if
(although other internal code will be run in parallel mode).
To run MPs in parallel, specify a named list with the name of the MP(s) assigned as TRUE. For example,
will run the
AvC MP in parallel mode.
SimulateMOM(): Simulate historical dynamics for multi-OM
ProjectMOM(): Run Forward Projections for a
multiMSE(): Run a multi-stock, multi-fleet MSE