Benchmarking of SoS steps about sos HOT 4 CLOSED

Why cannot we do this by default (or with command line option) for every
step as long as users provide a log file? Users can always use a script (or
a tool provided by us) to parse log file and get the details.

Bo

On Thu, Mar 10, 2016 at 6:13 PM, gaow [email protected] wrote:

I looked at the wiki but I did not see the a benchmarking
https://bitbucket.org/snakemake/snakemake/wiki/Documentation#markdown-header-benchmark-rules
feature for SoS steps. Perhaps it can be something good to have?

—
Reply to this email directly or view it on GitHub
#5.

from sos.

We can even save all these to our .runtime directory and provide details or
the statistics through some sort of 'sos analyze' command.

Bo

On Thu, Mar 10, 2016 at 6:46 PM, Bo Peng [email protected] wrote:

Why cannot we do this by default (or with command line option) for every
step as long as users provide a log file? Users can always use a script (or
a tool provided by us) to parse log file and get the details.

Bo

On Thu, Mar 10, 2016 at 6:13 PM, gaow [email protected] wrote:

I looked at the wiki but I did not see the a benchmarking
https://bitbucket.org/snakemake/snakemake/wiki/Documentation#markdown-header-benchmark-rules
feature for SoS steps. Perhaps it can be something good to have?

—
Reply to this email directly or view it on GitHub
#5.

from sos.

I agree we do this by default and it would be even better to provide an interface to summarize!

from sos.

See proposed interface at https://github.com/bpeng2000/SOS/wiki/User-Interface#subcommand-analyze-or-summarize
. Right now we have .sos/.runtime, I guess we can have
.sos/.runtime-datetime etc for individual runs and use the 'sos analyze'
command to gather statistics.

Bo

On Thu, Mar 10, 2016 at 7:06 PM, gaow [email protected] wrote:

I agree we do this by default and it would be even better to provide an
interface to summarize!

—
Reply to this email directly or view it on GitHub
#5 (comment).

from sos.