[Embedding] No scenes available for some of the result object
- Dominant language
- Python
- Stars
- 83
- Forks
- 37
- Avg merge
- 1d 3m
- Merged PRs (30d)
- 26
Description
From 26r1 onwards plotting result object is possible but some scenes are not available.
```
WARNING - - app - log_warning - No scene available for object Ansys.ACT.Automation.Mechanical.Results.ThermalResults.TemperatureResult!
WARNING - - app - log_warning - No scene available for object Ansys.ACT.Automation.Mechanical.Results.ThermalResults.TemperatureResult!
WARNING - - app - log_warning - Unexpected node: Ansys.Mechanical.Scenegraph.LineTessellationResultNodey
WARNING - - app - log_warning - Unexpected node: Ansys.Mechanical.Scenegraph.LineTessellationResultNode
WARNING - - app - log_warning - No scene available for object Ansys.ACT.Automation.Mechanical.Results.ProbeResults.ForceReaction!
WARNING - - app - log_warning - No scene available for object Ansys.ACT.Automation.Mechanical.Results.AcousticResults.AcousticPressureResult!
WARNING - - app - log_warning - No scene available for object Ansys.ACT.Automation.Mechanical.Results.AcousticResults.AcousticTotalVelocityResult!
WARNING - - app - log_warning - No scene available for object Ansys.ACT.Automation.Mechanical.Results.AcousticResults.AcousticSoundPressureLevel!
WARNING - - app - log_warning - No scene available for object Ansys.ACT.Automation.Mechanical.Results.AcousticResults.AcousticDirectionalVelocityResult!
WARNING - - app - log_warning - No scene available for object Ansys.ACT.Automation.Mechanical.Results.AcousticResults.AcousticKineticEnergy!
```
Contributor guide
Research direction
No files, tests, or entry points are named. Start by reproducing the embedding plot with the listed Thermal, Probe, and Acoustic result objects, then trace how scenes are selected for each result type; done means supported results have scenes without the reported warnings or unexpected-node messages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100