-
-
Notifications
You must be signed in to change notification settings - Fork 66
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
Docs rehaul for v0.8 #242
Docs rehaul for v0.8 #242
Conversation
Once the documentation build has completed, you can preview any updated documentation at this URL: https://fluxml.ai/Metalhead.jl/previews/PR242/ |
Signed-off-by: Abhirath Anand <74202102+theabhirath@users.noreply.github.com>
45952bd
to
d8cbdd1
Compare
Signed-off-by: Abhirath Anand <74202102+theabhirath@users.noreply.github.com>
436c958
to
ae8a8eb
Compare
Signed-off-by: Abhirath Anand <74202102+theabhirath@users.noreply.github.com>
We should disallow loading densenet pretrained weights and mark the weight as not available in the docs. |
Signed-off-by: Abhirath Anand <74202102+theabhirath@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks pretty good to me!
Other details that I cannot directly comment on:
- The
DenseNet
docstring has the "Arguments" bullet list indented which is being interpreted as a markdown code block - The
UNet
docstring has the same issue asDenseNet
- The
MLPMixer
+ResMLP
docstring should list the config types as symbols (i.e.:small
,:base
, etc.)
Also need to remove |
Also commented out DenseNet pretrained tests for now Co-Authored-By: Kyle Daruwalla <daruwal@cshl.edu>
Done, done, done and done! Hopefully tests pass, and then we can finally release this 😁. I have a ready blog post for the Flux website detailing the major improvements as well, so I can land that PR after we tag 😊. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Amazing, thanks!
Can I go ahead and tag v0.8 now? |
Yeah go for it |
This is the last PR for v0.8, and introduces just about enough documentation to ensure that users can find their way around the major parts of the repo. A large swathe of the builders remain undocumented, but that will take time and effort and I would rather get v0.8 out first and then worry about that.
cc @darsnack for suggestions in case something important has been missed.