Expensive models and experiments
PIML can reduce repeated simulation or experimental cost while retaining the governing knowledge used in Computer Engineering.
Engineering Research Community
Computer Engineering & Physics-Informed Machine Learning
Physics-grounded modelling, learning and validation for Computer Engineering
Computer Engineering designs processors, digital/analog hardware, embedded systems, computer architecture, memory, sensors, edge devices and hardware–software systems. It bridges electronics and computer science, often controlling or monitoring physical processes.
PIML can model semiconductor/electromagnetic/thermal behaviour, create digital twins of computing hardware and embed physical dynamics into edge or cyber-physical applications. It also enables physical computing substrates to participate directly in learning.
This page presents ten focused research areas, degree-level project pathways, selected publications and direct support through the PIMLS biweekly members meeting.
This Computer Engineering guide covers Physics-Informed Neural Networks (PINNs), physics-guided machine learning, scientific machine learning, neural operators, hybrid models and engineering digital twins. Explore the research and project pathways below, then join the Physics-Informed Machine Learning Society to connect with the international PIMLS community.
The central ideaEstablished Computer Engineering knowledge + measurements and simulation + machine learning
10focused research areas
3academic project pathways
6selected publications
Biweeklymember research meeting
Why this combination matters
Why Computer Engineering Needs Physics-Informed Learning
Use available scientific knowledge to make limited data more useful, transparent and testable.
Incomplete engineering models
Learn uncertain parameters, closures or discrepancies around an inspectable mechanistic foundation.
Transfer across conditions
Test whether structured models generalize across geometries, materials, assets, operating regimes or sites.
Trustworthy evidence
Use physical residuals, independent measurements, uncertainty and conventional engineering baselines before deployment.
Ten focused directions
Major Computer Engineering PIML Research Areas
Each card connects a meaningful Computer Engineering question with suitable scientific knowledge, modelling choices and evidence needed to test it.
01
Semiconductor Device Surrogates
Field and carrier equations are costly across geometry/bias. PIML opportunities: Use PDE/operators with device-solver verification.
Model and evidenceGoverning equations, calibrated measurements and held-out operating conditions
02
Circuit Parameter Estimation
Internal parameters drift and are indirectly observed. PIML opportunities: Use Kirchhoff/device equations and identifiable inverse models.
Model and evidenceMechanistic and data-only baselines, uncertainty and independent validation
03
Signal and Power Integrity
Interconnect fields and switching create noise. PIML opportunities: Train Maxwell/circuit-informed fast surrogates.
Model and evidenceGeometry, material or system parameters, sensor data and physical residuals
04
Processor Thermal Twins
Workload power creates spatial temperature fields. PIML opportunities: Fuse architecture counters, power and heat-transfer models.
Model and evidenceGoverning equations, calibrated measurements and held-out operating conditions
05
Data-Centre and Edge Cooling
Cooling must track computing load. PIML opportunities: Use physically consistent component models in MPC.
Model and evidenceMechanistic and data-only baselines, uncertainty and independent validation
06
Physical/Neuromorphic Computing
Analogue devices compute through real nonlinear dynamics. PIML opportunities: Use physics-aware in-situ training to compensate mismatch.
Model and evidenceGeometry, material or system parameters, sensor data and physical residuals
07
Embedded Virtual Sensors
Critical temperature/current/force may be unmeasured. PIML opportunities: Use stable dynamics-informed observers.
Model and evidenceGoverning equations, calibrated measurements and held-out operating conditions
08
Cyber-Physical Controllers
Embedded software interacts with plants. PIML opportunities: Co-model computation delay and physical dynamics.
Model and evidenceMechanistic and data-only baselines, uncertainty and independent validation
09
Robotics and Autonomous Hardware
Controllers face resource and actuator limits. PIML opportunities: Distil physical models while verifying timing and constraints.
Model and evidenceGeometry, material or system parameters, sensor data and physical residuals
10
Battery-Powered Systems
Energy, voltage, compute and radio loads couple. PIML opportunities: Use electrothermal models for runtime and safe scheduling.
Model and evidenceGoverning equations, calibrated measurements and held-out operating conditions
Choose the right research depth
Projects for Every Academic Stage
Start with a scope that matches your time, mathematical background, experimental access and expected research contribution.
Project pathway 1
B.E./B.Tech
Learn the foundations with a bounded, measurable system.
- Kirchhoff-constrained circuit learner
- processor lumped thermal model
- embedded virtual temperature sensor
- post-quantization physical-consistency test
Expected outcome
A reproducible implementation, clear baselines, a manageable dataset and physically meaningful validation.
Project pathway 2
M.Tech
Combine an engineering model, substantial data and rigorous comparison.
- chip thermal operator
- FPGA physics-informed accelerator
- adaptive edge cooling twin
- hardware degradation prognosis
Expected outcome
A thesis-quality study with held-out regimes, mechanistic and data-only baselines, ablation and uncertainty.
Project pathway 3
Ph.D.
Address a publishable methodological, multiscale or deployment research gap.
- device-to-system differentiable computer twin
- physics-aware neuromorphic learning hardware
- certifiable cyber-physical edge intelligence
- lifecycle PIML for reliable sustainable computing
Expected outcome
New methodology or validated engineering insight, multi-regime evidence, reproducible software and journal publications.
From idea to evidence
A Strong PIML Project Workflow
01
Define
Choose one Computer Engineering question and a measurable engineering output.
02
Model
State the governing relationships, constraints or validated domain knowledge you will retain.
03
Compare
Build mechanistic and data-only baselines before the hybrid model.
04
Validate
Hold out experiments, conditions, assets, sites or regimes at the deployment level.
05
Publish
Report uncertainty, ablation, limitations, data lineage and reproducible code.
Read before you modelDiscuss Your Literature
Selected Publications and Why They Matter
Use this focused reading list to understand the general PIML framework, direct Computer Engineering evidence and suitable hybrid modelling methods.
Literature review advice
Do not list papers only. Compare the engineering question, incorporated knowledge, data, split strategy, baselines, uncertainty and evidence level.
This source is included in the Computer Engineering literature guide because it demonstrates or reviews a relevant physics-informed, hybrid, inverse, surrogate or scientific-machine-learning approach. Read the methods, data split, baselines and validation evidence—not only the reported accuracy.
How to use this paper: Use this paper to refine the research question, identify a defensible physical prior and compare evidence requirements for Computer Engineering.
Read publication or record This source is included in the Computer Engineering literature guide because it demonstrates or reviews a relevant physics-informed, hybrid, inverse, surrogate or scientific-machine-learning approach. Read the methods, data split, baselines and validation evidence—not only the reported accuracy.
How to use this paper: Use this paper to refine the research question, identify a defensible physical prior and compare evidence requirements for Computer Engineering.
Read publication or record This source is included in the Computer Engineering literature guide because it demonstrates or reviews a relevant physics-informed, hybrid, inverse, surrogate or scientific-machine-learning approach. Read the methods, data split, baselines and validation evidence—not only the reported accuracy.
How to use this paper: Use this paper to refine the research question, identify a defensible physical prior and compare evidence requirements for Computer Engineering.
Read publication or record This source is included in the Computer Engineering literature guide because it demonstrates or reviews a relevant physics-informed, hybrid, inverse, surrogate or scientific-machine-learning approach. Read the methods, data split, baselines and validation evidence—not only the reported accuracy.
How to use this paper: Use this paper to refine the research question, identify a defensible physical prior and compare evidence requirements for Computer Engineering.
Read publication or record This source is included in the Computer Engineering literature guide because it demonstrates or reviews a relevant physics-informed, hybrid, inverse, surrogate or scientific-machine-learning approach. Read the methods, data split, baselines and validation evidence—not only the reported accuracy.
How to use this paper: Use this paper to refine the research question, identify a defensible physical prior and compare evidence requirements for Computer Engineering.
Read publication or record This source is included in the Computer Engineering literature guide because it demonstrates or reviews a relevant physics-informed, hybrid, inverse, surrogate or scientific-machine-learning approach. Read the methods, data split, baselines and validation evidence—not only the reported accuracy.
How to use this paper: Use this paper to refine the research question, identify a defensible physical prior and compare evidence requirements for Computer Engineering.
Read publication or record Build an interdisciplinary team
Where Computer Engineering Can Collaborate
Computer Science
Scientific ML, optimization, trustworthy AI and reproducible research software.
Applied Mathematics
Differential equations, numerical methods, inverse problems and uncertainty.
Sensing & Control
Instrumentation, data acquisition, state estimation and responsible deployment.
Domain Laboratories
Experiments, calibration, validation evidence and practical expertise for Computer Engineering.
Before you begin
Frequently Asked Research Questions
These answers help students avoid common scope, terminology and validation mistakes.
Still have a question?
Use the biweekly meeting form for research guidance.
Request accessNo. Computer Engineering projects may use physics-guided features, hybrid residual models, differentiable simulators, neural operators, constrained architectures or data assimilation. State exactly what knowledge is incorporated.
Choose one engineering question, a measurable output and a defensible mechanistic baseline. Add learning only where data can identify an uncertainty or discrepancy.
A meaningful question, justified prior knowledge, deployment-level holdouts, strong baselines, ablation, uncertainty, reproducibility and honest limitations.
Simulation can broaden coverage, but simulation-only evidence cannot establish real-system accuracy. Use calibrated experiments, field measurements or trusted independent references appropriate to the claim.
Submit the biweekly members meeting form to discuss your project level, branch, data, model, validation plan and possible collaborators.
Take the next step
Bring your Computer Engineering research idea to PIMLS
Join the biweekly members meeting for project guidance, collaboration and publication planning—or contact the Society directly.
Meeting participation is requested through the Google form. Complete it carefully so the Society can understand your research interest.