make the optitrack enabled by default in cfg #84
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If the enableOptitrack value is not explicitly set in the launch file, the package defaults to true, as specified in the source code. However, if the roscore is kept running in another terminal without restarting, this setting only takes effect once. The solution is to set the default value to True in the configuration (cfg) file.
Below are some relevant log entries:
For the first run, the enableOptitrack can be set to 1 by default.
However, for the second run, the enableOptitrack cannot be set to 1.