Skip to content

begin to deal with time varying ranges correctly in cinema

Before this change cinema exports would end up with the range of just the last timestep in the data base. Now we end up, after a simulation run or time varying data export, with the global range instead. specC direct float buffer outputs at least will now be correct at every timestep. specB still has issues because each timestep must be individually normalized.

Merge request reports