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

Trouble Running Tutorial 3 #826

Closed
KorelU opened this issue Oct 12, 2023 · 1 comment
Closed

Trouble Running Tutorial 3 #826

KorelU opened this issue Oct 12, 2023 · 1 comment
Assignees
Labels

Comments

@KorelU
Copy link

KorelU commented Oct 12, 2023

Describe the bug
I’ve been looking at Tutorials 3 from the Documentation which address mobility. Unfortunately, I am having trouble running the examples from Tutorial 3. The Running with XML file using NS2 Movement seems to throw an error when I follow the Documentations examples.

To Reproduce
Steps to reproduce the behavior:

  1. Launch Oracle VM Virtual Box with Ubuntu 22.04.3LTS installed
  2. Run sudop core-daemon on a new terminal
  3. Run core-gui on a new terminal
  4. Given a new interface go to file open and find directory "home/vboxuser/Documents/core/package/examples/turorials/tutorial3/scenario.xml"
  5. Click Start Session on the upper left corner
  6. Click Run on wLan3 Mobility Player
  7. New window opens saying GRPC Exception: Mobility Error "exception calling applicaiton: int() argument must be a string, a bytes-like obj ect or a real, number not a 'NoneType"

Expected behavior
Observe movement of the nodes

Screenshots
Screenshot 2023-10-10 140402

Desktop (please complete the following information):

  • OS: Ubuntu 22.04.3 LTS
  • CORE Version 9.0.3
  • EMANE Version 1.4.1

Additional context

@KorelU KorelU added the bug label Oct 12, 2023
@bharnden bharnden self-assigned this Nov 8, 2023
@bharnden
Copy link
Contributor

Thanks for helping point this out, paths for referenced files in the scenario are corrected on the develop branch for a develop install. Ready for the next release.

You could manually adjust the scenario.xml file to point to the right path to correct your issue.

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

No branches or pull requests

2 participants