Details
Description
This issue is to capture the impact of changing Sequence.sequenceFeatures from an unordered array to a structured data store of
SequenceFeatures // all features for one sequence
FeatureStore // all features for one sequence and type
// with internal structure including NCList for any nested features
Approach:
- inspect all calls to Sequence.getSequenceFeatures() and setSequenceFeatures() in Jalview
- look for optimisation opportunities (get features by type and/or range)
- identify any further impact on / methods wanted on SequenceFeatures
- identify regression testing required if migration proceeds
SequenceFeatures // all features for one sequence
FeatureStore // all features for one sequence and type
// with internal structure including NCList for any nested features
Approach:
- inspect all calls to Sequence.getSequenceFeatures() and setSequenceFeatures() in Jalview
- look for optimisation opportunities (get features by type and/or range)
- identify any further impact on / methods wanted on SequenceFeatures
- identify regression testing required if migration proceeds
Attachments
Issue Links
- blocks
-
JAL-2480 Encapsulate performant access to sequence features
- Closed
- related with
-
JAL-2446 Add NCList data structure to Jalview
- Closed
-
JAL-2444 Define requirements for efficient sequence feature datastore
- Closed
-
JAL-2505 Make 'key' members of SequenceFeature final
- Closed
-
JAL-2490 Performant lookup of features at position
- Closed
-
JAL-2492 Performant lookup of non-positional features
- Closed
-
JAL-2525 Performant lookup of features by Ontology term
- Closed
(2 related with)