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
Several of OSATE's model analyses (e.g., weight totals) have handlers with a public invoke method that make it possible to run the analyses programmatically from, e.g., ANT tasks.
For those analyses that do not have such a method, running them programmatically from outside an Eclipse UI execution event is very difficult. For the flow latency analysis, for example, one potentially has to go through two dialog boxes (for the analysis's five boolean parameters and for a list of system operation modes).
Ideally, each analysis handler should have a public method allowing the analysis to be run independent of the Eclipse UI harness.
The text was updated successfully, but these errors were encountered:
Several of OSATE's model analyses (e.g., weight totals) have handlers with a public
invoke
method that make it possible to run the analyses programmatically from, e.g., ANT tasks.For those analyses that do not have such a method, running them programmatically from outside an Eclipse UI execution event is very difficult. For the flow latency analysis, for example, one potentially has to go through two dialog boxes (for the analysis's five boolean parameters and for a list of system operation modes).
Ideally, each analysis handler should have a public method allowing the analysis to be run independent of the Eclipse UI harness.
The text was updated successfully, but these errors were encountered: