Processing timer bug (feature?) when queing projects

I have successfully had LiveODM installed on three systems and one of them are acting as a server and two are working as nodes.
Currently I’m doing some benchmarking and loaded up four different datasets that I run on both “Fast Ortophoto” and “High Resolution” presets, so in other words i run eight benchmarks per node and I noticed that the timer on each dataset continues to the next dataset. Is it supposed to work like this?

Example: I upload a dataset, it begings processing and the timer starts. I upload another dataset that gets queued and when the processing begins, the timer doesn’t reset, but keeps going from the old datasets timer.

Versions on all of the machines:

  • App Version: 1.3.2
  • API Version: 1.6.0
  • Engine Version: 0.9.8
1 Like