Decrease precision for Suggest Rules

Transformations of geometry using Rhino SDK produce results varying in decimal precision, therefore the precision for comparing naked edges has been significantly decreased. It has changed from absolute precision to precision dependent on the Slot diagonal.

Minor bugfixes for Suggest Rules from Geometry

Suggest Rules from Geometry

• Point coordinates rounded to 10 decimals for better results
• Points on the boundary of the Connectors are no considered to be in the connector
• Prevent null exception for meshes with no naked edges

Component Rule Explicit between 2 lists of Modules and Connectors

The component Rule Explicit between 2 lists constructs Explicit Rules between all Conectors of source Modules with all Connectors of target Modules. Optionally filters out Rules that are invalid with the given Modules based on Module names, Connector counts and Connector Axis and Orientation.

Suggest Rules by example

Features that extract Rules from example assembly of Module geometry:

• Suggest deterministic Slots from geometry similar to Module geometry (Slots From Geometry)
• Construct Rules from adjacency of deterministic Slots (Scan Slots for Rules)

Icon improvements:

• Construct indifferent Rule
• Construct Rule At Boundary

Code styling:

• Rename files to be named similar to class names

Monoceros

New Components:

• Construct Indifferent Rule
• Construct Rule at boundary
• Suggest Rules based on Module Geometry - detect identical naked edges on Module Connectors
  Fixes:
• Assemble Rule
• negative Connector planes orientation
• Component descriptions

Monoceros 1.0.3.3

Implement Connector Index data type to prevent mixing up Rule constructors
Significantly update documentation

Monoceros 1.0.3.2

• Fix Module type internalization (breaks backwards compatibility)
• Update Documentation