> For the complete documentation index, see [llms.txt](https://help.boomerang3.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.boomerang3.com/boomerang-3-domain-administrator-manual/admin/calibration/calibration-status.md).
# Calibration status
### Not calibrated MP
An MP that was never calibrated has gray background and a red exclamation mark before its name as shown below.
There may be an icon in the “History” column if a calibration was started but not finished.
### Calibrated MP
An MP that was calibrated has white background and icons in the “PDF” and “History” columns as shown below. It also has time stamps in “Last Calibrated” and “Next Calibration” columns.
The [Approve certificate](/boomerang-3-domain-administrator-manual/admin/calibration/approve-certificate.md) icon will be shown if the cerificate is not approved.
An MP for which a certificate was uploaded manually has a time stamp in “Manual Upload Time” column.
If an MP has a certificate but it is expired, then there is a red exclamation mark before its “Next Calibration” date.
### MP during automatic calibration
If calibration is done using ICU Scandinavia service, then an MP under calibration will present its status by a modified icon.
The blue MP icon is idle MP.
The yellow turning  icon represents an MP during the calibration process.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.boomerang3.com/boomerang-3-domain-administrator-manual/admin/calibration/calibration-status.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
