> 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/user-manual/settings.md).

# Settings

The GRYFN Processing Tool "Settings" tab allows users to control general application settings, utilize python scripts, input pilot information, and activate the software license.

## General

**Enable Dark Mode** will instantly convert the appearance of the software to/from a dark gray theme or GRYFN gold.

**Invert Target Select Scrolling** will reverse the current direction of image scrolling in the Draw Target Bounds window.

**Number of Threads to Utilize** is a sliding bar to control the number of CPU threads being utilized. Utilizing more threads will decrease processing time while increasing demand on the system. When connecting to a machine via remote desktop, or running other heavy software simultaneously, it is recommended to decrease the thread count slightly.

### Default Location Settings

Modifying each of the default path locations in the Default Location Settings will alter the starting location of external browsers opened by the software when selecting files.

**Default GRAW Output Location** defines the default path given to newly bundled GRAWs.

**Default GPRO Output Location** defines the default path given to newly created GPROs.

**Default Boresight Calibration Location** defines the default path when prompted to load system calibration files.

**Default Radiometric Calibration Location** defines the path to recursively search for radiometric calibration files when bundling/processing Headwall Nano HP or SWIR data. This path will be searched in addition to the flight's raw Nano HP/SWIR data location. Settings.txt is parsed for gain mode and exposure time, then the appropriate gain mode and exposure time coefficients are chosen. The .chd file specifies a minimum and maximum exposure time, where the next file's minimum will overlap with the previous file's maximum. If the selected exposure is the exact value of this overlap region, our implementation is inclusive lower boundary, exclusive upper boundary, so the longer exposure time would be selected.

For users with multiple supported sensors, a single parent directory containing a child directory for each sensor may be supplied. This will typically be `C:\Headwall\sensorConfig` where the sensorConfig folder contains one or multiple sensor subfolders with radiometric calibration data. An example direcotry is listed below.

```
C:\Headwall\sensorConfig
    nHP-001
        12mm
            radioCal.raw
                nHP-001_12mm_f#2.5_g#_e#ms.cff
                nHP-001_12mm_f#2.5_g#_e#ms.chd
                nHP-001_12mm_f#2.5_g#_e#ms_DF.bin
                nHP-001_12mm_f#2.5_g#_e#ms_DF.hdr
    nHP-002
        ...
    uVS-001
        ...
    uVS-002
        ...
```

**Default Extent Location** defines the default path when prompted to load extent files.

**Default Reflectance Target Location** defines the default path when prompted to load reflectance target files. Users may load any number of reflectance target files from multiple locations. For users with multiple sets of reflectance panels, we recommend separating them into folders based on panel batch serial number.

```
\path\to\reflectance\panel\parent\folder\
    UF200-26001-OrgName
        UF200-26001-11.json
        UF200-26001-30.json
        UF200-26001-56.json
        UF200-26001-82.json
    UF200-26002-OrgName
        UF200-26002-20.json
        UF200-26002-45.json
    ...
```

### Applanix Defaults

To process Applanix GNSS data through GRYFN Processing Tool, see the relevant expandable section below for your POSPac installation/license type.

<details>

<summary>POSPac UAV - Desktop</summary>

**POSPac Batch Runner Executable** defines the path to the POSPac Batch executable. This path must be set for POSPac Batch with desktop licenses. The default POSPac Batch install directory is:

```
C:\Program Files\Applanix\POSPac UAV x.x\PospacBatch.exe
```

If a user wishes to manually process APX-15 data in POSPac, they will need to install GRYFN's custom export formats. The .xsd export format profile can be found in:

```
Single-User Install:
    C:\Users\*User*\AppData\Local\Programs\GRYFN Processing Tool\pipeline_runner-v1.8.3\assets\GRYFN v0.3.xsd
Global Installation:
    C:\Program Files\GRYFN Processing Tool\pipeline_runner-v1.9.0\assets\GRYFN v0.3.xsd
```

The .xsd file must be **copied** into the following directory if users wish to process APX data manually in POSPac:

<pre><code><strong>  C:\ProgramData\Applanix\User Format Profiles
</strong></code></pre>

</details>

<details>

<summary>POSPac Cloud</summary>

For Users with POSPac Cloud licenses, there is no need to download POSPac UAV or install custom export format files. To use POSPac Cloud:

1. Toggle POSPac Cloud
2. Select the Production server
3. Enter your license credentials.

</details>

### SBG Defaults

**Qinertia CLI Location** defines the path to the Qinertia CLI executable. The default Qinertia CLI install directory is:

```
  C:\Program Files\SBG Systems\Qinertia\bin\qinertia-cli.exe
```

If a user wishes to manually process SBG data in Qinertia, they will need to install GRYFN's custom export formats. To install these profiles to Qinertia GUI, open Qinertia, open File, Exports, click the Import Profiles button, then import the Export and Event profiles from the following directory:

```
For local installs:
    C:\Users\*User*\AppData\Local\Programs\GRYFN Processing Tool\pipeline_runner-v#.#.#\assets
    
For global installs:
    C:\Program Files\GRYFN Processing Tool\pipeline_runner-v1.9.1\assets
```

**SBG Settings** Login to your Qinertia account using the **Login SBG** button to enable post-processing of SBG data.

## Pilot Information

On this page, users may add pilots and information that will be available for entry in bundled GRAW datasets from the Optional Parameters page.

## Product Licensing

Users may enter and activate their product key on the Product Licensing page. Expired licenses are generally valid to execute processing pipelines, but will not be entitled to software updates. Users may release their machine from this page in order to activate the license on another machine. Please contact <support@gryfn.io> for licensing inquiries.

## Scripts

GRYFN Processing Tool supports the execution of external Python scripts using a custom gryfn-python module and correctly configured script settings.

Users can configure the script settings to search a particular directory for compatible scripts, identify the Python executable to call, and provide additional launch arguments, such as how to run a specific Anaconda environment.

The gryfn-python module must be installed for this feature to work. A wheel file for installation is available [here.](http://gofile.me/5NQoc/z17wBelcE) or, see our [gryfn-python GitHub repo](https://github.com/gryfn-io/gryfn-python).

After successful configuration and software restart, valid scripts will be displayed in the "Scripts Found" section of the Scripts settings tab. These scripts can be appended to an existing processing Job by adding the script as a task in a pipeline, or run independently using the "Run Script on GPRO" button on the New Job page. GPRO folders are an implied argument of gryfn-python scripts. Any of the dataset or processing metadata can be queried with the gryfn-python module and additional arguments can be defined for the software UI to expose.

### External Script Location

This setting defines a path for GRYFN processing tool to search for compatible Python scripts. By default, the software will search for scripts in "C:\Users\User\AppData\Local\Programs\GRYFN\scripts". An example Python script is available here- "example.py"

### Python Executable

This setting defines a path to your Python executable. For Anaconda users the path may look like "C: \Users\User\anaconda3\Scripts\conda.exe"

* **Additional Launch Arguments** may be required when using conda or other virtual environments. An example of additional launch arguments is provided below. This example runs Python in a conda environment called "gryfn-python".

  ```
  run -n gryfn-python python
  ```


---

# 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, and the optional `goal` query parameter:

```
GET https://gryfn.gitbook.io/gryfn-software/user-manual/settings.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.