We need your help! 🔥
Please consider disabling your ad-blocker to support this website! 🔑
We are a free, community-supported website! 🥰
We only display small unobtrusive ads which help us stay online! 💯
Thank you in advance! ❤️
We are a free, community-supported website! 🥰
We only display small unobtrusive ads which help us stay online! 💯
Thank you in advance! ❤️
Colibri Outputs
Collects design parameters (us engineer types would call these 'performance metrics') to chart in Design Explorer. These will be the vertical axes to the far right on the parallel coordinates plot, next to the design inputs. These values should describe the characteristics of a single design iteration.
You can also combine this output as a static gene in Inputs.
Inputs
| Name | ID | Description | Type |
|---|---|---|---|
| Data | D[1] | Design results (performance metrics) to chart in Design Explorer. One or a list of values is acceptable, but each grip is limited with 10 values max. Null or Empty value will be marked as "NoData" | Text |
Outputs
| Name | ID | Description | Type |
|---|---|---|---|
| Outputs | OP | Colibri's Outputs. Plug this into the Colibri Aggregator downstream. Most users should connect 'Outputs' to the 'Outputs' input on the Aggregator. However, you can use 'Outputs' as an input for the Colibri Aggregator's Inputs param, too, which is useful when working with Galapagos or Octopus. | Generic Data |
Site design © Robin Rodricks.
Colibri and associated data © 2024 Thornton Tomasetti (CORE studio).
Rhinoceros and Grasshopper are registered trademarks of Robert McNeel & Associates.
Hosted by GitHub