Updates related to Assignment 5 Last update: Thu 07 Apr 2011 10:04:35 AM EDT Dear students, We will summarize major clarifications and corrections to the A4 specification document as they come to our attention. General ======================================================================== Assorted typos in Warm-up section have been fixed. Q1 ============================================================================= -Airport class, scheduleLandings() method: You are told in the spec that you should include currentTime in the method parameters. Don't worry if you don't use currentTime anywhere in this method. -Airline class: removed erroneous reference to dealing "arrival time". Arrival time is not part of the assignment at all. -Airline class: clarified how to parse the input String for addAirport() and addFlight() -Instructions for updateTowardGoal() in Jet have been clarified. **** Added more clarifications and HINTS about updateTowardGoal() **** Flight class, isInLandingRange() method: added clarification. " Note that it only makes sense for a Flight to be in landing range if it is currently INFLIGHT. **** Airline class, addFlight() method: fixed instructions that were accidentally flipped around. "For example, given a String of the form "01:00:00\tnew york\tmontreal\t8" the addFlight() method creates a flight with departure time of today at 01:00:00, associated Jet whose name is "8" and a Route ENDING at the Airport named "montreal" and STARTING at Airport named "new york". " -AirlineSimulator class: you have to make sure that all the airports show up on the canvas. This means you have you "convert" the coordinates used for Airport locations into coordinates that fit on the canvas (i.e. coordinates between 0 and 1). You may assume that all aiport coordinates will be positive and between 0 and 100. Q2 ============================================================================ Q: "When I print the toString() methods of all flights, it seems that all the flights that take off at time 12:xx:xx get converted to 00:xx:xx. However, the flights that take off at any other hour are all fine...Could anyone shed some light on what might be the problem?" A: "It's a problem with the format we were suggested to use; I switched to using HH:mm:ss, and those problems went away for me (now I've just got a few planes chilling in the middle of nowhere.)" Q: "I've been trying to figure out why planes 23, 25, 26, and 27 have a hard time reaching their destinations. Then I figured it out; they each have flights extending into the next day, but our time formatter doesn't understand this; the HH:mm:ss (so-used because it corrects for the 00/12 overlap) only sees two times that are marked 00:... ! Offending flights: 00:01:00 Anvard Tashbaan 23 00:08:00 Cair Paravel Anvard 23 00:01:00 Tashbaan Beaversdam 25 00:15:00 Cair Paravel Tashbaan 25 00:01:00 Tashbaan Chippingford 26 00:34:00 Chippingford Beaversdam 26 00:01:00 Tashbaan Anvard 27 00:32:00 Anvard Chippingford 27" A: "No flights should *take-off* after midnight, so I think it should be fine. But I can imagine there is a way to code it where this is a problem--particularly with delays and such. If this is causing an issue, then it's fine, since the spec says just to worry about 1 day simulation. You can confirm this is fine by temporarily deleting the flights from the flight list."