[fix][Ticket #900284] Investigate metadata delay in case western

[K4rishma]

Update: overview acquisition worked after waiting for the stage position to reach the target position.

Testing on 9th July

Please let me know where I can add logging to understand the metadata issue at Case Western.

Objective:

1. understand the source or where the delay occurs in saving the tiled images
2. try to make the overview images work by adding time delay if source of metadata issue is not clear

[patrickcleeve2]

Looks good to me. One note is that the additionally logging may slow things down enough that they are synced up, so might be hard to re-create.

Also, instead of adding an artificial display, you can force update the metadata with the stage position

das[0].metadata[model.MD_POS] = stage.position.value["x"], stage.position.value["y"]

[pieleric]

You'll need to also compare to the updated stage position by xt_client (in /var/log/odemis.log), see Updated position to.... And check the messages before, related to the stage movement. After the move it should always say "Stage move completed".
You also might want to add a log in actuators.ConvertStage._updatePosition() (which is called when the raw stage position changes) and look for "reporting position" corresponding to the MultiplexActuator.
Finally, you want to look for "Updating position for component..." from the mdupdater that is supposed to copy the stage position onto the ccd metadata (as MD_POS). All of this should happen before the image acquisition starts (although I don't think there is any code that ensures this is the case...)

[patrickcleeve2]

Some minor cleanup

[tepals]

Can you fix the linting?

[patrickcleeve2]

Just a minor comment