Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Walk issue in ChoosesMode #3441

Open
dgm90 opened this issue Jan 12, 2022 · 6 comments · May be fixed by #3476 or #3745
Open

Walk issue in ChoosesMode #3441

dgm90 opened this issue Jan 12, 2022 · 6 comments · May be fixed by #3476 or #3745
Assignees

Comments

@dgm90
Copy link
Collaborator

dgm90 commented Jan 12, 2022

There was a comment in art/new-york-only-code branch
image

It was removed before the branch was merged. It needs to be resolved one day.

@dimaopen
Copy link
Collaborator

From @zneedell

Basically if someone has a set of trips (e.g. home -> work -> eat -> work -> home) and no pre-determined modes, I think it would be great for us to totally clarify what mode options the agent has for each of their trips depending on what their first mode choice is. I think right now, if they choose CAR for their first trip they are locked in to CAR for every trip until they go back home, which I think is OK for now. But is that the case if they choose walk? E.g. they should be able to WALK to work and then take ride-hail home because they don't have a personal vehicle with them. I think it would be great to clarify what the logic currently is for these different combinations and then figure out if we want to make any changes. E.g. one nice change that we could make is if someone takes their car to work in the morning, they should still be able to choose walk for the work -> eat -> work trips (aka subtour) because they know they will return to where their car is parked before coming home. But that logic might be a little tricky to implement in all cases.

@dimaopen
Copy link
Collaborator

The current logic is

  • When a person has chosen the Mode they stick with it until they get Home or a Replanning happens.
    So if a person has chosen Walk they use this mode until they get Home. But if a replanning happens the may choose Car at work and get Hobe by a personal car which is also not quite right.
    car_from_work

@zneedell
Copy link
Collaborator

OK thanks--so yeah, I think it's worth exploring whether we can make currentTourMode not automatically determine the mode of the rest of the trips until they get home, instead for it to just constrain the available alternatives. Here's an initial proposal:

  • If the initial trip is CAR: all trips need to be by car. (we could make this more complex by saying they can choose other modes for a subtour as long as they return to the car's parked location before returning home, e.g. home->work->eat->work->home, but let's ignore that for now)
  • If the initial trip is by a private BIKE: Same as car
  • If the initial trip is walk-transit, walk, ridehail, or shared vehicle: They can choose any mode for subsequent trips (except for private car or bike, although we'd expect those not to show up as alternatives based on what is returned from the household vehicle manager.
  • If the initial trip is drive-transit: like above, except the last trip returning home must be drive-transit

How does that sound to everyone (including @haitamlaarabi , @wrashid , @nikolayilyin , anyone else)?

@zneedell
Copy link
Collaborator

zneedell commented Feb 17, 2022

One addition--I think we might want to change how currentTourMode is used. As I understand right now we're treating it like current trip mode (e.g. it's what the agent looks to to uniquely determine the mode of an upcoming trip), but really it's something that should be set for all trips on a tour when someone leaves for the tour, but rather than determining the mode for individual trips directly it should implement the logic above on constraining the modes.

@dimaopen dimaopen self-assigned this Feb 18, 2022
@dimaopen
Copy link
Collaborator

Generally, I agree with what @zneedell says. But we need to remember that CAR (BIKE) tour includes shared cars (bikes). So I think that we can simplify these rules (but have the same result) by using currentTourPersonalVehicle field that is supposed to be used this way.
In this case, we could always choose any mode for subsequent trips (or take the mode that is defined by the plan) but if the currentTourPersonalVehicle is set then we need to use it.

@dimaopen dimaopen linked a pull request Feb 25, 2022 that will close this issue
dimaopen added a commit that referenced this issue Mar 23, 2022
…rip-tour-mode

# Conflicts:
#	src/main/scala/beam/agentsim/agents/modalbehaviors/ChoosesMode.scala
Xuan-1998 added a commit that referenced this issue Mar 28, 2022
@dimaopen dimaopen linked a pull request Mar 28, 2022 that will close this issue
zneedell added a commit that referenced this issue Mar 29, 2022
…nto zn/nyc-runs-new-r5-and-current-tour-mode
dimaopen added a commit that referenced this issue Apr 19, 2022
…ce-strategy

# Conflicts:
#	src/main/R/freight/freight-processing.R
#	src/main/scala/beam/agentsim/agents/freight/input/FreightReader.scala
#	src/main/scala/beam/agentsim/agents/household/HouseholdActor.scala
#	src/main/scala/beam/agentsim/agents/household/HouseholdFleetManager.scala
zneedell added a commit that referenced this issue May 31, 2022
@dimaopen
Copy link
Collaborator

@zneedell AFAIR you took over this task. If you didn't please reassign it to me.

@dimaopen dimaopen assigned zneedell and unassigned dimaopen Aug 22, 2022
@dimaopen dimaopen linked a pull request Apr 25, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants