Ember: adds reading global string definitions from OTF2 traces #2450
+81
−44
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 change extends the OTF2 motif in Ember, so that it can read the global string definitions from an OTF2 trace into memory. String definitions (e.g., function names) are referenced in OTF2 event packets through stringRef ids. This change will allow Ember to interpret these references. There are also local (per rank) definitions in OTF2, but this change is concerned only with reading the global strings.
To avoid issues with potentially lots of string definitions in large trace files, the loading is disabled by default. To enable one has to set the readGlobalStringDefinitions config parameter:
...
ep = EmberMPIJob(0, topo.getNumNodes())
...
ep.addMotif("OTF2 tracePrefix=trace.otf2 readGlobalStringDefinitions=True")
....