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.

Sign up for GitHub

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

Jump to bottom

Add support for bounded choice model #106

Open
MarkRaadsen opened this issue Mar 22, 2024 · 0 comments
Open

Add support for bounded choice model #106

MarkRaadsen opened this issue Mar 22, 2024 · 0 comments
Assignees
@MarkRaadsen
Labels
documentation Improvements or additions to documentation done pending merge enhancement New feature or request
Milestone
Version 0.5.0

Comments

@MarkRaadsen
Copy link
Member

No description provided.

@MarkRaadsen MarkRaadsen added documentation Improvements or additions to documentation enhancement New feature or request labels Mar 22, 2024
@MarkRaadsen MarkRaadsen added this to the Version 0.5.0 milestone Mar 22, 2024
@MarkRaadsen MarkRaadsen self-assigned this Mar 22, 2024
MarkRaadsen pushed a commit that referenced this issue Mar 22, 2024
working on #106. Not done
c080f72
MarkRaadsen pushed a commit that referenced this issue Mar 28, 2024
#106 various edge case fixes. Now working unless aggressive step-size…
a4c85cf 
…s with fixed smoothing are chosen which is to be expected. For this a self-regulating average smoothing would be useful to add. TODO: add assertions to unit test with bounded choice model --> then start on pruning path choice set
MarkRaadsen pushed a commit that referenced this issue Apr 5, 2024
#107: implemented and tested self-regulating average approach based o…
e18e7d6 
…n Liu et al 2009 to smoothing options (Java)

#106: bounded choice model now supported and tested on a small network (more tests ideally required)
#100: various bug fixes for weibit implementation
#99: various improvements to path absed sLTM traffic assignment, now working on small test networks
MarkRaadsen pushed a commit that referenced this issue Apr 12, 2024
#99: effectively operational, tested on Sioux Falls, needs testing on…
101df14 
… larger networks (Chicago) stil

#106: minor updates, effectively done
#104: minor updates effectively done (sLTM now allows for configuring a threshold n when to remove paths previously added)
#103: done, usage within sLTM slightly different than normal as it is now based on Rasmussen et al. (where denominator is not setup to use min cost)
#102: effectively done
#100: effectively done (not tested on larger networks)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@MarkRaadsen MarkRaadsen

Labels
documentation Improvements or additions to documentation done pending merge enhancement New feature or request
Projects
None yet
Milestone
Version 0.5.0
Development

No branches or pull requests
1 participant
@MarkRaadsen