Katana uses Ops to build and modify the attribute state of your scene.  Some of the ops that set attributes are visible ops have a visible effect within the interactive katana session.  But , but some run behind the scenes - terminal ops, implicit resolvers, deferred op scripts.  If you write your own terminal ops , or are trying to debug why a certain an attribute isn't making it to the render, it can be extremely useful to be able to debug inspect the attribute state at the point your op runs.  The PrmanOpDebug node lets you inspect the full suite of ops - interactive render filters, implicit resolvers, and terminal opsInteractive Render Filters (IRFs), Implicit Resolvers, and Terminal Ops.

How to use the node

1. Insert the node at the end of your Node Graph - right before the Render node if there is one
2. The node will automatically populate with the current Interactive Render Filter ( IRF), Implicit Resolver, and Terminal Op state.
3. You can inspect view the full list of each of these op types in the node by expanding the groups ops by expanding each group in the Parameters Tab
4. To view the affect of a certain Op, you can right click on the op name and select "View at Location"
   
5. You can view the attribute state in Katana's Attributes Tab.
6. Note that this node wondoesn't pick up any changes to your scene or available Ops and IRFs's Op and IRF state after it is created.  There is a button to refresh each op type under their respective "user" group parameters groups.