Weekly check in 2011.09.29

Participants: David Emory, David Turner, Kevin Webb, Andrew Byrd, Bibiana McHugh, Frank Purcell and the TriMet intern team

Check-ins:

DE - In process of checking in UI improvements, will continue through weekend. Some IE compatibility issues hopefully addressed. Mode-specific icons now being displayed in elevation graph. Also, will be attending 9/14 launch event in Portland; available for other meetings that afternoon.

DT - Addressing Trimet-reported bugs, mostly elevation-related. Also performance issues -- working on some speed-ups on the longer trips.

AB - Catching up on documentation for PathService. Discussion about Hudson -- was set up by original OTP maintainers, was causing stability issues and is not activelty maintained. Will revisit issue after Trimet launch.

FP - Javascript changes for Trimet map. Some performance work -- stress testing w/ timeout function, OTP is more stable as result, no lockups. Throughput is about 30 trips per second. Setup includes four instances of Tomcat w/ 3 gigs apiece. About 50% of processor in sustained use w/ heavy load. DT would like to borrow load-testing scripts to evaluate ongoing performance enhancements.

Interns:

• Shortening narratives: extra directions w/ path-footbridge combinations when there is only one option. DT. Will put on to-do list to address after performance issues are

• Triangle / safety weights: new set of safety weights developed, more extreme version "smart" weights. Frank to help with testing of these. Also, drop-down "safest" option gives different results as the 100% safety setting in triangle. Discussion about how safest trips are calculated. Will look into non-linear weighting options for safety factor in triangle.

• On Bike/Transit trips -- sometimes too much transit and not enough bike. Usually people only want one transit leg. Can there be minimum distance for transit segments? Or can there be higher transfer penalty? DT: send the specific trip links, also suggested experimenting w/ manually changing boardCost / transferPenalty in code.

• Error with one-way OSM bike tags; DT submitted patch, interns to evaluate.

• Safety issues w/ bike-to-transit trips: AB: this can be configured in code, will follow up by email.

• Fewest transfers w/ bike-to-transit. DT: fewest transfers just does fastest trip w/ 30 minute transfer penalty. Could be a checkbox instead. AB: worth trying, could address other issues raised earlier.

General announcements/discussion:

• Pursuing potential opportunity for analytics test case involving Purple Line proposal in Maryland.

• Discussion regarding OTP partner programs and potential additional RFPs.