I have a model with various subsystems operating at different sample times. After generating code, I see that all outport data, regardless of sample period, is assigned to the one "ExtY_multirateExample_T" structure:

// External outputs (root outports fed by signals with default storage)
struct ExtY_multirateExample_T {
real_T LoRateOutport; // '<Root>/LoRateOutport'
real_T HighRateOutport; // '<Root>/HighRateOutport'
real_T BaseRateOutport; // '<Root>/BaseRateOutport'
real_T output_1hz; // '<Root>/output_1hz'
};
We have not yet finalized the sample times in our model, so we would like a flexible way for our test harness to know when to read new data.
 
1) Is there a recommended strategy to add some sort of flag/pulse in the generated code that would indicate when a certain subsystem's data is fresh (not stale)? This would indicate when a subrate's data (and its associated subsystem) gets fresh information written to it at that model step.
 
2) Is there a way to assign outport data of different sample periods to separate output data structures?