Skip to content

Kmesh distance floor - #38

Merged
junwen94 merged 3 commits into
mainfrom
kmesh-distance-floor
Sep 8, 2026
Merged

junwen94 merged 3 commits into
mainfrom
kmesh-distance-floor

Conversation

@junwen94

@junwen94 junwen94 commented Sep 8, 2026

Copy link
Copy Markdown
Collaborator

close #37

…t cap

Replace `max_kpoints_per_axis` (default 50) with `MIN_K_DISTANCE = 0.03` on the
solid-state 2*pi reciprocal lattice. The floor is the same for every axis, so
all axes run out of change points together and the ladder is gap-free by
construction -- the "truncate at the first >1 jump" rule is gone. The
"skip a repeat" dedup stays (degenerate axes plus the two rounding precisions).

Move `sweeps/kmesh.py` to a top-level `goldilocks_data.kmesh` module (geometry,
not a sweep definition) and fold `kindex_points` into it; delete
`sweeps/kindex.py` and drop the kmesh/kindex re-exports from `sweeps/__init__`.

Update the kmesh reference page, the AGENTS.md convention section, and the
deposit-record test fixture to the floor.
submit_initial.py was the one-off seed submission for the SSSP campaign, which
has run. It carried a third, 0-based copy of the ladder schedule; extend.py plus
goldilocks_data.kmesh supersede it.
…-index dataset

1-based, built with min_k_distance = 0.03; supersedes the 0-based d5ds2-64f16,
which stays listed for existing citations.
@junwen94
junwen94 merged commit 0a33bba into main Sep 8, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

kmesh: bound the ladder by a k-distance floor, and promote it to a top-level module

1 participant