You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit dbfba85
Browse filesBrowse the repository at this point in the historyBrowse files
fix(loop-link): send drillhole interval data as log set arrays
The viewer reads drillhole interval values only from arrays with the
association interval that belong to a log set. The encoder sent cell, so
the viewer accepted the data but did not offer it for colour. Send interval
with the log set intervals. The fake viewer now refuses cell on a drillhole.
Record the results of the manual checks M1 and M2 and add the 006 row to
the spec index.
5. Run the script. Type `packages/loop_link/.venv/Scripts/python.exe <script path>` and press Enter.
85
85
6. Check that seven objects show in the object list. Check that the types are: points, vectors, lines, surface, block model, tetra mesh and drillhole.
86
86
7. Select each object, one at a time. Check that the property name `grade` shows in the property table.
87
+
A tetra mesh has no Data button: use the isosurface or the filter controls to check `grade`.
88
+
The vectors show as flat discs that face up (+z).
87
89
8. Write the result in your test record.
88
90
89
91
Pass: seven objects show, each with the right type, and the property name `grade` shows in the property table for each object.
92
+
93
+
## Record
94
+
95
+
2026-11-07, window viewer of the geoviewer build with selection and fetch, token from the user:
96
+
97
+
- M1: pass. The grid was in the inventory 0.43 s after the send (limit 5 s). It ran against the window viewer, not the headless viewer.
98
+
- M2: pass after one fix.
99
+
- Drillhole `grade` was not selectable. The viewer reads drillhole interval values only from arrays with association `interval` in a log set. The encoder sent `cell`. It now sends `interval` with the log set `intervals`.
100
+
- Tetra mesh `grade` works through the isosurface. The viewer has no Data button for a tetra mesh.
101
+
- Vectors were too small to see on a 1 unit triangle (glyph size default is 1 percent of the object). They work on a 100 unit triangle.
102
+
- Open viewer issue: the vector glyphs and the drillhole tubes look pixelated (geoviewer issue 181).
Copy file name to clipboardExpand all lines: specs/README.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,6 +10,7 @@ not certify that an implementation or a numerical acceptance gate passed.
10
10
|[003-fault-evaluation-performance](003-fault-evaluation-performance/spec.md)| Implementation in progress; 005 contract cascade applied | Its active plan and tasks remain in the existing LoopStructural-native worktree. OP3 and OP4 remain open; completed tasks, including concurrent T043, and measured failures are preserved. |
11
11
|[004-matrix-free-directional-constraints](004-matrix-free-directional-constraints/spec.md)| Draft; 005 contract cascade applied; task graph checked | Review the updated plan and tasks. OP1 still requires the quadrature measurements before a default is chosen. |
12
12
| [005-coordinate-frame-correctness](005-coordinate-frame-correctness/spec.md) | S1 implemented 2026-11-04 on `feat/005-coordinate-frame-correctness` (17 of 17 tasks; evidence in [verification.md](005-coordinate-frame-correctness/verification.md)); S5 planned 2026-11-05 and revised after review; S6 not planned | Review and merge the S1 branch. S2 planned and tasked 2026-11-04 (T018 to T031, waves 8 to 13); run spec-orchestrator for S2. S3 planned and tasked 2026-11-05 ("Stage S3 design" in plan.md; OP4 and OP5 closed; T033 to T050, waves 14 to 22; build after S2 merges). S3 is built on `feat/005-s3-frame-persistence` (pull request #397, stacked on #396; 18 of 18 tasks, evidence in verification.md). S3 merged (#397); a follow-up keeps the legacy load backward compatible (pull request #400). S4 planned and tasked 2026-11-05 ("Stage S4 design" in plan.md; OP8 to OP10 have defaults and block nothing; T051 to T068, waves 23 to 31); run spec-orchestrator for S4. S5 planned 2026-11-05 and revised the same day after review and five maintainer answers ("Stage S5 design" in plan.md; OP13 to OP15 closed; OP12, OP16 and OP17 have defaults; OP17 blocks the S5 merge only if a parity file changes); S5 tasked 2026-11-05 (T069 to T088, waves 32 to 42; no open point blocks a task; build after S4 merges). OP1: plan S6 in a later planner run. OP3: constant-norm accuracy check. OP2 closed 2026-11-04: the R2/R5 matrix stays in the default pytest run. 7 minor review findings are open (run-state.json). |
13
+
|[006-loop-link](006-loop-link/spec.md)| S1 to S3 (stories 1 and 5) implemented 2026-11-07 on `feat/006-loop-link` (37 of 37 tasks, 13 waves; wave and end reviews passed; not merged) | Open a pull request. OP6: plan S4 (stories 6, 7). OP7: plan S5 (stories 2 to 4) after geoviewer spec 066-selection-and-fetch lands. Run manual checks M1 and M2 against the real viewer. |
0 commit comments