Audit de cohérence Wasserstein

VérifiéSûr

Analyse les manuscrits et le code pour les incohérences entre W₁ et W₂. Génère un rapport de réconciliation.

Spar Skills Guide Bot
DeveloppementIntermédiaire
0030/07/2026
Claude Code
#wasserstein#audit#consistency#manuscript#code-quality

Recommandé pour

Notre avis

Analyse les manuscrits et le code pour détecter les incohérences d'ordre de Wasserstein (W₁ vs W₂).

Points forts

  • Vérifie automatiquement la conformité à la convention de notation W₂.
  • Détecte les usages ambigus de W non indicé.
  • Produit un rapport structuré avec des suggestions de correction.

Limites

  • Ne corrige pas automatiquement les problèmes.
  • Nécessite une configuration préalable du standard de notation.
  • Peut ne pas couvrir tous les cas d'usage de Wasserstein dans les notebooks.
Quand l'utiliser

Utilisez cette compétence lorsque vous devez harmoniser les métriques Wasserstein dans un projet avec des manuscrits et du code.

Quand l'éviter

Ne l'utilisez pas si vous utilisez déjà W₁ de manière cohérente et documentée.

Analyse de sécurité

Sûr
Score qualité85/100

This skill only reads files and generates a report; it does not modify any files, execute code, or interact with external systems. There is no risk of destructive actions or data exfiltration.

Aucun point d'attention détecté

Exemples

Audit all manuscripts and code
/wasserstein-audit all
Audit only manuscripts
/wasserstein-audit papers
Audit only code
/wasserstein-audit code

/wasserstein-audit — Audit Wasserstein Order Consistency

Scan all manuscript drafts and codebase for W₁ vs W₂ inconsistencies. Resolves the blocking Phase 0 deliverable: the legacy P01 manuscript uses W₁ in several places while project convention mandates W₂ as the primary metric.

Usage

/wasserstein-audit
/wasserstein-audit [papers|code|all]

Example: /wasserstein-audit all


What this does

  1. Reads papers/shared/notation.md (canonical notation standard, Wasserstein Audit section)
  2. Scans manuscript .md files under papers/ for W₁, unsubscripted W, ambiguous W_p
  3. Scans Python files under all domain packages for Wasserstein calls without explicit p=2
  4. Cross-references findings against what notation.md already has "verified"
  5. Produces a structured reconciliation report — does not fix anything without confirmation

Manuscript patterns that trigger a flag

| Pattern | Issue | |---|---| | W_1 / $W_1$ / W_{1} | W₁ usage — needs justification or must change to W₂ | | $W$ (unsubscripted) | Always flag — violates notation standard | | bottleneck without alongside Wasserstein | Sole metric violation | | wasserstein without explicit order nearby | Ambiguous |

Code patterns that trigger a flag

| Pattern | Issue | |---|---| | wasserstein_distance(a, b) with no p= arg | Default may not be W₂ in all library versions | | p=1 or order=1 near Wasserstein call | Explicit W₁ usage | | bottleneck_distance(...) | Must not be used as sole metric | | gudhi.wasserstein.wasserstein_distance without order=2 | gudhi default not guaranteed |


Report format

## Wasserstein Audit Report — YYYY-MM-DD

### Manuscript Findings
| File | Line | Found | Issue | Suggested Fix |

### Code Findings
| File | Line | Found | Issue | Suggested Fix |

### Status
- Blocking Phase 0: YES / NO
- Total issues: N (manuscript: N₁, code: N₂)

### Recommended Actions

Library defaults (reference)

  • persim.wasserstein_distance — p=2 by default ✓
  • gudhi.wasserstein.wasserstein_distance — requires explicit order= arg
  • giotto-tda Wasserstein vectorisation — p=2 by default ✓
  • W₁ in theory proofs is acceptable in Methods sections if clearly labelled and distinguished from the computational metric used
Skills similaires