data preprocessing about boda2 HOT 4 CLOSED

Sorry, I don't have a pipeline for pulling things off the ENCODE portal which is where the processed MPRA data lives. Supplementary Table 1 contains accession IDs for counts data on the ENCODE portal. You can use these IDs to find the linked Dataset ID. The ENCODE Dataset will have all of the Processed Data files under the "File details" tab. Once you're at this list, look for "bed element enrichments" and "GRCh38" for File type and Genome assembly, and those are the files you'll want. Here's the spec for the BED6+5 files.

For example:

1. HepG2 counts file in SupTable 1: ENCFF379XWL
2. Is linked to data set ENCSR979TSK
3. And points to the processed file ENCFF262AZO

I can try to put together something automated to collect the relevant ENCODE data, but manual collection is what's happening now. I think the ENCODE consortium will be publishing a paper soon about retrieving/analyzing the MPRA data on the portal, so referring to that will likely be the long term best practice.

from boda2.

Thanks for getting in touch and sharing the details. May I ask what are the target columns in SupTable 2 - UKBB_GTEX_CODA_averaged_no_cutoffs.txt that the model is learning to predict?

I'll be closing this soon

from boda2.

Apologies for the delay. {K562,HepG2,SKNSH}_mean are the appropriate columns.

from boda2.

@talkhanz I wanted to let you know that the supplementary table was updated is is available here. In this new file predicted features are activity_columns=['K562_log2FC', 'HepG2_log2FC', 'SKNSH_log2FC'] and we also use stderr_columns=['K562_lfcSE', 'HepG2_lfcSE', 'SKNSH_lfcSE'] for preprocessing.

from boda2.