# My Models

<figure><img src="/files/udly0qrZib5JbT5oYkdh" alt=""><figcaption><p>Snippet of the Model Management Page</p></figcaption></figure>

The **“My Models”** page serves as an informative hub displaying an overview of all your models.&#x20;

Users can conveniently access and review all models submitted. For each model, a set of quick-look data points are shown to help prioritize model and actions of priority.\
\
The columns for each model are explained below:

* **Submission Number**: to the left of the model name in square parenthesis, e.g.  '\[3]'
  * Clicking the expander icon (▸) to the left opens a panel underneath to show all previous submissions for the same model
  * Users can navigate to any prior submission by clicking 'View' and continue working from that version too
  * The version of user's model held on SURGE may not be tied to the latest version on their own development GitHub/BitBucket repository\
    \
    the latest submission version number, date of status update, current status and version history of each model. Additionally, you can gather information regarding the visibility and activation status of your models.
* **Model Name**: a unique value across the user's SURGE account. No two models can have the same name.
  * Only the latest submission of the model is associated with this model number
  * Prior submissions are referred to using an internal model ID (the latest version has one too, but is not necessary as it is the primary version of record)
* **Date**: this is the date of the latest status change for the given model
* **Status**: each model can have ONE of the following 4 'phase' statuses with their color determined by the nature of the latest operation's outcome:

| Submission                                     | Validation                                     | Testing                                        | H/W Testing                                    |
| ---------------------------------------------- | ---------------------------------------------- | ---------------------------------------------- | ---------------------------------------------- |
| <mark style="color:yellow;">In Progress</mark> | <mark style="color:yellow;">In Progress</mark> | <mark style="color:yellow;">In Progress</mark> | <mark style="color:yellow;">In Progress</mark> |
| <mark style="color:green;">Successful</mark>   | <mark style="color:green;">Successful</mark>   | <mark style="color:green;">Successful</mark>   | <mark style="color:green;">Successful</mark>   |
| <mark style="color:red;">Failed</mark>         | <mark style="color:red;">Failed</mark>         | <mark style="color:red;">Failed</mark>         | <mark style="color:red;">Failed</mark>         |

{% hint style="info" %}
***Note:** These statuses are tracked under Notifications as well, and are sent out on the registered email whenever a status change occurs.*
{% endhint %}

* **Action**: Based on the current status of a model, action prompts will be shown in this column. For example, a 'Failed' status will prompt a 'Resubmit' action.
* **Activation status**: This displays the operational state of the model, as per
  * Draft: Submission is incomplete and 'Saved' for completion. These submissions will not be processed.
  * Activated: Latest submission of the model is 'Active' for the current and upcoming phases all the way to satellite deployment.
  * Not Activated: Latest submission of the model has been marked as unavailable for the current and all upcoming phases through till satellite deployment. Note: User can deactivate a model even after deployment.
* **Visibility**: This field tell whether the model (not just the latest submission) is visible to any public-use list of models on SURGE. Currently, all models are 'Private' - and no public-facing list exists.

By clicking on **"View"** from the list, user can navigate to the corresponding model version's dedicated tracker.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://skyserve.gitbook.io/skyserve-docs/my-models.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.