We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
.cali files are structured like:
.cali
... { "event.begin#mpi.function": "MPI_Send", "mpi.rank": 0, "time.duration.ns": 167010, "time.offset.ns": 240363845 }, { "mpi.comm": "2", "mpi.comm.is_world": "true", "mpi.comm.size": "4", "mpi.msg.dst": 2, "mpi.msg.size": 4, "mpi.msg.tag": 1, "mpi.rank": 0, "mpi.send.count": 1, "path": "MPI_Send", "time.duration.ns": 47307, "time.offset.ns": 240411152 }, { "event.end#mpi.function": "MPI_Send", "mpi.rank": 0, "path": "MPI_Send", "region.count": 1, "time.duration.ns": 5813, "time.offset.ns": 240416965 }, ...
The cali2events.py script successfully pairs any event.begin records with their corresponding event.end.
cali2events.py
event.begin
event.end
However, for MPI Point-To-Point calls, more information is included in the "in-between" record (see above).
Find a way to get this data (src, dst, size) into events.json so that we can track calls in the visualizations.
events.json
The text was updated successfully, but these errors were encountered:
No branches or pull requests
.cali
files are structured like:The
cali2events.py
script successfully pairs anyevent.begin
records with their correspondingevent.end
.However, for MPI Point-To-Point calls, more information is included in the "in-between" record (see above).
Find a way to get this data (src, dst, size) into
events.json
so that we can track calls in the visualizations.The text was updated successfully, but these errors were encountered: