Transport layer now uses a flexible, policy based design.
In short:
I you want to continue using queues, there's now a policy object in between, e.g.:
x.daqQueue
# becomes
x.policy.daqQueue
No more changes required (this is LegacyFrameAcquisitionPolicy running under the hood).
In any case, have a look at xcphello_recorder.py and run it, even if you are an experienced user!
P.S.: re-run python setup.py develop to rebuild extension module.
Now I have to fix some over-heating problems (including myself), than I'll write some more words.
It's worth mentioning that the x.policy.daqQueue items are now tuples with the content (counter, timestamp, payload) compared to (payload, counter, length, timestamp) before the policy change
Transport layer now uses a flexible, policy based design. In short: I you want to continue using queues, there's now a policy object in between, e.g.:
No more changes required (this is
LegacyFrameAcquisitionPolicy
running under the hood). In any case, have a look at xcphello_recorder.py and run it, even if you are an experienced user!P.S.: re-run
python setup.py develop
to rebuild extension module. Now I have to fix some over-heating problems (including myself), than I'll write some more words.