Event set and event browser support for custom events

In Release 2019.0, we introduced the concepts of an “Event Object” and an “Event Set.” Previously, there was no easy way to persist or store event inputs within or outside an Adams Car session. This made the ability to institute standard analysis procedures that were repeatable and consistent.  The concept of Event Objects was developed to address this need. Users could create and archive via files a consistent set of virtual test events using event objects. Each event object contains all the information required to create and run a specific simulation. The Event object combines what was in several separate files and makes the full definition of an event persistent. The user can run the same event in the same way with a different vehicle or vehicle variant.

Event sets are a suite or combination of specific event object instances and enabled the ability to test a vehicle model across a suite of events. Users could run design studies on a single event and on a combination of events to gauge vehicle responses. To aid in the user experience while leveraging these new features, Release 2019 also introduced a new Event Browser (similar to the model browser).

The event browser displays the grouping of events into event sets. Uses can interact with the events and events sets through the event browser to execute them, save them to a file, or modify them. Users can also monitor the status of an executed event via the event bowser.

The Event browser and Event Set features have supported only standard Adams Car events so far. In Adams 2021, custom user events are supported. The user can now convert a custom event macro into an Adams Car event object. One can then modify/update event inputs and take advantage of all the Adams Car event set, and event browser capabilities described earlier.

The conversion to an event set object is accomplished via the following CMD commands.

1. acar toolkit event convert macro=<macro_object> output_suffix=<output_suffix parameter> This command converts the custom event macro into an event class
2. acar toolkit event register macro=<macro_object> python_file=<python file created in step 1> plugin=<plugin name if applicable> This command registers the generated event class from step 1 to the existing macro.
3. acar analysis event create name=<output_prefix>_<output_suffix> class=<macro_reference> model=<model name> This command creates an event instance for the macro or dialog box execution commands. This event instance then becomes available in the event browser with all the event inputs exposed.

To learn more about the Event Set and Event Browser features and what they offer, watch these videos:

Leverage Adams Car Event Settings Consistently Across Projects and Team Members

Enabling Smarter Simulation Workflows using Event Sets and Variants in Adams Car