Per our most recent HEP-computing meeting -
We have a number of data sources and plotting tools for TaskVine, but no single "bright path" for users to follow when things go wrong. So:
- Create a single tool
vine_plot_run that consumes all the logs in a single run (maybe even default to vine-run-info/most-recent/vine-logs) runs the existing plotting tools, arranges them nicely with some summary info, and emits a file: url pointing to an index.html that arranges and displays everything nicely.
(don't create new tools, just stitch together the things that we have.)
- Update our manuals to encourage this as the one single way to plot all of the things by default.
Per our most recent HEP-computing meeting -
We have a number of data sources and plotting tools for TaskVine, but no single "bright path" for users to follow when things go wrong. So:
vine_plot_runthat consumes all the logs in a single run (maybe even default tovine-run-info/most-recent/vine-logs) runs the existing plotting tools, arranges them nicely with some summary info, and emits afile:url pointing to anindex.htmlthat arranges and displays everything nicely.(don't create new tools, just stitch together the things that we have.)