-
Notifications
You must be signed in to change notification settings - Fork 264
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improper documentation for SysId test state #2547
Comments
Were you intending to have a link in the last sentence? Why do you think the names need to be documented? General use of SysID doesn't require knowing the names, see this example. Are you writing your own new SysIdRoutine clone? If so that seems beyond the scope of the general documentation and more something that looking through the code should be an expectation. |
I wasn';t intending on putting down a link. We were using a custom SysId routine with CTRE logging. Paging @gabeStuk he will have more info. |
Based on the documentation given and the testing I did, loading a log into sysid with 3rd party logging requires a method passed into the For context, here is the SysIdRoutine logging method I am talking about. We used CTRE's SignalLogger: private SysIdRoutine sysIdRoutine = new SysIdRoutine(
new SysIdRoutine.Config(null, null, null, this::logSysIDState),
new SysIdRoutine.Mechanism(
volts -> setControl(voltRequest.withVoltage(volts.in(Units.Volts))),
null,
this));
private void logSysIDState(State state) {
if (state != State.kNone) {
switch (state) {
case kDynamicForward:
SignalLogger.writeString("test-mode", "dynamic-forward");
break;
case kDynamicReverse:
SignalLogger.writeString("test-mode", "dynamic-reverse");
break;
case kQuasistaticForward:
SignalLogger.writeString("test-mode", "quasistatic-forward");
break;
case kQuasistaticReverse:
SignalLogger.writeString("test-mode", "quasistatic-reverse");
break;
default:
break;
}
} Something like |
See wpilibsuite/allwpilib#6273 for related issue |
Doesn't |
Ah yes, you are correct |
My entire complaint is nullified |
Other than that the docs should say that |
While there is a slight mention of the general format of the SysId test states for logging, the names are not explicitly mentioned or explained. The only way we found the proper names for the
test-mode
log variable was through a screenshot of the log analysis tool itself:The names of each of the test modes should be explicitly documented here.
The text was updated successfully, but these errors were encountered: