Skip to content

Conversation

@jeromekelleher
Copy link
Member

Also includes the C testing framework for the rest of the balance metrics. So, to implement other balance metrics in C we add the implementation, and then test the returned value in these three test function.

cc @jeremyguez

@jeromekelleher
Copy link
Member Author

Sigh - codecov has gone a bit haywire again. I think everything that can be covered is covered.

@jeromekelleher
Copy link
Member Author

Bumping this one @benjeffery

Copy link
Member

@benjeffery benjeffery left a comment

Choose a reason for hiding this comment

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

LGTM - One question, is a 32bit depth only safe when _TSK_BIG_TABLES is not used? I'm not sure how paranoid to be here, but maybe the type of depth should be conditional on that macro?

+ Python/C glue for sackin_index

Closes tskit-dev#2253
@jeromekelleher
Copy link
Member Author

LGTM - One question, is a 32bit depth only safe when _TSK_BIG_TABLES is not used? I'm not sure how paranoid to be here, but maybe the type of depth should be conditional on that macro?

Hah, good spot. I changed the depth value to a tsk_id_t as that is always safe.

@mergify mergify bot merged commit 6152aef into tskit-dev:main May 16, 2022
@jeromekelleher jeromekelleher deleted the sackin-c branch June 17, 2022 09:31
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.

2 participants