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

Reuse network topologies between sub-experiments #50

Open
2 tasks
castarco opened this issue Jun 3, 2019 · 0 comments
Open
2 tasks

Reuse network topologies between sub-experiments #50

castarco opened this issue Jun 3, 2019 · 0 comments
Assignees
Labels
enhancement New feature or request P2P P2P network related simulation Related with the simulations themselves

Comments

@castarco
Copy link

castarco commented Jun 3, 2019

Right now, every sub-experiment generates a new random preferential attachment graph (using the Barabási–Albert model) to define its network topology.

In order to make comparisons between different settings sets more fair and useful, the sub-experiments should be executed using the same network topology.

Subtasks:

  • Ensure that all sub-experiments share network topology.
  • Enhance the experiment runner by allowing to execute the same sub-experiment many times on different network topologies (still shared with the other sub-experiments).
@castarco castarco added enhancement New feature or request P2P P2P network related simulation Related with the simulations themselves labels Jun 3, 2019
@castarco castarco self-assigned this Jun 3, 2019
castarco referenced this issue in castarco/unit-e-experiments Jun 5, 2019
Fixes the issue #50 .

Signed-off-by: Andres Correa Casablanca <[email protected]>
castarco referenced this issue in castarco/unit-e-experiments Jun 5, 2019
Fixes the issue #50 .

Signed-off-by: Andres Correa Casablanca <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request P2P P2P network related simulation Related with the simulations themselves
Projects
None yet
Development

No branches or pull requests

1 participant