DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to run the test suite and parity sweep on the orb engine with Thinking Orbs

Check the Swift engine against the original web geometry before you rely on it.

Who it is forA maintainer or contributor who needs proof that the Swift port matches the original engine before shipping or changing it.

The problemA port of a 3D animation engine can drift from the original in small ways that are hard to spot by eye.

The outcomeThe unit tests and the differential sweep both run, reporting pass or fail on the geometry checks.

What you need first

  • Xcode 16 or later with Swift 6, on a Mac
  • An app targeting iOS 17+, macOS 14+, tvOS 17+, watchOS 10+ or visionOS 1+
  • Node, only if you want to run Scripts/differential-sweep.sh (inferred from the README, which says the script runs the original engine under Node)

Steps

  1. Clone https://github.com/haplollc/ThinkingOrbs and open the folder in Terminal.
  2. Run xcodebuild test -scheme ThinkingOrbs -destination "platform=iOS Simulator,name=iPhone 17 Pro" to run the golden vector tests.
  3. Run Scripts/differential-sweep.sh to compare the Swift engine with the original engine under Node.
  4. Read the output and note any frame that does not match.
  5. If you change the engine, rerun both commands before you commit.

Prompt for your agent

In the ThinkingOrbs repo (https://github.com/haplollc/ThinkingOrbs), run `xcodebuild test -scheme ThinkingOrbs -destination "platform=iOS Simulator,name=iPhone 17 Pro"` and `Scripts/differential-sweep.sh`, then report the pass or fail result for each. Verify that the sweep reports zero mismatched frames before you claim parity.

Caveat. The sweep needs the original engine running under Node and an iPhone simulator, so it will not run on a machine without them.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page