Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
E
ensembl
Manage
Activity
Members
Labels
Plan
Issues
0
Issue boards
Milestones
Iterations
Wiki
Requirements
Jira
Code
Merge requests
1
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package Registry
Container Registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
ensembl-gh-mirror
ensembl
Commits
8a552edf
Commit
8a552edf
authored
21 years ago
by
Graham McVicker
Browse files
Options
Downloads
Patches
Plain Diff
updated a few things
parent
c33424e2
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/ensembl_changes_spec.txt
+38
-22
38 additions, 22 deletions
docs/ensembl_changes_spec.txt
with
38 additions
and
22 deletions
docs/ensembl_changes_spec.txt
+
38
−
22
View file @
8a552edf
...
...
@@ -6,7 +6,6 @@ REVISION HISTORY
Graham Mcvicker - July 9, 2003 - Created
GOALS
-----
-A cleaner, more intuitive API
...
...
@@ -209,10 +208,10 @@ Slice
The get_tiling_path method will have to be implemented differently for the
new system. It will take a coord_system string as an argument and rather than
returning a list of Tile objects it will return a listref of triplets
containing
a start int, and end int, and a 'to' slice object. The following
is an example
of how this method would be used ($clone is a reference to a
slice object in
the clone coordinate system):
returning a list of Tile objects it will return a listref of triplets
containing
a start int, and end int, and a 'to' slice object. The following
is an example
of how this method would be used ($clone is a reference to a
slice object in
the clone coordinate system):
my $clone_path = $slice->get_tiling_path('clone');
...
...
@@ -254,9 +253,10 @@ RawContig
RawContigAdaptor
----------------
The RawContigAdaptor is no longer necessary. The RawContigAdaptor is replaced
by the SliceAdaptor. For backwards compatibility a minimal implementation
of the RawContigAdaptor can remain which inherits from the SliceAdaptor.
The RawContigAdaptor is no longer necessary. The RawContigAdaptor is
replaced by the SliceAdaptor. For backwards compatibility a minimal
implementation of the RawContigAdaptor can remain which inherits from the
SliceAdaptor.
Clone
-----
...
...
@@ -438,15 +438,15 @@ Features
transform(coord_system)
-----------------------
Takes a single string specifying the new coord system. If the coord
system is not valid an exception is thrown. If the coord system is the
same coord system as the feature is currently in a new feature that is
a copy of the old one will still be returned. This will also retrieve
a slice which is the entire span of the region of the coordinate system
that this feature is being transformed to. For example transforming
an exon in raw contig coordinates to one in chromosomal coodinates
will place the exon on a slice of an entire chromosome. If a feature
spans a boundary in the coordinate system, undef is returned by the
method instead.
system is not valid an exception is thrown. If the coord system is the
same coord system as the feature is currently in a new feature that is
a copy of the old one will still be returned. This will also retrieve
a slice which is the entire span of the region of the coordinate system
that this feature is being transformed to. For example transforming
an exon in raw contig coordinates to one in chromosomal coodinates
will place the exon on a slice of an entire chromosome. If a feature
spans a boundary in the coordinate system, undef is returned by the
method instead.
translate(slice)
----------------
...
...
@@ -490,10 +490,16 @@ AssemblyMapper
do the following:
NTContig -> Contig -> Clone
This should simply be a matter of offsetting values in a stepwise matter when
loading the mapper. The mapper will have a table of conversions between the
NTContig and Clone systems which is constructed by the assembly mapper
(rather than read directly from the assembly table).
In the above example the assembly mapper would have do the following:
(1) Create a mapper object between the NTContig and Contig region
(2) Create a mapper object between the Contig and Clone region
(3) Create and return a third mapper constructed from the sets of mappings
generated by the intermediate mappers.
As an intermediate implementation step it would be possible to leave the
AssemblyMapper almost as is and to require explicit mappings between all
coordinate systems of intereset to be present in the assembly table.
FeatureAdaptors
...
...
@@ -558,9 +564,19 @@ Haplotypes
OTHER CONSIDERATIONS
--------------------
Feature Transfer Accross Assemblies
-----------------------------------
Future assemblies (especially human assemblies) are expected to be small
refinements of previous assemblies. Rather then recomputing all of the new
genes and features on these assemblies it makes more sense to transfer most
features across from the previous assembly, only rebuilding in areas of
change. We will supply a mechanism via which features from a previous
assembly may be transfered to a new assembly.
TBD
MHC Regions
Circular Chromosomes
Multiple
Chromosom
es
Multiple
Assembli
es
This diff is collapsed.
Click to expand it.
Preview
0%
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment