The assistant in Rhino
What the chat in the Rhino panel can do for you, what it asks before doing, and what stays with you.
Preview, Wrengler Pro. This is the assistant in the Wrengler panel in Rhino, with a file open. It works as you: the same account, the same plan, and the same access to the project.
In the Rhino panel, the chat can do what you can do there. Ask it to group the towers, run a sunlight study on the podium for the winter solstice or save that study to the project, and it does it with the same code the panel's buttons use. What it sends is a host program: a short list of typed steps from a fixed vocabulary, never code.
On the web, the chat has no Rhino file to act on. Ask it for a Rhino action there and it tells you where to do it instead.
What it can do
In the Rhino file
| You ask | What happens |
|---|---|
| Make, change or remove a geometry group | The group is created, objects are added or removed, or the grouping is removed. The objects themselves stay. |
| Read or set the site | The study site's latitude, longitude and name. |
| Run a study | A sunlight, view or radiation study on your groups, with the panel's settings unless you say otherwise: date and hours, cell size; observers and targets for a view study; direct and diffuse irradiance and the sun position for radiation. The result shows in Rhino as if you had pressed Run. |
| Read the study on screen | Its settings, sensor count, minimum, mean, maximum and unit. |
| Clear a study | Its display is removed from the viewport. |
| Set the legend | A fixed minimum and maximum, or automatic again, and the number of colour bands. |
| Show the sun HUD, the sun-path arc or the inspector | Shown or hidden; the HUD's time and the arc's date can be set. |
It can also still select, measure, keep what faces a direction, colour, hide, show, isolate and delete, as before.
In the project
| You ask | What happens |
|---|---|
| What's in the project | Whether the file is linked, the saved studies and their documents (and whether a document is out of date), the files and the tags. |
| Link this file | Linked to one of your projects, or to a new project it creates for you. |
| Save the study | The study shown in Rhino is saved to the project, exactly as Save to project in Project data → Studies does. |
| Save the measured areas | The measured areas and group values are saved as tags, as Add from Rhino in Project data → Tags does. |
| Read the project's files | Files not yet read are read into passages, so the assistant can quote them. |
| Save the study as a document | A result document is written into the project's files, or the study's existing document is updated to the newest run. |
A study saved from the chat and one you save by hand with the same settings are the same study, so the project keeps one document for it, not two.
What it asks first
The chat never saves anything or deletes anything on its own.
- Anything it would save to the project (linking the file, saving a study, tags or a document) shows a card with Approve. Nothing is saved until you press it. Dismiss runs nothing.
- Deleting objects is highlighted in Rhino first and waits for Approve, as before.
- Instant commands like select the podium run straight away, but only for plain, reversible actions. Saving, running a study and anything in the project always go through the full answer.
Changes to groups and the site are one Ctrl+Z in Rhino. A study's display, the legend and the overlays are not part of Rhino's undo; clear or change them again. What was saved to the project is not undone by Ctrl+Z either: change it on the project page, as you would something you saved by hand.
Studies
- View and radiation studies need Pro, as their commands do. On another plan the chat says so rather than running them.
- Sunlight needs a site. Without one, the chat says so; ask it to set one, or set it in the panel.
- Studies take time. A study run from the chat can take up to about five minutes; the panel shows the result as it does for a study you start.
Running a list of checks
Paste a list of checks and ask the chat to run them. It runs each one, reads the state back from Rhino and the project, and answers with one table: the step, what was expected, what it observed, and whether it passed.
What stays with you
These are yours to do, on purpose. The chat will tell you where, but it won't do them:
- Signing in or out, API keys and settings.
- Deleting a project, and deleting or moving the project's files.
- Your organization's members, roles, knowledge approvals and housekeeping.
- The image studio, and setting goals.
It also can't move, copy or edit geometry: those aren't in its vocabulary.
Start with what's in this project? It reads the link, studies, documents and tags, so the next request can name them.
Related
- Assistant: chips, sources and privacy.
- Host Programs: the steps, the checks, and approval.
- Projects: linking a file and what a project holds.