Brendan Jackman e672ea3faf energy_measurement: Allow multiple IIO devices for ACME ...

Devlib's ACME instrument uses iio-capture under the hood, which can
only capture data from one IIO device at a time. Devlib's instrument
API expects to produce a single CSV file for the Instrument, with a
single axis of sample timestamps. These two things cannot be
correctly reconciled without changing the devlib Instrument API -
get_data would need to be able to return two distinct sets of data.

Instead, where required WA will instantiate the ACME instrument
multiple times (once for each IIO device), producing two separate CSV
files. Aggregated energy info (as opposed to timestamped samples of
energy data) _can_ be meaningfully combined from multiple IIO
devices, so the derived stats are summed.

This requires altering the internal API of the energy_measurement
module - rather than a single instrument the super-instrument now has
a dictionary mapping 'device' keys (this is really an arbitrary key,
but I think that 'device' is a justifiable metaphor for whatever
might separate multiple instruments, plus it is the terminology used
by IIO/ACME) to Instrument objects.  Existing instruments simply
return a dict with a single entry, with None as the key.

It may in future be possible to solve this problem in devlib's ACME
instrument by avoiding the use of the iio-capture tool. In that case,
it should be possible to basically revert this patch and get the
required funcitonality from devlib.

2017-10-06 14:43:54 +01:00

..

__init__.py

Skeleton job execution

2017-03-15 14:34:23 +00:00

energy_measurement.py

energy_measurement: Allow multiple IIO devices for ACME

2017-10-06 14:43:54 +01:00

fps.py

instrumentation: add FPS instrument.

2017-09-29 13:50:23 +01:00

misc.py

Instrumentation/Misc: Fixed using 'target' instead of 'device'

2017-07-25 16:08:17 +01:00

trace-cmd.py

trace-cmd: add trace files as artificats

2017-10-02 13:55:58 +01:00