Skip to content

feat: add loopstructural-visualisation as packages/loopstructural_visualisation workspace package - #301

Merged
lachlangrose merged 3 commits into
split/01-intrusions-fixfrom
split/02-visualisation-package
Aug 17, 2026
Merged

feat: add loopstructural-visualisation as packages/loopstructural_visualisation workspace package#301
lachlangrose merged 3 commits into
split/01-intrusions-fixfrom
split/02-visualisation-package

Conversation

@lachlangrose

Copy link
Copy Markdown
Member

Split out of #298 / #299. PR 2 of 9 in the stack — depends on #300.

Adds the loopstructural_visualisation package (2D/3D viewers, trame UI) as a new self-contained workspace member under packages/loopstructural_visualisation. No wiring into the root workspace config yet — that's PR 4 (#303 stack, once opened).

Base is #300 only because of stack ordering; this package's content doesn't depend on the intrusions fix.

…ualisation workspace package

Ports the loopstructural-visualisation repo in as a uv-workspace member,
following the src-layout pattern proven by packages/loop_common and
packages/loop_interpolation in Stage 2. Import name stays
loopstructuralvisualisation; only the on-disk container path changes.

- Routed the one print() call in __init__.py's trame-ui import guard
  through LoopStructural.utils.getLogger, consistent with the rest of
  the ecosystem's logging conventions.
- Left LoopStructural.datatypes imports in _3d_viewer.py as-is rather
  than swapping to LoopStructural.geometry: that module only exists in
  this repo's unreleased dev tree, not in any published LoopStructural
  release, and the package's declared floor is LoopStructural>=1.6.17.

(cherry picked from commit 07f0868)
@lachlangrose
lachlangrose force-pushed the split/02-visualisation-package branch from 0db8c7d to ad714cd Compare August 14, 2026 11:14
…uv.sources

packages/* workspace glob makes any package dir under packages/ a uv
workspace member automatically, but uv separately requires each member
to have a tool.uv.sources entry declaring it as workspace = true.
Missing entries broke uv sync/build for every package in this repo
with: "loopstructuralvisualisation is included as a workspace member,
but is missing an entry in tool.uv.sources". LoopStructural is needed
too since loopstructuralvisualisation depends on LoopStructural>=1.6.17
and should resolve that against the local workspace root, not PyPI.
@lachlangrose
lachlangrose merged commit c26d59a into master Aug 17, 2026
33 checks passed
@lachlangrose
lachlangrose deleted the split/02-visualisation-package branch August 17, 2026 04:31
@github-actions github-actions Bot mentioned this pull request Aug 17, 2026
lachlangrose added a commit that referenced this pull request Aug 17, 2026
…o-bump (#319)

Neither package has a component-scoped release-please tag yet (they
were only just added to the workspace in #301/#302), so release-please
had no correct anchor for their next version and fell back to
misreading one of the repo's old generic v1.6.5 LoopStructural tags as
their baseline, proposing 1.6.5 for both in the open release PR
instead of a proper minor bump from their real current versions
(map2loop 3.3.1, loopstructuralvisualisation 0.1.17). One-time
release-as pins to the correct next versions; remove once that
release PR has merged and each package has its own release-please tag
to anchor future bumps.
lachlangrose added a commit that referenced this pull request Aug 17, 2026
… test (#320)

* ci: pin map2loop/visualisation release-please versions to fix bad auto-bump

Neither package has a component-scoped release-please tag yet (they
were only just added to the workspace in #301/#302), so release-please
had no correct anchor for their next version and fell back to
misreading one of the repo's old generic v1.6.5 LoopStructural tags as
their baseline, proposing 1.6.5 for both in the open release PR
instead of a proper minor bump from their real current versions
(map2loop 3.3.1, loopstructuralvisualisation 0.1.17). One-time
release-as pins to the correct next versions; remove once that
release PR has merged and each package has its own release-please tag
to anchor future bumps.

* fix: ensuring stratigraphic order is consistent between methods + adding test
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.

1 participant