This repository was archived by the owner on May 26, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 5
Logging Standards
AMMack26 edited this page Feb 6, 2016
·
30 revisions
- Initialization of a Command
- Command interruption
- Subsystem methods
- The execute function of a Command when it doesn't repeat
- ?
- The execute function of a Command when it constantly repeats (Can be done temporarily for testing. Or set the repeating method at fine level.)
- ?
- Add logger to top of class file like below. Replace with the class name.
Logger logger = Robot.getLogger(<Class>.class);
Logger logger = Robot.getLogger(Climber.class); - Use logger by calling the logger.info() or logger.fine() methods.
- Example Initializing log statement in the initialize method of a Command:
logger.info("[Initializing]"); - Example Initializing log statement in the method of the Climber Subsystem. Posts what it is doing and some info on the status of the Subsystem:
logger.fine(<Message and infor about subsystem>);
logger.fine("Latch Released: " + "ArmLatch=" + armLatch.get());");
- Example Initializing log statement in the initialize method of a Command:
- Use appropriate log level:
- Use logger.fine for all Subsystem classes.
- Use logger.info for all Command classes.