just to get the current state of tests
(next topic: get test coverage up ;) )

as a welcome page and with basic explanations on how to setup and run experiments.

When everthing is clear add a licence text. Hopefully MIT will be possible.

Also make repo public if OS licence is set

not sure if actually needed. Fix if requested

You can't do one without the other. Both migrations have to be done in one step.

• migrate to Python3 with 2to3

• get the input demos running

• get the visuals demo running

• get sound working again

• get the main thing running

• update documentation

• update start scripts

• validate windows runtime behaviour

in order to generate the documentation on each build (in a ci pipeline) a script is needed that compiles latex to a readable pdf

Pulse value is set to urge value

Is already built in int to issue #10

demVisuals curently runs in it's own runtime and duplicates some of the runtime code the experiment.
It also is a lot of code that can be replaced by some configured runs.

Goal:

• demo visuals runtie is gone
• demo visuals configuration is there with one configured run for each configuration feature to show

Use the full power of experiment configuration to show the full potential of the visual configurations instead of another program, which kinda doubles some parts of the logic

send one Pulse per recorded urge

how does the code find the folder of config and log?
a) constant relative path
b) system variable with path
c) configuration in code folder with paths

Choose one!

Check this for all supported input devices!
It seems that some computations that happen wehn computing the input value are instable and cause minor rounding errors, which might persist further and cause further numeric errors.

Check all Input Device value computations and harden the computation if possible.

unified configuration handler for each package, that provides default configuration