Files
Atomizer/CHANGELOG.md
Anto01 8b14f6e800 feat: Add robust NX expression import system for all expression types
Major Enhancement:
- Implemented .exp file-based expression updates via NX journal scripts
- Fixes critical issue with feature-linked expressions (e.g., hole_count)
- Supports ALL NX expression types including binary-stored ones
- Full 4D design space validation completed successfully

New Components:
1. import_expressions.py - NX journal for .exp file import
   - Uses NXOpen.ExpressionCollection.ImportFromFile()
   - Replace mode overwrites existing values
   - Automatic model update and save
   - Comprehensive error handling

2. export_expressions.py - NX journal for .exp file export
   - Exports all expressions to text format
   - Used for unit detection and verification

3. Enhanced nx_updater.py
   - New update_expressions_via_import() method
   - Automatic unit detection from .exp export
   - Creates study-variable-only .exp files
   - Replaces fragile binary .prt editing

Technical Details:
- .exp Format: [Units]name=value (e.g., [MilliMeter]beam_length=5000)
- Unitless expressions: name=value (e.g., hole_count=10)
- Robustness: Native NX functionality, no regex failures
- Performance: < 1 second per update operation

Validation:
- Simple Beam Optimization study (4D design space)
  * beam_half_core_thickness: 10-40 mm
  * beam_face_thickness: 10-40 mm
  * holes_diameter: 150-450 mm
  * hole_count: 5-15 (integer)

Results:
 3-trial validation completed successfully
 All 4 variables update correctly in all trials
 Mesh adaptation verified (hole_count: 6, 15, 11 → different mesh sizes)
 Trial 0: 5373 CQUAD4 elements (6 holes)
 Trial 1: 5158 CQUAD4 + 1 CTRIA3 (15 holes)
 Trial 2: 5318 CQUAD4 (11 holes)

Problem Solved:
- hole_count expression was not updating with binary .prt editing
- Expression stored in feature parameter, not accessible via text regex
- Binary format prevented reliable text-based updates

Solution:
- Use NX native expression import/export
- Works for ALL expressions (text and binary-stored)
- Automatic unit handling
- Model update integrated in journal

Documentation:
- New: docs/NX_EXPRESSION_IMPORT_SYSTEM.md (comprehensive guide)
- Updated: CHANGELOG.md with Phase 3.2 progress
- Study: studies/simple_beam_optimization/ (complete example)

Files Added:
- optimization_engine/import_expressions.py
- optimization_engine/export_expressions.py
- docs/NX_EXPRESSION_IMPORT_SYSTEM.md
- studies/simple_beam_optimization/ (full study)

Files Modified:
- optimization_engine/nx_updater.py
- CHANGELOG.md

Compatibility:
- NX 2412 tested and verified
- Python 3.10+
- Works with all NX expression types

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-17 12:34:06 -05:00

4.7 KiB

Changelog

All notable changes to Atomizer will be documented in this file.

The format is based on Keep a Changelog.

[Unreleased]

Phase 3.2 - Integration & NX Enhancements (In Progress)

Added

  • NX Expression Import System (2025-11-17)

    • Robust .exp file-based expression updates via NX journal scripts
    • Supports ALL NX expression types including binary-stored ones
    • Automatic unit detection and formatting
    • Fixes issue with hole_count and other feature-linked expressions
    • Documentation: NX_EXPRESSION_IMPORT_SYSTEM.md
    • New journal: import_expressions.py for .exp file import
    • Enhanced nx_updater.py with update_expressions_via_import() method
  • 4D Design Space Validation (2025-11-17)

    • Validated full 4-variable optimization (beam_half_core_thickness, beam_face_thickness, holes_diameter, hole_count)
    • All variables now updating correctly in optimization loop
    • Mesh adaptation verified across different hole_count values

Phase 2 - LLM Integration (Completed 85%)

  • Natural language interface for optimization configuration
  • Feature registry with capability catalog
  • Claude skill for Atomizer navigation
  • LLM workflow analyzer and extractor orchestration
  • Dynamic code generation for hooks and extractors

[0.2.0] - 2025-01-16

Phase 1 - Plugin System & Infrastructure

Added

  • Plugin Architecture

    • Hook manager with lifecycle execution at pre_solve, post_solve, and post_extraction points
    • Plugin auto-discovery from optimization_engine/plugins/ directory
    • Priority-based hook execution
    • Context passing system for hooks (output_dir, trial_number, design_variables, results)
  • Logging Infrastructure

    • Detailed per-trial logs in optimization_results/trial_logs/
      • Complete iteration trace with timestamps
      • Design variables, configuration, execution timeline
      • Extracted results and constraint evaluations
    • High-level optimization progress log (optimization.log)
      • Configuration summary header
      • Trial START and COMPLETE entries (one line per trial)
      • Compact format for easy progress monitoring
  • Logging Plugins

    • detailed_logger.py - Creates detailed trial logs
    • optimization_logger.py - Creates high-level optimization.log
    • log_solve_complete.py - Appends solve completion to trial logs
    • log_results.py - Appends extracted results to trial logs
    • optimization_logger_results.py - Appends results to optimization.log
  • Project Organization

    • Studies folder structure with standardized layout
    • Comprehensive studies documentation (studies/README.md)
    • Model files organized in model/ subdirectory (.prt, .sim, .fem)
    • Intelligent path resolution system (atomizer_paths.py)
    • Marker-based project root detection
  • Test Suite

    • test_hooks_with_bracket.py - Hook validation test (3 trials)
    • run_5trial_test.py - Quick integration test (5 trials)
    • test_journal_optimization.py - Full optimization test

Changed

  • Renamed examples/ folder to studies/
  • Moved bracket example to studies/bracket_stress_minimization/
  • Consolidated FEA files into model/ subfolder
  • Updated all test scripts to use atomizer_paths for imports
  • Runner now passes output_dir to all hook contexts

Removed

  • Obsolete test scripts from examples/ (14 files deleted)
  • optimization_logs/ and optimization_results/ from root directory

Fixed

  • Log files now correctly generated in study-specific optimization_results/ folder
  • Path resolution works regardless of script location
  • Hooks properly registered with register_hooks() function

[0.1.0] - 2025-01-10

Initial Release

Core Features

  • Optuna integration with TPE sampler
  • NX journal integration for expression updates and simulation execution
  • OP2 result extraction (stress, displacement)
  • Study management with folder-based isolation
  • Web dashboard for real-time monitoring
  • Precision control (4-decimal rounding for mm/degrees/MPa)
  • Crash recovery and optimization resumption

Development Timeline

  • Phase 1 ( Completed 2025-01-16): Plugin system & hooks
  • Phase 2 (🟡 Starting): LLM interface with natural language configuration
  • Phase 3 (Planned): Dynamic code generation for custom objectives
  • Phase 4 (Planned): Intelligent analysis and surrogate quality assessment
  • Phase 5 (Planned): Automated HTML/PDF report generation
  • Phase 6 (Planned): NX MCP server with full API documentation
  • Phase 7 (Planned): Self-improving feature registry

Maintainer: Antoine Polvé (antoine@atomaste.com) License: Proprietary - Atomaste © 2025