Service scope and implementation plan
direction numberD60
Demand scenario8 items
main inputNIR/MIR scientific image; scientific RAW L1/L5; NIR/MIR sequence; infrared spectrum L5
Typical routeT01、T05、T13、T07、T03、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
IR473Star point detection, centroid and astronomical image registration
- Minimum input and technical route
- NIR/MIR scientific images;T01
- target output
- Star points, centroids, registration and overlays
- Implementation
- Reusable A31/A43
- critical acceptance
- Compared with star catalog/known transformation, center of mass error
IR474Dark field, flat field, bad pixel and cosmic ray correction
- Minimum input and technical route
- Science RAW L1/L5;T01
- target output
- Correction map, bad element/cosmic ray mask
- Implementation
- Requires scientific imaging process
- critical acceptance
- Standard Star/Darkfield Repeatability and Residuals
IR475Infrared celestial object detection and sequential photometry
- Minimum input and technical route
- NIR/MIR sequence;T05
- target output
- Objectives, light curves and uncertainties
- Implementation
- Requires astronomical calibration
- critical acceptance
- Compare with standard star/public pipeline
IR476Infrared spectral line detection, red shift and composition analysis
- Minimum input and technical route
- Infrared spectrum L5;T13
- target output
- Spectral lines, redshifts and fitting parameters
- Implementation
- Spectral core required
- critical acceptance
- Wavelength scaling, standard sources and fitting residuals
IR477Imaging dust-obscured regions and star-forming regions
- Minimum input and technical route
- NIR/MIR multi-band;T13
- target output
- Multiband synthesis, targets and structures
- Implementation
- Requires astronomical data process
- critical acceptance
- Compare with authoritative data products/star catalogs
IR478Thermal infrared detection of near-Earth objects and trajectory candidates
- Minimum input and technical route
- MIR/TIR sequences;T07
- target output
- Point targets, trajectories and brightness
- Implementation
- Requires astronomical point target algorithm
- critical acceptance
- Injection testing, false alarm rate, trajectory integrity rate
IR479Observation of spacecraft surface thermal state and thermal balance
- Minimum input and technical route
- MWIR/LWIR L2/L3；T03+T05
- target output
- Surface temperature field and thermal model residuals
- Implementation
- Vacuum/radiation model required
- critical acceptance
- Versus thermocouple/telemetry/thermal model
IR480Infrared scientific data versions, calibration files and reproducible processing
- Minimum input and technical route
- scientific data;T20
- target output
- Raw data, calibration products and processing pedigrees
- Implementation
- Data system required
- critical acceptance
- Version traceability, hashing, reprocessing consistency
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.