11002 results for "fc points to coins calculator Visit Buyfc26coins.com Bardzo pod wrażeniem jakości usług..UK7B"

in 32.08 milliseconds.

• miRNA_expression_in_response_to_LPS_stimulus_in_macrophages

  Our lab is currently using macrophages as a model system for understanding how geneticvariation modulates the response to external environmental stimulus. We want to extend thisbeyond regular polyadenylated RNA to small RNAs such as miRNAs. This project wouldcover the costs of a pilot to study miRNA response to LPS stimulus, and will be performed aspart of a rotation project in the lab. We will require a small number of miRNA libraries and asingle lane of MiSeq

  Study EGAS00001000691

• Microarray Gene Expression Data from Early Skin Biopsies of a Secukinumab Clinical Trial in Psoriasis

  The phase II clinical study CAIN457A2223 (NCT01537432) was designed to evaluate the proportion of patients achieving reversal of chronic plaque psoriasis at weeks 4 and 12 following multiple doses of secukinumab, administered subcutaneously, compared to placebo. 36 patients were enrolled in this study, with 24 being randomly assigned to the treatment arm and 12 to the placebo arm. Starting from week 13, all patients received multiple doses of secukinumab up to week 52 to study long term effects of secukinumab. The microarray gene expression data deposited in this dbGaP study are derived from the early (baseline to week 12) skin biopsies of this clinical trial.

  Study phs001688

• A Genomics-Driven Artificial Intelligence-Based Model Classifies Breast Invasive Lobular Carcinoma and Discovers CDH1 Inactivating Mechanisms

  We developed an artificial intelligence (AI)-model applied to histological images using CDH1 biallelic mutations, pathognomonic for breast invasive lobular carcinoma (ILC), as ground truth. We evaluated the performance of the AI-model to predict the presence of CDH1 biallelic mutations and to diagnose ILC. Subsequently, we investigated the molecular underpinning cases of predicted by the model to harbor a CDH1 biallelic mutations but lacking these alterations according to targeted sequencing. Among this analyses, we subjected to whole genome sequencing (WGS) one ILC case lacking CDH1 biallelic mutations by targeted sequencing and lacking CDH1 promoter methylation to determine the molecular basis of its lobular phenotype.

  Study EGAS50000000485

• Guardians_of_the_genome__protecting_DNA_from_endogenous_sources_of_damage_

  Analysis of mutational signatures caused by DNA repair defects in human induced pluripotent stem (iPS) cells. A reference human iPS cell line will be used for genetic manipulation to introduce homozygous knockouts of 100 genes known to be involved in or connected to DNA repair or DNA editing. Following a defined period of growth after homozygous knockout of each gene, sub clones will be generated and sequenced. The progenitor “parental” IPS cell line will be used to generate reference sequence data, in order to determine the mutational signature acquired due to the gene knockout. This is a pilot study to investigate the effects of oxygen conditions and growth period on mutations acquired

  Study EGAS00001000874

• 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

• How to upload Crypt4GH files

  Uploading files Users who hold an ega-box-XXX account can upload files using either INBOX or FTP. Users who have a Submitter role associated with their email will only be able to upload files using INBOX. Before uploading your files, please make sure that any files that will be uploaded to EGA do not use special characters in their naming convention, such as # ? ( ) [ ] / \ = + < > : ; " ' , * ^ | &. This can cause issues with the archiving process, leading to problems for end users. The EGA is a shared, public service with limited storage. To manage the available resources, we enforce a limit of 10TB per submission account at any one time. If you exceed this limit, a “permission denied” message will be displayed. This will prevent you from uploading more files, but connecting to your inbox.For submissions larger than 10TB, please perform uploads in 10TB batches: register all the metadata and then finalise the submission. Upload the next batch of files and repeat the same metadata registration and finalisation process until you have completed the file upload. Further information can be found in the SP documentation. INBOX FTP The INBOX is only compatible with files encrypted using the Crypt4gh tool Before uploading If you are not a registered EGA user, you will first need an EGA user account. Please note that it may take a few days for your account to be activated, as it needs to be vouched for by the EGA Helpdesk. Once your account is validated, you will be able to request a submitter role. [Optional] Meanwhile, you can create and add your public key to your EGA account profile. This option is not available for old submission accounts (e.g., ega-box-NNN). As soon as you have been granted a submitter role, you will be able to connect with your username and password to the EGA inbox using the SFTP protocol. If you have also registered a public key in your profile, you can also connect using this key. To upload files to your account, you can use the graphical user interface (GUI) or the command line. Graphical User Interface (GUI)We recommend using FileZilla, a free, open-source FTP client. However, you can use any other GUI that allows connecting over the SFTP protocol. For FileZilla as your GUI, follow these steps to upload files: Create a new connection in Site Manager (File > Site Manager) and select the following options (Figure 1): Protocol: SFTP - SSH File Transfer ProtocolHost: __EGA_INBOX_DOMAIN__Logon Type: Key fileUser: your EGA usernameKey file: Path/to/your/private_keyFigure 1: Process of establishing a new connection to __EGA_INBOX_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 inbox, ensuring seamless data transfers.Click Connect, and you will log in remotely to your home directory. You can think of this folder as a storage "in the EGA cloud" in which you will add your files for the EGA. The uploading area has three folders:To-encrypt: Files uploaded in this folder will be encrypted automatically on the fly.Encrypted: Files uploaded in this folder must already be encrypted with Crypt4gh. Upload your files here if your connection is unstable or you have problems completing the upload into-encrypt.Etc: This folder contains two files that allow the server to show you your username and group instead of some internal numbers. Please do not upload files here; otherwise, you will obtain a permission denied error. Find the files you want to upload by browsing your local storage (left side of your screen in FileZilla). Select all the files you want to upload, then right-click on them and select Upload (Figure 2). Figure 2: Step-by-step process of manually uploading files to __EGA_INBOX_DOMAIN__ using FileZilla, with FileZilla version 3.52.2 operating on IOS v11.2.3. The figure demonstrates how users can transfer data from their local storage to the "EGA cloud" by following the depicted steps Please note that regardless of which folder you upload your files in, both folders (to-encrypt, encrypted) will point to the same path (/) (Figure 3). Therefore, you will see your files in both folders. Figure 3: Both folders, to-encrypt and encrypted, point to the same path (/)" If your connection is unstable, please encrypt your files first using Crypt4gh. Then upload them to the ‘encrypted’ folder. The example above shows how to connect to __EGA_INBOX_DOMAIN__ using the private key. However, if you prefer to log in using your credentials, you can do so. Please go to the Frequently Asked Questions (FAQs)  for more information. SFTP command line To upload files securely to your private area of the EGA, you can use SFTP(Secure File Transfer Protocol) with your favorite FTP client. Here's what you need to know to get started: Connect to the target host __EGA_INBOX_DOMAIN__. This is the new hostname for the EGA SFTP service. Log in with your EGA username and key files (or password). Upload files to your private EGA inbox to ensure that only you can access the files. By following these steps, you can securely upload your files to the EGA for safe storage and sharing. Using the SFTP command line client in Linux/Unix Open a terminal and type sftp username@hostnameEnter your EGA passwordTo see a list of available SFTP commands, type helpsftp> put – Upload filesftp> get – Download filesftp> cd path – Change remote directory to ‘path’sftp> pwd – Display remote working directorysftp> lcd path – Change the local directory to ‘path’sftp> lpwd – Display local working directorysftp> ls – Display the contents of the remote working directorysftp> lls – Display the contents of the local working directoryType the "put" command to upload files. For example: put *.bamUse the bye command to close the connection (SFTP session). After uploading- Once you have uploaded files to the inbox, please bear in mind that the checksum needs to be calculated, which can take up to two days. You will only be able to link your files to a run/analysis once the encrypted checksum has been calculated.- When linking your files to the 'Run' or 'Analysis', ensure that the file name matches the file path '/name' in the INBOX folder.- Please delete the files from your SFTP INBOX after all the runs/analyses have been registered and files are ingested (SP > Files > Files ingested). This will clear your inbox space an allow you to upload more files. This will also prevent the files from reappearing in your Submitter Portal inbox. Frequently Asked Questions Specific to the inbox What username should I use to log in to my inbox? The authentication process for logging in to the EGA website, as well as accessing your inbox and outbox, requires the use of your username.  If you have forgotten your registered username, please contact our Helpdesk team for assistance. How are checksums calculated in your inbox? If you encrypt the file beforehand and upload it to the "encrypted" folder, the unencrypted checksum will not be calculated until the file is ingested (i.e., until it is used in a run/analysis). If the file is uploaded to the "to-encrypt" folder, then both checksums are calculated.Please bear in mind that after files have been uploaded to the inbox, the checksum must be calculated, which can take from a few hours to two days.  Specific to using keys to authenticate 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_INBOX_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 submission/data/uploading-files/inbox

• Intercepting Progression from Pre-Invasive to Invasive Lung Adenocarcinoma

  An improved understanding of the biology of lung cancer is needed to intercept the disease at an early point in its progression. In this project we have used multidimensional methods to profile the tumor microenvironment (TME) and to determine the crosstalk between cancer cells and the TME in pre-invasive to invasive human lung non-solid adenocarcinomas. Comparative analysis of the cellular and molecular events associated with the distinct histological stages will lead to identification of the critical events triggering progression and thereby identify targets to intercept disease progression. The data being submitted represents the genomic profiles of patient samples with pre-invasive and invasive human lung adenocarcinomas.

  Study phs002818

• Molecular response of AML blasts to Aza-treatment.

  Azacytidine (Aza) treatment is effective in some patients with acute myeloid leukemia (AML). Clinical observations suggest that DNMT3A-mutant patients represent a subgroup of AML patients that responds particularly well to Aza-treatment. Data coming from a mouse model support this finding and we have already generated molecular data suggesting a molecular pathway involved in Aza-response in DNMT3A-mutant AML patients. We now aim to validate these findings in primary AML-blasts. To this end, we have FACS-sorted blasts from patients with AML prior to and under Aza-treatment and plan to correlate pre-treatment as well as on-treatment methylomes to clinical Aza-response.

  Study EGAS00001004825

• Identification of phenotype-modifier genes

  Patients were stratified at the extremes of the renal phenotype according to their estimated glomerular filtration rate annual decline and subjected to whole exome sequencing (WES) aiming to find candidate phenotype-modifier genes.

  Study EGAS50000000829

• Targeted resequencing of ribosomal proteins in multiple myeloma patient samples.

  We studied 38 multiple myeloma samples to discover mutations in ribosomal proteins. To this end, we ran a specifically designed targeted resequencing study to resequence the coding regions of all ribosomal proteins.

  Study EGAS00001002405

• NHLBI TOPMed: Characterizing the Response to a Leukotriene Receptor Antagonist and an Inhaled Corticosteroid (CLIC)

  Within-subject clinical responses to either inhaled corticosteroids or Montelukast were compared in 126 children with mild to moderate asthma.

  Study phs001729

• Boyes Lab - DAC policy

  Access to this data is controlled. Upon request from a third party for access to the data, a separate Data Sharing Agreement would be put in place between the University of Leeds and the third party prior to EGA granting access to the data to the third party.

  Dac EGAC50000000283

• Project for Development of Innovative Research on Cancer Therapeutics; Identifiying the predictive factors for response to chemoherapy in ovarian cancer

  To identify novel predictive biomarkers of response to chemotherapy for clear cell carcinoma of the ovary

  Study JGAS000076

• NHLBI GO-ESP: Family Studies (Hematological Cancers)

  The NHLBI "Grand Opportunity" Exome Sequencing Project (GO-ESP), a signature project of the NHLBI Recovery Act investment, was designed to identify genetic variants in coding regions (exons) of the human genome (the "exome") that are associated with heart, lung and blood diseases. These and related diseases that are of high impact to public health and individuals from diverse racial and ethnic groups will be studied. These data may help researchers understand the causes of disease, contributing to better ways to prevent, diagnose, and treat diseases, as well as determine whether to tailor prevention and treatments to specific populations. This could lead to more effective treatments and reduce the likelihood of side effects. GO-ESP is comprised of five collaborative components: 3 cohort consortia - HeartGO, LungGO, and WHISP - and 2 sequencing centers - BroadGO and SeattleGO. Two major goals in the study of human malignancies are (i) to understand the genetic basis that underlies the predisposition of certain individuals to develop cancer and (ii) to identify the full spectrum of acquired mutations that occur in human cancers. There has been some progress in both of these areas with respect to hematologic malignancies but much remains to be discovered. As a result of recent advantages in sequencing technologies it is now feasible to sequence multiple individual whole exomes at reasonable cost. Such technologies provide a unique opportunity to transform our understanding of the biological basis of human cancer and to identify inherited genetic variants that predispose individuals to the development of hematologic malignancies. Myeloproliferative neoplasms (MPN), myelodysplastic syndrome (MDS) and acute leukemia are clonal disorders of hematopoieis. Our study involves performing whole exome sequencing of individuals with these disorders for the purpose of identifying (i) novel inherited genetic variants associated with the risk of developing of MPN/MDS/acute leukemia and (ii) novel acquired mutations associated with the development of MPN/MDS/acute leukemia.

  Study phs000632

• NHLBI GO-ESP: Family Studies (JHMI-Molecular Genetics of Atypical Cystic Fibrosis (CF) Study)

  The NHLBI "Grand Opportunity" Exome Sequencing Project (GO-ESP), a signature project of the NHLBI Recovery Act investment, was designed to identify genetic variants in coding regions (exons) of the human genome (the "exome") that are associated with heart, lung and blood diseases. These and related diseases that are of high impact to public health and individuals from diverse racial and ethnic groups will be studied. These data may help researchers understand the causes of disease, contributing to better ways to prevent, diagnose, and treat diseases, as well as determine whether to tailor prevention and treatments to specific populations. This could lead to more effective treatments and reduce the likelihood of side effects. GO-ESP is comprised of five collaborative components: 3 cohort consortia - HeartGO, LungGO, and WHISP - and 2 sequencing centers - BroadGO and SeattleGO. Cystic fibrosis (CF) patients without detectable disease-causing mutations in CFTR present a clinical phenotype very similar to, but possibly discrete from, classic CF. We hypothesize that the phenotype of these atypical CF patients is not due only to mutations in the carbonic anhydrase gene CA12 or in the genes encoding the epithelium sodium ion channel ENaC, but is due to mutations in novel genes that have yet to be associated with CF. The goal of this study is to determine the molecular etiology of this atypical CF.

  Study phs000556

• Small_molecule_inhibitors_in_melanoma___Kenski___Kong___WES

  Small-molecule inhibitors targeting the most commonly activated pathway in melanoma, MAPK pathway (either alone or in combination) are already given to melanoma patients for few years, and initially reduce tumour burden dramatically, eventually melanomas become resistant and tumours progress while on treatment. Resistance to this treatment occurs by acquisition of additional mutations or other alterations that affect the mitogen-activated protein kinase (MAPK) pathway by either direct or indirect signalling. Many resistance mechanisms somehow lead to reactivation of extracellular signal-regulated kinase (ERK), thereby restoring signalling of the oncogenic BRAF/MEK/ERK pathway. In addition, PI3K pathway activation contributes to resistance to BRAF inhibition. Less frequent but equally important to the phenomenon of targeted drug resistance is the observation that B15–20% of BRAF mutant melanoma patients fail to respond to BRAF inhibition already early on treatment, owing to intrinsic resistance. These patients have little therapeutic options, unless immunotherapy can be given. To better understand the resistance mechanisms in MAPK inhibitor-treated melanoma patients and melanoma biology, our lab generated a big panel of MAPK inhibitor resistant melanoma cell lines by continuous drug exposure. The understanding of the genetic landscape and gene expression as well as cross resistance to other treatment regimens, and other aspects of melanoma biology such as phenotype switch, will allow us to better exploit new therapeutic strategies for melanoma patients.

  Study EGAS00001002863

• CYP2C19 long-read sequencing

  Inter-individual differences in drug response based on genetic variations can lead to drug toxicity and treatment inefficacy. A large part of this variability is caused by genetic variants in pharmacogenes. Unfortunately, the Single Nucleotide Variant (SNV) panels currently used in clinical pharmacogenomic (PGx) testing are unable to detect all genetic variability in these genes. Long-read sequencing, on the other hand, has been shown to be able to resolve complex (pharmaco)genes. In this study we have assessed the added value of long-read sequencing for PGx focusing on the clinically important and highly polymorphic CYP2C19 gene. With a capture-based long-read sequencing panel we were able to characterize the entire region and assign variants to their allele of origin (phasing), resulting in the identification of 813 unique variants in 37 samples. To assess the clinical utility of this data we have compared the performance of three different *-allele tools (Aldy, PharmCat and PharmaKU) which are specifically designed to assign clinical haplotypes to pharmacogenes based on all input variants. We conclude that long-read sequencing can improve our ability to characterize the CYP2C19 locus, help to identify novel haplotypes and that *-allele tools are an useful asset in phenotype prediction. Ultimately, this approach could help to better predict an individual’s drug response and improve therapy outcomes.

  Study EGAS00001006929

• Single Cell DNA Methylation Analysis for Forensic Epigenetics

  As part of the Epigenetic CHaracterization and Observation (ECHO) program, the Genomic Analysis Laboratory at the Salk Institute generated the DNA methylation profiles of certain PBMC cell types to determine the change in methylation levels before, during or after exposure to certain biological or chemical agents. Samples from individuals who either handled anthrax in controlled environments or who tested positive to MRSA, MSSA, HIV, COVID-19 or exposed to Flu virus or organophosphates, or control samples were used in single-nucleus methylation (snmC-seq) assays to quantify DNA methylation levels of cytosine residues of the DNA. Around 5-10% cytosine sites were sampled in the assay. Using computational analyses, regions in the genome differentially methylated in response to the exposure were identified. This information can be used to develop diagnostic tools to predict the type of infection or time since exposure.

  Study phs003204

• Ensilication as a Cold‑Chain–Free Solution for High‑Fidelity DNA Preservation in tumor samples

  Nucleic acid preservation requires continuous refrigeration at -20 °C to -80 °C, creating infrastructure barriers limiting genomic medicine access globally. While ambient-temperature preservation methods exist, their effects on DNA integrity and sequence fidelity remain incompletely characterized. The project aims to evaluate ensilication as a method for preserving DNA at ambient temperatures and to determine whether it can match or exceed the fidelity of conventional ultra‑low‑temperature storage. It seeks to assess the technology’s ability to maintain diagnostic accuracy, including detection of clinically actionable variants in tumor samples. Another goal is to compare sequencing‑related artifact rates between ensilicated and cryogenically stored DNA to quantify improvements in data quality. Ultimately, the project aims to establish ensilication as a cold‑chain‑independent solution that enables more accessible global genomic testing and biobanking.

  Study EGAS50000001698

• Assessment_of_genetic_and_epigenetic_variation_in_human_IPS_cells_RNA

  In order to progress human induced pluripotent stem cells (hiPSCs) towards the clinic, several outstanding questions must be addressed. It is possible to reprogram different somatic cell types into hiPSCs and from studies in the mouse, it appears that an epigenetic memory of the starting cell type is carried over to hiPSCs. However a comprehensive comparative study of the characteristics of these hiPSCs has been missing from the literature. Importantly studies which aimed to address these aspects of hiPSCs have used cells from different patients. In order to avoid this important confounding variable and to keep the genetic background constant, tissue samples were procured from the patients and reprogrammed to iPS cells. The transcriptomes of these iPS cells will be compared. Protocol: primary cultures of cells were reprogrammed to iPS cells. RNA was extracted using a standard column extraction kit.

  Study EGAS00001000367

• Ongoing_mutagenesis_RNAseq

  One of the key questions to be explored is whether the biological processes generating specific mutational signatures continue to operate in the human cancer cell lines or simply reflect past mutagenic activity which is no longer operative. To address this question, we have extracted mutational signatures from 1,000 cancer cell lines of diverse cancer types. Several cell lines with mutational signatures of interest were selected, subcloned over a defined period of time and their genomes sequenced. The increased load of the mutations representative of a specific mutational signature within the genome of a subclone when compared to its parental clone was informative of the on-going mutational processes. To further study the recent observation that some of the clones belonging to a same cell line acquired differencet numbers of mutations over a set period of time, their RNA will be subjected to RNA-sequencing to study their differences.

  Study EGAS00001002364

• Determinants of Venetoclax Resistance

  The study aimed to identify genetic determinants of resistance to Venetoclax, a recently approved BCL-2 inhibitor for patients with chronic lymphocytic leukemia (CLL). Whole exome sequencing of tumor samples from 6 CLL patients relapsing on Venetoclax revealed clonal evolution when comparing pre- and post-Venetoclax samples. Genetic screens for genes involved in sensitivity to Venetoclax and investigations of resistant cell lines (including OCI-Ly1) revealed MCL-1 and regulators of cellular energy metabolism (AMPK pathway) to drive resistance to Venetoclax. Further explorations of patient samples confirmed MCL-1 expression and AMPK activation to be increased at relapse on Venetoclax.

  Study phs001875

• Ancient genomes reveal insights into ritual life at Chichén Itzá

  To better understand the origin and biological relationships of the sacrificed children from Chichén Itzá to each other and to present-day inhabitants of the region, here we used a combined bioarchaeological and genomics approach to investigate 64 subadults interred within a chultún near the Sacred Cenote and compare them to 68 present-day Maya inhabitants of the nearby town of Tixcacaltuyub, as well as to other available ancient and contemporary genetic data from the region. The community of Tixcacaltuyub has been collaborating with our research team for many years, and their perspectives informed the development of this project.

  Study EGAS50000000296

• DAC Portal documentation

  DAC Portal Welcome to the DAC Portal documentation! If you are involved in governance or legal aspects, technical or operational aspects, or serving as a data steward, this page will be helpful for you. By exploring these materials, you can define your own Data Access Committee (DAC) and policies, understand the minimal requirements for a DAC and a policy object, and comprehend how the EGA data access requests are managed. DAC Portal Index Setting up your account DACs and Policies Pending Request table Manage Data Requests History page Audit your DACs, policies, and datasets Deprecation User Preferences DAC API - A programmatic approach Setting up your account Register yourself as an EGA user. The Helpdesk team will validate your account (this could take up to 48 hours). After validation, you will receive an email with a link to verify your email - Make sure you click on the link to verify your account! If you don’t receive the email, please check your spam folder. Once your account is active you can login to the DAC Portal. We recommend you to check out the Take The Tour! DACs and Policies Create a DAC Click on Create a DAC Add the title and description to your DAC. Once ready, click on the ‘Create’ button. You will have to wait until the Helpdesk Team validates the creation of your DAC. Once approved by Helpdesk, your DAC will be assigned with a persistent identifier (EGAC). Edit a DAC Once your DAC is registered and approved, you can edit it and add contacts. Remember, you can add as many contacts as needed. And, you can also remove/add contacts anytime. To add a contact, you must write the username or email of a registered EGA user in the Members field. Once you have typed the whole username or email, a drop-down menu will appear where you can select the contact. Select a contact from the drop-down menu. Make sure you write the full username or email of the contact so it appears as an option. Make sure that you select one main contact. Set up the role you want to grant to the new contact of the DAC. We recommend you to check out the FAQ to learn more about the different roles! After adding all the necessary contacts and assigning roles, click on Update. This will send an email notification to the new DAC member, letting them know about the invitation to managing the DAC. Once they log into the DAC Portal, they will be able to either accept or turn down the invitation. Create a policy First, please note that all information registered in a policy metadata object will be publicly available on the EGA website. For each released dataset, all users will be able to read the policy under the “Data Access” tab. Select Create a Policy from the Policies tab. Select the DAC that you want your policy to depend on. Add the title and terms and conditions for accessing and using your data. If you already have an external website for data access requests, you can add the URL directly here (see example here). You can find a template of a Data Access Agreement (DAA) document in our Policy documentation page. The DAA template is provided for guidance only and should be adapted to suit your own purpose depending on the security policies, terms for publication or embargoes, and restrictions on data use or sharing. You can also add Data Use Ontologies (DUO) to your policy. These DUO codes are used to semantically tag the terms and conditions of using the data linked to the policy (example). For more information, you can refer to the Data Uso Ontology documentation. Once completed, make sure to click the Create button in order to register your policy. A persistent identifier (EGAP) will be assigned automatically. Edit a policy Please, note that you will not be able to edit the policy if it shows in orange. Meaning that you are a member of the DAC linked to that policy. Members don’t have edit rights. Only admins can edit objects. You can check your registered policies on My policies, available at the menu in the top-right corner. Select your policy. It will then display the information of that policy, allowing you to edit the information. Once you are done with the modifications, click Update. Pending Requests Table Table Settings Upon selecting a specific DAC, you will be presented with a customisable table showcasing all pending data access requests. This table allows you to tailor the displayed information according to your preferences by selecting desired columns. Available Columns (Displayed with the Eye Icon): Date: The date when the data access request was submitted. Full Name: Name and surname of the user submitting the request. Email: Email address associated with the user's request. Username: The username linked to the EGA account of the user submitting the request. Organisation: Affiliated organisation of the user submitting the request. Dataset: EGA accession ID for the requested EGA dataset. Dataset Title: Title of the requested dataset. DAC Comment: Space provided for internal comments related to the request. Expiration: Option to specify an expiration date for granted permissions. Check more information on the pending request table here! Table Filters By default, all data access requests are displayed. However, you have the option to apply filters to refine your view. Follow these steps to apply filters: Click on the More button. This action will reveal the different columns available for applying filters. As you select columns, the checked fields will be displayed at the top of the request table. Choose the specific values within the selected columns that you want to filter for. Click the Search button to apply the selected filters. Do you find yourself frequently applying the same filters? You can save multiple combinations of filters for easy access at any time! Here's how: Click the Save button. Provide a descriptive name for the filter combination. Click Save to confirm. To load saved filters, simply select the saved filter from the dropdown menu to apply it automatically. Check more information on filters here! Advanced Search For users requiring more granular control over their data access requests, the DAC Portal offers an Advanced Search feature using JIRA Query Language (JQL). With JQL, you can craft precise and complex queries to filter and retrieve specific data access requests based on various criteria such as date, user details, dataset attributes, and more. Using JQL's flexibility, you can create custom queries to meet your specific needs, allowing for advanced filtering options beyond the standard filters provided. You can find the Advanced Search feature following these steps: Click the … button Select Advanced To view the allowed fields for filtering and explore all available options, simply click on the info icon. Once you have written the filtering values, click the Search button to apply. Check more information on filters here! Manage Data Requests Upon logging into the DAC Portal, you'll notice a sand clock icon next to the DAC ID, indicating the number of pending requests. Click on the DAC to review these requests. Accept requests Click on the right side of the toggle button to grant access to the user. You can manage other requests before proceeding to the next step. After managing the requests, click on the Apply button. A confirmation box will appear summarising the options to be applied. Click on Yes, Confirm to proceed with granting permissions. Deny requests Click on the left side of the toggle button to deny access to the user. Provide a reason for the denial. Note that the user will receive an email with this reason. Click on the Done button. You can manage other requests before proceeding to the next step. After managing the requests, click on the Apply button. A confirmation box will appear summarising the options to be applied. Click on Yes, Confirm to proceed with denying permissions. Tips! Apply a filter to view all requests to be managed at once. Use the toggle in the row with column names to grant or deny permissions for multiple requests simultaneously. You can grant and deny permissions in the same action, simplifying the process. The confirmation box will provide a summary of all actions, including grants, denials, DAC comments, and expiration dates. History Page The History page serves as a dedicated space to view information regarding all requests managed by all DAC members. Here, you can review active permissions and revoke them as needed. Go to the History page by clicking on the "HISTORY" button from a DAC page in the DAC Portal. Here are the different row types you may find: Current permissions: row in green with a toggle button to revoke permissions on the right. Approved requests: row in green, with no toggle button. Request denied: row in red with “request denied” on the right. Permission revoked: row in red with “permission revoked” on the right. Distinctions to Note! Between Request Denied and Permission Revoked: Request Denied: Refers to requests that were rejected from the outset, indicating that access to the dataset was never granted. Permission Revoked: Indicates that permissions were previously granted but have since been revoked. Users with permissions revoked have previously accessed the dataset. Between Approved Request and Current Permissions: Approved Request: Represents an entry when a data access request has been approved in the past. Current Permissions: Denotes ongoing permissions where a user has present access to the dataset. An approved request may now appear as Permission Revoked in the present. By observing these different rows, users can gain insight into the complete history of a user's interactions and permissions regarding a dataset over time. To revoke access to a specific user for a dataset, follow these steps: Go to History page Look for the row with the specific permissions. You can use the filters! Click on the toggle button to revoke access. Add a denial reason. Bear in mind that the requester will receive the denial reason! Click on the Apply button. Check more information on the Hisotry page here! Audit your metadata objects In the DAC Portal, you can efficiently manage and audit various metadata objects pertinent to your role as a Data Controller. Upon accessing the DAC Portal, you will encounter three primary tabs on the homepage: DAC: Contains information about Data Access Committees (DACs). Policies: Provides insights into linked policies. Datasets: Displays datasets and relevant details. Within each tab, you'll find a comprehensive list of the objects you manage, these being grouped by type (DAC, Policies, Datasets), as well as by your role (member/admin). Whilst the lists give you a quick look, to check how things are connected, we've added a table at the bottom DACs and policies. DACs Let’s check which policies are linked to a specific DAC: Go to "My DACs." Select a DAC. Click on "EDIT" to see more details. You are now on this page: Scroll down to see the linked policies. Click on “List of linked policies of this DAC” and you will see a list of all policies linked to your selected DAC. Policies Do you want to view a list of datasets connected to a particular policy? Follow the same steps mentioned earlier, but head to the policy tab this time. In the policy tab, you'll find a list of all your policies. Here, you may notice two different icons next to the policy ID (EGAP): DAC Icon (): This represents the DAC. Hover your mouse over the icon to see the DAC ID. Dataset icon (): This indicates datasets falling under that policy. The number next to the icon tells you how many datasets are linked to the policy. For example, if you see "2" next to the icon, it means there are two datasets linked to that policy. If you want to check the linked datasets and their relevant information, simply click on a specific policy. You'll then find the "List of linked datasets of this policy" at the bottom of the page. Datasets Finally, in the dataset tab, by default you will see a list of all the datasets you can manage with all your DACs and policies. Yet, we've included two handy ways to organise them: DAC vs. policy: You can group by datasets, either by DAC or policy. Released vs. unreleased: You can sort out datasets based on their release status. Feel free to experiment with both options! For instance, if you want to see which DACs have unreleased datasets, simply select DAC and unreleased, and you'll get the details you need! Deprecation Do you have a bunch of metadata objects like DACs and policies that you don’t need anymore? This section shows you how to get rid of them! But what does "deprecation" mean for EGA? It's basically changing the status of a metadata object to "deprecated," which means we won't be using it in the future. In simple terms, it's like saying these objects are no longer useful. However, because we believe in making metadata FAIR, once an object has a persistent identifier, we can't just delete it. So, instead of deleting, we deprecate it. Here's a helpful tip! If you want to make a metadata object disappear from the DAC Portal, deprecate it. You won’t see it in the portal anymore! Let’s say you want to deprecate a DAC. Let’s do it! Go to "My DACs." Select a DAC. Click "EDIT" to see more details. You are now in this page: Click on the Deprecate button It will then appear a message. There are two options here: Your DAC is not linked to any policy, hence it’s ready to be deprecated. Click on “Yes. Confirm” to deprecate your DAC object! Your DAC is linked to at least one policy, and you need to either: Deprecate the linked policy first, or Link the policy to a different DAC Now, let’s say you don’t want to get rid of the policy altogether, but you want to change the DAC it’s linked to. Here's how: Go to the policy tab. Find the policy you want to change (for example, EGAP50000000019). Choose a new DAC to link it to. Click on Update. See the Edit Policy section for more details. After ensuring that the DAC we want to deprecate isn’t linked to any policy, return to the "My DACs" section and follow the steps outlined previously. This will lead you to a confirmation message. You can only deprecate DACs and Policies. To deprecate a dataset, please contact our Helpdesk team. Check more information on how deprecation works here! User Preferences We have implemented email notifications in the DAC Portal. Here’s the complete list: DACs: Pending requests Approved by Helpdesk Rejected by Helpdesk DAC Invitation Requesters: Data access request approved Data access request denied Permissions revoked Upcoming expiration date As a DAC member, you will be able to decide whether you want to receive the DAC notifications or not. For that, go to the top-right corner menu, select User Preference. You will be able to decide whether you want to receive notifications for: Approved by Helpdesk Rejected by Helpdesk DAC Invitation For pending requests, you will be able to select how often do you want to receive the notification: Daily Weekly Fortnightly As a DAC member, you are responsible for managing data access requests. Consequently, you will receive notifications for pending requests. If you prefer not to manage these requests, please arrange to be removed as a contact for your DAC. Here's a tip! Do you have a pending request that you don’t want to receive a notification? Add a DAC comment! The EGA understands that a request resolution can take some time, for this reason, if you add a comment (make sure you save it by clicking the APPLY button!) we will filter those requests at the time of sending the notification! DAC API - A programmatic approach In addition to the new DAC Portal, we are excited to announce the release of the DAC API. This enables users to programmatically manage permissions. If you are interested in learning more about the technical specifications, you can click the button below. Check out the DAC API specification!

  Documentation access/data-access-committee/dac-portal

• Genetic Etiology of Hypoplastic Left Heart Syndrome

  To understand the genetic etiology of hypoplastic left heart syndrome (HLHS), patients with HLHS were consented and recruited, with blood drawn for DNA extraction and exome sequencing. Using the exome sequencing dataset obtained, rare coding sequence variants were recovered and enrichment analysis was carried out to identify genes and pathways that are likely to contribute to HLHS.

  Study phs001256