You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TALP reports are currently written to STDOUT (presumably). In many cases this adds noise and may disturb existing workflows which expect certain data in certain positions of the output.
I suggest to add an option to redirect TALP output to a file. (Personally, I like mpiP's approach to construct the filename.)
The text was updated successfully, but these errors were encountered:
This feature is already implemented, although not yet documented. Our documentation is lagging behind lately due to lack of time.
You can see the flag executing dlb -h:
DLB is configured by setting these flags in the DLB_ARGS environment variable.
Possible options are listed below:
Option Current value Possible value (type) / [choice] / {val1:val2}
--------------------------------------------------------------------------------------
...
--talp-output-file: (path)
Or in the extended help dlb -hh:
--talp-output-file: (path)
Write TALP metrics to a file. If this option is not provided,
the output is printed to stderr.
Accepted formats: *.json, *.xml, *.csv. Any other for plain text.
TALP reports are currently written to STDOUT (presumably). In many cases this adds noise and may disturb existing workflows which expect certain data in certain positions of the output.
I suggest to add an option to redirect TALP output to a file. (Personally, I like mpiP's approach to construct the filename.)
The text was updated successfully, but these errors were encountered: