> ## Documentation Index
> Fetch the complete documentation index at: https://docs-v2.ard.co/llms.txt
> Use this file to discover all available pages before exploring further.

# MAMS Overview

> Model Archive Management System for archiving ModMS NetCDF data

MAMS (Model Archive Management System) is an archiver system for ModMS NetCDF data. It provides long-term storage and query capabilities for archived model data across distributed servers.

## Overview

* **Purpose**: Archive ModMS NetCDF data to distributed storage servers
* **Main Server**: `mams.devops.arabiaweather.com` (148.251.6.197)
* **Archive Servers**: Multiple archive servers (e.g., `138.201.49.117` - Mams.04)
* **Code**: Uses the same codebase as the ModMS server, providing identical query capabilities
* **Registry**: Uses `registry.json` to track data locations and date ranges
* **Deployment**: Docker Swarm stacks with multiple services

## Access

**Web Interface:** [http://mams.devops.arabiaweather.com:8081/web/](http://mams.devops.arabiaweather.com:8081/web/)

**Credentials:**

* **Username:** `modms`
* **Password:** `CLandSky`

## System Components

<Columns>
  <Column>
    **ModMS Service**

    Main API service providing query capabilities (main server only)
  </Column>

  <Column>
    **Connector Service**

    Enables distributed queries across archive servers
  </Column>

  <Column>
    **Nginx Service**

    Serves archived files and registry metadata via HTTP
  </Column>

  <Column>
    **Registry System**

    Tracks data locations across distributed servers
  </Column>
</Columns>

## Quick Links

* [Deployment](/data-ai/modms/mams/deployment) - Docker Swarm deployment configuration
* [Connector](/data-ai/modms/mams/connector) - Connector service for distributed queries
* [Registry](/data-ai/modms/mams/registry) - Registry system and archive process
* [Nginx](/data-ai/modms/mams/nginx) - Nginx service for file serving
* [API Examples](/data-ai/modms/mams/api-examples) - Example requests and workflows

## Query Capabilities

Since MAMS uses the same code as the ModMS server, it provides identical query capabilities:

<Columns>
  <Column>
    **Spatial Queries**

    Geographic region filtering
  </Column>

  <Column>
    **Temporal Queries**

    Time range filtering
  </Column>

  <Column>
    **Variable Queries**

    Filter by specific model variables
  </Column>

  <Column>
    **Mathematical Expressions**

    Aggregations and calculations
  </Column>
</Columns>

The MAMS API supports the same query syntax as the main ModMS server. See the [ModMS Query Guide](/data-ai/modms/querying) for query details.

<Warning>
  **Important:** When specifying model runs in MAMS queries, you must use timestamp format (`MODEL@timestamp`) instead of model-run format (`MODEL@model-run`).

  * **ModMS**: `GFS@2218.ISO200HPA.UGRD` (model-run format) or `GFS@1766577600.ISO200HPA.UGRD` (timestamp format)
  * **MAMS**: `GFS@1766577600.ISO200HPA.UGRD` (timestamp format only)
</Warning>

## Query Routing

When a query comes in to the main MAMS server:

1. The ModMS service checks the `registry.json` file
2. It determines which server has the requested model and date range
3. If data is on the main server, it serves it directly
4. If data is on an archive server, it connects to that server's connector (port 8082)
5. The connector serves the data and returns it to the main server
6. The main server returns the results to the client

<Info>
  This routing is transparent to clients - they always query the main server, which handles the complexity of distributed data access.
</Info>

## Related Documentation

* [ModMS Overview](/data-ai/modms) - Main ModMS system documentation
* [ModMS Getting Started](/data-ai/modms/getting-started) - Setup and development guide
* [ModMS Architecture](/data-ai/modms/architecture) - System architecture and components