-
Notifications
You must be signed in to change notification settings - Fork 1
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
The U-MLP model #1
Comments
Sorry, back then I didn't release the training functions+dataloader. I only shared the building blocks from my shared code repository. I will be working on having a full working example for all the methods here soon (probably on just MNIST for simplicity). U-MLP is just a normal MLP that tries to predict the loss of a primary model. There is nothing special about its architecture. In my experience (and what was done in the paper) it works best if the input to the secondary model (the U-MLP) is a representation from the primary model concatenated with the prediction of the primary model.
I intended that people can instantiate the linked classes, e.g. for the sparse Gaussian Process. And then simply integrate that in their pipeline. |
I found my old code. I will have to do some cleaning and slight restructuring. After making sure that it returns the reported results, I will then push the code to this repository. I expect to push it this weekend. |
@ToBeNormal I pushed the training/grid-search functions yesterday. My next ToDos are (probably by the end of the next weekend): 1) functions to get the metrics reported in the paper; 2) share the data for the dataloaders (get the mnist data from |
Hi, Many thanks for providing the codes. I am a bit confused about the command for training the secondary model in README. Isn't the executed file named "train_secundary.py"? |
Thank you, I updated the readme. |
Thank you for your excellent work. I'm a bit confused about which test code is corresponding to the U-MLP model.
And I don't know how to reuse your code.
The text was updated successfully, but these errors were encountered: