saeranv / bibil Goto Github PK

Currently they are redundant.

Backtracking to parent node, and then traversing back to any child nodes does not output the most updated version of the child node. test here

Move ratio, axis, degree from node.grammar.type to node.grammar.type['divide']

Currently being tested in the tested in grammar.transform() function.

This method should allow you to extract the rule_stack of the child node, and reapply it while maintaining correct references.

Duplicate simply by pressing true in bibil UI twice.

First init

Second time same rules.

At tree.grammar.transform()

Vector to matrix multiplication is working correctly, but need to do some research on how to apply this to polylines.

Inputs: Seperation distance, tower dimension, external geometries.

Tower placement must:

• maximize number of towers in the lot
• prefer to be placed around the podium
• prefer configurations where max towers are closer to transit nodes

Thermal Zoning issues in HB (draft 1):

• inconsistent application for nonorthogonal, concave geometries
• heat/air flow issues for open plan spaces (convective, air flow transfer)
• boundary condition identification for non-intersecting, coincident faces i.e. infill lot condition
  

Use the move vector (cross product of inner_cut vector and ccw vector) to determine which side the valid and invalid node for courtyard split is.

So that you can remotely access it.

Take cross-product of (0,0,1) and shape vectors, extrude crv court width. Complexity = O(2n) time.

Achieved:

• Type rules can be applied using rule nodes.
• Meta-tree nodes can force-define hierarchies
• Proof-of-concept density and distribution set.
• Typologies can be set, although in a very clunky way.

Quick fixes needed:

• No filter for shape dimensions.
• No way to distribute thresholds using a rule.
• No way for nodes to auto-generate stepbacks based in inputted planes.
• No way to extract type rules and autocreate new type rules
• Difficulties in refreshing GH canvas to clean mutations/global variables

Complex shape issues:

• No way to recognize front/back.
• No way for nodes to recognize adjacent zoning.
• No way for nodes to recognize street adjacency and street ROW.
• No way for nodes to recognize adjacent geometries i.e. collision detection

Performance issues:

• how to get energy data in based on type
• how to get OSM data in
• how to integrate with Honeybee

Should output original node and traverse tree within miru_pattern.