From GridLAB-D Wiki
Jump to: navigation, search

event_trace - Event trace control variable Template:NEW30

Synopsis

Command line
host% gridlabd -D|--define event_trace=NONE|INIT|PRECOMMIT|PRESYNC|SYNC|POSTSYNC|COMMIT||FINALIZE|HEARTBEAT ...
GLM
#set event_trace=NONE|INIT|PRECOMMIT|PRESYNC|SYNC|POSTSYNC|COMMIT||FINALIZE|HEARTBEAT

Description

Events can be traced by setting the appropriate member of the event_trace set. A trace output resembles the following

event_trace event : object-name [ from -> to ]

The event indicates the type of event being traced. The object-name indicates the object for which the event was caught. Objects may be filtered using the event_trace_filter global variable.

The from and to dates indicates the date and times of the event, the meaning of which vary depending on the event as shown in Table 1.

Table 1 - Meaning of from and to event trace date/times

Event type
Meaning of from date
Meaning of to date
INIT starttime stoptime
PRECOMMIT clock tnext
PRESYNC tdesired tnext
SYNC tdesired tnext
POSTSYNC tdesired tnext
COMMIT tdesired tnext
FINALIZE clock stoptime
HEARTBEAT clock tnext

NONE

No events are traced.

INIT

Initialization events are traced.

PRECOMMIT

Pre-commit events are traced.

PRESYNC

Pre-sync events are traced.

SYNC

Sync events are traced.

POSTSYNC

Post-sync events are traced.

COMMIT

Commit events are traced.

FINALIZE

Finalize events are traced.

HEARTBEAT

Heartbeat events are traced.

See also