<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Jonathan! You didn't do yourself justice with your explanation!</div><div><br></div><div>Jonathan's tool suite can:</div><div>1) Automated overhead measurement: (step 1) Buy a new system. (step 2) Install Litmus and Jonathan's tools. (step 3) Run a script with default parameters. (step 4) A while later, you get overheads.</div><div>2) Automated Litmus testing. You give the scripts a few parameters, and it puts the various Litmus schedulers through their paces.</div><div>3) Framework for repeatable experiments. If you want to make your experiments repeatable for others, you can give them a few input files and parameters. The scripts do the rest.</div><div><br></div><div>-Glenn</div><div><br></div><div><div>On Apr 12, 2013, at 5:26 PM, Jonathan Herman <<a href="mailto:hermanjl@cs.unc.edu">hermanjl@cs.unc.edu</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div style="">Running experiments in LITMUS was hard for me to figure out. I created a repository of experiment scripts for my successors at UNC to make their lives easier. These are based off the scripts used by Chris and I in our paper submissions. I made them as user-friendly as possible, so that I will get as few emails as possible. I've also integrated a few ideas from other people at UNC, included instant messaging (Mac) when an experiment completes, and emails (Glenn) when all experiments complete.<br>
</div><div class="gmail_quote"><div dir="ltr">
<div><br></div><div>The scripts can be found here:</div><div><a href="https://github.com/hermanjl/experiment-scripts" target="_blank">https://github.com/hermanjl/experiment-scripts</a></div><div><br></div><div>
I think it would be cool if a repository like this was actively maintained. Anyone want to take mine? Currently, it is very difficult for casual readers to re-create the experiments presented in our papers. It's also too hard to quickly test, debug, and evaluate changes to Litmus, so people just don't do it.</div>
<div><br></div><div style="">P.S. Sorry for sending the other email twice.</div><span class="HOEnZb"><font color="#888888">
<div><br></div>-- <br>Jonathan Herman<br>Department of Computer Science at UNC Chapel Hill
</font></span></div>
</div><br><br clear="all"><div><br></div>-- <br>Jonathan Herman<br>Department of Computer Science at UNC Chapel Hill
</div>
_______________________________________________<br>litmus-dev mailing list<br><a href="mailto:litmus-dev@lists.litmus-rt.org">litmus-dev@lists.litmus-rt.org</a><br>https://lists.litmus-rt.org/listinfo/litmus-dev<br></blockquote></div><br></body></html>