-
Notifications
You must be signed in to change notification settings - Fork 0
Change file names to match new conventions #72
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
base: main
Are you sure you want to change the base?
Changes from 3 commits
7ba039f
741d4d6
bfec1ca
ab727b3
94adeee
4f9e34d
be5d9a8
f2eef23
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2,9 +2,9 @@ | |
|
||
import org.littletonrobotics.junction.AutoLog; | ||
|
||
public interface ElevatorIO { | ||
public interface ElevatorInterface { | ||
@AutoLog | ||
public static class ElevatorIOInputs { | ||
public static class ElevatorInterfaceInputs { | ||
junocapra marked this conversation as resolved.
Show resolved
Hide resolved
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. ElevatorInputs There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. por favor There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. plz correct this in all da files bc the elevator inputs are autologged from the specific impls. they aren't logged from the interface. @JacksonElia do u think this is good? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. yeah I think it is. I really think we should try to avoid using There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. okay after looking into it more I guess its not awful using There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The reason I think we do that is bc for log replay u need a blank impl of the io layer to rerun the code. So we just pass in the interface. What we could do instead is create a blank impl with the defaults seen in the interface, which would work. Idk which one is better. So like as opposed to using There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Thats a good explanation, thanks. I would say normally I feel like making something like Though, if we start writing a lot of replay specific code for whatever reason, then we should make a specific implementation for it. |
||
public boolean isConnected = false; | ||
|
||
public double leaderMotorPosition = 0.0; | ||
|
@@ -18,7 +18,7 @@ public static class ElevatorIOInputs { | |
public double followerMotorCurrentAmps = 0.0; | ||
} | ||
|
||
public default void updateInputs(ElevatorIOInputs inputs) {} | ||
public default void updateInputs(ElevatorInterfaceInputs inputs) {} | ||
|
||
public default double getElevatorPosition() { | ||
return 0.0; | ||
|
Uh oh!
There was an error while loading. Please reload this page.