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

mlflow checkpoints in the wrong location #2939

Closed
david-waterworth opened this issue Aug 12, 2020 · 3 comments
Closed

mlflow checkpoints in the wrong location #2939

david-waterworth opened this issue Aug 12, 2020 · 3 comments
Labels
bug Something isn't working help wanted Open to be worked on

Comments

@david-waterworth
Copy link
Contributor

david-waterworth commented Aug 12, 2020

I'm not sure if I'm doing something wrong, I'm using mlflow instead of tensorboard as a logger. I've used the defaults i.e.

mlflow = loggers.MLFlowLogger()
trainer = pl.Trainer.from_argparse_args(args, logger=mlflow)

I'm ending up with the following folder structure

\mlflow
\mlflow\1
\mlflow\1\{guid}\artifacts
\mlflow\1\{guid}\metrics
\mlflow\1\{guid}\params
\mlflow\1\{guid}\meta.yaml
\1\{guid}\checkpoints

i.e. the checkpoints are in the wrong location, they should be in the \mlflow folder.

Perhaps this is an mlflow rather than pytorch-lightning issue?

I'm using pytorch-lightning 0.8.5 on macos running in python 3.7.6

@david-waterworth david-waterworth added bug Something isn't working help wanted Open to be worked on labels Aug 12, 2020
@Borda
Copy link
Member

Borda commented Aug 13, 2020

@david-waterworth mind try the latest 0.9rc12?

@awaelchli
Copy link
Contributor

It was fixed here: #2502
The checkpoints subfolder will go here: mlflow\1{guid}\checkpoints, is that what you want @david-waterworth ?

@david-waterworth
Copy link
Contributor Author

Thanks @awaelchli yes that's what I want - thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Open to be worked on
Projects
None yet
Development

No branches or pull requests

4 participants