-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Documenting Pipeline Operators / Public Functions #73
Conversation
…C, SVC doc files. Needs formatting consideration, df name in example exported code
docs. Changed theme to allow for nested navigation in top bar.
…C, SVC doc files. Needs formatting consideration Updated example export code to reflect copying tpot_data
docs. Changed theme to allow for nested navigation in top bar.
Updated formatting for documentation, public func documentation for main TPOT object
…g of TPOT public functions documentation
Know what's causing that conflict? |
My mkdocs.yml was the source of the conflict. Seems resolved. |
Great start! I think the "example exported code" would also need to include the import statements for the corresponding operator, right? |
You're totally right. I reused the first part for all of the examples, and neglected to update import statements. I'll throw those in when I get a chance. |
Also please note that in #72 PCA was changed to RandomizedPCA. The operator is still named |
…edPCA. Updated RandomizedPCA Updated feature_selection and preprocessing operators.
Changes should be integrated. |
Documenting Pipeline Operators / Public Functions
Merged - thanks again! |
This is intended to be an enhancement to the documentation of the pipeline operators & public functions of the main TPOT class. Naturally this is just a first stab at formatting the pages, but hopefully we will not have to change much for the big refactor. At the very least there is some content for each of the operators & functions. I've also changed the theme and mkdocs config to help incorporate navigation to the new reference.