Skip to content

Conversation

@Georgehe4
Copy link

@Georgehe4 Georgehe4 commented Apr 30, 2017

Before
screen shot 2017-04-30 at 1 34 46 am

After
screen shot 2017-04-30 at 1 31 08 am

Modify coverage track to show lower coverage regions.

dorisjlee and others added 30 commits October 3, 2016 16:30
…and Genotype.js constructors to take in objects instead
…and Genotype.js constructors to take in objects instead
@AmplabJenkins
Copy link

Can one of the admins verify this patch?

localYScaleForRef(ref: string): (y: number) => number {
var maxCoverage = this.cache.maxCoverageForRef(ref);

var padding = 20; // TODO: move into style
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what is the TODO for?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is an artifact of the original yScaleForRef.

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we need the todo then?

.nice();
}

localYScaleForRef(ref: string): (y: number) => number {
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why is it called local?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The padding created in the original yScaleForRef seems to cause the y-coordinate of the DataCanvasRenderingContext2D in the render function to be shifted off by 10 degrees. The original yScaleForRef is still used to generate the tick marks, so I create another one for rendering coverage tiles that shouldn't be used outside of context of coverage tiles.

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I dont love the idea of having YScaleForRef and localYScaleForRef. We should probably just have 1 function.

@Georgehe4 Georgehe4 force-pushed the coverage_track branch 2 times, most recently from d845a3a to 95fa18e Compare April 30, 2017 06:47
@Georgehe4
Copy link
Author

Updated

@akmorrow13
Copy link
Owner

These changes should go in the hammerlab pileup

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants