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

Documentation: add information about different physSim and routers we have. #3300

Open
nikolayilyin opened this issue Sep 6, 2021 · 3 comments · May be fixed by #3636
Open

Documentation: add information about different physSim and routers we have. #3300

nikolayilyin opened this issue Sep 6, 2021 · 3 comments · May be fixed by #3636
Assignees

Comments

@nikolayilyin
Copy link
Collaborator

Currently only JDEQSim and R5 are mentioned in the latest documentation, but we also have BPRSim, ParBPRSim, CCHRoutingAssigment and additional routers - CCH, GH.

One needs to add some information into documentation about mentioned routers and physSim implementations

@nikolayilyin nikolayilyin changed the title Documentation: add a small entry about different physSim and routers we have. Documentation: add information about different physSim and routers we have. Sep 6, 2021
@nikolayilyin
Copy link
Collaborator Author

Also in the beam-template according config keys should have comments with all possible values

@HoneyTauOverTwo HoneyTauOverTwo self-assigned this Sep 29, 2022
@HoneyTauOverTwo
Copy link
Collaborator

beam-template already has comments about these:

physSim beam-template.conf#L478: values: JDEQSim, BPRSim, PARBPRSim, CCHRoutingAssignment

Routing beam-template.conf#L895: values: R5, staticGH, quasiDynamicGH, nativeCCH (Linux Only)

Documentation for phySim and router indeed needs updating

@HoneyTauOverTwo
Copy link
Collaborator

I identified the relevant java and scala files related to physics simulation (working on routers), but I might need some help to actually write the documentation.

For instance, what BPR and CCH stand for.

From what I understand, BPR, it is an alternative for Java Discrete Event Queue Simulator (JDEQ) from MATSim. It was implemented by Dima so might need his help.

I guess I'd have to know the difference, advantages, disadvantages of each approach.

As for CCHRoutingAssignment, it appears to be one that bypasses physics simulation ignoring congestion and such.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants