-
Notifications
You must be signed in to change notification settings - Fork 6
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
Trace: construct a CCT #29
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collaborator
adityaranjan
commented
Sep 12, 2022
•
edited
Loading
edited
- implementation of cct
- verified with external tools like vampir for otf2 traces
* tracedata schema * renaming column * tracedata schema * renaming column * move p2p to trace.py * remove .pyc files * cleaned up communication matrix function and added documentation * docs: specify sender/receiver dimensions in top level function comment Co-authored-by: Abhinav Bhatele <[email protected]>
movsesyanae
approved these changes
Oct 11, 2022
jordanmarry
approved these changes
Oct 14, 2022
jordanmarry
approved these changes
Oct 14, 2022
We need to test this with nsight data |
adityaranjan
added
priority: normal
status: ready for review
and removed
status: WIP
labels
Apr 23, 2023
Lets make the CCT construction optional (dependent on user input) |
hsirkar
approved these changes
Nov 3, 2023
pipit/trace.py
Outdated
Currently, the DataFrame index of the entry row is being stored | ||
in the node's calling context ids. This doesn't really have much of a | ||
purpose right now. What should we be storing as calling context ids | ||
for OTF2? Perhaps there should also be a way to map entry rows to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is resolved by match_rows()
function from #44 right?
bhatele
approved these changes
Nov 14, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.