Collaboration diagram for moot::mootHMM::ViterbiPathNode:
Public Attributes | |
| ViterbiNode * | node |
| ViterbiPathNode * | path_next |
Detailed Description
Type for a Viterbi path-node. It's faster to use the (ViterbiNode*)s directly, if you can deal with reverse order.
All relevant allocation (and de-allocation) is handled internally: All ViterbiPathNode pointers returned by any mootHMM method call are de-allocated on clear(). On viterbi_clear(), they're wiped and tossed onto an internal trash-stack: this is marginally faster than re-allocation.
- Warning
- Don't rely on the data in your (ViterbiPathNode*)s remaining the same over multiple mootHMM method calls: get what you need, and then lose the nodes.
Member Data Documentation
◆ node
| ViterbiNode* moot::mootHMM::ViterbiPathNode::node |
◆ path_next
| ViterbiPathNode* moot::mootHMM::ViterbiPathNode::path_next |
Corresponding pillar-level trellis node
Referenced by moot::mootHMM::viterbi_get_pathnode().
The documentation for this struct was generated from the following file:
