AutoMLSearch: update objective string to use human-readable format
See original GitHub issue- The
get_objective(objective)
only works if the input is an Objective or a snakecase representation. - It does not work if the objective str is something like
log loss binary
orLog Loss Binary
, even those this is from the name of the Objective
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:9 (7 by maintainers)
Top Results From Across the Web
September 2020 Milestone · GitHub
Large datasets: update TV split amount, and make it configurable enhancement An ... AutoMLSearch: update objective string to use human-readable format ...
Read more >ObjC/Cocoa class for converting size to human-readable string?
Starting in OS X 10.8 and iOS 6, you can use NSByteCountFormatter. Your example would look like this:
Read more >EvalML Documentation
Graphing methods, like AutoMLSearch, on Jupyter Notebook and ... objective (Object or string) – the objective to use to make predictions.
Read more >JavaScript | Convert bytes to human-readable string
Given the size of a file(in Bytes), The task is to convert it into human-readable form using JavaScript. Here are few methods discussed....
Read more >human-readable – create user-friendly strings for byte sizes in ...
If set the returned number string is formatted to the given fixed decimal places. If not set, the default behaviour of the conversion...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@freddyaboulton ah good point about that…
I suggest we don’t add a flag for that to
get_objective
. I think we should put validation logic intoAutoMLSearch
instead, where we read in and parse the objective.If we do that validation at a lower level I think its too confusing.
@dsherry I can take this on! I like the idea of deleting
Options
in favor ofget_importable_subclasses
. I think we would need to pass in anallowed_in_automl_search
flag toget_objective
to keep the current behavior of not allowing all objectives to be used inAutoMLSearch
(unless we want to get rid of that restriction).