Service scope and implementation plan
direction numberD56
Demand scenario8 items
main inputL2/L5；L5；LWIR L3；MWIR/LWIR L2/L3
Typical routeT03、T10、T05、T17、T01、T20
The project scope is determined based on samples, equipment, working conditions and written indicators; general modules, special models and multi-sensor integration are configured according to the evaluation results.
Application scenarios and development content
IR441Blackbody calibration, emissivity and reflected temperature teaching experiments
- Minimum input and technical route
- L2/L5；T03
- target output
- Calibration curves, error budgets and experimental reports
- Implementation
- Need standard source
- critical acceptance
- Versus reference blackbody/contact temperature
IR442Visualization of thermal diffusivity and thermal conduction processes
- Minimum input and technical route
- L5；T10
- target output
- Thermal response curve, phase and physical property candidates
- Implementation
- Requires physical model
- critical acceptance
- Compare with standard material parameters
IR443Natural convection, jets and thermal plumes PIV/optical flow proxies
- Minimum input and technical route
- LWIR L3；T05
- target output
- Plume boundaries, velocity proxies and changes
- Implementation
- Partially reusable A68
- critical acceptance
- Compare with particle/hotline wind speed results
IR444Thermal processes of phase changes, crystallization, melting and solidification
- Minimum input and technical route
- MWIR/LWIR L2/L3；T05+T17
- target output
- Phase boundaries, temperature plateaus and time
- Implementation
- Material/microscopic truth required
- critical acceptance
- Phase boundary error, temperature/time synchronization
IR445Observation of Microheat Sources in Friction, Fracture and Fatigue Processes
- Minimum input and technical route
- Highly sensitive MWIR/LWIR L3;T05
- target output
- Heat source location, amplitude and timing
- Implementation
- Requires scientific research grade equipment
- critical acceptance
- Versus mechanics/acoustic emission, SNR
IR446Microfluidics, droplet evaporation and heat transfer research
- Minimum input and technical route
- Macro MWIR/LWIR L2/L3;T05
- target output
- Temperature fields, interfaces and evaporation curves
- Implementation
- Requires macro calibration
- critical acceptance
- Compare with true microscopic/temperature values
IR447Infrared camera NETD, dead pixels, stability and MTF testing
- Minimum input and technical route
- Blackbody/standard target L5;T01+T03
- target output
- Camera Performance Metrics and Uncertainty
- Implementation
- Need to test tooling
- critical acceptance
- Repeat testing to applicable standards/specifications
IR448Infrared algorithm public data benchmarks and reproducible experiments
- Minimum input and technical route
- public data;T20
- target output
- Fixed divisions, metrics, code versions and limits
- Implementation
- Executable research verification
- critical acceptance
- Hashes, environments, random seeds and full logs
Implementation and delivery methods
- Project input confirmationCheck camera, spectral band, bit depth, SDK, environmental conditions, sample and acceptance true value.
- Sample verificationVerify key processing links, applicable conditions and abnormal working conditions, and determine the development scope and acceptance methods.
- Algorithm development and integrationImplement data parsing, algorithms, quality gating, interfaces and target platform deployment.
- Test acceptance and handoverRetest according to the agreed test set and target platform, and hand over the deliverables, test results and applicable conditions.
- Requirements and technical solutions, input and output and interface field definitions
- Algorithm library, model or SDK/API; delivery form is confirmed in the project plan
- Sample program, parameter configuration, error status and calling instructions
- Test set version, indicator definition, stratification results and failed sample records
- Target platform adaptation, resource usage and running delay records
- Version, dependencies, license, reproduction steps and applicable conditions description
Acceptance design
Each scenario establishes independent test cases according to "key acceptance". When sharing models across scenarios, results are reported separately for each scenario, distance, load, environment, and target size, supplemented by overall statistics.
When high-risk alarms or controls are involved, the algorithm output is used for review or linkage judgment; safety functions, regulatory responsibilities, and automatic disposal require separate design and acceptance.
Frequently Asked Questions for Enterprise Customers
Can I purchase directly based on one of the scenes?
Can be evaluated first as a separate work package. The formal scope should describe the device, data, target objects, environment, interfaces, delivery form, and acceptance thresholds.
Can it be started when there are no abnormal samples?
The data interface, normal baseline, acquisition plan and simulation/controlled test design can be completed first; the abnormal detection rate and fault classification effect can be evaluated after obtaining sufficient abnormal true values.
Can the algorithm directly trigger alarms or equipment actions?
Duration, deduplication, quality gating, manual review, communication failure and safety interlocking need to be designed based on business risks. High-risk actions should be activated after completion of independent safety mechanisms and on-site acceptance.