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

improper handling of neigh edges when loading .net.xml file #5916

namdre opened this issue Aug 13, 2019 · 1 comment


Copy link

commented Aug 13, 2019

if the origional network was computed using option --opposites.guess.fix-lengths (and fixes were applied) then problems occur when reprocessing the net.xml file

  • with netconvert, an unequal-length error is generated
  • with netedit the error is generated but the network is saved with missing neigh values
@namdre namdre self-assigned this Aug 13, 2019

This comment has been minimized.

Copy link
Contributor Author

commented Aug 13, 2019

The problem is not with the applied fixes (which are mainted using setLoadedLength) but rather with tiny numerical fluctuations (due to output precision) that can make neigh lengths unequel even if they were equal before.

@namdre namdre closed this in 84d5b3b Aug 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
1 participant
You can’t perform that action at this time.