Date: November 21, 2025 Version: 2.0.0 - FINAL For: Claude Code AI Assistant Priority: βββββ CRITICAL
New Dataset Features Added:
β Training Scenarios
- S70 (70/15/15) - Standard split
- S80 (80/10/10) - High training ratio
- All scenarios documented in
core_modules/constants.py
β Comprehensive Nuclei Distribution Analysis
- New module:
nuclei_distribution_analyzer.py - Detailed reports for each dataset: Z, N, A distributions
- Magic number proximity analysis
- Isotope and isotone diversity metrics
- Deformation statistics for Beta_2 datasets
β Enhanced Output Files
- MATLAB format (.mat files) - already implemented β
- Excel format (.xlsx files) - already implemented β
- CSV format (.csv files) - already implemented β
nuclei_distribution_report.xlsx- NEW! Detailed distribution analysis per datasetMaster_Nuclei_Catalog.xlsx- NEW! Complete catalog of all nuclei used
β Comprehensive Documentation
DATASET_GUIDE.md- Complete guide for dataset usage, MATLAB integration, Excel filespfaz_modules/pfaz01_dataset_generation/README.md- Updated with all new features- MATLAB usage examples included
- Distribution report explanations
Key Documents:
- π DATASET_GUIDE.md - NEW! Complete dataset documentation
- π pfaz_modules/pfaz01_dataset_generation/README.md - Updated module docs
Current Completion: 97%
Remaining Work: 3% (QA + Cleanup + Final Testing)
Target: 100% Production-Ready System
You are tasked with completing the final 3% of a comprehensive nuclear physics AI project. This is the FINAL PUSH to production readiness.
- MASTER_PROJECT_CHECKLIST.md - Complete project checklist
- QA_ENGINEER_MODULE_DESIGN.md - QA system design
- FILE_CONSOLIDATION_CLEANUP_GUIDE.md - File cleanup guide
- EXECUTIVE_SUMMARY.md - Project overview
Prompt for Claude Code:
TASK: Complete Project Audit
Please analyze the entire Nuclear Physics AI Project and provide a comprehensive report.
STEPS:
1. **File Inventory**
- List all Python files in the project
- Group by PFAZ module (pfaz01, pfaz02, ... pfaz13)
- Identify any ungrouped files
- Count total lines of code
2. **Duplicate Detection**
- Find files with similar names (e.g., *_v2.py, *_complete.py)
- Identify files with overlapping functionality
- Check FILE_CONSOLIDATION_CLEANUP_GUIDE.md for known duplicates
- Recommend which files to keep/delete
3. **Missing Components** (Use MASTER_PROJECT_CHECKLIST.md)
For each PFAZ (0-13):
- List expected modules (from checklist)
- Mark which exist β
and which are missing β
- Estimate completion percentage
4. **Import Dependency Analysis**
- Check all import statements
- Identify broken imports
- Find circular dependencies
- List unused imports
5. **Output Directory Structure**
- Check outputs/pfaz01/ through outputs/pfaz13/
- List expected vs actual outputs
- Identify missing reports/visualizations
6. **Generate Report**
Create PROJECT_AUDIT_REPORT.md with:
- Executive summary
- Detailed findings per PFAZ
- Priority issues list
- Recommended actions
CRITICAL: Be thorough! This audit guides all remaining work.
Expected Output:
PROJECT_AUDIT_REPORT.md(~10-15 KB)- Clear action items list
- Completion percentage per PFAZ
Prompt for Claude Code:
TASK: Implement QA Testing System
Follow the design in QA_ENGINEER_MODULE_DESIGN.md to create a complete testing infrastructure.
STEPS:
1. **Create Test Directory Structure**
tests/ βββ conftest.py βββ test_smoke/ βββ test_units/ βββ test_integration/ βββ test_system/ βββ test_data_quality/ βββ test_model_performance/ βββ test_regression/ βββ test_load/ βββ fixtures/ βββ reports/
2. **Implement Smoke Tests** (test_smoke/)
Create tests for:
- All imports work
- config.json loads
- main.py --help runs
- Data file exists
3. **Implement Unit Tests** (test_units/)
Priority modules to test:
- data_loader.py
- dataset_generator.py
- qm_filter_manager.py
- model_trainer.py (basic)
- semf_calculator.py
- woods_saxon.py
Target: 50+ unit tests covering core functionality
4. **Implement Integration Tests** (test_integration/)
Create tests for:
- PFAZ1 complete pipeline
- PFAZ2 AI training pipeline
- Data β Model β Prediction flow
Target: 10+ integration tests
5. **Create pytest Configuration** (conftest.py)
Include:
- Common fixtures (sample_dataset, trained_model)
- Test configuration
- Logging setup
6. **Setup CI/CD** (.github/workflows/tests.yml)
GitHub Actions workflow for:
- Run tests on every push
- Generate coverage report
- Upload to codecov
7. **Generate Test Report**
Run all tests and create TEST_COVERAGE_REPORT.md
DELIVERABLES:
- Functional test suite
- β₯50% code coverage
- CI/CD pipeline working
- TEST_COVERAGE_REPORT.md
REFERENCE: QA_ENGINEER_MODULE_DESIGN.md for complete specifications
Expected Output:
tests/directory with all structure- Working pytest tests
.github/workflows/tests.yml- Coverage >50%
Prompt for Claude Code:
TASK: Consolidate Duplicate Files
Follow FILE_CONSOLIDATION_CLEANUP_GUIDE.md to safely remove duplicates.
CRITICAL SAFETY RULES:
1. NEVER delete files directly - ALWAYS move to archive/
2. ALWAYS check for imports first
3. ALWAYS backup before any changes
4. ALWAYS test after changes
STEPS:
1. **Create Safety Backup**
```bash
mkdir -p archive/backup_$(date +%Y%m%d)
# Copy all .py files to backup
-
Check Import Dependencies For each file identified as duplicate in the guide:
- Search all .py files for imports
- If imported β₯1 time: KEEP THE FILE
- If imported 0 times: SAFE TO ARCHIVE
-
Move Duplicates to Archive Based on FILE_CONSOLIDATION_CLEANUP_GUIDE.md:
- control_group_evaluator.py β archive/
- enhanced_control_group_evaluator.py β archive/
- visualization_sample.py β archive/ (check first!)
-
Update Any Broken Imports If any file imported archived files:
- Update to use the kept version
- Example: control_group_evaluator β aaa2_control_group_comprehensive
-
Run Tests After each file moved:
pytest tests/test_smoke/ -v python main.py --check-deps
-
Create Migration Report Document in FILE_CONSOLIDATION_REPORT.md:
- Files archived
- Files kept
- Import updates made
- Test results
DELIVERABLES:
- Clean project (no duplicates)
- archive/ directory with old files
- All tests passing
- FILE_CONSOLIDATION_REPORT.md
**Expected Output:**
- ~3-5 files moved to archive/
- Updated imports (if needed)
- All tests passing
- Cleaner project structure
---
## π¦ PHASE 4: GITHUB ORGANIZATION (Priority: ββββ)
### Task 4.1: Implement Folder Structure
**Prompt for Claude Code:**
TASK: Organize Project for GitHub
Implement the folder structure from GITHUB_ORGANIZATION_GUIDE.md.
STEPS:
-
Create Target Directory Structure
pfaz_modules/ βββ pfaz01_dataset_generation/ βββ pfaz02_ai_training/ βββ ... βββ pfaz13_automl/ core_modules/ physics_modules/ analysis_modules/ visualization_modules/ tests/ docs/ scripts/ -
Move Files Systematically Use the mapping from GITHUB_ORGANIZATION_GUIDE.md:
Example:
- data_loader.py β pfaz_modules/pfaz01_dataset_generation/
- model_trainer.py β pfaz_modules/pfaz02_ai_training/
- semf_calculator.py β physics_modules/
-
Create init.py Files For each module directory:
# pfaz_modules/pfaz01_dataset_generation/__init__.py from .data_loader import DataLoader from .dataset_generator import DatasetGenerator # ... expose public API
-
Update Import Paths Throughout the project, update:
# OLD: from data_loader import DataLoader # NEW: from pfaz_modules.pfaz01_dataset_generation.data_loader import DataLoader
-
Update main.py Update all imports to use new structure
-
Create README.md Files For each pfaz_modules/ subdirectory:
- Brief description
- List of modules
- Usage examples
-
Test Everything
python main.py --check-deps python main.py --pfaz 1 --mode run # Test PFAZ1 pytest tests/ -v -
Create .gitignore Use template from GITHUB_ORGANIZATION_GUIDE.md
DELIVERABLES:
- Organized folder structure
- All imports working
- All tests passing
- README.md files
- .gitignore configured
**Expected Output:**
- Clean, organized folder structure
- All imports updated
- Tests passing
- Professional GitHub-ready layout
---
## π§ PHASE 5: MAIN.PY ENHANCEMENT (Priority: ββββ)
### Task 5.1: Update and Test main.py
**Prompt for Claude Code:**
TASK: Finalize main.py
Ensure main.py works perfectly with new structure.
STEPS:
-
Update All Imports Change to new pfaz_modules structure
-
Add QA Integration
if args.run_qa: from tests.qa_report_generator import run_all_tests results = run_all_tests() if not results['all_passed']: sys.exit(1)
-
Add Structure Validation
if args.check_structure: validate_directory_structure() validate_all_modules_present()
-
Improve Error Messages Make all error messages clear and actionable
-
Add Progress Indicators Better progress bars and status updates
-
Test All Modes
python main.py --interactive python main.py --run-all python main.py --pfaz 1 python main.py --check-deps python main.py --run-qa
DELIVERABLES:
- Updated main.py
- All modes working
- Clear error messages
- Good user experience
---
## π PHASE 6: FINAL VALIDATION (Priority: βββββ)
### Task 6.1: Complete System Test
**Prompt for Claude Code:**
TASK: Final System Validation
Perform complete end-to-end testing.
TEST CHECKLIST:
-
Installation Test β‘ Fresh virtual environment β‘ pip install -r requirements.txt β‘ No errors β‘ All dependencies installed
-
Structure Test β‘ All folders present β‘ All expected files exist β‘ No missing init.py
-
Import Test β‘ All modules import successfully β‘ No circular dependencies β‘ No broken imports
-
Smoke Test β‘ python main.py --help works β‘ python main.py --check-deps passes β‘ python main.py --check-structure passes
-
Unit Test β‘ pytest tests/test_units/ passes β‘ Coverage β₯50%
-
Integration Test β‘ pytest tests/test_integration/ passes β‘ PFAZ pipelines work
-
System Test (if time permits) β‘ python main.py --pfaz 1 --mode run succeeds β‘ Outputs generated correctly
-
QA Report β‘ Generate final QA report β‘ Document all metrics β‘ List any remaining issues
DELIVERABLES:
- FINAL_VALIDATION_REPORT.md
- All tests passing (or documented exceptions)
- System 100% ready
---
## π PHASE 7: DOCUMENTATION (Priority: βββ)
### Task 7.1: Update All Documentation
**Prompt for Claude Code:**
TASK: Finalize Documentation
Ensure all documentation is current and complete.
UPDATES NEEDED:
-
Main README.md
- Project overview
- Installation instructions
- Quick start guide
- New folder structure
- Testing instructions
-
INSTALLATION.md (docs/)
- Detailed setup steps
- Platform-specific instructions
- Troubleshooting
-
USAGE.md (docs/)
- How to run each PFAZ
- Command-line arguments
- Configuration options
-
TESTING.md (docs/)
- How to run tests
- Writing new tests
- CI/CD setup
-
CONTRIBUTING.md
- How to contribute
- Code style guide
- Pull request process
-
CHANGELOG.md
- Document all changes made
- Version 2.0.0 release notes
DELIVERABLES:
- Complete, accurate documentation
- Professional quality
- Easy to follow
---
## β
FINAL DELIVERABLES CHECKLIST
### Must Have (Before Declaring Complete):
β‘ PROJECT_AUDIT_REPORT.md β‘ Complete test suite (tests/) β‘ TEST_COVERAGE_REPORT.md (β₯50% coverage) β‘ FILE_CONSOLIDATION_REPORT.md β‘ Clean folder structure (pfaz_modules/, etc.) β‘ Updated main.py β‘ All imports working β‘ .gitignore configured β‘ README.md updated β‘ FINAL_VALIDATION_REPORT.md β‘ All smoke tests passing β‘ No critical issues
### Nice to Have:
β‘ Integration tests passing β‘ System tests passing β‘ Coverage β₯80% β‘ INSTALLATION.md β‘ USAGE.md β‘ CONTRIBUTING.md
---
## π¨ CRITICAL RULES
### DO:
1. β
**Always backup** before making changes
2. β
**Test after** every significant change
3. β
**Document** what you do
4. β
**Ask questions** if unclear
5. β
**Be systematic** - follow the phases in order
### DO NOT:
1. β **Never delete files** without checking imports
2. β **Never skip testing** - could break everything
3. β **Never assume** - always verify
4. β **Never rush** - quality over speed
5. β **Never modify** without understanding
---
## π COMMUNICATION
### Progress Updates
After each phase, report:
PHASE X COMPLETE
β Completed:
- Task 1
- Task 2
- Issue 1 (resolved)
π Metrics:
- Coverage: X%
- Files: Y
- Tests: Z passing
π― Next: Phase Y
### If Stuck
Ask for help with:
HELP NEEDED
Context: [What you're trying to do] Issue: [What's not working] Tried: [What you've attempted] Question: [Specific question]
---
## π― SUCCESS CRITERIA
Project is **COMPLETE** when:
β 100% of expected files present β 0 duplicate files β All tests passing β Coverage β₯50% (target: 80%) β Clean folder structure β Documentation complete β main.py fully functional β No broken imports β No critical issues β Professional quality
---
## π GETTING STARTED
### Your First Command:
```bash
# Start with Phase 1: Project Audit
# Read MASTER_PROJECT_CHECKLIST.md
# Then execute Task 1.1
Phase 1: Audit β 2-3 hours
Phase 2: QA System β 4-6 hours
Phase 3: Consolidation β 1-2 hours
Phase 4: Organization β 2-3 hours
Phase 5: main.py β 1-2 hours
Phase 6: Validation β 2-3 hours
Phase 7: Documentation β 2-3 hours
TOTAL: 14-22 hours (2-3 days)
- MASTER_PROJECT_CHECKLIST.md - What needs to be done
- QA_ENGINEER_MODULE_DESIGN.md - How to build QA
- FILE_CONSOLIDATION_CLEANUP_GUIDE.md - How to clean up
- GITHUB_ORGANIZATION_GUIDE.md - How to organize
- EXECUTIVE_SUMMARY.md - Why it all matters
You're completing the final 3% of an incredible 97% complete project. This is high-stakes work - the quality of your execution determines whether this goes from "good research project" to "production-ready professional system."
You've got this! π
Follow the phases systematically, test everything, and we'll have a 100% complete, professional-quality nuclear physics AI system.
Let's finish strong! πͺ
Prepared by: Claude (Anthropic)
For: Claude Code AI Assistant
Date: November 21, 2025
Version: 2.0.0 - FINAL
Status: Ready for execution
π€β¨π
# Claude Code, your first task:
# 1. Read this entire README
# 2. Read MASTER_PROJECT_CHECKLIST.md
# 3. Execute Phase 1, Task 1.1 (Project Audit)
# 4. Report results
# 5. Await next instruction
Good luck! π