Shorten results output in docs#3328
Conversation
Codecov Report
@@ Coverage Diff @@
## main #3328 +/- ##
=======================================
- Coverage 99.7% 99.0% -0.6%
=======================================
Files 327 327
Lines 31840 31840
=======================================
- Hits 31715 31494 -221
- Misses 125 346 +221
Continue to review full report at Codecov.
|
freddyaboulton
left a comment
There was a problem hiding this comment.
Thanks @bchen1116 ! This looks good to me. If we decide we need a pprint call in more places in the docs we can invest in trying to find a way to apply the pretty-printing automatically.
| "source": [ | ||
| "automl.results" | ||
| "import pprint\n", | ||
| "pp = pprint.PrettyPrinter(indent=0, width=100, depth=3, compact=True, sort_dicts=False)\n", |
There was a problem hiding this comment.
could we set depth=2 and then showcase just one pipelines results with:
automl.results['pipeline_results'][0]? I still think the output is rather long and takes multiple scrolls to get through.
There was a problem hiding this comment.
ah true that doesn't look the best.. lmk if adding more information will make it better but def not blocking!
angela97lin
left a comment
There was a problem hiding this comment.
Thanks @bchen1116! Agreed with @freddyaboulton that it could be a good idea to do this automagically if we run into it more in the future but this is great 😁


fix #3032
Rather than editing the output of the results themselves, I figured the better approach would be to truncate the cell output for this.
https://feature-labs-inc-evalml--3328.com.readthedocs.build/en/3328/user_guide/automl.html#Access-raw-results