Morton grid indexing
TerraInterlace is a Windows AI coding client for working through grid-index code. Discuss coordinate limits in the project context and review the proposed bit operations before accepting them.
def morton2(x, y, bits):
if type(bits) is not int or not 1 <= bits <= 16:
raise ValueError("bits.range")
if any(type(v) is not int or not 0 <= v < (1 << bits)
for v in (x, y)):
raise ValueError("coordinate.range")
result = 0
for i in range(bits):
result |= ((x >> i) & 1) << (2 * i)
result |= ((y >> i) & 1) << (2 * i + 1)
return result- Project
- Check corner coordinates and the maximum supported width, rejecting negatives, fractions and coordinates that do not fit.
- 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.
def morton2(x, y, bits):
if type(bits) is not int or not 1 <= bits <= 16:
raise ValueError("bits.range")
if any(type(v) is not int or not 0 <= v < (1 << bits)
for v in (x, y)):
raise ValueError("coordinate.range")
result = 0
for i in range(bits):
result |= ((x >> i) & 1) << (2 * i)
result |= ((y >> i) & 1) << (2 * i + 1)
return resultConnect compact indexing code to the data it serves
Indexing code can be short while its assumptions reach across storage and retrieval. TerraInterlace is a Windows AI coding client for reviewing that relationship in your own project. Ask the connected model to inspect the coordinate inputs, index representation and consumers before it suggests changes. Put the supported range into the request so a wider type does not silently become a wider contract.
For example, you might ask for help maintaining a grid key that interleaves coordinate bits. Bring the encoding helper and the code that stores or reads its output into the conversation. Request an explanation of axis order and bit width, followed by a focused proposal if those assumptions disagree. The task concerns your grid implementation rather than an included mapping system.
Verify the proposal at boundaries that affect real keys. Run checks for zero, the largest supported coordinates and values just outside the accepted range. Compare known coordinates with expected keys and inspect any change to persisted data interpretation. A mathematically plausible encoder still needs compatibility with the rest of the application.
TerraInterlace supports OpenAI-compatible and Anthropic endpoint connections. Select an uncensored AI model where your service makes one available; its context capacity, tools and restrictions remain properties of that setup. Keep the review centered on the project’s representation and the changes you can inspect.
Questions to settle before an index change
Why include consumers when reviewing a bit-interleaving helper?
A consumer may assume an axis order, width or persisted key format that the helper does not document. Inspecting both sides helps expose that dependency before a tidy-looking change alters how existing data is interpreted.
Does a larger integer type make a range extension safe?
Not automatically. Check validation, storage width and every consumer that handles the key. Ask the assistant to identify those dependencies and review a range extension as an intentional compatibility change with its own tests.
Which examples can reveal an axis-order mistake?
Use coordinates where only one axis is nonzero, plus a mixed case with an independently specified expected key. Symmetric coordinates can hide a swapped axis. Keep the expected convention written beside the project’s test fixtures.
Should stored keys be regenerated with the patch?
Only after determining whether the representation actually changes and how existing records must remain readable. Ask for that impact analysis first. A proposed helper edit does not by itself authorize or implement a data migration.
TerraInterlace · Updated 2026-10-25