Frequently Asked Questions
Questions about individual stocks listed in FlyBase should be directed to the collection that holds the stock. For collections with web sites, the name in the "Collection" field of the FlyBase Stock Report links to the collection's web site, where contact information can be found. For laboratory collections that do not have web sites, an e-mail address is included in the "To Request Stock" field of the FlyBase Stock Report.
Arm U is an unordered assembly of unplaced sequence scaffolds. More information about Arm U can be found in the GenBank record (FA000001).
Here is the comment section from this record:
How can I submit a correction to the genomic sequences of a Drosophila species other than D. melanogaster?
At the present time, the genomic sequences of the "other" Drosophila species (other than D. melanogaster) are static; there are no immediate plans to incorporate corrections. Since FlyBase does not store original sequence data, we suggest that you submit your sequence to GenBank. You can then send us a personal communication with the accession number and a description of the error. We will add that communication and the accession number to the gene records affected, so that other users of FlyBase may benefit from your improved data.
For gene models, if you have sequenced a cDNA, you should submit that sequence to GenBank. We have an automatic pipeline from NCBI for handling cDNA data. The accession number will be incorporated into the gene report and an alignment shown on GBrowse.
If you do not have a sequenced cDNA, but have a proposed correction determined by other means, you may be able to submit it to GenBank as a TPA (third party annotation). Again, in this case, we would appreciate a personal communication that includes the accession number and a description of the error.
If your correction cannot be appropriately submitted to GenBank by any of these routes, we will accept it as a personal communication --- but this is not preferrable. The sequence would not be available via BLAST or other queries, nor would it appear as an alignment in GBrowse.
If there is a full length DGC clone associated with a gene you will find it in the gene report under the REAGENTS/cDNA section in its own field. For example: Dmel\lark lists LD40792 as a DGC clone.
If the "DGC cDNAs" field does not appear in a report it means that a DGC clone has not been identified for the gene.
This works for some genes but not others. A work around for this until we get it fixed is to use the GBrowse 'Download sequence ' option. Here's how it works:
Using Dlic2 (CG1938) as an example, copy the coordinates from the 'Physical map' field of the annotation report into the GBrowse 'Find Genome Region' window. This displays X:10999619..11008430 in GBrowse. In the 'Feature Tracks' panel select the features you're interested in and update the map. Then open the 'Download sequences' panel toward the bottom of the page. From the 'Dumps,...' menu select 'Dump Decorated FASTA file' and choose 'Configure'. Select display settings to distinguish the features you're interested in.
Unfortunately there is not an easy way to get the flanking sequences for a specific subset of genes in FlyBase. You can get a multiple FASTA file containing the gene region sequences including 2000 bp flanking on either end from the ftp site.
The file: dmel-all-gene_extended2000-r4.2.1.fasta contains these sequences. There is also a file with all intergenic sequences.
You would then need to identify your genes of interest and pull out the section of sequence you were interested in.
Unfortunately Exelixis made the decision not to save their libraries as they felt the clones were largely overlapping with existing ones. Obviously that is not truly the case but that is the situation so none of these clones are available.
The Drosophila phylogeny shown on FlyBase is a compilation of information that can be found in:
A Powell, J.R. 1997 Progress and Prospects in Evolutionary Biology: The Drosophila Model.
Oxford University Press, Inc.
BIOSIS ID: 1102964
From this, you can go to the abstract search page to find your abstract-of-interest, for example:
BDGP genome assemblies are referred to using a 'Release_#' notation. The decimal in FlyBase release notation refers to an annotation set produced by FlyBase that is attached to that assembly; e.g., the release for February 2010 was Release_5.25. Note that feature coordinates will only change with new release assemblies. If you want information on the current assembly and current annotation set, you should look at FlyBase's Release Notes, opening up the subsection entitled "Drosophila melanogaster (R#.##)".
D. melanogaster has had 5 genome assemblies produced by BDGP. Release_1 and Release_2 were Celera whole genome shotgun (WGS) assemblies, whereas Releases_3, _4, _5 were all BDGP BAC tiling array assemblies taken to a high degree of finishing (except for the uncooperative parts of the centric heterochromatin and a small number of other sizeable regions containing highly repetitive sequences such as the histone gene cluster). Because of the WGS nature of Release_1 and Release_2, producing a coordinate converter for these releases to Releases_3, _4, _5 is not practically possible.
The D. pseudoobscura release 2 assembly was produced by the Baylor HGSC as an improvement to its initial release 1 assembly. The assemblies in FlyBase for the other sequenced Drosophila species are the initial frozen CAF1 assemblies that were produced as part of the same project. More information can be found at the AAA site.
The UCSC assembly numbers dm1 through dm3 correspond to BDGP/FlyBaseGenBank assemblies Release 3 through Release 5.
You can use the FlyBase Coordinate Converter tool to forward-migrate coordinates from Release 3 to Release 4, or from Release 4 to Release 5. No tool exists for migrating from BDGP/FlyBaseGenBank Releases 1 or 2.
We realize that many people like to print out the information provided by FlyBase, however some of the current browsers do not render the new FlyBase pages particularly well. If you routinely print out a significant amount of information from FlyBase we recommend that you use Opera as your browser. While many other browsers will print the information included in a report, at this time only Opera will print the page format properly (including colors and shading).
If your work requires that you print the page exactly as it appears on your monitor and you do not wish to install Opera, we suggest that you print a screen shot of the page. Instructions on how to take a screen shot on different platforms are given below.
If you use Safari consider installing the free program Netfixer that allows you to capture an image of an entire webpage no matter its length.