<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
The structure of the various sql tables are fixed, but the contents
of the sql time series output are completely user-specified. And
generating output for the design day simulations is also optional.
Each specified Output:Variable can be reported at one or more of the
following frequencies: hvac timestep, zone timestep, hourly, daily,
monthly, or annual. <br>
<br>
So, to do as you suggest (always report drybulb and wetbulb to match
the weather data), the user would create a snippet of input to add
to every idf file specifying these output variables at the timestep
frequency (due to sub-hourly interpolation it will match the hourly
weather data once per hour).<br>
<br>
Always interested in building bridges. Maybe we can pique your
curiosity enough to consider adding another tool to your toolbox.
:-) <br>
<br>
Mike<br>
p.s. See many of you soon in KC for ASHRAE and IBPSA-USA.<br>
<br>
<br>
<div class="moz-cite-prefix">On 6/20/2019 2:03 PM, Nicholas Caton
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:AM5PR04MB32987D279C3994CE4EAAF62CE7E40@AM5PR04MB3298.eurprd04.prod.outlook.com">
<p class="MsoNormal"><span style="color:windowtext">I sincerely
appreciate the spirit of building bridges in 2 directions,
thanks so much Mike!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">Out of
curiosity, does energy+ as an engine, or else any of its major
interfaces, permit an end-user to tweak this .sql output to
always (by default, with all projects) include as an example
drybulb and wetbulb at intervals to match the source weather
data fed in, or are the contents/structure of this particular
output kinda “boxed up?”<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:windowtext">With your
input, I might suggest some additional steps for anyone
following along:<o:p></o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph"
style="color:windowtext;margin-left:0in;mso-list:l8 level1
lfo11">
Trimming and/or isolating the first ### rows of data to review
regular simulation and design day information separately.
Alternatively these are likely tagged in some fashion I
haven’t discovered yet in the SQL structure and could be
filtered in/out based on that tag.<o:p></o:p></li>
<li class="MsoListParagraph"
style="color:windowtext;margin-left:0in;mso-list:l8 level1
lfo11">
By using ReportVariableWithTime, it <i><u>sounds like</u></i>
you can avoid the extra steps I suggested to convert the
interval count (the x-axes in the visuals below) into DateTime
format.
<o:p></o:p></li>
<li class="MsoListParagraph"
style="color:windowtext;margin-left:0in;mso-list:l8 level1
lfo11">
Once pivot charts/tables have properly formatted DateTime
stamps generated (or fed in), they can do a number of new
magical things around grouping and displaying
min/max/avg/more-complicated calcs with dynamic grouping. So
for example with the same query you could have a visual that
lets you start at an annual 12-month view then “zoom” into a
specific month/week/day/hour to see the data at its full
resolution or any grouping in between.</li>
</ul>
</blockquote>
<br>
</body>
</html>