The doc says ?val will retirve a value
I get the following..
mha [7] ?val:mha.sort_output.mhaconfig_out.srate
(mha_parser) Invalid query mode: "val"
What am I doing wrong?
Dan..
?val
-
- Posts: 118
- Joined: Mon Jun 24, 2019 12:51 pm
Re: ?val
MHA configuration language expects commands in the following order:
<path> <operator> <argument>
In your case, <path> is mha.sort_output.mhaconfig_out.srate, <operator> is the question mark, and <argument> is the query command "val". Change your command to
mha.sort_output.mhaconfig_out.srate?val
and it should work.
<path> <operator> <argument>
In your case, <path> is mha.sort_output.mhaconfig_out.srate, <operator> is the question mark, and <argument> is the query command "val". Change your command to
mha.sort_output.mhaconfig_out.srate?val
and it should work.
-
- Posts: 118
- Joined: Mon Jun 24, 2019 12:51 pm
Re: ?val
One addition because common instructions for reading openMHA configuration files may seem contradictory to what I just wrote (but aren't):
Our documentation like the getting-started guide contain configuration language commands like this to have the mha read a configuration file:
?read:gain_live_getting_started.cfg
Here, <path> is the empty path, <operator> is question mark, and <argument> is "read:gain_live_getting_started.cfg"
The empty path in MHA configuration language is equal to the root of the configuration language data tree. This example command instructs the root parser to read a configuration file.
Our documentation like the getting-started guide contain configuration language commands like this to have the mha read a configuration file:
?read:gain_live_getting_started.cfg
Here, <path> is the empty path, <operator> is question mark, and <argument> is "read:gain_live_getting_started.cfg"
The empty path in MHA configuration language is equal to the root of the configuration language data tree. This example command instructs the root parser to read a configuration file.