Enquire Now
70+ Topics · Spectre · Spectre · cloud sim Sim · MATLAB · Webots · Hardware · Bangalore 2026

Arduino Dashcam Trigger

Simulation · Control · Perception · Hardware — 12 Lead ECG Acquisition — hardware, sensors, cloud dashboards and protocols (Spectre, REST, CoAP, WebSockets) for BE BTech MTech students. Final-year robotics support with Spectre stacks, simulation worlds, reports and viva from Bangalore.

70+
Related Topics
6+
Sim & HW Tools
4.9★
573 Ratings

Interdisciplinary Journal of AI, Machine Learning & Data Science

(Ijaimlds)

© 2026 The Author(s) | Published by - Scholiora Research Publications Creative Commons Attribution 4.0 International License (CC BY 4.0)

Kandivali, Mumbai, 400101, Maharashtra, India

2Sr. Software Engineer, Here Technologies, Mumbai, 400063, Maharashtra, India Technology, Kandivali, Mumbai, 400101, Maharashtra, India Received: 27/02/2026 Revision Received: 30/03/2026

Abstract

EdgeAware is a distributed threat detection and monitoring system designed for smart-city applications where quick and coordinated actions are required for public safety and infrastructure management. Traditional city monitoring systems often rely on centralized processing and single threat event processing, and it can suffer from high latency, heavy bandwidth usage, limited scalability, and reduced reliability under real-world variability such as different viewpoints and domains. Many academic prototypes lack operational support for validation of event and multi-event monitoring. To address these gaps, EdgeAware integrates edge computing with a centralized monitoring workflow. The system demonstrates two multi- view object detection models for the detection of accident and pothole events, trained on YOLOv11s architecture using diverse perspective images from dashcam, drones, and surveillance system. It improves generalization across different domains and viewpoints. For edge deployment, models are converted to TensorFlow Lite and executed in an Android application that performs real-time inference on live camera streams. The app supports IoU- based tracking to filter duplicate detections, enabling event-level reporting. It transmits only representative frame per unique event, encrypted together with metadata and location information for secure and bandwidth-efficient communication. A backend platform is used for ingesting the events and providing a monitoring dashboard with visualization using Here Maps. This is for administrative validation and coordination with response teams such as police, ambulance, and road maintenance teams.

arduino-dashcam-trigger Diagram
Figure: System Model & Simulation Flow for Arduino Dashcam Trigger

The experimental results have also shown good quality in the detection aspect, with also resulted in an average time of approximately 90 ms and a runtime end-to-end latency of 1.5 s, as well as a reduced storage footprint through compression.

arduino-dashcam-trigger Diagram
Figure: System Model & Simulation Flow for Arduino Dashcam Trigger

KEYWORDS: Computer vision, Deep learning, Object detection, YOLO, Accident detection, Pothole detection, Edge computing, Android, Smart city. Interdisciplinary Journal of AI, Machine Learning & Data Science

1.1 Introduction

Smart cities are designed to help citizens and municipal systems by using digital technologies into urban infrastructure and services. It needs to monitor city environments in real-time, understand threat events accurately, and react in a timely manner to avoid impact on public safety and infrastructure. Smart city applications include heterogeneous sources of inputs such as surveillance cameras, vehicle-based dashcams, drones (UAVs), and mobile devices that constantly collect large amounts of visual information. If this information is processed efficiently, it can offer intelligent insights for smart traffic control, road maintenance, public safety, and emergencies.

arduino-dashcam-trigger Diagram
Figure: System Model & Simulation Flow for Arduino Dashcam Trigger

Most smart city monitoring systems use centralized cloud processing that may be subject to issues such as latency, network congestion and privacy concerns. For time-critical threats such as road accidents or fires, small delay can cause the effectiveness of response and rescue operations. Therefore, smart city applications demand distributed intelligence, where detection and preliminary decision-making can be performed close to the data source i.e., at the edge devices. Events like potholes are less time-sensitive but automating reporting of such events can result into faster response time than manual reporting. Edge-based processing allows rapid local inference, reduces unnecessary data transmission, and can preserve privacy by sharing only essential information rather than raw video streams -. Fig. 1 shows the different threat events and emergency situations in urban environment . Edge computing can enable effective management system for such events in coordination with response team.

arduino-dashcam-trigger Diagram
Figure: System Model & Simulation Flow for Arduino Dashcam Trigger

Fig. 1 Various Threats In Urban Environment

Proposed system is designed as a multi-tier architecture that combines edge computing with centralized monitoring. The core idea behind this is to use widely available edge devices such as smartphones, drones, and embedded processors with cameras as active sensor and detection nodes. These nodes perform real-time object detection to identify threat events, generate alerts for each event, and transmit only selected evidence like, a single representative Interdisciplinary Journal of AI, Machine Learning & Data Science

(Ijaimlds)

© 2026 The Author(s) | Published by - Scholiora Research Publications Creative Commons Attribution 4.0 International License (CC BY 4.0) frame with encrypted metadata to monitoring system. This reduces bandwidth requirement and improves scalability of the system. It can be useful in any environment like urban or rural area, infrastructure facilities such as manufacturing units or in natural environment such as forests due to the variety of edge devices it can utilize.

arduino-dashcam-trigger Diagram
Figure: System Model & Simulation Flow for Arduino Dashcam Trigger

The proposed system supports general smart city use cases such as prioritization of emergency dispatch by providing location specific visual evidence to monitoring teams, rapid accident awareness, traffic and rerouting support, pothole and road safety reporting for maintenance and repairing schedule, and city-wide situation awareness by notifying events and emergencies. Multi-view training increases the detection quality of model by generalizing across different camera angles, altitudes, and lighting conditions. It is useful for robust real- world deployment. Overall, EdgeAware contributes a practical framework for accurate threat detection, secure event reporting, and potential coordinated response, aligned with key smart city goals of safety, efficiency, and urban governance.

arduino-dashcam-trigger Diagram
Figure: System Model & Simulation Flow for Arduino Dashcam Trigger

1.2 Motivation

There are three practical reasons behind the design of EdgeAware. First is response time is critical. It is vital for emergency response to accidents, as well as prompt scheduling of road maintenance for potholes, which reduces secondary accidents, congestion, and economic loss.

Centralized video analytics can have a high response time because raw video needs to be transmitted to a remote server. Edge computing seeks to minimize response time by computing analytics closer to the source, thus minimizing end-to-end latency .

Second, cities must deal with multiple types of events. Most of the literature is focused on single-purpose solutions such as accident response pipelines or only pothole detection system. In real-world scenarios, there is a need for unified monitoring of diverse events by agencies such as the municipal corporation/governance teams. There is a strong literature focus on accident response using video analytics, emergency reporting, etc. -, while other critical road threats such as potholes have received limited attention .

Third, edge computing introduces security and resource constraints. Edge devices such as mobile phones, small GPUs, embedded CPUs like Raspberry Pi, Jetson Nano are heterogeneous in nature and usually have limited resources. Reporting events through such devices must be achieved securely with minimum bandwidth, storage, and power. Surveys highlight that security, privacy, and interoperability are major challenges for edge deployment .

1.3 Problem Statement

Despite the availability of good cameras and network connectivity, current smart-city monitoring systems have several limitations: (i) Centralized processing requires continuously sending of high-volume video data, which increases bandwidth cost and increases the latency.

(ii) Existing systems are mostly designed for a single threat type and cannot be easily extended to multiple events. (iii) Generalization across viewpoints is limited in the existing system. Models trained on a specific camera setting cannot perform well when deployed on different viewpoints, resolutions, or lighting variations and weather conditions. (iv) Event reporting is often insecure or inefficient in sending full clips or many frames can violate privacy, consume storage, and overload network links.

Therefore, the problem addressed in the proposed system is to create a smart-city monitoring system that detect and report multiple road threats in real time, across heterogeneous camera Interdisciplinary Journal of AI, Machine Learning & Data Science

(Ijaimlds)

© 2026 The Author(s) | Published by - Scholiora Research Publications Creative Commons Attribution 4.0 International License (CC BY 4.0) viewpoints, while meeting edge benchmarks of low latency, low bandwidth, limited storage, and strong security.

The Objectives Of The Edgeaware Project Are:

1. To design a distributed architecture that performs real-time threat detection at the edge and supports potential coordinated response through a municipal backend platform.

2. To demonstrate multi-event monitoring using two object-detection models i.e. accident detection and pothole detection, trained on multi-view imagery to improve deployment flexibility.

3. To convert the trained models using TensorFlow Lite, enabling inference on android devices for edge deployment. 4. To implement an android application for demonstration that performs live multiple model inference, supports per-model confidence threshold setting, and uses IoU- based tracking and deduplication to convert frame-level detections into unique events.

5. To implement a backend system using Django and PostgreSQL that ingests event reports using REST APIs, visualizes them on dashboard with a map interface, enables administrator validation by visualizing evidence frame, and supports coordination with response teams.

To align the end-to-end pipeline with edge benchmarks including security using encrypted evidence and access control, low latency with on-device inference, low bandwidth by sending only evident frame per event rather than continuous video, and reduced storage by using compressed ML models.

1.5 Contributions

The key contributions of proposed system are as follows:

•

The system was developed as a complete operational workflow that connected real- time edge inference, secure event reporting, backend ingestion, map-based monitoring, and response coordination, rather than limiting the scope to offline detection evaluation.

•

Developed accident and pothole detectors trained on multi-view imagery (dashcam, UAV, surveillance) to improve generalization across diverse smart-city deployment contexts within a single platform.

•

Deployed YOLOv11s via TFLite on Android with per-model thresholding and IoU- based tracking to deduplicate detections and report only unique events, reducing alert noise and backend workload.

•

Transmitted only selected representative encrypted frame and metadata per unique event, improving privacy, lowering bandwidth and storage needs, and enabling scalable city-wide monitoring.

2.1 Existing Work

EdgeAware intersects three research areas: edge computing for smart-city services, video- based accident detection and emergency response, and road-condition monitoring (potholes) using computer vision.

Edge computing for smart cities: Industry surveys and systematic studies indicate an increasing adoption of hybrid edge–cloud architectures, driven by the demand for low-latency analytics in transportation and manufacturing . However, these studies also point out unresolved challenges such as interoperability, security, and the absence of standardized evaluation benchmarks -. Security surveys stress that edge systems must address threats like DDoS, malware injection, privacy breaches, and insecure device onboarding, while remaining energy-efficient and deployable on diverse devices . Lightweight cryptography techniques and resource-aware strategies have been investigated to enable optimized processing with minimal energy and CPU overhead on resource-constrained IoT nodes .

Various studies integrate sensor data and machine learning techniques to detect accidents and alert emergency services. Systems combining IoT and deep learning utilize sensors like accelerometers, impact sensors, and GPS with CNN models to detect events and trigger alerts . Vision-based approaches employ CCTV or dashcam video with CNN pipelines and third- party messaging APIs for real-time event dispatch . Systems that incorporate evidence reporting and visualization (e.g., sending images or 3D reconstructions) enhance situational awareness but may increase network load and security risks . Deep-learning video models (I3D, ConvLSTM) and feature fusion strategies enhance robustness to weather and viewpoint variations but still face challenges under occlusion and low-light conditions . Reviews of multi-angle crash video systems suggest that integrating multiple cameras improves accuracy and reduces latency, though computational cost and fog/night robustness remain significant limitations .

Pothole detection and road-condition monitoring: Pothole detection has been tackled using traditional image processing, vibration sensors, and more recently, object detection models. Benchmarking studies compare YOLO variants under challenging road conditions and report and generalization issues . Recent YOLOv8-based pothole detectors demonstrate high accuracy and low inference time, but many studies remain single-view and do not incorporate secure municipal workflows . UAV and aerial imagery introduce additional challenges for small-object detection, and lightweight variants modify YOLO backbones and feature pyramids to enhance small-target recall while maintaining a low parameter count for drone deployment .

Existing literature in this field suggests the need for an integrated, secure, multi-event monitoring platform that performs edge inference on different viewpoints across various domains and reports only relevant and concise evidence for validated response. The proposed system is designed to meet this need by combining multi-view training, edge-optimized TFLite deployment, and a centralized backend workflow for monitoring.

2.2 Literature Survey

Edge-aware smart-city systems are fundamentally linked to the broader trend of edge computing. George et al. integrate a literature review with cross-sector surveys and interviews to assert that hybrid edge–cloud setups can minimize latency and offer substantial ROI for transportation and industrial monitoring. Their strength lies in an adoption-centric perspective rooted in industry practices; however, their limitation is a strategic focus, acknowledging interoperability and security challenges but providing few standardized KPIs or deployable reference frameworks. Prasad et al. conduct a systematic analysis of edge enablers (MEC, SDN/NFV, microservices, containerization, orchestration) and primarily evaluate benefits through simulation, indicating that containerized MEC services can decrease latency and that intelligent scheduling might lower energy consumption. The advantage is a clear linkage from components to anticipated benefits; the limitation is the lack of real- hardware validation and the absence of common benchmarks for reproducible comparisons.

Security is repeatedly cited as a first-class requirement for edge use cases. Sheikh et al. provide a survey of edge security threats such as malware, DDoS attacks, privacy leakage, routing attacks, and ML-specific attacks such as poisoning and evasion. They also survey the corresponding mitigants such as AI-based intrusion detection systems, federated learning, blockchain integrity, and hardware trust anchors such as PUFs. The advantage is the development of a taxonomy for threat and mitigation; the disadvantage is the absence of benchmark security data sets and experimental evaluations, along with the requirement for energy-aware and quantum-resistant assumptions. Rozlomii et al. are closer to the edge with an experimental evaluation of lightweight cryptography for constrained devices such as those in the IoT ecosystem (e.g., Arduino and STM32). The advantage is the demonstration of the potential for lightweight ciphers to reduce CPU and energy overheads and improve device up-time; the disadvantage is the lack of device and hardware specificity regarding threat modelling and the absence of standardized cross-device evaluations.

From an operational perspective, Costa et al. in present an overview of emergency management in smart cities in relation to IoT-based detection-alert-mitigation architectures. The benefits include an overall system perspective that incorporates the relationships between detection, analysis, and response workflows. The disadvantages include poor consideration of cybersecurity aspects, scalability/fault tolerance verification, and data modeling standards, which become critical in handling large numbers of concurrent incident reports.

In the field of accident detection, there are studies based on pipelines using sensor-based approaches as well as those using vision-based approaches. A two-stage system is proposed by Pathik et al. in , using IoT sensors for force, GPS, and GSM signals, as well as transfer learning classifiers for embedded devices. The benefits include high accuracy and better generalization using ensemble approaches. The disadvantages include limited datasets for analysis, hardware dependencies and costs, as well as latency in notifications and poor consideration of secure evidence sharing. Nandini et al. in propose using CCTV video streams with a custom CNN architecture and OpenCV for analysis and Twilio for notifications. The advantage is an end-to-end pipeline that demonstrates feasibility in monitored areas; limitations include viewpoint and lighting generalization issues, limited privacy/security discussion, and no multi-event scope.

Aslam et al. improve accident reporting by incorporating visual evidence of situations using controllers such as ESP32, MQTT/GSM, and verification delays, which reduce false reporting. The advantage is improved situational awareness, while the limitation is increased bandwidth/privacy risk, especially with visuals, and potential verification delays conflicting Interdisciplinary Journal of AI, Machine Learning & Data Science

(Ijaimlds)

© 2026 The Author(s) | Published by - Scholiora Research Publications Creative Commons Attribution 4.0 International License (CC BY 4.0) with emergency response needs, without strong edge CV security/robustness. Adewopo and Elsayed propose a deep learning ensemble method using a combination of RGB and motion information (optical flow) with I3D and ConvLSTM2D, showing improved robustness against weather, with possible efficiency-oriented variants. While the advantage is using motion information, there is limited performance against occlusion/low lighting, false positives with static scenes, and explainability for verification by municipalities. SAFE ROAD AI surveys various methods using multiple views of crash videos, such as YOLO family, Mask R-CNN, optical flow, and tracking methods such as Kalman filters, concluding that using multiple views can help improve the accuracy and latency of response by minimizing blind spots of single cameras. It needs improvement in sparse datasets and performance in foggy or night conditions. It also lacks evaluation of edge constraints, and unified, secure reporting workflow.

For pothole detection, comparative studies have validated the YOLO family’s suitability while revealing gaps in their deployment. Lieskovská et al. have benchmarked YOLOv3, v5, v7 on road scenes, showing high accuracy with practical inference speeds (with YOLOv7 showing good performance). The benefits lie in evidence-based selection of models, while drawbacks include generalization challenges, issues with dataset diversity, and poor integration with municipal workflows and security requirements. Addanki and Lin have trained YOLOv8, showing high mAP and inference speeds, thus making them feasible for near real-time use. Drawbacks include limited testing with multiple views, a lack of device benchmarking, and inadequate investigation of compression/quantization effects, security, and bandwidth-aware reporting, which is critical for real-world Android deployment.

Additionally, Luo et al. proposed ESOD-YOLO for aerial view sensing. The authors proposed the use of the YOLOv8n baseline with a RepNIBMS backbone, WFPN fusion, a small object head, and tri-focal loss for improved accuracy with low parameters for UAVs.

The advantage of this proposal lies in the explicit optimization of small object detection for drone views. The limitation lies in the absence of the integration of smart city response with the end-to-end solution and the absence of the exploration of transferability for dashcam/CCTV and aerial views. Khanam and Hussain proposed an overview of the YOLOv11 architectural improvements such as the use of C3k2, SPPF, and attention modules.

The advantage lies in the improved accuracy-efficiency trade-offs. The limitation lies in the absence of task-based benchmarking and the use of TFLite for edge device studies. Collectively, these research works show that there are recurring gaps that inform the current smart city threat monitoring research and practice. For one, there is a need for better robustness with respect to variability in real-world scenarios, which includes multi-view scenes, scenes under low-light conditions, scenes with occlusion, scenes with fog or at night, as well as domain variability in different smart cities and roads. Furthermore, it is also clear from the research that smart city research and practice must look beyond single-purpose solutions and instead provide a solution for multi-event monitoring under a single workflow, allowing smart city authorities to manage multiple types of threats under a single, unified platform. Finally, there is a need for a holistic evaluation of edge computing performance, where latency, bandwidth, storage, and security/privacy are collectively optimized and validated, as opposed to isolated optimization/validation of model accuracy.

3. Methodology

EdgeAware is designed as a distributed pipeline with three layers including edge layer, communication layer and centralized control layer as shown in the Fig. 2. Edge layer includes inference on heterogeneous devices such as Mobile phones, CCTV cameras, vehicle mounted dashcam, drones etc. It is facilitated with the small GPUs and embedded CPUs. Event of various threats are generated at this layer and securely reported over the network through communication layer. Centralized control layer is responsible to receive these events and provide effective monitoring, validation, and potential response coordination.

Fig. 2 Three Architectural Layers Of Edgeaware

The main idea is to use the edge device as a first point of intelligence that performs detection and aggregation of events locally and only sends compact evidence. This minimizes bandwidth usage as well as latency compared to sending raw video data. On the other hand, the backend offers governance features such as event storage, visualization, and auditing required by municipal organizations.

The high-level architecture of EdgeAware can be described as a distributed pipeline that connects local intelligence to centralized municipal monitoring as well as coordination with response team. It has five main blocks that function as showed in Fig. 3.

Fig. 3 High-level architecture diagram of EdgeAware, including various blocks in the three layers for complete distributed pipeline. Interdisciplinary Journal of AI, Machine Learning & Data Science

(Ijaimlds)

© 2026 The Author(s) | Published by - Scholiora Research Publications Creative Commons Attribution 4.0 International License (CC BY 4.0) EdgeAware starts with the first layer of sensing visuals in the smart city, in this layer multiple edge devices function as distributed observers. It includes devices such as vehicle-mounted Android phone cameras for dashcam view, UAV/drone cameras for aerial view, and surveillance cameras installed alongside roads for roadside view. The main function of this module is to capture live video stream from its viewpoint and process them locally. Since these devices operate near the area where the incident is taking place, they can quickly identify any potential threat, even if network connectivity is not always available. Each edge device uses a YOLOv11s object detection model, which is converted to TensorFlow Lite (TFLite) format. This object detection model processes video frames from the live video stream, detecting objects such as, Accident, Pothole, etc. To avoid reporting the same real- world incident multiple times in successive video frames, EdgeAware uses an IoU-based tracking and filtering module. This module uses the Intersection over Union (IoU) method to match current object detections with previous detection. It provides a unique identity for each event and filter out redundant events if any. It helps reducing false alarms and avoid repetitive notifications which minimize bandwidth usage.

After a unique threat event is identified at the edge, a small event bundle is sent to the backend. This backend uses Python’s Django as a web framework, along with PostgreSQL as a data store. This part of the system is responsible for safe ingestion of events, validation of payload structure, safe storage of event metadata such as time, GPS location, device type, model used, confidence, and tracking ID. This backend acts as a central source of truth for threat events reported throughout the distributed edge nodes. This block also offers a dashboard to administrators such as those in a municipality or government organization.

Events received at this backend are visualized on a HERE Maps display to show their location, allowing administrators to see events within their operational area of interest. This part of the system allows administrators to inspect events through visual confirmation of threat events through an encrypted representative frame, as well as to invalidate a threat event if it is a false alarm. This step helps to increase overall system reliability through human interaction, reducing the impact of false positives on system operation, as well as building trust in automated system responses.

After validation, the system can support coordinated response by alerting appropriate teams based on threat types and severity. This may include alerting police and ambulance teams in the event of an accident or alerting road maintenance teams in the event of a pothole. It can be further expanded to automate response rules and prioritization.

The entire system is demonstrated through an android application for threat detection such as an accident and a pothole. Fig. 4 is the android edge runtime process flow for the detection and reporting of threat events.

(Ijaimlds)

© 2026 The Author(s) | Published by - Scholiora Research Publications Creative Commons Attribution 4.0 International License (CC BY 4.0) Fig. 4 Android runtime pipeline including camera stream, preprocessing, TFLite inference, post processing, tracking and secure event upload.

At runtime, the Android application first loads the required TFLite object detection models for the supported threats (for example, accident and pothole). It then starts a CameraX live stream and processes the incoming video frame-by-frame. Each frame is preprocessed (such as resizing and normalization) to match the model’s input format, after which TFLite inference is executed to obtain detections. If no threat is detected, the system immediately continues to the next frame to maintain real-time performance. When a threat is detected, the output is postprocessed using steps like Non-Maximum Suppression (NMS) and confidence- based filtering to remove duplicate or low-quality bounding boxes. The remaining detections are passed to an IoU-based tracker, which compares detections across consecutive frames to identify the same physical object/event and performs event-level deduplication. If the tracker decides that the detection corresponds to an already reported event, it is ignored and the pipeline continues. If it is identified as a new unique threat instance, the app selects a representative frame and encrypts the frame along with metadata (such as threat type, confidence, timestamp, and location). Finally, the encrypted payload is sent as an event report to the backend, ensuring security while reducing bandwidth by transmitting only one frame per unique threat rather than streaming continuous video.

In this system object detection models plays crucial role. Training object detection model that will support multi-view compatibility and evaluation of its feasibility for the deployment is itself a dedicated pipeline which is shown in the Fig 5.

(Ijaimlds)

© 2026 The Author(s) | Published by - Scholiora Research Publications Creative Commons Attribution 4.0 International License (CC BY 4.0) Fig. 5 Model lifecycle for multi-view training and edge deployment.

3.1 Data Collection

The demonstration focuses on two common road threats including accident representing collisions, overturned vehicles and pothole representing road-surface holes, cracks or severe pavement distress that can damage vehicles. Each threat is modeled using a dedicated YOLOv11s detector. Using separate models simplifies label space, allows different thresholds and anchors, and makes it easier to extend the platform by adding new specialized detectors such as fire, flooding, illegal dumping without retraining a single large multi-class model.

To improve deployment ability across smart-city settings, the training dataset is collected from multiple viewpoints such as street level imageries, surveillance cameras and aerial images. Street level imageries are collected from dashcams, phone-mounted vehicle cameras and augmenting the images using low angle, motion blur, changing exposures. Fixed surveillance cameras expressing high viewpoint stability, wide field-of-view and variable resolutions added to the dataset. UAV/drone imagery shows top-down or oblique view, smaller target scale and complex background which adds more diversity to the dataset.

Bounding-box annotations are created using consistent guidelines focusing on tight boxes around damaged road regions of potholes and relevant vehicle regions or collision indicators of accident. Some online videos containing potential accidents and pothole instances are gathered and frames are extracted from it to manually annotate. Also, already annotated images are gathered from online open-source datasets. Two-pass quality assurance process is used to ensure that the annotations having good quality by verifying invalid or duplicate boxes, class-name consistency, partial occlusion, nighttime glare and shadows using manual review.

Besides the annotated images that have accidents and potholes, some negative images from the same sources but without any accidents and potholes are added to the dataset. This negative data is included intentionally to provide context of what an image should look like when there are no accidents and potholes on the road. It helps to reduce false positives, meaning that the detectors will be able to identify real threats and differentiate them from the usual scenery on the road to improve the overall robustness and reliability of the detection system. Distribution of the dataset is given in the Table 1 for both the models showing the numbers of images per class.

928

Each of the subset mentioned in above Table 1 contains 50% street level images captured from dashcam, 30% aerial images and 20% images from surveillance cameras. Dataset is recommended to split into 70% training, 20% testing and 10% validation set.

3.2 Data Preprocessing

Data preprocessing involves standardization of input data as well as robustness enhancement.

Normalization,

color/illumination normalization. Frame extraction/filtering involves sampling video sources at a constant stride of 3-10 FPS to minimize redundancy while maximizing temporal diversity.

Images are resized to a size of 640x640, which is the input size during training, while maintaining the aspect ratio through letterboxing. Optionally, histogram equalization/adaptive normalization can also be performed to minimize exposure variation effects.

Data augmentation plays a crucial role in multi-view generalization. Geometric as well as photometric augmentations are part of a typical pipeline. Random scaling, translation,

Data

augmentation. Brightness/contrast adjustment, blur effects, rain/fog simulation, color adjustment are part of photometric data augmentation. Care is taken to avoid unrealistic scenarios that can induce noise in labels such as extreme rotations of road images. Albumentations, Scikit-image, OpenCV libraries are used for image data augmentation.

3.3 Model Training

YOLO models are popular for real-time object detection tasks owing to their good accuracy- speed trade-offs. The system proposed utilizes the YOLOv11s model for a balance of accuracy and deployment constraints for mobile/edge computing. An overview of YOLOv11 was published, which discussed the architectural advancements of the model for better efficiency and performance, such as optimized convolutional blocks and attention mechanisms, among others . YOLO models learn bounding boxes, objectness, and class probabilities. The model is trained using the Ultralytics tool. This simplifies the training of the model. It needs a dataset configuration file (YAML) which is created with class names and paths for the train, valid, and test datasets. The model is then trained with minimal setup and configuration of hyperparameters. Table 2 is a representation of the system configuration for training the model.

12.6

After that, training is performed by executing a single command that mention the various hyperparameters such as learning rate schedule, batch size, input resolution, optimizer, and augmentation strength. Early stopping is done by using validation mAP. Accident and pothole detectors are trained independently to allow tailored augmentation and sampling.

Hyperparameters used for both models are given in the Table 3. Accident data is sampled to include normal traffic scenes to reduce false positives, while pothole data includes varied road textures to avoid overfitting to a particular pavement style. Both tasks can be imbalanced, especially if accidents are rare. To handle that strategies such as balanced sampling and hard- negative mining is used. Some confusing non-event scenes are added to the dataset.

Table 3 Hyperparameters used for model training for each model

0.002

0.002

Augmentations scale, crop, blur, brightness, scale,

3.4 Model Evaluation

Evaluation is conducted along two dimensions; one is object detection quality and other is edge-deployment performance. The primary object-detection metrics are precision, recall, and mean Average Precision (mAP). For a given confidence threshold:

(𝑇𝑃+𝐹𝑁) (2)

Average Precision (AP) is computed as the area under the precision–recall curve. mAP averages AP across classes and IoU thresholds. Two commonly reported settings are Bounding-box overlap is measured using Intersection over Union (IoU):

Authors:

Peder EZ Larson 1, 2,* , Jenna ML Bernard1, James A Bankson 3, Nikolaj Bøgh 4, Robert A Bok1, Albert P. Chen 5, Charles H Cunningham 6,7, Jeremy Gordon1, Jan-Bernd Hövener 8, Christoffer Laustsen 4, Dirk Mayer 9,10, Mary A McLean11 12, Franz Schilling13, James Slater1, Jean-Luc Vanderheyden5, 14, Cornelius von Morze 15, Daniel B Vigneron1, 2, Duan Xu1, 2, and the HP 13C

94143, Usa.

Denmark. 5 GE Healthcare, Menlo Park, California, USA. 6 Physical Sciences, Sunnybrook Research Institute, Toronto, Ontario, Canada.

ansys-mri-compatible-device Diagram
Figure: System Model & Simulation Flow for Ansys Mri Compatible Device

8 Section Biomedical Imaging, Molecular Imaging North Competence Center (MOIN CC), Medicine, Baltimore, MD, USA. Cambridge, United Kingdom.

ansys-mri-compatible-device Diagram
Figure: System Model & Simulation Flow for Ansys Mri Compatible Device

14Jlvmi Consulting Llc, Dousman, Wi, Usa

#See Acknowledgements for a list of all HP 13C MRI Consensus Group Members This work was supported by the ISMRM Hyperpolarized Media MR Study Group, the ISMRM Hyperpolarization Methods & Equipment Study Group, and the Hyperpolarized MRI Technology Resource Center (NIH/NIBIB grant P41EB013598).

ansys-mri-compatible-device Diagram
Figure: System Model & Simulation Flow for Ansys Mri Compatible Device

Abstract

MRI with hyperpolarized (HP) 13C agents, also known as HP 13C MRI, can measure processes such as localized metabolism that is altered in numerous cancers, liver, heart, kidney diseases, and more. It has been translated into human studies during the past 10 years, with recent rapid growth in studies largely based on increasing availability of hyperpolarized agent preparation methods suitable for use in humans. This paper aims to capture the current successful practices for HP MRI human studies with [1-13C]pyruvate - by far the most commonly used agent, which sits at a key metabolic junction in glycolysis. The paper is divided into four major topic areas: (1) HP 13C-pyruvate preparation, (2) MRI system setup and calibrations, (3) data acquisition and image reconstruction, and (4) data analysis and quantification. In each area, we identified the key components for a successful study, summarized both published studies and current practices, and discuss evidence gaps, strengths, and limitations. This paper is the output of the “HP 13C MRI Consensus Group” as well as the ISMRM Hyperpolarized Media MR and Hyperpolarized Methods & Equipment study groups. It further aims to provide a comprehensive reference for future consensus building as the field continues to advance human studies with this metabolic imaging modality.

ansys-mri-compatible-device Diagram
Figure: System Model & Simulation Flow for Ansys Mri Compatible Device

Keywords: Hyperpolarized MRI, metabolic imaging, carbon-13, pyruvate, dissolution dynamic

Introduction

MRI with hyperpolarized 13C agents, also known as hyperpolarized (HP) 13C MRI, has shown great potential as a novel imaging modality, particularly for its ability to probe metabolic processes in real time. The first human studies with HP [1-13C]pyruvate were performed in 2011 in prostate cancer patients (1).

ansys-mri-compatible-device Diagram
Figure: System Model & Simulation Flow for Ansys Mri Compatible Device

Since then, there have been over 60 papers published with imaging results of human subjects from 13 different sites, with applications including prostate cancer, brain tumors, breast cancer, kidney cancer, pancreatic cancer, metastatic disease, liver disease, ischemic heart disease, diabetes and cardiomyopathies. The vast majority of these studies used [1-13C]pyruvate (1–63), where [2-13C]pyruvate (64) and 13C-urea (56) have been demonstrated too.

ansys-mri-compatible-device Diagram
Figure: System Model & Simulation Flow for Ansys Mri Compatible Device

As clinical HP 13C MRI advances, there is a growing need to build consensus for best practices, which are critical for comparing data across sites, performing multi-site trials,deploying methods to new sites, partnering with vendors, and potentially for obtaining broader regulatory approvals.

ansys-mri-compatible-device Diagram
Figure: System Model & Simulation Flow for Ansys Mri Compatible Device

In March 2022, we initiated an effort to build consensus within the HP 13C MRI community with this opportunity in mind, and it was greeted with strong enthusiasm. The “HP 13C MRI Consensus Group”, containing over 55 members from 27 sites, identified the area of greatest need and opportunity for consensus building to be HP [1-13C]pyruvate human

●

Pyruvate is the most mature and widely used HP agent and has the most significant translational evidence emphasizing the potential clinical impact.

●

Clinical trials, particularly multi-site trials, have the strongest need for consensus methods to ensure that data can be combined across sites. This work is a Position Paper for which the goal is to describe current successful practices and study methods for HP [1-13C]pyruvate human studies along with justification to support those practices. This is divided into four major topic areas: (1) HP 13C-pyruvate preparation, (2) MRI system setup and calibrations, (3) data acquisition and image reconstruction, and (4) data analysis and quantification (Fig. 1). The current successful practices and study methods include a literature review of published peer-reviewed journal papers showing human HP [1-13C]pyruvate study data, up to September 2022 (1–63), as well as new unpublished information from surveys of HP 13C study sites. Based on this information, we also highlight the evidence gaps, strengths, and limitations of current practices which are summarized at the end of each section.

ansys-mri-compatible-device Diagram
Figure: System Model & Simulation Flow for Ansys Mri Compatible Device

Figure 1: Illustration of the HP 13C MRI human study process, including the 4 major areas covered in this paper: Hyperpolarized 13C-pyruvate preparation, MRI system setup and calibration, Acquisition and Reconstruction, and Data Analysis and Quantification.

ansys-mri-compatible-device Diagram
Figure: System Model & Simulation Flow for Ansys Mri Compatible Device

Figure 2: Anatomical targets of HP [1-13C]pyruvate MRI human studies published up to September 2022.

Hyperpolarized 13C-Pyruvate Preparation

This section covers the processes for creating the HP agent, 13C pyruvate, and will include many aspects and considerations that are needed to safely and effectively prepare doses for metabolic imaging studies in human subjects. These include material, personnel, equipment and facility, fluid path preparation, quality control, and release.

ansys-mri-compatible-device Diagram
Figure: System Model & Simulation Flow for Ansys Mri Compatible Device

It is helpful to understand that the specifications of a dose of 13C pyruvate suitable for in vivo MR HP metabolic imaging were shaped in part by early preclinical studies performed by GE HealthCare summarized in Ref. (65). In short, the safety of the two novel drug components, 13C pyruvate and the electron paramagnetic agent (EPA) AH111501, were demonstrated in those studies. The more precise formulation of the dose suitable for human use was then determined from clinical studies (66) that included two Phase 1 clinical trials in young and elderly healthy volunteers without hyperpolarization of the 13C nuclei and another Phase 1/2a dose escalation and imaging feasibility study with HP 13C pyruvate in 31 prostate cancer patients at the With the exception of the first HP 13C imaging clinical trial, which utilized a prototype device in a cleanroom (1), all HP 13C studies performed in humans to date have utilized the SPINlab polarizer (manufactured by GE HealthCare). Consequently all doses of the HP 13C pyruvate delivered by SPINlab have been produced using the “SPINlab Pharmacy Kit” that serves as the container-closure system for the various drug components (13C pyruvic acid and EPA mixture, dissolution medium, and neutralization and dilution medium) during sample polarization, dissolution and quality control (QC) processes. Thus many aspects of the HP sample preparation considerations discussed below are related to the SPINlab instrument and the consumables designed to be used with it (67).

General Considerations

While more than 860 patients or healthy subjects having been injected with HP 13C pyruvate as of January 2022 without reports of any serious adverse events (68), HP 13C pyruvate injection remains an investigational MR contrast agent and can only be administered by those with Investigational New Drug (IND) exemption from the Food and Drug Administration (FDA) in the USA, a Clinical Trial Application (CTA) in Canada, approval from National Research Ethics Committee Services in the UK, or approval from the relevant local regulatory body. Thus, methods and processes involved to produce a dose should have patient safety as the first priority. Since utilizing dissolution dynamic nuclear polarization (dissolution-DNP) for human use is still a relatively new development, there are no existing published regulatory guidelines specifically for this method.

There are two major production styles that determine how various sites approach the agent preparation. In the US, the most common approach is to rely on a sterilizing filter (“Terminal Sterilization”) to ensure sterility of the final product, akin to PET tracer production, where a starting molecule with a radioisotope is processed using various other ingredients to make the final, desired and injectable contrast agent within a necessarily short amount of time (69). For these sites, sterilization of the components and accessories upstream of this filter are not required, although many of them were manufactured and tested following Good Manufacturing Practice (GMP) or Good Laboratory Practice (GLP) requirements. The filling process is usually performed under an ISO 5 laminar flow hood, but a clean room or an isolator is not required.

This approach is typically accompanied by testing the integrity of the sterilizing filter prior to release of the dose for injection. Typically, post release endotoxin and sterility tests are performed using an aliquot reserved from each released dose.

In the UK and EU, the most common approach is to more-closely follow sterile pharmaceutical compounding guidelines (70), where all components and ingredients are required to be sterile or manufactured under GMP guidelines and are assembled and filled within a clean room environment or an isolator system (“Sterile Preparation”). Typically a batch of Pharmacy Kits for HP 13C pyruvate injection are prepared together. The sterility of the final dose is also ensured by batch validation testing, in addition to the sterility of the ingredients and the sterile compounding process. The endotoxin and sterility testing are performed for the process validation but are not performed for each injected dose.

Some institutions fill and assemble the Pharmacy Kit required for a specific study on the same day or the day prior to polarization, dissolution, and patient administration, but others have also demonstrated the feasibility of preparing a batch of kits, keeping them in a -20ºC freezer and using them over a period of a few months.

Beyond the obvious requirements that the process and the facility has to ultimately produce a dose that is safe to inject into a human, regulatory authorities will also focus on the question “Are you in control of your processes?”. To be in control of your process requires an in-depth and broad understanding of all processes involved in pre, post, and during the production process.

Personnel

It is typical and may be required to have licensed personnel involved in the production process depending on local regulations.Typically a pharmacist, radiopharmacist or other similarly qualified person (QP), in charge of the facility where the Pharmacy Kit filling and preparation is taking place, is responsible for the overall process and the release of the injectable dose.

Qualified cleanroom technicians are often involved in the Pharmacy Kit filling under the supervision of the pharmacist or QP. As is required for pharmaceutical compounding or PET tracer production, training requirements and training records for all personnel need to be maintained and available for audit by the FDA or equivalent.

Equipment And Facility

The facility and all equipment need to have standard operating procedures (SOPs) that describe how equipment is used, maintained, and calibrated to comply with relevant legislation. Currently, almost all the filling of the Pharmacy Kit takes place within a compounding laminar flow hood or isolator (typically ISO 5). At some sites, the filling is conducted within a cleanroom, while at others, it is conducted in a dedicated non-cleanroom space, reflecting differences in cleanroom approach and specifications between regulators worldwide (71). Some equipment or facilities, such as the compounding hood or cleanroom, may require external certified laboratories for testing.

Material Handling

Material handling guidelines (69,70) require SOPs detailing a system to track all of the materials involved in the HP production process for a particular patient dose, similar to current good manufacturing practice (cGMP) requirements for material handling for drug compounding. This includes acceptance standards, storage conditions, amount used in the patient dose for each ingredient and materials used in the assembly of the fluid path and Pharmacy Kit. Currently some users choose to open and inspect and sometimes modify the Pharmacy Kits upon arrival, but some users keep them in the sealed packaging until they are required for dose preparation.

Pharmacy Kit Filling And Assembling

As required by an IND or its equivalent, the preparation of the doses of HP 13C agent are detailed in the Chemistry, Manufacturing, and Control (CMC) section of an applicable regulatory submission; an example of this has been made available (72). It describes the processes of filling the Pharmacy Kit with the different components that make up the final drug product, and of assembling the final kit for either storage or immediate use in the polarizer. Special attention should be given to the laser welding process in order to satisfy installation qualification (IQ) and operational qualification (OQ). Typically, the final developed process is validated by process qualification (PQ) runs, during which 3 or more Pharmacy Kits are filled and used and the final HP 13C products are tested for endotoxin and sterility and to confirm that they meet the dose specifications for injections (usually including pyruvate concentration, residual EPA concentration, pH, liquid state polarization level and dose temperature). The data from 3 consecutive PQ runs are submitted as part of the IND submission (or its equivalent), and are often also reviewed by the Institutional Review Board (IRB) where the studies are conducted.

Quality Control And Dose Release

The quality control (QC) and dose release can be separated into two aspects: one is the QC and release of the filled Pharmacy Kit, and second is the QC and release of the HP 13C agent for injection, after polarization and dissolution. For institutions filling a batch of kits and storing them to use over a period of time, typically the batch can be released based on initial validation, environmental monitoring data from the day of kit production, and if filters are used during preparation of any of the components, filter integrity testing. But in some cases one or more kits are used for validation before the batch of kits are released for future use. For institutions that fill only the kits required for specific studies shortly before the experiment, the filled kits often do not go through separate release tests before they are used.

The quality control of the HP 13C pyruvate solution post dissolution is primarily performed to ensure that the agent meets the dose specifications (Table 1) before it is administered to the subject. These specifications target both safety (pH, residual EPA, temperature) and efficacy (pyruvate concentration, polarization, volume). Typically, the pyruvate concentration, residual EPA concentration, pH, dose temperature, dose volume, and liquid state polarization are measured by the QC accessory associated with the SPINlab polarizer. Some users perform a secondary measurement for one of the parameters, such as pH, using a different instrument or pH paper. For sites that do not go through a separate release testing process for batch filled kits, the integrity of the sterilization assurance filter, a part of the Pharmacy Kit, is typically tested as a part of the dose release. It is also common for these users to preserve an aliquot of the final HP 13C pyruvate solution for post-release endotoxin and sterility testing. This testing cannot be completed fast enough to test an individual dose prior to injection, but this is why other processes such as PQ runs and validation testing are done to minimize the chance a subject could be injected with a contaminated dose.

The Final Dose Release And Injection

should be done under the supervision of a licensed professional, based on local regulations.

Some Key Challenges

Many of the challenges associated with HP 13C pyruvate preparation can be attributed to the conditions required for the dissolution-DNP method of high magnetic field (~3-7 T) and very low temperature (~1 K) during polarization, with pressurized and superheated water necessary for the rapid dissolution event. These extreme conditions are quite challenging for the design of the container-closure and fluid path system. In particular, the cryogenic temperature in the polarizer requires special attention to any moisture or ambient (moist) air introduced into that portion of the fluid path, which can form an ice block at ~1 K. This ice can lead to flow restriction during the dissolution event and reduce the strength of the laser welded bond between the cryovial and its cap. This can ultimately produce failures in the dissolution step, including variations in final pyruvate concentration and pH that may fail to meet QC release criteria as well as fluid path ruptures that provide no available dose and result in polarizer down-time.

The polarization of the HP 13C pyruvate sample decays quickly over the span of a few minutes after dissolution, and thus the process of dissolution, QC for release, and injection should be completed as fast as possible to preserve the high polarization level achieved. Any delays in the preparation process, such as transportation time or equipment malfunction, can significantly reduce the final polarization and result in lower quality imaging data.

Current Practices

A summary of data collected from all sites performing clinical trials with HP 13C-pyruvate is shown in Fig. 3 and Table 1, including the specification of the final dose and how the quality control and release of the final dose are performed. There is a split in the Production Style, described in the General Considerations section above, with 8/13 sites using Sterile Preparation versus 5/13 using Terminal Sterilization. While many of the dose specifications show notable differences in acceptable ranges, all of these variations listed in tables have been successfully and safely been used to perform HP 13C pyruvate studies in humans. Their differences depend on the institutions’ preferences, resources and their particular regulatory situation. There is high similarity in pyruvate ranges, temperature ranges, EPA limits, and volume limits. There is modest variability in pH ranges and large variability in the endotoxin test limit. There is a 3-fold difference in acceptable polarization levels, which are measured to ensure a futile dose is not injected since the polarization is directly proportional to SNR. This reflects the decision by several sites to believe that useful data can be still be obtained with suboptimal polarizations.

Figure 3: Hyperpolarized agent preparation methods reported by sites currently performing HP

In House

Table 1: HP 13C-pyruvate preparation parameters, methods, and dose specifications used for quality control testing and release as well as validation. These were obtained from a survey of all sites performing clinical trials with HP [1-13C]pyruvate. The parameters used for product release are noted in bold text, otherwise these parameters are measured for batch validation or other QC measurements. The endotoxin and sterility testing are performed during process validation of the batch and/or post-injection, and largely depends on the agent production approach.

Summary

The overall safety record of HP 13C-pyruvate has been very strong, and the SPINlab hyperpolarizer has proven to provide high polarizations at human sized doses while meeting numerous QC and release criteria. A weakness remains the failure modes of the SPINlab Phamacy Kits (e.g. ice blocks, path ruptures), which are placed under extreme requirements particularly during dissolution. The preparation process still requires a high degree of expertise.

Therefore, there is a significant need to improve the reliability, robustness, and ease of operation for generating HP 13C-pyruvate doses for human studies. Furthermore, there is a divide between manufacturing and sterile compounding style preparation as well as other site-specific practices, resulting in variations in SOPs and justification required to relevant regulatory bodies. There have also been no comparisons between these approaches. It is also unclear what release criteria and QC parameters are truly required to ensure patient safety.

However, all of the reported methods are acceptable and approved by the appropriate regulatory authorities, and have led to the rapid expansion of successful human studies in recent years.

Mri System Setup And Calibrations

This section covers the MRI system setup, including the imaging system, RF coils, phantoms, and prescan calibration methods.

Imaging System

The main prerequisite for a given MRI scanner to be capable of supporting studies with HP 13C is its “broadband” capability to transmit and receive radiofrequency (RF) signal at the frequency of 13C, which is around 4 times lower than 1H. This does not come as a default on clinical MR devices. The transmit power of the broadband amplifier should also be sufficient to support the intended flip angle and RF pulse shape with the employed transmission RF coil(s) for 13C. Most studies to date use relatively low flip angles (< 90 degrees) for HP 13C in order to preserve polarization for time-resolved imaging. The capability to receive 13C signal on multiple channels is also desirable to increase SNR, as discussed further in the “RF coils” section.

The choice of magnetic field strength is primarily dependent on the metabolites’ frequency separation due to chemical shift dispersion and 1H imaging. High field strengths do not enhance hyperpolarized 13C signal as they do for 1H because the signal strength in a HP experiment relies on manipulating the population of quantum energy states outside of the MRI scanner.

However, the injected HP 13C-pyruvate and its metabolic products have greater frequency separation at higher fields, and it may thus be easier to separate and quantify these resonances at higher fields. This comes at the cost of a reduction in the achievable T2* and often reduced T1. As the initial polarization is independent of the imaging field strength it has been proposed that the increased T2* at 1.5T can potentially be exploited to increase SNR by adapting the acquisition bandwidth or reduce off-resonance imaging effects in cases when the decay of the transverse magnetization is dominated by T2* (73). In practice, 3T has been used in all published human 13C-pyruvate studies surveyed (Supporting Table S1), and comprises the majority of scanners currently in use for human studies (Table 3). A field strength of 3T is well-suited for 1H MRI anatomical reference and correlative imaging.

Stronger and more rapidly slewing magnetic field gradients support more rapid spatial encoding, particularly for metabolite-specific single-shot imaging using echo-planar imaging (EPI) or spiral imaging (See “Acquisition and Reconstruction”). Although the spatial resolution acquired for HP 13C imaging is typically much coarser than for 1H MRI, the factor of ~4 in gyromagnetic ratio leads to the same reduction factor in performance of the gradient system, so 13C experiments are potentially more limited by gradient hardware performance. To date, all human studies have used the commercially-available integrated gradient systems provided in clinical MRI scanners.

Optimization of scanner design has understandably focused on minimization of artifacts in 1H MRI, where devices such as room lights, the gradient amplifiers, and the motors driving the patient bed are checked to ensure that they do not produce RF interference at the 1H frequency, but artifacts may arise at other frequencies. Eddy current compensation is also not always appropriately adjusted for nuclei at other frequencies (74). In order to optimize for 13C, many sites have performed checks on phantoms for RF interference, gradient artifacts, and eddy currents (74), including the use of post-hoc gradient impulse response function characterisation and correction, and some vendors have fixed these issues as well.

Rf Coils

For HP 13C imaging studies in humans, RF coils for both 1H and 13C nuclei are needed, with 1H MRI providing an anatomical reference for registration and optional additional multiparametric MRI readouts. At the Larmor frequency of 13C nuclei, the relative contributions from coil noise compared to sample noise increase compared to 1H (73,75), although sample noise still is likely the dominant contributor for human-sized coils at 32.1MHz - the resonance frequency of 13C nuclei at 3T.

The key requirement for human 13C-pyruvate RF coils are that the coil geometry and sensitive volume must cover the volume of interest in the subject. Table 2 and Figure 4 shows coil configurations that have been used and optimized for applications in different anatomic regions.

Volume resonators are most commonly used for transmit, as they surround the subject to

Provide B1 Transmit Across The Fov (B1

+). While 1H relies on a large birdcage (“body”) coil built into the scanner, 13C transmit coils must be placed inside the bore. This takes up valuable space within the magnet, and also has led to the use of designs with relatively inhomogeneous

B1

+. Many human studies have used Helmholz pair resonators for transmit, including the “clamshell coil”, which has a notably inhomogeneous B1

+ Profile But Has Been Used Because Of

relatively easy integration into the scanner bore. B1

+ Variation Results In Variations In The Flip

angles that control the use of the hyperpolarized magnetization and creates errors in common HP metrics (9,76). The exception are head coils, where birdcage designs with highly

Homogeneous B1

+ can be placed around the head while easily fitting inside the bore. As with 1H MRI, higher SNR can typically be achieved by smaller receive coil elements, such as surface coils or phased arrays, and the majority of 13C receive coils used have layouts similar to 1H phased arrays.

RF coil quality control is important to ensure proper functioning of the coils to provide consistent imaging quality, especially with limited natural abundance 13C signal in vivo. It typically involves 1) a physical integrity check of the coil cables and connectors and 2) phantom SNR tests to check the coil’s performance and to monitor it over time (see Phantoms below). An useful reference for RF coil quality control is outlined in the MRI accreditation program of the American College of Radiology (77) and can be adapted for 13C coils.

Notably, configurations for brain and prostate studies used dual-tuned 1H/13C coil designs, which greatly simplify workflow and registration of 1H and 13C images, as no switching of coils is needed.

(1)

Table 2: RF coil configurations reported for human HP [1-13C]pyruvate studies.

Tx = Transmit

coil, RX = receive coil. The commonly used “clamshell” TX coil is a Helmholz pair design. For 1H RF configurations, all used the Body coil for TX unless otherwise noted, and “repositioned” indicates the 13C coil was removed for 1H imaging. One representative reference is listed for each configuration. The RF coil configurations reported in the reviewed papers are shown in Supporting Table S1.

Figure 4: Examples of RF coil configurations used for human HP [1-13C]pyruvate brain studies. (A,B) 13C Clamshell TX (Helmholz pair) and 2× 4-channel paddle RX arrays. (C) 13C Birdcage volume TX and 32-channel RX array (RX array slides into TX coil). (D) 13C Birdcage volume TX and 24-channel RX array, combined with a 1H 8-channel RX array. Image reproduced with permission from Ref (16).

Phantoms

Since hyperpolarized magnetization is non-renewable, phantoms containing 13C nuclei are important to: 1) test the multi-nuclear capabilities of the imaging system, including all parts of the signal excitation and receive chain; 2) perform calibration measurements before a scan with hyperpolarized nuclei; and 3) perform necessary pre-scan adjustments (see “Prescan Calibration” section). The phantoms currently in use are listed in Table 3. Their composition must provide sufficient 13C signal, with additional considerations of conductivity, stability, chemical shift(s) present, potential for dynamic imaging, and cost. The phantom geometries are typically either compact, in order to be used alongside the subject during a HP scan, or large enough to mimic the inner volume of a RF coil for system testing.

One popular compact design contains enriched 13C-urea at high concentration, typically 8 M, which provides a single resonance, placed inside a small container ~1 mL. The most common recipe mixes 13C-urea in a 90% water/10% glycerol solution, with glycerol used to increase the urea solubility and doping with a Gd-based contrast agent to shorten T1 which increases the potential SNR per unit time. For example, when Dotarem is added at a 3:1000 volume ratio the 13C-urea T1 is around 500 ms and T2 is around 100 ms. However, when testing pulse sequences influenced by T1 and T2, doping should be used carefully. This phantom is suitable for frequency calibration, transmit gain calibration, sequence testing, and as a fiducial marker when placed next to a patient. However, enriched 13C-urea has a relatively high cost compared to natural abundance compounds.

For larger volumes (>100 ml), the phantoms most often used contain undiluted ethylene glycol, glycerol, or dimethyl silicone. These compounds have sufficiently high carbon concentrations to provide sufficient 13C signal even with the 1.1% natural abundance of 13C. These larger phantoms matching the inner volume of an RF coil are useful for coil testing, including transmit

+) And Receive (B1

-) coil profile mapping, as well as to mimic acquisitions using in vivo FOV requirements. In this case, size and conductivity should match the expected subject size in order to mimic coil loading and get a realistic estimation of B1+. Large-volume natural abundance urea phantoms have also been used by some sites, but suffer from higher conductivity compared to biological tissues. Typically, it is easier to increase the conductivity and hence coil loading of the non-conductive phantom by adding NaCl to match physiological loading (16,78).

Dynamic phantoms that aim to mimic metabolite kinetics have also been developed (79–81), and have the potential to more closely mimic the HP experiment, but so far these are not widely used.

Prescan Calibration

Prior to performing an MRI acquisition, the so-called prescan procedure is used to set the shim parameters to maximize B0 homogeneity over the field of view (FOV) or a specific region of interest (ROI), the scanner center frequency (CF), the RF transmit gain, and the receiver gain.

While this calibration procedure is usually automated for 1H, the lack of sufficient natural abundance 13C signal prevents use of automated methods. (Although natural abundance 13C lipid signal has been detected, there are so far no reports on using this signal for prescan.) Table 3 shows current practices across sites.

Maximizing B0 homogeneity is independent of the nucleus and is therefore performed prior to 13C imaging using the 1H water signal and existing shimming tools, such as by a standard automated process (“Auto Shimming”) or using high order shimming routines. Similarly, the 13C CF can be calculated from the 1H CF using a predetermined scaling factor that depends on the target chemical shift (82). Another common approach used is to have a small, high-concentration 13C phantom, e.g. 8M 13C-urea, integrated in the RF coil or placed next to the scan subject (1). The reference frequency can also be based on real-time measurements after the HP injection but prior to imaging (83). Both the CF and B0 shimming are critical when using spectrally-selective RF pulses, as inmetabolite-specific imaging methods, where the desired excitation bandwidths are typically very narrow and frequency offsets can lead to a failure mode that is only apparent after injection.

The calibration of the RF transmit power is typically performed on a small, high-concentration 13C phantom placed near the region of interest during the scan or on a large 13C phantom of similar size and coil loading as the subject, prior to the subject scan. Reference power is often done by sweeping the power in a pulse-acquire sequence (53,62), or the Bloch-Siegert method (52,84). When using a small phantom, the location of the phantom, B1

+ Inhomogeneity As Well

as any shielding effects, e.g., when the phantom is integrated into a coil (1), may degrade the accuracy. Other methods include real-time Bloch-Siegert method measurements after the HP injection (83), and using the stronger natural abundance 23Na signal that is close enough to the 13C resonance frequency to be detected by 13C coils (82).

The receiver gain is predetermined, either systematically based on independent phantom measurements and assuming the dose and polarization of the HP compound is known prior to injection, or based on past HP imaging studies.

Power [Kw]

Phantom(s) - during study Phantom(s) - before study 13C Frequency

8

13C-bicarbonate doped with dimethyl silicone, various

Maximum Values

Table 3: Summary of the imaging systems, phantoms, and prescan procedures used at sites currently performing HP 13C-pyruvate human studies. These were obtained from a survey of all sites performing clinical trials with HP [1-13C]pyruvate. *Previously performed studies with a Siemens 3T Tim Trio. The imaging systems, phantoms, and prescan procedures reported in the reviewed papers are shown in Supporting Table S1.

Summary

Commercially available 3T MRI systems are by far the most commonly used for human HP 13C-pyruvate studies, although a systematic investigation of the impact of B0 has only recently been investigated (73). The multi-nuclear RF transmit and receive chain has proven sufficient for current acquisition strategies, although many sites have observed artifacts due to RF interference, gradient interference, and residual eddy currents when operating at the 13C frequency. A variety of 13C RF coils, tailored for numerous anatomical targets, have been successfully demonstrated, with the main limitation that most transmit coils take up a lot of additional space inside the bore and provide relatively inhomogeneous B1

+ Profiles. The

phantoms used have converged into generally 2 categories - small phantoms containing 13C-enriched compounds that can be used during the study and human-sized phantoms containing compounds with high carbon concentrations but without 13C enrichment that are used to test and calibrate the coils. There are no standardized compositions or geometry, and dynamic phantoms that recapitulate in vivo kinetics would be desirable but are still an emerging area. Prescan calibration procedures were not well defined in most publications, so we surveyed individual sites to determine current practices. Calibration procedures for the B0 field (13C CF and shimming) for most sites take advantage of 1H signal and methods, while methods

For Calibration Of B1

+ is more variable across sites, likely a reflection of remaining challenges in how to perform this calibration. Standardization of both phantoms and calibration procedures would synergistically improve the robustness and reproducibility of HP 13C studies.

Acquisition And Reconstruction

Data acquisition strategies in human HP [1-13C]pyruvate MRI studies must account for multiple chemical shifts, efficiently utilize the non-renewable HP magnetization, and acquire data quickly relative to metabolism and relaxation decay processes. These studies require spectral encoding to separate metabolites, necessitating pulse sequences that efficiently encode up to 5D data (3 spatial + 1 spectral + 1 temporal dimension). RF pulses must efficiently sample without immediately saturating the non-renewable HP magnetization, and sequences must acquire data quickly and be robust to both experimental and physiologic variation (e.g. B1

+ Inhomogeneity,

variation in perfusion) to ensure reproducibility and minimize scan-to-scan variability. This section covers current successful practices for data acquisition in human [1-13C]pyruvate studies, and accompanying 1H imaging, from different anatomic regions, including scan parameters and image reconstruction.

Acquisition And Reconstruction Methods

The acquisition methods used in human [1-13C]pyruvate studies can be classified into 3 categories: 1) MR spectroscopy or MR spectroscopic imaging (“MRS/I”), 2) chemical shift encoding methods, and 3) metabolite-specific imaging (Fig. 5).

Mrs/I Methods Specifically

resolve a spectrum that can be analyzed to extract expected as well as unexpected resonances, making this approach very robust. It was used in many initial studies (1).

Chemical Shift

encoding methods, most commonly the Iterative Decomposition of water and fat with Echo Asymmetry and Least-squares estimation (IDEAL) method, use imaging sequences acquired with multiple TEs and rely on a model-based separation of expected chemical shifts (85).

Metabolite-specific imaging methods use specialized RF pulses that are spatially and spectrally selective to excite individual metabolites which are then typically imaged with fast k-space trajectories such as echo planar imaging (EPI) or spirals (86).

Their Application To Different

organ systems is described below. The image reconstruction methods used in human [1-13C]pyruvate studies have typically been conventional methods (e.g. FFT, non-uniform FFT, or equivalent). The incorporation of accelerated imaging and advanced reconstruction methods including parallel imaging (4,57,87) and compressed sensing (7) has also been applied in human studies for improved spatial resolution, temporal resolution and coverage, but have the potential for additional artifacts as well as SNR losses due to ill-conditioning of the reconstruction (e.g. g-factor).

The Majority Of

published studies do not use accelerated imaging indicating the resolution and coverage achievable without acceleration is currently adequate for successful data collection. Performing coil combination, even with fully sampled data has also been shown to have specific challenges for HP human images: using naive sum-of-squares methods suffer from high noise amplification in the relatively low SNR regime of HP [1-13C]pyruvate (compared to 1H), motivating several HP 13C-specific methods that include data-driven coil sensitivity estimation which have shown obvious improvements over sum-of-squares (11).

More recently denoising techniques have been applied as post-processing of human HP data(41,42,44). The techniques applied are based on spatial-temporal singular value decomposition for unsupervised estimation of signal and noise components. They have shown improvements in apparent SNR in the brain and liver, while care must be taken to choose parameters such as the rank threshold to avoid oversmoothing and overfitting to the estimated signal components.

Prostate Studies

Prostate cancer was the first human application of HP [1-13C]pyruvate (1), and data was acquired with MRS/I methods: 1D dynamic MRS, single-slice 2D dynamic echo-planar spectroscopic imaging (EPSI), and single time point 3D EPSI. Advances in imaging strategies led to the development and application of new acquisition schemes, including undersampled 3D EPSI with compressed-sensing (7), model-based chemical shift encoding methods that use a priori information (47,59), and metabolite-specific EPI (10), all of which can provide volumetric whole-organ coverage and dynamic acquisitions.

The pyruvate bolus arrival in the prostate can vary by ± 10 s between patients, necessitating dynamic imaging to reliably and consistently capture the pyruvate bolus (18). For this reason, all currently ongoing studies acquire dynamic data. While MRS/I, chemical shift encoding, and metabolite-specific imaging can all achieve dynamic imaging, chemical shift encoding and metabolite-specific imaging provide greater dynamic and volumetric coverage (85). For scan prescriptions, the FOV is designed to provide full prostate coverage and typically to match the orientation of the anatomic imaging used for registration. Flip angles used in current studies are constant through time, as quantification with a variable-through-time flip scheme is highly sensitive to bolus timing (8) and errors in the RF transmit (B1 +) field (76).

Heart Studies

Data acquisition methods for 13C imaging in the heart must be designed to meet the demands of significant cardiac motion and blood flow. To cope with the periodic cardiac motion, most human heart studies to date used gating to the diastolic window, the longest cardiac cycle interval, which has reduced motion (2,22,28,30,35,36,38,45,52). The duration of the diastolic window limits the available data sampling time, making cardiac acquisitions the most time-constrained of the HP 13C MRI applications. The most common acquisition approach is metabolite-specific imaging with spiral k-space trajectories (2). Their single-shot imaging capability makes these methods particularly robust to motion effects. Furthermore, spiral k-space trajectories provide rapid k-space coverage and relatively benign flow and motion artifacts. The majority of studies have used 2D multi-slice acquisitions, but 3D encoding has also been used successfully (35).

Brain Studies

For HP 13C MRI of the human brain, the majority of studies have also used 2D (slice selective) acquisitions (10–12,14,16,28,33,40,41,44,51,53,60), with a trend toward volumetric coverage using 2D multi-slice metabolite-specific imaging. 3D metabolite-specific imaging of the whole brain, with phase encoding of the slice direction (34,57), has been shown to provide similar SNR efficiency (88) compared with multislice imaging. A number of studies have employed MRS/I (5,6,29,31–33,50,55) resulting in a spectrum from each voxel, which has the advantage of not requiring a priori information about which peaks to encode. This was important in early brain studies when it was not known which peaks would be detectable. Chemical shift encoding, using a set of images with different echo times and an iterative reconstruction of the individual resonances (i.e. the IDEAL approach (85)), has also been used (12,49,54), with the drawback that coverage in the slice direction was limited due to the time required to acquire multiple echo time images.

Abdomen And Breast Studies

The fundamental approaches to data acquisition and reconstruction in the abdomen and breast are largely similar to the aforementioned applications, but demand attention to particular challenges associated with these anatomic regions, especially relating to respiratory motion.

Although it has been shown that a basic 2D MRSI approach based on phase encoding and FID readout can be successfully applied for HP 13C imaging in breast (15) and kidney (13), major advantages in terms of spatiotemporal resolution and coverage have been realized using tailored approaches based on metabolite-specific imaging (43,62) and chemical shift encoding (43), which have facilitated multi-slice or 3D dynamic acquisitions over large FOVs in the abdomen (4,37,46).

The significant respiratory motion encountered in these regions can directly blur 13C images, and has further favored these rapid acquisition strategies. Motion also degrades B0 homogeneity, which can shift frequency-selective excitation profiles and introduce artifacts into rapid imaging readouts. This makes accurate determination of the acquisition center frequency and shimming essential in these regions which often cover large FOVs. (See “Prescan Calibration” section for more information). In some studies, breath-holding was used to minimize motion effects and enforce frame-to-frame data consistency (42). A pragmatic and reasonably effective approach for dealing with respiratory motion during 13C data acquisition is an initial breath-hold (as long as can be tolerated), followed by free-breathing (46,62).

1H Imaging

Collection of 1H imaging data is essential both for prescribing the 13C acquisition and for interpretation of the resulting 13C data. Multi-planar 1H scouts are acquired prior to 13C acquisition to enable graphical prescription of the 13C imaging region. All human HP 13C-pyruvate imaging studies acquire conventional MRI scans (e.g. T1- and T2-weighted volumes) for anatomic reference, aiming to cover at least the full 13C FOV. Acquiring these anatomic scans as close as possible to the time of 13C imaging (immediately before or after) minimizes potential misregistration between the data sets. Depending on the application, other advanced 1H sequences are also acquired (e.g. diffusion-weighted imaging for cancer imaging).

When contrast-enhanced data is acquired, it is done after 13C imaging, as paramagnetic contrast agents will accelerate 13C relaxation.

Reported Study Parameters

Figures 5 and 6, and Supporting Table S2 shows the reported acquisition study parameters for human HP [1-13C]pyruvate studies published as of September 2022. Figure 5 shows a mixture of MRS/I, metabolite-specific imaging, and chemical shift encoding methods have been successfully used, where spectroscopy-based methods have become less prevalent in recent studies. Figure 6 shows the acquisition timing, including the important start time and interval/temporal resolution, is quite variable across studies.

Figure 5: Acquisition methods used in published HP [1-13C]pyruvate human studies published up to September 2022, classified into: MR spectroscopy and spectroscopy imaging (MRS/I); chemical shift encoding methods, such as IDEAL, that use multiple TEs and model-based reconstructions; and metabolite-specific imaging methods that use spectrally-selective excitation to image a single resonance at a time.

Figure 6: Temporal acquisition characteristics reported in HP [1-13C]pyruvate human studies published up to September 2022. (a) Reported referencing of acquisition start times.

(B)

Acquisition start times reported when using dynamic imaging and when timing was reported relative to the end of the injection. (c) Temporal resolutions. “Not Applicable” indicates dynamic imaging was not used.

Summary

Three general categories of acquisition strategies have been used successfully for human HP 13C-pyruvate studies: MRS/I, model-based chemical shift encoding (e.g. IDEAL) methods, and metabolite-specific imaging methods. These have enabled successful studies in the prostate, heart, brain, abdomen, and breast. Recent studies increasingly have used the imaging-based strategies of metabolite-specific imaging and chemical shift encoding which are the fastest methods, although a heads-to–head comparison between techniques has not been performed.

Metabolite-specific imaging is quite popular because of its speed and compatibility with single-shot imaging, but is sensitive to B0 field variations and thus requires careful calibrations. Nearly all studies surveyed acquired data dynamically, allowing measurement of the bolus and metabolite kinetics. The exact timings and associated flip angles vary quite widely across reported studies, with no consensus yet as to how to choose these parameters. Image reconstruction is typically done directly using Fourier Transform methods, and accelerated imaging strategies are uncommon.

Data Analysis And Quantification

This section covers the analysis of data from human HP [1-13C]pyruvate studies, including modeling and metrics, visualization, as well as considerations for how to store data and metadata. Depending on study design, the analysis may need to give quantitative or semi-quantitative output reflecting a biological process or may just reflect a contrast between different regions of interest for quantitative evaluation.

Metrics

Figure 7: HP [1-13C]pyruvate raw data (A) have typically been quantified using four categories of metrics depending on the acquisition. Data acquired as a single time point are often quantified using normalized metabolite images or metabolite ratios (B). Dynamic data can be quantified using normalized metabolite images or metabolite ratios (B), or with metabolite timings such as time-to-peak (TTP) or pharmacokinetic (PK) models (C). The latter two require the data to be time-resolved. [1-13C]alanine and 13C-bicarbonate are analyzed similarly to [1-13C]lactate but omitted here for display.

Metabolite images are commonly used as summary metrics for HP MRI data, often including some form of normalization as well as summed over time as an area under the time curve (AUC) (17). These are analogous to the visual evaluation that is most used for routine clinical work (89,90). In these metabolite images, we expect that the [1-13C]pyruvate AUC signal is predominantly weighted towards perfusion and uptake, while [1-13C]lactate, [1-13C]alanine and 13C-bicarbonate AUCs represent metabolic conversion. The strength of this approach lies in its simplicity and relatively few underlying assumptions. Limitations to the use of single-metabolite images or AUCs include sensitivity to inhomogeneous coil profiles (57,87,91), the acquisition strategy and acquisition parameters, pyruvate polarization and concentration level, and signal relaxation rates (92). Further, the reader must be careful to interpret all the images in conjunction to better understand the underlying biology; for example, increased [1-13C]lactate in the presence of decreased [1-13C]pyruvate delivery can have a very different meaning compared to increased [1-13C]lactate with increased [1-13C]pyruvate delivery.

In an attempt to address variations in coil sensitivity, polarization level, and pyruvate delivery, AUC images are often computed by normalizing to a specified parameter, such as the maximum pyruvate or average lactate signals, or presented as a ratio such as lactate/pyruvate or divided by “total Carbon” - the sum total of HP 13C signal observed across all metabolites. The AUC ratios between metabolites and pyruvate are proportional to the corresponding forward kinetic rates (81,93), but are not directly comparable to rate constants when magnetization loss rates (e.g. relaxation and losses due to signal excitation) differ between studies. Similarly, the ratios between the produced metabolites (e.g. bicarbonate/lactate) can reflect the balance between downstream metabolic pathways (12,55). Care must be taken to consider how AUC images are calculated and normalized before comparing values between studies.

To further quantify the interpretation, pharmacokinetic (PK) modeling approaches were developed to compute the apparent kinetics of pyruvate-to-metabolite exchange (92,94–99). These yield semi-quantitative to quantitative apparent rate constants, given in s-1. Some models require a vascular input function, while others avoid this requirement (95). PK models can explicitly account for acquisition-specific details such as excitation angle and repetition time, and thus may reduce the effects of these details on quantification. An input-less model, provided in the Hyperpolarized-MRI-Toolbox (https://github.com/LarsonLab/hyperpolarized-mri-toolbox) (100) and thus frequently employed for human data, has been shown to fit well and robustly to prostate and brain data (8,20). PK models are quantitative in nature, arguably provide more relevant biological information (8,20), and appear to be reproducible across sites (51). However, rate constants derived from PK models are still apparent rates, and likely do not reflect a single biological characteristic.

Some additional considerations include whether complex or magnitude data is used, as the noise behaviors will impact the analysis differently. Additionally, cut-off thresholds or other criteria may be used to identify and avoid voxels with insufficient SNR before analysis to improve robustness (20,41).

Regardless of the analysis approach, the underlying biology is not always clearly represented by the data; instead, the metrics may be influenced by perfusion, barrier permeability, intercellular shuttles, enzyme activities, co-substrate concentrations, or combinations thereof, depending on the organ and disease of interest (19,43,94,101–103). This may be addressed by incorporating complementary information. As an example, HP 13C pyruvate data is influenced by perfusion, and thus addition of perfusion MRI could be important for interpretation (98,104,105).

All the methods outlined above have been explored in clinical studies, described in Supporting Table 3 and summarized in Figure 8. As of September 2022, approximately 52% of studies involving human subjects report rate constants derived from a PK model with a few different models reported. A nearly equal fraction (51%) of the studies report AUC ratio values.

Approximately 66% of these studies report metabolite-specific images or AUC values. About 40% report SNR values; this metric is particularly frequent in manuscripts that describe technical developments for clinical HP MRI. Approximately 16% of these studies summarize model-free metrics, and 10% report measurements from a single timepoint. Most studies report a combination of quantities.

Figure 8: Reported metrics used for analysis in HP [1-13C]pyruvate human studies published up to September 2022.

Visualization

A wide variety of approaches have been used for visualizing data from human HP 13C-MRI studies. The challenges and practical considerations are: 1) choosing the appropriate metrics to display, 2) how to encode the parameters (e.g. the colormap), and 3) choosing how to provide anatomical context and other multi-parametric data. The choice of visualization also depends on the goal which could be for diagnostic interpretation, but also quality control, reproducibility among readers and publication.

Metrics

The choice of HP 13C metrics is described in detail above. At this stage in HP 13C development where there is no standardized metric, often a combination of metabolite images and ratios or PK model parameters are shown.

Parameter Encoding

The mapping function chosen should provide an adequate, often quantitative, impression of the parameter mapped. There is a consensus in the visualization field that perceptually uniform maps are best suited to visualize continuous parameters, like the greyscale typically used by radiologists as well as other monochrome (black to blue) and color ranges (fire-type, rainbow-type) (106,107). Multi-color heatmaps have been the most frequently employed method for HP 13C data, while greyscale has infrequently been used but it ensures there is no coloring-based bias as well as facilitating later reuse (Fig. 9a). Among the color schemes employed in the clinical HP 13C literature, fire-type scheme seems to be the most common [similar to “Plasma” or “Inferno” in matplotlib.org]. Next most commonly employed is the rainbow-type scheme [similar to “Rainbow” in matplotlib.org].

Anatomical Context

HP MRI faces the challenge that it does not necessarily depict the anatomical features, similar to PET, and thus requires an anatomical reference. Most often, a grayscale anatomical image is overlaid with a HP colormap (Fig. 9c,d). This approach is very intuitive, but can skew perception as the grey-scale anatomical reference may affect the brightness of the HP data (e.g. signal in the skull). This bias does not occur when showing adjacent maps (Fig. 9a, b). Here, anatomical outlines may help to provide reference (Fig. 9b).

Related Journal Articles & DOI Links

Selected peer-reviewed publications relevant to 12 Lead ECG Acquisition. Click the DOI to access the full paper (may require institutional access).

Why Choose Us?

Bangalore guidance for robotics, Spectre and autonomous systems projects.

Spectre & Simulation

Gazebo, cloud twin and Webots worlds with navigation, SLAM and control stacks.

Control & Planning

Compliance, deep learning control, path planning and behavior trees.

Hardware Bring-up

Motors, sensors, ESP32/STM32 firmware and HIL validation paths.

Report & Viva

University-format documentation, PPT and viva preparation.

FAQ

Spectre, Gazebo, NVIDIA cloud twin, MATLAB/Simulink, Webots, Blynk / ThingSpeak, plus Arduino/STM32/ESP32, cameras, LiDAR and motor drivers.
Yes — simulation packages, hardware guidance, report, PPT and viva Q&A.