847 results for "1m coin team fc 26 Besök Buyfc26coins.com Hjälpsamma och vänliga medarbetare i kundservice..wTD1"

in 52.43 milliseconds.

• WGS in insulinomas

  Whole-Genome Sequencing datasets of insulinoma samples and paired blood controls

  Dataset EGAD50000000464

• Transcriptomic profiling of patient-derived xenografts and organoids in prostate cancer

  Dataset contains RNA-seq of 30 samples (normal prostate tissue, human prostate cancer, PDX and organoids).

  Dataset EGAD00001006404

• Single-Cell TCR/BCR Sequencing for Korean COVID-19 Vaccinated and Patient Samples

  We conducted longitudinal single-cell TCR/BCR sequencing for COVID-19 vaccinated cases (297 samples from 112 cases) and COVID-19 infected cases classified as Asymptomatic (26 samples from 12 cases), Mild (82 samples from 37 cases), Moderate (123 samples from 50 cases), Severe (216 samples from 58 cases), and Critical (142 samples from 41 cases) according to the NIH guideline.

  Study phs003341

• EGA account management

  How to manage your EGA account Welcome to the documentation page for creating an EGA user. The European Genome-Phenome Archive (EGA) is a platform for archiving, managing, and sharing human genomic and phenotypic data. To submit, access, and manage requests for the data hosted on the EGA platform, users are required to register for an account. This documentation page provides step-by-step instructions for creating an EGA user account, as well as information on the different types of EGA user accounts and their associated privileges. You can check the EGA data flow for a better understanding. Manage EGA account step-by-step guide Contact Information Public Keys Password Authenticator Federated Identity Sessions Request an EGA account step-by-step guide Fill in this form.You cannot use a generic email account (e.g., Gmail). Make sure you use your institutional email account.Your email is by default your username.The criteria for a strong password is: It should contain between 8 and 32 charactersIt should contain at least one uppercase letterIt should contain at least one numberIt should contain at least one special characterYou will need to wait for the Helpdesk team to check your identity. Please allow two business days for this step.After the Helpdesk validation step, you will receive an email with a link to validate your institutional email.Click the link to verify your email. It will redirect you to the EGA website.As soon as your account has been validated, you will be able to start adding more information to your EGA profile. For that, you first need to log in using your credentials from step 1. Manage EGA account step-by-step guide As a logged-in user, go to your profile by clicking on Welcome > My Profile. To modify it, click the Edit button.You will see the following options: Contact Information In this section, you can modify the personal information of your EGA account. Public Keys Adding a public key is necessary for downloading data via Live Outbox distribution. If you don’t know how to generate your key, you can follow the instructions available on How do I create a key? Password In the Password tab, you can change your password anytime to ensure the security of your account. However, if you receive an email notifying you that your password was modified and you did not initiate the change, it could be a sign that your account has been compromised. In this case, you should immediately contact our Helpdesk team to report the issue and receive assistance in restoring your account security. Authenticator You can set your two-factor authentication (2FA) system for your EGA account as an identity and access management security method that requires two forms of identification to access resources and data. To obtain your code, please follow the instructions below, also available in the Authenticator tab in your profile. Sessions The Sessions tab displays a list of all devices where you are currently logged in as an EGA user. This includes any open sessions you have on your computer, phone, or other devices. By reviewing the list of active sessions, you can monitor the devices that have access to your account and ensure that there are no unauthorised logins. If you notice any suspicious activity, you can close the sessions from this page to immediately terminate access to your account from the unauthorised device.

  Documentation how-to-manage-your-account

• Data Access Commitee - Monocyte and macrophage lipid accumulation results in downregulated type-I interferon responses - FH monocytes RNA sequencing data

  Dac EGAC00001002495

• Metaplastic breast cancer in a patient with neurofibromatosis type 1 and somatic loss of heterozygosity

  Targeted genetic sequencing was performed on a 41-year-old female with metaplastic breast cancer (MBC) and neurofibromatosis type I (NF1). A custom panel capturing 279 cancer related genes was used to identify a germline pathogenic SNV in NF1, as well several other somatic alterations.

  Study phs001566

• Molecular Epidemiology of Colorectal Cancer (MECC) Metastasis Study: A Germline Variant on Chromosome 4q31.1 Associates with Susceptibility to Developing Colon Cancer Metastasis

  This study compared Ashkenazi Jewish individuals with Stage IV metastatic colon cancer to those with non-metastatic Stage I or II colon cancers. A genome-wide association study, using a 2-stage design, identified a significant association with rs60745952.

  Study phs001045

• Copy number and mutation profiling of Stage 1 epithelial ovarian cancer biopsies

  This project aims at characterizing the genome-wide copy number profile and the variant profile of 139 genes om the five major histotytpes of early-stage (stage I) epithelial ovarian cancer (EOC), to provide insight in the the aethiology and development of the disease.

  Study EGAS00001004961

• Combined Telomerase Vaccination and Pembrolizumab in Advanced Melanoma: WES and RNA sequencing of biopsies from a Phase I Trial

  This dataset contains whole-exome and RNA sequencing of biopsies obtained from patients enrolled in a phase I clinical trial investigating the UV1 vaccine in combination with pembrolizumab in patients with advanced melanoma.

  Dataset EGAD00001011074

• Distribution of data using Live Distribution

  Live Distribution Welcome to the documentation for using the Live Distribution feature for distributing data files securely through the EGA platform. This guide will walk you through the process of downloading encrypted files and decrypting them using Crypt4GH. Please follow the steps below to ensure a smooth experience. Before Downloading Create an EGA user. Make sure that you have the permissions to download the dataset of interest. In case you don’t have access, request access to the dataset. Add your Crypt4GH-compatible public key to your EGA account. Please allow a few hours for your public key to be synced with your profile. Afterwards, you will be able to connect to your EGA outbox using the SFTP protocol. Download Graphical User Interface (GUI) You can use any GUI that supports SFTP connections, such as FileZilla, an open-source FTP client. For Filezilla as your GUI, follow these steps to download files: Open FileZilla and access Site Manager (File > Site Manager). Create a new connection with the following settings (Figure 1): Protocol: SFTP - SSH File Transfer Protocol Host: __EGA_OUTBOX_DOMAIN__ Logon Type: Key file User: your EGA username Key file: path/to/your/private_key Figure 1: Process of establishing a new connection to __EGA_OUTBOX_DOMAIN__ using a key file as the logon method in FileZilla. The figure showcases the FileZilla version 3.52.2 operating on IOS v11.2.3. By following the depicted steps, users can create a secure and efficient connection to the EGA outbox, ensuring seamless data transfers. Click Connect to access your Outbox. This folder serves as your storage space within the EGA cloud, containing files accessible for download in a secure way. Browse the remote directory on the right side of the FileZilla screen. Select the files you wish to download, right-click, and choose Download (Figure 2). Figure 2: Step-by-step process of manually downñoad files from __EGA_OUTBOX_DOMAIN__ using FileZilla, with FileZilla version 3.52.2 operating on IOS v11.2.3. The figure demonstrates how users can downñoad data from the EGA outbox to their local storage by following the depicted steps SFTP command line You can also use the SFTP command line to securely download files from the EGA Outbox. Using SFTP command line client in Linux/Unix Open a terminal window Enter the following command to connect: sftp username@hostname Enter your EGA password To see a list of available sftp commands type help sftp> put – Upload file sftp> get – Download file sftp> cd path – Change remote directory to ‘path’ sftp> pwd – Display remote working directory sftp> lcd path – Change the local directory to ‘path’ sftp> lpwd – Display local working directory sftp> ls – Display the contents of the remote working directory sftp> lls – Display the contents of the local working directory Type get command to download files. For example: get encrypted_file.c4gh Use the bye command to close the connection (SFTP session). Convenient SSH settings Include the following settings in your SSH config file, located in ~/.ssh/config Host __EGA_OUTBOX_DOMAIN__ EGA-outbox hostname __EGA_OUTBOX_DOMAIN__ User username IdentityFile path/to/the/private/key Replace username and path/to/the/private/key with the appropriate settings, and you will be able to connect to the __EGA_OUTBOX_DOMAIN__ simply using sftp EGA-outbox. How to decrypt Files archived at the EGA are encrypted based on Crypt4GH. Hence, to decrypt the files you need to install Crypt4GH. You can install a python implementation of it, with pip install crypt4gh or directly from the Github repository pip install git+https://github.com/EGA-archive/crypt4gh.git After installing Crypt4GH, decrypt files using the following command: crypt4gh decrypt --sk /path/private/key < encrypted_file.c4gh > decrypted_filename The command reads the encrypted file from stdin (with <) and output the decrypted version to stdout (with >). Replace encrypted_file.c4gh and decrypted_filename with the appropriate filenames but make sure to not use the same filename for both reading and writing because your SHELL would then truncate both files before you even read or write. Frequently Asked Questions What username should I use to log in to my outbox? The authentication process for logging in to the EGA website, as well as accessing your inbox and outbox, requires the use of your username, not your email address. Therefore, if you registered a username different from your email address when creating your EGA account, you must use that username to log in. If you have forgotten your registered username, please, contact our Helpdesk team for assistance. I see that some files in my dataset have 'unavailable' as extension. What should I do? Within your Outbox, you'll find a list of all the datasets available for download. Occasionally, certain files may be marked as "unavailable". These unavailable files can be identified by the "unavailable" extension added to their filenames (e.g. filename.fastq.gz.unavailable.c4gh). If you encounter an unavailable file that you need, please reach out to our Helpdesk. We'll promptly work on making the file accessible for download as soon as possible. Specific to using keys Can I access one EGA account from different devices? Yes, you can access your account from different devices by linking several public keys to your EGA account. Each device can generate a unique public-private key pair, and the corresponding public keys can be linked to the same account. This way, you can use different public keys on different devices and still have access to the same account and data. I have several keys and I don't remember which one is which When generating SSH keys, it's a good practice to add a comment using the -C flag. This will allow you to add a descriptive tag to your key, making it easier to identify later on. Here's an example command that generates an SSH key with a comment: ssh-keygen -t ed25519 -C work-pass In this example, we're generating an ed25519 SSH key with the comment work-pass. Once you have multiple keys with different comments, you can use the comments to easily identify each key. To view the comments for your existing SSH keys, you can use the following command: ssh-keygen -l -f /path/to/key This will display the key fingerprint and the associated comment. By checking the comments, you should be able to identify which key is which. What if I can't find my SSH keys for uploading files with a key file, and how can I use new keys? If you can't find your SSH keys, don't worry - you can make new ones. To do this, open your terminal or command prompt and type a command to make a new SSH key. You can pick a name for the key, and choose a password to keep it safe. After making the key, you can add the new key to your account or server where you want to upload files using the key file. This usually involves copying and pasting the key's "public" (e.g. file.pub) part to the right place. If you lose track of the key again, just make a new one and add it again. Keep in mind that SSH keys belong to you and your computer, so if you switch computers or accounts, you'll need to make new keys. I don't want to type the passphrase every time I use the key. What can I do? You can use an ssh-agent to avoid typing the passphrase every time you use the key. An ssh-agent is a program that stores your private keys in memory and provides them to ssh when needed. You can add your key to the ssh-agent using the command ssh-add followed by the path to your key file.Here's an example of the steps to follow: Open a terminal window.Start the ssh-agent by typing the command eval $(ssh-agent).Add your key to the ssh-agent by typing the command ssh-add [key filepath]. For instance, if your key file is located in the home directory with the name mykey, the command will look like this: ssh-add ~/mykey After adding your, key to the ssh-agent, you should be able to use ssh without having to enter your passphrase every time. Can I use my password for authentication (without my private key)? If you prefer to use your username and password for authentication instead of your private key, you can still do so. When using a Graphical User Interface (GUI) such as FileZilla, you can select Ask for password as your Logon Type (Figure 3). This option will prompt you to enter your password when you click Connect, instead of using your private key. Figure 3: This option will prompt you to enter your password when you click "Connect", instead of using your private key. Figure 3: Process of establishing a new connection to __EGA_OUTBOX_DOMAIN__ using your password as the logon method in FileZilla. The figure showcases the FileZilla version 3.52.2 operating on IOS v11.2.3. By following the depicted steps, users can create a secure and efficient connection to the inbox, ensuring seamless data transfers. It's worth noting that using a password for authentication can be less secure than using an SSH key, as passwords can be more easily compromised through various means. However, if you choose to use your password for authentication, selecting "Ask for password" as your Logon Type is a good way to do so securely via a GUI. Why is it better to use my key and not my password? SSH keys for authentication is generally considered to be more secure and convenient than using passwords. SSH keys are more difficult to crack than passwords, and they can be restricted to specific users and machines, giving you more control over access. Once you set up your SSH keys, you can use them to authenticate quickly and easily, without having to enter a password every time. This makes automation of tasks, such as uploading encrypted files, much simpler. Additionally, SSH keys provide better logging, allowing you to keep track of who is accessing your systems and when. All in all, using SSH keys is a good practice for improving security and convenience in your authentication process.

  Documentation access/download/files/live-outbox

• PyEGA3 download client

  PyEGA3 Checks prior to download - Is the dataset available for download? Most datasets are available using the PyEGA3 Download client, except for specific legacy datasets. For these ones, refer to Live Outbox distribution, an alternative way to download these datasets.If the dataset you've been granted access to begins with the ID EGAD5XXXXXXX, please refer to the Live Outbox distribution. If the dataset you have been granted access to contains encrypted data (filename ending in .gpg), contact EGA Helpdesk for detailed information on how to download these files.General Information The PyEGA3 download client is available at its GitHub repository. In its README you will find a step by step guide on how to use it to download files you have been granted access to. PyEGA3 implements the GA4GH-compliant HTSGET protocol supporting requests over genomic ranges. This enables the download of specific regions of interest rather than the entire file. HTSGET is not possible for all the files held by EGA: if the dataset does not contain index files (e.g. filename ending in *.crai), then genomic range requests cannot be performed. The maximum number of connections allowed is 30. If more than 30 connections are used, the download client will encounter 500 errors. The recommended number of connections for maximum output is one. Check out our video tutorial! Frequently Asked Questions General questions How do I download the datasets to which I have been granted access? After setting up your EGA download account, you can proceed to download using the EGA download client – PyEGA3. The pyEGA3 download client is a python-based tool for viewing and downloading files from authorised EGA datasets. This download client is continuously being developed for more user-friendly download experiences. Can I download the dataset’s metadata via the download client? No, the download client cannot be used to download metadata. Registered EGA users can download metadata of an authorised dataset by logging into the EGA webpage and navigating to the dataset of choice. Approximately two thirds down the page you will find the option to download the metadata as a zip file. How do I download large datasets as quickly as possible? The main EGA download client is pyEGA3 download client, a python-based tool for viewing and downloading files from authorised EGA datasets.We could exceptionally consider the option of an Aspera download for users experiencing very slow download rates or facing particular issues.Contact the EGA Helpdesk for further information. Pre-requirement and Installation What are the major requirements for the PyEGA3 download client installation and usage? The PyEGA3 client is compatible with any OS with Python 3.6+ installed. The client requires a connection to the internet, sufficient space on the destination drive, and the EGA download account credentials. Where can I find the PyEGA3 download client installation and download instructions? We strongly recommend checking our video tutorial demonstrating the usage of PyEGA3 from installation to file download. More detailed information is available at PyEGA3 GitHub. What ports are required for the PyEGA3 download client to function? PyEGA3 makes HTTPS calls to the EGA Data API (https://ega.ebi.ac.uk:8443). This port 8443 must be reachable from the location where PyEGA3 is executed to avoid timeouts. PyEGA3 download client How to update the PyEGA3 download client to be on the latest version? Updating the client to the latest version can be achieved by running the following command: pip3 install pyega3 --upgrade I do not have an active EGA account. Can I test the download with the PyEGA3 download client? An EGA download test account (ega-test-data@ebi.ac.uk) has been created for troubleshooting and training purposes. The test account does not require an EGA username and password because it contains publicly accessible files from the 1000 Genomes Project. More information about the use of this account and log in details are available at pyEGA3. I lost my connection while the download was in progress. Does this mean that I have to download the file again from the start? The PyEGA3 download client supports automatic resumption of downloads. To enable quicker download speeds, the API breaks files into up to four segments and downloads them in parallel. With the resume feature, downloads will automatically resume if you encounter any errors or if the connection is interrupted. How can I improve the overall download speed of the PyEGA3 download client? Download speeds can be optimised using the --connections parameter which will parallelise download at the file level. If the --connections parameter is provided, all files >100Mb will be downloaded using the specified number of parallel connections. It is important to note that files are still downloaded sequentially, so using multiple connections does not mean downloading multiple files in parallel. The maximum number of connections allowed is 30. If more than 30 connections are used, the download client will encounter 500 errors. The recommended number of connections for maximum output is one. Why is my file taking a long time to be saved? Please note that when a file is being saved, it goes through two processes. First, the downloaded file "chunks" are pieced back together to reconstruct the original file. Secondly, PyEGA3 calculates the checksum of the file to confirm that the file was downloaded successfully. Larger files will take more time to reconstruct and validate the checksum. Why is the HTSGET protocol not working with my dataset of interest? PyEGA3 implements the GA4GH-compliant htsget protocol for supporting requests over genomic ranges. This exciting new feature means that for data files with accompanying index files (e.g. .crai for CRAM files) users can download specific regions of interest rather than the entire file, saving both time and storage space. Please note that in order for the genomic range requests to work for a BAM, CRAM or VCF file there must be an associated BAI, CRAI or TBI file, respectively. If the dataset does not contain these index files then genomic range requests cannot be performed. After download Do I need to decrypt data files downloaded through the pyEGA3 download client? Files are transferred over secure HTTPS connections and received unencrypted, thus there is no need for decryption after data download. What is the purpose of an MD5 file? After the download completes, file integrity is verified using checksums. The PyEGA3 download client automatically verifies each file’s unencrypted md5 after download to ensure that the file was downloaded correctly from the EGA. Errors Why do I get a “400 Client Error” while trying to access the download client? Ensure that your credentials are formatted correctly. Please contact the EGA Helpdesk if you are unsure about your account’s username (i.e. your email address). Why do I get a “500 Server Error”? It is important to note that files are still downloaded sequentially, so using multiple connections does not mean downloading multiple files in parallel. The maximum number of connections allowed is 30. If more than 30 connections are used, the download client will encounter 500 errors. The recommended number of connections for maximum output is one. Otherwise, 500 server errors are internal server errors from EGA’s end. Retry after some time and, if the 500 error persists: check our homepage or Twitter for any outage information or report it to EGA Helpdesk. Why do I get a “slice error”? This type of error occurs when one slice download was prematurely interrupted. Please re-start the same download. The download client will pick up any partial download and download any missing slices. Why do I get the error “Dataset' EGADXXXXXXXXXXX' is not in the list of your authorised datasets”? Please note that the data access was given to the email (username) provided to the Data Access Committee (DAC) in your official request. Therefore, you shall check that the account that you are using is the same one that you sent to the DAC. Why do I get “ERROR:root:Failed to obtain IP address”? This might mean that the connection ports are blocked. Check that the port 8443 is reachable.In case the port is reachable and the error persists, please try to modify the file pyega3.py on line 44 in the python module installation: Replace endpoint = 'https://ipinfo.io/json' with endpoint = 'https://api.myip.com' Why do I get the error “Invalid username, password or secret key - please check and retry”? Make sure that you are using the correct credentials (username and password) and there is no typo. Contact EGA Helpdesk if the problem persists.

  Documentation access/download/files/pyega3

• Glioblastoma epigenome profiling identifies SOX10 as a master regulator of molecular tumour subtype

  Glioblastoma in adult patients are classified into four subtypes, IDH, MES, RTK I, and RTK II, based on DNA methylation and RNA expression data. Tumour subtype transitions commonly occur during the treatment of glioblastoma patients, and transitions to the mesenchymal (MES) subtype have been associated with therapy resistance and adverse prognosis. Here, we generate DNA methylome and histone modification data of glioblastoma primary tumours and show that glioblastoma subtypes differ by their enhancer landscapes. Using Core Regulatory Circuitry analysis of H3K27ac data, and independent analysis of RNA-derived gene regulatory networks, we identified 38 subtype master regulators whose cell type-specific activities we mapped in single-cell RNA sequencing data. These analyses identified the chromatin modifier SRY-Box 10 (SOX10) as a master regulator in tumours of the RTK I subtype. In functional studies we demonstrate that SOX10 loss causes a transition of RTK I tumour cells to a mesenchymal cellular state by altering the accessibility of enhancer-rich chromatin regions and their occupancy by Bromodomain Containing 4 (BRD4), a dynamic constituent of super-enhancers. Treatment with the BRD4 inhibitor JQ1 blocked this transition. These data demonstrate the fundamental role of enhancer chromatin remodelling and master regulator activity in the establishment, maintenance and plasticity of glioblastoma cellular states. We also make our data publically browsable at https://dkfz-b060.github.io/gb_browse/

  Study EGAS00001003953

• Genome-wide cell-free DNA termini in patients with cancer

  The structure, fragmentation pattern, length and terminal sequence of cell-free DNA (cfDNA) is under the influence of nucleases present in the blood. We hypothesized that differences in the diversity of bases at the end of cfDNA fragments can be leveraged on a genome-wide scale to enhance the sensitivity for detecting the presence of tumor signals in plasma. We surveyed the cfDNA termini in 72 plasma samples from 319 patients with 18 different cancer types using low-coverage whole genome sequencing. The fragment-end sequence and diversity were altered in all cancer types in comparison to 76 healthy controls. We converted the fragment end sequences into a quantitative metric and observed that this correlates with circulating tumor DNA tumor fraction (R = 0.58, p &lt; 0.001, Spearman). Using these metrics, we were able to classify cancer samples from control at a low tumor content (AUROC of 91% at 1% tumor fraction) and shallow sequencing coverage (mean AUROC = 0.99 at &gt;1M fragments). Combining fragment-end sequences and diversity using machine learning, we classified cancer from healthy controls (mean AUROC = 0.99, SD = 0.01). Using unsupervised clustering we showed that early-stage lung cancer can be classified from control or later stages based on fragment-end sequences. We observed that fragment-end sequences can be used for prognostication (hazard ratio: 0.49) and residual disease detection inresectable esophageal adenocarcinoma patients, moving fragmentomics toward a greater clinical implementation.

  Study EGAS00001005738

• Genome-wide cell-free DNA termini in patients with cancer

  The structure, fragmentation pattern, length and terminal sequence of cell-free DNA (cfDNA) is under the influence of nucleases present in the blood. We hypothesized that differences in the diversity of bases at the end of cfDNA fragments can be leveraged on a genome-wide scale to enhance the sensitivity for detecting the presence of tumor signals in plasma. We surveyed the cfDNA termini in 72 plasma samples from 319 patients with 18 different cancer types using low-coverage whole genome sequencing. The fragment-end sequence and diversity were altered in all cancer types in comparison to 76 healthy controls. We converted the fragment end sequences into a quantitative metric and observed that this correlates with circulating tumor DNA tumor fraction (R = 0.58, p &lt; 0.001, Spearman). Using these metrics, we were able to classify cancer samples from control at a low tumor content (AUROC of 91% at 1% tumor fraction) and shallow sequencing coverage (mean AUROC = 0.99 at &gt;1M fragments). Combining fragment-end sequences and diversity using machine learning, we classified cancer from healthy controls (mean AUROC = 0.99, SD = 0.01). Using unsupervised clustering we showed that early-stage lung cancer can be classified from control or later stages based on fragment-end sequences. We observed that fragment-end sequences can be used for prognostication (hazard ratio: 0.49) and residual disease detection inresectable esophageal adenocarcinoma patients, moving fragmentomics toward a greater clinical implementation.

  Study EGAS00001005747

• NHLBI TOPMed: The Genetic Epidemiology of Asthma in Costa Rica

  This administrative supplement to the project, "The Genetic Epidemiology of Asthma in Costa Rica" (R37 HL066289) is in response to NOT-HL-14-029 to perform whole genome sequencing (WGS) on existing NHLBI populations. We focus on asthma because of its public health significance. Asthma affects 26 million U.S. children and adults, remains a major cause of morbidity (one-half million hospitalizations a year) and is the most common cause of school and work days lost. Asthma-related costs are estimated to be over $12.7 billion annually. The Asthma Probands for both the extended pedigrees and the trios utilized in this study were selected on the basis of a physician diagnosis of asthma; a history of recurrent asthma attacks or at least 2 respiratory symptoms; and either airway hyperresponsiveness to methacholine or significant response to bronchodilator (Albuterol) administration. These criteria are identical to the criteria used in the Childhood Asthma Management Program (CAMP). The three primary goals of this project are to: (1) identify common and rare genetic variants that determine asthma and its associated phenotypes (height, weight, IgE level, lung function, bronchodilator response, steroid treatment response) through whole genome sequencing (WGS); (2) perform novel family based association analysis of our WGS data to identify novel genes for asthma; and (3) integrate epigenomic and transcriptomic data with our WGS data and determine the epistatic interactions present using systems genomics approaches. Identification of the molecular determinants of asthma remains an important priority in translational science. Genome-wide association studies (GWAS) have been successful in this regard, identifying at least 10 novel susceptibility genes for asthma. However, as with most complex traits, the variants identified by GWAS explain only a fraction of the estimated heritability of this disorder. Herein, we propose a novel family-based study design and state-of-the-art genome sequencing techniques to map a set of sequence variants for asthma and its associated phenotypes and assess the interrelationships of the identified genes and variants using systems genomics methods. We have assembled a team of investigators highly-skilled and expert in whole genome sequencing (Drs. Michael Cho and Benjamin Raby), genetic association analysis (Drs. Scott T. Weiss, Jessica Lasky-Su and Christoph Lange), integrative genomics (Drs. Raby, Kelan Tantisira, Augusto Litonjua and Dawn DeMeo), and systems genomics (Drs. Weiss, Amitabh Sharma, Lange and Raby) to address this important problem with both a novel study design and data set.

  Study phs000988

• RNA-sequence analysis in patients with inclusion body myositis

  This study aimed to elucidate the molecular features of inclusion body myositis (IBM). We performed RNA sequencing analysis of muscle biopsy samples from myositis patients with the pathological finding of CD8-positive T cells invading non-necrotic muscle fibers expressing major histocompatibility complex class I (IBM, polymyositis, and unclassifiable myositis), and controls.

  Study JGAS000068

• WES dataset of a TIL-ACT metastatic melanoma cohort

  Whole-exome sequencing (WES) data from 13 patients with metastatic melanoma in a TIL-ACT cohort, generated to characterize tumor genomics and neoantigen landscapes relevant to adoptive T cell therapy.

  Dataset EGAD50000001731

• alopecia areata

  exome sequencing files from 25 alopecia areata samples from spain.

  Dataset EGAD00001006370

• International Collaboration of Incident HIV and HCV in Injecting Cohorts (InC3)

  This study represents a merged international multi-cohort project of pooled biological and behavioral data from ten prospective cohorts of injection drug users (Grebely J, Morris MD, Rice TM, Bruneau J, Cox AL, Kim AY, et al., 2012, PMID: 23203695). Of the 10 cohorts, six provided data and samples for the genome wide association study (GWAS) entitled &#8220;Genetic Analysis of Opioid Addiction in People Who Inject Drugs&#8221;. The InC3 cohorts included in the GWAS were: i) Australian Trial in Acute Hepatitis C (ATAHC-I, Sydney); ii) Hepatitis C Incidence and Transmission Study in Prison (HITS-p) (Sydney); iii) Hepatitis C Incidence and Transmission Study in Community (HITS-c) (Sydney); iv) HepCo Study (Montreal); v) SuperMIX Study (combining the Networks II &amp; MIX studies, Melbourne); and vi) the UFO Study (San Francisco).

  Study phs002310

• Massachusetts General Hospital (MGH)/Broad Hurthle cell carcinoma whole exome sequencing study

  In this study, we performed whole-exome sequencing of 41 patients with Hurthle cell carcinoma, a thyroid cancer variant with abundant mitochondria. We were able to identify recurrent somatic mutations in both the nuclear and mitochondrial genomes of Hurthle cell carcinoma. Our study identifies mutations in DAXX (GeneID: 1616), TP53 ( GeneID:7157), NF1(GeneID:4763) , NRAS (GeneID:4893), CDKN1A (GeneID:1026), ARHGAP35 (GeneID:2909), the TERT (GeneID:7015) promoter, and mitochondrial-encoded complex I genes to be candidate driver events in Hurthle cell carcinoma. Furthermore, copy number analysis revealed widespread chromosomal losses, resulting in loss-of-heterozygosity and a near-haploid state, to be a defining feature of these tumors. Finally, by analyzing locoregional recurrences and metastases, we were able to identify that widespread chromosomal losses and mitochondrial complex I mutations appear to be early driver events that are selected during clonal evolution.

  Study phs001580

• CRLF2_sequencing_project_

  I hope to gain insight into novel genetic aberrations present in these patients that will highlightimportant pathways that are involved in this subtype of leukaemia. It would be interesting to see ifthe mutations and pathways that are activated are consistent between the patients, or differencesare observed dependent upon whether the patient has the translocation or the PAR1 deletion. Ofnote is the high association with either numerical gains of chromosome X or numerical/structuralabnormalities of chromosome 21 (Down syndrome, iAMP21) in patients with CRLF2 deregulation. Ihope to find abnormalities linking chromosomes X and 21 to CRLF2 deregulation in BCP‐ALL. Byincluding the three patients that are normal for CRLF2, but have consistent genetic abnormalitiesfound in the experimental cohort, I expect to find genetic differences between these two groupsthat will help us to identify novel molecular targets specific to CRLF2 deregulation.

  Study EGAS00001000080

• Single-cell RNA sequence analysis of iPS cell-derived cardiomyocytes treated with S-RBD-sfGFP or GFP

  To determine the transcriptional response in human cardiomyocytes treated with SARS-CoV-2 spike receptor-binding domain (S-RBD-sfGFP), human cardiomyocytes differentiated from induced pluripotent stem cells (iPSC-CMs) were replated on day 21 after differentiation and treated with S-RBD-sfGFP or control-GFP for 48 hours on day 26-28. iPSC-CMs were dissociated and the single cell suspension was analyzed by single cell RNA-sequence.

  Study JGAS000620

• High-depth whole genome sequencing of paired ductal carcinoma in-situ (DCIS) and germline control samples from 26 individuals.

  Deposited here are whole-genome sequencing data for 26 paired breast cancer DCIS and matched-normal samples taken from the same individual. Average sequence coverage is 118x for DCIS samples and 41x for matched-normals. Matched-normal samples are from blood. Sequencing was performed on an Illumina HiseqX. Due to specific restrictions imposed by the ethical approval at sample collection, the use of the germline data is restricted to filtering of somatic mutation calls only and cannot be used outside this purpose.They are a part of a broader project that uses high-depth WGS to investigate the somatic mutation genomic landscape of DCIS in order to uncover biological insights into breast cancer progression as well as possible methods to stratify DCIS patients for individualised therapy or disease monitoring.

  Dataset EGAD50000002237

• RNA-Sequencing and Somatic Mutation Status of Adrenocortical Tumors: Novel Pathogenetic Insights

  To investigate the relationship between transcriptome profile and genetic background in a large series of adrenocortical tumors and to identify new potential pathogenetic mechanisms, we performed transcriptome profiling by high-throughput sequencing. We collected snap-frozen tissue from patients with adrenocortical tumors (n = 59) with known genetic background: 26 adenomas with Cushing syndrome, 17 adenomas with mild autonomous cortisol secretion, 9 endocrine-inactive adenomas, 7 adrenocortical carcinomas. Additionally, we sequenced 4 control samples.

  Study EGAS00001004533

• Breast Cancer Single-Cell RNA-Seq Dataset

  Single-cell RNA-Sequencing of 26 primary breast cancers from Wu et al. (2021) study. Data was generated using the Chromium controller (10X Genomics) and sequenced on the NextSeq 500 platform.

  Dataset EGAD00001007495