<div dir="ltr">Hi all,<div><br></div><div>Sorry to bug you again with my issues. I activated casual gain control and ran a simulation with trace facility for casual gains on. The results at a random time step look like this:</div><div><br></div><div><div>Subroutine MZCASI Trace output 26 Zone 15</div><div> Day No. = 147 (i.e. 27th of May.), Time 18:00 Hours</div><div> Subroutine INTLUM Trace output 27 Zone 15 Lvl3.LivingRoom</div><div> Day No. = 147 (i.e. 27th of May.), Time 18:00 Hours</div><div> Light|Sens|sun |via |daylight|visib|sun/dir|sky/dif|sensed|set |ext vert</div><div> zone|num.|seen|window|factor% |trnsm|contrib|contrib|lux |point|ilum(Ev)</div><div> 1 1 no 9 1.23 0.67 0.0 148.4 148.4 500. 6018.</div><div> 1 1 no 10 0.66 0.67 0.0 79.6 79.6 500. 15506.</div><div> 1 1 no 11 0.63 0.67 0.0 76.0 76.0 500. 38597.</div><div> Light zone 1 ON/OFF ESP-r calc df, ZFRAC= 0.00</div><div>Fraction of lighting "ON" FRAC=0.00</div><div> Ext: Dir.nor.rad. W/m^2( 431.0) Dif.hor.rad.( 97.0)</div><div> : sun light lux(34985.0) sky light lux(12035.5)</div><div> : sun/dir efficacy ( 81.17) sky/dif efficacy ( 124.08)</div><div> : solar azi deg( 286.2) solar alt deg( 14.1)</div><div> : TMC blind/shuter(0.00) Sun patch no.( 0)</div></div><div><br></div><div>I have trouble understanding the results. As I have three windows, I see that MZCASI calculates the lux for each one and compares it to the set point (500 here). However, a few lines down, the fraction of lighting "ON" is at 0. Shouldn't that be more than 0 since the sum of the sensed lux from the windows is below 500? Is there something I am missing? I would appreciate it if you could let me know where I could find more information in order to understand the results by the trace facility.</div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div>Kind regards,</div><div><br></div><div>Dimitris</div><div><br></div></div></div></div></div></div></div></div></div></div></div></div></div></div>
<br><div class="gmail_quote">On Sun, Mar 12, 2017 at 2:39 PM, Achim Geissler <span dir="ltr"><<a href="mailto:achim.geissler@intergga.ch" target="_blank">achim.geissler@intergga.ch</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Hi Dimitris,<div><br></div><div>as far as I know, there is no guide readily available, no. The steps are basically the following:</div><div><br></div><div>In cetc/h3kmodule.f90 add the parameter definitions … just follow the general structure of variables given. You will need to give the type (somewhere close to the beginning of the file) </div><div><br></div><div><div style="margin:0px;font-size:11px;line-height:normal;font-family:Menlo;color:rgb(0,143,0)"><span style="font-variant-ligatures:no-common-ligatures;color:#000000"> </span><span style="font-variant-ligatures:no-common-ligatures">!Used by casual.F</span></div><div style="margin:0px;font-size:11px;line-height:normal;font-family:Menlo"><span style="font-variant-ligatures:no-common-ligatures"> </span><span style="font-variant-ligatures:no-common-ligatures;color:#0433ff">Type</span><span style="font-variant-ligatures:no-common-ligatures">(ReportVariable) :: rvXX, rvYY (whatever name you fancy, the “rv” is “report variable” ...)</span></div><div style="margin:0px;font-size:11px;line-height:normal;font-family:Menlo;min-height:13px"><span style="font-variant-ligatures:no-common-ligatures"></span><br></div></div><div style="margin:0px;font-size:11px;line-height:normal;font-family:Menlo;min-height:13px"> ...</div><div><br></div><div>and also the definitions similar to</div><div><br></div><div><div style="margin:0px;font-size:11px;line-height:normal;font-family:Menlo"><span style="font-variant-ligatures:no-common-ligatures"> rvInsolationTotal%<wbr>VariableName = </span><span style="font-variant-ligatures:no-common-ligatures;color:#b4261a">'building/*/insolation/total'</span></div><div style="margin:0px;font-size:11px;line-height:normal;font-family:Menlo"><span style="font-variant-ligatures:no-common-ligatures"> rvInsolationTotal%MetaType = </span><span style="font-variant-ligatures:no-common-ligatures;color:#b4261a">'units'</span></div><div style="margin:0px;font-size:11px;line-height:normal;font-family:Menlo"><span style="font-variant-ligatures:no-common-ligatures"> rvInsolationTotal%VariableType = </span><span style="font-variant-ligatures:no-common-ligatures;color:#b4261a">'(W)'</span></div><div style="margin:0px;font-size:11px;line-height:normal;font-family:Menlo"><span style="font-variant-ligatures:no-common-ligatures"> rvInsolationTotal%Description = </span><span style="font-variant-ligatures:no-common-ligatures;color:#b4261a">'Solar gains admitted through glazing'</span></div><div style="margin:0px;font-size:11px;line-height:normal;font-family:Menlo"><span style="font-variant-ligatures:no-common-ligatures"> </span><span style="font-variant-ligatures:no-common-ligatures;color:#0433ff">Call</span><span style="font-variant-ligatures:no-common-ligatures"> AddVariable(rvInsolationTotal)</span></div><div style="margin:0px;line-height:normal;min-height:13px"><span style="font-variant-ligatures:no-common-ligatures"></span><br></div></div><div style="margin:0px;line-height:normal;min-height:13px">somewhere later on in the file. The “*” in above example allows for zone naming. Likely, you will want to have a second “*” for the lighting zone in a given zone. Then, in casual.F (probably necessary, because the variables of interest are not available via a program-wide common, I think), you will need to call “Addtoreport” like so:</div><div style="margin:0px;line-height:normal;min-height:13px"><br></div><div style="margin:0px;line-height:normal;min-height:13px"><div style="margin:0px;font-size:11px;line-height:normal;font-family:Menlo"><span style="font-variant-ligatures:no-common-ligatures"> </span><span style="font-variant-ligatures:no-common-ligatures;color:#0433ff">call</span><span style="font-variant-ligatures:no-common-ligatures"> AddToReport(</span></div><div style="margin:0px;font-size:11px;line-height:normal;font-family:Menlo"><span style="font-variant-ligatures:no-common-ligatures"> & rvBldZnLightPow%Identifier,</span></div><div style="margin:0px;font-size:11px;line-height:normal;font-family:Menlo"><span style="font-variant-ligatures:no-common-ligatures"> & Cas_Lights(iZone),</span></div><div style="margin:0px;font-size:11px;line-height:normal;font-family:Menlo"><span style="font-variant-ligatures:no-common-ligatures"> & cZone_Chars)</span></div><div style="margin:0px;font-size:11px;line-height:normal;font-family:Menlo;min-height:13px"><br><span style="font-variant-ligatures:no-common-ligatures"></span></div></div><div style="margin:0px;line-height:normal;min-height:13px">where of course the “rvXX” is the name you chose in step 1. Cas_Lights is the value and cZone_Chars is the zone name. If you also have the lighting zone, simply add the appropriate variable after cZone_Chars. Probably it is best to place this close to where the “final value” per time step is available. The procedure is actually quite straightforward and there are many examples in the code from which to learn.</div><div style="margin:0px;line-height:normal;min-height:13px"><br></div><div style="margin:0px;line-height:normal;min-height:13px">Recompile (depending on your development environment, make sure the relevant object files actually have been created newly - make does not always accept the .f90 and attached module as changed!), rerun and check out.dictionary … the new variables should be available.</div><div style="margin:0px;line-height:normal;min-height:13px"><br></div><div style="margin:0px;line-height:normal;min-height:13px">Good luck!</div><div style="margin:0px;line-height:normal;min-height:13px"><br></div><div style="margin:0px;line-height:normal;min-height:13px">Best</div><span class="HOEnZb"><font color="#888888"><div style="margin:0px;line-height:normal;min-height:13px">Achim</div></font></span><div><div class="h5"><div><br></div><div><br><div><blockquote type="cite"><div>On 12 Mar 2017, at 18:54, Dimitris Jim Sfakianakis <<a href="mailto:dsfakianakis@gmail.com" target="_blank">dsfakianakis@gmail.com</a>> wrote:</div><br class="m_3726976239697169348Apple-interchange-newline"><div><div dir="ltr">Hi Achim,<div><br></div><div>I found selum() and zelum() in casual.F, however, I don't know what is the process of including additional variables in the h3k reports. Is there a guide available that can guide me through the process?</div><div class="gmail_extra"><br clear="all"><div><div class="m_3726976239697169348gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div>Kind regards,</div><div><br></div><div>Dimitris</div><div><br></div></div></div></div></div></div></div></div></div></div></div>
<br><div class="gmail_quote">On Fri, Feb 17, 2017 at 12:06 PM, Achim Geissler <span dir="ltr"><<a href="mailto:achim.geissler@intergga.ch" target="_blank">achim.geissler@intergga.ch</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Hi Jim,<div><br></div><div>most likely selum() and zelum(), one is per sensor, the other per zone as far as I recall / can see by a quick peek. Subroutine intlum(). However, at least selum() is reported by trace, so I am not entirely sure they are what you are looking for. </div><div><br></div><div>Best</div><div>Achim</div><div><br></div><div><div><div class="m_3726976239697169348h5"><br><div><blockquote type="cite"><div>On 16 Feb 2017, at 23:01, Dimitris Jim Sfakianakis <<a href="mailto:dsfakianakis@gmail.com" target="_blank">dsfakianakis@gmail.com</a>> wrote:</div><br class="m_3726976239697169348m_6606641627838258025Apple-interchange-newline"><div><div dir="auto"><div>Hi Achim,<div dir="auto"><br></div><div dir="auto">Thank you for the response, really appreciate it. Do you happen to remember what the variable for the lumens is? I am pretty sure it won't be difficult to locate but it'd help a lot if you happene to remember it.</div><div dir="auto"><br></div><div dir="auto">Thanks!</div><br><div class="gmail_extra"><br><div class="gmail_quote">On Feb 14, 2017 8:55 AM, "Achim Geissler" <<a href="mailto:achim.geissler@intergga.ch" target="_blank">achim.geissler@intergga.ch</a>> wrote:<br type="attribution"><blockquote class="m_3726976239697169348m_6606641627838258025quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang="DE-CH" link="blue" vlink="purple"><div class="m_3726976239697169348m_6606641627838258025m_-6139035582710096006WordSection1"><p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Dear Jim,<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">it has been a while, but as far as I recall that data really is not transported to any results listings. If you are prepared to compile ESP-r, you could probably pipe the desired variables out via h3k output quite easily (esrubld/casual.F).<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Best<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Achim<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p><p class="MsoNormal"><b><span lang="DE" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Von:</span></b><span lang="DE" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> <a href="mailto:esp-r-bounces@lists.strath.ac.uk" target="_blank">esp-r-bounces@lists.strath.ac.<wbr>uk</a> [mailto:<a href="mailto:esp-r-bounces@lists.strath.ac.uk" target="_blank">esp-r-bounces@lists.st<wbr>rath.ac.uk</a>] <b>Im Auftrag von </b>Dimitris "Jim" Sfakianakis<br><b>Gesendet:</b> Montag, 13. Februar 2017 21:29<br><b>An:</b> <a href="mailto:esp-r@lists.strath.ac.uk" target="_blank">esp-r@lists.strath.ac.uk</a><br><b>Betreff:</b> [esp-r] Getting the value for Lumens in a zone<u></u><u></u></span></p><div class="m_3726976239697169348m_6606641627838258025elided-text"><p class="MsoNormal"><u></u> <u></u></p><div><p class="MsoNormal">Hi group,<u></u><u></u></p><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">I have been working on a project with lighting control. I set up a casual gains control file in order to represent optimal lighting control in my model.<u></u><u></u></p></div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">Is there a way to pull the value for the Lumens in a zone at each time step, after the simulation?<u></u><u></u></p></div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">I checked in the "results analysis" and "trace facilities" but couldn't locate the associated parameter.<u></u><u></u></p></div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">Your help is greatly appreciated!<u></u><u></u></p></div><div><p class="MsoNormal"><br clear="all"><u></u><u></u></p><div><div><div><div><div><div><div><div><div><div><p class="MsoNormal">Kind regards,<u></u><u></u></p></div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">Jim<u></u><u></u></p></div><div><p class="MsoNormal"><u></u> <u></u></p></div><div><p class="MsoNormal">e: <a href="mailto:dsfakianakis@gmail.com" target="_blank">dsfakianakis@gmail.com</a><u></u><u></u></p></div><div><p class="MsoNormal"><u></u> <u></u></p></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div><br>______________________________<wbr>_________________<br>
esp-r mailing list<br>
<a href="mailto:esp-r@lists.strath.ac.uk" target="_blank">esp-r@lists.strath.ac.uk</a><br>
<a href="http://lists.strath.ac.uk/mailman/listinfo/esp-r" rel="noreferrer" target="_blank">http://lists.strath.ac.uk/mail<wbr>man/listinfo/esp-r</a><br></blockquote></div><br></div></div></div>
</div></blockquote></div><br></div></div><div>
<span class="m_3726976239697169348m_6606641627838258025Apple-style-span" style="border-collapse:separate;font-family:Helvetica;font-size:12px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-variant-numeric:normal;font-variant-alternates:normal;font-variant-east-asian:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><div><a href="mailto:achim.geissler@intergga.ch" target="_blank">achim.geissler@intergga.ch</a></div><div><br></div><div><br></div></span><br class="m_3726976239697169348m_6606641627838258025Apple-interchange-newline">
</div>
<br></div></div><br>______________________________<wbr>_________________<br>
esp-r mailing list<br>
<a href="mailto:esp-r@lists.strath.ac.uk" target="_blank">esp-r@lists.strath.ac.uk</a><br>
<a href="http://lists.strath.ac.uk/mailman/listinfo/esp-r" rel="noreferrer" target="_blank">http://lists.strath.ac.uk/mail<wbr>man/listinfo/esp-r</a><br></blockquote></div><br></div></div>
______________________________<wbr>_________________<br>esp-r mailing list<br><a href="mailto:esp-r@lists.strath.ac.uk" target="_blank">esp-r@lists.strath.ac.uk</a><br><a href="http://lists.strath.ac.uk/mailman/listinfo/esp-r" target="_blank">http://lists.strath.ac.uk/<wbr>mailman/listinfo/esp-r</a></div></blockquote></div><br><div>
<span class="m_3726976239697169348Apple-style-span" style="border-collapse:separate;font-variant-ligatures:normal;font-variant-numeric:normal;font-variant-alternates:normal;font-variant-east-asian:normal;line-height:normal;border-spacing:0px"><div><a href="mailto:achim.geissler@intergga.ch" target="_blank">achim.geissler@intergga.ch</a></div><div><br></div><div><br></div></span><br class="m_3726976239697169348Apple-interchange-newline">
</div>
<br></div></div></div></div><br>______________________________<wbr>_________________<br>
esp-r mailing list<br>
<a href="mailto:esp-r@lists.strath.ac.uk">esp-r@lists.strath.ac.uk</a><br>
<a href="http://lists.strath.ac.uk/mailman/listinfo/esp-r" rel="noreferrer" target="_blank">http://lists.strath.ac.uk/<wbr>mailman/listinfo/esp-r</a><br></blockquote></div><br></div></div>