# avt_analysis2notify

The avt_analysis2notify adapter receives OVM data from its analysis_export, converts it to VMM, then indicates the configured event notification, passing the converted data as vmm_data-based status. VMM components that have registered a callback for the notification will received the converted data

See also the avt_analysis2notify example.

Summary

avt_analysis2notify
The avt_analysis2notify adapter receives OVM data from its analysis_export, converts it to VMM, then indicates the configured event notification, passing the converted data as vmm_data-based status.
Class Hierarchy
ovm_component
avt_analysis2notify
Class Declaration
> class avt_analysis2notify #(
> | type | OVM | = | int,
> |  | VMM | = | int,
> |  | OVM2VMM | = | int
> ) extends ovm_component
Ports |
analysis_export | The adapter receives OVM transactions via this analysis export.
Variables |
notify | The notify object that this adapter uses to indicate the RECEIVED event notification.
RECEIVED | The notification id that this adapter indicates upon receipt of OVM data from its analysis_export.
Methods |
new | Creates a new analysis-to-notify adapter with the given name and optional parent; the notify and notification_id together specify the notification event that this adapter will indicate upon receipt of a transaction on its analysis_export.
write | The write method, called via the analysis_export, converts an incoming OVM transaction to its VMM counterpart, then indicates the configured <RECEIVE> notification, passing the converted data as status.

### Ports

### analysis_export

The adapter receives OVM transactions via this analysis export.

### Variables

### notify

> vmm_notify notify

The notify object that this adapter uses to indicate the RECEIVED event notification.

### RECEIVED

> int RECEIVED

The notification id that this adapter indicates upon receipt of OVM data from its analysis_export.

### Methods

### new

Creates a new analysis-to-notify adapter with the given name and optional parent; the notify and notification_id together specify the notification event that this adapter will indicate upon receipt of a transaction on its analysis_export.

If the notify handle is not supplied or null, the adapter will create one and assign it to the notify property. If the notification_id is not provided, the adapter will configure a ONE_SHOT notification and assign it to the RECEIVED property.

### write

> virtual function void write( | OVM | t | )

The write method, called via the analysis_export, converts an incoming OVM transaction to its VMM counterpart, then indicates the configured <RECEIVE> notification, passing the converted data as status.

> class avt_analysis2notify #( | type | OVM | = | int,
> |  | VMM | = | int,
> |  | OVM2VMM | = | int | ) extends ovm_component

The avt_analysis2notify adapter receives OVM data from its analysis_export, converts it to VMM, then indicates the configured event notification, passing the converted data as vmm_data-based status.
The adapter receives OVM transactions via this analysis export.

> vmm_notify notify

The notify object that this adapter uses to indicate the RECEIVED event notification.

> int RECEIVED

The notification id that this adapter indicates upon receipt of OVM data from its analysis_export.

> virtual function void write( | OVM | t | )

The write method, called via the analysis_export, converts an incoming OVM transaction to its VMM counterpart, then indicates the configured RECEIVE notification, passing the converted data as status.
This example shows how to use the avt_analysis2notify adapter to connect an OVM publisher to a VMM xactor that receives data via vmm_notify event notifications.