-
Notifications
You must be signed in to change notification settings - Fork 13
Update FRCRobotTemplate with post-season changes #70
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?
Conversation
stephenjust
commented
Oct 18, 2025
- Integrate MapleSim
- Handle breaking changes from SCL
- Update deps
* Integrate MapleSim * Handle breaking changes from SCL * Update deps
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for doing this! Would eventually be nice to backport it into the EDU project as well so the robots there start hitting walls =D
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this an intelliJ thing?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| import edu.wpi.first.math.geometry.Pose2d; | ||
| import xbot.common.subsystems.pose.SimulatedPositionSupplier; | ||
|
|
||
| public interface BaseSimulator extends SimulatedPositionSupplier { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking at it now, should we have called this ISimulator?
| import org.ironmaple.simulation.drivesims.configs.DriveTrainSimulationConfig; | ||
|
|
||
| @Singleton | ||
| public class MapleSimulator implements BaseSimulator { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
⭐ if we're going to keep putting more stuff in here, should we just call this Simulator? Or BaseSwerveSimulator?
| private SwerveModulePosition[] getSwerveModulePositions() { | ||
| // if we have simulated data, return that directly instead of asking the | ||
| // modules | ||
| if (simulatedModulePositions.isPresent()) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you have any better ideas for how to handle this interface? Felt icky hacking it into the code like this but was expedient.
