aforren1 / toon

47%

master: 80%

LAST BUILD ON BRANCH 0.7.0

branch: 0.7.0

CHANGE BRANCH

x

Reset

• 0.7.0
• 0.0.2
• 0.1.0
• 0.1.2
• 0.10.0
• 0.10.1
• 0.11.0
• 0.11.1
• 0.11.2
• 0.11.3
• 0.11.4
• 0.11.5
• 0.12.0
• 0.12.1
• 0.12.2
• 0.12.3
• 0.12.5
• 0.12.6
• 0.12.7
• 0.12.8
• 0.13.0
• 0.13.1
• 0.13.2
• 0.14.0
• 0.3.0
• 0.5.1
• 0.6.0
• 0.8.1
• 0.8.5
• 0.9.0
• 0.9.1
• 0.9.2
• anim
• clocks
• context
• devel
• docs
• fts
• master
• mk
• mpinput
• new-api
• pass-obj
• read
• sphinx
• trakstar
• travis

Build # 262

Build Type

push

travis-ci

Committed by web-flow

Commit Message

0.7.0 (#41)

Switch to a much simpler multiprocessing implementation, change keyboard backend, and allow tweaking of the remote process WRT garbage collection/priority.

 - Rather than shared arrays, we're sending a dictionary (with arbitrary data) via a `multiprocessing.Pipe`. Notes:
    - Pipe is unidirectional (only data from remote to local).
    - We don't lock access to the connections because a) Reduces performance, esp. >1kHz, and b) Not super necessary (no chance of data corruption, read function never gets a chance to finish at high frequencies, i.e. data is always available).
    - This montage seems to work fine at 2kHz, but above gets a little shaky. Haven't tried a fast "real" device yet.
    - Dicts get us a few things:
        a. Completely arbitrary data shapes, with little effort (no need to keep track of dimensions).
        b. Named data elements (e.g. `data['time']`, `data['rel_wheel']`)
 - Trying [pynput](https://github.com/moses-palmer/pynput) as the backend (key release for the previous version didn't seem quite right).
 - Allow running the remote process as high priority/low niceness (may need root on Unix platforms?), and optional disabling of garbage collection. Neither seems to make a *ton* of difference, but haven't tested beyond a few minutes.

Coverage Stats

123 of 123 new or added lines in 7 files covered. (100.0%)

217 of 466 relevant lines covered (46.57%)

0.93 hits per line