You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are building a manufacturing test station, which needs to run test groups over 4 modules at a time. Those 4 test groups share couple of instruments so they will need to take turn on those test cases; but other than that they have their own resources for remaining test cases. All the I/O data, like user input, prompts and logs, test results, of 4 test groups need to be displayed and refreshed on a single webpage. How does openhtf support such a use case? Any suggestions are highly appreciated.
The text was updated successfully, but these errors were encountered:
well, similar functionality is already in the _MonitorThread class, however:
if we use any sort of input that requires human intervention, the whole program locks up. input blocks globally (does it?)
we should make a "ConcurrentGroup", which should (should it?) open up a whole bunch of threads...
if__name__=="__main__":
executor=htf.Test(
htf.ConcurrentGroup(
... # < a list of phases, just as a thread
),
htf.ConcurrentThread(
...
)
)
executor.execute()
So, the executor has a global threading.Event(). When all of the ConcurrentThreads stop -> kill the runner thread?
This way this API wouldn't break the existing APIs.
Although I wouldn't have any idea how does this mess up the GUI. I would imagine that the GUI would need some reimagination.
We are building a manufacturing test station, which needs to run test groups over 4 modules at a time. Those 4 test groups share couple of instruments so they will need to take turn on those test cases; but other than that they have their own resources for remaining test cases. All the I/O data, like user input, prompts and logs, test results, of 4 test groups need to be displayed and refreshed on a single webpage. How does openhtf support such a use case? Any suggestions are highly appreciated.
The text was updated successfully, but these errors were encountered: