72 results for ""developer+diary"+"autumn"+game+'developer+diary'+'autumn'+'download'"

in 6.03 milliseconds.

• Submitters and requesters Statistics

  EGA Statistics Bibliography Growth Community Archive Distribution Catalogue Here, we show the amount and global distribution of submitters and requesters Requester accounts created by country The below figure represents the number of requester accounts by country. In most of the cases cases, country was inferred from the requester email domain. Those requesters whose email domain could not be assigned to a country such as @gmail.com, are not included. Note that a requester is a user that has had a granted permission at some point in time. Requester Accounts Created by Country Download as PNG Download as JPG Download as WEBP Download as CSV map pie mapChart('requester-country', 'https://stats.ega-archive.org/requester/country') pieChart('requester-country-pie-chart', 'https://stats.ega-archive.org/requester/country','Requester accounts created by country') Requester accounts created by year The below figure represents the number of requester accounts by year. Note that a requester is a user that has had a granted permission at some point in time. Requester Accounts Created by Year Download as PNG Download as JPG Download as WEBP Download as CSV barChart('requester-year', 'https://stats.ega-archive.org/requester/year', ['Requester Accounts', 'Years'], true) Industry requester accounts The below figure represents the top 15 industry requesting companies. Industry Requester Accounts Download as PNG Download as JPG Download as WEBP Download as CSV pieChart('industry-requester-accounts', 'https://stats.ega-archive.org/industry/requester/accounts', 'Industry Requester Accounts') Submitter accounts created by country The below figure represents the number of submitter accounts by country. Location was infered from the requester email domain. Submitter Accounts Created by Country Download as PNG Download as JPG Download as WEBP Download as CSV map pie mapChart('submitter-accounts', 'https://stats.ega-archive.org/submitter/accounts/country') pieChart('submitter-accounts-pie-chart', 'https://stats.ega-archive.org/submitter/accounts/country','Submitter accounts created by country') Submitter accounts created by year The below figure represents the number of submitter accounts by year. Submitter Accounts Created by Year Download as PNG Download as JPG Download as WEBP Download as CSV barChart('submitter-users-year', 'https://stats.ega-archive.org/submitter/users/year', ['Submitter Accounts', 'Years'], true) DAC Members by Country The below figure represents the number of DAC members by country. DAC Members by Country Download as PNG Download as JPG Download as WEBP Download as CSV map pie mapChart('dac-members-by-country', 'https://stats.ega-archive.org/dac_member/country') pieChart('dac-members-by-country-pie-chart', 'https://stats.ega-archive.org/dac_member/country','DAC members by country')

  Documentation about/statistics/community

• PyEGA3 download client

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

  Documentation access/download/files/pyega3

• OncoArray: Follow-up of Ovarian Cancer Genetic Association and Interaction Studies (FOCI)

  The Follow-up of Ovarian Cancer Genetic Association and Interaction Studies (FOCI) was one of five projects funded in 2010 as part of the NCI's Genetic Associations and Mechanisms in Oncology (GAME-ON) initiative (http://epi.grants.cancer.gov/gameon/). FOCI represents a collective effort that builds upon the strengths and history of collaboration inherent in the Ovarian Cancer Association Consortium (OCAC), a multidisciplinary group comprised of epidemiologists, genetic epidemiologists, statistical geneticists, molecular and cell biologists and clinicians that was formed in 2005. The other four funded GAME-ON projects were: the ColoRectal TransdisciplinaryStudy (CORECT), Elucidating Loci Involved in Prostate Cancer Susceptibility (ELLIPSE), Discovery, Biology, and Risk of Inherited Variants in Breast Cancer (DRIVE), and Transdisciplinary Research in Cancer of the Lung (TRICL). As part of our aim to discover, expand, and replicate ovarian cancer susceptibility loci, the GAME-ON projects and other consortia formed the OncoArray network (http://epi.grants.cancer.gov/oncoarray/) to develop and genotype a new custom genotyping array in large numbers of cancer cases and controls (over 400,000 samples) across multiple cancer types. The FOCI data includes over 50,000 ovarian cancer cases and controls genotyped with the Oncoarray at the Center for Inherited Disease Research (CIDR). Genotype calling and quality control procedures were performed under a standardized protocol across the Oncoarray consortium, and over 490,000 SNPs passed QC and are included under this dbGaP submission.

  Study phs001882

• Discovery, Biology, and Risk of Inherited Variants in Breast Cancer (DRIVE) - OncoArray Genotypes

  Discovery, Biology, and Risk of Inherited Variants in Breast Cancer (DRIVE) was one of five projects funded in 2010 as part of the NCI's Genetic Associations and Mechanisms in Oncology (GAME-ON) initiative (http://epi.grants.cancer.gov/gameon/). GAME-ON's overall goal was to foster an intra-disciplinary and collaborative approach to the translation of promising research leads deriving from the initial wave of cancer GWAS. Specific goals included replication of previous GWAS findings and identification of new susceptibility loci through meta analyses of existing GWAS data and fine mapping of identified loci to better pinpoint causal variants; and identify germline variants that are associated with risk of multiple cancers. The other four funded GAME-ON projects were: the ColoRectal TransdisciplinaryStudy (CORECT), Elucidating Loci Involved in Prostate Cancer Susceptibility (ELLIPSE), Follow-up of Ovarian Cancer Genetic Association and Interaction Study (FOCI), and Transdisciplinary Research in Cancer of the Lung (TRICL). To identify additional cancer risk loci, improve the precision of fine-mapping, and facilitate cross-cancer analyses, the GAME-ON projects and other consortia formed the OncoArray network (http://epi.grants.cancer.gov/oncoarray/), which developed and genotyped a new custom genotyping array (the "OncoArray") in large numbers of cancer cases and controls (over 400,000 samples). The OncoArray is a custom array manufactured by Illumina. The array includes a backbone of approximately 260,000 SNPs that provide genome-wide coverage of most common variants, together with markers of interest for each of the five GAME-ON cancers identified through genome-wide association studies (GWAS), fine-mapping of known susceptibility regions, sequencing studies, and other approaches. The array also includes loci of interest identified through studies of other cancer types, and other loci of interest to multiple cancer types (including loci associated with cancer related phenotypes, drug metabolism and radiation response). Additionally, SNPs relating to quantitative phenotypes such as body mass index (BMI), height, and breast density that correlate with common cancer risks are also included. The DRIVE data included under this dbGAP submission include OncoArray data from 60,015 breast cancer cases and controls genotyped at the Center for Inherited Disease Research (CIDR), University of Cambridge, National Cancer Institute, University of Copenhagen, University of Southern California and Mayo Clinic. Details on an additional approx. 80,000 breast cancer cases and controls genotyped at other centers can be found at http://bcac.ccge.medschl.cam.ac.uk/bcacdata/oncoarray/.

  Study phs001265

• Discovery, Biology, and Risk of Inherited Variants in Breast Cancer (DRIVE) - germline whole genome sequencing

  This study consists of whole genome sequencing (target: average 30x coverage) of 110 European-ancestry (EA), early-onset, family-history-positive breast cancer cases, 21 Asian cases, 25 African-American cases, and 24 controls from six studies participating in the Discovery, Biology, and Risk of Inherited Variants in Breast Cancer (DRIVE) consortium, part of the NCI's Genetic Associations and Mechanisms in Oncology (GAME-ON) initiative ( http://epi.grants.cancer.gov/gameon/ )

  Study phs001483

• Data distribution Statistics

  EGA Statistics Bibliography Growth Community Archive Distribution Catalogue Here, we show the amount of data distributed by the EGA. Data Distributed / Live EGA Data Distribution / Live SFTP Aspera HTSGET lineChartLive("svg#ega-dist-live", document.querySelector("#ega-figure-dist-live figcaption")); Data Distributed The below figure represents the cumulative EGA data distribution via the download clients(v2 and v3.x api versions) using HTTPS, FTP, and download boxes using ASPERA. You can see cumulative values by clicking "Cumulative". EGA Data Distribution //lineChart('#ega-data-distribution svg.stats', 'https://stats.ega-archive.org/distribution', // ['Amount of Distributed Data', ['Aspera', 'Download Clients', 'Total']]) curveChart('#ega-data-distribution', [ { domId: 'stats-aspera', label: 'Aspera', url: 'https://stats.ega-archive.org/distribution/aspera' }, { domId: 'stats-sftp' , label: 'SFTP', url: 'https://stats.ega-archive.org/distribution/sftp' }, //{ domId: 'stats-htsget', label: 'HTSGET', url: 'https://stats.ega-archive.org/distribution/htsget' }, { domId: 'stats-streamer' , label: 'Download Client', url: 'https://stats.ega-archive.org/distribution/streamer' }, { domId: 'stats-total' , label: 'Total', url: 'https://stats.ega-archive.org/distribution/total' } ] );

  Documentation about/statistics/distribution

• Using your EGA account

  Using your EGA account The purpose of this page is to help you access and download the data you have been granted permission to view through your EGA account. To obtain an EGA account please register here. Once your account is created, you can find details on how to manage your EGA account here. EGA access policy (New account holders please read) Access to EGA services are only provided to EGA account holders. EGA accounts are created, updated and closed upon direct instruction from the relevant DAC contact, using the EGA account management tools or through EGA Helpdesk. As part of the EGA account creation process, the EGA account holder must reset their password when instructed. Password resets are checked and verified usually within 24 business hours, during which time the EGA account is inaccessible. EGA accounts are assigned on an individual basis for the exclusive use of the registered EGA account holder; log-in details must remain private and only be used by the EGA account holder. Controlled access data files are only provided, in accordance to the permissions set by the DAC, to EGA account holders. EGA controlled access data files are encrypted prior to download and must be decrypted on the EGA account holders side. EGA account holders are provided access to the EGA download streamer to download access approved datasets and files therein. The EGA download streamer represents the primary means for the EGA account holder to download access approved datasets and files therein. EGA account holders may be provided with an EGA download account for accessing approved datasets and files therein, using FTP or Aspera in response to clearly defined technical reasons, which may restrict the use of the EGA download streamer. It is the sole responsibility of the EGA account holder to ensure full compliance to all terms and conditions of the Data Access Agreement are met once data is downloaded from the EGA. Should you move institute you must contact all Data Access Committee's contacts to update your details and, if necessary, re-apply for data access. The Data Access Agreement (DAA) is a contract made between the DAC and the EGA account holder; the EGA is not responsible for enforcing the DAA. EGA reserves the right to place EGA accounts 'onhold', pending DAC approval to re-activate, should EGA account 'misuse' be suspected. Further information Introduction to the EGA Frequently Asked Questions Subscribe to the EGA mailing list

  Documentation download/using_ega_account

• Out with the Java, in with the Python - new EGA data download client unveiled

  We will shortly be deprecating the Java-based download client also known as API V2. The Java client began its life at the back end of 2014, and during its time has seen many developments that have served our users well. During its tenure, the Java client enabled distribution of over 6.5 million files totalling nearly 15 petabytes of data to researchers around the globe. Recent increases in genomic and phenotypic data file sizes, the number of datasets archived in the EGA, the number of users downloading data, and the diversity of download locations has meant that at times the Java client struggled to distribute data efficiently. In response, our team of developers have built a new download client with more robust features and better functionality and reliability. Enter stage left our shiny new API V3.1! The new API V3.1 will replace both API V2 and API V3. The download client for the new API V3.1 is written in Python, and the code is openly available on Github. This Python client makes https calls to the EGA AAI (https://ega.ebi.ac.uk:8443/) and to the EGA Data API (https://ega.ebi.ac.uk:8052), both of which must be accessible from the client location. In addition to general updates to improve performance, the API V3.1 has three new features enhancing the EGA distributions services. First, requested data are now downloaded over secure https connections rather than http, meaning that data can be delivered unencrypted. Instead of separately requesting, downloading, and decrypting data using the Java client, data can now be requested and downloaded using a single command without the need for decrypting. The API V3.1 also automatically verifies each file’s unencrypted md5 after download to ensure the file has downloaded correctly. Second, the new API supports segmenting and automatic resuming. To enable quicker download speeds, the API breaks files into up to four segments and downloads them in parallel. With the new resume feature, downloads - both segmented and continuous stream - will automatically resume if they encounter any errors or the connection is interrupted. These features result in both a faster and more reliable download experience. Finally, the new API V3.1 implements the GA4GH-compliant htsget protocol for supporting requests over genomic ranges. This exciting new feature means that for data files with accompanying index files (e.g. .crai for CRAM files) users can download specific regions of interest rather than the entire file saving both time and storage space. The new features of the Python-based API V3.1 represent significant improvements in security, speed, reliability, and flexibility that are sure to provide a better data download experience. To take full advantage of these features, users must update to Python 3.X. Considering the changes in the data structures with the new API, the upgrade to a new version of the Python client is also mandatory. Updating the client to the latest version can be achieved by running the following command: pip3 install pyega3 -U We are excited for users to try out the new features and take advantage of the multifariously growing EGA distribution services for human biomedical omics data. If you have any questions or feedback, please email the EGA Helpdesk team. We'd love to hear from you!

  Blog new-ega-data-download-client

• Discovery, Biology, and Risk of Inherited Variants in Breast Cancer (DRIVE) - Genome-Wide Association Study Meta-Analysis

  Discovery, Biology, and Risk of Inherited Variants in Breast Cancer (DRIVE) was one of five projects funded in 2010 as part of the NCI's Genetic Associations and Mechanisms in Oncology (GAME-ON) initiative (http://epi.grants.cancer.gov/gameon/). GAME-ON's overall goal was to foster an intra-disciplinary and collaborative approach to the translation of promising research leads deriving from the initial wave of cancer GWAS. Specific goals included replication of previous GWAS findings and identification of new susceptibility loci through meta analyses of existing GWAS data and fine mapping of identified loci to better pinpoint causal variants; and identify germline variants that are associated with risk of multiple cancers. The other four funded GAME-ON projects were: the ColoRectal TransdisciplinaryStudy (CORECT), Elucidating Loci Involved in Prostate Cancer Susceptibility (ELLIPSE), Follow-up of Ovarian Cancer Genetic Association and Interaction Study (FOCI), and Transdisciplinary Research in Cancer of the Lung (TRICL). To identify additional cancer risk loci, improve the precision of fine-mapping, and facilitate cross-cancer analyses, DRIVE investigators performed a meta-analysis of eleven genome-wide association studies of breast cancer: The Australian Breast Cancer Family Study (ABCFS), the British Breast Cancer Study (BBCS), the Breast and Prostate Cancer Cohort Consortium (BPC3), the Breast Cancer Family Registries (BCFR), the Dutch Familial Bilateral Breast Cancer Study (DFBBCS), German Consortium for Hereditary Breast and Ovarian Cancer (GC-HBOC), the Helsinki breast cancer family Study (HEBCS), the Mammary Carcinoma Risk factor Investigation (MARIE), the Singapore and Sweden Breast Cancer Study (SASBAC), the Triple Negative Breast Cancer Study (TNBC), and the UK2 GWAS. These studies comprised a total of 16,062 cases and 46,157 controls. Imputation to the 1,000 Genomes Project Phase 1 v3 ALL reference panel was performed by study, and summary statistics from each study were combined using fixed-effect meta analysis.

  Study phs001263

• using-ega-account

  Using your EGA account The purpose of this page is to help you access and download the data you have been granted permission to view through your EGA account. To obtain an EGA account please register here. Once your account is created, you can find details on how to manage your EGA account here. EGA access policy (New account holders please read) Access to EGA services are only provided to EGA account holders. EGA accounts are created, updated and closed upon direct instruction from the relevant DAC contact, using the EGA account management tools or through EGA Helpdesk. As part of the EGA account creation process, the EGA account holder must reset their password when instructed. Password resets are checked and verified usually within 24 business hours, during which time the EGA account is inaccessible. EGA accounts are assigned on an individual basis for the exclusive use of the registered EGA account holder; log-in details must remain private and only be used by the EGA account holder. Controlled access data files are only provided, in accordance to the permissions set by the DAC, to EGA account holders. EGA controlled access data files are encrypted prior to download and must be decrypted on the EGA account holders side. EGA account holders are provided access to the EGA download streamer to download access approved datasets and files therein. The EGA download streamer represents the primary means for the EGA account holder to download access approved datasets and files therein. EGA account holders may be provided with an EGA download account for accessing approved datasets and files therein, using FTP or Aspera in response to clearly defined technical reasons, which may restrict the use of the EGA download streamer. It is the sole responsibility of the EGA account holder to ensure full compliance to all terms and conditions of the Data Access Agreement are met once data is downloaded from the EGA. Should you move institute you must contact all Data Access Committee's contacts to update your details and, if necessary, re-apply for data access. The Data Access Agreement (DAA) is a contract made between the DAC and the EGA account holder; the EGA is not responsible for enforcing the DAA. EGA reserves the right to place EGA accounts 'onhold', pending DAC approval to re-activate, should EGA account 'misuse' be suspected. Further information Introduction to the EGA Frequently Asked Questions Subscribe to the EGA mailing list

  Documentation using-ega-account