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

EMANE parameter descriptions say absolute path required when relative paths are allowed #65

Closed
sgalgano opened this issue Aug 12, 2016 · 1 comment
Closed

EMANE parameter descriptions say absolute path required when relative paths are allowed #65

sgalgano opened this issue Aug 12, 2016 · 1 comment
Labels
bug

Comments

@sgalgano
Copy link
Member

From emane-users mailing list: [emane-users] Feedback on the "Comm Effect Model" wiki docs:

Another thing that confused me was the explanation of the “filterfile” parameter, which says: “Defines the absolute URI of the…”, although a relative path such as “myfilter.xml” is fine as well.

Reported-by: Jonathan Kirchhoff
@sgalgano sgalgano added the bug label Aug 12, 2016
@sgalgano
Copy link
Member Author

Prior to version 0.9.1, parameters referencing external files had to be absolute references. Most parameter descriptions were not updated to reflect changes that allow relative paths.

The following parameter descriptions also require updating:

  • TDMA Model - pcrcurveuri
  • Emualtor - antennaprofilemanifesturi
  • IEEE 802.11abg Model - pcrcurveuri
  • RF Pipe Model - pcrcurveuri

sgalgano added a commit that referenced this issue Aug 18, 2017
@sgalgano
Removed absolute path requirement from parameter descriptions that
40465e2 
allow relative path.

Reported-by: Jonathan Kirchhoff <jonathan.kirchhoff@fkie.fraunhofer.de>
See #65
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sgalgano