Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This provides an example using the contact concurrences introduced in #28. Although I prefer to get example trajectories from figshare, this specific case is a little too vaguely sourced (I got the force field from someone and have an incomplete description of how it was parametrized) to put up on figshare until there's a paper out on it. However, the purpose here is not the specific science behind the trajectory, but to use that trajectory as an illustration of contact concurrences. In the future we might replace this with something to be hosted on figshare.
This also does a little bit of cleanup of the concurrence plot output (removes misleading yticks).