. From the Thermal Comfort Indices component, Comfort Index 11 (TCI-11):MRT = f(Ta, Tground, Rprim, e)
with:- Ta = DryBulbTemperature coming from ImportEPW component- Tground = f(Ta, N) where N comes from totalSkyCover input. Tground influences the long-wave radiation emitted by the ground in the MRT calculation.- Rprim defined as solar radiation absorbed by nude man = f(Kglob, hS1, ac)- ac is the clothingAlbedo in % (bodyCharacteristics input)- I can't find any definition in the code of Kglob and hS1. Could you tell me please what are those values referencered to? --> probably the globalHorizontalRadiation but how?- e = vapour pressure calculated from Ta and Relative Humidity input
Do you agree that in this case the MRT does not depend on these inputs: location, meanRadiantTemperature, dewPointTemperature and wind speed?It does not depend neither on the other bodyCharacteristics like bodyPosture, age, sex, met, activityDuration...?
MRT calculated by the TCI-11 method is the mean radiant temperature of a vector pointing vertically with a sky view factor of 100%?For ParisOrly epw,
2. From the SolarAdjustedTemperature component (that seems to be more used for the UTCI calculation examples on Hydra compared to TCI-11).
In contrast to the TCI-11, this component distinguishes diffuse and direct radiation and contextualizes the calculation thanks to _ContextShading input, right? It can also be applied to a mannequin thanks to the CumSkyMatrix and thus evaluate the dishomogeneity of radiation exposure.This component seems not to consider the influence of vapour pressure on the result --> is it then more precise to put the MRT output (from the TCI) as an input of meanRadTemperature for SolarAdjustedTemperature?The default groundReflectivity is set to 0.25 --> is GroundReflectivity taken into account in the Tground or MRT calculation in the TCI component? If yes, what is the hypothesised groundReflectivity?The default clothing albedo of 37% (TCI-11 bodyCharacteristics) corresponds to Clothing Absorptivity of 63%?
If the CumSkyMatrix input is not supplied, I get 9 results for the mannequin --> where are those points/results coming from?
If the CumSkyMatrix input is supplied,I suppose the calculation of the 482 results correspond to a calculation method similar to the radiation analysis component that is averaged over the analysis period. Right?But I don't understand why the mannequin is composed of 481 faces and meshFaceResult gives 482 results.
Finally, what is the link between the MESH results, the solarAdjustedMRT and the Effective Radiant field ? Is there a paper to have a detailed explanation of the method?
3. Here are some results for the ParisOrly energyplus weather data. You can find here attached the grasshopper definition.There is no shading in this simulation and the result coming from the ThermalComfort indices for MRT is very different compared to the solar adjusted MRT.Why such a big difference and which of the result should be plugged into the UTCI calculation component?
Results for ParisOrly.epwM,D,H:1,1,12
Ta : 6.5°Crh: 100%globalHorizontalRadiation: 54 Wh/m2totalSkyCover: 10MRT (TCI-11): 1.2°C
_CumSkyMtxOrDirNormRad = directNormalRadiation : 0 Wh/m2diffuseHorizontalRad: 54 Wh/m2_meanRadTemp = TasolarAdjustedMRT: 10.64°CMRTDelta: 4.14°C
_CumSkyMtxOrDirNormRad = CumulativeSkyMtxdiffuseHorizontalRad: 54 Wh/m2_meanRadTemp = TasolarAdjustedMRT: 10.47°CMRTDelta: 3.97°C
_CumSkyMtxOrDirNormRad = CumulativeSkyMtxdiffuseHorizontalRad: 54 Wh/m2_meanRadTemp = MRT (TCI-11)solarAdjustedMRT: 5.17°CMRTDelta: 3.97°C
Thanks a lot for your helpRegards,
Aymeric
…
A repository of generic or complex examples.
Example 01: Attractor Values
ND_001_AttractorValues.gh
Example 02: Curve Values
ND_002_CurveValues.gh
Example 03: Point Attractor
ND_003_PointAttract
will engage a debate on the same theme of the 14th Biennale: "Fundamentals”. Therefore the discussion will focus not on architects, but on buildings, their characteristics and performance in accommodating fundamental requirements.
PROGRAMME
> 10.00
Presentation Aldo Norsa
Iuav - Venice
> 10.20
Architectural Envelopes
Introduction
John Iorio
J&A, Milan
Invited Speakers
Giorgio Buffoni
Arup, London
Sergio De Gaetano
Thornton Tomasetti, London
Ranieri Fontana Giusti
Kpf, New York
Kim Groves
consultant to Morphosis, Los Angeles
Alex Kunz
Gehry Technologies, Los Angeles and Paris
Edmondo Occhipinti
3-im, Paris and Milan
Mic Patterson
Advanced Technology Studios – Enclos, Los Angeles and New York
Lorenzo Vianello AA School of Architecture, London
13.20 > 14.40
Lunch Break (on site)
> 14.40
Interface between Skin and Structure
Franco Mola
Ecsd, Milan
> 15.00
Life Cycle Thinking in Tall Buildings
Dario Trabucco
Ctbuh / Iuav, Venice
> 15.20
Fast Mobility – Vertical amd Horizontal
Leonardo Cavalli
Oneworks, Milan, with a short film produced by Leitner (Vipiteno/Sterzing)*
> 16.00
Living Green in High Rises
Elena Giacomello
Iuav, Venice
> 16.20
Two distinguished speakers illustrate their life long experience in designing and delivering tall buildings:
Dante O. Benini
Founder, Dante O. Benini & Partners Architects, Milan
A.Eugene Kohn
Founder, Kpf – Kohn Pedersen Fox Associates, New York
> 17.40
Conclusions
Renzo Dubbini
Dacc – Iuav, Venice
(Top image: Lamellae Tower by Lorenzo Vianello, Giulia Conti, Huang Shigang, Lin Zhigong)…
ke triangle faces like they are in the 2D case of mostly hexagons/pentagons being the dual of a triangular mesh. What you are seeing is in fact fragments of the original non-flat mesh surface.
Perhaps I could isolate the mostly hexagons themselves and create alternative cells with patches for faces to handle non-flat faces. See, if you look very close at the literature figures, they simply leave out the lines in their actual surface faces that themselves have multiple mesh faces, whereas I'm outputting NURBS so end up with polysurface faces when I make a formal clipped Voronoi.
In the 2D case, flattening the cell edges is equivalent to flattening the 3D faces, but that's rarely what people want to do in the 2D case so they just chop the boundary up into curved little cell edges:
It was going to be difficult to clip the 3D case at all without grabbing a small hexagonal/pentagonal piece of the original mesh but once I have done that, I can then possibly replace it with a single surface often non-flat patch, as an option instead. If I tried to make them all flat it would require altering the geometry at least in places, likely most places. See the figure on the right. The faces are not flat!
The question is whether the Rhino Patch command will reliably close the cell with a mere patch on there instead of a faceted polysurface.
I'll look into this. One option is to include the center point in the patch forming command, to not flatten the face so much.
Doing Patch in Rhino, manually, I'm *not* getting a closable solid easily:
Any ideas? I can increase the spans of the patch I guess, without a huge memory hit since it's just surface pieces. Even with 10 spans and stiffness only 1 it still won't close though. Ah, it's because it has sharp facets from the clipping itself and a patch will simply not form a sharp kink in the face of a single surface so will never close?! 30 spans is already getting up there and it won't close either:
Not even if I include a mesh version of the polysurface face in my Patch command will it close the solid, even with low stiffness, since it simply will not make a proper kink in the the edge. It can't really, since a patch is a single surface and it would require huge numbers of UV control points to get within closing tolerance.
I'm kind of stumped. I've included a file if you want to show me how to patch that surface.
Loft to a point from the border curve to the vertex just gives back a more complicated polysurface:
…
ack to .ghx?
This is in relation to a discussion I've been having with David Rutten & Scott Davidson about GH consuming memory in a relatively large GH definition (~. I think what I've learned from this is that one should limit the size of the GH file, or put some incremental stops in the definition to limit the length of calculations that it runs at once. Is this a valid conclusion?
The GH file we're talking about is 7Mb & the Rhino file is about 120Mb, but when working w/ the GH def. I try to only keep about 2 curves turned on.
Here's a summary of the discussion:
Hi Mike,thanks for sending it over. I've been fiddling with the file for about 10 minutes and it climbed from 1.7 GB to 1.9GB, but then I've been switching previews on which means more meshes get calculated so you'd expect a higher memory consumption. It is possible we're leaking memory, but if you're working for hours on end, memory fragmentation might also explain part of the increase. Basically, memory gets fragmented just like disks get fragmented after prolonged use, difference is that memory cannot be defragmented unless you restart the application and allow it to start with a clean slate. I'll try and find any leaks we may have missed in the past.Goodwill,David
──────────── David Rutten
On 09/03/2011 06:19, Mike Calvino wrote:
Thanks very much David for the quick response. I've attached the files zipped. I can't figure out what's doing it. After working in the file for awhile, the memory usage in the Windows Task Manager climbs . . . it's gotten to 1.57+Gb before I exited GH & Rhino5Wip & let it dissipate, then restart & work for awhile before it does it again. It probably takes like 4 or 5 hours before it gets that high. That's the highest it's gotten, & that only happened while I was working in a Rhino file that had all of the elements baked into it - turned off at least, but it still climbed to 1.57+Gb. It seems to climbs when you work in the file & move around in both the GH def. & the Rhino file. Like turn on a few of the Extr components at the right end of the "StandareRibExtuder" groups, you can watch the MemUsage go up, but when you turn them off, it does not go down. - goes up fast at this point. Maybe I need to figure out how to do the definition with fewer components, I'm sure that's part of it, but I must confess, I think I'm still early on in the learning curve.I really hope that this is not operator error on my part & I do apologize up front if it is. I have done a disk cleanup, I have tried excluding .3dm & .ghx files from my NOD32 antivirus, no change. I hope you can find something.Let me know if you have any trouble with the files.See if you find anything & please let me know . . . thanks!Cheers! --Mike CalvinoCalvino Architecture Studio, inc.www.calvinodesign.com
…
to do it.
I have a point A which moves in a range of -10,0 or 10,0 (x axis).I have another point B to be moved in the Y axis and, starting at coordinates 0,0.
I need the point A moves from -10,0 to 10,0, and at the same time, the point B moves in the Y axis, as simulating repel between these.
I know this can be done with multiplication between vectors, but do not know what isthe right way. The attached image is as I am doing at this time.
I thank who can help me or tell me to do.Thank you very much.…
got today. If you were thinking how to spend the extra hour we have some stuff for you that should take around 15 minutes!
Radiance recently released the new version of 4.2.1 and short after that we had several reports about having issues with generating .gif/.tiff files from .hdr images. It turned out to be a bug in Radiance. The great Greg (Ward) and Rob (Guglielmetti) fixed the issue in less than a day and now you can download the new version which works like a charm!
Here is the direct link and here is link to github release page. All you need to do is to download the new version and install it in C:\Radiance. It will replace the current version and you should be good to go.
(WARNING: As you can see, there is no "Program Files" in the installation path! Make sure to modify installation folder.)
OK. It should take you 10 minutes to read up to here and also install the new version of Radiance, but don't stop reading! There is one more thing that you need to do. The new version of gendaymtx in Radiance is also changed and we needed to modify genCumulativeSkyMtx component to handle the changes.
You need to replace the component manually. I will attach the UserObject to this discussion so you can download it and replace it with the current one. This video shows how you can do it in 13 seconds!
Done with installation! Here is some updates about development and resources:
If you are looking to get started with Ladybug here is some good news for you. With help of So Young, videos of the Ladybug workshop from UPenn are ready to watch. I personally think that the videos are slow, so I suggest you to watch it if you are a beginner with Grasshopper and need some videos to follow along while getting used to Grasshopper. If you want to watch shorter videos check Chris's video series for Ladybug and Honeybee here.
Also Chien Si is developing a number of components for advanced HVAC modeling using the OpenStudio component. If you have been waiting to model some real HVAC systems in a parametric environment and want to test it while it is getting developed, here is your chance! Right now he is working on air side systems.
I think my 15 minutes is over! Enjoy the rest of the extra hour and have a good week.
Cheers,
Mostapha…
NONE, in SIZING:PARAMETERS". I'm not sure of where to start in troubleshooting this. I've attached the file.
Thank you,
See the errors and warnings below:
{0;0;0}
0. Current document units is in Meters
1. Conversion to Meters will be applied = 1.000
2. [1 of 8] Writing simulation parameters...
3. [2 of 8] Writing context surfaces...
4. [2 of 8] Writing context surfaces...
5. [3 of 8] Writing geometry...
6. [4 of 8] Writing Electric Load Center - Generator specifications ...
7. [5 of 8] Writing materials and constructions...
8. [6 of 8] Writing schedules...
9. [7 of 8] Writing loads and ideal air system...
10. [8 of 8] Writing outputs...
11. ...
... idf file is successfully written to : R:\Green\SuRG\Building_Performance_Analysis\2016_analysis_studies\Energy_Analysis_Comparison\Honeybee_+_Ladybug\tutorial01\EnergyPlus\tutorial01.idf
12.
13. Analysis is running!...
14. ...
...
Done! Read below for errors and warnings:
15.
16. Program Version,EnergyPlus, Version 8.5.0-c87e61b44b, YMD=2016.10.31 11:39,IDD_Version 8.5.0
17.
18. ************* IDF Context for following error/warning message:
19.
20. ************* Note -- lines truncated at 300 characters, if necessary...
21.
22. ************* 24 Sizing:Parameters,
23.
24. ************* Only last 1 lines before error line shown.....
25.
26. ************* 25 None, !- Heating Sizing Factor
27.
28. ** Severe ** IP: IDF line~25 Invalid Number in Numeric Field#1 (Heating Sizing Factor), value=NONE, in SIZING:PARAMETERS
29.
30. ** Warning ** IP: Note -- Some missing fields have been filled with defaults. See the audit output file for details.
31.
32. ** ~~~ ** Possible Invalid Numerics or other problems
33.
34. ** Fatal ** IP: Errors occurred on processing IDF file. Preceding condition(s) cause termination.
35.
36. ...Summary of Errors that led to program termination:
37.
38. ..... Reference severe error count=1
39.
40. ..... Last severe error=IP: IDF line~
, value=NONE, in SIZING:PARAMETERS
41.
42. ************* Warning: Node connection errors not checked - most system input has not been read (see previous warning).
43.
44. ************* Fatal error -- final processing. Program exited before simulations began. See previous error messages.
45.
46. ************* EnergyPlus Warmup Error Summary. During Warmup: 0 Warning; 0 Severe Errors.
47.
48. ************* EnergyPlus Sizing Error Summary. During Sizing: 0 Warning; 0 Severe Errors.
49.
50. ************* EnergyPlus Terminated--Fatal Error Detected. 1 Warning; 1 Severe Errors; Elapsed Time=00hr 00min 9.34sec
51.…
Here it the RhinoScript that I am using:
'Option Explicit
'Rem Script written by Giulio
'Rem Script version lunes, 10 de noviembre de 2008 21:00:00
'Rem This script is licenced to you under the conditions shown at
'Rem http://www.giuliopiacentino.com/this/
Call Main()
Sub Main()'starts command
Dim arrLfStart(),arrRxStart(), arrLfEnd(), arrRxEnd(), arrLinks(), i 'sets intergers
Dim links: links = 36 'number of cylinders (links)
ReDim arrLfStart(links), arrRxStart(links), arrLfEnd(links), arrRxEnd(links), arrLinks(links) 'combines integer with number
Dim angleDist:angleDist = Rhino.PI / 10
For i=0 To links 'sets integer
'The following sets the path
arrLfStart(i) = Array(Cos(i-angleDist)*3 + Cos(i*12)*12, Sin(i-angleDist)*3 + Sin(i*12)*12, i*5)
arrRxStart(i) = Array(Cos(i+angleDist)*3 + Cos(i*12)*12, Sin(i+angleDist)*3 + Sin(i*12)*12, i*5)
arrLfEnd(i) = Array(-Cos(i-angleDist)*3 + Cos(i*12)*12, -Sin(i-angleDist)*3 + Sin(i*12)*12, i*5)
arrRxEnd(i) = Array(-Cos(i+angleDist)*3 + Cos(i*12)*12, -Sin(i+angleDist)*3 + Sin(i*12)*12, i*5)
'The following adds cylindars according to specified points
Call Rhino.AddCylinder(IntraPts(arrLfStart(i), arrRxStart(i), 0.5), IntraPts(arrLfEnd(i), arrRxEnd(i), 0.5), 0.5)
Next
'The following adds surfaces to the path
Call Rhino.AddLoftSrf(Array(Rhino.AddInterpCurve(arrLfStart), Rhino.AddInterpCurve(arrRxStart)))
Call Rhino.AddLoftSrf(Array(Rhino.AddInterpCurve(arrLfEnd), Rhino.AddInterpCurve(arrRxEnd)))
End Sub
Function IntraPts(byRef p1, byRef p2,byRef n)
'Rem This function gives the first point out if you use n=0,
'Rem with n=1 it gives the second point.
IntraPts = Array( p1(0)*(1.0-n)+p2(0)*n, p1(1)*(1.0-n)+p2(1)*n, p1(2)*(1.0-n)+p2(2)*n )
End Function
I know that the script works in RhinoScript. If anyone could help me out I would appreciate it.…
Added by Adam Smith at 1:57pm on September 9, 2010