Skip to content

Commit

Permalink
update README.md with updated location of PaRSEC Python module ... re…
Browse files Browse the repository at this point in the history
…solves #266
  • Loading branch information
evaleev committed Oct 31, 2023
1 parent 3e27a91 commit 4c5cad6
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -277,7 +277,7 @@ To generate the trace results of any TTG program follow the process discussed be
- Set the environment variable `PARSEC_MCA_profile_filename` to the PBT file name _prefix_, e.g. `/tmp/ttg`.
- Run the program and make sure the trace files (in PBT format) have been generated; e.g., if you set `PARSEC_MCA_profile_filename` to `/tmp/ttg` you should find file `/tmp/ttg-0.prof-...` containing the trace from MPI rank 0, `/tmp/ttg-1.prof-...` from rank 1, and so on.
- Convert the traces from PaRSEC Binary Trace (PBT) format to the Chrome Trace Format (CTF):
- Add `{TTG build directory}/_deps/parsec-build/tools/profiling/python/build/{lib folder for your version of Python}` (currently it is not possible to use PaRSEC Python module from the install tree, only from its build tree)
- Add `{TTG build directory}/_deps/parsec-build/tools/profiling/python/python.test` (currently it is not possible to use PaRSEC Python module from the install tree, only from its build tree)
to the `PYTHONPATH` environment variable so that the Python interpreter can find the modules for reading the PaRSEC trace files.
- Convert the PBT files to a CTF file by running the conversion script:
```
Expand Down

0 comments on commit 4c5cad6

Please sign in to comment.