Codethink partnered with York Instruments on a project to develop a new Magnetoencephalogram (MEG) scanner to replace their existing apparatus. This is a neuroimaging device which maps brain activity by recording magnetic fields which are produced by naturally occurring electrical currents in the brain.
The problem at the time was that the capture-and-compute brain of the original scanner was difficult to repair or replace if there was a failure. This was due to the unavailability of the original equipment manufacturer (OEM), resulting in a lack of available parts.
Within the main apparatus of an MEG, superconducting quantum interference devices (SQUIDs), are used to measure very subtle changes in magnetic fields influenced by brain activity. These SQUIDs require super-cooling, commonly with liquid helium, which means that the apparatus to store them needs to be substantial. Liquid helium is also very dangerous to humans so a high level of due diligence is required for the safety of anyone interacting with the scanner. In their new MEG system, York Instruments replaced the SQUIDs used with Hybrid Quantum Interference Devices (HyQUIDs), which are able to operate at higher temperatures than SQUIDs and can operate more accurately. This has positive implications for the safety and cost of the MEG, as less coolant is required.
In this project, Codethink worked on both hardware and software, in a range of different areas including upgrading the Linux kernel used, assisting with updating U-boot, working on the in FPGA and CPLD firmware, working on the core data transfer protocols, the sample data multiplexer, and real-time-displays as well as further software assistance and consulting.
Codethink engineers worked on the full low-level command and control system for synchronising and monitoring a distributed network of data capturing systems. Throughout our time working with York Instruments, Codethink engineers ensured a high standard of code and documentation was maintained.
The development of York Instrument’s main data acquisition pipeline and a variety of GUIs was done in tandem with the hardware design in order to closely integrate the two. One of the most challenging aspects of the work involved developing a system that ensures hundreds of sensors, that were all connected to different computers, actually took measurements within microseconds of each other. Engineers managed this by means of a pair of counter rotating, fibre-optic loops, with a precise calibration algorithm.
The sensors send thousands of samples of data per second over the network to a single system. This system is required to rapidly match up each incoming sample so that all sample numbers are grouped together. Due to the volume of data that the system is required to match together and the minimal amount of time available to do it in, the multiplexer needs to be very efficient. Once the data has been gathered and grouped, it saves samples to HDF5 format and also multicasts to a LAN for real-time data consumers to present or process captured data in real time.
“The real time display we wrote implemented a noise cancellation system. The sizes of the magnetic field fluctuations caused by brain activity is tiny compared to electromagnetic noise created by external sources, such as a passing car. The noise cancellation system worked by having some extra sensors in the magnetically shielded room which were far enough from the head of the patient that they would not pick up the brain activity, only the noise. Then the readings for these were used with some weightings to subtract the noise from the sensors around the brain.” - Michael Drake
Codethink’s engineers enjoyed working on a medical product, contributing to something that would, in turn, help others.
Other Content
- Codethink/Arm White Paper: Arm STLs at Runtime on Linux
- Speed Up Embedded Software Testing with QEMU
- Open Source Summit Europe (OSSEU) 2024
- Watch: Real-time Scheduling Fault Simulation
- Improving systemd’s integration testing infrastructure (part 2)
- Meet the Team: Laurence Urhegyi
- A new way to develop on Linux - Part II
- Shaping the future of GNOME: GUADEC 2024
- Developing a cryptographically secure bootloader for RISC-V in Rust
- Meet the Team: Philip Martin
- Improving systemd’s integration testing infrastructure (part 1)
- A new way to develop on Linux
- RISC-V Summit Europe 2024
- Safety Frontier: A Retrospective on ELISA
- Codethink sponsors Outreachy
- The Linux kernel is a CNA - so what?
- GNOME OS + systemd-sysupdate
- Codethink has achieved ISO 9001:2015 accreditation
- Outreachy internship: Improving end-to-end testing for GNOME
- Lessons learnt from building a distributed system in Rust
- FOSDEM 2024
- QAnvas and QAD: Streamlining UI Testing for Embedded Systems
- Outreachy: Supporting the open source community through mentorship programmes
- Using Git LFS and fast-import together
- Testing in a Box: Streamlining Embedded Systems Testing
- SDV Europe: What Codethink has planned
- How do Hardware Security Modules impact the automotive sector? The final blog in a three part discussion
- How do Hardware Security Modules impact the automotive sector? Part two of a three part discussion
- How do Hardware Security Modules impact the automotive sector? Part one of a three part discussion
- Automated Kernel Testing on RISC-V Hardware
- Automated end-to-end testing for Android Automotive on Hardware
- GUADEC 2023
- Embedded Open Source Summit 2023
- RISC-V: Exploring a Bug in Stack Unwinding
- Adding RISC-V Vector Cryptography Extension support to QEMU
- Introducing Our New Open-Source Tool: Quality Assurance Daemon
- Achieving Long-Term Maintainability with Open Source
- FOSDEM 2023
- Think before you Pip
- BuildStream 2.0 is here, just in time for the holidays!
- A Valuable & Comprehensive Firmware Code Review by Codethink
- GNOME OS & Atomic Upgrades on the PinePhone
- Flathub-Codethink Collaboration
- Codethink proudly sponsors GUADEC 2022
- Tracking Down an Obscure Reproducibility Bug in glibc
- Web app test automation with `cdt`
- FOSDEM Testing and Automation talk
- Protecting your project from dependency access problems
- Full archive