Define temporal folder for SUMO and Netedit

[palvarezlopez]

This temporal folder will be used for:

• Save temporal SUMO and tools templates
• Security copies of the edited network and files.
• Temporal saving of files during Recomputing with Volatile options without saving
• Dump files

Windows: %userprofile%/AppData/LocalLow/DLR/SUMO Linux: $HOME/.config/DLR/SUMO MAC: ~/Library/Application Support/DLR/SUMO

Update: Use /Eclipse/ instead /DLR/

[palvarezlopez]

@behrisch @angelobanse What do you think?

[behrisch]

We should use eclipse/sumo and not DLR/sumo here (not sure about the capitalization). I understand that this is probably the default location for such data but honestly I get lost most of the time if I try to find things in those directories. We already create a $HOME/Sumo dir for osmWebWizard outputs if the tools dir is not writable. Should we abolish this?

[palvarezlopez]

In Windows, I am against using the SUMO/tools as default output folder for OSM webWizard, and the temporal folder could be useful for this. This is my first notice about $HOME/Sumo in Linux 😅. A possible solution for finding the temporal directory is to open it after using osmWebWizard ,and add a shortcut in NETEDIT.

[namdre]

The default is writing into the working directory and I'd very much like to keep this (a common usage pattern for me is to enter some directory and then calling %SUMO_HOME%\tools\osmWebWizard.py (or $SUMO_HOME). However, we could make an exception for SUMO_HOME/tools and avoid writing there.

I don't like the idea of letting webWizard write into a tmp dir because the generated files are not meant to be temporary and this would force the user to move them (with annoying results if sumo-gui is still open). I would reserve use of the tmp dir to things the user (usually) doesn't wish to keep, such as intermediate configuration templates we intend to parse.

[behrisch]

I am not in favor of changing the current webWizard behavior I just want to avoid having a third location besides working dir and $HOME/Sumo and I don't like the very deeply nested config dirs. If it is really temporary, it should go to $TEMP otherwise we could also use something like $HOME/Sumo/tmp (similar to what texttest does). I am not against the proposal, I will find my way, just want to mention some options. Just to make clear what I mean by "really temporary": It has an assumed lifetime of less than one day because there may be cronjobs cleaning up the temp dir. This is for instance not true for the texttest tmp, at least in my usage pattern I regularly keep texttest sessions open for longer times.