In CASAS code, distributed development time model (DDTM) contains two extra bins in its implementation: flow-in, and flow-out.
The value of the flow-in bin is set to be the flow out of the previous life-stage, which feeds into the first bin of the DDTM. The flow in bin does not empty.
The flow-out bin accumulates the flow-out of the final bin of the life-stage.
Questions
The flow-in bin does not empty, and is overwritten daily. Therefore not every member added to the flow-in bin passes into the DDTM. Is there a physiological reason for this? Does it model loss between stages/some harbouring behaviour?
The flow-in and flow-out functionality creates 'buffers' or 'discontinuities' when the model is run, in the sense that between days, there are individuals who sit between models. This does not seem natural.
Does CASAS want the functionality where between life-stages, the last bin of the previous stage is linked to the first bin of the next stage and simulated immediately, in the same way that flow between bins in a single DDTM is simulated?
Description
In CASAS code, distributed development time model (DDTM) contains two extra bins in its implementation: flow-in, and flow-out.
Questions