What does a real call return?
For 6 supplied samples over 150 minutes, the expected rotation is 16.85° per hour and the measured rotation 16.85° per hour, with a largest residual of 0.005°. The verdict is compatible. The example samples were prepared to follow the Sun.
Recorded on 2 November 2026 through the public MCP endpoint, service release 0.17.1. Inputs and full responses, response SHA-256 59508009a1a1…. Verdict values are the literal values the tool returns. Run the same inputs yourself to compare; elapsed times vary, and a new release may change the figures.
Checked against
- Tracks through independent DE421 daylight directions, together with reversal, opposing residual and time-lapse regression cases.
Recorded on release 0.16.1. These checks cover the listed cases, not every input. Evidence cards.
How it works
A solar model predicts the change in horizontal shadow direction over the supplied time samples. The engine compares drift and per-sample residuals so opposite errors cannot cancel into a false compatibility result.
Inputs and units
Supply a starting UTC date, geographic coordinates and samples containing elapsed minutes and measured shadow azimuth. Set an angular tolerance appropriate to measurement quality.
What the result contains
Expected and measured slopes, residuals and a conditional verdict can reveal a timeline or speed mismatch worth examining.
Connect and inspect the inputs
Initialize an MCP connection, call tools/list and inspect the schema for check_shadow_track. The live lab provides a complete example with editable inputs.
Call this engine in one command
Node.js 20+ and npm. This downloads a small remote MCP client; it does not install the engine locally.
npx --yes --package https://scorecompute.com/downloads/scorecompute-call-0.14.2.tgz scorecompute-call check_shadow_track --arguments '{"date_utc":"2026-06-21T08:00:00Z","latitude":48.85,"longitude":2.35,"samples":[{"minutes":0,"azimuth_deg":277.56},{"minutes":30,"azimuth_deg":284},{"minutes":60,"azimuth_deg":291.16},{"minutes":90,"azimuth_deg":299.32},{"minutes":120,"azimuth_deg":308.82},{"minutes":150,"azimuth_deg":320.01}],"tolerance_deg":5}'Client download, PowerShell input and verification →
Cite this engine
Engine identified by source hash, source SHA-256 18068d3a1b7c…. Evidence recorded on release 0.16.1; the public service currently runs 0.17.1. Replace the access date when you cite it.
ScoreCompute. Temporal shadow consistency in video (check_shadow_track), identified by source hash, source SHA-256 18068d3a1b7c32bc41626e52fee104925a35cc18ac5f50fa35fa4faef6251152. Evidence release 0.16.1, service release 0.17.1. https://scorecompute.com/engines/check-shadow-track/ (accessed YYYY-MM-DD).
All engine citations · Evidence card
Execution and availability
ScoreCompute exposes this tool through MCP Streamable HTTP. Rust computation runs on a connected worker; the public website and MCP gateway run separately. Among these 22 scientific tools, CUDA is implemented for simulate_pi; the other scientific engines run on CPU. The separate contributor network runs two compiled public workloads: a π estimate and fixed synthetic schedule probes. Requests are bounded and concurrent work may be refused when capacity is occupied.
Record inputs, assumptions and returned provenance when sharing a result. The public observatory displays software client names and tool activity, without publishing calculation arguments or results.