08-19-2022 08:42 AM
Hi all,
I'm using Batch Synch however a slight variation on the traditional use is that I want to force the thread used in the first synchronized section (set to one thread only) to then be the thread that executes the remaining synchronized sections so I'm currently thinking of a hybrid Batch synch + Rendezvous approach. See attached seq.
However there's a lot of sections to be wrapped like this AND the termination / error handling of this gets complicated really quickly if we're to avoid deadlocks. Feels like a hack honestly.
Anybody got another pattern they would care to suggest?
Cheers
Chris
08-19-2022 01:29 PM
Why not enclose all the steps with just one batch sync, this way all steps run in the same socket.
08-19-2022 01:49 PM - edited 08-19-2022 01:51 PM
My example was just to simplify the situation. Sadly there are steps that require all sockets to execute along with some that are one batch only. There are many many steps and several sub sequences,
08-19-2022 10:43 PM
This exactly sounds like the way TSM (TestStand Semiconductor Module) works (on top of Batch model)