Replies: 2 comments
-
We decided to separate |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Bottom line up front: I'm trying to understand the differences between the various ways you can specify "temperature" in a Fastconformer hybrid RNNT-CTC model and what they mean.
I've been working with some coworkers to use riva's wfst decoder (https://github.com/nvidia-riva/riva-asrlib-decoder/blob/main/src/riva/asrlib/decoder/test_decoder.py). I trained some models that were fine tuned from https://catalog.ngc.nvidia.com/orgs/nvidia/teams/nemo/models/stt_multilingual_fastconformer_hybrid_large_pc but i've been getting an error when i try to use the WFST decoder:
I found a model that did work and discovered the primary difference between our model configs is that mine says
whereas the model that does work has:
As far as i can see, temperature can be specified in multiple places in the config though many are set to
DEPRECATED
, e.g. decoding.confidence_cfg.measure_cfg.temperature=DEPRECATED, decoding.greedy.confidence_measure_cfg.temperature=DEPRECATED, decoding.beam.softmax_temperature=1.0, decoding.temperature=1.0 (and the same flags exist under aux_ctc as well).So my question is this: what do the various
temperature
fields actually refer to and which one(s) are in active use? Any advice will be helpful. Thanks!Beta Was this translation helpful? Give feedback.
All reactions