-
Notifications
You must be signed in to change notification settings - Fork 0
Simnet example #3
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
base: main
Are you sure you want to change the base?
Conversation
edfc3d5 to
cb93735
Compare
|
I think we should have both Shadow and simnet in attsim in a way that we can switch the simulator easily so that we can compare both simulators any time we want, instead of replacing one with the other. |
4b7c75e to
0e8fb77
Compare
|
I think it's looking good overall |
useful when debugging and iterating to be sure you're running on the expected changes
|
I'm pretty happy with how well this matches with shadow. 200 nodes For the short term I think it's fine to have both. The work for using both is already done. Long term, I think using the simnet is more flexible and we may craft scenarios that are hard to translate to shadow. But we can cross that bridge when we come to it. |




this is a bigger change than expected because I also added the gmlparser/shadowconfig/topology.json parser/reader. So that it can use the same files as shadow.
Normally, you wouldn't need all of that because you'd define your network in Go.