README.md

In AstroPathJHU/mIFTO: mIFTO: Multiplex Immunoflourescence Titration Optimization

Multiplex Immunoflouresence Titration Optimization (mIFTO) R Package

v.2.00.202

Section 1: Summary

This R package was developed to help organize and quantify the inForm Cell Analysis output for pixel-by-pixel, cell-by-cell, and tissue segmentation data. The primary goal of this package is to aid in the assessment and determination of optimum staining conditions for multiplex immunofluorescence titrations on Akoya’s scanning and staining platform. There are two primary functions of mIFTO; FOP() and mIFTOapp(). FOP() was designed to measure the ‘fractions of positivity’ for individual conditions. Then, with a unique identifier, the grouped conditions are exported together into a csv output file with the average fraction of positivity and a csv output file with the individual fractions of positivity per slide. The function uses the inForm output tables (IF or IHC) for cell segmented, colocalization data, or tissue segmented data as input. The other primary function, mIFTOapp(), was developed to aid in determining an optimum condition for a series of reagent titrations. The output includes pixel histograms of intensity, t-statistics, signal-to-noise ratios, fractions of positivity, and boxplots of expression profiles.

Section 2: Getting Started

Section 2.1: Initial Package Install

Open an Rstudio session to get started. Next, install the package from github using the following commands:

detach("package:mIFTO", unload=TRUE)

It is helpful to run these lines before performing the installation incase the libraries are currently in use.

If it says "Error in detach("package:mIFTO", unload = TRUE) : invalid 'name' argument" this is ok.

install.packages("devtools")

The installation of ‘devtools’ is usually the most interactive and takes the longest. This is a provided R package which is used for external programmers to develop R packages. During the devtools installation command (command 1 above), R may require some user input, examples of this include:

1. R may indicate that some packages should be updated. The user can either indicate to update all, some or none of the packages. It is usually best to select the update all option.
2. A dialog box may also open asking the user if the package should ‘be compiled from source’, it is usually best to answer ‘yes’ to this
3. A dialog box may open telling the user that a package is in use and that the R session must be restarted to continue installation of a package. It is usually best to allow R to do so. Note that is may take a few moments for R to reinitialize after it restarts, this is normal.

Errors are common in this step, usually when updating packages. If a package fails to update properly and crashes the installation process an error message is usually output beginning with: “Error: package ‘failed_package_name’ failed to install’. Installing the package separately may be necessary. Enter install.packages(‘failed_package_name’); replacing ‘failed_package_name’ with the name of the failed package.

For more advanced users of R, it may be easier to specify additional options during a package installation. For example, when installing ‘devtools’ the following options can be specified:

install.packages(‘devtools’, ask = FALSE, quiet = TRUE, verbose = FALSE)

This command will install ‘devtools’ without asking the user if it is okay to updated or compile a package and will carry out the procedures automatically. The command will also significantly reduce the output to the console.

library(devtools)

Warning messages like these are fine. Let me know if something else comes up.       "1: package ‘devtools’ was built under R version 4.1.3"       "2: package ‘usethis’ was built under R version 4.1.3"

install_github("AstroPathJHU/mIFTO")

• A list should pop up asking what you want to update. Enter 1 to update all.
• If it looks like nothing is happening for a while, check the taskbar at the bottom of the screen. There might be a window that popped up asking the user if the package should ‘be compiled from source’. Click “OK”
• There may be warnings that certain packages couldn't be updated. This is fine. Make sure this shows - building 'mIFTO_2.00.196.tar.gz' after the packages finish installing. The v.2.0... number at the top of this page is the latest.
• If you see the following, that means it didn't install. Let me know.       Execution halted       ERROR: lazy loading failed for package 'mIFTO'        removing 'C:/Users/ /Documents/R/win-library/4.1/mIFTO'        restoring previous 'C:/Users//Documents/R/win-library/4.1/mIFTO'
• A lot of times there are problems with updating packages in R. If you get something like 'vctrs' 0.5.1 is already loaded, but >= 0.6.0 is required, try the following:       run install.packages("vctrs").       If it says Problem copying ... vctrs package location ... Permission denied then you have to go into the location of your libraries and delete the vctrs folder.       You can usually tell where the folder is from the outputs in RStudio. This user's libraries happen to be at C:\Users\cnajera2\Documents\R\R-4.1.1\library

      Then install.packages("vctrs") should work and you can resume updating mIFTO.       This applies to any other package, not just vctrs. rlang is another one that does this a lot.       If it doesn’t let you delete the folders, email [e-mail]

You should see something that says * DONE (mIFTO) meaning that it installed correctly.

Note: When the package begins to install a number of messages will appear in the console indicating the status of different events, especially during the initial install or just after R has been updated, this is normal. Some of the messages may be in red, this does not indicate an error. If there is an error during installation, usually the output message to the console will start with “Error:” or “Warning:”, then describe the corresponding error.

Section 2.2: Running Package

The library(devtools) call will only be needed the first time the mIFTO package is used, unless additional updates to the package have been posted.

Once installed once for a user profile, the user can run the apps one of two ways:

1. load a library into the current ‘workspace’ by using library(current_package) replacing ‘current_package’ for whichever library is needed. To load the mIFTO R package type: library(mIFTO). Afterward call the apps using FOP() and mIFTOapp().
2. Explicitly call the package and the functions simultaneously without loading the package into memory. In this case use the syntax package_name::function_name. For the main apps described in this document use mIFTO::FOP() and mIFTO::mIFTOapp().

Code performance is reliant on the local systems connection to the images as well as the computational resources of the local system. Since the image data for these images can be very large, it is advisable that either the images are kept local to the machine the software is run on or that they can be accessed by a high speed network connection.

Section 2.3: Updating the Package

Before attempting to update the package, run the following line and compare the version output with the version number at the top of this Readme. If they are the same, mIFTO does not need ot be updated.

packageVersion("mIFTO")

When an update for the package is available on github, it is advisable that, if the user already had an R session open with an old version running, the user clear their R history, completely close their current R session or window, and open a new session.

To clear the R history, go to the ‘history’ tab on the top right of the R user interface and select the broom icon, as shown below:

After the new R session is open, the advisable steps for updating the mIFTO R package would be the same as a new install:

install.packages(‘devtools’)
library(devtools)
install_github("AstroPathJHU/mIFTO")

For additional details see section 2.1. If the most up to date package is already installed under the current user profile the following message may appear instead:

A second installation may corrupt the package, in this case the following message will appear:

Once ‘OK’ is clicked, the following lines will be printed into the console (with a local R library path in place instead of bgreen42):

To fix this error, close the current R sessions completely, open a new session, and reinstall the package.

Section 3: Slide and Folder Naming

Section 3.1: Slide Names

For mIFTO to process the data correctly, the files and folders must follow the proper naming conventions and the structures of the folders need to be correct. A full naming protocol for the scans can be found here.

Section 3.2: Folder Names

For mIFTO, folders should also follow a specific naming convention. - IF - [PrimaryAntibody]_1to[ConcentrationofPrimaryAntibody]_[PolymerUsed]_Opal[OpalUsed]_1to[OpalConcentrationUsed] (e.g. 'PD1_1to150_PV50_Opal650_1to50') - IHC - '[Antibody]_IHC' (e.g. 'PD1_IHC')

For FOP, the folder names don't matter. What is important is grouping same titrations together such that the cases that have the same variables are in the same folder. This should result in each folder having one of each tissue type.

Section 4: FOP

Section 4.1: Description

This function is used to measure the fraction of positivity across a subset of images for a uniquely named slide. The function is designed to count positivity for cell-by-cell, pixel-by-pixel, or tissue segmented data exported from inForm.

Section 4.2: Extracting and Exporting Data from inForm

a. For cell-by-cell data: - use the 'Phenotyping' module of inform and export the 'RBG', 'Segmentation Maps (multi-image TIFF)' and 'Cell Segmentation Data'. Name the positive phenotype with the same name (case sensitive) as the input for ‘Primary Antibody’ in the GUI (see below). Name the negative phenotype 'Other'.

b. For pixel-by-pixel: - use the 'cClocalization' module of inForm to export the 'RBG', 'Component Images (multi-image TIFF)' and 'Colocalization Data'. Do not name the opals in the ‘prepare’ tab of inForm.

c. For tissue segmentation: - use the 'Segment Tissue' module in inForm to export the 'RBG', 'Segmentation Maps (multi-image TIFF)' and 'Tissue Segmentation Data'. Name the categories ‘Tumor’ and ‘Non Tumor’ in inForm.

For all exports, do not name the opals in the ‘prepare’ tab of inForm, the code will not be able to find the correct columns. Note that the code will generate statistics for all slides in the selected folder (see below for more details in step 5).

Section 4.3: GUI Input and Running

1. Open R Studio and install the package (see ‘Section 2: Getting Started’ for installation instructions)
2. Type mIFTO::FOP() & ENTER
3. The app will open in a web browser with the following inputs
4. Slide Identifier:
   • This is where the specimen numbers or other slide distinctions are located
   • Do not add ‘–‘ or spaces in names
   • Place a comma between names
   • E.g.: Melanoma1,Melanoma2
   • Primary Antibody:
   • This is the antibody the analysis is running for
   • E.g.: CD8
   • Other condition delineation:
   • Anything else in the name that could separate different conditions in excel spreadsheet output
   • E.g.: (V1, IHC, IF, 1to100, 1to200)
   • E.g.: for GranB put IF in the ‘other condition delineation’ field for the IF and IHC in the ‘other condition delineation’ field for the IHC you will would get the following:
   • Primary Opal
   • This is the Opal the primary AB is in
   • E.g.: 540
   • Is this IHC?
     • Blank = no
     • Check = yes
   • Is this MoTiF?
     • Blank = no
     • Check = yes
   • What kind of positivity measure?
     • Drop down box with the following options
     • PPC pixels
     • Cells
     • Tissue
5. Click ‘Run FOP’
6. A windows explorer will ask you to point it to the directory with the data inside
7. The code will generate statistics for all slides in the selected folder.
8. The program will run for this condition then ask if there is another condition
9. Only say yes if the Slide Descriptors are the exact same
10. Yes:
11. A new GUI will open asking for the new:
    • Primary Antibody
    • Other condition delineation
    • Primary Opal
    • IHC?
    • MoTiF?
12. Click Run
13. A windows explorer will ask you to point it to the directory with the data inside
14. The program will run and ask if there is more data
15. No:
16. A window explorer will open for the output directory
17. Two files called + PPC Pixels_raw_data_ordered and + PPC Pixels will be located in the output directory

Once finished running the app will idle in the background and continue to wait for input. To stop the UI, either close out the web browser or click the red ‘stop’ sign button just above the console window in RStudio and close the web browser.

Section 4.4: Common things to check after running into errors

1. Not putting conditions into separate folders
2. Misspelling input to charts
3. Not labeling Opals – AB pairs in inform output
4. Leaving out Slide Descriptors for slides in the data folder when writing into input box
5. Typing Slide Descriptor names in wrong
6. Sometimes the folder browsing window opens behind the Rstudio session.
7. The UI will not respond well to multiple clicks
8. You may need to adjust the browser window sizing on your machine to get everything to line up well
9. In output, if some columns do not average
10. See 4 or 5

Section 5: mIFTOapp

Section 5.1: Description

This function is used to select optimum dilutions from a titration series. For a titration series, at least 3 cases with 10 HPFs each should be used. For best results stain at least 5 dilutions, one above and 4 below the manufactures recommended concentration.

Section 5.2: Exctracting and Exporting Data from inForm

The pixel-by-pixel analysis and cell-by-cell analyses are performed by separate modules in the app as usually one modality or the other is used to determine the optimal dilution. Once the slides have been stained and scanned, establish thresholds for pixel-by-pixel data or phenotype the data for cell-by-cell data in the respective modalities. For cell-by-cell analysis, export the cell segmented for each HPF. For pixel-by-pixel analysis export the component data images for each HPF. Dilutions\conditions can either be exported into separate or a single folder.

Section 5.3: GUI Input and Running

1. Open R Studio and install the package (see ‘Section 2: Getting Started’ for installation instructions)
2. Type mIFTO::mIFTOapp() & ENTER
3. The app will open in a web browser with the following inputs: (Note: it may be necessary to resize the window to allow all fields to line up appropriately)
4. Slide Identifier:
   • This is where the specimen numbers or other slide distinctions are entered
     • Do not add '–' or spaces in names
   • Place a comma between names
   • E.g. Melanoma1,Melanoma2
5. Primary Antibody:
   • This is the antibody the app is analyzing
   • E.g. CD8
6. Concentration:
   • Concentrations being tested
   • 100,200,400
7. Fluorophore (TSA)
   • This is the fluorophore used to detect the antibody
   • E.g. 540 OR 570
   • The code only supports the use of component tiffs with image layers unmixed from Akoya’s 7 and 9 color libraries using the following wavelengths:
   • DAPI, 480, 520, 540, 570, 620, 650, 690, 780
8. Was naming convention followed? (Was more than one dilution used in the name …)
   • Check Yes if the files are named using the naming convention described in section 4.2
9. What is being titrated
   • Primary Antibody
   • Fluorophore (TSA)
10. For Cell segmented data – NOT YET FUNCTIONING
11. For Pixel data
    • Is the data in separate folders according to dilution
    • Check = yes
    • Blank = no
    • Was an IHC thresholded with this dilution
    • Check = yes
      • add the connected pixels and threshold values to the end of their respective lists
      • This option also requires that the ‘component tiffs’ are exported from inForm for the IHC images
      • For data separated in folders by dilution, put the IHC data into a folder named ‘AntibodyX_IHC’ replacing ‘AntibodyX’ for the value in the ‘Primary Antibody’ field
    • Blank = no
    • Were thresholds different for each case
    • Check = yes
      • new fields will open for each slide identifier under the ‘connected pixels’ and ‘thresholds’ input locations
    • Blank = no
    • List the thresholds in order of increasing dilution separated by a comma
    • E.g. 12.5,13.6,14.7
    • Must be same length as number of concentrations
    • List the connected pixel values in order of increasing dilution separated by a comma
    • E.g. 12,13,14
    • Number of pixels above the threshold which must be connected for the values to be included in the positive signal, (setting can be set in inForm colocalization module and should be translated here)
    • Must be same length as number of concentrations and should be whole numbers
    • Click ‘Run Pixel-by-Pixel’
12. A windows explorer box will be generated to find a data folder and a progress bar should open in the bottom right hand corner
    • If data is in separate folders select the parent folder
    • The windows explorer may open behind the Rstudio or web browser window
13. The program will produce results in a Results.cell or Results.pixels folder for cell or pixel data respectively
14. There will be a ‘Finished’ Dialog when the software finished
15. If no more conditions need to be run, close the web page to exit and exit the mIFTOapp in R by click the red stop sign button in the RStudio console.

Section 5.4: Common things to check after running into errors

1. For most errors a dialog should open with a clear message of what went wrong.
2. If the error causes the UI windows to grey out simply close the web browser window, select the red ‘stop sign’ in the RStudio console

Then rerun the app using ‘mIFTO::mIFTOapp()’

Section 6. Credits

Created by: Benjamin Green & Charles Roberts

Edited by: Sigfredo Soto-Diaz

Based on code orginally written by Dr. Nicolas Giraldo-Castillo

Tumor Microenvironment Technology Development Center

The Johns Hopkins University Bloomberg~Kimmel Institute for Cancer Immunotherapy

Correspondence to: [e-mail]

AstroPathJHU/mIFTO documentation built on April 14, 2025, 7:22 a.m.