I assume this is because there is no precise 810.0 s floating point, and at any rate this is not mitigated by passing 810 time (without the decimal point). Still, to avoid errors in record keeping, ideally COSplay should record the instructions it receives and it executes. If there is no way to distinguish 809.9999 from 810.0 that means it's just as correct to record 810.0.
@faymanns thoughts?
An onset time of 810.0 s (
.tsv
file below)is represented by COSplay as 809.9999:
I assume this is because there is no precise 810.0 s floating point, and at any rate this is not mitigated by passing 810 time (without the decimal point). Still, to avoid errors in record keeping, ideally COSplay should record the instructions it receives and it executes. If there is no way to distinguish 809.9999 from 810.0 that means it's just as correct to record 810.0. @faymanns thoughts?