Timestep illogical graph from OS output - split over two periods
OK, I can't upload any files yet so I'll have to describe.
Edit: here's the graph. link text
Looking at OS report in Timetep, a line graph for operative temperature shows the expected fluctuations throughout the weather year from 2006-2007. Fine. It also shows a line running from the first point in 2006 to a point at the start of 2017, where it populates a much more sparse and messy graph where points connect horizontally backwards to other points, as if the sequence is not related to the plotted dates. It looks like someone's done a scribble on the end of the graph effectively.
I thought it might be the .ddy file being based on a separate year, and the sparser second graph was just showing the design days, but looking at the .ddy and .epw files in elements shows they're all for the same year, which is actually 2013, not 2006. The .epw and .ddy files are drawn from a 2006-2018 dataset, so it may just be ignoring the year stamp when it runs the simulation?
The weather files are from here: link text
Any ideas? I'm quite new to this and learning as I go. Cheers.
You said you looked at an OS report in "Timestep" -- what is Timestep?
Timestep's an open-source alternative to DView that is able to handle larger files for visual graphing. I don't think it's the problem though. I can't check as DView doesn't seem to have that same line graph option. I was just a little concerned that it represented a flaw in the weather data I was using.
@ARYardley can you include a link to your OSM? From the Timestep screen shot, my best guess is that you are running multiple design days for heating and cooling first, then an annual simulation after that. If you were to really zoom in, the lines would start on the right for the design days in 2017, then connect to the first point in 2006 for the annual simulation.
Sure, here's the link: https://drive.google.com/file/d/1Qtsw...
I think you're probably right, as the .ddy file seems to include several iterations fo each day at different probability ratings. Given my lack of experience, I just decided to use the ddy file as is and not touch anything, since I didn't want to break anything, but it does take much longer to run simulations than another building I'm running witha different weather file. It's important that I get it right as this is the location most of my study will use.