The 'otns' binary is installed in the path so that it can be run from anywhere.
However, the standard OT node executables (e.g. br, v11, v12, etc) are not found when running otns from a different (non-default) directory. This could be resolved by having the default OT node binaries location added to the search path, such that the OT node exes can be found.
The search path is already an existing internal function: e.g. it looks for nodes in the current working directory as well as in the location ./ot-rfsim/ot-versions.
The 'otns' binary is installed in the path so that it can be run from anywhere.
However, the standard OT node executables (e.g. br, v11, v12, etc) are not found when running otns from a different (non-default) directory. This could be resolved by having the default OT node binaries location added to the search path, such that the OT node exes can be found.
The search path is already an existing internal function: e.g. it looks for nodes in the current working directory as well as in the location
./ot-rfsim/ot-versions.