The templates are there to set up the node names for the plants and air loops.
If you look at the expIDF, the thermostat is expanded into zone notes, zone thermostat schedules. The zone unitry is expanded to provide the damper (Air terminal uncontrolled) The system unitary is expanded into the OA mixder box, heating and cooling coils, fan, primary air loop, zone splitter, zone mixer, zone sizing, etc.
What component you get, depends on how you choose the options in the templates.
If you choose no heating in the system template, the heating coil would not be provided.
On the control of zone temperature, the template generates Type 4 as default, if you do not choose to have Summer and Winter seasons.
With the Type 4 theremostat control type, you do have the htg_setpoint_sch and Clg_setpoint_Sch. At pressent, these two schecule has a constant value of 25 for Summer and 20 for Winter. You can have one of these schedule per zone, and for different day types. For Summer, the night time setpoint can be increased say to 35°C. This would keep the system off. If you keep the temperature high for the whole day, you will see the PMV value varies as the zone temperature changes.
If you are not changing the system to Winter/Summer mode, it is not necessary to change the thermostat control type to type 2.
HVACTemplate:Thermostat,
Termostato, !- Name
Htg_Sch_temp, !- Heating Setpoint Schedule Name
20, !- Constant Heating Setpoint {C}
Clg_Sch_temp1, !- Cooling Setpoint Schedule Name
25; !- Constant Cooling Setpoint {C}
When a schedule name is provided, the number following is ignored.
Schedule:Compact,
Htg_Sch_temp, !- Name
Temperature, !- Schedule Type Limits Name
Through: 12/31, !- Field 1
For: alldays, !- Field 2
Until:24:00, 20; !- Field 4
Schedule:Compact,
Clg_Sch_temp1, !- Name
Temperature, !- Schedule Type Limits Name
Through: 12/31, !- Field 1
For: alldays, !- Field 2
Uniil:06:00, 35,
Uniil:08:00, 30,
Uniil:17:00, 25,
Uniil:20:00, 30,
Until:24:00, 35; !- Field 4
You should have the above declared with the zone theremostat and zone unitary. The same name Termostato is used for all zones. If you have different thermostat names for different zones, then all the set point values can be different.
HVACTemplate:System:Unitary,
Sistema Piso 1, !- Name
Sch_Equip, !- System Availability Schedule Name
411655, !- Control Zone or Thermostat Location Name
autosize, !- Supply Fan Maximum Flow Rate {m3/s}
Sch_Equip, !- Supply Fan Operating Mode Schedule Name
0.7, !- Supply Fan Total Efficiency
.....
.....;
In your case, because there is only one zone per system, the zone name is the master zone. The theremostat in that zone will control the system operation. Each zone may have a common or different schedule.
! HVACTemplate:Thermostat,
! Constant Setpoint Thermostat, !- Name
! , !- Heating Setpoint Schedule Name
! 20, !- Constant Heating Setpoint {C}
! , !- Cooling Setpoint Schedule Name
! 25; !- Constant Cooling Setpoint {C}
You had that in your IDF. Are you still using this format?
! -------------------------------------------------------------
! New objects created from ExpandObjects
! -------------------------------------------------------------
!
ScheduleTypeLimits,
HVACTemplate Any Number; !- Name
!- ===== The following defines the type to use. and links to your schedules
ThermostatSetpoint:DualSetpoint,
Termostato Dual SP Control, !- Name
Htg_Sch_temp, !- Heating Setpoint Temperature Schedule Name
Clg_Sch_temp; !- Cooling Setpoint Temperature Schedule Name
!- ============== These two were added by the template
Schedule:Compact,
HVACTemplate-Always 1, !- Name
HVACTemplate Any Number, !- Schedule Type Limits Name
Through: 12/31, !- Field 1
For: AllDays, !- Field 2
Until: 24:00, !- Field 3
1; !- Field 4
Schedule:Compact,
HVACTemplate-Always 4, !- Name
HVACTemplate Any Number, !- Schedule Type Limits Name
Through: 12/31, !- Field 1
For: AllDays, !- Field 2
Until: 24:00, !- Field 3
4; !- Field 4
ZoneControl:Thermostat,
411655 Thermostat, !- Name
411655, !- Zone or ZoneList Name
HVACTemplate-Always 4, !- Control Type Schedule Name (this is where you change to Tpe 2)
ThermostatSetpoint:DualSetpoint, !- Control Object Type ( cooling only)
Termostato Dual SP Control; !- Control Name ( a different name with cooling only.)
!- ========= This last line links to your htg and clg setpoints schedules through the object on top..
You can try removing the heating electricity field in the template and see whether the template will change accordinglyu. If you change this manually in the expIDF, you cannot go back to use the template version.
Dr. Li
To: EnergyPlus_Support@xxxxxxxxxxxxxxx
From: barth.poker@xxxxxxxxxxxx
Date: Thu, 5 Jul 2012 13:12:47 +0000
Subject: [EnergyPlus_Support] Re: Too many vertices
__._,_.___
Primary EnergyPlus support is found at:
http://energyplus.helpserve.com or send a message to energyplus-support@xxxxxxxx
The primary EnergyPlus web site is found at:
http://www.energyplus.gov
The group web site is:
http://groups.yahoo.com/group/EnergyPlus_Support/
Attachments are currently allowed but be mindful that not everyone has a high speed connection. Limit attachments to small files.
EnergyPlus Documentation is searchable. Open EPlusMainMenu.pdf under the Documentation link and press the "search" button.
![]()
__,_._,___
If you look at the expIDF, the thermostat is expanded into zone notes, zone thermostat schedules. The zone unitry is expanded to provide the damper (Air terminal uncontrolled) The system unitary is expanded into the OA mixder box, heating and cooling coils, fan, primary air loop, zone splitter, zone mixer, zone sizing, etc.
What component you get, depends on how you choose the options in the templates.
If you choose no heating in the system template, the heating coil would not be provided.
On the control of zone temperature, the template generates Type 4 as default, if you do not choose to have Summer and Winter seasons.
With the Type 4 theremostat control type, you do have the htg_setpoint_sch and Clg_setpoint_Sch. At pressent, these two schecule has a constant value of 25 for Summer and 20 for Winter. You can have one of these schedule per zone, and for different day types. For Summer, the night time setpoint can be increased say to 35°C. This would keep the system off. If you keep the temperature high for the whole day, you will see the PMV value varies as the zone temperature changes.
If you are not changing the system to Winter/Summer mode, it is not necessary to change the thermostat control type to type 2.
HVACTemplate:Thermostat,
Termostato, !- Name
Htg_Sch_temp, !- Heating Setpoint Schedule Name
20, !- Constant Heating Setpoint {C}
Clg_Sch_temp1, !- Cooling Setpoint Schedule Name
25; !- Constant Cooling Setpoint {C}
When a schedule name is provided, the number following is ignored.
Schedule:Compact,
Htg_Sch_temp, !- Name
Temperature, !- Schedule Type Limits Name
Through: 12/31, !- Field 1
For: alldays, !- Field 2
Until:24:00, 20; !- Field 4
Schedule:Compact,
Clg_Sch_temp1, !- Name
Temperature, !- Schedule Type Limits Name
Through: 12/31, !- Field 1
For: alldays, !- Field 2
Uniil:06:00, 35,
Uniil:08:00, 30,
Uniil:17:00, 25,
Uniil:20:00, 30,
Until:24:00, 35; !- Field 4
You should have the above declared with the zone theremostat and zone unitary. The same name Termostato is used for all zones. If you have different thermostat names for different zones, then all the set point values can be different.
HVACTemplate:System:Unitary,
Sistema Piso 1, !- Name
Sch_Equip, !- System Availability Schedule Name
411655, !- Control Zone or Thermostat Location Name
autosize, !- Supply Fan Maximum Flow Rate {m3/s}
Sch_Equip, !- Supply Fan Operating Mode Schedule Name
0.7, !- Supply Fan Total Efficiency
.....
.....;
In your case, because there is only one zone per system, the zone name is the master zone. The theremostat in that zone will control the system operation. Each zone may have a common or different schedule.
! HVACTemplate:Thermostat,
! Constant Setpoint Thermostat, !- Name
! , !- Heating Setpoint Schedule Name
! 20, !- Constant Heating Setpoint {C}
! , !- Cooling Setpoint Schedule Name
! 25; !- Constant Cooling Setpoint {C}
You had that in your IDF. Are you still using this format?
! -------------------------------------------------------------
! New objects created from ExpandObjects
! -------------------------------------------------------------
!
ScheduleTypeLimits,
HVACTemplate Any Number; !- Name
!- ===== The following defines the type to use. and links to your schedules
ThermostatSetpoint:DualSetpoint,
Termostato Dual SP Control, !- Name
Htg_Sch_temp, !- Heating Setpoint Temperature Schedule Name
Clg_Sch_temp; !- Cooling Setpoint Temperature Schedule Name
!- ============== These two were added by the template
Schedule:Compact,
HVACTemplate-Always 1, !- Name
HVACTemplate Any Number, !- Schedule Type Limits Name
Through: 12/31, !- Field 1
For: AllDays, !- Field 2
Until: 24:00, !- Field 3
1; !- Field 4
Schedule:Compact,
HVACTemplate-Always 4, !- Name
HVACTemplate Any Number, !- Schedule Type Limits Name
Through: 12/31, !- Field 1
For: AllDays, !- Field 2
Until: 24:00, !- Field 3
4; !- Field 4
ZoneControl:Thermostat,
411655 Thermostat, !- Name
411655, !- Zone or ZoneList Name
HVACTemplate-Always 4, !- Control Type Schedule Name (this is where you change to Tpe 2)
ThermostatSetpoint:DualSetpoint, !- Control Object Type ( cooling only)
Termostato Dual SP Control; !- Control Name ( a different name with cooling only.)
!- ========= This last line links to your htg and clg setpoints schedules through the object on top..
You can try removing the heating electricity field in the template and see whether the template will change accordinglyu. If you change this manually in the expIDF, you cannot go back to use the template version.
Dr. Li
To: EnergyPlus_Support@xxxxxxxxxxxxxxx
From: barth.poker@xxxxxxxxxxxx
Date: Thu, 5 Jul 2012 13:12:47 +0000
Subject: [EnergyPlus_Support] Re: Too many vertices
I mentioned the pmv e pdd because when the temperature was not regulated, the values from them was out of range for confort of the the people, obviously. Our goal mostly is to simulate the same building and see what is the thermic load in kWh that the bulding needs, because students are complaing about how hot is there sometimes.
When the thermostat start the "kick in", the pmv and ppd began to stay at that certain range -1<pmv<1, pdd<10. Witch is great, but if you make the graphics you will see that the temperature e these coefficients seems to follow the occupaion schedule. May be a missleading information, i dont know.
Is it a easy way to trasnform my thermostat witch is type 4 (cooling and heating with deadband) to type 2?
because the way that the simualtion was built, the thermostat dosent follow any schedule, just a setpoint in C for cooling and heating. It is an object on Hvac template.
Can i make a schedule either way?
--- In EnergyPlus_Support@xxxxxxxxxxxxxxx, YuanLu Li <yli006@...> wrote:
>
>
>
> I did not know that you are in such a rush. The building geometry is fine. Just let your professor know, that the calculation of shade has many different algorithms. The warning simply let you know that some of the reflections may not be calculated. As these reflections are all outside the building, it will not affect the building heat load very much. All you need to watch is that the solar beam direct component is excluded using the window shades. The beam value for each window can be displayed in your .csv. "too many vertices" may also be produce by some third party software. This can be ignored, if they are all for the external shades. Those I have looked at are all with 4 vertices. One reason is the use of the long decimal numbers in the data entry. The third party software adds extra small areas between the shade and the window or wall. If this is the case, you may declare the shades as detached shades and remove these small area. Heating load is zero is a warning to you so that you need not provide heating in the system. As your thermostat is Type 4, and heating equipment is available, the warnings are given. With type 4 thermostat control, the equipment is left on all the time so that the transiion period may have both heating and cooling. This is done using the availability schedule. The thermostat is the temperature schedule. The Thermostat heating and cooling are controlled by the two band values. The dead band makes sure that the heating and cooling would not come on at the same time. If you remove the heating equipment for the x and y zones, the warning should disappear. You may also need to change the thermostat type to type 2 for cooling only. Because you are using templates for input, this may cause a problem in the entry. It is simpler to ignore the warning and provide a reason. The internal load usually increases the zone temperature making the heating not necessary and therefore the no heating load warning. If you remove the people, lights, etc. the warning may disappear. This is just to show that the warnings are good and not performance or design errors. PMV, PPD's are all post-processing according to the comfort rules. If you use natural ventilation and in tropical countries, they do not have much meaning. Dr. Li
> To: EnergyPlus_Support@xxxxxxxxxxxxxxx
> From: barth.poker@...
> Date: Wed, 4 Jul 2012 18:38:41 +0000
> Subject: [EnergyPlus_Support] Re: Too many vertices
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Hi Dr. Li
>
>
>
> I have just now read your email..
>
> Im not quite sure but, as you say when that schedule turns 0 or "Cycling" it seems that it turns on right in time as the Ocupation Schedule. Because the temperature is controled when have people inside the envelope, and the coefficients pmv and ppd follow that in the graphics.
>
> So, i decide that it works for me that way, so i did not change anything yet.
>
> But, im giving this to my professor as an research job, and i wanted to closed this 3 warnings that remains.
>
>
>
> 2 of that says that heat loads of X and Y zones are zero. (witch i expected)
>
>
>
> and 1 of them is this one of too many vertices.
>
>
>
> I still didnt figured out how to exclude that, only by deleting the faces.
>
>
>
> I wish i could just fixed that 3 warnings.
>
>
>
> --- In EnergyPlus_Support@xxxxxxxxxxxxxxx, YuanLu Li <yli006@> wrote:
>
> >
>
> >
>
> > Hi, Douglas and Linda I ran his IDF using DD sizing and the error file is attached. The external shading are for window boxes. I think, the warnings can be ignored. The vertical fins are very close between windows. Only the adjacent ones overlap. There is one box for each window. The total number is quite large.
>
> >
>
> > Because the Winter is mild, the heating was not required for some zones. Therefore, the warning can also be ignored. The error reporting seems to be different for tha weather file and sizing simulation. The warnings are summarized in my error file rather than listed one at a time. "DoNotMirrorDetachedShading, " was suggested in an earlier error file, and I have this included in the IDF Diagnostic object. I have sent the IDF I used to Douglas. He also had a question on Fan mode schedule. I have not yet heard from him on the detailed change he made. The compact schedule for fan mode was the as as that for other equipment. 0 for night time and 1 for day time. I told him that the mode and on/off may not be the same, but should not stop the system frm running. Dr. Li
>
> > To: EnergyPlus_Support@xxxxxxxxxxxxxxx
>
> > From: linda@
>
> > Date: Wed, 4 Jul 2012 08:39:25 -0600
>
> > Subject: Re: [EnergyPlus_Support] Too many vertices
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> > What does your ShadowCalculation object look like?
>
> >
>
> >
>
> > The 2nd field in that object sets the number of figures in a shadow
>
> > overlap but maybe this is a different detection.
>
> >
>
> > Feel free to send your input file to the helpdesk for further analysis or
>
> > alleviation of this warning, if possible.
>
> >
>
> >
>
> >
>
> >
>
> > At 08:31 AM 7/4/2012, barth.poker wrote:
>
> >
>
> > Hi guys, my simulation was
>
> > giving and overlapping shadow warnings wicth i corrected.
>
> >
>
> > But, Now is displaying this warning:
>
> >
>
> >
>
> > "Too many vertices [>=12] in a shadow overlap"
>
> >
>
> >
>
> > and then it told me to run the ExtraWarnings for more
>
> > information
>
> >
>
> >
>
> > and this came up:
>
> >
>
> > " ** Warning ** Too many vertices [>=12] in a shadow overlap
>
> >
>
> > ** ~~~ ** Overlapping figure=3965AF,
>
> > Surface Class=[Detached Shading:Building]
>
> >
>
> > ** ~~~ ** This error
>
> > occurred 1 times.
>
> >
>
> > ** ~~~ ** Figure being
>
> > Overlapped=79BA0A, Surface Class=[Detached Shading:Building]
>
> >
>
> > *************
>
> >
>
> > ** Warning ** Too many vertices [>=12] in a shadow
>
> > overlap
>
> >
>
> > ** ~~~ ** Overlapping figure=E7C01A,
>
> > Surface Class=[Detached Shading:Building]
>
> >
>
> > ** ~~~ ** This error
>
> > occurred 1 times.
>
> >
>
> > ** ~~~ ** Figure being
>
> > Overlapped=4F4431, Surface Class=[Detached Shading:Building]
>
> >
>
> > *************
>
> >
>
> > ** Warning ** Too many vertices [>=12] in a shadow
>
> > overlap
>
> >
>
> > ** ~~~ ** Overlapping figure=E3C3A1,
>
> > Surface Class=[Detached Shading:Building]
>
> >
>
> > ** ~~~ ** This error
>
> > occurred 1 times.
>
> >
>
> > ** ~~~ ** Figure being
>
> > Overlapped=D611AE, Surface Class=[Detached Shading:Building]
>
> >
>
> > *************
>
> >
>
> > ** Warning ** Too many vertices [>=12] in a shadow
>
> > overlap
>
> >
>
> > ** ~~~ ** Overlapping figure=E942EA,
>
> > Surface Class=[Detached Shading:Building]
>
> >
>
> > ** ~~~ ** This error
>
> > occurred 1 times.
>
> >
>
> > ** ~~~ ** Figure being
>
> > Overlapped=E21B91, Surface Class=[Detached Shading:Building]
>
> >
>
> > *************
>
> >
>
> > ** Warning ** Too many vertices [>=12] in a shadow
>
> > overlap
>
> >
>
> > ** ~~~ ** Overlapping figure=5578E7,
>
> > Surface Class=[Detached Shading:Building]
>
> >
>
> > ** ~~~ ** This error
>
> > occurred 1 times.
>
> >
>
> > ** ~~~ ** Figure being
>
> > Overlapped=3534EE, Surface Class=[Detached Shading:Building]
>
> >
>
> > *************
>
> >
>
> > ** Warning ** Too many vertices [>=12] in a shadow
>
> > overlap
>
> >
>
> > ** ~~~ ** Overlapping figure=376846,
>
> > Surface Class=[Detached Shading:Building]
>
> >
>
> > ** ~~~ ** This error
>
> > occurred 1 times.
>
> >
>
> > ** ~~~ ** Figure being
>
> > Overlapped=79BA0A, Surface Class=[Detached
>
> > Shading:Building]"
>
> >
>
> >
>
> > and i looked the shd file and it seems that is nothing i can do about
>
> > it
>
> >
>
> >
>
> > Is a solution for this? Or some way the i could ignore this
>
> > warning?
>
> >
>
> >
>
> >
>
> >
>
> >
>
> > ------------------------------------
>
> >
>
> >
>
> > Primary EnergyPlus support is found at:
>
> >
>
> >
>
> > http://energyplus.helpserve.com or send a message to
>
> > energyplus-support@
>
> >
>
> >
>
> > The primary EnergyPlus web site is found at:
>
> >
>
> >
>
> > http://www.energyplus.gov
>
> >
>
> >
>
> > The group web site is:
>
> >
>
> >
>
> > http://groups.yahoo.com/group/EnergyPlus_Support/
>
> >
>
> >
>
> > Attachments are currently allowed but be mindful that not everyone has a
>
> > high speed connection. Limit attachments to small files.
>
> >
>
> >
>
> > EnergyPlus Documentation is searchable. Open EPlusMainMenu.pdf
>
> > under the Documentation link and press the "search"
>
> > button.
>
> >
>
> > Yahoo! Groups Links
>
> >
>
> >
>
> >
>
> >
>
> > http://groups.yahoo.com/group/EnergyPlus_Support/
>
> >
>
> >
>
> > Individual Email | Traditional
>
> >
>
> >
>
> >
>
> >
>
> > http://groups.yahoo.com/group/EnergyPlus_Support/join
>
> >
>
> > (Yahoo! ID required)
>
> >
>
> >
>
> > EnergyPlus_Support-digest@xxxxxxxxxxxxxxx
>
> >
>
> >
>
> > EnergyPlus_Support-fullfeatured@xxxxxxxxxxxxxxx
>
> >
>
> >
>
> >
>
> > EnergyPlus_Support-unsubscribe@xxxxxxxxxxxxxxx
>
> >
>
> >
>
> >
>
> >
>
> > http://docs.yahoo.com/info/terms/
>
> >
>
When the thermostat start the "kick in", the pmv and ppd began to stay at that certain range -1<pmv<1, pdd<10. Witch is great, but if you make the graphics you will see that the temperature e these coefficients seems to follow the occupaion schedule. May be a missleading information, i dont know.
Is it a easy way to trasnform my thermostat witch is type 4 (cooling and heating with deadband) to type 2?
because the way that the simualtion was built, the thermostat dosent follow any schedule, just a setpoint in C for cooling and heating. It is an object on Hvac template.
Can i make a schedule either way?
--- In EnergyPlus_Support@xxxxxxxxxxxxxxx, YuanLu Li <yli006@...> wrote:
>
>
>
> I did not know that you are in such a rush. The building geometry is fine. Just let your professor know, that the calculation of shade has many different algorithms. The warning simply let you know that some of the reflections may not be calculated. As these reflections are all outside the building, it will not affect the building heat load very much. All you need to watch is that the solar beam direct component is excluded using the window shades. The beam value for each window can be displayed in your .csv. "too many vertices" may also be produce by some third party software. This can be ignored, if they are all for the external shades. Those I have looked at are all with 4 vertices. One reason is the use of the long decimal numbers in the data entry. The third party software adds extra small areas between the shade and the window or wall. If this is the case, you may declare the shades as detached shades and remove these small area. Heating load is zero is a warning to you so that you need not provide heating in the system. As your thermostat is Type 4, and heating equipment is available, the warnings are given. With type 4 thermostat control, the equipment is left on all the time so that the transiion period may have both heating and cooling. This is done using the availability schedule. The thermostat is the temperature schedule. The Thermostat heating and cooling are controlled by the two band values. The dead band makes sure that the heating and cooling would not come on at the same time. If you remove the heating equipment for the x and y zones, the warning should disappear. You may also need to change the thermostat type to type 2 for cooling only. Because you are using templates for input, this may cause a problem in the entry. It is simpler to ignore the warning and provide a reason. The internal load usually increases the zone temperature making the heating not necessary and therefore the no heating load warning. If you remove the people, lights, etc. the warning may disappear. This is just to show that the warnings are good and not performance or design errors. PMV, PPD's are all post-processing according to the comfort rules. If you use natural ventilation and in tropical countries, they do not have much meaning. Dr. Li
> To: EnergyPlus_Support@xxxxxxxxxxxxxxx
> From: barth.poker@...
> Date: Wed, 4 Jul 2012 18:38:41 +0000
> Subject: [EnergyPlus_Support] Re: Too many vertices
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Hi Dr. Li
>
>
>
> I have just now read your email..
>
> Im not quite sure but, as you say when that schedule turns 0 or "Cycling" it seems that it turns on right in time as the Ocupation Schedule. Because the temperature is controled when have people inside the envelope, and the coefficients pmv and ppd follow that in the graphics.
>
> So, i decide that it works for me that way, so i did not change anything yet.
>
> But, im giving this to my professor as an research job, and i wanted to closed this 3 warnings that remains.
>
>
>
> 2 of that says that heat loads of X and Y zones are zero. (witch i expected)
>
>
>
> and 1 of them is this one of too many vertices.
>
>
>
> I still didnt figured out how to exclude that, only by deleting the faces.
>
>
>
> I wish i could just fixed that 3 warnings.
>
>
>
> --- In EnergyPlus_Support@xxxxxxxxxxxxxxx, YuanLu Li <yli006@> wrote:
>
> >
>
> >
>
> > Hi, Douglas and Linda I ran his IDF using DD sizing and the error file is attached. The external shading are for window boxes. I think, the warnings can be ignored. The vertical fins are very close between windows. Only the adjacent ones overlap. There is one box for each window. The total number is quite large.
>
> >
>
> > Because the Winter is mild, the heating was not required for some zones. Therefore, the warning can also be ignored. The error reporting seems to be different for tha weather file and sizing simulation. The warnings are summarized in my error file rather than listed one at a time. "DoNotMirrorDetachedShading, " was suggested in an earlier error file, and I have this included in the IDF Diagnostic object. I have sent the IDF I used to Douglas. He also had a question on Fan mode schedule. I have not yet heard from him on the detailed change he made. The compact schedule for fan mode was the as as that for other equipment. 0 for night time and 1 for day time. I told him that the mode and on/off may not be the same, but should not stop the system frm running. Dr. Li
>
> > To: EnergyPlus_Support@xxxxxxxxxxxxxxx
>
> > From: linda@
>
> > Date: Wed, 4 Jul 2012 08:39:25 -0600
>
> > Subject: Re: [EnergyPlus_Support] Too many vertices
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> > What does your ShadowCalculation object look like?
>
> >
>
> >
>
> > The 2nd field in that object sets the number of figures in a shadow
>
> > overlap but maybe this is a different detection.
>
> >
>
> > Feel free to send your input file to the helpdesk for further analysis or
>
> > alleviation of this warning, if possible.
>
> >
>
> >
>
> >
>
> >
>
> > At 08:31 AM 7/4/2012, barth.poker wrote:
>
> >
>
> > Hi guys, my simulation was
>
> > giving and overlapping shadow warnings wicth i corrected.
>
> >
>
> > But, Now is displaying this warning:
>
> >
>
> >
>
> > "Too many vertices [>=12] in a shadow overlap"
>
> >
>
> >
>
> > and then it told me to run the ExtraWarnings for more
>
> > information
>
> >
>
> >
>
> > and this came up:
>
> >
>
> > " ** Warning ** Too many vertices [>=12] in a shadow overlap
>
> >
>
> > ** ~~~ ** Overlapping figure=3965AF,
>
> > Surface Class=[Detached Shading:Building]
>
> >
>
> > ** ~~~ ** This error
>
> > occurred 1 times.
>
> >
>
> > ** ~~~ ** Figure being
>
> > Overlapped=79BA0A, Surface Class=[Detached Shading:Building]
>
> >
>
> > *************
>
> >
>
> > ** Warning ** Too many vertices [>=12] in a shadow
>
> > overlap
>
> >
>
> > ** ~~~ ** Overlapping figure=E7C01A,
>
> > Surface Class=[Detached Shading:Building]
>
> >
>
> > ** ~~~ ** This error
>
> > occurred 1 times.
>
> >
>
> > ** ~~~ ** Figure being
>
> > Overlapped=4F4431, Surface Class=[Detached Shading:Building]
>
> >
>
> > *************
>
> >
>
> > ** Warning ** Too many vertices [>=12] in a shadow
>
> > overlap
>
> >
>
> > ** ~~~ ** Overlapping figure=E3C3A1,
>
> > Surface Class=[Detached Shading:Building]
>
> >
>
> > ** ~~~ ** This error
>
> > occurred 1 times.
>
> >
>
> > ** ~~~ ** Figure being
>
> > Overlapped=D611AE, Surface Class=[Detached Shading:Building]
>
> >
>
> > *************
>
> >
>
> > ** Warning ** Too many vertices [>=12] in a shadow
>
> > overlap
>
> >
>
> > ** ~~~ ** Overlapping figure=E942EA,
>
> > Surface Class=[Detached Shading:Building]
>
> >
>
> > ** ~~~ ** This error
>
> > occurred 1 times.
>
> >
>
> > ** ~~~ ** Figure being
>
> > Overlapped=E21B91, Surface Class=[Detached Shading:Building]
>
> >
>
> > *************
>
> >
>
> > ** Warning ** Too many vertices [>=12] in a shadow
>
> > overlap
>
> >
>
> > ** ~~~ ** Overlapping figure=5578E7,
>
> > Surface Class=[Detached Shading:Building]
>
> >
>
> > ** ~~~ ** This error
>
> > occurred 1 times.
>
> >
>
> > ** ~~~ ** Figure being
>
> > Overlapped=3534EE, Surface Class=[Detached Shading:Building]
>
> >
>
> > *************
>
> >
>
> > ** Warning ** Too many vertices [>=12] in a shadow
>
> > overlap
>
> >
>
> > ** ~~~ ** Overlapping figure=376846,
>
> > Surface Class=[Detached Shading:Building]
>
> >
>
> > ** ~~~ ** This error
>
> > occurred 1 times.
>
> >
>
> > ** ~~~ ** Figure being
>
> > Overlapped=79BA0A, Surface Class=[Detached
>
> > Shading:Building]"
>
> >
>
> >
>
> > and i looked the shd file and it seems that is nothing i can do about
>
> > it
>
> >
>
> >
>
> > Is a solution for this? Or some way the i could ignore this
>
> > warning?
>
> >
>
> >
>
> >
>
> >
>
> >
>
> > ------------------------------------
>
> >
>
> >
>
> > Primary EnergyPlus support is found at:
>
> >
>
> >
>
> > http://energyplus.helpserve.com or send a message to
>
> > energyplus-support@
>
> >
>
> >
>
> > The primary EnergyPlus web site is found at:
>
> >
>
> >
>
> > http://www.energyplus.gov
>
> >
>
> >
>
> > The group web site is:
>
> >
>
> >
>
> > http://groups.yahoo.com/group/EnergyPlus_Support/
>
> >
>
> >
>
> > Attachments are currently allowed but be mindful that not everyone has a
>
> > high speed connection. Limit attachments to small files.
>
> >
>
> >
>
> > EnergyPlus Documentation is searchable. Open EPlusMainMenu.pdf
>
> > under the Documentation link and press the "search"
>
> > button.
>
> >
>
> > Yahoo! Groups Links
>
> >
>
> >
>
> >
>
> >
>
> > http://groups.yahoo.com/group/EnergyPlus_Support/
>
> >
>
> >
>
> > Individual Email | Traditional
>
> >
>
> >
>
> >
>
> >
>
> > http://groups.yahoo.com/group/EnergyPlus_Support/join
>
> >
>
> > (Yahoo! ID required)
>
> >
>
> >
>
> > EnergyPlus_Support-digest@xxxxxxxxxxxxxxx
>
> >
>
> >
>
> > EnergyPlus_Support-fullfeatured@xxxxxxxxxxxxxxx
>
> >
>
> >
>
> >
>
> > EnergyPlus_Support-unsubscribe@xxxxxxxxxxxxxxx
>
> >
>
> >
>
> >
>
> >
>
> > http://docs.yahoo.com/info/terms/
>
> >
>
__._,_.___
Primary EnergyPlus support is found at:
http://energyplus.helpserve.com or send a message to energyplus-support@xxxxxxxx
The primary EnergyPlus web site is found at:
http://www.energyplus.gov
The group web site is:
http://groups.yahoo.com/group/EnergyPlus_Support/
Attachments are currently allowed but be mindful that not everyone has a high speed connection. Limit attachments to small files.
EnergyPlus Documentation is searchable. Open EPlusMainMenu.pdf under the Documentation link and press the "search" button.
Your email settings: Individual Email|Traditional
Change settings via the Web (Yahoo! ID required)
Change settings via email: Switch delivery to Daily Digest | Switch to Fully Featured
Visit Your Group | Yahoo! Groups Terms of Use | Unsubscribe
Change settings via the Web (Yahoo! ID required)
Change settings via email: Switch delivery to Daily Digest | Switch to Fully Featured
Visit Your Group | Yahoo! Groups Terms of Use | Unsubscribe
__,_._,___