FAQ === This page lists common questions and issues when using CONOPS. Models (MAMOTH and DVI) ----------------------- What is the difference between MAMOTH and DVI? ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ * **MAMOTH** provides mosquito abundance indicators (entomological perspective). * **DVI** provides mosquito-borne disease risk indicators (epidemiological perspective). Use **MAMOTH** when you want to understand mosquito pressure. Use **DVI** when you want an early-warning signal about disease risk. Can I run both models for the same area and time period? ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Yes. A common workflow is to run **MAMOTH** and **DVI** for the same AOI and time period and compare outputs. This helps distinguish mosquito presence from disease-risk patterns. Which model should I start with? ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ * Start with **DVI** for public-health early warning and risk communication. * Start with **MAMOTH** for entomology-focused monitoring and environmental suitability analysis. Explainability (XAI) -------------------- What is the XAI feature? ^^^^^^^^^^^^^^^^^^^^^^^^ XAI (Explainable AI) provides additional information that helps explain *why* a result looks the way it does. Depending on the workflow, XAI may provide explanation attributes alongside results (e.g., main drivers, feature importance, or quality/confidence indicators). Where can I see XAI information? ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Open a **Completed** order → go to **Results**. If XAI is available for your run, you will see extra layers/fields/attributes related to explanation (e.g., “drivers”, “importance”, “explanation”, “confidence/quality”, or similar labels). Why don’t I see XAI for my order? ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Common reasons: * XAI is not available for the selected model/output in the current release. * The selected configuration does not generate explanation products. * You are viewing a simplified result view. If you expect XAI but do not see it, contact support and include the order identifier. How should I use XAI? ^^^^^^^^^^^^^^^^^^^^^ Recommended practice: * Use XAI to sanity-check whether the dominant drivers make sense for the selected AOI and period. * Compare the same AOI across months to see whether explanations evolve consistently. * If the service provides a confidence/quality indicator, treat low-confidence outputs cautiously. Data availability and archive ----------------------------- Can I run orders for the past (archive)? ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Yes. CONOPS supports processing historical periods within the supported archive window. * Supported archive window: **up to 1 year before the current date**. (**EDIT IF NEEDED**) If you request older dates, the UI may prevent selection or the order may fail due to archive limitations or input data availability. Why can’t I select older dates than 1 year? ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This is usually due to platform/service constraints such as: * archive/retention policy for inputs available to the service * operational constraints (resource limits for historical reprocessing) * completeness/availability of required input data for the requested period If you have a justified need for older periods, contact support and provide AOI + dates. Orders and execution -------------------- My order is stuck in "Queued" ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This typically means compute resources are busy. Try: * Wait and refresh the Orders/Jobs view. * Submit a smaller request (smaller AOI or shorter time period) if possible. * If it persists, contact support with the order identifier. My order is stuck in "Running" ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Longer runtimes can happen for larger AOIs or heavy time periods. Try: * Refresh and check whether the status changes. * If the UI provides messages/logs, review them. * If it remains Running unusually long, contact support with the order identifier. My order failed ^^^^^^^^^^^^^^^ Common causes include: * no data coverage for the selected AOI and time period * temporary service or platform disruption * unsupported input combination (e.g., AOI too large) What to do: 1. Open order details and read the error message (if available). 2. Retry with a different month/time period or a smaller AOI. 3. If it fails again, contact support and include: * order identifier * AOI and time period * selected model (MAMOTH/DVI) * screenshot of the error (if visible) Results and interpretation -------------------------- I see empty results or very limited coverage ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This can occur when: * EO inputs are limited (clouds, missing scenes, seasonal gaps) * the selected period does not have sufficient inputs for the workflow Try: * Choose a different month within the mosquito season. * Reduce the AOI. * Re-run with default options. Values look unrealistic (too high/too low) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ First verify: * AOI and time period are correct. * You are viewing the intended model and indicator. Then: * Compare with a neighboring month/region. * Check XAI/quality fields if available. * See :doc:`results` for interpretation guidance and limitations. Exporting (CSV and GeoJSON) --------------------------- What formats can I export? ^^^^^^^^^^^^^^^^^^^^^^^^^^ CONOPS exports results as: * **CSV** for tabular analysis * **GeoJSON** for mapping (geometries + attributes) See :doc:`export`. What is the difference between CSV and GeoJSON? ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ * Use **CSV** for Excel, reporting, statistics, and data science workflows. * Use **GeoJSON** for GIS/web maps where geometry is needed. Does export include XAI fields? ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ If XAI is generated for your workflow, it may appear: * as additional columns in the **CSV**, and/or * as additional properties in the **GeoJSON** features. If you do not see XAI-related fields, XAI may not be available for that order/model/version. How do I open the GeoJSON? ^^^^^^^^^^^^^^^^^^^^^^^^^^ You can open GeoJSON in QGIS: * Layer → Add Layer → Add Vector Layer → select the ``.geojson`` file See :doc:`export`. Access and login ---------------- I cannot access CONOPS / I get "Access denied" ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Access is managed through DestinE IAM and your organization’s roles. Try: * Sign out and sign in again. * Confirm you are using the correct DestinE account. * If the issue persists, contact your Client Administrator or DestinE support.