Machine Learning

1 readers

1 users here now

Community Rules:

Be nice. No offensive behavior, insults or attacks: we encourage a diverse community in which members feel safe and have a voice.
Make your post clear and comprehensive: posts that lack insight or effort will be removed. (ex: questions which are easily googled)
Beginner or career related questions go elsewhere. This community is focused in discussion of research and new projects that advance the state-of-the-art.
Limit self-promotion. Comments and posts should be first and foremost about topics of interest to ML observers and practitioners. Limited self-promotion is tolerated, but the sub is not here as merely a source for free advertisement. Such posts will be removed at the discretion of the mods.

founded 1 year ago

MODERATORS

communick@academy.garden

[D] Do you obsessively watch your models train? (alien.top)

submitted 11 months ago by TehDing@alien.top to c/machinelearning@academy.garden

60 comments fedilink hide all child comments

I find myself watching tensorboard more than working- just wondering if others who have fallen into this pattern have words of advice wrt productivity

you are viewing a single comment's thread
view the rest of the comments

[–] 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.

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

I wondered about weights and biases. Does it go well with tensorflow? Are you liking it so far?

[–] 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.

load more comments (9 replies)