Open Ephemeris
Astrology app for ChatGPT and Claude: real charts from NASA JPL DE440, not AI guesses.
Vedic astrology and astronomical ephemeris: kundali, panchanga, dashas, vargas, transits
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 8/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 20/100 |
质量: 基础检查通过 2/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Vedaksha Vedic Astrology。按照 https://mcp.popnx.com/i/arthiqlabs-vedaksha-vedic-astrology.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 2/3 项检查 · 在你的电脑上运行 · ✓ 命令已检查 2026年11月13日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
需要先在电脑上安装 Docker(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
把这段话复制到 Claude 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude 安装 MCP server Vedaksha Vedic Astrology,按顺序:1) 用 docker --version 检查是否有 Docker。没有的话,请让我从 https://www.docker.com/products/docker-desktop/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "vedaksha-vedic-astrology": { "command": "docker", "args": [ "run", "-i", "--rm", "ghcr.io/arthiqlabs/vedaksha-mcp:v10.2.0", "--stdio" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Vedaksha Vedic Astrology 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
docker --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 安装 Docker Desktop:Mac 打开 Docker.dmg,把图标拖到“应用程序”(按电脑选择 Apple silicon 或 Intel 版本)· Windows 双击 Docker Desktop Installer.exe · 装好后打开 Docker Desktop 应用并保持运行。不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: docker --version
安装一次,所有需要 Docker 的工具都能用
SettingsDeveloperEdit Config
{
"mcpServers": {
"vedaksha-vedic-astrology": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/arthiqlabs/vedaksha-mcp:v10.2.0",
"--stdio"
]
}
}
}用 Vedaksha Vedic Astrology 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Vedaksha Vedic Astrology,或回答中出现 Vedaksha Vedic Astrology 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 Vedaksha Vedic Astrology
Vedaksha Vedic Astrology 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
A · 使用能连接 Vedaksha Vedic Astrology 的应用
B · 占星与吉日 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
可连接 Claude Code,但需要先准备
需要先在电脑上安装 Docker(只需一次)
把这段话复制到 Claude Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude Code 安装 MCP server Vedaksha Vedic Astrology,按顺序:1) 用 docker --version 检查是否有 Docker。没有的话,请让我从 https://www.docker.com/products/docker-desktop/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):claude mcp add --scope user vedaksha-vedic-astrology -- docker run -i --rm ghcr.io/arthiqlabs/vedaksha-mcp:v10.2.0 --stdio 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Vedaksha Vedic Astrology 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
docker --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 安装 Docker Desktop:Mac 打开 Docker.dmg,把图标拖到“应用程序”(按电脑选择 Apple silicon 或 Intel 版本)· Windows 双击 Docker Desktop Installer.exe · 装好后打开 Docker Desktop 应用并保持运行。不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: docker --version
安装一次,所有需要 Docker 的工具都能用
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --scope user vedaksha-vedic-astrology -- docker run -i --rm ghcr.io/arthiqlabs/vedaksha-mcp:v10.2.0 --stdio应能看到 Vedaksha Vedic Astrology 在列表中并显示已连接
用 Vedaksha Vedic Astrology 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Vedaksha Vedic Astrology,或回答中出现 Vedaksha Vedic Astrology 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor,但需要先准备
需要先在电脑上安装 Docker(只需一次)
把这段话复制到 Cursor 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Cursor 安装 MCP server Vedaksha Vedic Astrology,按顺序:1) 用 docker --version 检查是否有 Docker。没有的话,请让我从 https://www.docker.com/products/docker-desktop/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "vedaksha-vedic-astrology": { "command": "docker", "args": [ "run", "-i", "--rm", "ghcr.io/arthiqlabs/vedaksha-mcp:v10.2.0", "--stdio" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Vedaksha Vedic Astrology 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
docker --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 安装 Docker Desktop:Mac 打开 Docker.dmg,把图标拖到“应用程序”(按电脑选择 Apple silicon 或 Intel 版本)· Windows 双击 Docker Desktop Installer.exe · 装好后打开 Docker Desktop 应用并保持运行。不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: docker --version
安装一次,所有需要 Docker 的工具都能用
用 Vedaksha Vedic Astrology 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Vedaksha Vedic Astrology,或回答中出现 Vedaksha Vedic Astrology 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code,但需要先准备
需要先在电脑上安装 Docker(只需一次)
把这段话复制到 VS Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 VS Code 安装 MCP server Vedaksha Vedic Astrology,按顺序:1) 用 docker --version 检查是否有 Docker。没有的话,请让我从 https://www.docker.com/products/docker-desktop/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "servers": { "vedaksha-vedic-astrology": { "type": "stdio", "command": "docker", "args": [ "run", "-i", "--rm", "ghcr.io/arthiqlabs/vedaksha-mcp:v10.2.0", "--stdio" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Vedaksha Vedic Astrology 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
docker --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 安装 Docker Desktop:Mac 打开 Docker.dmg,把图标拖到“应用程序”(按电脑选择 Apple silicon 或 Intel 版本)· Windows 双击 Docker Desktop Installer.exe · 装好后打开 Docker Desktop 应用并保持运行。不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: docker --version
安装一次,所有需要 Docker 的工具都能用
用 Vedaksha Vedic Astrology 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Vedaksha Vedic Astrology,或回答中出现 Vedaksha Vedic Astrology 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
Claude Code
claude mcp add --scope user vedaksha-vedic-astrology -- docker run -i --rm ghcr.io/arthiqlabs/vedaksha-mcp:v10.2.0 --stdioClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"vedaksha-vedic-astrology": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/arthiqlabs/vedaksha-mcp:v10.2.0",
"--stdio"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"vedaksha-vedic-astrology": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/arthiqlabs/vedaksha-mcp:v10.2.0",
"--stdio"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"vedaksha-vedic-astrology": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/arthiqlabs/vedaksha-mcp:v10.2.0",
"--stdio"
]
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月20日
注册名称已通过 GitHub 账户 arthiqlabs 验证,该账户拥有此仓库
代码最后更新于18天前
GitHub 无法识别许可证类型;请打开文件自行查看
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/arthiqlabs-vedaksha-vedic-astrology)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 2 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于18天前,最新版本(10.2.0)于18天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Docker。
同一分类中有:Open Ephemeris, Totally Tarot Calculators, Moon Dasha Vedic Astrology, Supastro, NatalChart.AI Astrology
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Astrology app for ChatGPT and Claude: real charts from NASA JPL DE440, not AI guesses.
Engine-calculated astronomy and calendar calculators, for reflection. No account; inputs not logged.
Vedic astrology: birth charts, 26 vargas, 7 dasha systems, Shadbala, Panchang and Guna Milan.
Vedic astrology calculations: birth charts, dashas, transits, yogas, compatibility and panchang
Swiss Ephemeris astrology: natal charts, transits, synastry, solar returns and astrocartography.
| 本项 Vedaksha Vedic Astrology | Open Ephemeris | Totally Tarot Calculators | Moon Dasha Vedic Astrology | Supastro | NatalChart.AI Astrology | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 2/3 | 4/4 | 2/3 | 2/3 | 2/3 | 2/3 |
| 许可证 | NOASSERTION | MIT | – | – | – | – |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
For developers building kundli (kundali) apps, panchang calendars and AI agents. Natal charts, dashas, vargas, shadbala and panchanga, computed from an ephemeris that agrees with JPL Horizons to 0.096″ mean in longitude, in Rust, Python and WebAssembly, and as 17 MCP tools. Clean-room: every algorithm is traced to a primary source. Source-available under BUSL-1.1, with no AGPL obligations; each release becomes Apache-2.0 four years after it ships.
Website · Docs · Playground · API reference · Blog
clean-room · 0.096″ mean longitude vs JPL Horizons · 1,625 tests (per push) + 24,350 oracle rows · MCP-native · BUSL-1.1 → Apache 2.0
Install · Quick start · Accuracy · What's inside · MCP + property graph · Provenance · FAQ · License
| Platform | Install | Notes |
|---|---|---|
| Rust | cargo add vedaksha | full pipeline |
| Python | pip install vedaksha | engine via WebAssembly, py3-none-any, Python ≥ 3.9 — no Rust toolchain |
| WASM | npm install vedaksha-wasm | browser & edge, no data files |
| MCP | cargo install vedaksha-mcp | stdio + HTTP (bearer auth) |
| Docker | docker run -e VEDAKSHA_MCP_TOKEN=… -p 3100:3100 ghcr.io/arthiqlabs/vedaksha-mcp | multi-arch (amd64 + arm64) |
Compute janam kundali (natal charts), panchanga, dashas, nakshatras, vargas, shadbala, ashtakavarga, muhurta and transits/gochara from a sub-arcsecond ephemeris (JPL DE440s/DE441, worst case 0.272″ against Horizons) or from the data-file-free VSOP87A + ELP/MPP02 series (mean 0.160″, worst case 1.473″ over 1900–2025).
flowchart LR
K["JPL DE440s / DE441 SPK kernel, ~31 MB"] --> E V["VSOP87A + ELP/MPP02 compiled to constants, no data files"] --> E E["Ephemeris core precession · nutation light-time · deflection · ΔT"] --> W["Western houses · aspects dignities"] E --> J["Jyotish nakshatras · dashas · vargas panchanga · shadbala · muhurta"] W --> C["ComputedChart"] J --> C C --> G["Property graph Cypher · SurrealQL JSON-LD · RAG text"] C --> M["MCP server 17 tools · stdio + HTTP"] C --> S["Rust · Python · WASM"]
Python (pip install vedaksha): a sidereal (Lahiri) whole-sign chart, i.e. a kundli.
from vedaksha import Vedaksha
vk = Vedaksha() chart = vk.natal_chart(julian_day=2451545.0, latitude=28.6139, longitude=77.2090, ayanamsha="IndianOfficial", house_system="WholeSign") print(chart"houses", [(p["name"], p["sign"]) for p in chart["planets"]])
Rust (cargo add vedaksha):
use vedaksha::prelude::*;
fn main() { // 2024-03-20 12:00 UT1. The day is a fraction: noon on the 20th is 20.5. let jd = calendar_to_jd(2024, 3, 20.5); let moon = apparent_position(&AnalyticalProvider, Body::Moon, jd).expect("in range"); println!("Moon {:.4}°", moon.ecliptic.longitude.to_degrees()); }
A full chart, with houses and a sidereal zodiac, is the compiled doctest in crates/vedaksha/src/lib.rs.
JavaScript in the browser (npm install vedaksha-wasm; no data files):
import init, { compute_natal_chart } from "vedaksha-wasm";
await init(); const chart = JSON.parse(compute_natal_chart(JSON.stringify({ year: 2024, month: 3, day: 20, hour: 12, minute: 0, // UTC latitude: 28.6139, longitude: 77.2090, ayanamsha: "IndianOfficial", house_system: "WholeSign", })));
MCP (Claude Desktop claude_desktop_config.json, Cursor .cursor/mcp.json, or any stdio MCP client):
{
"mcpServers": { "vedaksha": { "command": "docker", "args": ["run", "--rm", "-i", "ghcr.io/arthiqlabs/vedaksha-mcp", "--stdio"] } } }
Without Docker, cargo install vedaksha-mcp and set "command": "vedaksha-mcp" with no arguments, or pip install vedaksha and use vedaksha-mcp the same way.
Every Julian Day on the public surfaces is UT1, not TT and not TDB. The engine converts to TT internally for the dynamical terms and uses UT1 for Earth rotation, which fixes the ascendant, MC and all twelve cusps. Passing a TDB Julian Day adds ΔT worth of rotation instead of removing it — 0.289° (17.3′) at today's ΔT ≈ 69 s, on every cusp. Two exceptions say so in their names: the raw SPK query (state_vector), which indexes the kernel directly and takes TDB, and the Python binding's analytical_position(body, julian_day_tt), which takes TT.
These figures are reproducible, not just asserted: vedaksha-parity is a separate harness (maintained by the same authors as this engine) that anyone can run against their own copies of the reference kernels to check the published numbers below.
Every figure is printed by a named test. Reproduce the ephemeris tables with bash scripts/download_de440s.sh, then cargo test -p vedaksha-ephem-core --release -- --include-ignored --nocapture; the ayanamsha figures come from cargo test -p vedaksha-astro sidereal, and the cross-check against an independent Python derivation of the same primaries from cargo test -p vedaksha-astro --test ayanamsha_fixture.
What the headline 0.096″ measures — precisely. It is a mean *apparent geocentric ecliptic-longitude* residual, not a general position-accuracy figure: the fixture also carries ref_latitude, ref_distance and ref_speed, but oracle_comparison.rs marks them dead_code and none of the three enters this number. It covers the 1900–2025 rows, at 1,535 comparisons per body (15,350 total across 10 bodies). The full 1900–2100 grid of 24,350 rows has a mean of 0.088″ and the same worst row (see below); the 1900–2025 cut is kept so that the published count and definition do not change. And it compares against planetary-system barycentres, not physical planet centres, matching what the DE440s kernel stores and what SpkReader returns; querying centres instead would inject a spurious ~0.1″ offset for the outer planets (scripts/generate_horizons_oracle.py) — the same order of magnitude as the headline mean itself. These facts are also published as data in metrics.json's accuracy block (quantity, era, targetConvention), so the site renders them rather than anyone hand-copying this paragraph.
SpkReader vs JPL Horizons (DE441) — oracle_comparison.rs, 24,350 committed rows (10 bodies × 2,435 dates, 1900–2100). Horizons serves DE441, so this measures our DE440s pipeline against an independent kernel.
| Era | Comparisons | Mean | Max |
|---|---|---|---|
| 1900–2025 | 15,350 | 0.096″ | 0.272″ (Moon, 1962-01-06) |
| 1900–2100 (all) | 24,350 | 0.088″ | 0.272″ (Moon, 1962-01-06) |
All 24,350 comparisons are within one arcsecond. Per body over 1900–2025 the mean runs from 0.092″ (Moon) to 0.100″ (Pluto), and the worst row of every body is between 0.243″ and 0.272″.
Time scale. Horizons' time tags are UT1 before 1962-01-20 and UTC from then. The oracle converts the UTC tags to TT with the leap-second count, as Horizons does itself, and reads the engine in TT, so neither ΔT nor UT1 − UTC is part of those rows' residual, and the oracle says nothing about ΔT there; earlier rows go through the engine's ΔT. Rows from 2026 on are compared the same way and are within 0.189″ (Moon, 2099-10-04). A Julian Day in UT1 after 2033.75 rests on an extrapolated ΔT (delta_t.rs), and one second of ΔT moves the Moon about 0.55″.
What the remaining 0.096″ is. After 1962 every body sits at 0.047″ to 0.054″ mean and at most 0.062″; before 1962 the bodies sit at 0.138″ to 0.146″ mean. That offset is shared by every body: it is the difference between Horizons' IAU 1976/1980 precession and nutation and the IAU 2006/2000B this engine uses. It is a difference of convention, and it is not emulated here. The largest row, the Moon on 1962-01-06, lies between 1962-01-01, where this engine hands ΔT from the SMH2016 spline to the USNO rows, and 1962-01-20, where Horizons switches from its pre-1962 series to its Earth-orientation file; the two series differ by 0.371 s across that handover, which is 0.2″ of Moon longitude (delta_t.rs). The Sun's light deflection of the planets is applied (solar_deflection_oracle.rs).
AnalyticalProvider vs JPL Horizons — analytical_oracle.rs, 1900–2025: overall mean 0.160″, worst case 1.473″ (Neptune, 2025-09-02), Moon 0.094″ mean via ELP/MPP02 (0.055″ after 1962). 13,815 comparisons across 9 bodies (1,535 dates per body) over 1900–2025; see metrics.json's accuracy.analytical block. The same run over all 21,915 comparisons to 2100 has a mean of 0.251″ and a worst case of 2.248″ (Neptune, 2078-01-27); metrics.json does not publish that pair.
Per body, because the mean hides a pattern worth knowing before you pick this provider:
| body | mean″ | body | mean″ |
|---|---|---|---|
| Sun | 0.094 | Jupiter | 0.148 |
| Moon | 0.094 | Saturn | 0.159 |
| Mercury | 0.094 | Uranus | 0.257 |
| Venus | 0.094 | Neptune | 0.410 |
| Mars | 0.090 |
The Sun, the Moon and the inner planets sit in a tight band at 0.090″ to 0.094″ and the error then grows outward. Split at 1962-01-20, all nine bodies sit at 0.131″ to 0.153″ mean before it, the same frame offset the SPK path shows. After it the Sun and the inner planets are at 0.038″ to 0.039″, the Moon at 0.055″, and Jupiter, Saturn, Uranus and Neptune at 0.165″, 0.165″, 0.365″ and 0.660″.
That growth belongs to the theory, not to how the tables are cut. scripts/generate_vsop87a.py drops terms below a uniform absolute amplitude of 1e-7 AU, but evaluating the complete untruncated VSOP87A series gives the same outer-planet residuals as the committed tables to four decimals (measured on geometric heliocentric vectors against DE440s over 1900–2100; the notes on VSOP87A_TO_EQUATORIAL in crates/vedaksha-ephem-core/src/analytical/mod.rs have the table). The authors fitted the theory to the JPL integration DE200, not to DE440 (vsop87.doc, "PRECISION"), and that is what the residual measures. If you need the outer planets to sub-0.1″, use `SpkReader`, where they are no worse than the inner bodies: Jupiter and Saturn are 0.096″ mean against the same oracle, inside the 0.092″ to 0.100″ band of every other body.
Until 2026-08-20 the analytical figures were an order of magnitude worse, and this README attributed the gap to VSOP87A being a truncated theory. That was wrong, and the wording protected a defect of ours: the analytical provider answered EarthMoonBarycenter with VSOP87A's Earth-centre series, so the observer sat 4,671 km off, and earth_state divided a barycentre-relative Moon by 1 + EMRAT instead of EMRAT for a further 56.8 km. Both are fixed; the figures before and after are in CHANGELOG-v6.1.0.md.
**The SPK and analytical figures