个人 GitHub 账号下公开仓库的所有者可以登录并验证所有权,自行管理介绍,无需管理员批准。
登录并生成验证文件,在 30 分钟内将其提交到此仓库的默认分支。其他分支或分叉仓库中的文件无效。然后在下方检查文件,即可无需管理员批准直接管理项目。请保留文件以维持管理权限。
如需登录,将前往登录页面。登录后请回到此处,再次点击所选的验证按钮。
在项目文件夹中运行 /nomorevibe verify,即可验证所有权并自行管理介绍。
一分钟完成验证正在加载完整 README。 以下为已保存的摘录。
COSMOS Archive of MultiPle-Field Internal Reductions & Extractions
CAMPFIRE is a data reduction pipeline and web portal for JWST spectroscopy and imaging.
It contains tools for processing raw JWST data (NIRSpec MSA spectroscopy, NIRCam imaging)
through custom reduction stages and hosts the resulting products through an interactive
web interface.
The pipeline and portal were built to support spectroscopic survey work in COSMOS and
other deep fields, but the pipeline components are general enough to be adapted to
other JWST programs.
This is a monorepo with several components:查看完整 README ↗COSMOS Archive of MultiPle-Field Internal Reductions & Extractions
CAMPFIRE is a data reduction pipeline and web portal for JWST spectroscopy and imaging. It contains tools for processing raw JWST data (NIRSpec MSA spectroscopy, NIRCam imaging) through custom reduction stages and hosts the resulting products through an interactive web interface.
The pipeline and portal were built to support spectroscopic survey work in COSMOS and other deep fields, but the pipeline components are general enough to be adapted to other JWST programs.
This is a monorepo with several components:
| Directory | Description | Stack |
|---|---|---|
pipeline/ | JWST reduction pipeline | Python, jwst, astropy |
web/ | Interactive web portal | Next.js, Supabase, Tailwind |
python/ | Unified Python package: API client, CLI, and deploy tools | Python, httpx, Supabase, Cloudflare R2 |
etc/ | Empirical NIRSpec exposure-time calculator, spectrum simulator and MCP server | Python (numpy), MCP, Fly.io |
Supporting directories:
| Directory | Description |
|---|---|
supabase/ | Database migrations and local dev config |
scripts/ | One-off utility scripts (seeding, backfills, etc.) |
See the README in each subdirectory for more detail.
The interactive installer asks which components you need (basic CLI usage, data reduction, deployment, web development), manages the conda environment (conda / mamba / micromamba, or a plain venv), installs everything in the right order, and verifies the result:
python3 install.py
Non-interactive use mirrors every prompt with a flag:
python3 install.py --profiles reduction,deploy --yes # e.g. a reduction cluster
python3 install.py --doctor # verify an existing install
python3 install.py --help # all options
Alternatively, the classic one-shot conda env (everything, no choices):
conda env create -f environment.yml
conda activate campfire
git pull && python3 install.py
The installer remembers your previous answers (.campfire-install.json,
gitignored) and converges the environment without re-asking: editable installs
pick up code changes immediately, and the re-run applies anything else — new
or changed dependency pins, new extras, web/package-lock.json drift. It
never runs git for you, so pulling (and dealing with local changes) stays in
your hands.
# Set up your data directory (raw data, config, and outputs live here, not in the repo)
export CAMPFIRE_ROOT=/path/to/your/data
# Download raw data from MAST -> $CAMPFIRE_ROOT/raw/
cfpipe download --program 6585 --instrument nirspec
# Run the full reduction for an observation (a group of exposures to reduce + stack)
# Outputs to $CAMPFIRE_ROOT/products/<observation_name>/
cfpipe nirspec run --obs <observation_name> --all --processes 4
# Or run individual stages
cfpipe nirspec stage1 --obs <observation_name> --processes 4
cfpipe nirspec stage2a --obs <observation_name>
cfpipe nirspec stage3 --obs <observation_name> --processes 4
cfpipe nirspec zfit --obs <observation_name>
Requires Python 3.12+ and a CRDS cache.
See pipeline/README.md for full documentation.
cd web
npm install
npm run dev
Requires Supabase and R2 credentials in .env.local.
See web/README.md for setup.
Bug reports and feature requests are welcome via GitHub Issues. If you're interested in contributing code, feel free to open a PR — just note that much of the configuration (observation definitions, deployment targets) is specific to our survey, so pipeline and portal improvements are the most useful contributions.