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

Fix degeneracy order and remove more clones #1

Conversation

michaelsproul
Copy link

  • Fix degeneracy_order. It was doing the indexing-after-deleting thing, which was not correct. I think the tests were passing because the degeneracy order doesn't affect correctness (just speed).
  • Remove some unnecessary clones in bron_kerbosch. We could use either HashTrieSet or Vec for the neighbourhoods. I'm not sure which is better, they seem about the same speed in testing, so using Vec for now.
  • Tweak the asserts in the attestation_pairwise_overlapping test so that they pass. Another configuration that is feasible (but blows up badly) is num_validators = 15 * spec.target_committee_size with step_size = 1.
  • Correct typo in name of compute_neighbourhood function.

}
}
o
v.sort_unstable_by_key(|i| neighbourhoods[*i].len());
Copy link
Author

Choose a reason for hiding this comment

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

I'm pretty sure this is what was intended, but would appreciate a double-check from you @GeemoCandama

Copy link
Owner

Choose a reason for hiding this comment

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

Yes that should be better. I don't know how I overlooked this before. I hadn't changed this from the Satalia code.

@GeemoCandama GeemoCandama merged commit 74d0a15 into GeemoCandama:bron_kerbosch_attestation_aggregation Oct 31, 2023
@michaelsproul michaelsproul deleted the bron_kerbosch_attestation_aggregation branch October 31, 2023 06: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