Geometry code
Small numeric differences can change a geometric result. CG Orbit helps you examine tolerances, coordinate assumptions and the code behind a visual calculation.
const distance = Math.hypot(a.x - b.x, a.y - b.y);
const coincident = distance <= tolerance;
return { distance, coincident };| Review before applying | Compare actual behavior with the expected result. If a check fails, investigate it before applying more changes. |
|---|---|
| Connection | Base URL, credentials and a reachable server. |
| Project | Test coincident points and values just inside and outside the boundary rather than assuming exact floating-point equality. |
const distance = Math.hypot(a.x - b.x, a.y - b.y);
const coincident = distance <= tolerance;
return { distance, coincident };Give numerical changes an application context
CG Orbit brings a project folder and an AI coding conversation together on Windows. Use it when a numerical change needs more explanation than a replacement expression. Identify the feature that consumes the result, describe the visible behavior you expect, and ask the connected model to trace the relevant calculation through your source.
For example, a geometric comparison may treat nearby points as coincident using a tolerance. The important maintenance question is what that tolerance means to the application: which units it uses, who supplies it, and what happens at its boundary. Discuss those decisions before asking for a patch. CG Orbit provides the coding workspace rather than an integrated geometry engine.
Review the resulting proposal against cases drawn from your own coordinate system. Include identical points and distances on either side of the threshold, then inspect how the caller uses the answer. Run your project's numerical checks yourself. A change that looks reasonable in isolation can still alter selection, snapping or another consumer's expectations.
You can connect a supported OpenAI-compatible or Anthropic endpoint, including an unfiltered AI model where the provider makes one available. That description concerns the selected model's behavior, not a promise of perfect calculations or universal freedom from restrictions. Context limits and tool support depend on the model and server.
Reviewing a geometry-related patch
Should I provide the drawing or the calculation first?
Start with the source calculation and the behavior it affects. A small coordinate example with stated units is useful evidence. Explain what the application should do with the result so the discussion connects numerical decisions to a visible outcome.
Who decides the acceptable tolerance?
Your application requirements do. Ask the model to expose existing assumptions and propose alternatives, then choose a threshold justified by the data and user expectations. Do not accept a convenient constant merely because it makes one example pass.
Can I use CG Orbit to review callers as well?
Yes. Identify the callers in the project and ask how they interpret the comparison result. Review proposed edits across that path, especially where a Boolean answer changes selection or rendering, and verify those behaviors with your existing tools.
Does an unfiltered model improve numerical accuracy?
The label does not establish mathematical reliability. Check the specific model's output against explicit examples and project tests. Configure a supported endpoint with any required credentials; the provider determines the available models and their actual capabilities.
CG Orbit · Updated 2026-10-25
