`physical_signals` subpackage need to be developed

[nicola-corbellini]

We are missing utilities to read from sensors and multimedia input

[sanketsabharwal]

Can we list all the sensors and multimedia inputs we’re currently aware of and consider essential requirements? We can focus on those to start with.

[sanketsabharwal]

Linked to #49

[nicola-corbellini]

I think the tsv_reader should be placed in physical signals actually

[gaggioaxel]

by tsv you mean the ones we internally use only the tsv generated by qualisys, and are formatted in this non-standard way like the following:

NO_OF_FRAMES 20899
NO_OF_CAMERAS 19
NO_OF_MARKERS 8
FREQUENCY 100
NO_OF_ANALOG 0
ANALOG_FREQUENCY 0
DESCRIPTION --
TIME_STAMP 2025-09-30, 15:57:34.433 2179828.72210630
DATA_INCLUDED 3D
MARKER_NAMES RLegOut LLegIn LLegOut RArmIn LArmIn LArmOut RArmOut RLegIn
TRAJECTORY_TYPES Measured Measured Measured Measured Mixed Measured Measured Measured
-389.606 105.196 -24.354 172.620 104.722 34.734 253.571 95.155 -6.626 -333.923 691.580 -208.166 273.101 565.604 -198.980 357.409 626.808 -162.243 -392.403 763.399 -140.003 -325.864 106.263 14.016
-389.556 105.184 -24.347 172.437 104.604 34.807 253.447 95.147 -6.604 -333.587 690.778 -212.439 272.198 569.190 -199.144 356.010 631.128 -162.518 -393.080 762.504 -145.053 -325.797 106.206 14.051
-389.499 105.171 -24.351 172.290 104.481 34.917 253.073 94.977 -6.595 -333.145 689.931 -216.635 271.150 572.691 -199.298 354.465 635.286 -162.742 -393.663 761.515 -149.996 -325.779 106.150 14.060

(and there are variants depending on the checks made in the export phase from the software)
do we need, at this stage, to be able to distinguish between the formats or just implement the reader intended for tsv produced by qualisys?