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.
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. CUDA is implemented for simulate_pi; the other tools currently run on CPU. 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.