Sujet : devices
-
Mesurer sa vitesse de frappe chez soi : un protocole à texte et durée fixes, avec des règles écrites pour les mots et les erreurs
Ce protocole proposé pour un relevé personnel de vitesse de frappe inscrit les définitions dans le journal : un mot standard vaut cinq caractères, espaces compris, les débits brut et net suivent des formules explicites, et chaque session consigne le clavier, la disposition, le logiciel et le réglage de correction. Trois essais chronométrés de durée fixe portent sur des textes d’un type fixé, puis leur médiane est rapportée ; aucun débit, objectif ou progrès n’est annoncé.
-
A device battery health log: what phones, Windows laptops and the Linux power-supply interface report
A monthly log of the battery figures a device reports about itself: the iPhone Battery Health screen's maximum capacity relative to new, the HTML report from powercfg /batteryreport on Windows, and the charge_full and charge_full_design attributes of the Linux power-supply class; recorded raw with date, software version and events, the series shows the trend and its jumps without any charging advice.
-
Logging a consumer PM2.5 sensor: what to record beside each reading and what the number cannot say
A consumer particulate sensor reports an estimate of the mass of particles 2.5 micrometres and smaller; the EPA states that such sensors come with lower accuracy and higher uncertainty than regulatory monitors, describes collocation with reference instruments as an effective way to assess them, and notes that an outdoor correction may not apply indoors and that changing temperature and humidity may affect some sensors. A household log therefore stores the raw value, the averaging interval, placement, indoor events and the nearest official monitor's value with its distance.
-
A wrist step counter and a pocket phone diverge more on days with many short walking bouts and occupied hands
Hypothesis: two consumer step counters worn by one person, one on the wrist and one in a trouser pocket, disagree by a larger fraction on days the diary marks as many short walks or hands occupied (pram, bags, trolley) than on days with a few long walks, because the two devices read different body motions; a daily log with both devices stated is proposed as the test and no measurement is reported.
-
A home network device inventory: an observation table behind every row, and the MAC address as an observation rather than a key
A proposed record-only protocol for an inventory of devices on a home network: one row per physical device with a household name and a printed identifier, a separate append-only table of dated observations (MAC address, hostname, IP lease, source such as the router's client list or ip neigh), and first-seen and last-seen derived from that table; Apple and Android documentation describe randomised per-network Wi-Fi MAC addresses, so the MAC column is not used as the key; no security assessment or router configuration advice is given.
-
A personal typing error log with categories: aligning typed output against the source and coding each difference by a written rule
A proposed protocol for turning the stored output of typing trials into a categorised error log: align the typed text against the source with a difference tool such as Python's difflib, whose get_opcodes method returns replace, delete, insert and equal spans with index ranges, code every non-equal span with a fixed category list (adjacent-key substitution, transposition, omission, insertion, doubled letter, case, word substitution, autocorrection, other) with tie-break rules written before coding, and count per session with keyboard and software in the header; no error rate or cause is claimed.
-
Organising a personal photo archive: capture date from EXIF, exact duplicates by checksum, and an inventory that is checked yearly
A proposed method for bringing photos from phones, cameras and messaging apps into one archive: take the date from the EXIF DateTimeOriginal tag and its time-zone offset where present and mark files where only the file system date exists, find byte-identical copies with SHA-256 checksums before looking for re-encoded near-duplicates by eye, keep an inventory file that names every folder, and follow the Library of Congress advice to keep at least two copies and check readability yearly.
Lisible par machine : JSON