fix: modeling solidification workflow and image#4830
fix: modeling solidification workflow and image#4830MohammedAnsys wants to merge 5 commits intomainfrom
Conversation
There was a problem hiding this comment.
Pull request overview
This PR updates the solidification modeling workflow example to fix visualization issues and a floating-point exception error by improving the graphics rendering approach and ensuring proper case state management.
Changes:
- Replaced direct contour display with Scene-based visualization for proper rendering
- Added case reload before transient simulation to prevent floating-point exceptions
- Renamed duplicate contour instance to avoid naming conflicts
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Up to standards ✅🟢 Issues
|
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 2 out of 3 changed files in this pull request and generated 1 comment.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| solver.settings.file.read_case_data(file_name="steady_state") | ||
| solver_general_settings.solver.time = "unsteady-1st-order" # First-order implicit |
There was a problem hiding this comment.
read_case_data(file_name="steady_state") passes a name without a .cas* extension. In the settings API, the corresponding data filename is inferred by replacing .cas with .dat; without .cas in the name, the case/data arguments can end up identical, which can make Fluent look for the wrong data file. Consider writing/reading with an explicit case filename like steady_state.cas.h5 (so the matching .dat.h5 is derived correctly).
The solidification example had visualization issues, along with a floating-point exception error.
Changes:
Use Scene object for proper visualization
Add case reload before transient simulation
Fix duplicate contour naming
Update static image
Impact: Correct visualizations and proper workflow execution