Troubleshooting
This page provides diagnosis and solutions for common issues when using MipMapEngine SDK.
đ Diagnostic Toolsâ
When encountering issues, please first use the following diagnostic tools:
1. Configuration File Validationâ
task_json_check.exe -task_json your_config.json
2. Hardware Checkâ
hardware_check.exe
3. License Statusâ
license_manager.exe -info
đ Common Errors and Solutionsâ
Configuration File Errorsâ
Error: JSON Parse Failedâ
Error Message:
[ERROR] JSON parse failed: expected ',' or '}' at line 45
Cause: JSON format error, usually missing comma or extra comma.
Solution:
- Use JSON formatting tools to check syntax
- Ensure there is no comma after the last element
- Check for unclosed brackets or quotes
Example Fix:
// Wrong
{
"image_meta_data": [
{"id": 1, "path": "image1.jpg"}, // Last element should not have comma
]
}
// Correct
{
"image_meta_data": [
{"id": 1, "path": "image1.jpg"}
]
}
Error: Image File Not Foundâ
Error Message:
[ERROR] Image file not found: C:/images/DJI_0001.JPG
Cause: Specified image path is incorrect or file does not exist.
Solution:
- Check file path spelling
- Confirm file actually exists
- Use correct path separator (recommend using
/) - Try using absolute path
Path Examples:
// Windows - Recommended
"path": "C:/Projects/Images/DJI_0001.JPG"
// Windows - Also works
"path": "C:\\Projects\\Images\\DJI_0001.JPG"
// Relative path
"path": "../images/DJI_0001.JPG"
Error: Parameter Out of Rangeâ
Error Message:
[ERROR] Invalid resolution_level: 5 (should be 1-3)
Cause: Parameter value is not within allowed range.
Solution: Check and correct parameter values:
resolution_level: 1 (High), 2 (Medium), 3 (Low)input_image_type: 1 (RGB), 2 (Multispectral), 3 (Infrared)coordinate_system.type: 1 (Projected), 2 (Geographic), 3 (Geocentric)
Image Processing Errorsâ
Error: Insufficient Imagesâ
Error Message:
[ERROR] Insufficient images for reconstruction. Minimum 5 images required, found 3.
Cause: Too few images to perform 3D reconstruction.
Solution:
- Provide at least 5 images
- Ensure sufficient overlap between images (recommended >60%)
- Check if any images were automatically filtered (see logs)
Error: No GPS Informationâ
Error Message:
[WARNING] No GPS information found in image EXIF
Cause: No GPS information in image EXIF.
Solution:
- Use custom POS data:
{
"id": 1,
"path": "image.jpg",
"meta_data": {
"pos": [114.123, 22.456, 100.5],
"pos_sigma": [0.5, 0.5, 1.0]
}
}
- Reduce position constraints:
{
"use_image_position_constraint": false
}
Multi-Camera Reconstruction Issuesâ
Error: Camera Group Image Count Mismatchâ
Error Message:
[ERROR] Camera group image count mismatch: nadir(50), oblique_f(48)
Cause: Inconsistent image count across different camera groups.
Solution:
- Check if any images are missing
- Ensure multi-camera synchronous triggering works properly
- Use
task_json_checkto verify grouping configuration
Correct Grouping Example:
{
"image_meta_data": [
// Each position should have images from all cameras
{"id": 1, "path": "pos1/nadir.jpg", "group": "nadir"},
{"id": 2, "path": "pos1/forward.jpg", "group": "forward"},
{"id": 3, "path": "pos1/backward.jpg", "group": "backward"},
// ... next position
{"id": 4, "path": "pos2/nadir.jpg", "group": "nadir"},
{"id": 5, "path": "pos2/forward.jpg", "group": "forward"},
{"id": 6, "path": "pos2/backward.jpg", "group": "backward"}
]
}
Memory and Performance Issuesâ
Error: Out of Memoryâ
Error Message:
[ERROR] Out of memory. Required: 24GB, Available: 16GB
Cause: System memory insufficient to process current task.
Solution:
- Lower precision level:
{
"resolution_level": 3 // Use low precision
}
- Limit memory usage:
{
"min_avali_memory_size": 12.0 // Limit to 12GB
}
- Reduce output formats:
{
"generate_obj": true,
"generate_osgb": false, // Disable unnecessary outputs
"generate_3d_tiles": false
}
Error: GPU Out of Memoryâ
Error Message:
[ERROR] CUDA out of memory. Tried to allocate 2.00 GiB
Cause: Insufficient GPU memory.
Solution:
- Close other programs using GPU
- Lower
resolution_level - Use block processing (for large projects)
License Issuesâ
Error: Invalid Licenseâ
Error Message:
[ERROR] Invalid license: License has expired
Solution:
- Check license status:
license_manager.exe -info - Confirm system time is correct
- Reactivate license
- Contact technical support to update license
Error: Virbox Service Not Runningâ
Error Message:
[ERROR] Virbox service not running
Solution:
Windowsīŧ
# Start service
net start "Virbox Service"
# Check service status
sc query "Virbox Service"
Linuxīŧ
# Load driver
sudo modprobe virbox
# Check driver
lsmod | grep virbox
Output Result Issuesâ
Issue: Model Has Holesâ
Possible Causes:
- Insufficient image overlap
- Texture-poor areas (water surface, glass, etc.)
- Poor image quality
Solution:
- Increase image overlap to 80%
- Use oblique photography to supplement side views
- Avoid shooting in strong light or shadow conditions
- Check and remove blurry images
Issue: Blurry Textureâ
Possible Causes:
- Original images are blurry
- Flight altitude too high
- Improper camera settings
Solution:
- Use faster shutter speed (âĨ1/1000s)
- Lower flight altitude
- Use higher resolution camera
- Ensure camera focus is correct
Issue: Coordinate Offsetâ
Possible Causes:
- Incorrect coordinate system settings
- Poor GPS accuracy
- No control points used
Solution:
- Check coordinate system configuration:
{
"coordinate_system": {
"type": 2,
"label": "WGS 84",
"epsg_code": 4326
}
}
- Add control points:
{
"gcp_path": "gcps.txt",
"gcp_coor_sys": {
"type": 3,
"epsg_code": 32650 // Ensure consistency with actual
}
}
đ ī¸ Advanced Diagnosticsâ
View Detailed Logsâ
Log file location: working_dir/log/log.txt
Find key information:
# View errors
grep -i "error" log.txt
# View warnings
grep -i "warning" log.txt
# View progress
grep "PROGRESS" log.txt
Performance Analysisâ
Find performance metrics in logs:
[TIMING]- Time consumption for each stage[MEMORY]- Memory usage[GPU]- GPU utilization
Intermediate Results Checkâ
Check intermediate results to locate issues:
- AT results:
working_dir/AT/mvs.xml - ROI range:
working_dir/milestones/roi.json - Quality report:
working_dir/report/report.json
đ Getting Helpâ
If the above solutions cannot solve your problem:
-
Collect diagnostic information:
- Output from running
task_json_check - Complete
log.txtfile - Configuration file (with sensitive data removed)
- System information (hardware configuration)
- Output from running
-
Submit issue:
- GitHub Issues: [Project Repository]
- Technical support email: support@mipmap.com
- Include the above diagnostic information
-
Check for updates:
- Check if there's a new version
- Review version changelog
- Follow known issues list
Continuously updated. If you encounter unlisted issues, please contact technical support.