Skip to main content
Skip table of contents

File Organization

Overview

This section provides a brief overview of an Aechelon Image Generator file structure.  The structure is designed to be modular so databases or software versions can be added or removed easily.  The structure also contains all customer editable files in one location for easy access or review.  It is recommended that the file structure outlined below and delivered with the system be followed to ensure proper operation of the image generator.  Additionally, all relevant files (E:\CM) should be maintained within our CM system (Perforce) and tracked appropriately.

Custom Configuration Files

All custom configuration files are in E:\CM\data\custom. These are the files the user can edit to configure software, databases, and model settings within the image generator unique to their configuration.

  • IG_CONFIG/<configuration> - IG configuration directory that includes serval config files which define a unique channel configuration. Some customers may have multiple configurations, and the AECHELON_DEVICE_CFG environment variable points to the <configuration> directory that is currently active.

    • cluster.cfg – Contains all basic channel definitions for the entire system.  Resolution, channel type, FOV, orientation are some of parameters defined here.  Any parameters can also be overridden in the individual channel type overrides below.

    • igconfig.ccfg – A list of all channels that is loaded by the start script run through aeAdmin.  The start script will parse this file and load each channel defined on the specified computer along with their override file.

    • override_system_FRONTEND.cfg

    • override_system_PAGER.cfg

    • override_system_ISECT.cfg

    • override_system_DISTRIBUTOR.cfg

    • override_render_<CHANNEL>.cfg

    • displayConfiguration_<COMPUTER>.xml

  • pc-nova.cfg – a global override file typically referenced by the <database>.cfg file.  A place to put settings used by all channels.

  • cigi/ovrd_host_cigi.cfg – the main CIGI override file parsed by nova.exe.  This file references config_host_if_cigi.cfg used by the CIGI dll.

  • cigi/config_host_if_cigi.cfg – the configuration file ready by the CIGI dll and our validator.  This file includes the CIGI connection information for the system.

  • standalone/ovrd_host_standalone_spy.cfg – the configuration file used by Nova when in standalone mode.  This file is equivalent to ovrd_host_cigi.cfg and has some of the same tokens.

  • standalone/spy.cfg – the configuration file used by our standalone interface to setup the Spy GUI, validator, etc. This is equivalent to config_host_if_cigi.cfg and has some of the same tokens.

  • config_tgts*.cfg – the moving models used by the system.  This is typically set in a global override file pc-nova.cfg or override_<database>.cfg

  • config_tgts_destroy.cfg – this is the model file used for destroyed states.  When the user switches to the destroyed state, nova switches out the model for the one defined here.  Most of the moving models have a destroyed state, but more generic ones can be defined if needed.

  • override_<database>.cfg – used to override database specific settings

  • fx_overrides.cfg – overrides any system FX configuration parameters.  These parameters are in E:\CM\software\<version>\data\DB\DB_SYSTEM\DB_SYS_DATA\*\*.fx

Software

Nova software is located on the system under E:\CM\software.  Underneath the software folder one or more version folders can exist which represent independent software versions.  Each folder should contain a full software release or release candidate.

The software version in use is controlled by an environment variable on the system called AECHELON_SOFTWARE_DIR.  The user can switch between runtimes by stopping and closing all software, changing the environment variable, and restarting the software.  This is useful for regression testing and comparison between software versions.

 

Database

The Visual database is made up of two main parts: the clipmaps and the overlay configuration files.  The clipmaps are typically stored on a RAID or NAS.  If the clipmaps are local on the system, they are stored at E:\CLIPMAPS.  All folders should be underneath a version folder.  The clipmaps are made up of several layers of the database.  This includes the terrain texture, terrain elevation, terrain material, 3D geotypical and geospecific features.

The database overlay folder comprises all the configuration files that tie the database together.  All database references and supporting files are self-contained within this folder.  Database overlay folders are located here:  E:\CM\data\DB_OVERLAY

  • <database>.cfg – this is the main database file referenced when starting nova.  All database files are referenced from this file including the custom/pc-nova.cfg and custom/override_<database>.cfg where the user can override any database specific files.

 

The <database>.cfg file also references a db_<database>.cfg file.  This db_<database>.cfg file will reference the rest of the database files and settings.

Anything needing to be changed in the database settings should be added to custom/override_<database>.cfg since that is the last database file parsed.

 

Models

Moving models, including humanoid characters are on the system in the following locations.  They are broken down into several categories such as CIVILIAN, MILITARY, AIRCRAFT, SHIP, etc.

E:\CM\data\COMMON\RELEASE\V1\DB\

E:\CM\data\DB\DB_MOVING_MODELS

Models all have common articulations and lights as defined by .csv files located at DB_MOVING_MODELS\CONTROLS_DEFINITIONS\

 

ANALOG_CONTROLS_DEFINITIONS defines all available moving model articulations broken down by type.  Not all models of a particular type will have those articulations available, but they will all use the same values.

Similarly, LIGHT_GROUPS_CONTROLS_DEFINTIONS.csv defines the standard light group definitions per model type.  Not all models will have all available lights and some models may have additional unique lights not defined in this .csv file.

 

Tools

Various tools and scripts can be found under here:

E:\CM\tools

 

Licenses

Licenses can be found under E:\CM\licenses.  The license directory is controlled by an environment variable AECHELON_LICENSE_DIR

 

Logging

 pC-Nova logs several different files typically to the C:\pc-nova folder on each computer it runs on.  In there the user will find the following types of log files:

Parsed Tokens

Typically found on the system in the C:\pc-nova\ folder, the parsed_tokens_<CHANNEL_NAME>.cfg file will describe all of the system level tokens that have been found and parsed.  It will show the final value for a particular token that the system is using.

Parsed FX Tokens

Typically found on the system in the C:\pc-nova\ folder, the parsed_FX_tokens_<CHANNEL_NAME>.cfg file will describe all of the fx file tokens that have been found and parsed.  It will show the final value for a particular token that the system is using.  These fx files come from the DB_SYSTEM\DB_SYS_DATA folder in software as well as the fx_override file.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.

Contact Support Close