Switching of the rod color or the camera view becomes very slow when corrections have been made to the rod data.
The switching then takes ~1-2 sec. This happens because the application writes the changes to a file on disk and blocks during that period. It was coded this way to:
avoid RAM usage by only having the contents of one data file loaded at a time and immediatly release that again after the relevant data was extracted.
avoid reading attempts to a file that is currently being written to.
This is specifically a problem when trying to track one rod across two views and/or multiple frames as the waiting period then would be a big percentage of the total work time. When trying to correct the positions of all rods in one image before one of the switching operations occurs, this waiting time is only an insignificant portion of the total work time and might therefore not be an issue.
@adithyaOvGu, @messyblanket Do you find this "laggy" behavior disturbing during your correction/tracking work and do you want it fixed at the expense of a bit more RAM usage?
Switching of the rod color or the camera view becomes very slow when corrections have been made to the rod data. The switching then takes ~1-2 sec. This happens because the application writes the changes to a file on disk and blocks during that period. It was coded this way to:
This is specifically a problem when trying to track one rod across two views and/or multiple frames as the waiting period then would be a big percentage of the total work time. When trying to correct the positions of all rods in one image before one of the switching operations occurs, this waiting time is only an insignificant portion of the total work time and might therefore not be an issue.
@adithyaOvGu, @messyblanket Do you find this "laggy" behavior disturbing during your correction/tracking work and do you want it fixed at the expense of a bit more RAM usage?