timo_kk

joined 11 months ago
[–] timo_kk@alien.top 0 points 11 months ago

The rebuttal period over the weekend is just a flat-out dick move by the organizers :(

I also love these "Why don't you run on super compute intensive benchmark X" type reviews.

[–] timo_kk@alien.top 1 points 11 months ago

Dude that's slick af

[–] timo_kk@alien.top 1 points 11 months ago

Yeah, I'm liking it. It has strengths and weaknesses like every tool. The biggest advantages for me are:

  • Dead easy to use.
  • Very good for collaborations: You can set up teams or share reports.
  • Good features for analyzing results: You can filter, group etc.

Disadvantages:

  • The interface becomes slow when you've uploaded lots of runs to the same project. That's why I usually split runs into multiple projects depending on the hypotheses that I want to verify.
  • Exporting data from the server is not trivial. Once you've figured it out though you can re-use your code.

The pros outweigh the cons for me.

[–] timo_kk@alien.top 1 points 11 months ago (11 children)

I mark the expected duration of my experiments both in a google calendar as well as a project journal. That way, I know when it's "time" to check in on the runs.

I also use Weights & Biases, which sends me a mail if something crashes so I can check up when I really need to.

Curve watching is just a waste of time, you should train yourself to get out of the habit even if it's difficult for you.