All that work we did to save off the state variables so that you could run a model for, say, 100 ms, then continue it on for 100 ms has a little problem, which @ajc158 already mentioned in #16:
If you have delays in the connections between the populations, you need a record of the delayed state variables in order to be able to continue the model correctly, so the saving code needs to deal with that in some way. Essentially, we have delayed differential equations whose correct operation depends on having old state variable data available - the amount of old state variable data you need depends on the timestep size and the amount of delay in the connection.
The components have a delay buffer when there's a connection delay - we need to store this delay buffer in the model xml or some sort of associated file, and then restore it into the component at run time.
All that work we did to save off the state variables so that you could run a model for, say, 100 ms, then continue it on for 100 ms has a little problem, which @ajc158 already mentioned in #16:
If you have delays in the connections between the populations, you need a record of the delayed state variables in order to be able to continue the model correctly, so the saving code needs to deal with that in some way. Essentially, we have delayed differential equations whose correct operation depends on having old state variable data available - the amount of old state variable data you need depends on the timestep size and the amount of delay in the connection.
The components have a delay buffer when there's a connection delay - we need to store this delay buffer in the model xml or some sort of associated file, and then restore it into the component at run time.