Closed saroele closed 10 years ago
IDEAS.BoundaryConditions.WeatherData.ReaderTMY3 contains two separate CombiTables1Ds because apparently some of the signals require a time offset of 1800s. So to me this looks like expected behavior.
Yes, solar data have t obe read differently compared to the other type of data.
On Mon, Jun 2, 2014 at 4:50 PM, Filip notifications@github.com wrote:
IDEAS.BoundaryConditions.WeatherData.ReaderTMY3 contains two separate CombiTables1Ds because apparently some of the signals require a time offset of 1800s. So to me this looks like expected behavior.
— Reply to this email directly or view it on GitHub https://github.com/open-ideas/IDEAS/issues/58#issuecomment-44846414.
Would it be possible to apply a time lag to the input or output of just one table reader?
The delay()-function is computationally much heavier, While this one doesn't impact simulation speed ...
On Monday, June 2, 2014, saroele notifications@github.com wrote:
Would it be possible to apply a time lag to the input or output of just one table reader?
— Reply to this email directly or view it on GitHub https://github.com/open-ideas/IDEAS/issues/58#issuecomment-44851847.
I'm already looking at the case of MPC: if the emulator model has to load the same file twice every time it is called, it will be slower. We noticed before that loading of the input files is the main time constraint for MPC.
Let's leave it for now and we solve this issue when it is blocking us in MPC applications.
I don't immediately find the cause, but the climate file is loaded twice:
dymosim started ... "dsin.txt" loading (dymosim input file) ... loading "data" from "/home/roel/data/work/temp/../Inputs/Uccle_TMY3_60.txt" ... loading "data" from "/home/roel/data/work/temp/../Inputs/Uccle_TMY3_60.txt" ... "Heating_Radiators.mat" creating (simulation result file)