preparation, pre-processing, and harmonization of data for mofa analysis

Unsupervised Analysis of Multi-Omics Data in Coronary Syndromes Using MOFA

Disease mechanisms are usually complex and governed by the interaction of several distinct molecular processes. Deciphering the complex molecular mechanisms that lead to specific diseases or govern the evolution of a disease is a task with high medical relevance as it might reveal new insights for understanding and treating diseases.
Recent technological advances enable to measure those processes on a higher resolution (e.g., on the single-cell level) and at various biological layers (e.g., DNA, mRNA, chromatin accessibility, DNA methylation, proteomics) at the same time. This leads to the increasing generation of large multidimensional biological datasets, which can be jointly analyzed to generate more insights into the underlying processes. At the same time, combining and analyzing the different data sources in a biologically meaningful way remains a challenging task1.
Different technological limits, noises, and ranges of variability between different omics pose one challenge. For example, single-cell RNA-sequencing (scRNA-seq) data is very sparse and often influenced by large technical or batch effects. Additionally, the feature space is often very large, ranging across several thousand measured genes or proteins, while sample sizes are limited. This is further complicated by complex designs, which might include several disease conditions, confounding factors, time points, and resolutions. For example, in the presented use case, different data types were available either on the single-cell or sample (bulk) level. Besides that, the data may be incomplete, and not all measurements might be available for all analyzed subjects.
Due to these challenges, different omics and included features are still often analyzed only separately2 even though performing an integrated analysis cannot only provide a complete picture of the process but biological and technical noises from one omic might also be compensated by other omics3,4. Several different methods have been proposed to perform an integrated analysis of multi-omics data, including Bayesian methods, network-based methods5,6, multimodal deep learning7, and dimensionality reduction methods via matrix factorization8,9. For the latter, the results of a large benchmarking study10 have shown the MOFA9 (multi-omic factor analysis) method to be one of the better-suited tools when data should be linked to clinical annotations.
Especially in complex settings, unsupervised matrix factorization methods are a useful approach to reduce complexity and extract shared and complementary signals from different data sources and features. By decomposing the complex space into lower-rank latent representations, the major sources of variance within the data can be quickly explored and linked to known covariates. In case the same pattern of variation is shared across multiple features (e.g., genes or proteins), this may be aggregated to a few factors while noise is reduced. Regularization can be used to increase the sparsity of model coefficients, which makes the approach well-suited in settings where the feature space is large while the number of samples is limited9.
This protocol presents a flexible analysis workflow that uses the MOFA model to showcase how to quickly explore a complex multi-omics dataset and distill the main patterns of variation that characterize this dataset. The workflow consists of three main steps. In the first step, Data pre-processing and harmonization, different strategies for data preprocessing based on different input data types (scRNA-seq, proteomics, cytokine, clinical data) are presented. The protocol elaborates on how to process the features of the different input datasets, filter out low-quality features, and normalize them to harmonize their distributions. We also show how those pre-processing decisions might affect downstream results. In the second step, the MOFA model is applied to the data, and the resulting variance decomposition can be used to evaluate the integration of the different datasets. The third step shows how to link the captured factors to covariates and uncover the molecular programs that define those factors. With the presented workflow, we were able to extract several latent factors linked to clinical covariates in a dataset of patients suffering from coronary syndromes and identify potential underlying multicellular immune programs from a previous project11. We will use this dataset here, but the protocol can easily be applied to other contexts, including other omics.
The dataset consists of samples from patients with stable chronic coronary syndromes (CCS), acute coronary syndromes (ACS), and a control group with healthy coronaries (non-CCS) (Figure 1). ACS is caused by plaque rupture in preexisting CCS, leading to an acute disruption of blood flow to the myocardium and a subsequent ischaemic injury of the heart. This injury causes an inflammatory response by the immune system followed by a reparative phase, which lasts until several days after the acute event12. To be able to characterize this immune response for ACS patients, blood samples were taken at four different timepoints: acute (TP1); after recanalization (14 [&#177; 8] h) (TP2); 60 [&#177; 12] h later (TP3); before discharge (6.5 [&#177;1.5] days) (TP4) (Figure 1A). For CCS and patients with healthy coronaries, only one time point was available- (TP0). For all patients and time points different assays based on the blood samples were measured: clinical markers of inflammation (Creatine-Kinase (CK), CK-MB, Troponin, C-reactive protein (CRP)), scRNA-seq of peripheral blood mononuclear cells (PBMCs), cytokine analysis, plasma proteomics and prime-seq13 data of neutrophils.
<img alt="Figure 1" class="xfigimg" src="/files/ftp_upload/66659/66659fig01v2.jpg" /> 
Figure 1: Myocardial infarction multi-omic input dataset. Input dataset: The analyzed data includes blood samples from patients (n = 62) with acute coronary syndrome (ACS), chronic coronary syndromes (CCS), and&#160;patients with healthy coronaries (non-CCS). For ACS patients blood samples were included at four&#160;different time points (TP1-4), for CCS and non-CCS patients at a single time point (TP0). Each patient and time point combination is treated as a separate sample in the analysis. Different omic assays were measured on the samples: clinical blood tests (n = 125), scRNA-seq (n = 121), plasma-proteomics (n = 119), cytokine assay (n = 127) and neutrophil prime-seq (n = 121). Subsequently, the described protocol was applied to integrate the data across all omics and explore it using the MOFA model and further downstream analysis (factor analysis, pathway enrichment). <a href="https://www.jove.com/files/ftp_upload/66659/66659fig01largev2.jpg" target="_blank">Please click here to view a larger version of this figure.</a>
As input for the workflow as presented here, we take raw counts from scRNA-seq data after processing with cellranger and quality control (QC) as, for example, outlined in the scanpy14 preprocessing tutorial. For cell-type annotation, we used the automated Azimuth15 pipeline. The counts are then aggregated on the sample level for each cell-type by taking the mean across all cells for each sample and cell-type (pseudobulk aggregation). Plasma-proteomics is included as normalized and median-centered intensities, and for neutrophils, we take the umi unique molecular identifier (UMI) exon counts from the prime-seq. On cytokine and clinical values, no previous preprocessing has been applied. Further details on the (experimental) data generation are outlined in the corresponding manuscript11. As the results presented here are based on using the automated Azimuth annotation for cell-types in the scRNA-seq data compared to the marker based strategy that was used in the referenced publication the results presented here are similar but not exactly the same as presented in the publication. In the manuscript it could be shown that the cell-type annotation strategy does not change the main patterns and biological interpretations of the analysis but small changes in the exact values resulting from the model might vary. Overall the input data was a complex multi-dimensional dataset including different time points and measurement levels (single-cells vs. bulk) of more than 10,000 different features (genes, proteins, clinical values). A strict pre-processing and data harmonization strategy followed by MOFA analysis has been shown to be a useful and quick tool for exploring the data and extracting relevant immune program. Each time point and patient combination is treated as an independent sample in the MOFA analysis.&#160;Each data type and cell-type is considered a separate view in the MOFA analysis.
This protocol provides instructions for preparing the input data for the workflow, executing the different workflow steps, customizing configurations, interpreting the resulting figures, and iteratively adjusting the configurations based on the interpretations. An overview of the different steps of the protocol, the required input datasets at each step, and resulting figures and datasets is given by the technical workflow overview (Figure 2).
<img alt="Figure 2" class="xfigimg" src="/files/ftp_upload/66659/66659fig02v2.jpg" /> 
Figure 2: Technical workflow overview. Outline of the workflow for the analysis of the multi-omics dataset. The different elements are highlighted by different colors and symbols. Jupyter Notebooks belonging to the Data Preprocessing and Harmonization (1) step are colored in blue. Jupyter Notebooks belonging to the &#39;MOFA Model&#39; (2) step are colored in orange. Jupyter Notebooks belonging to the &#39;Downstream Analysis&#39; (3) step are colored in green. One Jupyter Notebook to be used for comparison of the results is colored in yellow. Configuration files where parameters for the execution of the workflow can be modified are highlighted in purple. Input datasets that are required to run the workflow are indicated by the dataset symbol and highlighted in grey. All figure outputs that are generated during the workflow execution are indicated by the magnifying glass symbol. Datasets generated during workflow execution are indicated as tables. In general, the workflow is executed sequentially: (1) Data Preprocessing and Harmonization consists of two steps: first generation of a pseudobulk table based on the scRNA-seq input data (01_Prepare_Pseudobulk) and subsequent integration and normalization of this data together with all the other sample-level (bulk) inputs (02_Integrate_and_Normalize_Data). Within this step via the configuration files, it is possible to configure for each dataset separately which of the indicated pre-processing and normalization steps (e.g., Sample Filter) should be applied. (2) &#39;MOFA Model&#39;: runs the MOFA model on the generated input of the first step with the configurations specified in the configuration file (03_MOFA_configs.csv) (3) &#39;Downstream Analysis&#39;: consists of three different notebooks which may be run independently of each other to generate insights into the generated MOFA results and associate them with sample meta-data (covariates) provided as input via the &#39;Sample Meta Data.csv&#39; file. (4) &#39;Model Comparison&#39;: is a small separate step that may be used to compare different models generated in step 2. <a href="https://www.jove.com/files/ftp_upload/66659/66659fig02largev2.jpg" target="_blank">Please click here to view a larger version of this figure.</a>
The workflow consists of several Jupyter Notebooks written in R and Python (knowledge of the R and Python language is not required to run the workflow but might be helpful in case errors appear). In various steps of the protocol, parameters are changed via configuration files (&#39;.csv&#39; files containing the postfix &#39;_Configs&#39; in the name). Within the protocol, we only outline the parameters that need to be changed starting from the default configuration.
Several other parameters may also be changed, for example to customize the pre-processing. A documentation of these parameters and explanations is given in the file &#39;Documentation_Config_Parameter&#39;, which is included in the downloaded repository.

Author Spotlight: Integrated Multi-Omics Analysis for Unveiling Multicellular Immune Signatures in Clinical Heart Attack Cohorts

Application of Unsupervised Multi-Omic Factor Analysis to Uncover Patterns of Variation and Molecular Processes Linked to Cardiovascular Disease

Our workflow makes it possible to easily analyze complex multi-omics data sets of different resolutions. The approach extracts a major patterns of variants that are either unique or shared to the specific data types and aggregates them. The resulting so-called factors can then be linked to molecular processes and clinical or technical covariates.Our analysis was among the first to apply the MOFA model to multi-omics and single-cell data of multiple samples. Importantly, these samples were from a clinical cohort of heart attack patients. This allowed us to identify multicellular immune signatures that are associated with outcome and disease state.So, the availability of single-cell and multi-omic data sets increases, but often, the features of those data sets are only analyzed separately. This limits insights because usually, biological processes are the result of the interactions between multiple features and cell types. With our protocols, users can easily perform an integrated analysis of the complete dataset and identify those multicellular programs.We think that applying this protocol to additional multi-omics data sets will generate new insights into other diseases or contexts. These insights will then inform future biomarker or therapeutic studies.

Preparation, Pre-Processing, and Harmonization of Data for MOFA Analysis

Begin by adding all the multiomics input data sets to the input data folder. Here they contain data from patients with stable, chronic, and acute coronary syndromes. To pre-process the data, click on the folder symbol, then double-click on the mofa_workflow scripts and configurations to access the configuration folder.Double-click on the data configuration CSV file to open it. In the value column, enter the paths to the input data and results folders. In the configuration name-value column, specify a name to be added as a file extension for all saved files.To save the changes, select File and Save CSV File from the menu at the top. Then, using the navigation menu on the left side, click on scripts to go to the scripts folder. Double click on 00_Configuration_Update.ipynb to open the initialization notebook. To run the script, click on the Restart Kernel and Run All Cells button at the top, and then click Restart in the popup. To navigate to the configurations folder, double-click on configurations.Then double-click on 01_Pre_Processing_SC_Data. csv to open the file. Verify the automatically filled in values, select File and Save CSV file from the menu at the top to save the changes.Then use the navigation menu on the left side and click on scripts to navigate to the scripts folder. Double-click on 01_Prepare_Pseudobulk. ipynb to open the notebook.To run the script, click on the Restart Kernel and Run All Cells button at the top, and then click Restart in the popup. To navigate to the figures folder, double-click first on figures, and then on 01_figures. Open the newly generated plot, FIG01_Amount_of_Cells overview.Then examine the plot to identify cell type clusters with a very low number of cells per sample. Note down the names of those cluster IDs to exclude them in the subsequent steps. To navigate back to the configuration folder, click on dots and double click on configurations.Then open the file 02_Pre_Processing_Configuration_SC.csv. Add all cluster IDs identified for exclusion in the previous step, separated by commas in the cell_type_exclusion column. To save the changes, select File and Save CSV File from the menu at the top.Now open the file 02_Pre_Processing_Configuration. CSV, and adjust the pre-processing configuration for each dataset included and stored in the data input folder. Adjust the parameters in the columns as needed depending on which pre-processing steps should be applied.Save the changes by selecting File and Save CSV File. To navigate to the scripts folder, click on scripts. Open the notebook 02_Integrate_and_Normalize_Data_Sources.ipynb.Click on the Restart Kernel and Run All Cells button at the top, and then click Restart in the popup. Next, navigate to the generated 02_results folder. Click on the folder symbol, then double click on results and 02_results.Verify that it includes the file 02_Combined_Data, configuration name, INTEGRATED CSV containing the combined pre-process data input file.

preparation-pre-processing-and-harmonization-of-data-for-mofa-analysis

Research

JoVE Journal

Genetics

58 visualizações. Comece adicionando todos os conjuntos de dados de entrada multiômica à pasta de dados de entrada. Aqui eles contêm dados de pacientes com síndromes coronarianas estáveis, crônicas e agudas. Para pré-processar os dados, clique no símbolo da pasta e, em seguida, clique duas vezes nos mofa_workflow scripts e configurações para acessar a pasta de configuração.Clique duas vezes no arquivo CSV de configuração de dados para abri-lo. Na coluna de...