he new ones start like this:
Imports RhinoImports Rhino.GeometryImports Rhino.Collections
So when I try to run my old code:
Dim vertexList As New List(Of On3dPoint) Dim ribList As New list(Of OnLine) Dim spineList As New list(Of OnLine)
I get these errors:
Error: Type 'On3dPoint' is not defined. (line 93)Error: Type 'OnLine' is not defined. (line 94)Error: Type 'OnLine' is not defined. (line 95)
So this is probably a really easy question. Can I still use the OpenNURBS library or do I need to rewrite using Rhino.Geometry? If so, where is best reference for that?…
Added by Chris Wilkins at 3:32pm on October 15, 2012
your question before. This uses the cotan weighted discrete Laplace-Beltrami operator, for which the earliest reference I know of is Duffin's 1959 paper “Distributed and lumped networks”, but I think it is more commonly associated with Pinkall and Polthier 93 “Computing discrete minimal surfaces and their conjugates”.…
more complex geometries, nothing works anymore and the output is weird: every test point has the same value (97% DA) and it's impossible to visualize these values even if a text tag 3D is assigned to points (check Result.jpg)
The output that we get is a uniform mesh.
To check this output we also run an illuminance analysis using the same test surface, giving 300lux as high and low bound and some areas didn't reach the target value - which means that there must be some areas below that threshold.
Another thing: as you can see from Screenshot.jpg at one point we get the string saying *.dgp not found. Is that a problem?
Attached you can find the Grasshopper file.
Thank you all!
Simone
…
untime error:
Runtime error (PythonException): unable to add point to document Traceback: line 97, in AddPoint, "C:\Users\AKIDRIBM\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rhinoscript\geometry.py" line 136, in Point, "" line 47, in toGH, "" line 187, in RunScript, ""
Could anyone help me figure out what's causing it? The code for adding the point is below:
# Plots points/text dots def Point(self, pointSource): print pointSource, type(pointSource) pt = rs.AddPoint(float(pointSource.value.x.value), float(pointSource.value.y.value), float(pointSource.value.z.value)) return pt
pointSource is a custom object that stores information about the point. Its only relevance here is to obtain the point coordinates. I do not get this error all the time, so I'm having trouble figuring out what is exactly causing it.…
r "virtual partitions" as follows:
What I mean "air walls" here, is derived from the description of the E+ documentation with the header of "Air wall, Open air connection between zones". (Page 17, http://apps1.eere.energy.gov/buildings/energyplus/pdfs/tips_and_tricks_using_energyplus.pdf)
As I understand, the term "air wall" used in E+ here refers to a description of something like "boundary condition" between adjacent interzone heat transfer surfaces, but not a kind of "construction or material" (like air space resistance or air gaps within a wall/double glazing window).
The main purpose of introducing the "air wall", is to simulate or approximate the airflow/convection/natural ventilation effect between multiple thermal zones which are connected by a large opening.
In my previous tests, using HBzones and GB, I managed to create the gbXML file which can be successfully imported to DB (without assigning any constructions within HB). And the adjacency condition can be recognized automatically by DB, even when I did not use the "Solve adjacencies" component in HB - shared surfaces between multiple thermal zones are recognized automatically by BD as "internal - partition"(which are standard partitions, but not virtual partitions).
In order to create/approximate "virtual partition", I need to manually draw a "hole" in the standard partition surface (fig.1&2). Again, the reason why we want to use "virtual partitions"(or "air wall") is that it allows airflow between multiple thermal zones which are connected by large openings and we could get different temperature of the each subdivided thermal zone which compose a large thermal zone.
My question is, if there is a possible way to simulate/approximate this kind of "virtual partitions"(or "air wall") in HBzones or in GB? If so, I would like to test if DB recognizes it or not. Actually, we expect that there is no need to involve any manual operations (like drawing a "hole" in the standard partition surface) in DB, due to an automatic optimization loop.
Thank you!
Best,
Ding
fig.1
fig.2
…