Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closes #151 #152

Merged
merged 4 commits into from
Jul 3, 2019
Merged

Closes #151 #152

merged 4 commits into from
Jul 3, 2019

Conversation

leoisl
Copy link
Collaborator

@leoisl leoisl commented Jun 28, 2019

Closes #151

Switching to uint16 for coverage information reduced the RAM usage for pandora compare on the full klebs dataset from 17.1 GB to 13.5 GB.

This dataset contains only 151 samples, and the more samples, the larger is the reduction, so this change is important for scalability.

@leoisl leoisl requested review from rmcolq and mbhall88 June 28, 2019 14:46
Copy link
Member

@mbhall88 mbhall88 left a comment

Choose a reason for hiding this comment

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

A couple of variable name suggestions.

As a more general statement. I would like if we could move away from having these enormous tests that test a huge number of different states and conditions. A test should test one single case and it should be fairly easy to see what the test is testing from reading the code.
The test here that you have added realistically should be broken up into many smaller tests. Additionally, the name of a test should tell the reader what the test does and what the expected outcome is. See this test suite for an example of testing a single function.

include/kmergraphwithcoverage.h Outdated Show resolved Hide resolved
include/kmergraphwithcoverage.h Outdated Show resolved Hide resolved
include/kmergraphwithcoverage.h Outdated Show resolved Hide resolved
@leoisl
Copy link
Collaborator Author

leoisl commented Jun 29, 2019

As a more general statement. I would like if we could move away from having these enormous tests that test a huge number of different states and conditions. A test should test one single case and it should be fairly easy to see what the test is testing from reading the code.
The test here that you have added realistically should be broken up into many smaller tests. Additionally, the name of a test should tell the reader what the test does and what the expected outcome is. See this test suite for an example of testing a single function.

Indeed, you are right, it is a better approach. I will break this single test into 6 different tests.

@leoisl leoisl requested a review from mbhall88 July 2, 2019 22:21
@leoisl
Copy link
Collaborator Author

leoisl commented Jul 2, 2019

All your suggestions were done in 910e49b, please check if further improvements should be made.

@rmcolq
Copy link
Collaborator

rmcolq commented Jul 2, 2019 via email

Copy link
Member

@mbhall88 mbhall88 left a comment

Choose a reason for hiding this comment

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

The tests look good to me now.

@rmcolq rmcolq merged commit 472f95a into iqbal-lab-org:dev Jul 3, 2019
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.

3 participants