Repository navigation
Updated and expanded compas_singular version 1.0.0 - #10
Open
bladtcasper wants to merge 103 commits into
Open
bladtcasper wants to merge 103 commits into
bladtcasper wants to merge 103 commits into
Conversation
Update of compas_singular to compas-v2
Keep the branch limited to the existing compas_singular scripts ported to COMPAS 2.x. The exploratory vault/pole examples, the documents written around them, and the viewer patch they needed are not part of that port. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The old setup.py declared packages=[compas_singular] only, so a plain install shipped the top-level package without datastructures/, algorithms/, geometry/, topology/, utilities/ or rhino/ -- every documented import failed. requirements.txt was also empty, so compas itself was never pulled in. - move all packaging metadata to pyproject.toml and use packages.find so every subpackage is included; setup.py is now a shim for legacy invocations - fill requirements.txt (compas>=2.0,<3, networkx) and add requirements-viewer.txt behind a [viewer] extra, both read by pyproject - add environment.yml for a one-command conda setup - document install and verification steps in README.md - drop the setup.cfg universal-wheel flag (Python 3 only now) Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Dev compas-v2 compatibility Adds requirements to make cloning the repo more straightforward
Direct integration of compas v2 functions to delete _compat.py
Feature that merges compas_quad improvements over compas_singular Port batches 1-2 of the compas_quad review: the safe fixes land unconditionally, every behavioural change ships behind a keyword argument defaulting to the current behaviour. - fix the __all__ submodule leak in 19 package __init__ files, which made datastructures.add_strip/delete_strip modules rather than functions and broke algorithms/mapping.py - QuadMesh: face_opposite_edge null guard, six polyedge accessors, and the opt-in flags strict=, oriented=, both_sides=, legacy= - collect_polyedges/collect_strips: O(1) edge removal with the seed order preserved, so keys and output are unchanged - twocoloring: drop the self.times line that raised NameError at the end of every successful projection_0() - CI matrix to 3.9-3.12, action bumps, remove dead [tool:pytest] block Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> @
Merge the compas_quad synch feauture into dev to create a solid foundation for compas_singular expansion
… in the next commit
…ue, better captures symmetry, still within thesis bounds)
This branch has not been deployed
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.
Update and expansion of compas_singular, originally developed by Robin Oval during his PhD. This is the merge of all the work done during the past months on my own fork to update, fix and expand the package to create a working quad meshing tool.
What type of change is this?
Checklist
CHANGELOG.mdfile in theUnreleasedsection under the most fitting heading (e.g.Added,Changed,Removed).invoke test).invoke lint).compas.datastructures.Mesh.