Skip to content

IFI Access

Gillian Petro edited this page Jan 30, 2025 · 23 revisions

*** Disclaimer ***

The In-Flight Icing (IFI) code is protected intellectual property and is not available to the public. Only approved persons will be allowed access to the repository. To inquire about access, please contact the code managers with justification for access. The code managers will evaluate the request to determine whether to approve or deny. All parties (i.e., NCAR and NOAA/GSL/EMC) must agree and give approval for access to be granted. If access is granted, new users should be trained by a code manager or appropriate point of contact in the proper access and use of the repository to ensure integrity of the intellectual property.

EMC Code manager: Sam Trahan (samuel.trahan@noaa.gov) - NOAA/GSL

NCAR Code manager: Paul Prestopnik (prestop@ucar.edu) - NCAR

How to clone IFI repository

  1. Clone the UPP repository with the recursive option

    git clone https://github.com/NOAA-EMC/UPP 
    git -c submodule."sorc/libIFI.fd".update=checkout submodule update --init --recursive
    

    * If you have previously been granted access to the IFI repository, these procedures will populate the code into the UPP/sorc/libIFI.fd directory.

  2. Restrict the IFI code

    cd UPP
    chmod -R go-rwx sorc
    

    * Please do not distribute the IFI code to the public.

How to build UPP executable for generating IFI product

There are three options:

  1. Internal build: Check out IFI code and build along with the general UPP code.

    cd UPP/tests
    ./compile_upp.sh -I
    

    You would expect the following messages from your build log:

    Building IFI inside the post.
    Enabling USE_IFI in the post.
    
  2. Internal build with libIFI test programs. In addition to the internal build (above), this instructs libIFI to compile its own test programs.

    cd UPP/tests
    ./compile_upp.sh -I -B
    

    You would expect the following messages from your build log:

    Building IFI inside the post.
    Building libIFI FIP2-lookalike and test programs.
    Enabling USE_IFI in the post.
    
  3. External build: Build with pre-installed IFI library (access for authorized users only). This is only available on Acorn, Hera, and Jet. Note: Preinstalled libraries aren't allowed on WCOSS Cactus and Dogwood for security reasons. On those machines, we must use the internal builds.

    cd UPP/tests
    ./compile_upp.sh -i
    

    You would expect the following messages from your build log:

    Linking to IFI external to the post.
    Enabling USE_IFI in the post.