# swipe.futo.org's 5nd collection run

This collection expands to different languages and layouts to validate the encoder model's generalization capabilities.

The layout files are provided in `layouts/` subdirectory. The `swipe-5.jsonl` contains every layout and language, so you may want to filter it by `layout` and `language` columns.

## Sentences

The sentences used are subsets of Mozila Common Voice's processed sentences primarily from Wikipedia except for Polish. Sources:
* English: https://github.com/common-voice/common-voice/blob/main/server/data/en/wiki.en.txt
* Shavian: same as English with https://github.com/nwah/to-shavian applied
* German: https://github.com/common-voice/common-voice/blob/main/server/data/de/wiki.de.txt
* Spanish: https://github.com/common-voice/common-voice/blob/main/server/data/es/wiki.es.txt
* Lithuanian: https://github.com/common-voice/common-voice/blob/main/server/data/lt/wiki.lt.txt
* French: https://github.com/common-voice/common-voice/blob/main/server/data/fr/wiki-1.fr.txt
* Polish: https://github.com/common-voice/common-voice/blob/main/server/data/pl/selected-europarl-v7-pl.txt

The sentences have a strong encyclopedic and formal bias, so informal grammar and informal words will be underrepresented in this set.

## Dual-finger swiping

This collection also includes some nintype-style two-finger swipes. These allowed the user to make as many swipes and taps per word before continuing by tapping on spacebar. The "data" field is no longer an array of positions but contains `{"L": [...], "R": [...]}`, meant to represent left and right fingers. These were guessed by touchdown position x coordinate, so it's possible some words may have left/right reversed.

These lists contain lists of positions, representing a full swipe from touchdown to release. As an extremely simplified example, the world "hello" may have a data field like so

```json
"data": {
    "L": [
        /* H -> E swipe */
        [{"x": 0.6, "y": 0.5, "t": 0}, /*...*/ {"x": 0.25, "y": 0.166, "t": 30}]
    ],
    "R": [
        /* L tap */
        [{"x": 0.9, "y": 0.5, "t": 33}],

        /* L -> O swipe */
        [{"x": 0.9, "y": 0.5, "t": 36}, /*...*/ {"x": 0.85, "y": 0.166, "t": 67}]
    ]
}
```

You can filter for `"dual_finger":0` if you are not interested in two-finger swiping, since these can heavily complicate parsing logic and handling.

## Filtering

No filtering has been applied to this data. You can filter out most bad swipes through the `distance` field, but this may also filter out some valid swipes.

Due to complexity, the `distance` field is not computed for dual-finger swipes and their value is always `100004`.