Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Log run naming #127

Open
abelsiqueira opened this issue Jul 5, 2023 · 0 comments
Open

Log run naming #127

abelsiqueira opened this issue Jul 5, 2023 · 0 comments

Comments

@abelsiqueira
Copy link
Contributor

abelsiqueira commented Jul 5, 2023

It would be useful to have some functions on the dataset and the model to help name the logs. Something like

"runs/" + dataset.oneline_description() + "/" + model.oneline_description() + other_info

These need to incorporate all that is needed to have uniqueness and it would also be helpful if they helped organize the comparisons.

By using /, we separate into folders, so the rightmost folders are easier to be compared together (although tensorboard is helpful enough for this).
So I think it is better to start with everything related to the dataset.

It might get crowded, so maybe some very short description tag is better? Like hash-ME650-MN50-MP500-...?

For the model, describing which layers (including sizes) would be necessary. It would be better to have it automatically, but it doesn't seem easy. Also, the model is small enough to be easy to change the string generator. That being said, at least the layer size needs to be given dynamically. Something like

def str_description(self):
    return f"in-GC{len(self.conv1)}-RELU-GCout-mean"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant