Epic: Cesium integration: performance and verification
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript, three.js
- Domain
- performance, testing-qa
Research direction
This is an umbrella issue; start with children #105, #104, and #103, which cover the parity script, permalink screenshot test, and Cesium shadow-context mode. Read the linked child issues to find their files, tests, and entry points. Done means the numeric parity and screenshot checks run in CI or with one command, and the shadow-context cost is halved or its reason documented.
Written by the indexing model from the issue text.
Description
Track G (platform, performance and quality), item 1. The numeric parity script should precede #92 and #93 in the Earth parity epic, whose "done when" lines require exactly that comparison.
Goal
The Cesium compositing stays fast on real devices and its visual parity with celestiary is checked by scripts, not by hand.
Done when
The numeric parity check and the permalink screenshot test run in CI or with one command; the shadow-context cost is halved or a reason is documented.
Children
- #105 Scripted Cesium-vs-celestiary parity check (PR #134)
- #176 Cesium Earth layer runs out of memory at telescope FOVs from the ground (PR #180)
- #189 Frame rate on and near Earth's surface: 30–40 FPS against 60 in space (the
?perf=1overlay, the invisible Cesium work and the meter's readback are done; the checkpoint's queries andcesium.replay's CPU are open) - #104 E2E permalink screenshot test
- #103 Cesium shadow-context no-draw mode (upstream in portal-netgl)
- #213 yarn parity: views that fail or don't settle with Bing blocked
Done without a child issue: ion imagery sessions kept to close-up views (PR #202; CESIUM.md).
- Dominant language
- JavaScript
- Stars
- 55
- Forks
- 4
- Avg merge
- 10h 12m
- Merged PRs (30d)
- 134
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from celestiary/web
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
celestiary/web#345 ·
Maintainers usually reply within 1 day
-
Cesium guest (?cesium=iframe): white flicker near Mars's and Earth's surface remains after #335Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
celestiary/web#344 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
celestiary/web#340 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 1-2 days Newbie friendliness 48/100
celestiary/web#336 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
celestiary/web#334 · 1 comment ·
Maintainers usually reply within 1 day
Similar issues
-
44-x-y bug :beetle:
Difficulty 1/5 Under an hour Newbie friendliness 82/100
electron/electron#55528 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
react/react-native#59699 ·
Maintainers usually reply within 2 days
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
mastra-ai/mastra#29053 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
fjaeckel/seriesoftubes#230 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day