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.

Sign up for GitHub

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

Jump to bottom

train3: checkpoint failed #4

Open
chaytonmin opened this issue Dec 10, 2019 · 2 comments
Open

train3: checkpoint failed #4

chaytonmin opened this issue Dec 10, 2019 · 2 comments
Labels
code

Comments

@chaytonmin
Copy link

捕获
2
@walsvid walsvid added the code label Dec 12, 2019
@walsvid
Copy link
Owner

walsvid commented Dec 14, 2019 •
edited
Loading

Hi, @chaytonmin. I think it may due to the mismatch variable names in checkpoint files, I'll try to reproduce this bug. Before that, I think there are 2 ways to solve this problem. 1. You can change the name of MVP2M model from MeshNetMVP2M to MeshNet or change the scope from meshnet/cnn to meshnetmvp2m/cnn to load CNN variables. 2. You can manually map the corresponding name between checkpoint files and current session

@walsvid walsvid added the bug Something isn't working label Dec 14, 2019
@chaytonmin
Copy link
Author

chaytonmin commented Dec 14, 2019 via email •
edited
Loading

@walsvid walsvid removed the bug Something isn't working label Dec 15, 2019
@topinfrassi01 topinfrassi01 mentioned this issue Mar 17, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
code
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@walsvid @chaytonmin