Skip to content

deprecate skyum's algorithm#207

Open
ljwolf wants to merge 9 commits into
pysal:mainfrom
ljwolf:dep-skyum
Open

deprecate skyum's algorithm#207
ljwolf wants to merge 9 commits into
pysal:mainfrom
ljwolf:dep-skyum

Conversation

@ljwolf

@ljwolf ljwolf commented Apr 28, 2026

Copy link
Copy Markdown
Member

This is an API-transparent swap of the skyum algorithm with shapely's minimum_bounding_circle(). Let's merge this after #206

@codecov

codecov Bot commented Apr 28, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 73.8%. Comparing base (a798e9e) to head (d6d1b88).
⚠️ Report is 5 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##            main    #207     +/-   ##
=======================================
+ Coverage   72.9%   73.8%   +0.9%     
=======================================
  Files         12      12             
  Lines       2118    2006    -112     
=======================================
- Hits        1543    1480     -63     
+ Misses       575     526     -49     
Files with missing lines Coverage Δ
pointpats/centrography.py 93.9% <100.0%> (+9.9%) ⬆️

... and 1 file with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Comment thread pointpats/centrography.py Outdated
Comment thread pointpats/centrography.py

@singledispatch
def minimum_bounding_circle(points):
"""

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we keep some docstring here?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh yes of course, sorry!

Co-authored-by: Martin Fleischmann <martin@martinfleischmann.net>
@jGaboardi

Copy link
Copy Markdown
Member

After conflicts are resolved will this be good to merge?

@martinfleis

Copy link
Copy Markdown
Member

After conflicts are resolved will this be good to merge?

No, we need the docstring.

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.

3 participants