Distances in Report about amodeus HOT 4 CLOSED

Hi Michael, would you be so kind and let me know which version you use? Please pull master and try with the newest version. In old versions, the processing was faster but full accurarcy was only possible if the export time constant was set to 1 second. Default was 10 s.
Additionally, there was one issue a while ago which was related to the sampling time. Then, you have to be careful what unit the coordinated system that you use is in... not all of the EPSG systems are in meter.

from amodeus.

Thanks @claudioglasses.
I use version 1.8.9 as given in the pom.xml from the amod repository

<dependency>
    <groupId>ch.ethz.idsc</groupId>
    <artifactId>amodeus</artifactId>
    <version>1.8.9</version>
</dependency>

You mentioned setting the time constant, is this possible in the config file?

It really seems to be an post-processing issue. As I said, the routes driven in the simulation seem to be correct, also their distances written to plans.xml.

Regarding the reference system I was using
UTM Zone 32 N (EPSG:25832), which should be okay. I also added a new enum in UserReferenceFrames for my implementation.

I will try your suggestion an do some test with the actual master from this repo.

Thanks so far!

from amodeus.

Hey Michael
Apparently there was an unnoticed bug introduced a while ago. This should now be fixed with the new 1.9.1 version of amodeus.
There will still be some inaccuracies given the way the sampling works.
Let us know if there are still problems.

from amodeus.

@JoelGaechter thanks for your support. I works now!

from amodeus.