14982 results for "cancer studies using rna-seq"

in 20.69 milliseconds.

• Evolutionary histories of breast cancer and related clones

  Study EGAS00001006282

• Guiding Evidence Based Therapy Using Biomarker Intensified Treatment in Heart Failure (GUIDE-IT-BioLINCC)

  Accessing Data: Please refer to “Authorized Access” below regarding accessing data through the BioData Catalyst ecosystem. The data from this accession is not available for download through dbGaP.Objective: To determine whether an amino-terminal pro-B-type natriuretic peptide (NT-pro-BNP)-guided treatment strategy improves clinical outcomes vs usual care in high-risk patients with heart failure (HF) and reduced ejection fraction (HFrEF).Background: Heart failure is a common disorder. Standard treatment for HF includes diuretics to control fluid, and drugs called "neurohormonal antagonists" (such as beta-blockers and ACE-inhibitors) to help the heart work more efficiently. The natriuretic peptides, specifically NT-pro-BNP, are biomarkers that reflect HF severity and are significantly associated with adverse outcomes in HF. Smaller studies have evaluated adjusting HF therapy based on natriuretic peptide levels (“guided therapy”) with inconsistent results.Participants: A total of 894 participants were enrolled at 45 sites in the United States and Canada, with 446 randomized to the NT-pro-BNP-guided strategy treatment group and 448 randomized to the usual care treatment group.Design: GUIDE-IT was a multicenter randomized clinical trial with participants randomized to either the NT-pro-BNP-guided therapy strategy or usual care. Given the nature of the study intervention, treatment assignment was not blinded. For participants randomized to the NT-pro-BNP-guided strategy, clinicians were instructed to titrate HF therapy to target an NT-pro-BNP level After an initial visit at 2 and 6 weeks, visits occurred every 3 months throughout the remainder of the study. After therapy adjustment for HF (whether driven by NT-pro-BNP levels or clinical reasons), participants had a 2-week follow-up visit for reassessment. All participants in either group also had blinded NT-pro-BNP concentrations measured in a core laboratory at each study visit. The primary end point was the composite of time-to-first HF hospitalization or cardiovascular mortality. Secondary end points included all-cause mortality, total hospitalizations for HF, days alive and not hospitalized for cardiovascular reasons, the individual components on the primary end point, and adverse events. Conclusions: The guided strategy intervention was stopped in July of 2016 (median follow-up of 15 months) after the study met prespecified inefficacy criteria. Compared to usual care, a strategy of NT-pro-BNP-guided therapy was not more effective in improving time-to-first HF hospitalization or cardiovascular mortality in high-risk participants with HFrEF.

  Study phs003621

• Mapping the Human Connectome - Structure, Function, and Heritability: Healthy Young Adults (Age 22-35 Years) Including Twins and their Non-Twin Siblings

  The Human Connectome Project (HCP) has acquired vast amounts of data about the pattern of long-distance connections (wiring) in the brains of large numbers of healthy participants aged 22-35 using cutting-edge MRI and MEG neuroimaging, and extensive behavioral testing. Types of MR data collected included diffusion MRI (dMRI), resting-state functional MRI (r-fMRI), and structural MRI at both 3T and 7T, and task-evoked functional MRI (t-fMRI) at 3T. Following an extensive period of development and optimization of data acquisition and analysis methods, at Washington University in St. Louis we studied 1,206 participants comprising twins and their non-twin siblings. A subset of 184 twins was scanned again at the University of Minnesota using a 7T scanner. A different subset of 95 twins was studied at St. Louis University using combined resting state and/or task-activated MEG. We were able to collect genetic data on 1142 of our 1206 participants, including 149 pairs of genetically-confirmed monozygotic twins (298 participants) and 94 pairs of genetically-confirmed dizygotic twins (188 participants). Overall, there are 457 different families in the study, as determined by genetic analysis. Our rich set of imaging, behavioral and genetic data - available through the Human Connectome database - will enable many types of analysis of brain circuitry, its relationship to behavior, and the contributions of genetic and environmental factors to brain circuits.

  Study phs001364

• Single cell transcriptomics in expanded Tregs of APS-1 patients

  Aim of study: Exploring single cell transcriptomics in expanded Tregs of with autoimmune polyendocrine syndrome type 1 (APS-1) patients (global gene expression, immune panel, TCR). N= 9 APS-1 patients and 9 healthy controls Protocol 1. Regulatory T cells (Tregs) were isolated from EDTA-blood, activated with anti-CD3/CD28 and IL2, expanded in cell culture for 14 days and stored at -150℃ in AB serum or FBS + 5% DMSO until use. 2. Cells were thawed, run through a Live/Dead column and carefully counted. 10000 Tregs were used as input for the 10x protocol. 3. cDNA was generated and amplified using Single Cell VDJ 5’ Gel Beads, Chromium Next GEM Chip K Single cell Kit, Next GEM Single Cell 5’ GEM Kit v2 and 5’ Feature Barcode Kit (all from 10x genomics). 4. Gene expression (GEX) libraries were generated by using the Library Construction Kit from 10x genomics. 5. T-cell receptor (TCR) libraries were generated using the Single Cell Human TCR Amplification Kit and the Library Construction Kit from 10x genomics. 6. 10x Genomics Target Hybridization Kit and Human Immunology Panel was used with GEX libraries. Only 8 patient samples and 8 control samples were used for the immune panel. 7. All libraries have a unique sample index (Dual Index TT Set A). 8. All samples were sequenced on Illumina NovaSeq 6000 on a NovaSeq S2 flow cell.

  Study EGAS50000000181

• Identification of colorectal cancer susceptibility genes in Japanese

  We performed whole genome sequencing of 617 colorectal cancer patients registered in BioBank Japan to identify novel susceptibility genes.

  Study JGAS000699

• Identification of gastric cancer susceptibility genes in Japanese

  We performed whole genome sequencing of 256 gastric cancer patients registered in BioBank Japan to identify novel susceptibility genes.

  Study JGAS000698

• Identification of gastric cancer susceptibility genes in Japanese

  We performed whole genome sequencing of 2067 gastric cancer patients registered in BioBank Japan to identify novel susceptibility genes.

  Study JGAS000701

• BASIS_Genome_Validation_Study

  Bespoke validation experiments will be performed on ER+ Breast Cancer cases to confirm the presence of mutations found in whole genome sequencing.

  Study EGAS00001000403

• ENCORE__New_Targets_for_Effective_Combination_Therapies_in_Tumors_with_Unmet_Medical_Need

  This study utilises 2G-CRISPR screens to identify effective target combinations in KRAS-mutant colorectal and triple-negative breast cancer cell lines.

  Study EGAS00001004775

• Buccal Sample Methylation for Breast Cancer Detection

  This study encompasses buccal sample DNA methylation (IlluminaMethylationEPIC array) from breast cancer cases and healthy age-matched controls.

  Study EGAS00001007658

• Genomics of Prostate Cancer

  This dataset includes genomic data from patients with prostate cancer. Specimens include archival active surveillance biopsies, radical prostatectomy specimens selected based on evidence of PD-L1 expression and/or T lymphocyte infiltrates, and rapid autopsy material from patients deceased of prostate cancer. These data include low pass whole genome sequencing and targeted sequencing with matched normal.

  Study phs002398

• Identifying and Reducing Disparities in Patient-Reported Outcomes Among African American Prostate Cancer Survivors

  This research study aimed to identify disparities in prostate cancer symptom burden and their contributors among African American, Hispanic, and non-Hispanic White prostate cancer survivors. We collected patient-reported outcomes data, focusing on various aspects of the survivors' health and well-being, clinical data, demographics data, and germline genomic data.

  Study phs003745

• Target sequencing of 11 hereditary breast cancer genes in Japanese

  We performed a case control association study for variants in coding regions of 11 hereditary breast cancer genes in 7,051 female unselected breast cancer patients, 11,241 female controls, 53 male patients, and 12,490 male controls of Japanese ancestry. The 11 genes were ATM, BRCA1, BRCA2, CDH1, CHEK2, NBN, NF1, PALB2, PTEN, STK11, and TP53.

  Study JGAS000140

• Cell_Line_Sub_Clone_Rearrangement_Screen

  Genomic libraries (500 bps) will be generated from total genomic DNA cancer samples and subjected to paired end sequencing on the llumina GA. Paired reads will be mapped to build 37 of the human reference genome to facilitate the generation of genome wide copy number information, and the identification of novel rearranged cancer genes and gene fusions.

  Study EGAS00001000178

• Genomic landscape of inflammatory breast cancer by whole-genome sequencing

  Inflammatory breast cancer (IBC) is the most aggressive form of breast cancer, characterized by a highly invasive and metastatic phenotype, but little is known about its genetic drivers. Here we report whole-genome sequencing (WGS) of 20 newly diagnosed IBC biopsies to characterize for the first time the entire genomic landscape of this disease.

  Study EGAS00001004117

• Whole-exome sequencing of paired tumour/blood of 58 T1 stage bladder cancer patients

  To understand the molecular determinants that underpin the clinical heterogeneity of non-muscle-invasive bladder cancer (NMIBC) we carried out whole-exome sequencing (WES) of stage T1 bladder tumours to identify prognostic biomarkers and novel therapeutic targets. The study includes paired tumour/blood samples of 58 T1 stage bladder cancer patients.

  Study EGAS00001005765

• How to upload GPG files

  Uploading files Users that holds 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. In order to manage the available resources, we enforce a limit of 10Tb per submission account at any one time. Please do not exceed this limit. INBOX FTP The FTP is only compatible with files encrypted using the EGACryptor tool Before uploading Once your submission files have been prepared using the EGAryptor, the resulting encrypted files and associated md5sum files can be uploaded to your submission account using Aspera or FTP. The EGA is a shared, public service with limited resources. In order to manage the available resources, EGA submission boxes should not exceed 8Tb in size, and cannot exceed 12Tb. If you are approaching this limit please contact contact EGA Helpdesk so that we can advise on how to register the associated metadata and trigger the archiving of files, so that you can continue with your submission. If we note that your submission account increases above 10Tb on a consistent base your password will be changed until metadata is associated. Aspera Download Aspera Using Aspera FTP FTP windows FTP Linux / Unix FTP client (Filezilla) FTP and TLS Troubleshooting Troubleshooting Aspera Download Aspera is a commercial file transfer protocol that may provide faster transfer speeds than ftp especially over longer distances. The Aspera ascp command line client. Please select Aspera Connect. The ascp command line client is distributed as part of the aspera connect highperformance transfer browser plugin and is free to use, without registration. The minimum required version of the IBM Aspera Cli is V4. Further instructions. Using the Aspera ascp command line program The location of the ascp program in the filesystem: Mac: on the desktop go cd /Applications/Aspera\ Connect.app/Contents/Resources/ there you'll see the command line utilities where you're going to use ascp. Windows: the downloaded files are a bit hidden. For instance, in Windows 7 the ascp.exe is located in the users home directory in: AppData\Local\Programs\Aspera\Aspera Connect\bin\ascp.exe Linux: should be in your user's home directory, cd /home/username/.aspera/connect/bin/ there you'll see the command line utilities where you're going to use ascp. Your command should look similar to this: ascp -P33001 -O33001 -QT -l300M -L- /path/file ega-box-N@fasp.ega.ebi.ac.uk:/path If you wish to upload several files without being requested the password, please use the below command : ASPERA_SCP_PASS=ega-box-password ascp -P33001 -O33001 -QT -l300M /path/file ega-box-N@fasp.ega.ebi.ac.uk:/path/ Explanation of parameters l300M option sets the upload speed limit to 30MB/s. You may wish to lower this value to increase the reliability of the transfer. L option is for printing logs out while transferring files to upload can be a file mask (e.g. '/homes/submitter/*.srf) or a list of files. ega-box-N is your submission account login. Add k2 switch for transfer restarts Check the command line transfer usage for more configuration details. Using FTP to upload your prepared files Use your preferred ftp client. For example, lftp is a popular choice for Linux and Mac users. Use binary mode for file transfers. Use ftp.ega.ebi.ac.uk as the target host. Login with your ega-box username and password. Upload files to your private ega-box upload area. Depending on your network setting you might wish to start FTP in passive or active mode. Using default FTP command line client in Windows Start the command line interpreter: press WinR, type cmd, hit enter Enter ftp ftp.ega.ebi.ac.uk Enter your submission username Enter your submission password Type binary to enter binary mode for transfer To see a list of available ftp commands type help. Type ls command to check the content of your submission account. Type prompt to switch off confirmation for each file uploaded. Use mput command to upload files: mput *.bam* Use bye command to exit the ftp client. Use exit command to exit the command line interpreter. Using default FTP command line client in Linux / Unix Open a terminal and type ftp ftp.ega.ebi.ac.uk Enter your submission username Enter your submission password Type binary to enter binary mode for transfer To see a list of available ftp commands type help. Type ls command to check the content of your submission account. Type prompt to switch off confirmation for each file uploaded. Use mput command to upload files: mput *.bam* Use bye command to exit the ftp client. Using FTP client FileZilla We recommend the use of FileZilla, a free FTP client . FileZilla is open source software distributed free of charge under the terms of the GNU General Public License. Use the following connection details (File - Site Manager) and add yoursubmission account username and password: Using FTP client FileZilla Select the files you wish to upload and then select upload: Using FTP client Filezilla Using LFTP with TLS We recommend the following to force the use of a secure connection. lftp > set ftp:ssl-force yes We also recommend setting the following for not encrypting the bulk data itself for performance reasons (theauthentication will still be encrypted): lftp > ftp:ssl-protect-data no In order to verify the certificate,the recommended way would be to use the CA certificates from your machine. To do that use this command in lftp adjusting the path to your ca-certificates location. lftp > ssl:ca-file "/etc/ssl/certs/ca-certificates.crt" If that is not possible or certificates are old and you can't update them, you can download the certificates needed from Quo Vadis Digital Repository The two certificates to download in PEM format are: QuoVadis Root CA2 G3 QuoVadis EV SSL ICA G3 Then you can concatenate them in a file one after the other and save it as lftp-certificates.pem Once this is done you have to point the ssl:ca-file variable to the path lftp > set ssl:ca-file "/path/to/lftp-certificates.pem" Also note that you can save this configuration at ~/.lftp/rc Another option is to download the certificates and add them to the ca-certificates of your machine. For example: In RHEL7 and cenots and others box the process to add the certificates globally is: Download the two certificates (in PEM or DER format, doesn't matter) and save them to "/etc/pki/ca-trust/source/anchors/" Run "update-ca-trust extract" Another less secure option is to turn off certificate verification with the following command: lftp > set ssl:verify-certificate false Troubleshooting If you are having problems with Aspera connection timeouts, it can be down to either one of the following. Transfers cannot start the connection fails instantly. Ensure that TCP traffic on port 33001 is allowed (open) for outbound connections through your computer's firewall and network's firewall. The connection is made, transfers are started, but 0 bytes (0%) are uploaded for each file. Ensure that UDP traffic on port 33001 is allowed (open) for outbound connections through your computer's firewall and network's firewal

  Documentation submission/data/uploading-files/ftp

• Cancer Biomarkers team at The ICR DAC

  DAC for Cancer Biomarkers

  Dac EGAC50000000200

• TransNEO neoadjuvant breast cancer study

  Study EGAS00001004582

• Intratumoural heterogeneity and immune modulation in lung adenocarcinoma of female smokers and never smokers

  Lung cancer is still the leading cause of cancer death worldwide despite declining smoking prevalence in industrialised countries. Although lung cancer is highly associated with smoking status, a significant proportion of lung cancer cases develop in patients who never smoked, with an observable bias towards female never smokers. A better understanding of lung cancer heterogeneity and immune system involvement during tumour evolution and progression in never smokers is therefore highly warranted. We employed single nucleus transcriptomics of surgical lung adenocarcinoma (LADC) and normal lung tissue samples from patients with or without smoking history. Immune cells as well as fibroblasts and endothelial cells respond to tobacco smoke exposure by inducing a highly inflammatory state in normal lung tissue. In the presence of LADC, we identified differentially expressed transcriptional programmes in macrophages and cancer-associated fibroblasts, providing insight into how the niche favours tumour progression. Within tumours, we distinguished eight subpopulations of neoplastic cells in female smokers and never smokers. Through pseudotemporal ordering, we inferred a trajectory towards two differentiated tumour cell states implicated in cancer progression and invasiveness. A proliferating cell population sustaining tumour growth exhibits differential immune modulating signatures in both patient groups. Our results resolve cellular heterogeneity and immune interactions in LADC, with a special emphasis on female never smokers and implications for the design of therapeutic approaches.

  Study EGAS00001006331

• Neoantigen-Targeted CD8+ T-Cell Responses 1 With PD-1 Blockade Therapy

  Background: The primary target of T-cell responses induced against cancer cells are peptides derived from non-synonymous mutations presented by HLA (neoantigens). However, the large diversity of HLA alleles and restricted availability of clinical samples have limited the study of the specificity and the evolution over time of the neoantigen-specific T cell responses induced after treatment with immune checkpoint blockade (ICB) immunotherapy. Methods: We applied a newly developed neoepitope-specific T cell isolation technology to perform a longitudinal landscape analysis of the neoepitope-specific T cells in peripheral blood and tumor from 11 patients with metastatic melanoma; 7 with response and 4 with no response to ICB. Briefly, first using computational prediction, the putative neoantigens in each patient were ranked based on affinity for the patient's HLA and expression levels. Then hundreds of barcoded capture reagents consisting of the patient HLA class I subtypes loaded with the corresponding predicted neoantigen were made and used to isolate neoepitope-specific T cells. Once isolated, the TCRs and the barcodes were sequenced. Finally, the tumor reactivity of the isolated neoepitope-specific TCRs (neoTCRs) was assessed upon co-culture of autologous melanoma cell lines from each patient with primary human T cells expressing the neoTCRs generated using a CRISPR-based non-viral gene editing to replace the endogenous TCRs. Results: The tumor mutation burden ranged between 3507 and 177 for patients with response to therapy and 977 to 31 for patients without response to therapy. We screened a median of 172 predicted neoantigen-HLA per patient across their 6 HLA molecules and isolated neoTCRs in all 11 patients. The number of mutations targeted ranged between 13 and 1. We assessed the neoTCR-tumor reactivity in samples from 3 patients with response and 3 patients without response. 39 of the 62 neoTCRs demonstrated specific recognition and cytotoxicity to patient-matched melanoma cell lines. Multiple T cell clonotypes recognized a limited number of mutations in 7 patients with response (median of 41 different neoTCR clonotypes per patient), and the T cell specificities were recurrently detected in the blood and the tumor over time. Samples from 4 patients without response to therapy also demonstrated neoepitope-specific T cell responses in blood and tumor to a similarly restricted number of mutations, but lacked TCR polyclonality (median 6.5 neoTCR clonotypes per patient) and were not recurrently detected in sequential samples. Conclusion: Effective ICB therapy is associated with polyclonal neoepitope-specific T-cell responses in the tumor and blood that recognize a limited number of immunodominant mutations and are recurrently detected over time.

  Study phs003153

• SNP array karyotyping of upper urinary tract urothelial carcinoma

  Genome-wide copy number analysis of upper urinary tract urothelial carcinoma using GeneChip Human Mapping 250K Nspl

  Dataset EGAD00010002098

• RealSeqS ovarian amplicon counts

  Dataset contains text files that describe the chromosome, position, and read count for an amplicon using the RealSeqS assay.

  Dataset EGAD50000000013

• H3Africa NEEDI SNPs and INDELs

  SNPs and INDELs of novel hereditary neurological disease genes in Mali using Beckman 8800, ABI 3730/3730xl.

  Dataset EGAD00001006295

• 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

• APOBEC3 mutagenesis drives therapy resistance in breast cancer

  Acquired genetic alterations commonly drive resistance to endocrine and targeted therapies in metastatic breast cancer, however the underlying processes engendering these diverse alterations are largely uncharacterized. To identify the mutational processes operant in breast cancer and their impact on clinical outcomes, we utilized a well-annotated cohort of 3,880 patient samples with paired tumor-normal sequencing data. The mutational signatures associated with apolipoprotein B mRNA-editing enzyme catalytic polypeptide-like 3 (APOBEC3) enzymes were highly prevalent and enriched in post-treatment compared to treatment-naïve hormone receptor-positive (HR+) cancers. APOBEC3 mutational signatures were independently associated with shorter progression-free survival on antiestrogen plus CDK4/6 inhibitor combination therapy in patients with HR+ metastatic breast cancer. Whole genome sequencing (WGS) of breast cancer models and selected paired primary-metastatic samples demonstrated that active APOBEC3 mutagenesis promoted resistance to both endocrine and targeted therapies through characteristic alterations such as RB1 loss-of-function mutations. Evidence of APOBEC3 activity in pre-treatment samples illustrated a pervasive role for this mutational process in breast cancer evolution. The study reveals APOBEC3 mutagenesis to be a frequent mediator of therapy resistance in breast cancer and highlights its potential as a biomarker and target for overcoming resistance.

  Study EGAS50000000875

• Colorectal cancer functional annotation - MPRA

  We performed a Massively Parallel Reporter Assay (MPRA) in colorectal cancer (CRC) cell lines HT29 and SW403 and normal colon cell line HCEC-1CT. We specifically targeted the regions around the CRC GWAS loci to identify which variants alter transcription.

  Study EGAS50000000406

• Comprehensive analyses of genetic aberrations in gastroenterological tumors

  Intestinal metaplasia (IM) is a risk factor of gastric cancer in gastric mucosa with Helicobacter pylori infection. To explore the susceptibility to the cancer development in pure gastric IM, we investigated landscape of genetic alterations in gastric single-glands with IM.

  Study JGAS000269

• Digital tEchnology For Lung Cancer Treatment

  DEFLeCT metadata: 1) A table containing the mutational profile for all human genes across the cohort of the 81 PROMOLE lung cancer samples. 2) A table containing the expression levels for all human genes across the cohort of the 81 PROMOLE lung cancer samples. 3) A table containing the clinical, histology data and follow-ups of the cohort of 81 PROMOLE lung cancer patients.

  Dataset EGAD00001010838

• Genetic alterations in benign breast biopsies of subsequent breast cancer patient

  This dataset consists of amplicon sequencing of fibrocystic breast tissues, subsequent cancer tissue and germline control of 17 patients. The target genes include all exons of 27 protein-coding genes and 2 non-coding genes, as well as mutation hotspots in three cancer genes, frequently mutated in breast cancer. Ion AmpliSeq libraries were generated and sequenced on the Ion S5 XL system.

  Dataset EGAD00001004874