You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we have TimedAction statement in the BA, the time unit is not set in the model after name resolution.
Expected and Current Behavior
When writing
``àadl
computation(4 us..5us)
in a BA subclause, the corresponding model after parsing and name resolution does not contain the unit.
## Environment
* **OSATE Version**: 2.3.5
* **Operating System**: Linux
The text was updated successfully, but these errors were encountered:
Summary
When we have TimedAction statement in the BA, the time unit is not set in the model after name resolution.
Expected and Current Behavior
When writing
``àadl
computation(4 us..5us)
The text was updated successfully, but these errors were encountered: