[esp-r] Re: Getting the value for Lumens in a zone

Achim Geissler achim.geissler at intergga.ch
Fri Mar 17 17:39:26 GMT 2017


Dear Dimitris,

have you looked at earlier time steps in the trace? In any case, your control period stops at 18:00 and the time step reported on is also 18:00 so this could be an issue. Everything else in the .cgc looks O.K., to me.

Achim


> On 17 Mar 2017, at 18:31, Dimitris Jim Sfakianakis <dsfakianakis at gmail.com> wrote:
> 
> Dear Achim,
> 
> The switch off level has been set to 1.5 (default) as seen in the .cgc file pasted below. The way I translate that is that if the setpoint is 500lux, the lights will switch off at 750lux. As I have a simple "on-off" control law, I assume that if the natural lighting entering the zone is below 750lux, the lights should be on. 
> 
> *Casual_gain_ctl
> *desc Labs have a min lux of 500
> 2 2 2 2 # Gain to ctl for different day types
>   8 18  # Control period start & end hours
>   1  # No. of lighting zone(s)
>  500.0  1.5  0.1  0.1  0 # Setpt, switch off lvl, min dim/el, delay
>  1.00  1  1 # % casual, no of sensors, calc type
>   4.150 18.200  9.800  0.000  0.000  1.000 # Sensor x y z & dir vect
>   1 # Control law: On-Off  
> 
> As for the lighting load in the .opr file, yes, I have defined lighting heat gains for 3 different day types (weekday, sat and sun).
> 
> Also the position of the sensor is defined based on the site coordinates and not relative to the thermal zone.
> 
> Kind regards,
> 
> Dimitris
> 
> 
> 
> On Fri, Mar 17, 2017 at 10:47 AM, Achim Geissler <achim.geissler at intergga.ch <mailto:achim.geissler at intergga.ch>> wrote:
> Hi Dimitris,
> 
>  
> 
> as mentioned earlier, I haven’t used this for quite some time. However, I seem to remember that there was a “switch off level” to be defined. If this is set below 1.0, then you may have lights off even though your setpoint is not reached.
> 
>  
> 
> You have one lighting zone in your thermal zone, so “ % casual” is set to 1.0?
> 
>  
> 
> Also (I hesitate to ask) you do have light loads defined in .opr? Even though I have no idea if the non-definition could have any influence on what you report, below.
> 
>  
> 
> Hopefully, someone else will be able to help more.
> 
>  
> 
> Best
> 
> Achim
> 
>  
> 
>  
> 
>  
> 
> Von: esp-r-bounces at lists.strath.ac.uk <mailto:esp-r-bounces at lists.strath.ac.uk> [mailto:esp-r-bounces at lists.strath.ac.uk <mailto:esp-r-bounces at lists.strath.ac.uk>] Im Auftrag von Dimitris "Jim" Sfakianakis
> Gesendet: Freitag, 17. März 2017 15:56
> An: esp-r at lists.strath.ac.uk <mailto:esp-r at lists.strath.ac.uk> Club
> Betreff: [esp-r] Re: Getting the value for Lumens in a zone
> 
>  
> 
> Hi all,
> 
>  
> 
> 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:
> 
>  
> 
> Subroutine MZCASI Trace output  26     Zone 15
> 
>  Day No. = 147 (i.e. 27th of May.),  Time 18:00 Hours
> 
>  Subroutine INTLUM  Trace output  27 Zone 15 Lvl3.LivingRoom
> 
>  Day No. = 147 (i.e. 27th of May.),  Time 18:00 Hours
> 
>  Light|Sens|sun |via   |daylight|visib|sun/dir|sky/dif|sensed|set  |ext vert
> 
>   zone|num.|seen|window|factor% |trnsm|contrib|contrib|lux   |point|ilum(Ev)
> 
>      1    1  no       9     1.23  0.67     0.0   148.4  148.4  500.    6018.
> 
>      1    1  no      10     0.66  0.67     0.0    79.6   79.6  500.   15506.
> 
>      1    1  no      11     0.63  0.67     0.0    76.0   76.0  500.   38597.
> 
>  Light zone 1 ON/OFF ESP-r calc df, ZFRAC= 0.00
> 
> Fraction of lighting "ON" FRAC=0.00
> 
>  Ext: Dir.nor.rad. W/m^2(  431.0) Dif.hor.rad.(   97.0)
> 
>     : sun light lux(34985.0) sky light lux(12035.5)
> 
>     : sun/dir efficacy (  81.17) sky/dif efficacy ( 124.08)
> 
>     : solar azi deg( 286.2) solar alt deg(  14.1)
> 
>     : TMC blind/shuter(0.00) Sun patch no.(  0)
> 
>  
> 
> 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.
> 
> 
> 
> Kind regards,
> 
>  
> 
> Dimitris
> 
>  
> 
>  
> 
> On Sun, Mar 12, 2017 at 2:39 PM, Achim Geissler <achim.geissler at intergga.ch <mailto:achim.geissler at intergga.ch>> wrote:
> 
> Hi Dimitris,
> 
>  
> 
> as far as I know, there is no guide readily available, no. The steps are basically the following:
> 
>  
> 
> 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) 
> 
>  
> 
>    !Used by casual.F
> 
>    Type(ReportVariable) :: rvXX, rvYY (whatever name you fancy, the “rv” is “report variable” ...)
> 
>  
> 
>    ...
> 
>  
> 
> and also the definitions similar to
> 
>  
> 
>       rvInsolationTotal%VariableName = 'building/*/insolation/total'
> 
>       rvInsolationTotal%MetaType = 'units'
> 
>       rvInsolationTotal%VariableType = '(W)'
> 
>       rvInsolationTotal%Description = 'Solar gains admitted through glazing'
> 
>       Call AddVariable(rvInsolationTotal)
> 
>  
> 
> 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:
> 
>  
> 
>         call AddToReport(
> 
>      &     rvBldZnLightPow%Identifier,
> 
>      &     Cas_Lights(iZone),
> 
>      &     cZone_Chars)
> 
>  
> 
> 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.
> 
>  
> 
> 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.
> 
>  
> 
> Good luck!
> 
>  
> 
> Best
> 
> Achim
> 
>  
> 
>  
> 
> On 12 Mar 2017, at 18:54, Dimitris Jim Sfakianakis <dsfakianakis at gmail.com <mailto:dsfakianakis at gmail.com>> wrote:
> 
>  
> 
> Hi Achim,
> 
>  
> 
> 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?
> 
> 
> 
> Kind regards,
> 
>  
> 
> Dimitris
> 
>  
> 
>  
> 
> On Fri, Feb 17, 2017 at 12:06 PM, Achim Geissler <achim.geissler at intergga.ch <mailto:achim.geissler at intergga.ch>> wrote:
> 
> Hi Jim,
> 
>  
> 
> 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. 
> 
>  
> 
> Best
> 
> Achim
> 
>  
> 
>  
> 
> On 16 Feb 2017, at 23:01, Dimitris Jim Sfakianakis <dsfakianakis at gmail.com <mailto:dsfakianakis at gmail.com>> wrote:
> 
>  
> 
> Hi Achim,
> 
>  
> 
> 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.
> 
>  
> 
> Thanks!
> 
>  
> 
>  
> 
> On Feb 14, 2017 8:55 AM, "Achim Geissler" <achim.geissler at intergga.ch <mailto:achim.geissler at intergga.ch>> wrote:
> 
> Dear Jim,
> 
>  
> 
> 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).
> 
>  
> 
> Best
> 
> Achim
> 
>  
> 
>  
> 
>  
> 
> Von: esp-r-bounces at lists.strath.ac.uk <mailto:esp-r-bounces at lists.strath.ac.uk> [mailto:esp-r-bounces at lists.strath.ac.uk <mailto:esp-r-bounces at lists.strath.ac.uk>] Im Auftrag von Dimitris "Jim" Sfakianakis
> Gesendet: Montag, 13. Februar 2017 21:29
> An: esp-r at lists.strath.ac.uk <mailto:esp-r at lists.strath.ac.uk>
> Betreff: [esp-r] Getting the value for Lumens in a zone
> 
>  
> 
> Hi group,
> 
>  
> 
> 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.
> 
>  
> 
> Is there a way to pull the value for the Lumens in a zone at each time step, after the simulation?
> 
>  
> 
> I checked in the "results analysis" and "trace facilities" but couldn't locate the associated parameter.
> 
>  
> 
> Your help is greatly appreciated!
> 
> 
> 
> Kind regards,
> 
>  
> 
> Jim
> 
>  
> 
> e: dsfakianakis at gmail.com <mailto:dsfakianakis at gmail.com>
>  
> 
> 
> _______________________________________________
> esp-r mailing list
> esp-r at lists.strath.ac.uk <mailto:esp-r at lists.strath.ac.uk>
> http://lists.strath.ac.uk/mailman/listinfo/esp-r <http://lists.strath.ac.uk/mailman/listinfo/esp-r>
>  
> 
>  
> 
> achim.geissler at intergga.ch <mailto:achim.geissler at intergga.ch>
>  
> 
>  
> 
>  
> 
>  
> 
> 
> _______________________________________________
> esp-r mailing list
> esp-r at lists.strath.ac.uk <mailto:esp-r at lists.strath.ac.uk>
> http://lists.strath.ac.uk/mailman/listinfo/esp-r <http://lists.strath.ac.uk/mailman/listinfo/esp-r>
>  
> 
> _______________________________________________
> esp-r mailing list
> esp-r at lists.strath.ac.uk <mailto:esp-r at lists.strath.ac.uk>
> http://lists.strath.ac.uk/mailman/listinfo/esp-r <http://lists.strath.ac.uk/mailman/listinfo/esp-r>
>  
> 
> achim.geissler at intergga.ch <mailto:achim.geissler at intergga.ch>
>  
> 
>  
> 
>  
> 
>  
> 
> 
> _______________________________________________
> esp-r mailing list
> esp-r at lists.strath.ac.uk <mailto:esp-r at lists.strath.ac.uk>
> http://lists.strath.ac.uk/mailman/listinfo/esp-r <http://lists.strath.ac.uk/mailman/listinfo/esp-r>
>  
> 
> 
> _______________________________________________
> esp-r mailing list
> esp-r at lists.strath.ac.uk <mailto:esp-r at lists.strath.ac.uk>
> http://lists.strath.ac.uk/mailman/listinfo/esp-r <http://lists.strath.ac.uk/mailman/listinfo/esp-r>
> 

achim.geissler at intergga.ch




-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.strath.ac.uk/archives/esp-r/attachments/20170317/4927c0cc/attachment-0001.html 


More information about the esp-r mailing list