Quadratic Bézier points
A curve is more than a line between two endpoints. CurveHearth brings control-point fixtures and interpolation code into a Windows workspace for discussing the calculation with a compatible model and reviewing the resulting edits.
from math import isfinite
def quadratic_bezier(points, t):
def valid(v):
return type(v) in (int, float) and -1e100 <= v <= 1e100 and isfinite(v)
if type(points) not in (list, tuple) or len(points) != 3:
raise ValueError("three control points")
if any(type(p) not in (list, tuple) or len(p) != 2 or not all(map(valid,p)) for p in points):
raise ValueError("bounded finite 2D controls")
if not valid(t) or not 0 <= t <= 1: raise ValueError("parameter 0 through 1")
def mix(a,b): return tuple((1-t)*x+t*y for x,y in zip(a,b))
return mix(mix(points[0],points[1]),mix(points[1],points[2]))- Project
- Check both endpoints and the midpoint, rejecting non-finite coordinates or a parameter outside zero through one without changing the controls.
- 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.
from math import isfinite
def quadratic_bezier(points, t):
def valid(v):
return type(v) in (int, float) and -1e100 <= v <= 1e100 and isfinite(v)
if type(points) not in (list, tuple) or len(points) != 3:
raise ValueError("three control points")
if any(type(p) not in (list, tuple) or len(p) != 2 or not all(map(valid,p)) for p in points):
raise ValueError("bounded finite 2D controls")
if not valid(t) or not 0 <= t <= 1: raise ValueError("parameter 0 through 1")
def mix(a,b): return tuple((1-t)*x+t*y for x,y in zip(a,b))
return mix(mix(points[0],points[1]),mix(points[1],points[2]))Bring visual expectations into the code review
A curve that looks wrong may reflect a data convention rather than a broken formula. CurveHearth is a Windows AI coding workspace for connecting that visible result to your project’s implementation. Start with the expected shape, the control data and the component that consumes it, then ask the connected model to inspect the path between them.
One possible task is reviewing a quadratic curve helper used by an editor preview. Ask the assistant to examine control-point order, parameter bounds and how the caller supplies coordinates. Request a focused patch only after those assumptions are clear. The preview is an example application task; the useful result is code you can understand and verify in your own project.
Check the proposal with exact endpoint fixtures and an intermediate value, then inspect the rendered result using the application’s coordinate system. Include invalid or non-finite inputs if the helper promises to reject them. Run the relevant project tests and look for unrequested changes to accepted ranges, since a visual improvement can conceal a broader contract change.
CurveHearth connects to supported OpenAI-compatible or Anthropic endpoints. Select an uncensored AI model if one is available through your service; its tools, context and restrictions remain setup-dependent. The conversation supports your review, while your fixtures and interface checks determine whether the edit meets the requirement.
Questions for an interpolation change
What context helps explain a distorted curve?
Provide control points in their actual order, the parameter value and the caller’s coordinate convention. Include the expected visual result. Those details help separate an interpolation mistake from a transform or display assumption elsewhere in the application.
Are endpoint checks sufficient?
They are useful but incomplete. An implementation may return both endpoints correctly and still produce wrong intermediate values. Add at least one independently calculated interior fixture and check the visual path in the application that uses it.
Should the helper accept values outside its current interval?
Decide whether extrapolation belongs in the contract before extending the range. Ask which callers need it and how invalid inputs are handled today. Keep a range extension explicit rather than hiding it inside an interpolation correction.
Can CurveHearth confirm the appearance without running my editor?
Do not assume code inspection proves the rendered result. Use your editor or application to check the actual coordinate transforms and display. Review the proposed calculation separately, then verify that its integration produces the intended shape.
CurveHearth · Updated 2026-10-25