Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Minor
-
Resolution: Fixed
-
Labels:None
Description
Looks like BAM data slices loaded from a DAS/2 source are not being merged. Thus when one moves to a different location and hits Refresh Data a new track is created. This is a recent issue and wasn't a problem 6 months ago.
I also noticed that the name given to the data track isn't the DAS/2 delivered name but a local temp file? This is also a new bug.
To reproduce this navigate to chrY on Human_Feb_2009, enable the UofUBioinformatics Core DAS/2 server and goto -> BamTest -> ChrY -> select the "All Paired 101bp Fixed" track. then zoom in on a gene hit Refresh Data, move over a few mb, hit Refresh again.
Note this is particular to BAM data and doesn't appear to be a problem with other binary data such as xxx.useq.
Attachments
Issue Links
- relates to
-
BUG-647 Server bugs
-
- Closed
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
| Status | Resolved [ 5 ] | Closed [ 6 ] |
| Assignee | Alyssa Gulledge [ alyssa ] |
| Resolution | Fixed [ 1 ] | |
| Status | Closed [ 6 ] | Reopened [ 4 ] |
| Assignee | Katharine Kubiak [ kkubiak ] |
| Assignee | Katharine Kubiak [ kkubiak ] | Anuj Puram [ anuj ] |
| Assignee | Anuj Puram [ anuj ] | Alyssa Gulledge [ alyssa ] |
| Status | Reopened [ 4 ] | Resolved [ 5 ] |
| Assignee | Alyssa Gulledge [ alyssa ] | |
| Resolution | Fixed [ 1 ] |
| Status | Resolved [ 5 ] | Closed [ 6 ] |
| Resolution | Fixed [ 1 ] | |
| Status | Closed [ 6 ] | Reopened [ 4 ] |
| Assignee | Vineeth Mylapur [ smylapur ] |
| Status | Reopened [ 4 ] | Resolved [ 5 ] |
| Assignee | Vineeth Mylapur [ smylapur ] | |
| Resolution | Fixed [ 1 ] |
| Resolution | Fixed [ 1 ] | |
| Status | Resolved [ 5 ] | Reopened [ 4 ] |
| Status | Reopened [ 4 ] | Closed [ 6 ] |
| Resolution | Fixed [ 1 ] |
Fixed in r8824.