| [sumo-user] "device.toc.file" Does Not Support Relative Paths as Expected |
|
Dear SUMO Community,
I have observed that in "additional-files" such as "detectors_template.add.xml" and "additionals_template.add.xml", the file attribute can correctly interpret relative paths. For example: <inductionLoop id="mydetector" lane="mylane" pos="30.00" period="300.00" file="../../results/outputDetectors.xml" /> <edgeData id="emissions" type="emissions" freq="300" file="../results/outputEmission.xml" excludeEmpty="true" /> In both cases, the relative paths are resolved relative to the location of the .add.xml file, which works as expected. However, I’ve noticed that the device.toc.file parameter within a vType definition does not behave the same way. When a relative path is used there, it appears to be interpreted relative to the current working directory (i.e., where the SUMO executable is called from), rather than the XML file’s location. For example: <vType accel="1.003" id="vehCAVGAFSP0" ...> <param key="device.toc.file" value="../results/outputToC.xml" /> </vType> Unless an absolute path is provided, this setting often fails to locate the file as intended. Thank you in advance for your time and support.
Με φιλικούς χαιρετισμούς / Kind Regards
Vasilios Karagounis
Software
Engineer
Center
for Research and Technology Hellas (CERTH)
Hellenic
Institute of Transport (HIT)
CONFIDENTIALITY NOTICE: The information in this email and any attachments thereto are confidential, except where the e-mail specifically states that its contents can be disclosed, and is intended solely
for the use of its intended recipient(s). It may also be subject to legal privilege or otherwise protected from disclosure. If you are not the intended recipient of this communication, you are hereby notified that any disclosure, copying, distribution,
or use of the information contained in or attached to this e-mail is strictly prohibited. Please refrain from disclosing its contents to any third party, but notify the sender immediately and make sure to delete and permanently destroy the e-mail (including
any attachments thereto) from your filing systems. Internet communications are not secure and therefore sender/CERTH does not accept any liability for the contents of this message and for any damage whatsoever that may be caused by viruses.
|