Skip to content

Conversation

@mmaelicke
Copy link
Owner

Summary

Fix inconsistent MetricSpace instantiation in Variogram for different maxlag settings. Previously, absolute maxlag (>=1) created sparse MetricSpace, while relative maxlag (<1) created dense, leading to different distance calculations and incorrect plots/binning.

Changes

  • Modified Variogram.__init__ to always create MetricSpace with max_dist=None for consistent dense distance matrices.
  • Updated test expectations in test_sparse_maxlag_30 to reflect improved accuracy.
  • Enhanced maxlag docstring with examples, including pre-computed MetricSpace usage.

Impact

  • Ensures uniform variogram calculations across maxlag types.
  • Slight performance trade-off for absolute maxlag on large datasets (users can pre-compute MetricSpace for optimization).
  • Fixes issue Bug in MetricSpace #101: Bug in MetricSpace maxlag handling.

All tests pass, no regressions.

@mmaelicke mmaelicke changed the title Fix MetricSpace maxlag inconsistency for consistent variogram calculation Enhance maxlag handling with max_dist parameter and estimation for relative maxlag Jan 16, 2026
…lative maxlag

- Add max_dist parameter to Variogram.__init__ for explicit distance limiting
- Implement estimation for relative maxlag using random samples with warning
- Update docstring and add test for warning
- Ensure consistent experimental variograms for equivalent maxlag values
- Limit distance computation for performance on large datasets
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.

2 participants