Files
Anto01 0a7cca9c6a feat: Complete Phase 2.5-2.7 - Intelligent LLM-Powered Workflow Analysis
This commit implements three major architectural improvements to transform
Atomizer from static pattern matching to intelligent AI-powered analysis.

## Phase 2.5: Intelligent Codebase-Aware Gap Detection 

Created intelligent system that understands existing capabilities before
requesting examples:

**New Files:**
- optimization_engine/codebase_analyzer.py (379 lines)
  Scans Atomizer codebase for existing FEA/CAE capabilities

- optimization_engine/workflow_decomposer.py (507 lines, v0.2.0)
  Breaks user requests into atomic workflow steps
  Complete rewrite with multi-objective, constraints, subcase targeting

- optimization_engine/capability_matcher.py (312 lines)
  Matches workflow steps to existing code implementations

- optimization_engine/targeted_research_planner.py (259 lines)
  Creates focused research plans for only missing capabilities

**Results:**
- 80-90% coverage on complex optimization requests
- 87-93% confidence in capability matching
- Fixed expression reading misclassification (geometry vs result_extraction)

## Phase 2.6: Intelligent Step Classification 

Distinguishes engineering features from simple math operations:

**New Files:**
- optimization_engine/step_classifier.py (335 lines)

**Classification Types:**
1. Engineering Features - Complex FEA/CAE needing research
2. Inline Calculations - Simple math to auto-generate
3. Post-Processing Hooks - Middleware between FEA steps

## Phase 2.7: LLM-Powered Workflow Intelligence 

Replaces static regex patterns with Claude AI analysis:

**New Files:**
- optimization_engine/llm_workflow_analyzer.py (395 lines)
  Uses Claude API for intelligent request analysis
  Supports both Claude Code (dev) and API (production) modes

- .claude/skills/analyze-workflow.md
  Skill template for LLM workflow analysis integration

**Key Breakthrough:**
- Detects ALL intermediate steps (avg, min, normalization, etc.)
- Understands engineering context (CBUSH vs CBAR, directions, metrics)
- Distinguishes OP2 extraction from part expression reading
- Expected 95%+ accuracy with full nuance detection

## Test Coverage

**New Test Files:**
- tests/test_phase_2_5_intelligent_gap_detection.py (335 lines)
- tests/test_complex_multiobj_request.py (130 lines)
- tests/test_cbush_optimization.py (130 lines)
- tests/test_cbar_genetic_algorithm.py (150 lines)
- tests/test_step_classifier.py (140 lines)
- tests/test_llm_complex_request.py (387 lines)

All tests include:
- UTF-8 encoding for Windows console
- atomizer environment (not test_env)
- Comprehensive validation checks

## Documentation

**New Documentation:**
- docs/PHASE_2_5_INTELLIGENT_GAP_DETECTION.md (254 lines)
- docs/PHASE_2_7_LLM_INTEGRATION.md (227 lines)
- docs/SESSION_SUMMARY_PHASE_2_5_TO_2_7.md (252 lines)

**Updated:**
- README.md - Added Phase 2.5-2.7 completion status
- DEVELOPMENT_ROADMAP.md - Updated phase progress

## Critical Fixes

1. **Expression Reading Misclassification** (lines cited in session summary)
   - Updated codebase_analyzer.py pattern detection
   - Fixed workflow_decomposer.py domain classification
   - Added capability_matcher.py read_expression mapping

2. **Environment Standardization**
   - All code now uses 'atomizer' conda environment
   - Removed test_env references throughout

3. **Multi-Objective Support**
   - WorkflowDecomposer v0.2.0 handles multiple objectives
   - Constraint extraction and validation
   - Subcase and direction targeting

## Architecture Evolution

**Before (Static & Dumb):**
User Request → Regex Patterns → Hardcoded Rules → Missed Steps 

**After (LLM-Powered & Intelligent):**
User Request → Claude AI Analysis → Structured JSON →
├─ Engineering (research needed)
├─ Inline (auto-generate Python)
├─ Hooks (middleware scripts)
└─ Optimization (config) 

## LLM Integration Strategy

**Development Mode (Current):**
- Use Claude Code directly for interactive analysis
- No API consumption or costs
- Perfect for iterative development

**Production Mode (Future):**
- Optional Anthropic API integration
- Falls back to heuristics if no API key
- For standalone batch processing

## Next Steps

- Phase 2.8: Inline Code Generation
- Phase 2.9: Post-Processing Hook Generation
- Phase 3: MCP Integration for automated documentation research

🚀 Generated with Claude Code

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-16 13:35:41 -05:00

126 lines
4.3 KiB
Python

"""
Detailed Logger Plugin
Logs comprehensive information about each optimization iteration to a file.
Creates a detailed trace of all steps for debugging and analysis.
"""
from typing import Dict, Any, Optional
from pathlib import Path
from datetime import datetime
import json
import logging
logger = logging.getLogger(__name__)
def detailed_iteration_logger(context: Dict[str, Any]) -> Optional[Dict[str, Any]]:
"""
Log detailed information about the current trial to a timestamped log file.
Args:
context: Hook context containing:
- trial_number: Current trial number
- design_variables: Dict of variable values
- sim_file: Path to simulation file
- working_dir: Current working directory
- config: Full optimization configuration
Returns:
Dict with log file path
"""
trial_num = context.get('trial_number', '?')
design_vars = context.get('design_variables', {})
sim_file = context.get('sim_file', 'unknown')
config = context.get('config', {})
# Get the output directory from context (passed by runner)
output_dir = Path(context.get('output_dir', 'optimization_results'))
# Create logs subdirectory within the study results
log_dir = output_dir / 'trial_logs'
log_dir.mkdir(parents=True, exist_ok=True)
# Create trial-specific log file
timestamp = datetime.now().strftime('%Y%m%d_%H%M%S')
log_file = log_dir / f'trial_{trial_num:03d}_{timestamp}.log'
with open(log_file, 'w') as f:
f.write("=" * 80 + "\n")
f.write(f"OPTIMIZATION ITERATION LOG - Trial {trial_num}\n")
f.write("=" * 80 + "\n")
f.write(f"Timestamp: {datetime.now().isoformat()}\n")
f.write(f"Output Directory: {output_dir}\n")
f.write(f"Simulation File: {sim_file}\n")
f.write("\n")
f.write("-" * 80 + "\n")
f.write("DESIGN VARIABLES\n")
f.write("-" * 80 + "\n")
for var_name, var_value in design_vars.items():
f.write(f" {var_name:30s} = {var_value:12.4f}\n")
f.write("\n")
f.write("-" * 80 + "\n")
f.write("OPTIMIZATION CONFIGURATION\n")
f.write("-" * 80 + "\n")
config = context.get('config', {})
# Objectives
f.write("\nObjectives:\n")
for obj in config.get('objectives', []):
f.write(f" - {obj['name']}: {obj['direction']} (weight={obj.get('weight', 1.0)})\n")
# Constraints
constraints = config.get('constraints', [])
if constraints:
f.write("\nConstraints:\n")
for const in constraints:
f.write(f" - {const['name']}: {const['type']} limit={const['limit']} {const.get('units', '')}\n")
# Settings
settings = config.get('optimization_settings', {})
f.write("\nOptimization Settings:\n")
f.write(f" Sampler: {settings.get('sampler', 'unknown')}\n")
f.write(f" Total trials: {settings.get('n_trials', '?')}\n")
f.write(f" Startup trials: {settings.get('n_startup_trials', '?')}\n")
f.write("\n")
f.write("-" * 80 + "\n")
f.write("EXECUTION TIMELINE\n")
f.write("-" * 80 + "\n")
f.write(f"[{datetime.now().strftime('%H:%M:%S')}] PRE_SOLVE: Trial {trial_num} starting\n")
f.write(f"[{datetime.now().strftime('%H:%M:%S')}] Design variables prepared\n")
f.write(f"[{datetime.now().strftime('%H:%M:%S')}] Waiting for model update...\n")
f.write("\n")
f.write("-" * 80 + "\n")
f.write("NOTES\n")
f.write("-" * 80 + "\n")
f.write("This log will be updated by subsequent hooks during the optimization.\n")
f.write("Check post_solve and post_extraction logs for complete results.\n")
f.write("\n")
logger.info(f"Trial {trial_num} log created: {log_file}")
return {
'log_file': str(log_file),
'trial_number': trial_num,
'logged': True
}
def register_hooks(hook_manager):
"""
Register this plugin's hooks with the manager.
This function is called automatically when the plugin is loaded.
"""
hook_manager.register_hook(
hook_point='pre_solve',
function=detailed_iteration_logger,
description='Create detailed log file for each trial',
name='detailed_logger',
priority=5 # Run very early to capture everything
)