How bangoriyabhavya151107/pinkops works
PinkOps is a cricket player-evaluation and squad-selection framework. Its documented workflow moves from auditing immutable competition data and reconstructing match state through pressure measurement, context-adjusted player evidence, reliability classification, and batter/bowler selection with auction strategy. Stage 4.0’s orchestrator explicitly invokes its analytical modules; Stage 4.1’s pipeline explicitly assembles evidence, assigns roles, and runs robustness analysis. README documents the broader stage progression. Later-stage internals are represented at file level because their call relationships are not shown in the supplied excerpts.
Main entry points: evidence_profiles.py Player evidence profiles · run_stage_4_0.py Stage 4.0 orchestrator · candidate_selection.py Candidate selection · 01_data_audit.py Data audit
Components 21
Data foundation
- Competition data
- Data audit
src/01_data_audit.py - Match-state builder
src/02_build_match_state.py
Pressure modeling
- Pressure discovery
src/03_pressure_discovery.py - Stage 3.1 validation
src/stage_3_1
Reliability evidence
- Stage 4.0 orchestrator
src/stage_4_0/run_stage_4_0.py - Pressure opportunity
src/stage_4_0/opportunity.py - Contextual expectation
src/stage_4_0/expectation.py - Player attribution
src/stage_4_0/attribution.py - Clutch matching
src/stage_4_0/clutch.py - Match consistency
src/stage_4_0/consistency.py - Uncertainty bounds
src/stage_4_0/uncertainty.py - Player evidence profiles
src/stage_4_1/evidence_profiles.py - Tactical roles
src/stage_4_1/role_analysis.py - Reliability profiles
src/stage_4_1/reliability_classification.py - Robustness analysis
src/stage_4_1/robustness.py - Methodological multiverse
src/stage_4_1_1/multiverse.py
Squad decisions
- Candidate selection
src/stage_5/candidate_selection.py - Target-file generation
src/stage_5/generate_target_files.py - Auction strategy
src/stage_5/auction_strategy.py - Stage 6 defense
src/stage_6/build_stage_6_defense.py
Connections 25
- Competition data → Data audit: audited by
- Data audit → Match-state builder: informs
- Match-state builder → Pressure discovery: feeds
- Pressure discovery → Stage 3.1 validation: extends
- Stage 3.1 validation → Stage 4.0 orchestrator: informs
- Stage 4.0 orchestrator → Pressure opportunity: calls
src/stage_4_0/run_stage_4_0.py - Stage 4.0 orchestrator → Contextual expectation: calls
src/stage_4_0/run_stage_4_0.py - Stage 4.0 orchestrator → Player attribution: calls
src/stage_4_0/run_stage_4_0.py - Stage 4.0 orchestrator → Clutch matching: calls
src/stage_4_0/run_stage_4_0.py - Stage 4.0 orchestrator → Match consistency: calls
src/stage_4_0/run_stage_4_0.py - Stage 4.0 orchestrator → Uncertainty bounds: calls
src/stage_4_0/run_stage_4_0.py - Stage 4.0 orchestrator → Player evidence profiles: feeds
- Player evidence profiles → Pressure opportunity: uses
src/stage_4_1/evidence_profiles.py - Player evidence profiles → Contextual expectation: uses
src/stage_4_1/evidence_profiles.py - Player evidence profiles → Player attribution: uses
src/stage_4_1/evidence_profiles.py - Player evidence profiles → Clutch matching: uses
src/stage_4_1/evidence_profiles.py - Player evidence profiles → Uncertainty bounds: uses
src/stage_4_1/evidence_profiles.py - Player evidence profiles → Tactical roles: assigned by
src/stage_4_1/stage_4_1_pipeline.py - Player evidence profiles → Robustness analysis: evaluated by
src/stage_4_1/stage_4_1_pipeline.py - Player evidence profiles → Reliability profiles: classified by
- Player evidence profiles → Methodological multiverse: stress-tested by
src/stage_4_1_1/multiverse.py - Player evidence profiles → Candidate selection: supports
- Candidate selection → Target-file generation: produces
- Candidate selection → Auction strategy: informs
- Auction strategy → Stage 6 defense: supports