Question-and-Answer Resource for the Building Energy Modeling Community
Get started with the Help page
Ask Your Question

Revision history [back]

Dear Raphael,

I followed your suggestion, but there is something strange within the evaluated schedule after applying EMS coding on the transparency shading schedule.

As you see here I defined three ranges to control the shading transparency based on the 'Surface Outdoor Face Sunlit Fraction' which in my case I selected the external window surface as a sample.

EnergyManagementSystem:Sensor,

S1,                      !- Name

zone_0_Srf_0_glz_0,      !- Output:Variable or Output:Meter Index Key Name

Surface Outside Face Sunlit Fraction ;  !- Output:Variable or Output:Meter Name

EnergyManagementSystem:Actuator,

myA1,                    !- Name

ASF,                     !- Actuated Component Unique Name

Schedule:Year,           !- Actuated Component Type

Schedule Value;          !- Actuated Component Control Type

EnergyManagementSystem:ProgramCallingManager,

MyComputedTransProg,     !- Name

BeginTimestepBeforePredictor,  !- EnergyPlus Model Calling Point

MyComputedTransSch;      !- Program Name 1

EnergyManagementSystem:Program,

MyComputedTransSch,      !- Name

Set SurfaceFraction = S1,!- Program Line 1

IF SurfaceFraction < 0.3,!- Program Line 2

SET myA1 = 0.9,          !- A4

ELSEIF (SurfaceFraction >= 0.3) && (SurfaceFraction < 0.8),  !- A5

SET myA1 = 0.4,          !- A6

ELSE,                    !- A7

SET myA1 = 0.1 ,           !- A8

ENDIF;                   !- A9

EnergyManagementSystem:GlobalVariable,

myglobeA1;               !- Erl Variable 1 Name

EnergyManagementSystem:OutputVariable,

Weighted Shade Fraction Schedule,  !- Name

myglobeA1,               !- EMS Variable Name

Averaged,                !- Type of Data in Variable

SystemTimestep;          !- Update Frequency

But, when I see the results, everyday I obtain a strange number out of the ranges I defined with EMS in the beginning and ending hour of the daytime.

image description

Did I do sth wrong in the definition?

Regards Amir

Dear Raphael,

I followed your suggestion, but there is something strange within the evaluated schedule after applying EMS coding on the transparency shading schedule.

As you see here I defined three ranges to control the shading transparency based on the 'Surface Outdoor Face Sunlit Fraction' which in my case I selected the external window surface as a sample.

EnergyManagementSystem:Sensor,

S1,                      !- Name

zone_0_Srf_0_glz_0,      !- Output:Variable or Output:Meter Index Key Name

Surface Outside Face Sunlit Fraction ;  !- Output:Variable or Output:Meter Name

EnergyManagementSystem:Actuator,

myA1,                    !- Name

ASF,                     !- Actuated Component Unique Name

Schedule:Year,           !- Actuated Component Type

Schedule Value;          !- Actuated Component Control Type

EnergyManagementSystem:ProgramCallingManager,

MyComputedTransProg,     !- Name

BeginTimestepBeforePredictor,  !- EnergyPlus Model Calling Point

MyComputedTransSch;      !- Program Name 1

EnergyManagementSystem:Program,

MyComputedTransSch,      !- Name

Set SurfaceFraction = S1,!- Program Line 1

IF SurfaceFraction < 0.3,!- Program Line 2

SET myA1 = 0.9,          !- A4

ELSEIF (SurfaceFraction >= 0.3) && (SurfaceFraction < 0.8),  !- A5

SET myA1 = 0.4,          !- A6

ELSE,                    !- A7

SET myA1 = 0.1 ,           !- A8

ENDIF;                   !- A9

EnergyManagementSystem:GlobalVariable,

myglobeA1;               !- Erl Variable 1 Name

EnergyManagementSystem:OutputVariable,

Weighted Shade Fraction Schedule,  !- Name

myglobeA1,               !- EMS Variable Name

Averaged,                !- Type of Data in Variable

SystemTimestep;          !- Update Frequency

But, when I see the results, everyday I obtain a strange number out of the ranges I defined for Transparency SCH with EMS in the beginning and ending hour of the daytime.

image description

Did I do sth wrong in the definition?

Regards Amir

Dear Raphael,

I followed your suggestion, but there is something strange within the evaluated schedule after applying EMS coding on the transparency shading schedule.

As you see here I defined three ranges to control the shading transparency based on the 'Surface Outdoor Face Sunlit Fraction' which in my case I selected the external window surface as a sample.

EnergyManagementSystem:Sensor,

S1,                      !- Name

zone_0_Srf_0_glz_0,      !- Output:Variable or Output:Meter Index Key Name

Surface Outside Face Sunlit Fraction ;  !- Output:Variable or Output:Meter Name

EnergyManagementSystem:Actuator,

myA1,                    !- Name

ASF,                     !- Actuated Component Unique Name

Schedule:Year,           !- Actuated Component Type

Schedule Value;          !- Actuated Component Control Type

EnergyManagementSystem:ProgramCallingManager,

MyComputedTransProg,     !- Name

BeginTimestepBeforePredictor,  !- EnergyPlus Model Calling Point

MyComputedTransSch;      !- Program Name 1

EnergyManagementSystem:Program,

MyComputedTransSch,      !- Name

Set SurfaceFraction = S1,!- Program Line 1

IF SurfaceFraction < 0.3,!- Program Line 2

SET myA1 = 0.9,          !- A4

ELSEIF (SurfaceFraction >= 0.3) && (SurfaceFraction < 0.8),  !- A5

SET myA1 = 0.4,          !- A6

ELSE,                    !- A7

SET myA1 = 0.1 ,           !- A8

ENDIF;                   !- A9

EnergyManagementSystem:GlobalVariable,

myglobeA1;               !- Erl Variable 1 Name

EnergyManagementSystem:OutputVariable,

Weighted Shade Fraction Schedule,  !- Name

myglobeA1,               !- EMS Variable Name

Averaged,                !- Type of Data in Variable

SystemTimestep;          !- Update Frequency

But, when I see the results, everyday I obtain a strange number numbers out of the ranges I defined for Transparency SCH with EMS in the beginning and ending hour of the daytime. Like in below I got 0.76666 and 0.3666 for which based on my definition in EMS-Program and sunlit fractions must be 0.9 and 0.1 respectively.

image description

Did I do sth wrong in the definition?

Regards Amir

Dear Raphael,

I followed your suggestion, but there is something strange within the evaluated schedule after applying EMS coding on the transparency shading schedule.

As you see here I defined three ranges to control the shading transparency based on the 'Surface Outdoor Face Sunlit Fraction' which in my case I selected the external window surface as a sample.

EnergyManagementSystem:Sensor,

S1,                      !- Name

zone_0_Srf_0_glz_0,      !- Output:Variable or Output:Meter Index Key Name

Surface Outside Face Sunlit Fraction ;  !- Output:Variable or Output:Meter Name

EnergyManagementSystem:Actuator,

myA1,                    !- Name

ASF,                     !- Actuated Component Unique Name

Schedule:Year,           !- Actuated Component Type

Schedule Value;          !- Actuated Component Control Type

EnergyManagementSystem:ProgramCallingManager,

MyComputedTransProg,     !- Name

BeginTimestepBeforePredictor,  !- EnergyPlus Model Calling Point

MyComputedTransSch;      !- Program Name 1

EnergyManagementSystem:Program,

MyComputedTransSch,      !- Name

Set SurfaceFraction = S1,!- Program Line 1

IF SurfaceFraction < 0.3,!- Program Line 2

SET myA1 = 0.9,          !- A4

ELSEIF (SurfaceFraction >= 0.3) && (SurfaceFraction < 0.8),  !- A5

SET myA1 = 0.4,          !- A6

ELSE,                    !- A7

SET myA1 = 0.1 ,           !- A8

ENDIF;                   !- A9

EnergyManagementSystem:GlobalVariable,

myglobeA1;               !- Erl Variable 1 Name

EnergyManagementSystem:OutputVariable,

Weighted Shade Fraction Schedule,  !- Name

myglobeA1,               !- EMS Variable Name

Averaged,                !- Type of Data in Variable

SystemTimestep;          !- Update Frequency

But, when I see the results, everyday I obtain a strange numbers out of the ranges I defined for Transparency SCH with EMS in the beginning and ending hour of the daytime. Like in below I got 0.76666 and 0.3666 for 0.3666, which based on my definition in EMS-Program and sunlit fractions must be 0.9 and 0.1 respectively.

image description

Did I do sth wrong in the definition?

Regards Amir

Dear Raphael,

I followed your suggestion, but there is something strange within the evaluated schedule after applying EMS coding on the transparency shading schedule.

As you see here I defined three ranges to control the shading transparency based on the 'Surface Outdoor Face Sunlit Fraction' which in my case I selected the external window surface as a sample.

EnergyManagementSystem:Sensor,

EnergyManagementSystem:Sensor,
  S1,                      !- Name
  zone_0_Srf_0_glz_0,      !- Output:Variable or Output:Meter Index Key Name
  Surface Outside Face Sunlit Fraction ;  !- Output:Variable or Output:Meter Name

EnergyManagementSystem:Actuator,


EnergyManagementSystem:Actuator,
  myA1,                    !- Name
  ASF,                     !- Actuated Component Unique Name
  Schedule:Year,           !- Actuated Component Type
  Schedule Value;          !- Actuated Component Control Type

EnergyManagementSystem:ProgramCallingManager,


EnergyManagementSystem:ProgramCallingManager,
  MyComputedTransProg,     !- Name
  BeginTimestepBeforePredictor,  !- EnergyPlus Model Calling Point
  MyComputedTransSch;      !- Program Name 1

EnergyManagementSystem:Program,


EnergyManagementSystem:Program,
  MyComputedTransSch,      !- Name
  Set SurfaceFraction = S1,!- Program Line 1
  IF SurfaceFraction < 0.3,!- Program Line 2
  SET myA1 = 0.9,          !- A4
  ELSEIF (SurfaceFraction >= 0.3) && (SurfaceFraction < 0.8),  !- A5
  SET myA1 = 0.4,          !- A6
  ELSE,                    !- A7
  SET myA1 = 0.1 ,           !- A8
  ENDIF;                   !- A9

EnergyManagementSystem:GlobalVariable,


EnergyManagementSystem:GlobalVariable,
  myglobeA1;               !- Erl Variable 1 Name

EnergyManagementSystem:OutputVariable,


EnergyManagementSystem:OutputVariable,
  Weighted Shade Fraction Schedule,  !- Name
  myglobeA1,               !- EMS Variable Name
  Averaged,                !- Type of Data in Variable
  SystemTimestep;          !- Update Frequency

But, when I see the results, everyday I obtain a strange numbers out of the ranges I defined for Transparency SCH with EMS in the beginning and ending hour of the daytime. Like in below I got 0.76666 and 0.3666, which based on my definition in EMS-Program and sunlit fractions must be 0.9 and 0.1 respectively.

image description

Did I do sth wrong in the definition?

Regards Amir