Summary: When creating a train with invalid arguments the train creation continous without throwing an exception
System Configuration: Zach's Computer
Steps to Reproduce: Create a train with invalid arguments
Expected behavior: Exception thrown
Actual behavior: No Exception thrown

Summary: time modifier was able to have a value of zero. This is bad for the train model, and I was requested to change this.
System Configuration: Justin's computer, Java 1.8
Steps to reproduce: press the pause button next to "current time," or change the time modifier to 0.
Expected behavior: time modifier should be set to a very small value instead of zero to avoid problems in the train model.
Actual behavior: the value was changed to zero.

Summary: When selecting a different train in the Train Model GUI the selction does not remain constant and get resets
System Configuration: Zach's Computer
Steps to Reproduce: Use GUI to select a different train
Expected behavior: Train remains selected
Actual behavior: Train does not remain selected

Summary: Starting a Train samples every chance it gets, should instead sample every millisecond or slightly less than that
System Configuration: Zach's Computer
Steps to Reproduce: Start up a Train
Expected behavior: resources are conserved
Actual behavior: resources are not conserved

Summary: suggested speed and authority were sent as messages to the track controller even when a train was not yet created or the schedule was not yet active.
System Configuration: Justin's computer, Java 1.8
Steps to reproduce: update the suggested speed or authority before executing a schedule.
Expected behavior: no updates to the track controller should be sent before schedule execution starts
Actual behavior: suggested speed and authority are sent regardless of the schedule exeucting.

Summary: When the train model determines if it is over max speed it should take into account the time multiplier and remove it from the calculation
System Configuration: Zach's Computer
Steps to reproduce: Set Power to 15 Watts, Set time multiplier to 1000
Expected Behavior: velocity exceeds the limit
Actual Behavior: velocity does not excede the limit

Summary: suggested speed remained the same value even after authority was zero.
System Configuration: Justin's computer, Java 1.8
Steps to reproduce: use MessageTester to send location messages to the CTC server until the authority becomes zero.
Expected behavior: suggested speed should become zero when authority is zero.
Actual behavior: suggested speed retains its value even after the authority decreases to zero.

Summary: Power over 120k and below 0 should be forced to 0 or 120k instead of ignored on train model
System Configuration: Zach's Computer
Steps to reproduce: Send the train a power greater than 120k Watts
Expected Behavior: Train defaults to 120k Watts
Actual Behavior: Train ignores power

Summary: Next destination was not being reset on update
System Configuration: Justin's computer, Java 1.8
Steps to reproduce: use MessageTester to send train location messages to the CTC Server
Expected behavior: next destination should be set to the next destination or "None" if a train arrives at a location.
Actual behavior: next destination remains the same.

Summary: When adding a new block to the train model via the GUI the Train controller does not receive an update message
System Configuration: Zach's Computer
Steps to Reproduce: Use GUI to add new block to train
Expected behavior: Message sent to corresponding Train Controller
Actual behavior: No message sent