Clarify if access/egress depart_early arrive_late (etc) variables account for direction of trip

[e-lo]

@danielsclint : In filling out the pathweights for our final calibration runs, it struck me that depart_early_min should be very high for a work trip starting at work, but very low for a work trip coming from work. Can we segment?

Also - is there a reason why it has to be assigned to a specific access mode? Right now that means that we have to specify it separately for knr, pnr and walk which doesn't make too much sense.

cc: @lmz

[e-lo]

If the code doesn't account for it, we can just create a segment in config_ft.py, but I just wanted to clarify.

[danielsclint]

In the use case above, wouldn't the return trip purpose be 'Home'. The tour purpose would be 'Work'. If the trip purpose is segmented by inbound and outbound, then the pathweight_ft would support it.

In regards to the mode, I see it both ways. Yes, it's a little annoying, but I could see different values by mode. If I'm headed to an A's game, I might be willing to be a few minutes later if I can take BART versus the bus.