# 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

Toggling dark mode will instantly convert the appearance of the software to/from a dark gray theme or GRYFN gold.

#### Invert Target Select Scrolling

Toggling the "Invert Target Select Scroll Direction" slider will reverse the current direction of image scrolling in the Draw Target Bounds window.

#### Number of Threads to Utilize

A sliding bar to control the number of CPU threads being utilized. Utilizing more threads will decrease processing time while increased demand on the system.

### 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

This defines the default path given to newly bundled GRAWs.

#### Default GPRO Output Location

This defines the default path given to newly created GPROs.

#### Default Boresight Calibration Location

This defines the default path when prompted to load system calibration files.

#### Default Radiometric Calibration Location

This defines the path to recursively search for radiometric calibration files when processing Headwall nHP data. This path will be searched in addition to the flight's raw nHP data location.

#### Default Extent Location

This defines the default path when prompted to load extent files.

#### Default Reflectance Target Location

This defines the default path when prompted to load reflectance target files.

### Applanix Defaults

#### POSPac Batch Runner Executable

This setting defines the path to the POSPac Batch executable. The default POSPac Batch install directory is:

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

Additionally, GRYFN's custom trajectory export format file, found in

```
C:\Users\*User*\AppData\Local\Programs\GRYFN Processing Tool\pipeline_runner-v1.8.3\assets\GRYFN v0.3.xsd
```

&#x20;must be placed in the following directory:

```
  C:\ProgramData\Applanix\User Format Profiles
```

{% hint style="info" %}
For Users with POSPac Cloud licenses, there is no need to download POSPac UAV or install custom export format files. To use POSPac Cloud, open Settings in GRYFN Processing Tool, toggle POSPac Cloud, and enter your license credentials.
{% endhint %}

### SBG Defaults

#### Qinertia CLI Location

This setting 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:

```
  C:\Users\*User*\AppData\Local\Programs\GRYFN Processing Tool\pipeline_runner-v#.#.#\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 Optional Parameters.

## Product Licensing

Users may enter and activate their product key on the Product Licensing page. Expired licenses are genrally valid to execute processing pipelines, but will not be entitled to software updates. Please contact [support@gryfn.io](mailto: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
    ```
