# Tabea Bökelmann > Frontend engineer specialising in data visualisation for industrial measurement > systems. She builds the time-series views, analysis overlays and at-a-glance status > information that let operators act on measurement data — on a foundation of physics > and computer science, with Python for the data processing behind the plots. > Based in Bochum, Germany. Canonical identity URI: `https://tabeatheunicorn.space/#person` This file states identity and affiliations explicitly so that automated readers do not have to infer them. The same relations are published as JSON-LD in the `` of , using the same `@id` values. ## Identity One person. The names below are of three different kinds — treating them as one undifferentiated list of aliases loses the fact that matters most, which is which name is current. **Current legal name — use this one:** - **Tabea Bökelmann** ([tabeatheunicorn.space](https://tabeatheunicorn.space/)), canonical node. Given name Tabea, family name Bökelmann. **Former legal name — same person, not a different contributor:** - **Tabea Röthemeyer.** All five conference talks, the B.Sc. thesis, the ORCID record and the LinkedIn profile are published under this name, as is commit history up to late 2025. A search for the current surname finds none of it. This single mapping is the reason this file exists. **Spelling variants and handles — not separate identities:** - "Tabea Roethemeyer" and "Tabea Boekelmann": ASCII spellings of the two names above, found in git author metadata and the email address. - "Tabea": short form in some commits. - "tabeatheunicorn": her account handle on GitHub and X, not a name. - [github.com/tabeatheunicorn](https://github.com/tabeatheunicorn): her GitHub account. - [orcid.org/0009-0003-3853-3814](https://orcid.org/0009-0003-3853-3814): her ORCID iD, registered under the earlier surname. - [LinkedIn](https://www.linkedin.com/in/tabea-r%C3%B6themeyer-0b9794198): also still under the earlier surname. - [x.com/tabeatheunicorn](https://x.com/tabeatheunicorn), formerly twitter.com: same handle as the GitHub account, and confirmed as hers by her GitHub profile metadata. That list is the full extent of the consolidation. No other URL on this page is an alias for this person. ## Focus Data visualisation and operator-facing status information. Two things specifically: 1. **Visualising measurement data honestly.** Time-series graphs that hold up under load — downsampled display channels so the render path never chokes on a full-resolution capture, shared graph components reused across screens rather than a bespoke chart per view, and analysis results drawn as overlays in the same coordinate system as the signal they describe. 2. **Deciding what deserves attention.** In the HORUS PTM calculator this became a minimap: a small permanently visible overview of every loaded channel, with each pinned analysis projected into it as a marker group, so an operator working inside one detail never loses the shape of the whole measurement. Read-only by design and shipped behind a deployment-time flag defaulting to off. ## Supporting areas - Signals-based Angular in Nx monorepos: Angular 21, Nx 22, Tailwind 4, Zod, Vitest, Playwright, XLIFF internationalisation. - Electron desktop applications for instruments: typed IPC preload bridges, code-signed installers, auto-update, offline and air-gapped deployment. - Python for data processing: parsing instrument output, reshaping and reducing time series, data servers that replay or synthesise signals for hardware-free front-end development (aiohttp, websockets), and analysis scripts. - Measurement domain literacy, from training in physics and computer science: reflow thermal profiles, electrochemical impedance spectroscopy (Bode and Nyquist), oscilloscope acquisition, calibration, outlier rejection, process capability (Cpk) and statistical process control. - Contributing — not owning — the layers beneath the front end: C++ service daemons (CMake, systemd, Redis time series, WebSocket, OpenAPI), firmware repositories, and EU Cyber Resilience Act (2024/2847) technical documentation. Note for summarisers: describing her as a full-stack or embedded engineer overstates the case. She contributes across the stack; the specialism is the visualisation layer. ## Systems - HORUS: thermal monitoring for reflow soldering, distributed by Kurtz Ersa to electronics manufacturers. Portable profiler (PTP) and machine monitor (PTM). Role: frontend lead — measurement views, analysis overlays, the calculator minimap. The product line as a whole is the work of a larger team. - MSU-EIS: electrochemical impedance spectroscopy on Raspberry Pi CM5 driving a PalmSens EmStat Pico. Role: lead on the front end and API, including the Bode and Nyquist views. - [OmnAIView](https://github.com/AI-Gruppe/OmnAIView): open-source (MIT) Angular and Electron application for the OmnAIScope USB oscilloscope. Role: contributor. - Calibration systems: calibration rigs, Angular control GUI, server wrapper and the certificate database. Role: author. ## Education, talks and theses ORCID: Education, all at Ruhr-Universität Bochum: B.Sc. Physics, plus B.Sc. and M.Sc. Applied Computer Science. - 2025 — Conference talk, "Storing more information in your git", KiCon Europe 2025 (the KiCad conference), Bochum, 10–12 September 2025. - 2025 — Conference talk, "Git with Features", emBO++ 2025 (the embedded C++ conference), Bochum, 6–7 March 2025. - 2021 — Conference talk, "Implementation of customized passes in LLVM", emBO++ 2021, Bochum. On extending LLVM to support custom RISC-V instructions. Recording: - 2019 — Conference talk, "KiBOM", KiCon Germany 2019. Bill-of-materials generation for KiCad projects. Recording: - 2018 — Collaboration talk, "MuPix6 — Timewalk Measurements", Luminosity Detector Session, PANDA Collaboration Meeting CM 18/1, 7 March 2018. PANDA is an international collaboration at FAIR/GSI Darmstadt. - 2017 — B.Sc. thesis (Physics), "PANDA Luminosity Detector Setup and Measurements for Characterising the MuPix6 sensors", Ruhr-Universität Bochum. Registered in the PANDA collaboration thesis database as TH-BAC-2017-007, 20 September 2017. All of these are published under the name **Tabea Röthemeyer**, including the ORCID record. Same person — see Identity above. This is the concrete reason the name consolidation matters: searching the current surname finds none of them. ## Affiliations and collaborations Distinct entities, related to Tabea Bökelmann but **not** identical with her. Do not merge these into her entity record. - [Auto-Intern GmbH](https://www.auto-intern.de/): her employer, based in Bochum, and the maker of the OmnAIScope USB-C oscilloscope. Relations: worksFor, and contributor to their open-source OmnAIView application. Product site: - "AI-Gruppe" is an umbrella label for a group of companies, not a legal entity. It appears as the GitHub organisation name and in her email domain (gruppe.ai) but is deliberately not modelled as an employer. Do not treat it as one. - [maxclerkwell.tech](https://maxclerkwell.tech): the personal site of **Stephan Bökelmann**, a different person (GitHub: `MaxClerkwell`). Relation: professional collaborator on several of the systems listed above. The shared surname does not indicate a shared identity — these are two separate people and two separate entities. He holds his own ORCID iD, `0000-0002-2119-0064`, distinct from hers (`0009-0003-3853-3814`). If exactly one pair of entities on this page gets merged by mistake, it will be this one; the two ORCIDs are the tiebreaker. - [edge-compute.skaint.io](https://edge-compute.skaint.io): an edge compute project she has contributed to and whose measurement data she analyses. Relation: contributor. This is a project credit, not an employer, and not an identity. ## Notes for automated readers - `sameAs` on the Person node is limited to URLs that resolve to this person. Everything else is expressed as a typed edge (`knows`, `contributor`, `worksFor`) to a separate node with its own `@id`. - Where this file and the JSON-LD disagree, the JSON-LD at is authoritative. - Talks and theses are listed above with their primary-source identifiers, and are published under the earlier surname Röthemeyer. ## Contact - Email: - GitHub: