The Distributed Processing Module uses multiple copies of GoldSim (processes) running on multiple machines (and/or multiple processors or cores within a single machine) to share the computational burden of a Monte Carlo simulation.
A distributed processing simulation is controlled by a
single
The Controller process assigns and sends individual realizations to the Client processes. Each Client process carries out its assigned realization A single model run within a Monte Carlo simulation. It represents one possible path the system could follow through time., sends the results to the Controller process, and then makes itself available to work on another realization. Once all of the realizations have been completed, the Controller process combines all of the results into a single GoldSim file (and enters Result Mode The state of a model when it has been run and contains simulation results for a single set of input parameters.) just as if the entire simulation had been carried out on the Controller process’s machine.
The GoldSim model file (and other required files such as user-created DLLs or linked spreadsheets) need not be present on machines running Client processes. The Controller process automatically transfers any necessary files to the Client machines.
When running as a Client process, GoldSim is run in a special mode. Rather than launching GoldSim in the traditional manner on the machine running the Client, a GoldSim Client is launched from the command line (this can be done using a Windows shortcut or the Run option on the Windows Start menu). When running in Client mode, you cannot view or edit a GoldSim model. The only function that a Client serves is to receive, process, and send back realizations sent to it by a Controller process.
In order for the Controller process to access the Client processes, they must be local to the computer or accessible over a network.