Source code for a sample plugin can be found at
To view and run the sample code in Visual Studio
By default Ecosim runs on a monthly time step, 12 time steps per year. To accommodate a variable time step Ecosim can be told to run more then one time step in a month via the cEcosimDataStuctures.StepsPerMonth property. The StepsPerMonth property is only accessible from code and can not be set in the Scientific Interface. This allows Ecosim to run on a sub time step scheme by setting the cEcosimDataStuctures.StepsPerMonth property to the number of sub time steps to run in a month. At the end of each run Ecosim will set cEcosimDataStuctures.StepsPerMonth back to its default value of one.
When running on sub time steps Ecosim will only update its results objects cCore.cEcoSimResults(), cCore.cEcosimGroupOutput(), cCore.cEcosimOutput() and cCore.cEcosimFleetOutput() once at the end of the month. Data computed for the sub time step can only be access via the cEcosimDataStrucutres provided by the IEcosimSubTimestepsPlugin.EcosimSubTimeStepBegin() and IEcosimSubTimestepsPlugin.EcosimSubTimeStepEnd() plugin points. The IEcosimBeginTimestepPlugin.EcosimBeginTimeStep() and IEcosimEndTimestepPlugin.EcosimEndTimeStep() will only be call at the start and end of the month not during the sub time step and will not contain the sub time step data.
IEcosimSubTimestepsPlugin.EcosimSubTimeStepBegin(ByRef BiomassAtTimestep() As Single, ByVal TimeInYears As Single, ByVal DeltaT As Single, ByVal SubTimestepIndex As Integer, ByVal EcosimDatastructures As Object)
IEcosimSubTimestepsPlugin.EcosimSubTimeStepEnd(ByRef BiomassAtTimestep() As Single, ByVal TimeInYears As Single, ByVal DeltaT As Single, ByVal SubTimestepIndex As Integer, ByVal EcosimDatastructures As Object)
Ecosim can be run on its own thread by setting the cEcosimDataStuctures.bMultiThreaded Boolean flag to True. The next time Ecosim is run it will run on its own thread. Once the Ecosim run has completed the cEcosimDataStuctures.bMultiThreaded flag will be automatically set to its default value of False and all subsequent runs will be on the main application thread. All plug-in calls that originate on a thread other than the main thread will be marshaled to the main thread. This is for robustness, in .NET user interface controls cannot be accessed from a thread other than that which they were created on. Plug-ins are created and run on the main thread by the EwE framework. By automatically marshaling all plug-in calls to the main thread plug-in points do not have to marshal calls to an interface.