Autodesk

software, architecture, sustainability, environmental design, architectural science...


Object schedule

[Archived phorum post from squ1.com v2 by Olivier]

Hello everyone,

Has anyone assigned a schedule to an object recently?
I have been testing this feature (trying to model the closing and opening of windows at different time of the year), but I cannot seem to make it work.
I would just like to check if it's me or the software.

Any help is appreciated.
Thank you.

Olivier

New Building Materials
new to ecotect/roof shading question

Re: Object schedule

comment posted by Rehan (not verified) :: 1 April 2004 - 5:23pm

[Archived phorum post from squ1.com v2 by Rehan]

Hi Oliver
its interesting to know that yesterday i was thinking about the same because i just did model the trees in my BIG MODEL as 2d and then the interzonal adj and other calculations didnt take too long time (although a bit long Smiling and the computer i have is the fastest i can have its p4 with 1024 ram and i am a bit afraid to overlock it for processor speed Smiling ) well what i want to model is that the trees be more tranparent in winter and less transparent in summer to give a bit closer effect of what can happen in real situation on site analysis features. I am on the same track of questioning i ended up in a bit mess last night while trying to do this Smiling if someone knows pl do help me
Rehan

Re: Object schedule

comment posted by andrew :: 5 April 2004 - 1:40pm

[Archived phorum post from squ1.com v2 by Andrew]

Hi Olivier and Rehan,

I've just run a quick test assigning a schedule to both an appliance objects (to generate a burst of internal gain) and to the air change rate of a zone to simulate the opening and closing of windows. Both seemed fine - I could see a clealy defined temperature increase when the appliance was activated and could see the internal environment temperature move closer to outside temperature when the zone was activated (I used a maximum air change rate of 10ac/h to clearly see the effect). You might want to send over the model with a quick explanation of what you are trying to do and what you can't see for me to investigate.

Regarding the changing overshadowing from trees, when ECOTECT does a thermal calculation it caches the shading mask from surrounding objects. Thus to simulate variable shading of deciduous trees you need to do the following steps:

Step 1:
- Assign the trees the lowest transparency (ie: the maximum opacity) value that you want to use.
- Select one of the windows they will overshadow and click the Calculate » Sun-Path Diagram menu item.
- Calculate the Calculate Shading toolbar button in the Sun-Path Diagram dialog and generate an Overshadowing Percentage display.
- When complete, choose the Display » Display Shading Coefficients menu item and read off the average shading coefficient for the month when the trees will be at their most opaque.

Step 2:
- Assign the trees the highest transparency (ie: the minimum opacity) value that you want to use, and then do the same as Step 1 but read off the month at which the trees will be the least opaque.

Step 3:
You now have the variation in average overshadowing resulting from the trees - in the example I used, it varied from 21% to 71%. As the window itself already has a shading coefficient (SC) due to the glass and frame of 0.74, we need to moderate this value based on the additional SC of the trees.

- Thus, the minimum SC will be 0.74x0.21 = 0.1554.
- The maximum SC will be 0.74x0.71 = 0.5254.

Assuming that the transparency of the trees varies with season, you can take a relatively simple approach and use a schedule to vary the SC of the window by creating one window material with the maximum SC value and another with the minimum. If you assign one as the primary material of the window and another as the alternate, you can then use a schedule to vary between the two materials over the months of the year. You can do this with a simple step, by changing the between one 100% daily profile in summer and a 0% daily profile in winter, or you could even set up 12 different daily profiles for each month of the year, gradually varying between the two.

In the next release of ECOTECT you will be able to use scripts to modify schedules and shading masks interactively during your calculations, however in the interim this will give you pretty close to the same result.

Hope that helps...

Regards,
Andrew

Dr. Andrew Marsh
Square One research Pty Ltd

Re: Object schedule

comment posted by Olivier :: 6 April 2004 - 1:26pm

[Archived phorum post from squ1.com v2 by Olivier]

Thank you Andrew,
once again, you clarified things to me.
i was going the wrong approach to both problems (I tried the trees as well).
I was going the route of the alternate material:
For the opening of the windows, I assigned a void as alternate material, + a schedule to the window. I thought it would switch back and forth between the two...
Same thing with the trees: I made two different material with different opacities to model the change of season + assign a schedule to the tree.

Nothing seemed to happen in both cases. I was expecting to "see" the actual opacity of the trees changing in OpenGl when changing the date...

I understand what to do now.
Thank you.
Olivier

PS: Rehan, about your trees in your model, I have noticed they EACH are made up of over 150 objects! No wonder your calculations take so long. You should simplify these trees to speed up calcs.

Re: Object schedule

comment posted by Rehan (not verified) :: 6 April 2004 - 5:13pm

[Archived phorum post from squ1.com v2 by Rehan]

Hi Oliver and Andrew
First of all thanks alot for helping me out with stuff i cant do my self at all.
I noticed that out as well that calculation time is really because of the trees so now for the model i made the trees as a 2d object and it works good witht the calculation time. About scheduling the trees i am working it out and hopefuly i will manage it:
What i have done now for this model is that i placed the analysis grid at the area where the buildings are and then ran cummulative insolation.
when the insolation completes what i expect is that the area covered by buildings should be showing no solar radiation at all thus giving a blue colour corresponding to 0 Wh but its not the case in the inner sides of the buildings and there are no windows at all and i have run interzonal adj to see if there is some discrepency in model but couldnt find any. I will send this model with the analysis grid to u people.
my second question is about Wh.
see i make a simple calculation that for freiburg avg solar radiation is 1000 kWh/m2 per year so for per day it would be 1000/365 = 2.73 kWh/m2 as an average daily for 1m2 now when i multiply it for one m2 it will give me 2.73kWh or 2739 Wh but when there is an analyis grid or even if i do surface subdivision i get a value like 3000 Wh or something like this which can be acceptable if it is per m2 but if the grid dimensions are lets say 5m2 and i get an answer in Wh it should give me 2.73kWh/m2*5m2 = 13.698 kWh or 13698 Wh. I need a comment on these two issues from you or anyone who knows about it what it corresponds to.
best regards
Rehan

Re: Object schedule

comment posted by Olivier :: 7 April 2004 - 4:29am

[Archived phorum post from squ1.com v2 by Olivier]

Rehan,
Remember that the radiation levels you get from the analysis grid are not from a flat plane, but rather from points (located at the intersections of the grid's mesh). Therefore, the results, in Wh, cannot be associated with an area, since a point has no surface. Instead, the result is a evaluation of how much insolation each point receives throughout the day (or whatever span of time). Because they are _points_ and not planes, they capture the solar radiation as if it was tracking the sun throughout the day (I guess you could imagine the points as being small spheres that would have a surface facing all directions).
So, the results are larger that what it would be on a simple plane (only one surface direction).
To get a valid insolation measure in wh/m2, I use the cumulative insolation feature. Then, it calculates how much solar radiations fall on that particular plane, which has a surface area.
Now you mentioned you get the same results from a gris analysis than with a surface subdivision? Do you calculate the surface subdivision radiation with cumulative radiation?

Hope it clarifies things a bit.
Andrew, please correct me if I am wrong myself - I have just recently grasped the concept of the analysis grid... Smiling

Olivier

point versus surface for insolation...

comment posted by craines :: 7 April 2004 - 5:30pm

[Archived phorum post from squ1.com v2 by craines]

Andrew has said to let you know Olivier that you are absolutely spot on with the grid point versus surface plane for Rehan's Wh questions.

As you mention it would be more appropriate (if you are after Wh relative to area/surface etc.) to use the Cummulative Insol. not with the grid but using objects in the model (on thermal zones). Usually the best thing for this is to setup one object and then use the surface subdivision function (Modify Menu » Surface Subdivision » Rectangular Tiles) to get your objects to calc from.

With regard to the first issue you had Rehan, the colour of each grid cell is an average of all four vertices that make up the square. Thus if all four vertices are inside the building then you will have blue squares of value 0Wh, but if one or more points are outside the average will be greater.
One way to investigate this further is to turn off the Shade Grid Squares option, and turn on the Show Node Values instead. Then if you zoom into your model you will see that all the nodes that are inside do get 0Wh.
Becareful though because some of the nodes seem to line up exactly with the geometry of your buildings -- if a point exists exactly on some model geometry its results will be innacurate, as ECOTECT (being a dumb computer program) will sometimes think the point is outside, and other times think it is inside, so the value will not be useful for you.

To avoid all this hassle it is best to do a couple of things when setting up your Analysis Grid:
1. Always make sure you leave a small gap between any Analysis Grid point and model geometry, around 50mm is good. The aim is not to have any points line up exactly with any objects, as this will cause confusion for ECOTECT Smiling As a side, this is the reason why, when you use the automatic Fit Grid options in ECOTECT that it always offsets the grid inwards slightly.
2. If you don't want particular areas of your grid to show values, or you need a grid shape other than square, use the SHow / Hide Grid Nodes function (click Select Grid Nodes first). This way you will not only remove any nodes that you aren't interested in, the calculation will be quicker because ECOTECT won't calc. values for nodes it can't see, and you also won't see the confusing averaging that Rehan mentioned.

Small sample screen shot from Rehan's model
Regards,
Caroline

Caroline Raines
Square One research Pty Ltd

Scheduling Blinds not giving expected results

comment posted by Andrew S :: 14 September 2007 - 12:32am

Hi,

I am tryting to model blinds which are shut from 3pm to 7pm from December to February. I have copied the window material and modified the SHGC from 0.53 to 0.2 for the window with blinds and the transparency from 0.74 to 0.2.

I have run the monthly loads report and the reults show that the cooling load decreases (as expected) but the heating load increases. I would expect some increase in heating load if the blinds were shut all year round but in the cooler months i would expect the heating load to remain the same seeing as the blinds are not drawn through this period (i am in Australia so that why blinds are drawn in Dec - Feb)

I have run the calculate shading tool for a point i set up on the floor which will be affected by the blinds to check what was happening but there is no change in the results with or without the blinds.

I am not sure what I am doing wrong as I believe I have set up the schedule and the window data correctly.

Any help would be greatly appreciated.

Andrew

Blinds - Object Activation

comment posted by Olivier :: 12 December 2007 - 7:14am

UPDATE
Sorry Andrew..don't know what happened...
I am re-attaching the file here.
Should work...let me know.
I have made the window with "blind" come up in the winter so that it is more obvious on the north facing window (for down under).

Best,
Olivier

------------------------------------------------------
Hello Andrew,

This is a great feature.
Try this:

Select your window.
Set the Primary Material to that of the shaded window.
Set the Alternate Material to that of the non-shaded window.
Note that both have to be a WINDOW element.
Now set you schedule: 100% from 3pm to 7pm. Assign that schedule to December untill February. Save it as a schedule.
Next, with the window still selected, go to the Object Selection panel and under Activation, select your saved schedule.
Now run the IZA and check the Direct Solar Gains for that zone. You should see the change.
Sometimes, it is more obvious than other time; if you have more than one window on your zone, the results will get mixed up on the graph, but the numbers should tell the story.

I am attaching a test file for you. I do not know if the schedule will stay embeded. I set it up for Sydney. I encourage you to experiment.

Let me know,

Best,
Olivier

AttachmentSize
Object_Activation.eco130.59 KB

Hi Oliver, Thank you for

comment posted by Andrew S :: 4 October 2007 - 6:39am

Hi Oliver,

Thank you for your help. I have some aditional questions.

Do you mean that the primary material should be the non shaded window? As I only want shading from 3pm to 7pm.

Does the IZA need to be run every time there is a change to the schedule?

What should the Time on and Time off settings be under Activation (0.00 and 24.00?)

Regards,
Andrew

Object Activation

comment posted by Olivier :: 11 October 2007 - 4:54am

Andrew,

Nope. The Primary material should be the shaded window element. It might be a bug...but the schedule for the Object Activation seems to work with the primary material only. You can experiment.

If you want shading only from 3pm to 7pm every day of the year, then you can set that in the Time on - time off - that would be Time On: 15:00 and Time Off: 19:00.
This is unlikely though. You would most likely want to set a time schedule so that it does so only for a few weeks throughout the year, in which case you have to create a schedule.

Best,
Olivier

Shading coefficient

comment posted by Alice :: 22 February 2008 - 8:26am

Hello,

I opened the file you sent as an example, Olivier, but I could not see a difference between the window's primary material and it's alternate material. Is that normal? I can't find where to change an object's shading coefficient...

Regards,

Alice

Ok, never mind, I found it!

shading coefficients multiplied by shading coefficients..

comment posted by Alice :: 21 February 2008 - 8:58am

Hello Andrew,

I've been reading your post over and over again and I still don't understand: how can you just multiply the window's SC by the SC caused by the overshadowing of the trees?
This basically means that if the window is very shaded, its SC will be very big, and it will let a lot of energy in. Isn't that wrong?
Shouldn't you multiply the window's SC by 1-the shading coefficients caused by the trees?

And another question I had about your post is: when you calculate the shading coefficients of the window without any trees, they're not equal to 0, which means that the shading coefficients you get with the trees are not entirely caused by them! Shouldn't you take this into acount when assigning a SC value to your window? Cause if not, won't it suffer the overshadowing of other things (building itself, other buildings, etc...) twice?

I hope I am being understandable... And hope you will answer me soon because I have really spent a lot of time trying to figure this out!

(what I want to do is calculate the g ("facteur solaire") of a window with its blinds, and I thought I could use your method for this..)

Thank you very much,

Alice

Andrew's response to my question

comment posted by Alice :: 17 April 2008 - 10:24am

If your window has an SC of say 0.82, and the tree applies another effective SC of 0.6, then the overall SC will simply be (0.82 x 0.6) = 0.492. Thus, only 60% of the available light/radiation actually reached the window, and of that 60%, only 82% actually got through (hence: 0.82 x 0.6).

Higher shading coefficients actually mean more light/radiation passing through. For some standard SC value, see the following WIKI page:

http://squ1.org/wiki/Shading_Coefficient

Thus, you are absolutely right. The SC in the tables produced by ECOTECT are in error. There is supposed to be 7 columns, 3 for shading and 3 for shading coefficients. It seems that a bug has been included in the June 2007 update that omits half the columns. The real SC is, as you suggest, 1 - the displayed value.



Related websites

Translate This Site

User login