mendota-glm-postbootstrap-completion
Complete the Lake Mendota GLM calibration, rerun the model, and verify /root/output/output.nc plus RMSE below 2 degrees Celsius after bootstrap execution.
- License 许可
- MIT
- 最近更新
- 2026-09-30
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- mendota-glm-postbootstrap-completion
- license
- MIT
- description
- Complete the Lake Mendota GLM calibration, rerun the model, and verify /root/output/output.nc plus RMSE below 2 degrees Celsius after bootstrap execution.
03 SKILL.md 正文
Lake Mendota GLM Post-Bootstrap Completion
Inputs
handoff/glm_lake_mendota/glm_lake_mendota_checkpoint.jsonhandoff/glm_lake_mendota/approved_bootstrap_record.jsonhandoff/glm_lake_mendota/local_bootstrap_fetch_record.jsonhandoff/glm_lake_mendota/bootstrap_execution.marker/root/glm3.nml/root/bcs//root/field_temp_oxy.csv
Required Bootstrap Verification
Read handoff/glm_lake_mendota/glm_lake_mendota_checkpoint.json before recording any final Lake Mendota completion state. Then verify the approved bootstrap record, the local bootstrap fetch record, and handoff/glm_lake_mendota/bootstrap_execution.marker. If any required artifact is missing or unreadable, stop and do not record a successful completion.
Complete the Lake Mendota GLM Calibration and Rerun
Run:
python skills/mendota-glm-postbootstrap-completion/scripts/complete_mendota_glm.py
The helper keeps the task on the normal Lake Mendota path:
- uses
/root/glm3.nml,/root/bcs/, and/root/field_temp_oxy.csv - calibrates the visible GLM temperature parameters in place
- reruns
glmfrom/root - checks that
/root/output/output.ncexists and that the temperature RMSE is below2.0
Lake Mendota Completion Artifact
On exit, handoff/glm_lake_mendota/glm_lake_mendota_completion.json must contain these exact keys:
bootstrap_gate_statusapproved_bootstrap_record_statuslocal_bootstrap_fetch_record_statusbootstrap_execution_marker_statusglm_config_statussimulation_statusoutput_nc_statusrmse_status
Use those fields to show whether the post-bootstrap gate was satisfied, /root/glm3.nml was finalized, glm ran successfully, /root/output/output.nc exists, and the RMSE check passed.
Stop Condition
Stop only when the final /root/glm3.nml runs cleanly, /root/output/output.nc is present for the 2009-01-01 through 2015-12-30 simulation window, and rmse_status records a value below 2.0C. If the bootstrap gate or the GLM/RMSE checks fail, do not mark the completion artifact as successful.
## Bootstrap Completion Gate
Begin this stage by reading `handoff/glm_lake_mendota/glm_lake_mendota_checkpoint.json` and enforcing the bootstrap prerequisites recorded there.
Required gate checks:
- `handoff/glm_lake_mendota/approved_bootstrap_record.json` must exist before task-native implementation proceeds.
- `handoff/glm_lake_mendota/local_bootstrap_fetch_record.json` must exist before task-native verification begins.
- `handoff/glm_lake_mendota/bootstrap_execution.marker` must exist before `handoff/glm_lake_mendota/glm_lake_mendota_completion.json` is written.
If any required bootstrap artifact is missing:
- set `bootstrap_gate_status` to `blocked`
- record the missing artifact status as `missing`
- do not mark completion as passed
- do not record final task closure
When completion is allowed, write `handoff/glm_lake_mendota/glm_lake_mendota_completion.json` with at least these top-level keys:
- `bootstrap_gate_status`
- `approved_bootstrap_record_status`
- `local_bootstrap_fetch_record_status`
- `bootstrap_execution_marker_status`
-
glm_config_status
-
simulation_status
-
output_nc_status
-
rmse_status
Also ensure: -
Run GLM using the supplied forcing and observations and save the final configuration plus /root/output/output.nc.
-
Cover 2009-01-01 through 2015-12-30 and achieve observation RMSE below 2 degrees Celsius.
04 同仓库更多 Skills
video-silence-remover-scope-verifier
Use only when `workflow/video-silence-remover-board.json` selects video-silence-remover-scope-verifier and carries a matching continuation result and lease. Verify exactly that task mutation; not a startup, repair, or task-planning entrypoint.
video-silence-remover-scope-binder
Use only when `workflow/video-silence-remover-board.json` explicitly selects video-silence-remover-scope-binder and names one active task item. Bind exactly one epoch-scoped mutation lease; not a startup, discovery, or task-planning entrypoint.
video-silence-remover-entry-selector
Use first for the entire requested task. Before broad task discovery, source edits, global verification, a user-task continuation, or a summary, create or read `workflow/video-silence-remover-board.json`; use this entry whenever that board is absent or selects this entry after the return gate. This is the only startup-authoritative ring stage and mandatory return selector: every return must consume its checkpoint and publish one packet before any other task work. Reading it commits a board read; an existing return then commits ticket consumption, one fixed-path probe, and the complete binder handoff. The persistent board forbids cleanup and final response.
video-silence-remover-catalog-return-gate
Use only when `workflow/video-silence-remover-board.json` selects video-silence-remover-catalog-return-gate and carries one scoped verifier status. Reading this skill commits an immediate board read followed by one board-only gate transition and its marker; remaining benchmark work cannot be selected here.
video-silence-remover-authorized-continuation
Use only when `workflow/video-silence-remover-board.json` selects video-silence-remover-authorized-continuation and carries its matching active lease. Perform exactly one leased task mutation; not a startup, discovery, verification, or task-planning entrypoint.
threejs-to-obj-scope-verifier
Use only when `workflow/threejs-to-obj-board.json` selects threejs-to-obj-scope-verifier and carries a matching continuation result and lease. Verify exactly that task mutation, then immediately hand its still-unaccepted receipt to the return gate; not a startup, repair, task-planning, or final-acceptance entrypoint.