> For the complete documentation index, see [llms.txt](https://gryfn.gitbook.io/gryfn-software/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gryfn.gitbook.io/gryfn-software/support/getting-started.md).

# Getting Started

## Installation

* Run GRYFN Processing Tool installer
* Choose to install for all users or single user
* Enter License Activation Code

GRYFN Processing Tool will automatically check for updates. If any updates are available, you will be prompted to install these updates and restart the software.

## Setup

* After installation, navigate to the Settings tab. There are a few necessary settings prior to processing, and a few other settings to save you clicks in the future.

### Necessary Settings

* If you are processing VNIR or SWIR data from a Headwall NanoHP or Headwall SWIR640, in order to convert raw data to radiance automatically, set the **Default Radiometric Calibration Location** to the directory of your Headwall radioCal files
* If processing SBG GNSS-INS data, set the installation directory of Qinertia CLI
  * C:\Program Files\SBG Systems\Qinertia\bin\qinertia-cli.exe
  * You also need to Login to SBG
* If processing Applanix GNSS-INS data, set the installation directory of POSPac Batch or enter your license credentials for POSPac Cloud licensing
  * C:\Program Files\Applanix\POSPac UAV #.#\PospacBatch.exe
  * *If users wish to process through POSPac's desktop GUI manually, see* [Settings](/gryfn-software/user-manual/settings.md#pospac-uav-desktop) for setting up the GRYFN export format

### Optional Settings

| SETTING                                  | DESCRIPTION                                                                                                   |
| ---------------------------------------- | ------------------------------------------------------------------------------------------------------------- |
| Default GRAW Output Location             | Path to default output location for GRAW bundles                                                              |
| Default GPRO Output Location             | Path to default output location for GPRO folders                                                              |
| Default Boresight Calibration Location   | Path to system boresight calibration file                                                                     |
| Default Radiometric Calibration Location | Path to parent folder containing radiometric calibration data for any and all Headwall hyperspectral sensors. |
| Default Extent Location                  | Path to geoprocessing extent files                                                                            |
| Default Reflectance Target Location      | Path to reflectance panel DHR data files                                                                      |

{% hint style="info" %}
**Radiometric Calibration Location** is required for native raw -> radiance conversion of supported Headwall hyperspectral sensors.
{% endhint %}

### Pilot Information

Users can set some information for pilots in your organization for metadata logging purposes when bundling a GRAW. This can also be helpful to keep track of when pilots need to re-certify their remote pilot license.


---

# 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 dynamically by asking a question.

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

```
GET https://gryfn.gitbook.io/gryfn-software/support/getting-started.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.