Stage H: deployment environment — probe a modern CDS-capable env, else clone the site CDS env
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- anaconda, git, github, python
- Domain
- devops, infrastructure
Research direction
Read the deployment requirements in the issue and the linked notes/cds-hardware-bringup-2026-08.md, then probe the deployment machine at Python 3.12, 3.11, and 3.10 with the listed CDS packages. Record the solve results; if needed, clone the site CDS environment, install the repository with --no-deps, and verify the CDS imports and py3.9-baseline tests. Document the separate read-only deploy-key setup in an untracked local note.
Written by the indexing model from the issue text.
Description
Stage H (spec §8). Investigate empirically before committing; the expected answer is
already documented but should be verified on the box rather than inferred.
The probe
On the deployment machine, dry-run solve a modern environment together with the CDS packages
(foton, python-foton, python-awg, cdsutils, nds2-client) at python 3.12, then 3.11, then 3.10.
Record the outcome in notes/cds-hardware-bringup-2026-08.md.
Expected: unsolvable. The CDS 3.1.2 control packages are py3.9-only builds in that channel, which
is exactly why the sibling project had to change python>=3.9 → python=3.9 and drop the anaconda
metapackage. If it does solve, verify both that the CDS modules import and that the py3.9-baseline
test subset passes in it before trusting it.
Fallback (the expected path)
Clone the site CDS conda environment — it is the ABI reference for the compiled foton/awg/nds2
extensions — then pip install -e . --no-deps. All six of this repo's core dependencies (numpy, scipy,
control, slycot, pyyaml, matplotlib) are already in that lock, so --no-deps is sufficient and
mandatory: nothing may bump numpy/scipy underneath those extensions.
Keep the modern sysid environment as the primary dev/docs environment either way — this decides only
what runs on the deployment machine.
Also needed
Unattended git pull on the deployment machine needs its own read-only deploy key for this repo and
forge. The sibling project's key is registered on a different forge and a different project, so it does
not transfer. Concrete host / account / path values stay in an untracked local access note — this repo is
public, unlike the sibling GitLab project that tracks them.
Campaign: CDS hardware backend · branch feat/cds-hardware-backend
· spec · plan · handoff
Code is deferred until the plan and issues have been reviewed.
- Dominant language
- Python
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
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 CaltechExperimentalGravity/system_ident
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in CaltechExperimentalGravity/system_ident
Similar issues
-
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
WLAN-Pi/wlanpi-profiler#341 ·
Maintainers usually reply within 1 day
-
Memory leak: the shared `validation_aborted_error` keeps every traceback it is raised throughPossibly taken @Fire162 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
graphql-python/graphql-core#287 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
roman-corgi/ctc-dip#160 ·
Maintainers usually reply within 1 day
-
type-bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
render_findings.py reads and writes in the host's default encoding, so findings.html breaks on a cp1252 Windows hostPossibly taken @Aaqibhafeezkhan claimed this today. Openbug good first issue mentored python size: XS up-for-grabs
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
dheerajjha/mcp-migrate#366 · 1 comment ·
Maintainers usually reply within 1 day