6938 results for "fc coins xbox one Buyfc26coins.com is FC 26 coins official site..hLXt"

in 14.69 milliseconds.

• High-coverage whole exome sequence in non-TRU-type lung adenocarcinomas

  In order to elucidate the key genetic events in non-TRU-type lung cancer, we selected 43 non-TRU-type lung adenocarcinomas and performed a whole exome sequence and RNA-seq analysis using a next-generation sequencer. The results of the analysis identified mutations in TP53, KRAS and NKX2-1 as the top three significantly mutated genes, while the EGFR mutation was rare in this cohort. Eight NKX2-1 mutations (5 frameshift, 2 nonsense, and one missense) were identified, with one case harboring two distinct NKX2-1 mutations (missense and frameshift). All NKX2-1 mutants were transcriptionally inactive in reporter assays. Histologically, invasive mucinous adenocarcinomas accounted for most of the NKX2-1 mutations (5 cases), while 1 enteric and 1 acinar adenocarcinoma harbored the NKX2-1 mutation.

  Study JGAS000105

• Gliomas, glioneuronal and neuronal tumors

  The dataset represents a total of 85 DNA samples from 22 male and 20 female pediatric patients affected with gliomas, glioneuronal, and neuronal tumors. The samples were subject to whole genome sequencing, WGS, [71 samples, (representing 18 male and 17 female individuals)] and whole exome sequencing, WES, [14 samples, (representing 4 males and 3 female individuals)]. One tumor tissue sample and one peripheral blood sample were analyzed from each of 84 patients, whereas two tumor tissue samples and one peripheral blood sample were analyzed from one patient. The WGS samples were sequenced 2x150 bp paired-end on an Illumina HiSeqX v2.5 instrument, and the WES samples were sequenced 2x100 bp paired-end on an Illumina HiSeq 2500 instrument. The FASTQ files generated were aligned to the human reference genome sequence GRCh38/hg38 using bwa-mem, with the ALT-aware option turned on. Sorting of reads and marking of PCR duplicates was performed with GATK. Base quality score recalibration and joint realignment of reads around insertions and deletions (indels) were conducted using GATK tools. The dataset consists of 85 files in the CRAM format (lossless compression) with a total file size of ~13,3 TB. Additional genomic and molecular data (FASTQ, BAM, IDAT, and VCF files) and limited clinical data can be requested by ethically approved projects conducting research in the field of pediatric cancer.

  Dataset EGAD50000000300

• Synthetic data - Genome in a Bottle

  In May, the National Institute of Standards and Technology (NIST) released its first genome in a bottle, a reference sample of DNA for validating human genome sequences. This so-called truth sequence comes from a decades-old sample donated by a Utah woman for (other) research purposes (NA12878 cell line), which, over the years, has been one of the most studied, and hence best-characterized, human samples. Seeing genomic medicine moving toward mainstream healthcare, researchers at NIST recognized the need for a reference human genome and assembled a private-public consortium in 2012 to create one. As detailed in a 2014 Nature Biotechnology paper (Nat. Biotechnol.32, 246–251, 2014), the group integrated and arbitrated among sequences from 14 data sets, five sequencing technologies, seven read mappers and three variant callers.

  Study EGAS00001005591

• 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

• RNA-Seq in Patients with Primordial Dwarfism

  Transcriptome studies in patients with rare genetic diseases can potentially aid in the interpretation of likely causal genetic variation through identification of altered transcript abundance and/or structure. RNA-Seq is the most sensitive assay for both investigating transcript structure and abundance The primary aim of this pilot project is to investigate to what degree integrating exome-Seq and RNA-Seq data on the same individual can accelerate the identification of causal alleles for rare genetic diseases. There are two main strands to this: (i) identifying which variants discovered in exome-seq appear to be having a functional impact on transcripts, and (ii) identifying transcript outliers, especially among known causal genes, that may not necessarily have a causal variant identified from exome sequencing. The latter may identify the presence of causal variants that lie far from coding regions (e.g. the formation of cryptic splice sites deep within introns, or loss of long range regulatory elements), which can be confirmed with further targeted genetic assays. Just over 50% of all disease-causing variants recorded in the Human Gene Mutation Database (HGMD) affect transcript structure and abundance (e.g. nonsense SNVs, essential splice site SNVs, frameshifting indels, CNVs). This pilot project will study RNA from lymphoblastoid cell-lines from 12 patients with primordial dwarfism syndromes, for 10 of these samples we have previously generate exome data as part of our collaboration with the group of Prof Andrew Jackson. The two remaining samples are positive controls where the causal mutation is known, and is known to affect transcript structure and/or abundance. Primordial dwarfism is a prime candidate for these RNA-seq studies because all known causal mutations to date have key roles in DNA replication and thus, unsurprisingly, the products of the causal genes are typically ubiquitously expressed. Each RNA will be sequenced, with two technical replicates (independent RT-PCR and libraries) per sample, and each replicate run in 1/2 of a HiSeq lane using 100bp paired reads. Samples preparation was as follows :The cells were grown to confluency, then pellets frozen at -80. RNA samples were prepared using the Qiagen RNeasy kit, then nanodropped and analyzed using the bioanalyzer to determine concentration and purity. This data is part of a pre-publication release. For information on the proper use of pre-publication data shared by the Wellcome Trust Sanger Institute (including details of any publication moratoria), please see http://www.sanger.ac.uk/datasharing/

  Dataset EGAD00001000640

• Alzheimer's Disease Sequencing Project (ADSP)

  NOTICE OF CHANGE IN LOCATION FOR ALZHEIMER&#39;S DISEASE SEQUENCING PROJECT (ADSP) GENETIC AND PHENOTYPIC DATA: ADSP whole exome and whole genome sequence data that are shared through dbGaP were mapped to the Genome Reference Consortium human genome GRCh37 (build 37). These data are from the Discovery Phase of the project (described below) and will continue to be available at this site. Please see the ADSP Design page for the complete study description. All data that are mapped to GRCh38 (hg38) are being shared through the NIA Genetics of Alzheimer&#39;s Disease Data Storage Site (NIAGADS) Data Sharing Service (DSS). For instructions on how access the ADSP Build 38 data that are shared through NIAGADS DSS, visit the Application Instructions page. STUDY DESCRIPTION FOR dbGaP BUILD 37 ADSP DATA: The overarching goals of the Alzheimer&#39;s Disease Sequencing Project (ADSP) are to: (1) identify new genomic variants contributing to increased risk of developing Alzheimer&#39;s Disease (AD), (2) identify new genomic variants contributing to protection against developing AD, and (3) provide insight as to why individuals with known risk factor variants escape from developing AD. These factors will be studied in multi-ethnic populations in order to identify new pathways for disease prevention. Such a study of human genomic variation and its relationship to health and disease requires examination of a large number of study participants and needs to capture information about common and rare variants (both single nucleotide and copy number) in well phenotyped individuals. Using existing samples from NIH funded and other studies, three NHGRI funded Large Scale Sequencing and Analysis Centers (LSAC) - Broad, Baylor, and Washington University - produced the DNA sequence data. Variant call data are being made available to the scientific community through NIH-approved data repositories. Statistical analysis of the sequence data is anticipated to identify new genetic risk and protective factors. The ADSP will conduct and facilitate analysis of sequence data to extend previous discoveries that may ultimately result in new directions for AD therapeutics. Analysis of ADSP data will be done in two phases. The Discovery Phase analysis (2014-2018) is funded under PAR-12-183. The entire Discovery dataset contains whole-genome sequencing data on 584 subjects from 113 families, and pedigree data for &#62; 4000 subjects; whole exome sequencing data on 5096 cases 4965 controls; and whole exome sequence data on an additional 853 (682 Cases [510 Non-Hispanic, 172 Hispanic]), and 171 Hispanic Control subjects from families that are multiply affected with AD. The Replication Phase (2016-2021) analysis will be funded under RFA-AG-16-001 and RFA-AG-16-002 and is expected to include a combination of genotyping and sequencing approaches on at least 30,000 subjects. Targeted sequencing will be done by the LSACs. GRCh37 Data Releases The first ADSP data release occurred on November 25, 2013. It included the whole-genome sequencing data in BAM file format on 410 individuals. The second ADSP data release occurred on March 31, 2014, and included the whole-genome sequencing data in BAM file format for an additional 168 individuals. The third ADSP data release occurred on November 03, 2014 and included whole-exome sequencing data in BAM file format for 10,939 individuals. The fourth ADSP data release occurred on February 13, 2015 and included revised ethnic data for subjects with whole-exome sequencing data. The fifth ADSP data release occurred on July 13, 2015 and included whole-genome genotypes and updated phenotypes as well as changes to pedigree structures and sample IDs. The sixth ADSP data release occurred on December 8, 2015, and included whole-exome genotypes and updated phenotypes as well as changes to subject IDs. This seventh ADSP data release on April 12, 2016 includes: (1) WES and WGS SNV VCF files (2) WES and WGS Indel PLINK files ADSP Data Available through dbGaP: ADSP - Whole Genome Sequencing ADSP - Whole Exome Sequencing Comments DNA-Seq (BAM) n=578 n=10913 Sequence data available (plus n=38 replications w/out genotype data) Concordant SNV Genotypes (PLINK format) N/A n=10913 QC&#39;ed genotypes that are concordant between the Atlas (Baylor&#39;s) and GATK (Broad&#39;s) calling pipelines (a subset of the consensus genotype set) Consensus Genotypes (PLINK and VCF format) n=578 n=10913 QC&#39;ed genotypes that are concordant between Atlas and GATK pipelines as well as those that that were called uniquely by Atlas or GATK Concordant Indel Genotypes (PLINK format) n=578 n=10913 QC&#39;ed genotypes that are concordant between the Atlas and GATK calling pipelines Phenotype Data n=4735 n=10913 Data of n=53 phenotype variables available (plus administrative data), including APOE genotype. WGS phenotypes include data of connecting family members. Please use the release notes provided by dbGaP to obtain detailed information about study release updates. The ADSP data portal provides a customized interface for users to quickly identify and retrieve files by covariates, phenotypes, and data properties such as sequencing facility or coverage. For more information about the ADSP study and the data portal, please visit https://www.niagads.org/adsp/.

  Study phs000572

• Whole Exome Sequencing of Calcitonin Producing Pancreatic Neuroendocrine Neoplasms (CT-pNENs) Indicates a Unique Molecular Signature

  Calcitonin-producing pancreatic neuroendocrine neoplasms (CT-pNENs), which can mimic clinical and laboratory features of medullary thyroid carcinoma, are an extremely rare clinical entity with approximately 60 cases reported worldwide. The molecular profile of CT-pNENs is not yet known. Whole-exome sequencing (WES) was performed on tumor and corresponding serum samples of five patients with increased calcitonin serum levels and histologically proven calcitonin-positive CT-pNENs. cBioPortal analysis and gene enrichment analysis with DAVID were performed to validate candidate genes. Immunohistochemistry was used to detect protein expression of MUC4 and MUC16 in CT-pNEN specimens. Common somatic mutations of pNENs like MEN1, ATRX and PIK3CA were identified in cases of CT-pNENs. New somatic SNVs in ATP4A, HES4, and CAV3 have not yet been described in CT-pNENs. Pathogenic germline mutations in FGFR4 and DPYD were found in three of five cases. Mutations of CALCA (calcitonin) and the corresponding receptor CALCAR were found in all five tumor samples, but none of them resulted in clinical or protein sequelae. All five tumor cases showed single nucleotide variations (SNVs) in MUC4, and four cases showed SNVs in MUC16, both of which were membrane-bound mucins. Immunohistochemistry showed protein expression of MUC4 and MUC16 in one case each, and the liver metastasis of a third case was double positive for MUC4 and MUC16. The homologous recombination deficiency (HRD) score of all tumors was low.CT-pNENs have a unique molecular signature compared to other pNEN subtypes, specifically involving the FGFR4, DPYD, MUC4, MUC16 and the KRT family genes. However, these WES data from only five cases must be interpreted with caution because causal interpretation of the mutational landscape in CT-pNENs is difficult. Further research is needed to explain differences in pathogenesis compared with other pNENs. In particular, multi-omics data such as RNASeq, methylation, and whole genome sequencing could be informative.

  Study phs003060

• Metagenomic Analysis to Identify Novel Infectious Agents in Systemic Anaplastic Large Cell Lymphoma

  Anaplastic large cell lymphoma (ALCL) is a rare T-cell non-Hodgkin lymphoma (NHL). Risk of systemic ALCL is markedly increased among immunosuppressed people, such as those with human immunodeficiency virus (HIV) infection or solid organ transplant recipients. This increased risk in immunosuppressed populations suggests a viral etiology, given similar elevations for diffuse large B-cell lymphoma (DLBCL), Burkitt lymphoma, and Hodgkin lymphoma (caused by Epstein-Barr virus [EBV]) and other virus-related cancers in immunosuppressed individuals. EBV might be a plausible candidate, but most reported ALCL tumors are EBV-negative. Therefore, we conducted a metagenomic analysis of microbial associations with ALCL to determine whether a known or novel pathogen is associated with the tumor. We obtained archived formal fixed paraffin embedded (FFPE) ALCL tumor tissue from the Iowa cancer registry and an additional case from an immunosuppressed individual infected with human immunodeficiency virus. Controls included 3 diffuse large B-cell lymphomas (DLBCLs) in transplant recipients (shown to be related to Epstein-Barr virus [EBV] by in situ hybridization) and 3 breast cancers (no known viral etiology). RNA was extracted from FFPE specimens, and total RNA libraries were prepared using the KAPA RNA HyperPrep Kit (Roche). Five samples (IA01, IA53, IA57, IA07, and IA17) were sequenced on a NextSeq 500 (Illumina) and the remainder on a NovSeq 6000 (Illumina). Using novel computational approaches, we eliminated human reads and aligned residual non-human reads to known microbial references using GATK-PathSeq or conducted de novo assembly of unassigned reads using virID pipeline. Although EBV was detected in the 3 DLBCL controls, we did not detect EBV or any novel pathogen in ALCL tumors or in the breast cancers. Our study had a modest sample size and only one case arising in HIV-infected individual. Therefore, further studies are required to characterize the metagenome of systemic ALCLs, especially cases arising in immunosuppressed people.

  Study phs002064

• National Institute on Aging - Late Onset Alzheimer's Disease Family Study: Genome-Wide Association Study for Susceptibility Loci

  Alzheimer disease is the most common neurodegenerative disorder of the elderly affecting an estimated five million Americans. Genetic factors contribute to the risk for disease with heritability estimates ranging from 57% to 79%. More than a decade ago, the &#949;4 variant of APOE was identified and remains the most consistently replicated genetic variant influencing the risk of late onset Alzheimer disease. A segregation analysis suggests there may be four additional genes influencing the age-at-onset of Alzheimer disease. In 2007 there were 968 association studies in 398 candidate genes reported, but none replicated consistently. There are many reasons for the lack of consistency, but one important reason for the lack of progress is the paucity of a sufficient number of well characterized families and patients available to the entire scientific community. The extensive effort and expense required to ascertain such a population has been addressed by the NIA-LOAD Family Study. Its goal is to identify and recruit families with two or more siblings with the late-onset form of Alzheimer&#39;s disease and a cohort of unrelated, non-demented controls similar in age and ethnic background, and to make the samples, the clinical and genotyping data and preliminary analyses available to qualified investigators world-wide. Genotyping by the Center for Inherited Disease Research (CIDR) was performed using the Illumina Infinium II assay protocol with hybridization to Illumina Human 610Quadv1_B Beadchips. This genotyping represents the largest collection of families ever assembled with Alzheimer&#39;s disease combining the NIA-LOAD Genetics Initiative Multiplex Family Study, the National Cell Repository for Alzheimer&#39;s Disease (NCRAD) with additional controls from the University of Kentucky. These genotyping results will serve as a focal point for future research that will identify all of the remaining genetic variants in Alzheimer&#39;s disease.

  Study phs000168

• Gene Environment Association Studies (GENEVA): Genetics of Early Onset Stroke (GEOS) Study

  The Genetics of Early Onset Stroke (GEOS) Study is a population-based case-control study designed to identify genes associated with early-onset ischemic stroke and to characterize interactions of identified stroke genes and/or SNPs with environmental risk factors such as smoking and oral contraceptive use. The GEOS study consists of 921 ischemic stroke cases with age of first stroke 16-50 years and a similar number of controls, identified from the Baltimore-Washington area. Cases and controls were recruited in 3 different time periods: Stroke Prevention in Young Women-1 (SPYW-1) conducted from 1992-1996, Stroke Prevention in Young Women-2 (SPYW-2) conducted from 2001-2003, and Stroke Prevention in Young Men (SPYM) conducted from 2003-2007. The overall GEOS sample includes 477 cases who self-reported their race as "white" and 396 cases who self-reported their race as "African American." Traditional stroke risk factors and other study variables, including age, ethnicity, and history of hypertension, diabetes, myocardial infarction (MI), current smoking status, and current oral contraceptive use (both defined as use within one month prior to event for cases and at a comparable reference time for controls), were also collected during standardized interview and were included as covariates in our analyses. This study is part of the Gene Environment Association Studies initiative (GENEVA, http://www.genevastudy.org) funded by the trans-NIH Genes, Environment, and Health Initiative (GEI). The overarching goal is to identify novel genetic factors that contribute to early-onset ischemic stroke through large-scale genome-wide association studies of cases and controls of European and African descent from the Baltimore-Washington area. Genotyping was performed at the Johns Hopkins University Center for Inherited Disease Research (CIDR). Data cleaning and harmonization were done at the GEI-funded GENEVA Coordinating Center at the University of Washington.

  Study phs000292