FAQ
Frequently Asked Questions
Can I process images from cameras that are not MAPIR brand with Chloros?
No, Chloros only supports processing MAPIR camera images. Please see the list of supported camera models for more information. We do offer processing of other cameras on MAPIR Cloud, see full list here.
Can I calibrate my images for reflectance without a calibration target?
No. Without an image of the calibration target captured around when the non target images are captured you will not be able to relate the image's pixel values to a known reflectance percent. If you also do not include the log from a MAPIR light sensor then the ambient light spectrum will not be measured, and the reflectance results will not be accurate.
Can I edit my images prior to processing in Chloros?
No. Chloros assumes the input data has not been modified. Do not change the file names.
Can I set my MAPIR Survey3 cameras to auto exposure and process the images in Chloros?
No. Survey3 image datasets must have a fixed/locked exposure, so no auto shutter speed or auto ISO. All images of the same camera model must have identical shutter speed and ISO (exposure).
Can Chloros process or analyze orthomosaic images?
No. Only individual MAPIR camera images are supported, not stitched images like an orthomosaic map.
How can I speed up the target detection step of Chloros?
In the file browser table pre-selecting the target images in the right column will tell Chloros to only look in those images for calibration targets, greatly speeding up the processing.
If I will upload my images to MAPIR Cloud should I process in Chloros prior to uploading?
If you plan to upload to our online processing platform MAPIR Cloud do not edit the images prior to uploading. Cloud will perform all the same processing and more.
Will MAPIR ever support X feature? I really wish MAPIR offered X.
We are always interested in receiving feedback on our products. If you find an issue with our products, or have a suggestion on how we can improve our products please CONTACT US to share your thoughts. Most of our R&D is guided by listening to our customer's biggest needs.
Is Chloros available for Linux?
Yes! Chloros 1.1.0 supports Linux amd64 (x86_64) and arm64 (NVIDIA Jetson JetPack 6) via .deb packages. The CLI and Python SDK are fully supported on Linux. There is no GUI for Linux — all interaction is via the CLI or Python SDK. See Linux Overview for details.
Can I run Chloros on NVIDIA Jetson?
Yes! Chloros 1.1.0 supports NVIDIA Jetson platforms including Jetson Nano, Orin Nano, Orin NX, and AGX Orin running JetPack 6. Chloros automatically detects your Jetson model and optimizes its processing strategy. See the NVIDIA Jetson Guide for setup and deployment instructions.
Does Chloros automatically optimize for my hardware?
Yes! Chloros 1.1.0 includes Dynamic Compute Adaptation that auto-detects your CPU, GPU, RAM, and (on Jetson) thermal sensors. It then selects the optimal processing strategy — from GPU_PARALLEL on high-memory systems to GPU_SINGLE on constrained devices to CPU_PARALLEL on systems without an NVIDIA GPU. No manual configuration is needed.
What is the 4-thread processing pipeline?
Chloros 1.1.0 uses a 4-thread pipelined architecture for Chloros+ users: Thread 1 (Detection) loads images and detects calibration targets, Thread 2 (Calibration) computes reflectance calibration, Thread 3 (Processing) performs GPU-accelerated debayering and index calculation, and Thread 4 (Export) writes output files. Multiple images can be in different threads simultaneously for maximum throughput. See Processing Pipeline for details.
How do I run diagnostics on my Chloros installation?
Use the selftest command to run 7 system diagnostics including version check, port availability, backend startup, API connectivity, system info, denoiser models, and CUDA availability:
This is especially useful on Linux/Jetson systems to verify GPU and CUDA setup.
Last updated