`GetDataIdentifier`¶

Get a diagnostic identifier (string) for the given data, if available.

This node uses a precedence of heuristics to construct a reasonably short but complete identifier suitable for eg diagnostics. Note that this node should mainly be used for debugging and diagnostics, rather than for production systems, since the format of the identifier is not guaranteed to be stable. In such cases, it is recommended to form an identifier in a more prescribed way, for example using the Get Nested node. Version 0.5.0

Ports/Properties¶

`data`¶

Data to process

verbose name: Data
default value: None
port type: DataPort
value type: AnyNumeric (can be None)
data direction: IN

`identifier`¶

Data identifier.

verbose name: Identifier
default value: None
port type: DataPort
value type: str (can be None)
data direction: OUT

`if_inconsistent`¶

What to do if multiple inconsistent identifiers apply to the data.

verbose name: If Inconsistent
default value: warn
port type: EnumPort
value type: str (can be None)

`set_breakpoint`¶

Set a breakpoint on this node. If this is enabled, your debugger (if one is attached) will trigger a breakpoint.

verbose name: Set Breakpoint (Debug Only)
default value: False
port type: BoolPort
value type: bool (can be None)

`metadata`¶

User-definable meta-data associated with the node. Usually reserved for technical purposes.

verbose name: Metadata
default value: {}
port type: DictPort
value type: dict (can be None)

GetDataIdentifier¶

Ports/Properties¶

data¶

identifier¶

if_inconsistent¶

set_breakpoint¶