feat(2-bm): record the DMM substrate two-stripe fact, no per-energy selector (ENERGY-6)#293
Merged
Conversation
xmap
force-pushed
the
worktree-2bm-dmm-stripes
branch
from
325a53e to
a002fd7
Compare
…elector (ENERGY-6) Staff settled ENERGY-6 (#255): the DMM substrate carries two W-B4C/Si multilayer stripes (periods 24 and 13.8 angstrom, 4 mm apart, 140 x 44 mm each), and the stripe choice is a ONE-TIME setup, not a per-energy selection. The 24 angstrom stripe is the in-beam one (inferred from the Bragg-arm geometry: all six Mono energies cluster at d ~ 24 angstrom); the 13.8 angstrom stripe is never calibrated into store_0. The lateral X motors 2bma:m25 / m28 are constant alignment positions in both modes (ENERGY-5), not stripe selectors. So CORA records the two-stripe fact as a documentary block on the Monochromator descriptor (stripes list + active_stripe) and deliberately models NO DMM stripe-selector axis: there is no per-energy degree of freedom to model. This is the second Pink-cluster slice, data-only (no code, no scenario change). Inventory + the answered ENERGY-6 question row updated. Addresses ENERGY-6 (#255). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
xmap
force-pushed
the
worktree-2bm-dmm-stripes
branch
from
a002fd7 to
f69a12a
Compare
Coverage report
This PR does not seem to contain any modification to coverable code. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Second Pink-cluster slice (data-only). Stacked on #292 (slice 1); base retargets to
mainonce #292 merges, then this rebases to a single commit.What
Staff settled ENERGY-6 (#255): the DMM substrate carries two W-B4C/Si multilayer stripes (periods 24 and 13.8 Å, 4 mm apart, 140 x 44 mm each), and the stripe choice is a one-time setup, not a per-energy selection. The 24 Å stripe is in beam (inferred from the Bragg-arm geometry: all six Mono energies cluster at d ~ 24 Å); the 13.8 Å stripe is never calibrated into
store_0. The lateral X motors2bma:m25/m28are constant alignment positions in both modes (ENERGY-5), not stripe selectors.How
CORA records the two-stripe fact as a documentary block on the
Monochromatordescriptor (stripeslist +active_stripe) and deliberately models no DMM stripe-selector axis — there is no per-energy degree of freedom to model. This is the monochromator counterpart fact to the mirror coating stripe (MIRROR-1), but unlike the mirror stripe (energy-swept in Pink) the DMM stripe is static.Data-only: no code, no scenario change. Descriptor + inventory updated; the answered ENERGY-6 question row removed.
Tests
tests/unit/deployments/(62 passed) +mkdocs build --strictclean.Addresses ENERGY-6 (#255).
🤖 Generated with Claude Code