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

Storing netdiff toolcfg from netedit doesn't seem to work #16006

Open
schwepmo opened this issue Jan 13, 2025 · 2 comments
Open

Storing netdiff toolcfg from netedit doesn't seem to work #16006

schwepmo opened this issue Jan 13, 2025 · 2 comments
Assignees
Milestone

Comments

@schwepmo
Copy link
Contributor

I was playing around with netdiff and tried to save the toolcfg using the marked button.

grafik

Unfortunately, the configuration file is not created, or at least not in the selected directory and I can't seem to locate it.
Attached is a minimal network that contains the exemplary networks I was using
netdiff_test.zip

SUMO-version: 1.21.0

operating system: Windows 11

@namdre
Copy link
Contributor

namdre commented Jan 14, 2025

  • netdiff.py uses unnamed arguments for source, dest, and outprefix whereas netedit tries to pass them as --original-net --modified-net --outprefix
  • netdiff.py doesn't recognize the options --select-modified --select-added --select-deleted --load-shapes-modified --load-shapes-added --load-shapes-deleted which are only used in the context of netedit when loading netdiff results into the GUI. (the relevant netdiff.py options are --write-selections and --write-shapes)

Since the netdiff.py tool receives special handling among the tools (with custom options and loading of results) it's not obvious what the toolcfg should contain:

  • options for running netdiff outside of netedit (this is easy to fix)
  • or options for running netdiff from within netedit (in this case, a new mechanism is needed for writing options that netdiff ignores and netedit reads)

@schwepmo
Copy link
Contributor Author

For my use case, being able to store the original and modified network as well as the outprefix would probably suffice. As the main nuisance was locating the networks every time I ran netdiff.

On another note, the outprefix options was a little bit confusing at first, since it isn't only a prefix but also excepts a path + prefix, which is convenient but not what I would've expected.

@behrisch behrisch added this to the 1.22.0 milestone Jan 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants