Hi,
I am trying to get a sense of the kinds of inputs that DM gets from the NLU pipeline.
Is it only the output from the end of the pipeline that gets passed to the DM?
As a newbie, my sense is that NLU only sends intents and entities to the DM. All of the examples of NLU output shown at Components and intent and/or entity information. (If there is a spec describing the full extent of stuff DM can receive from NLU, please do tell! (-: — haven’t been able to find one yet)
I mean, yeah, there’s a lot of fine-grained detail about intents and entities (e.g. confidences, intent rankings, start and end char positions for entities etc etc).
However, my question is this: is there important non-entity and non-intent info being passed from the various native Rasa pipeline configurations to the DM?
For example, does, say, the tokenizer pass info to the DM?
Here’s the motivation for my question: we have a strong need to use our in house NLU. I’ve been reading up on helpful resources such as Using Custom NLU with Rasa X - #5 by Tobias_Wochinger and NLU-Only Server.
We take interest in @Tobias_Wochinger’s comment at Using Custom NLU with Rasa X - #5 by Tobias_Wochinger where he says " I can only strongly recommend to use the integrated NLU in Rasa Open Source" and “team which is continuously working on improvements for NLU and also integrating the dialogue management with the NLU predictions more and more which should lead to more robust decisions by the bot”.
So, we are trying to get a sense of the nature of the tight integration between Rasa NLU and Rasa DM.
If Rasa NLU / Rasa DM integration is built around the idea that only intent and entity related into gets passed from NLU to DM, that’s one thing. But if all sorts of random info apart from intents and entities get passed to DM, that’s another thing. (e.g. we stand to loose more if we roll our own NLU).
Even worse would be if Rasa DM passed information back to the Rasa NLU. Does this happen? (If so, this would be an even bigger “loose” for those of us wanting to use our own NLU bc our in house NLU (currently) does not understand such inputs).