For the most part, if you need to run Monte Carlo simulations for a complex model, the use of the Distributed Processing Module is advantageous and strongly encouraged. There are some situations, however, in which use of the Distributed Processing Module may not be feasible.
In particular, because a distributed processing simulation requires that potentially large quantities of data (i.e., the GoldSim model file and other associated files, the results of each realization A single model run within a Monte Carlo simulation. It represents one possible path the system could follow through time.) be passed between the Controller process A GoldSim executable that manages Client processes in order to carry out distributed processing of a Monte Carlo simulation using the Distributed Processing Module. and Client Also referred to as a Client process. A GoldSim executable running on a client machine that can be used to carry out distributed processing of a Monte Carlo simulation using the Distributed Processing Module. processes over a network, effective use of the Distributed Processing Module requires fast network connections (and fast computers). If the connections between the processes are slow, a distributed processing simulation may be impractical.
In addition, there are three situations in which distributed processing is not supported at all:
- You cannot run multiple scenarios (using the Scenario Manager A dialog that allows you to create, define and run scenarios.) and utilize distributed processing. That is, the Scenario A specific set of input data (and corresponding outputs) for a model. Multiple scenarios can be defined for a model. Different scenarios within a model are specifically differentiated by having different values for one or more Data elements. Manager provides no access to distributing processing capabilities.
- Because distributed processing can not be used for a single realization, and high resolution results (in which all unscheduled timesteps are displayed) are only available for single realizations runs, high resolution results (i.e., time histories that include unscheduled updates Timesteps that are inserted automatically by GoldSim during a simulation and are not directly specified by the user prior to running the model.) can never be viewed for distributed processing simulations.
- You cannot export results to a Spreadsheet element An element that can dynamically link to an Excel spreadsheet. when doing a distributed processing run (as each realization would result in a different spreadsheet file).