Don’t forget to measure time…

I just did a batch of test runs of my NMF code, and I noticed that I forgot to capture the elapsed execution time in the code for the projected gradient approach. I also forgot to use the time command in my bash test scripts. Which means that the 3 hours of testing produced exactly zero time measurements for me on one of the test machines. And this si essentially all I really cared about at the moment. Sigh…

Oh well, at least I got some data for convergence graphs out of this. Remember kids - if your researching new ways to optimize old algorithms, it is usually a good idea to try to capture the execution time of your test runs. |

I can’t wait to be done with this.

Related Posts:

  • Don’t Kill Freedom!
  • Don’t go all Jack Thompson on Virginia Tech
  • Bill Gates for President - Worst Idea Ever!
  • Don’t you just love the classics?
  • No breaking DRM, even if it may kill you
  • Don’t Grep the Cat
  • Wow! I got Gmail!
  • I just don’t know what to say…
  • How come I don’t have Gmail IMAP yet?
  • God! Why people don’t mak their emails NSFW!

  • Leave a Reply

    XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <pre lang=""> <em> <i> <strike> <strong>

    [Quote selected]