(In reply to Patricia Lawless from comment #4)
I believe the server (test runner) can be any Windows machine capable of running the video capture software.
The test runner can really be anything that can run the capture device's software. Preferably, the capture device drivers can be invoked using script to get the recordings. The test runner just needs to be powerful enough to record the frames without dropping any.
There's the analysis step as well, which might use a tool I wrote called croptop1, unless PI comes up with something better (which is maybe preferable). That runs in a web browser.
(In reply to Kendall Libby [:fubar] (he/him) from comment #5)
(In reply to Patricia Lawless from comment #0)
Is this particular device a hard requirement or do we have some flexibility? 4gb of memory and Celeron means it's going to be a bit slow, both in terms of running tests but also for general management of the system which in turn leads to longer downtime between testing, etc.
This is the reference device that we're supposed to be measuring against, so unless we can somehow simulate its low power in a reliable way, it's probably what we should be using.