|
|
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 |
|
|
|
be3b9ee5d5
|
feat: Add complete optimization runner pipeline
Implement core optimization engine with:
- OptimizationRunner class with Optuna integration
- NXParameterUpdater for updating .prt file expressions
- Result extractor wrappers for OP2 files
- Complete end-to-end example workflow
Features:
- runner.py: Main optimization loop, multi-objective support, constraint handling
- nx_updater.py: Binary .prt file parameter updates (tested successfully)
- extractors.py: Wrappers for mass/stress/displacement extraction
- run_optimization.py: Complete example showing full workflow
NX Updater tested with bracket example:
- Successfully found 4 expressions (support_angle, tip_thickness, p3, support_blend_radius)
- Updated support_angle 30.0 -> 33.0 and verified
Next steps:
- Install pyNastran for OP2 extraction
- Integrate NX solver execution
- Replace dummy extractors with real OP2 readers
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
|
2025-11-15 10:29:33 -05:00 |
|
