ere are ways to remap the data (PathMapper etc) and there's an excellent tutorial by David Rutten about path mapper on this forum somewhere.
And always look at whether you simply need to flatten your data to ba able to work with it.
For point lists I often use the PointNumber component to help visualise the data and the good old Panel component helps too!
When you see some of the elegant, compact definitions on here, there often seems to be some mystical foresight needed right from the first component but hopefully this jedi skill comes with practice!…
Added by martyn hogg at 12:24pm on January 13, 2014
windows. I manage to have proper HBZones with RADMaterials and EPConstructions (I've run Daylight calculation on them successfully), but when I plug the zones to GrizzlyBear this error appears:
Solution exception:'EPZone' object has no attribute 'getCurrentLoads'
In addition, something similar happens when I plug these HBZones to the newest decomposeByType component, althought it works properly when plugged to the previous version of it. This is what the error says:
Solution exception:'hb_EPZoneSurface' object has no attribute 'BC'
Same thing with SetEPZoneConstruction:
Solution exception:'hb_EPZoneSurface' object has no attribute 'BCObject'
Any thought?
Ander…
ular heights and widths of units.
3. I then fill these grids with placement panels.
4. Create 2D adaptive components with materials applied along with parameters for specified offsets of materials. I'll name each ac as a unit type name ie WT-1, WT-2 etc.
5. I replace the placement panels with particular adaptive components (unit types).
6. I prepare a schedule for both unit and material takeoff in Revit.
So I guess I would like to achieve something similar to this where I can have multiple unit types already made/determined with materials and apply them to a grid or divided surfaces and they will adapt or fit into this divided grid. and from there i could extract data like sqft of a particular unit and material.
see attached images for clarification and thanks again for your time and help, this issue has had me stumped for a while now and I'd love to solve it.
Thanks again
…
les, also this image shows where i'm defining/assigning all of them:
BTW, the warehouse stuff appears ONLY in the exportToOpenStudio option.
Finally, i'm not conditioning the zones. Explicitly i asked to set the isConditioned_ input in the HB_createHBZones to False. The discussion you mentioned approaches this differently oversizing the heating/Cooling so you never need the AC. The IDF created don't have any definition of IdealSystems, so i don't believe this is the problem. If you want to see the IDF files you can see them above (attached in a previous message).
Weird ...
Thanks,
-A.
…
e section which wont recompute with owner.expiresolution(true). Am I missing something ? I cannot declare buttons and form and all that stuff in run script, cause it doesnt accept withevents property. My idea is to recompute all the script component stuff...
This is my code :
Private Sub RunScript(ByVal x As Object, ByVal y As Object, ByRef A As Object)
If x = True Then frm.Controls.Add(b1) t1.location = p0 frm.Controls.add(t1) frm.show a = zmienna Else frm.Dispose End If
End Sub
'<Custom additional code> Dim frm As New system.windows.Forms.Form WithEvents b1 As New system.Windows.Forms.Button WithEvents t1 As New system.Windows.Forms.TextBox Dim p0 As New system.Drawing.Point(30, 30) Dim zmienna As String
Private Sub b1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles b1.click
zmienna = t1.Text owner.ExpireSolution(True)
End Sub
…
can be found in "C:\Documents and Settings\<user name>\Application Data\McNeel\Rhinoceros\5.0\Plug-ins\IronPython\settings\lib\rhinoscript" folder on WinXP. So could have used yours too.
RhinoCommon is a SDK and basically the power behind grasshopper and rhinoscriptsyntax functions. In fact each time you call a rhinoscriptsyntax, a RhinoCommon code gets executed.
And, yes:
import Rhino - imports RhinoCommon
import utility - enables importing utility.coercebrep() (or coerce3dpoint() coercecurve() ... so on)
Item access means an input is consisted of a single item.List access means an input is a list.Tree access means an input is consisted of a tree with data on different branches.rs.BooleanDifference requires both of it's arguments to be lists, so it would be logical to set the inputs b1 and b2 as lists. But there is one problem, that Mitch pointed out to me: it seems that python components (like grasshopper components) are "intelligent", and can distinguish whether you are inputting item, list, or tree. Setting your input as list, might disable this ability and leave you with only possible type of input (list).So honestly I do not know why in this case, setting the inputs to Lists worked - due to mentioned "intelligence" of python component, even an Item type would work.This might be a question for an experienced user, I am just a beginner.…
n make it possible to Motivation generate
a variety of interesting objects, from abstract fractals to plant-like
branching structures, their modeling power is quite limited. A major
problem can be traced to the reduction of all lines to integer multiples
of the unit segment. As a result, even such a simple figure as an
isosceles right-angled triangle cannot be traced exactly, since the ratio
of its hypotenuse length to the length of a side is expressed by the irrational
number √2. Rational approximation of line length provides only
a limited solution, because the unit step must be the smallest common
1
1
√2
denominator of all line lengths in the modeled structure. Consequently,
the representation of a simple plant module, such as an internode, may
require a large number of symbols. The same argument applies to angles.
Problems become even more pronounced while simulating changes
to the modeled structure over time, since some growth functions cannot
be expressed conveniently using L-systems. Generally, it is difficult
1.10. Parametric L-systems 41
to capture continuous phenomena, since the obvious technique of discretizing
continuous values may require a large number of quantization
levels, yielding L-systems with hundreds of symbols and productions.
Consequently, model specification becomes difficult, and the mathematical
beauty of L-systems is lost.
In order to solve similar problems, Lindenmayer proposed that numerical
parameters be associated with L-system symbols [83]. He illustrated
this idea by referring to the continuous development of branching
structures and diffusion of chemical compounds in a nonbranching filament
of Anabaena catenula.
The following is an example of its application:
starting string: A
p1: A F(1)[+A][-A]
P2: F(s) F(s*R)
which I think is basically trying to say
F(s) = move forwar a step of length s > 0.
Thanks again,
Mateo…