15070 results for "cancer studies using rna-seq"

in 36.07 milliseconds.

• Programmatic submission based on XML

  Programmatic submissions (XML based) For further information please check our Submission FAQs, submission quickguide as well as submission terms! Introduction Besides the Submitter Portal tool, EGA supports programmatic sequence and clinical data metadata submissions. If you are not sure what this means, you may want to explore our brief metadata introduction. Programmatic submissions are recommended for array-based submission. Moreove, it may be of help if your submission is recurrent or it is difficult to manage manually due to its sheer size. Otherwise, we highly recommend using the Submitter Portal to perform submissions. In this page we will guide you through the required steps to programmatically submit data to the EGA. Programmatic submissions require your metadata to be structured for an easy and straightforward validation and archival. It basically consists in formatting your metadata as Extensible markup language (XML) files and submitting them to the EGA using the WEBIN Before submitting metadata to the EGA, it is important to ensure that the information in your XML files is compliant with our standards. You can see further details on how these standards are maintained at EGA at our EGA Schemas documentation page. Using WEBIN, you can validate your XML files against EGA's schemas to ensure that your metadata is compliant before submission. WEBIN services WEBIN production service WEBIN test service We advise you to submit your metadata to the test service when submitting to the production service for the first time. The test service is identical to the production service except that all submissions will be discarded in the following 24 hours. This allows you to learn about the submission process without having to worry about data being submitted. Authentication Authentication is required each time a submission is made. The submission service uses HTTPS protocol for metadata encryption and identification to provide a secure submission environment. Data file upload Both Runs and Analyses reference files (e.g. FASTQ need to be uploaded to the EGA before these metadata objects are submitted. In other words, if you submit a Run that references a file that we cannot find associated with your account, the metadata submission will fail. See further details on how to upload your files in our File Upload documentation. Metadata model of the EGA Our metadata model is formed by multiple metadata objects. Check further details in our documentation at our EGA Schema documentation page. Working with EGA XMLs files Now that the basic concepts of the EGA metadata have been described, you can start preparing your programmatic submission through XML. Here you will find the guidance on how to prepare the XML files. Programmatic Submission Tutorial Video Take a look at the Programmatic Submission Tutorial Video, which explains the workflow of a programmatic submission and goes over an example metadata submission. Programmatic Submission Tutorial Video. When building your XML files, we recommend using text editors (e.g.Sublime Text or VisualStudio) that allow you to visualise the structure of the XML with ease. Furthermore, these editors constantly check the consistency of the XML structure. Alternatively, and if the submission consists of a big number of objects (specially analyses), you may find the tool star2xml handy. This tool allows for a direct conversion between metadata in a tabular format (e.g. a spreadsheet) into XMLs. Identifying objects: Aliases and center names Every EGA object must be uniquely identified within the submission account using their alias attribute. The aliases can be used in submissions to make references between EGA objects. Let us dig into EGA's use of aliases and center names: alias: every object should have a name that is unique within your submission account. Once submitted successfully, every alias will be assigned a unique and permanent accession (EGA ID). refname: when an object references another by its alias, the alias of the referenced object goes into the "refname" attribute of the referencing object. For example, if a sample has the alias "sample1", and an experiment uses this sample, then the experiment's "EXPERIMENT/SAMPLE/refname" attribute should be "sample1". center_name: The "center_name" attribute is required within the submission XML and, if not provided when the object is submitted, it will be automatically filled using your default EGA account center_name. This element is the "controlled vocabulary acronym or abbreviation that is provided to the account holder when the account is first generated". If the submitter is brokering a submission for another institute, the submitter should use their special broker account name in broker_name while the data centre acronym remains in center_name. Log-in details should have been provided when you requested a submission account. Please contact our Helpdesk team if you have any questions. run_center: Many submitting centers contract out the actual sample sequencing to another center. In these cases, the sequencing center should be acknowledged in the run_center attribute. Again, this is controlled vocabulary and the acronym should be sought from EGA helpdesk before submitting. Please contact our Helpdesk team if you have any questions. Prepare your XMLs The goal of this section is to provide sufficient information to be able to create the metadata XML documents required for programmatic submissions. Please note, the EGA utilises the XML schemas maintained at the European Nucleotide Archive (ENA). It is important due to the fact that by using a similar system, some pieces of documentation from the ENA's programmatic submission can also help you with your programmatic submission to the EGA. For example, you can submit programmatically without using a Submission XML by following the steps at Submission actions without submission XML. A submission does not have to contain all different types of XMLs. For example, it is possible to submit only a few samples; or a study that is later to be referenced. You can submit each object one by one, or submit all in a batch: you choose what method of submission works best for you. We do recommend, nevertheless, that you submit the objects to be referenced (e.g. samples or studies) first, and the objects that reference these (e.g. experiments or datasets) afterwards. You can see a graphical view of these objects and their relationships at our EGA Schemas page. Independently of the submission scenario, you will always require a Dataset XML. The entity of a dataset is what is used to control access to the given data, in the form of runs or analyses. In other words, when a requester is granted access, it is through the dataset and the objects (e.g. runs or analyses) that the dataset contains, granting access to them in one go. Given the nature of the EGA, a dataset XML will always be required for the data access. First, we will differentiate between submissions of "raw" and "processed" data: Runs and Analyses, respectively. Run data submissions Raw data derives from instruments "as is". For example, a plain sequence file (e.g. FASTQ or unaligned BAM files) would be considered raw data. A typical raw (unaligned) sequence read submission consists of 8 XMLs: Submission Study Sample Experiment Run DAC Policy Dataset When technical reads (e.g. barcodes, adaptors or linkers) are included in the submitted raw sequences, a spot descriptor must be submitted to describe the position of the technical reads so that they can be removed. The following data files can be submitted without providing spot descriptor information in the experiment/run XML: BAM files (single reads) SFF files (single reads without barcodes) FastQ files (single reads without any technical reads) Complete Genomics files Analysis data submissions Processed data is, in some way, refined raw data. This includes raw data that has been processed by some form of analysis method (e.g. alignment, noise reduction, etc.). For example, an aligned sequence (e.g. BAM file), that was created using raw FASTQ files, would be a processed file. This category includes most types of data: sequence alignment files (e.g. BAM or CRAM), clinical data (e.g. phenopackets), sequence variation files (e.g. VCF), sequence annotation, etc. A typical EGA analysis data submission consists of 7 EGA XML: Submission Study Sample Analysis DAC Policy Dataset We accept three different types of analysis data submissions: BAM files (for multiple read alignments) VCF files (for sequence variations) Phenotype files (in any format) In anycase, keep in mind that samples must be created in order to be referenced in the analyses. In other words, the provenance of the information within the BAM, VCF and phenotype files Example XMLs Below you can find a non-extensive list of example XMLs with descriptive fields (i.e. explaining what to provide in each field). Furthermore, you can also find real examples (i.e. the true value of the provided fields) in our GitHub repository. Submission XML The submission XML is used to validate, submit or update any number of other objects. The submission XML refers to other XMLs. New submissions use the ADD action to submit new objects. Object updates are done using the MODIFY action and objects can be validated using the VERIFY action. Descriptive submission XML example True values submission XML example Study XML The study XML is used to describe the study containing a title, a study type and abstract as it would appear in a publication. Descriptive study XML example True values study XML example Please use the following notation within the property "STUDY_LINKS" when including PubMed citations in the Study XML: <STUDY_LINKS> <STUDY_LINK> <XREF_LINK> <DB>PUBMED</DB> <ID>18987735</ID> </XREF_LINK> </STUDY_LINK> </STUDY_LINKS> Sample XML The sample XML is used to describe the samples used to obtain the data, whether they were sequenced, measured in any other way, or have an associated phenotype. The mandatory fields include information about the taxonomy of the sample, sex, subject ID and phenotype. For example, the mandatory attribute fields for each sample would look like these, within the array of "SAMPLE_ATTRIBUTES": <SAMPLE_ATTRIBUTES> <SAMPLE_ATTRIBUTE> <TAG>subject_id</TAG> <VALUE>free text!</VALUE> </SAMPLE_ATTRIBUTE> <SAMPLE_ATTRIBUTE> <TAG>sex</TAG> <VALUE>female/male/unknown</VALUE> </SAMPLE_ATTRIBUTE> <SAMPLE_ATTRIBUTE> <TAG>phenotype</TAG> <VALUE>Free text, EFO terms (e.g. EFO:0000574) are recommended</VALUE> </SAMPLE_ATTRIBUTE> </SAMPLE_ATTRIBUTES> Sample is one of the most important objects to be described biologically, it is highly recommended that “TAG-VALUE” pairs are generated as SAMPLE_ATTRIBUTES to describe the sample in as much detail as possible. For example, were we to give the population ancestry of the sample, we could add a new attribute to the array, in which, for example, we would indicate that the sample derives from an individual of "Mende in Sierra Leone" (MSL), with an african ancestry: <SAMPLE_ATTRIBUTE> <TAG>Population</TAG> <VALUE>MSL</VALUE> </SAMPLE_ATTRIBUTE> Given that VALUE and TAG are free text, the combinations are limitless in order to give you full flexibility on the information you want to provide. We recommend you use the Experimental Factor Ontology (EFO) to describe the phenotypes of your samples. You can provide more than one phenotype by adding more items to the array of SAMPLE_ATTRIBUTES. Phenotypes considered essential for understanding the data submission should be provided. Each phenotype described should be listed as a separate sample attribute <SAMPLE_ATTRIBUTE> </SAMPLE_ATTRIBUTE>. There is no limit to the number of phenotypes that can be submitted. If a suitable EFO accession cannot be found for your phenotype attribute, please consider using another controlled ontology database (e.g. HPO, MONDO, etc.) before using free text. Descriptive sample XML example True values sample XML example Experiment XML The experiment XML is used to describe the experimental setup, including instrument platform and model details, library preparation details, and any additional information required to correctly interpret the submitted data. Where any of these values differ between runs, a new experiment object must exist, since runs are grouped by experiments. Each experiment references a study and a sample by alias, or if previously-submitted, by accession. Pooled data must be demultiplexed by barcode for submission. Descriptive experiment ( Illumina paired read ) XML example True values experiment ( Illumina paired read ) XML example Run XML The run XML is used to associate data files with experiments and typically comprises a single data file (e.g. a FASTQ file). Please note that pooled samples should be de-multiplexed prior submission and submitted as different runs. Descriptive run XML example True values run XML example Analysis XML Given that an analysis can be used to submit any type of processed data to the EGA, we will list below an example of each of the three most common types of analysis XMLs submitted to the EGA: sequence alignments (e.g. BAM files); sequence variation (e.g. VCF files); and clinical metadata or phenotypes (e.g. phenopackets). Regardless of the type of processed data submitted in the analysis, the analysis must be associated with a Study and can reference multiple types of other objects, from samples to experiments, if they are available at the EGA. Just like with Runs, whenever a file is submitted to the EGA through an analysis object, the file MD5 checksums must be present, in order for the EGA to validate file integrity upon transfer. This also includes index files when applicable (e.g. .bai.md5 files). Ideally, any analysis that uses a reference sequence for some kind of alignment (e.g. BAM, CRAM or VCF files), would contain metadata about the alignment, such as INSDC reference assemblies and sequences, by either using accessions (e.g. CM000663.1) or common labels (e.g. GRCh37). Read alignment (BAM) Analysis XML The Analysis can be used to submit BAM alignments to EGA. Only one BAM file can be submitted in each analysis and the samples used within the BAM read groups must be associated with Samples. Descriptive bam alignments XML example True values bam alignments XML example Sequence variation (VCF) Analysis XML The Analysis can be used to submit VCF files to EGA. Only one VCF file can be submitted in each analysis and the samples used within the VCF files must be associated with Samples. Download analysis XML (VCF) Phenotype files The Analysis XML can be used to submit phenotype files to the EGA. Only one phenotype file can be submitted in each analysis and the samples used within the phenotype files must be associated with EGA Samples. Download analysis XML (Phenotype) DAC XML The DAC XML describes the Data Access Committee (DAC) affiliated to the data submission. The DAC may consist of a group or a single individual and is responsible for the data access decisions based on the application procedure described in the POLICY.XML. As with any other object, if it was already submitted to the EGA, there is no need to submit it again: you can reference an existing object within the EGA. Hence, A DAC XML does not need to be provided if your submission is affiliated to an existing EGA DAC.. Further information on DACs can be found here, and you can always contact our Helpdesk team if you have further inquiries. Descriptive dac XML example True values dac XML example Policy XML The Policy XML describes the Data Access Agreement (DAA) to be affiliated to the named Data Access Committee. Descriptive policy XML example True values study XML example Dataset XML The dataset XML describes the data files, defined by the Run.XML and Analysis.XML, that make up the dataset and links the collection of data files to a specified Policy. The dataset xml is commonly the last metadata object to be submitted, since it references multiple other entities. Please consider the number of datasets that your submission consists of. For example, a case-control study is likely to consist of at least two datasets. In addition, we suggest that multiple datasets should be described for studies using the same samples but different sequence technologies. Descriptive dataset XML example True values dataset XML example Validating and submitting your EGA Validating EGA's XMLs through Webin After you have ensured that the XMLs are properly formatted and contain all the required information. You can proceed to validate and submit your data. Use the curl command to validate your XML file: Once you have prepared your XML file and asserted you have access to Webin, you can validate your XML file programmatically against EGA's schemas using the curl command. There are multiple ways in which you can validate your XMLs. This variety has to do with the fact that: (1) there are 2 instances of Webin (test and production); and (2) that validation is a default step during submission. In other words, any time that you submit your data through Webin, it will be validated automatically before being accepted. This allows for 4 possible routes of validation, all having the same validation result: validating or submitting to either the production service or the test service of Webin. For example, directly validating a "study" object XML in the testing service (wwwdev…) would look like the following: curl -u <USERNAME>:<PASSWORD> -F "ACTION=VALIDATE" "https://wwwdev.ebi.ac.uk/ena/submit/drop-box/submit/" -F "STUDY=@study.xml" In this command, you would need to replace <USERNAME> and <PASSWORD> with your EGA account username and password, respectively. You would also replace <INPUT_FILE> with the path to your XML file. A mock example would look like the following: curl -u ega-test-data@ebi.ac.uk:egarocks -F "ACTION=VALIDATE" "https://wwwdev.ebi.ac.uk/ena/submit/drop-box/submit/" -F "STUDY=@study.xml" The validation attempt can have different results depending on the given arguments: If your XML file is valid according to EGA's schemas, you will see a message indicating that your XML file is compliant. For example, see below for our mock example, where the "success" was "true" (i.e. no validation errors found). Nevertheless, notice how the "<STUDY accession=" is empty: it is because we were simply validating, so the study did not get an accession or ID. <?xml version="1.0" encoding="UTF-8"?> <?xml-stylesheet type="text/xsl" href="receipt.xsl"?> <RECEIPT receiptDate="2023-04-11T15:19:28.850+01:00" submissionFile="submission-EBI-TEST_1681222768850.xml" success="true"> <STUDY accession="" alias="Mock example" status="PRIVATE"/> <SUBMISSION accession="" alias="SUBMISSION-11-04-2023-15:19:28:840"/> <MESSAGES> <INFO>VALIDATE action has been specified.</INFO> <INFO>Submission has been rolled back.</INFO> <INFO>This submission is a TEST submission and will be discarded within 24 hours</INFO> </MESSAGES> <ACTIONS>VALIDATE</ACTIONS> <ACTIONS>PROTECT</ACTIONS> If there are any errors or warnings, the tool will display them, allowing you to correct them before submitting your data to EGA. For example, in the following response, it is said that the object we were trying to submit was already existing, and therefore the "success" was "false". <?xml version="1.0" encoding="UTF-8"?> <?xml-stylesheet type="text/xsl" href="receipt.xsl"?> <RECEIPT receiptDate="2023-04-11T15:12:35.609+01:00" submissionFile="submission-EBI-TEST_1681222355609.xml" success="false"> <STUDY alias="Example!_Human Microbiome Project SP56J" status="PRIVATE" holdUntilDate="2023-03-11Z"/> <SUBMISSION alias="SUBMISSION-11-04-2023-15:12:35:576"/> <MESSAGES> <ERROR>In study, alias: "Example!_Human Microbiome Project SP56J". The object being added already exists in the submission account with accession: "ERP127584".</ERROR> <INFO>VALIDATE action has been specified.</INFO> <INFO>Submission has been rolled back.</INFO> <INFO>This submission is a TEST submission and will be discarded within 24 hours</INFO> </MESSAGES> <ACTIONS>VALIDATE</ACTIONS> <ACTIONS>PROTECT</ACTIONS> If the curl command retrieves no response at all, please double check if your username and password are correctly provided. Also notice the "ACTION=..." argument passed to the Curl command. This specifies the action to take during the call to Webin, so we do not need a "Submission" XML just for a validation attempt. See more at submission actions without submission XML. Furthermore, validation of multiple files or objects (e.g. sample, experiment, study…) can be done in a single command by adding more arguments (i.e. '-F'). For example: curl -u <USERNAME>:<PASSWORD> -F "ACTION=VALIDATE" "https://wwwdev.ebi.ac.uk/ena/submit/drop-box/submit/" -F "STUDY=@study.xml" -F "SAMPLE=@sample.xml" -F "DATASET=@dataset.xml" As mentioned above, beside "validate" action in the test environment, you can also validate your metadata by three other methods: "Validate" in the production server. From our example above, you simply need to take the "dev" away from the URL. curl -u <USERNAME>:<PASSWORD> -F "ACTION=VALIDATE" "https://www.ebi.ac.uk/ena/submit/drop-box/submit/" -F "STUDY=@study.xml" "Add" in the development server. From our example above, you would simply need to replace the action: from "validate" to "add". Whatever is submitted to this service will be discarded in 24h, so whether something gets submitted or not would not matter in the long run. curl -u <USERNAME>:<PASSWORD> -F "ACTION=ADD" "https://wwwdev.ebi.ac.uk/ena/submit/drop-box/submit/" -F "STUDY=@study.xml" "Add" in the productionserver. A combination of the previous two methods, which would render this attempt into a submission. This path is just to be taken when you are sure your metadata is compliant and what you want to submit. curl -u <USERNAME>:<PASSWORD> -F "ACTION=ADD" "https://www.ebi.ac.uk/ena/submit/drop-box/submit/" -F "STUDY=@study.xml" What happens after the submission of a dataset XML? Once you have completed the registration of your dataset/s please contact our Helpdesk Team to provide a release date for your study. Please note that all datasets affiliated to unreleased studies are automatically placed on hold until the authorised submitter or DAC contact contact the EGA Helpdesk for the study to be released. We strongly advise you not to delete your data until EGA Helpdesk confirms that your data has been successfully archived.

  Documentation submission/metadata/submission/programmatic-submission-xml

• Young Boost Trial for Breast Cancer patients

  The Young Boost Trial (YBT, YOUNG BOOST / BOOG 2004-01 (Borstkanker) | Kanker.nl investigated the optimal radiation dose for breast cancer patients aged 50 years or younger, treated with breast-conserving therapy (BCT). In this randomized study, participants were assigned to receive either a 26 Gy or a 16 Gy radiation boost, with the primary endpoint being local recurrence. To explore potential predictive biomarkers of treatment response in this patient group, whole exome sequencing (WES) was performed on tumor samples to identify genetic factors that could guide personalized treatment strategies and improve clinical outcomes for these young breast cancer patients.

  Study EGAS50000000797

• 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

• EGAD00010000730

  WTCCC2 Psychosis Endophenotype samples from UK, Germany, Holland, Spain and Australia using the Affymetrix 6.0 array

  Dataset EGAD00010000730

• MS-Twins-EPIC-PBMCs

  Genome-wide DNA methylation profiles of MZ twins clinically discordant for MS generated using Illumina’s Infinium MethylationEPIC BeadChip assay (EPIC array)

  Dataset EGAD00010001618

• GR@ACE_StageI.v02

  Binary Plink files for post-GWAS quality control in 7409 samples genotyped using Axiom 815K Spanish Biobank array (Thermo Fisher)

  Dataset EGAD00010001653

• Methylation_Both

  Epigenome wide DNA methylation assay of OSCC-GB using Illumina methylation array

  Dataset EGAD00010001850

• Dataset for COPD human sputum 16S rRNA gene sequencing data

  Dataset for 16S rRNA gene sequencing data for sputum samples 61 COPD patients, generated using PacBio sequencing technology.

  Dataset EGAD00001009103

• whole genome sequencing data of LMS cell lines

  The data set contains bam files aligned using bwa-0.7.8 mem -t 8 -R.

  Dataset EGAD00001003827

• Heart Failure Network - Xanthine Oxidase Inhibition for Hyperuricemic Heart Failure Patients (HFN EXACT-BioLINCC)

  ObjectivesTo determine the effect of allopurinol after 24 weeks on a composite clinical endpoint that classifies subject's clinical status (improved, worsened, unchanged) in patients with heart failure and high uric acid levels.BackgroundMorbidity and mortality rates for patients with heart failure are high, despite guideline-recommended therapy. Heart failure is characterized by an imbalance between left ventricular (LV) performance and myocardial energy consumption. There is a growing body of evidence that suggests oxidative stress contributes to ventricular and vascular remodeling, and disease progression in heart failure. Targeting potential source(s) of oxidative stress, e.g. Xanthine oxidase (XO), was the focus of recent clinical trials and epidemiological studies. Increased XO activity has been shown to lead to production of superoxide and uric acid (UA). Serum uric acid levels are included in heart failure risk scores, and hyperuricemia is present in about 25% of patients with heart failure. Hyperuricemia is associated with exercise intolerance, reduced survival, and worsening symptoms. The EXACT-HF trial tested allopurinol, an inhibitor of XO, as a potential target therapy for hyperuricemic heart failure patients.Subjects253 subjects were enrolled in the EXACT-HF study. 128 participants were randomized to the allopurinol arm, and of those participants, 119 completed the trial and 9 did not. 125 participants were randomized to the placebo arm, and of those participants, 116 completed the trial and 9 did not.DesignEXACT-HF was a multi-center, double-blind, placebo controlled, 24-week trial of allopurinol. Eligible participants had to be receiving a stable regimen for at least two weeks (3 months for beta-blockers) prior to randomization. Participants were randomized by an automated system to either the allopurinol or placebo arm, and started treatment within 12 hours of completing the baseline visit. During the first week, participants in both treatment arms received 300mg daily of the respective medications. For the following 23 weeks, participants in both treatment arms received 600mg daily of the respective medications. Patients unable to tolerate 600 mg were maintained on 300 mg.The primary endpoint was a composite clinical endpoint (CCE) that classified a subject's clinical status as improved, worsened, or unchanged at 24 weeks. The CCE was determined based on the following: death; hospitalization, emergency room visit or emergent clinic visit for worsening HF; medication change for worsening HF; and Patient Global Assessment using a 7-point scale. Secondary endpoints at 12 and 24 weeks included changes in quality of life as assessed by the Kansas City Cardiomyopathy Questionnaire, and submaximal exercise capacity as assessed by a 6-minute walk test.ConclusionsParticipants who received allopurinol had significantly less serum uric acid laboratory levels after 24 weeks; however, no significant difference was observed in the primary and secondary endpoints between the allopurinol and placebo-treated patients. Therefore, in high-risk HF patients with reduced ejection fraction and elevated uric acid levels, xanthine oxidase inhibition with allopurinol failed to improve clinical status, exercise capacity, quality of life, or LVEF at 24 weeks (Circulation. 2015 May 19; 131(20):1763-71).

  Study phs003533

• HeartShare - Extant Datasets - Harmonized Clinical Trials Collection

  Heart failure with preserved ejection fraction (HFpEF) prevalence is rising with an aging population and contributing comorbidities, such as obesity and diabetes. The Get With The Guidelines - Heart Failure (GWTG-HF) study showed that the proportion of hospitalized HFpEF patients rose from 2005 to 2010, and this trajectory continued to increase through 2020. HFpEF patients have a poor 5-year outcome with a 75% mortality rate. Taken together, these data suggest that HFpEF may be the dominant HF subtype in the future, affecting approximately 1 in 10 adults during their lifetime.In addition to its increasing prevalence, HFpEF is a heterogeneous syndrome with multiple pathophysiological processes and varied clinical presentations. There is an urgent need to improve understanding of different HFpEF phenotypes to match patients with interventions based on their unique subtype. Phenomapping studies have identified between two and six HFpEF clusters/phenogroups with shared features. Of these, three overlapping phenotypes repeatedly arise: an 'older, vascular aging' phenotype, 'metabolic, obese' phenotype, and 'relatively younger, natriuretic peptide (NP) deficiency' phenotype. Continued refinement of these HFpEF subtypes is needed to identify distinct characteristics and underlying biologic and molecular mechanisms towards therapeutic development and future precision trials with improved diagnostic criteria and treatment including prevention.The HeartShare extant datasets collection consists of selected completed trials on HFpEF which have been harmonized for the purpose identifying and defining subtypes. The goal is to identify HFpEF subtypes that have a common pathophysiology. Through the HeartShare extant datasets collection, users can request access to both the harmonized data and the individual trial datasets.To request access to this study collection, select phs003989 in the dbGaP when submitting a data access request. The following clinical trials and harmonized data is available through this collection:Study NameHandleAccessionConsent GroupsSurgical Treatment for Ischemic Heart FailureBioLINCC_STICHphs003493.v1.p1GRUHeart Failure Network Aldosterone Targeted Neurohormonal Combined with Natriuresis TherapyBioLINCC_HFN_ATHENAphs003506.v1.p1GRUHeart Failure Network - Effectiveness of Ultrafiltration in Treating People With Acute Decompensated Heart Failure and Cardiorenal SyndromeBioLINCC_HFN_CARRESSphs003510.v1.p1GRUHeart Failure Network: Diuretic Optimization Strategies Evaluation in Acute Heart FailureBioLINCC_HFN_DOSEphs003524.v1.p1GRUHeart Failure Network - Xanthine Oxidase Inhibition for Hyperuricemic Heart Failure PatientsBioLINCC_EXACT_HFphs003533.v1.p1GRUHeart Failure Network: Functional Impact of GLP-1 for Heart Failure TreatmentBioLINCC_HFN_FIGHTphs003542.v1.p1GRUHeart Failure Network - Nitrate's Effect on Activity Tolerance in Heart Failure with Preserved Ejection FractionBioLINCC_HFN_NEATphs003548.v1.p1GRUHeart Failure Network - Phosphodiesterase-5 Inhibition to Improve Clinical Status and Exercise Capacity in Diastolic Heart FailureBioLINCC_HFN_RELAXphs003565.v1.p1GRUHeart Failure Network - Renal Optimization Strategies Evaluation in Acute Heart Failure and Reliable Evaluation of DyspneaBioLINCC_HFN_ROSEphs003589.v1.p1GRUHeart Failure: A Controlled Trial Investigating Outcomes of Exercise TrainingBioLINCC_HF_ACTIONphs003599.v1.p1HMBHeart Failure: A Controlled Trial Investigating Outcomes of Exercise TrainingBioLINCC_HF_ACTIONphs003599.v1.p1HMB-NPUGuiding Evidence Based Therapy Using Biomarker Intensified Treatment in Heart FailureBioLINCC_GUIDE_ITphs003621.v1.p1GRUSudden Cardiac Death in Heart Failure TrialBioLINCC_SCD_HeFTphs003654.v1.p1GRUTreatment of Preserved Cardiac Function Heart Failure With an Aldosterone AntagonistBioLINCC_TOPCATphs003665.v1.p1HMB-MDSHeart Failure Network - Inorganic Nitrite Delivery to Improve Exercise Capacity in HFpEFBioLINCC_HFN_INDIEphs003667.v1.p1GRUStudies of Left Ventricular DysfunctionBioLINCC_SOLVDphs003668.v1.p1GRUEvaluation Study of Congestive Heart Failure and Pulmonary Artery Catheterization EffectivenessBioLINCC_ESCAPEphs003782.v1.p1GRU

  Study phs003989

• Resolving complex duplication variants using long read genome sequencing in autism spectrum disorder

  The goal of the study is to resolve complex genomic rearrangements in individuals diagnosed with autism spectrum disorder (ASD). Families were identified where at least one individual had previously been diagnosed with ASD, and carried a complex genomic rearrangement as determined by short-read whole genome sequencing. In this study the parents, proband and additional siblings, a total of 20 individuals, were analyzed using Oxford Nanopore Technologies long-read sequencing. Each individual was sequenced on one PromethION flow-cell, providing approximately 25-30X coverage of the genome. The data is deposited as nanopore BAM files with methylation information included.

  Study EGAS50000000390

• Single Cell Sequencing of Sperm (scSperm)

  The aim of this project is to genotype and sequence single spermatozoa from two men, one in his twenties and the other in his seventies. The resulting data is used to quantify the mutations that have arisen in the gametes of both individuals in order to better understand the effect of aging on mutation rates and modes.Project Outline. In order to quantify mutations, semen from two individuals are sequenced. 48 single sperm cells are isolated from each individual, and their DNA is extracted. The resulting genomes are amplified using PicoPlex, GenomiPhi MDA, Repli-G MDA, and MALBAC. QC step is applied to check the quality of WGA DNA using standard Sequenom plex (26 SNPs). A subset of 32 amplification products which pass the intiall QC, are genotyped using Affymetrix SNP6 chips. 12 of the genotyped amplification products are also sequenced. In addition, one multi-cell sample per individual is sequenced as a reference and for validation purposes.Altogether, 12 single cell sperm genomes and two multi-cell genomes are sequenced, coming to a total of 14 genomes. Of the single cell sperm genomes, 2 are sequenced to 50x coverage, and the other 10 to 25x coverage. Both multi-cell genomes are sequenced to 25x coverage.

  Dataset EGAD00001001216

• Identification_and_functional_validation_of_driver_mutations_in_colorectal_cancer

  Targeted exome sequencing of human colorectal cancers for the identification of novel cancer drivers.

  Study EGAS00001000044

• Breast Cancer Matched Pair Cell Line Whole Genomes

  Breast Cancer Matched Pair Cell Line Whole Genomes

  Dataset EGAD00001000130

• Yale Policy for head and neck cancer and HPV clinical trials

  Yale Policy for human controlled access data associated with head and neck cancer and HPV clinical trials

  Dac EGAC50000000403

• Whole_Genome_sequencing_of_rhabdomyosarcoma_tumour_tissue

  The aim of this study is to investigate the genomic landscape of human cancer.

  Study EGAS00001008280

• Single_cell_RNA_sequencing_of_rhabdomyosarcoma_tumour_tissue

  The aim of this study is to investigate the genomic landscape of human cancer.

  Study EGAS00001008281

• Bulk_RNA_sequencing_of_rhabdomyosarcoma_tumour_tissue

  The aim of this study is to investigate the genomic landscape of human cancer.

  Study EGAS00001008282

• Bulk_RNA_sequencing_of_rhabdomyosarcoma_tumour_tissue

  The aim of this study is to investigate the genomic landscape of human cancer.

  Study EGAS00001008278

• Single_cell_ATAC_sequencing_of_rhabdomyosarcoma_tumour_tissue

  The aim of this study is to investigate the genomic landscape of human cancer.

  Study EGAS00001008283

• Single_cell_ATAC_sequencing_of_rhabdomyosarcoma_tumour_tissue

  The aim of this study is to investigate the genomic landscape of human cancer.

  Study EGAS00001008279

• Single cells of colorectal cancer organoids

  Dataset contains 854 single cell sequenced colorectal cancer organoids.

  Dataset EGAD00001005422

• 108 samples liver cancer and normal controls (54 pairs), whole exome sequencing

  liver cancer paired with normal controls, viral and non-viral origin

  Dataset EGAD00001006005

• FFPE Normal Panel V3 Cancer Panel

  FFPE normal panel generation for use with V3 cancer panel 0618521

  Dataset EGAD00001001122

• Single Cell RNAseq of PBMC from renal cancer patients

  Single Cell RNAseq of PBMC from renal cancer patients

  Dataset EGAD00001006175

• Submitting array based metadata

  Submitting array based metadata For further information please check our Submission FAQs, submission quickguide as well as submission terms! The submission metadata required for Array-based submission must be submitted using EGA programmatic submission and by completing the Array-based format (AF) template. The guidelines for this workflow are described on this page. Please notice that all files should be encrypted and uploaded prior to the processing of your EGA Array-based-Format (AF) template. You can request a legacy EGA submission account (ega-box-XXXX) by populating this form. Please, allow two business days for our Helpdesk team to contact you after populating this form. Please notice that all files should be encrypted and uploaded prior to the processing of your EGA-Array-based-Format (AF) template. Metadata Model Registering Metadata Use the EGA programmatic submission to register your Study, Samples, Data Access Committee (DAC) and Policy. This online interface enables you to create new and edit existing submissions. Do not use the Submitter Portal to register the metadata objects for array submissions. Please, go to the EGA programmatic submission. Registering Study Go to the EGA programmatic submission Submit an study XML Take a note of your study accession number (EGASXXXXXXXXXXX) To use the study accession number in a publication, we suggest the following format: "Sequence data has been deposited at the European Genome-phenome Archive (EGA), which is hosted by the EBI and the CRG, under accession number EGASXXXXXXXXXXX. Further information about EGA can be found on https://ega-archive.org "The European Genome-phenome Archive of human data consented for biomedical research"(https://doi.org/10.1093/nar/gkab1059 ). Registering Samples Go to the EGA programmatic submission Submit a sample XML Save the list of accession numbers. These will be needed for the AF template. Registering Data Access Committee Further information on the role of your DAC. Go to the EGA programmatic submission Submit a DAC XML Take a note of the DAC accession number (EGACXXXXXXXXXXX) Registering Policy Your Data Access Policy provides the terms and conditions of data use. This is also referred to as the Data Access Agreement (DAA). Completion of a DAA by the applicant/s should form part of the application process to the Data Access Committee (DAA) Go to the EGA programmatic submission Submit a Policy XML Take a note of the Policy accession number (EGAPXXXXXXXXXXX) Complete the Array-based format (AF) spreadsheet Once you have completed the registration of your Study, DAC and Policy using the programmatix submission, you must then complete and return the AF spreadsheet The AF spreadsheet consists on four components: Do not use EGA IDs registered using the Submitter Portal. You can easily identify objects registered in the Submitter Portal by their EGA ID pattern: EGA[A-Z]5{10 more digits} (e.g. for a sample EGAN50000002506). For populating an AF spreadsheet, please exclusively use EGA IDs following this specific pattern: EGA[A-Z]0{10 more digits} (e.g. for a sample EGAN00001691542). Tab1) Webin accessions : Provide the accession numbers for your study, DAC and policy. Please, also add your ega-box number. Tab2) Sample & phenotypes: Please, leave this tab blank. Tab3) Dataset: Describe the dataset to be created Tab4) Data files: Define how your data is going to be organised into datasets and packets for distribution (linkage between samples and files). Should further assistance be required after going through the guide below; please do not hesitate to contact the EGA helpdesk Once the AF spreadsheet is populated, please send it to our EGA helpdesk for further validation. AF spreadsheet Should your submission require multiple DAC's or policies, use ' ; ' to separate the accession numbers. Accessions AF spreadsheet: Samples & phenotypes Samples and phenotypes AF spreadsheet: Datasets We suggest that each dataset consists of a common set of data. The example below consists of two datasets, grouped according to shared data type, technology and by case/control. We also like to capture the number of unique samples that make up the dataset and the Data Access Committee (DAC) responsible for providing the named dataset and their policy (EGAP). Datasets AF spreadsheet: Data files What follows is an example of how to map your samples to the array based files added to your upload account (4th tab). Data Files Please, find below some practical examples on how to register the linkage between samples-files Case 1) 1 sample or list of samples in different datasets: Data Files In case you have a list of samples that belong to different datasets, please, repeat the samples accession number/s in the first column and link the sample to the corresponding dataset each time (each row). Each row is one linkage between sample-file-dataset. Case 2) 1 sample links to several files: Data Files In order to add multiple files to one sample you MUST use “ ; “ between filenames. Example: file1.gpg;file2.gpg;file3.gpg In case that you want to add an extra file to the sample (phenotype or .Rdata), please use “Additional files” column. Important note: You MUST upload the encrypted and unencrypted md5sum values of all files uploaded to your submission account using the filename nomenclature (file.gpg, file.md5,file.md5.gpg). Your submission will not be processed without md5values supplied for all files in the CORRECT format. What happens after the submission of a dataset? All datasets affiliated to unreleased studies are automatically placed on hold until the authorised submitted or DAC contact instructs our EGA helpdesk for the study to be released. Finally, your data is archived within our databases and prepared for encrypted distribution upon the request of permitted EGA account holders. We strongly advise you NOT to delete your data until we confirm that your data has been successfully archived.

  Documentation submission/metadata/submission/array

• Exceptional Outcomes in a Phase Ib Study Combining PARP and MEK Inhibition, With or Without Anti-PD-L1, for BRCA-Wildtype Platinum-Sensitive Recurrent Ovarian Cancer

  To evaluate regimens combining PARP and MEK inhibition, with or without PD-L1 inhibition, for BRCA-wildtype platinum-sensitive recurrent ovarian cancer (PSROC).

  Study EGAS00001007496

• Primary ER-positive Breast Cancer Treated with Neoadjuvant Letrozole

  These are tumor biopsies and corresponding normal samples from patients with early stage ER+/HER2- breast cancer who had received the aromatase inhibitor letrozole for 10-21 days prior to surgery.

  Study phs000857

• Integrative modeling of tumor genomes and epigenomes for enhanced cancer diagnosis by cell-free DNA.

  3784 whole genome sequencing bam files were generated from plasma cell-free DNA of healthy individuals and patients with cancer. Paired reads were mapped to hg19 human reference genome.

  Study EGAS00001006553

• Transcriptome sequence data from a metastatic breast cancer patient

  Transcriptome sequence data from a metastatic breast cancer patient, generated as part of the BC Cancer Agency's Personalized OncoGenomics (POG) study

  Dataset EGAD00001003690

• RRBS data from TRACERx non-small cell lung cancer (NSCLC) tumours and matched normal adjacent tissue.

  TRACERx (TRAcking Cancer Evolution through therapy (Rx)) is a prospective cohort study designed to investigate intratumor heterogeneity (ITH) in relation to clinical outcome, and to determine the clonal nature of driver events and evolutionary processes in early stage non-small cell lung cancer (NSCLC).

  Dataset EGAD00001015534

• Low-coverage whole-genome sequencing of cancer and healthy plasma circulating DNA

  Plasma samples from patients with melanoma (stage II/III/IV) and breast cancer (stage IV) as well as healthy individuals were subjected to low-coverage whole-genome sequencing (less than 10x average depth). This dataset contains raw fastq files from 39 breast cancer, 127 melanoma and 42 healthy control plasma samples.

  Dataset EGAD00001011817

• The dataset for Genome-wide cell-free DNA fragmentation in patients with cancer

  The dataset for Genome-wide cell-free DNA fragmentation in patients with cancer includes 538 bam files from whole genome next-generation sequencing on the Illumina HiSeq2500. The samples analyzed include plasma samples from healthy individuals and patients with cancer.

  Dataset EGAD00001005339

• Feasibility and Clinical Utility of Whole Genome Profiling in Pediatric and Young Adult Cancers

  Comprehensive Whole Genome Sequencing and Whole Transcriptome (RNASeq) analyses from 114 pediatric patients at Memorial Sloan Kettering. This dataset was used as a prospective clinical utility and feasibility study. By using our Isabl infrastructure for precision medicine, we developed a 2-week end-to-end pipeline to analyze cfDNA, WGS and WTS, which we refer to as cWGTS.

  Study phs002620

• Myocardial Infarction Genetics Exome Sequencing Consortium: Ottawa Heart Study

  The Ottawa Heart Study is a cross-sectional case-control study designed to identify genes that predispose to angiographically defined coronary artery disease. All exome sequencing was performed at the Broad Institute of Harvard and MIT; samples sequence capture was performed using Agilent SureSelect Human All Exon Kit v2 and sequencing was performed on an Illumina HiSeq 2000 or 2500.

  Study phs000806

• Genetic Determinants of Susceptibility to Severe COVID-19 Infection

  The goal of the project is to identify genetic susceptibility variants associated with acute COVID-19 infection susceptibility and severity using whole genome sequencing. The target of the project will include WGS data from whole blood samples of up to approximately 2000 COVID-19 patients (including critical/severe patient subgroup, asymptomatic/mild subgroup) from domestic and international medical institutions.

  Study phs002245

• Whole-genome variant calling of individuals from the study of allergic diseases in the Canary Islands

  Research study of genetic susceptibility and analyses of polygenic risk scores in allergic diseases. This dataset consists of variant data derived from whole-genome sequencing in reference samples from one of the parental populations (i.e., North Africans). The dataset consist of 15 VCF files (and corresponding index files) with a total of 1.58 million variants called using GATK v4 and following the Broad Variant Calling Best Practices, from a set of unrelated individuals sequenced in paired-read mode 2x150 bp using an Illumina HiSeq 4000 sequencer.

  Dataset EGAD50000000429

• Mutational Profile in Newly Diagnosed Diffuse Large B-Cell Lymphoma: GAINED Study

  The GAINED study (NCT01659099) is a randomized phase 3 trial comparing obinutuzumab (G) to rituximab (R) in combination with ACVBP or CHOP14 induction, followed by PET-guided consolidation. This post-hoc analysis focuses on primary mediastinal B-cell lymphoma (PMBL) patients, confirmed through expert pathological review and characterized using gene-expression profiling (GEP) and Next-Generation Sequencing (NGS)

  Study EGAS50000000929

• The Genomic Map of Poland in Open Access

  The main goal is to prepare and share WGS/WES of Polish population In this project NGS (next generation sequencing) was performed using Illumina NOVASEQ 6000 and Illumina DRAGEN aligner was used. Shared BAM and BAM.BAI files Library Construction Protocol: Illumina DNA PCR-Free Prep, Tagmentation. Reference Genome: GRCh37.

  Study EGAS50000000091

• SECRETO Oral metagenome study

  The main goal of the project is to study the associations between the oral metagenome and young-onset cryptogenic ischemic stroke (CIS). The dataset includes information for n=329 participants who underwent saliva sampling. Participants for the SECRETO Oral study were enrolled between December 2013 and November 2019. Shotgun metagenomic sequencing was performed using the Illumina NovaSeq 6000 platform.

  Study EGAS00001007505

• MorphoITH: A Framework for Deconvolving Intra-Tumor Heterogeneity Using Tissue Morphology

  The ccRCC-ITH study WES dataset is derived from a morphology guided multi-regional sequencing dataset used to study the relationship between morphology and genetic evolution. It contains whole exome sequencing data of 18 tumor and 2 adjacent normal samples from 2 UTSW patients, who have consented to depositing their genomic data to public repository. Tumor samples come from different tumor sites, including primary tumor, thrombus and metastases. WES was performed using 75bp paired-end fragments at an average read depth > 50x on a NovaSeq 6000 platform (Illumina, San Diego, CA, USA). The raw data is in fastq format.

  Dataset EGAD50000001550

• Reference Panel for Imputation Analysis Based on Whole Genome Sequencing Data of 3,256 Japanese Individuals(BioBank Japan genotype data)

  This reference panel was constructed using whole genome sequencing data from 3,256 Japanese individuals and the 1000 Genomes Project. It provides high accuracy and utility in analyzing genetic polymorphisms, while also reflecting the genetic diversity specific to the Japanese population. This dataset is expected to contribute to the advancement of genetic research and personalized medicine.

  Study JGAS000746

• CLUSTER Consortium RNAseq PBMC Dataset of pre-methotrexate UK JIA patients cohort

  This is the RNAseq PBMC dataset (paired FASTQ files, n = 82 paired files) generated from pre-methotrexate treatment JIA patients cohort samples. Total PBMC were isolated from pre-treated blood of JIA patients and clinical metadata is also included in this dataset. Samples were sequenced on the NovaSeq6000 instrument (Illumina, San Diego, US) at 300pM, using a 100bp paired read run with corresponding 8bp dual sample index and 5bp or 8bp unique molecular index reads. Run data were demultiplexed and converted to FASTQ files using Illumina’s BCL Convert Software v3.75.

  Dataset EGAD50000001457

• CLUSTER Consortium RNAseq CD8 Dataset of pre-methotrexate UK JIA patients cohort

  This is the RNAseq CD8 dataset (paired FASTQ files, n = 85 paired files) generated from pre-methotrexate treatment JIA patients cohort samples. CD8 cells were sorted from isolated total PBMC by cell sorter (BD FACSAriaTM III, BD Biosciences). Clinical metadata is also included in this dataset. Samples were sequenced on the NovaSeq6000 instrument (Illumina, San Diego, US) at 300pM, using a 100bp paired read run with corresponding 8bp dual sample index and 5bp or 8bp unique molecular index reads. Run data were demultiplexed and converted to FASTQ files using Illumina’s BCL Convert Software v3.75.

  Dataset EGAD50000001456

• CLUSTER Consortium RNAseq CD4 Dataset of pre-methotrexate UK JIA patients cohort

  This is the RNAseq CD4 dataset (paired FASTQ files, n = 86 paired files) generated from pre-methotrexate treatment JIA patients cohort samples. CD4 cells were sorted from isolated total PBMC by cell sorter (BD FACSAriaTM III, BD Biosciences). Clinical metadata is also included in this dataset. Samples were sequenced on the NovaSeq6000 instrument (Illumina, San Diego, US) at 300pM, using a 100bp paired read run with corresponding 8bp dual sample index and 5bp or 8bp unique molecular index reads. Run data were demultiplexed and converted to FASTQ files using Illumina’s BCL Convert Software v3.75.

  Dataset EGAD50000001455

• CLUSTER Consortium RNAseq CD14 Dataset of pre-methotrexate UK JIA patients cohort

  This is the RNAseq CD14 dataset (paired FASTQ files, n = 80 paired files) generated from pre-methotrexate treatment JIA patients cohort samples. CD14 cells were sorted from isolated total PBMC by cell sorter (BD FACSAriaTM III, BD Biosciences). Clinical metadata is also included in this dataset. Samples were sequenced on the NovaSeq6000 instrument (Illumina, San Diego, US) at 300pM, using a 100bp paired read run with corresponding 8bp dual sample index and 5bp or 8bp unique molecular index reads. Run data were demultiplexed and converted to FASTQ files using Illumina’s BCL Convert Software v3.75.

  Dataset EGAD50000001458

• CLUSTER Consortium RNAseq CD19 Dataset of pre-methotrexate UK JIA patients cohort

  This is the RNAseq CD19 dataset (paired FASTQ files, n = 83 paired files) generated from pre-methotrexate treatment JIA patients cohort samples. CD19 cells were sorted from isolated total PBMC by cell sorter (BD FACSAriaTM III, BD Biosciences). Clinical metadata is also included in this dataset. Samples were sequenced on the NovaSeq6000 instrument (Illumina, San Diego, US) at 300pM, using a 100bp paired read run with corresponding 8bp dual sample index and 5bp or 8bp unique molecular index reads. Run data were demultiplexed and converted to FASTQ files using Illumina’s BCL Convert Software v3.75.

  Dataset EGAD50000001459

• EstMB cohort participants sequenced with MGISEQ-2000 platform

  Ensuring the comparability of data generated across different sequencing platforms has become a pressing concern in efforts to uncover robust links between the microbiome and human health. In this study, we conducted a comprehensive comparison of taxonomic and functional profiles from matched human gut microbiome sample pairs, sequenced using both the MGISEQ-2000 (MGI) and NovaSeq 6000 (Illumina NovaSeq) platforms.

  Study EGAS50000001538

• Exome-sequencing of human B cell lymphoma cell lines

  26 cell lines derived from human Diffuse Large B Cell lymphomas (DLBCL) or Burkit Lymphomas (BL) were subjected to whole exome sequencing. Exome capture was carried out using the SeqCap EZ Exome Library 2.0 kit (Roche/Nimblegen) and 100 bp single-read sequencing was performed on a HiSeq2500 (Illumina). 82% of the coding region was covered at least 30x.

  Study EGAS00001001463

• Chromatin 3D interactions mediate genetic effects on gene expression

  Studying the genetic basis of gene expression and chromatin organization is key to characterize the effect of genetic variability on the function and structure of the human genome. Here, we unravel how genetic variation perturbs gene regulation using a dataset combining activity of regulatory elements, gene expression and genetic variants across 317 individuals and two cell types.

  Study EGAS00001003485

• Genetic_vulnerability_of_knockout_cancer_lines

  Genome-wide CRISPR/Cas9 library screen was performed in isogenic cell lines. Three biological replicates were used. Cells were harvested at initiation of screen and at specific time points following cell culture. Using this approach we aim to identify genes specifically important in cell survival in engineered cell lines. Please perform 72, instead of 36, PCR reactions as the screen performed at 200x coverage.

  Study EGAS00001002253

• Lothian Birth Cohort 1921 whole genome sequencing study

  297 members of the Lothian Birth Cohort 1921 (LBC1921) were sequenced using the Illumina HiSeq X platform. The LBC1921 are a relatively healthy cohort of 550 individuals who underwent cognitive and medical testing at a mean age of 79.1 (SD=0.6) years. They have since undergone four further waves of testing, approximately three years apart.

  Study EGAS00001003818

• Multiple esclerosis and mixed microbial infections

  This Project deals with the sequencing of ITS1 region, which is highly variable both in length and in nucleotide sequence for different yeast using yeast-specific primers ITS1 and ITS2. A total of 19 samples involving different brain regions from patients with different conditions were analysed. Of these, 10 are controls-healthy patients and 9 multiple sclerosis (MS) patients.

  Study EGAS00001002957

• Genomic landscape of signals of positive natural selection in North Eurasia

  We searched for the genomic signatures of positive selection in the genome-wide data of 432 people from eight different northern Russian populations (Russians from the Archangelsky and Vologdsky regions, Izhemski Komi, Priluzski Komi, Veps, Khanty, Mansi and Nenets) who were genotyped using microarrays for 700,000 SNPs (InfiniumOmniExpress-24v1-2_A1) through testing the extended haplotype homozigosity (EHH).

  Study EGAS00001003955

• Lothian Birth Cohort 1936 whole genome sequencing study

  1075 members of the Lothian Birth Cohort 1936 (LBC1936) were sequenced using the Illumina HiSeq X platform. The LBC1936 are a relatively healthy cohort of 1091 individuals who underwent cognitive and medical testing at a mean age of 69.5 (SD=0.8) years. They have since undergone four further waves of testing, approximately three years apart.

  Study EGAS00001003819

• Evolutionary analysis of pancreatic neoplastic cysts through whole-exome and targeted sequencing

  Intraductal papillary mucinous neoplasms (IPMNs) and mucinous cystic neoplasms (MCNs) are non-invasive neoplasms that are often observed in association with invasive pancreatic cancers, but their origins and evolutionary relationships are poorly understood. In this study, we analyzed 148 samples from IPMNs, MCNs, and small associated invasive carcinomas from 18 patients using whole exome or targeted sequencing.

  Study EGAS00001004473

• Finding structural variation and functional consequences from the primary leukemia cells (CLL) at the single-cell level

  In this study, we aimed to identify somatic structural variation of chronic lymphocytic leukemia (CLL) at the single-cell level and investigate its direct consequence on the nucleosome occupancy using scNOVA approach. For this purpose, we performed strand-specific single-cell sequencing of primary leukemia samples from 63-year-old female patient.

  Study EGAS00001004925

• COVID-19 GWAS in Japanese

  The Japan COVID-19 Task Force (JCTF) was established in early 2020 as a nation-wide multicenter consortium to overcome the COVID-19 pandemic in Japan. We conducted a genome-wide association study (GWAS) involving 2,393 Japanese COVID-19 cases collected in initial pandemic waves with 3,289 controls. GWAS genotyping was performed using Infinium Asian Screening Array (Illumina, USA).

  Study EGAS00001006284

• Polymorphisms in the Mitochondrial Genome associated with Bullous Pemphigoid in Germans

  This study is the first to interrogate the whole mtDNA in BP patients and controls and to implicate multiple novel mtDNA variants in disease susceptibility. Whole mtDNA of German BP patients (n=180) and age- and sex-matched healthy controls (n=188) were sequenced using next generation sequencing (NGS) technology, followed by the replication study using Sanger sequencing of an additional independent BP (n=89) and control cohort (n=104). While the BP and control groups showed comparable mitochondrial haplogroup distributions, the haplogroup T exhibited a tendency of higher frequency in BP patients suffering from neurodegenerative diseases (ND) compared to BP patients without ND (p= 0.1448, Fisher’s exact test)

  Dataset EGAD00001005379

• Mutational analysis of an oligoprogressive sarcomatoid hepatocellular carcinoma treated with an immune checkpoint inhibitor.

  The dataset is composed of three sequenced tumor samples: (I) Meta-bone-557 (bone metastasis obtained from occipital lesion resection during treatment with Liposomal doxorubicin); (II) Meta-CNS-888 (brain metastasis obtained from surgical resection during treatment with Nivolumab); (III) Primary-liver-463 (primary hepatic tumor obtained from surgical resection during treatment with Nivolumab). Genomic DNA from tumor samples was extracted using GeneRead DNA FFPE kit (Qiagen), containing Uracyl-D Glycosylase, according to the manufacturer’s instructions. Whole-exome libraries were prepared using SureSelect XT Clinical Research Exome Target Enrichment kit (Agilent Technologies # 5190-7338). Sequences (150bp paired-end) were generated on a NextSeq 500 sequencing platform (Illumina).

  Dataset EGAD00001006982

• Whole genome sequencing of acute erythroid erythroid leukemia

  Briefly, twenty paired tumor and germline DNAs were extracted from patients’ BM and from buccal mucosa, respectively. Samples were subjected to massively parallel sequencing using the HiSeq 2000, HiSeq2500, HiSeq X Ten, and/or NovaSeq 6000 according to the manufacturer’s instructions. Sequencing reads were aligned to NCBI Human Reference Genome Build 37 (hg19) by Burrows−Wheeler Aligner, version 0.7.10, with default parameters (http://bio-bwa.sourceforge.net/). PCR duplicates were eliminated using Picard tools version 1.39 (GATK).

  Dataset EGAD00001008357

• Somatic mutations predict an aggressive phenotype in meningioma but do not drive grade progression

  A subset of meningiomas progress in histopathological grade and drivers of progression are poorly understood. We aimed to identify somatic mutations and copy number alterations (CNAs) associated with grade progression in a unique matched tumour dataset. This dataset consists of DNA sequencing from 10 individuals with meningiomas, where the meningiomas have underdone grade progression. 50 meningiomas were sequenced from the 10 individuals using the hybrid capture-based TruSight Oncology 500 (TSO500) Library Preparation Kit, and 13 of those meningiomas were also sequenced using Agilent SureSelect Clinical Research Exome V2. BAM files for the sequencing data are included in the dataset.

  Dataset EGAD00001009391

• C9orf72 region reads of 3001 samples

  This dataset includes cram files from 3,001 samples. These cram files include all read pairs where at least one of the reads aligns within 1kb of the C9orf72 repeat expansion. Additionally, these cram files also contain reads that are aligned to any of 29 pre-determined off target locations where the aligners are known to mis-align reads associated with this repeat expansion. These samples were sequenced using a combination of 2x100bp reads on an Illumina HiSeq2000 and 2x150bp reads on an Illumina HiSeqX sequencer and aligned using the Isaac aligner.

  Dataset EGAD00001004834

• Genetic background for cardio vascular disorders in the general Finnish population

  Low coverage (4-6x) sequencing on samples from population cohorts (Finrisk, Health2000) will be done at Wellcome Trust Sanger Institute (WTSI) using Illumina HiSeq sequencing technology. We will produce 100bp paired end reads. Variants will be called using the 1000 Genomes Project pipeline. The samples have been selected from a national representative set of approximately 30,300 samples and comprises 500 individuals of each gender in the extreme tail of high density lipoprotein (HDL) concentrations. Included individuals were between 25 and 65 years of age. Individuals with a diagnosis of diabetes or BMI&gt;30 were excluded from the study.

  Dataset EGAD00001001251

• LCM_WES__Thyroid_

  Whole exome sequencing through the low-input DNA pipeline in thyroid samples. Tissue will be processed either from laser capture microdissection or directly from bulk frozen/fixed/paraffin-embedded tissue. Insights will be gained here directly from the sequencing but also from using the data as a matched normal in Exome Nanoseq. Thyroid samples will be obtained from patients with and without thyroid disease.

  Study EGAS00001007772

• Long read mRNA sequencing of human neural retinal samples

  Long-read (PacBio) RNA sequencing dataset of three neural retinal samples. Files are raw BAM format files generated by a Sequel II machine. Additionally, the ccs3 BAM format files are included.

  Dataset EGAD50000000101

• Transcriptomic sequencing of early and late passage of mCRC tumoroids

  Dataset of 46 mCRC tumoroids from different passages (23 early-passage 3, 23 late-passage 8-12). FASTQ files of paired sequencing of PolyA-enriched total RNA

  Dataset EGAD50000000153

• RNAseq of samples from CLL patients treated with idelalisib in vivo

  The dataset contains RNA sequencing data from 18 paired samples of 9 CLL patients treated with idelalisib in vivo (median time on therapy 4 weeks; range 2-5 weeks).

  Dataset EGAD50000000878

• Single-cell genotype-to-phenotype (scG2P) of normal esophageal epithelium

  Single-cell genotype-to-phenotype (scG2P) of normal esophageal epithelium, based on targeted DNA genotyping of mutation hot spots and targeted RNA capture.

  Dataset EGAD50000002066

• single cell RNAseq data of lung adenocarcinoma

  Single-cell RNA sequencing was performed for cells from five early-stage LUADs and fourteen multi-region normal lung tissues of defined spatial proximities from the tumors.

  Dataset EGAD00001006936

• Hospital for Sick Children 2020 Pediatric Low-Grade Glioma RNA and Targeted DNA Sequencing

  Whole transcriptome and targeted dna sequencing (Ampliseq) of pediatric low-grade glioma samples at the Hospital for Sick Children

  Dataset EGAD00001005987

• Whole-exome sequencing and microRNA profiling predicted relapse risk of stage I lung adenocarcinomas

  This dataset contains BAM files for RNA-sequencing of stage I lung adenocarcinomas from Asian patients. In total, there are 107 patients and 107 tumor samples.

  Dataset EGAD00001006187

• anti-SARS-CoV-2 IgG and Fostamatinib treated human primary IL10-M2 macrophages

  RNA sequencing data of anti-SARS-CoV-2 spike IgG (monoclonal or patient serum), poly(I:C) and Fostamatinib treated human primary IL10-M2 macrophages

  Dataset EGAD00001007512

• Human tumor single-cell mutiome

  We profiled 1 patient neuroblastoma-FOXR2 tumor sample by single-cell multiome RNA + ATAC. The raw fastqs are provided.

  Dataset EGAD00001010902

• m6A profiling in Lung Adenocarcinoma

  Applying a refined m6A RNA immunoprecipitation method, we profiled the m6A epitranscriptome on 10 non-neoplastic lung (NL) tissues and 53 lung adenocarcinoma tumors.

  Dataset EGAD00001008026

• Dr. Fatima Mechta-Grigoriou, PhD, DR1 Head of Stress and Cancer Laboratory Deputy Director Genetic and Biology of Cancer Dpt Institut Curie - Inserm U830

  Dac EGAC00001000581

• ICGC prostate cancer whole genome sequencing

  ICGC prostate cancer whole genome sequencing

  Dataset EGAD00001000306

• Converging and evolving immuno-genomic routes towards immune escape in breast cancer

  Data access committe for the project: Converging and evolving immuno-genomic routes towards immune escape in breast cancer

  Dac EGAC50000000074

• Thoracic Patient-Derived Xenografts

  Targeted capture sequencing of 341 cancer associated genes in thoracic patient-derived xenografts.

  Study phs001192

• scRNAseq of ovarian cancer patient derived organoids

  scRNAseq of ovarian cancer patient derived organoids with or without estradiol

  Dataset EGAD50000002058

• Single_cell_RNA_sequencing_of_rhabdomyosarcoma_tumouroids

  The aim of this study is to investigate the genomic landscape of human cancer.

  Study EGAS00001008273

• Single_cell_RNA_sequencing_of_rhabdomyosarcoma_tumour_tissue

  The aim of this study is to investigate the genomic landscape of human cancer.

  Study EGAS00001008275

• Whole exome sequencing of 103 pairs BLCA-CN

  We sequenced 50M exomes of 103 pairs bladder cancer of chinese

  Study EGAS00001000677

• Single_cell_ATAC_sequencing_of_rhabdomyosarcoma_tumour_tissue

  The aim of this study is to investigate the genomic landscape of human cancer.

  Study EGAS00001008276

• Genentech gallbladder cancer study - whole genome sequencing

  Genentech gallbladder cancer study - whole genome sequencing

  Dataset EGAD00001004855

• Plasma methylome of metastatic prostate cancer

  The dataset contains plasma DNA methylation data derived from metastatic prostate cancer patients.

  Dataset EGAD00001005433

• 65 prostate cancer cases wgs sequencing

  65 prostate cancer cases wgs sequencing

  Dataset EGAD00001000983

• 65 prostate cancer cases wgs sequencing

  65 prostate cancer cases wgs sequencing

  Dataset EGAD00001001004

• Premalignant SOX2 in ovarian cancer patients

  Whole Genome Sequencing data set for the study "Premalignant SOX2 in ovarian cancer patients"

  Dataset EGAD00001002734

• CALGB 80303:Genome-Wide Association Study of Advanced Pancreatic Cancer Patients - A Randomized Phase III trial of Gemcitabine Plus Bevacizumab versus Gemcitabine Plus Placebo in Patients with Advanced Pancreatic Cancer

  CALGB 80303 was a randomized, phase III study in advanced pancreatic cancer patients treated with Gemcitabine plus either Bevacizumab or placebo. No difference in overall survival (OS) was observed between the two arms. We prospectively collected germline DNA and conducted a genome-wide association study (GWAS).

  Study phs000250

• CAGEKID: Cancer Genomics of the Kidney

  The aim of CAGEKID is to carry out comprehensive detection of DNA markers for conventional (clear cell) renal carcinoma. The project includes complete analysis of somatic and constitutional DNA variation, methylation patterns and expression in a large number of constitutional/tumor pairs. CAGEKID is a part of the International Cancer Genome Consortium, ICGC.

  Study EGAS00001000083

• Identification of drug resistance genes in cancer cell lines by insertional mutagenesis

  Our aim is to identify genes involved in resistance to anti-cancer therapies. In order to do this we have taken advantage of a lentiviral vector (LV)-based insertional mutagen to mutagenize cancer cell lines. LV-transduced cell lines were then treated with anti-cancer therapies and the emergence of resistant clones scored. DNA from pools of resistant clones was collected, subjected to custom capture by baits designed against the LV sequence, and then sequenced to identify the LV-genomic junction. We hope that the identification of recurrently targeted genes in resistant cell population will allow us to identify genes that mediate drug resistance.

  Dataset EGAD00001002207

• AVENIO Expanded ctDNA panel sequence alignments (BAMs) from plasma DNA of BC, CRC and NSCLC patients

  The AVENIO ctDNA Expanded Kit is a next-generation sequencing (NGS) liquid biopsy assay with a 77 gene panel (192 kb) containing genes in U.S. National Comprehensive Cancer Network (NCCN) Guidelines and emerging cancer biomarkers. This pan-cancer assay was applied to 48 plasma samples from patients with breast, colorectal and non-small cell lung cancer. After sequencing 150bp paired-end, reads were aligned to the hg38 genome with the AVENIO Oncology Analysis Software (version 2.0). These files are the deduplicated alignments generated by the analysis software used for subsequent variant, indel and CNV calling.

  Dataset EGAD00001006301

• EGAD00010000634

  WTCCC2 People of the British Isles (POBI) samples using Affymetrix 6.0 array

  Dataset EGAD00010000634

• Oncotrack_450K_tumor

  Oncotrack primary tumor samples using 450K. The dataset includes shared AF analysis files oncotrackDNAmAnalysis.R and oncotrackDNAmBetaScores.txt which were applied for both Oncotrack_450K_tumor (EGAD00010001162) and Oncotrack_450K_metastatic (EGAD00010001161) datasets.

  Dataset EGAD00010001162

• Whole Genome Sequencing of tissues

  Whole genome sequencing profiling of 4 primary PDAC tissue samples - WGS unmapped reads, sequenced using NovaSeq 6000, 15x coverage 160 million reads per sample.

  Dataset EGAD50000000279

• AVENIO mutation analysis

  Mutation analysis in cfDNA from plasma and urine (stored under different storage conditions) from CRC patients using the AVENIO Expanded Kit

  Dataset EGAD50000001588

• 10K Project Metagenomic

  This dataset includes metagenomic sequencing of faecal samples from 7,190 Israeli individuals. Single-end sequencing was performed using a NovaSeq sequencing platform (Illumina).

  Dataset EGAD00001010925

• Somatic SNVs and Indels for INSPIRE Tumor WES

  Somatic SNVs and Indels for INSPIRE Tumor WES called using Mutect, Mutect2, Varscan2, Vardict, and Strelka2

  Dataset EGAD00001006569