In v7.4.0 when the “paired cameras” check was initially deselected, it’s possible to edit it later based on How a project is organised | AddaxAI : “Change it later on the Deployments page under Edit. AddaxAI regroups the deployment’s events and reprocesses the labels”
This change can only be done one deployement at a time, and when changing it, a message is displayed “Saving regroups this deployment’s events.” But when “Save changes” is clicked, the “Applying settings messgae shows that “Processing deployment x/…” - where n is TOTAL deployments, and x cycles from 1 through n.
In my case I have 50 deployments (that were loaded from csv) and having to do this a deployment at a time is ok, but having to wait several minutes for all deployments to process seems like a bug?
Is this expected behavior when editing “Paired cameras” deployment info?
Hi @Heinrich,
Yes, this is expected, but your surprise is fair. Both messages tell the truth: saving regroups only that deployment’s events, and the label reprocess that follows always runs over the whole project. That’s why the counter walks through all 50. It is definately inefficient, but it doesn’t break your data.
The good news is that nothing goes wrong with your data. The smoothing runs per deployment, and the grouping of the other 49 didn’t change, so they simply get the same labels written back. It’s safe, it just costs more time than strictly needed. Under the hood the app keeps one “labels match the settings” flag for the whole project, so after any change it re-checks everything. A targeted version that only reprocesses the edited deployment is on my list, but I can’t promise when it lands.
The deployment CSV now has a paired_cameras column. Now that you know it’s there, set it to true for the next deployments you import. The grouping is right from the start then, so no editing afterwards and no reprocesses at all.
Hope this helps!
Cheers,
Peter