Details
-
Type:
Task
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Story Points:1
-
Epic Link:
-
Sprint:Spring 3 : 3 Feb to 14 Feb, Spring 3 : 17 Feb to 28 Feb, Spring 4 : 2 Mar to 13 Mar, Spring 5 : 16 Mar to 27 Mar, Spring 6 : 30 Mar to Apr 10, Spring 7 : 13 Apr to 24 Apr, Spring 8 : 24 Apr to 8 May, Spring 8 : 11 May to 25 May
Description
Add breakpoints to the annotation factory class in com.affymetrix.igb.view.factories and observe what happens when you click Load Data after opening a narrowpeak file.
Based on looking at the code, it looks like this method:
private void addAnnotationGlyphs(SeqMapView smv, RootSeqSymmetry annotSym, BioSeq seq)
in
com.affymetrix.igb.view.TrackView
Is where the MapTierGlyphFactoryI for a given data set is identified and used to add Glyphs to IGB's SeqMapView
We need to confirm this.
Ideally, we can write a new new factory class that will let us add custom Glyphs to a genotyping results class, simply by adding the factory to the service registry for same.
Attachments
Issue Links
Activity
Srishti Tiwari - follow-up question:
If you were to remove "Annotation" from the static array, would that cause the Annotation tab to stop becoming active when users click on an "Annotation" track label?
Findings regarding whether Annotation Track is extensible to proposed user-created file type categories:
In AnnotationTrackPanel and AnnotationOperationImpl classes there is a static array of file type categories defined, which contains only three values - Annotation, Alignment, and ProbeSet.
Hi Dr. [~aloraine],
The above understanding is correct. However, as per current implementation, we cannot have multiple GylphFactories for one File type category. (Please refer: MapTierTypeRegistry.java > getDefaultFactoryFor(FileTypeCategory) This method returns the first GlyphFactory in the list of preprocessors it has)
For our case, we could change this behavior by making a change in the above method or add a new file type category.
Also,
In FileTypeHolder there is a Map that stores file extensions and their FileTypeHandlers.
As per current implementation, the number of FileTypeCategories is fixed (as enums). Every new extension must belong to one of the predefined file type categories. If the new file type category needs to be added, we have to touch the core IGB codebase. We can change this by making the FileTypeCategory extensible. The way to do that is mentioned below:
https://dzone.com/articles/java-extensible-enum-with-interface
If you have some tips or advice for the next developer who works on this, please add them to this ticket. Then move to Done. If not, also move to Done.
cc: Srishti Tiwari