-
-
Notifications
You must be signed in to change notification settings - Fork 212
Feature #753 #932
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
Merged
Merged
Feature #753 #932
Changes from all commits
Commits
Show all changes
37 commits
Select commit
Hold shift + click to select a range
b3b7867
Create first section: Creating Custom Flow
PGijsbers 19d79d7
Add Section: Using the Flow
PGijsbers 208f6cd
Allow run description text to be custom
PGijsbers 2247bbc
Draft for Custom Flow tutorial
PGijsbers 326510c
Add minimal docstring to OpenMLRun
PGijsbers 872bd75
Process code review feedback
PGijsbers c3a5326
Use the format utility function in automatic runs
PGijsbers a7cb290
Process @mfeurer feedback
PGijsbers e5dcaf0
Rename arguments of list_evaluations (#933)
Bilgecelik 1670050
adding config file to user guide (#931)
marcoslbueno 9c93f5b
Edit api (#935)
sahithyaravi 666ca68
Adding support for scikit-learn > 0.22 (#936)
Neeratyoy 5d9c69c
Add flake8-print in pre-commit (#939)
22quinn 7d51a76
Fix edit api (#940)
sahithyaravi 75a5440
Update subflow paragraph
PGijsbers 23a08ab
Check the ClassificationTask has class label set
PGijsbers 95d1fcb
Test task is of supported type
PGijsbers 41aa789
Add tests for format_prediction
PGijsbers 5d2e0ce
Adding Python 3.8 support (#916)
Neeratyoy 5ef24ab
Process feedback Neeratyoy
PGijsbers 1ce5a12
Test Exception with Regex
PGijsbers f70c720
change edit_api to reflect server (#941)
sahithyaravi f8839de
Create first section: Creating Custom Flow
PGijsbers 2a6903b
Add Section: Using the Flow
PGijsbers 4802497
Allow run description text to be custom
PGijsbers 7fb64b4
Draft for Custom Flow tutorial
PGijsbers a6f0a38
Add minimal docstring to OpenMLRun
PGijsbers 3748ae0
Process code review feedback
PGijsbers 5479d7b
Use the format utility function in automatic runs
PGijsbers 4b71c30
Process @mfeurer feedback
PGijsbers 942d66e
Update subflow paragraph
PGijsbers 9ba363e
Check the ClassificationTask has class label set
PGijsbers a72053d
Test task is of supported type
PGijsbers de31490
Add tests for format_prediction
PGijsbers 832f437
Process feedback Neeratyoy
PGijsbers 3cc74de
Test Exception with Regex
PGijsbers 03e1e8b
Merge branch 'feature_#753' of https://github.com/openml/openml-pytho…
PGijsbers File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,205 @@ | ||
| """ | ||
| ================================ | ||
| Creating and Using a Custom Flow | ||
| ================================ | ||
|
|
||
| The most convenient way to create a flow for your machine learning workflow is to generate it | ||
| automatically as described in the `Obtain Flow IDs <https://openml.github.io/openml-python/master/examples/30_extended/flow_id_tutorial.html#sphx-glr-examples-30-extended-flow-id-tutorial-py>`_ tutorial. # noqa E501 | ||
| However, there are scenarios where this is not possible, such | ||
| as when the flow uses a framework without an extension or when the flow is described by a script. | ||
|
|
||
| In those cases you can still create a custom flow by following the steps of this tutorial. | ||
| As an example we will use the flows generated for the `AutoML Benchmark <https://openml.github.io/automlbenchmark/>`_, | ||
| and also show how to link runs to the custom flow. | ||
| """ | ||
|
|
||
| #################################################################################################### | ||
|
|
||
| # License: BSD 3-Clause | ||
| # .. warning:: This example uploads data. For that reason, this example | ||
| # connects to the test server at test.openml.org. This prevents the main | ||
| # server from crowding with example datasets, tasks, runs, and so on. | ||
| from collections import OrderedDict | ||
| import numpy as np | ||
|
|
||
| import openml | ||
| from openml import OpenMLClassificationTask | ||
| from openml.runs.functions import format_prediction | ||
|
|
||
| openml.config.start_using_configuration_for_example() | ||
|
|
||
| #################################################################################################### | ||
| # 1. Defining the flow | ||
| # ==================== | ||
| # The first step is to define all the hyperparameters of your flow. | ||
| # The API pages feature a descriptions of each variable of the `OpenMLFlow <https://openml.github.io/openml-python/master/generated/openml.OpenMLFlow.html#openml.OpenMLFlow>`_. # noqa E501 | ||
| # Note that `external version` and `name` together uniquely identify a flow. | ||
| # | ||
| # The AutoML Benchmark runs AutoML systems across a range of tasks. | ||
| # OpenML stores Flows for each AutoML system. However, the AutoML benchmark adds | ||
| # preprocessing to the flow, so should be described in a new flow. | ||
| # | ||
| # We will break down the flow arguments into several groups, for the tutorial. | ||
| # First we will define the name and version information. | ||
| # Make sure to leave enough information so others can determine exactly which | ||
| # version of the package/script is used. Use tags so users can find your flow easily. | ||
|
|
||
| general = dict( | ||
| name="automlbenchmark_autosklearn", | ||
| description=( | ||
| "Auto-sklearn as set up by the AutoML Benchmark" | ||
| "Source: https://github.com/openml/automlbenchmark/releases/tag/v0.9" | ||
| ), | ||
| external_version="amlb==0.9", | ||
| language="English", | ||
| tags=["amlb", "benchmark", "study_218"], | ||
| dependencies="amlb==0.9", | ||
| ) | ||
|
|
||
| #################################################################################################### | ||
| # Next we define the flow hyperparameters. We define their name and default value in `parameters`, | ||
| # and provide meta-data for each hyperparameter through `parameters_meta_info`. | ||
| # Note that even though the argument name is `parameters` they describe the hyperparameters. | ||
| # The use of ordered dicts is required. | ||
|
|
||
| flow_hyperparameters = dict( | ||
| parameters=OrderedDict(time="240", memory="32", cores="8"), | ||
| parameters_meta_info=OrderedDict( | ||
| cores=OrderedDict(description="number of available cores", data_type="int"), | ||
| memory=OrderedDict(description="memory in gigabytes", data_type="int"), | ||
| time=OrderedDict(description="time in minutes", data_type="int"), | ||
| ), | ||
| ) | ||
|
|
||
| #################################################################################################### | ||
| # It is possible to build a flow which uses other flows. | ||
| # For example, the Random Forest Classifier is a flow, but you could also construct a flow | ||
| # which uses a Random Forest Classifier in a ML pipeline. When constructing the pipeline flow, | ||
| # you can use the Random Forest Classifier flow as a *subflow*. It allows for | ||
| # all hyperparameters of the Random Classifier Flow to also be specified in your pipeline flow. | ||
| # | ||
| # In this example, the auto-sklearn flow is a subflow: the auto-sklearn flow is entirely executed as part of this flow. | ||
| # This allows people to specify auto-sklearn hyperparameters used in this flow. | ||
| # In general, using a subflow is not required. | ||
| # | ||
| # Note: flow 15275 is not actually the right flow on the test server, | ||
| # but that does not matter for this demonstration. | ||
|
|
||
| autosklearn_flow = openml.flows.get_flow(15275) # auto-sklearn 0.5.1 | ||
| subflow = dict(components=OrderedDict(automl_tool=autosklearn_flow),) | ||
Neeratyoy marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
|
||
| #################################################################################################### | ||
| # With all parameters of the flow defined, we can now initialize the OpenMLFlow and publish. | ||
| # Because we provided all the details already, we do not need to provide a `model` to the flow. | ||
| # | ||
| # In our case, we don't even have a model. It is possible to have a model but still require | ||
| # to follow these steps when the model (python object) does not have an extensions from which | ||
| # to automatically extract the hyperparameters. | ||
| # So whether you have a model with no extension or no model at all, explicitly set | ||
| # the model of the flow to `None`. | ||
|
|
||
| autosklearn_amlb_flow = openml.flows.OpenMLFlow( | ||
| **general, **flow_hyperparameters, **subflow, model=None, | ||
| ) | ||
| autosklearn_amlb_flow.publish() | ||
| print(f"autosklearn flow created: {autosklearn_amlb_flow.flow_id}") | ||
|
|
||
| #################################################################################################### | ||
| # 2. Using the flow | ||
| # ==================== | ||
| # This Section will show how to upload run data for your custom flow. | ||
| # Take care to change the values of parameters as well as the task id, | ||
| # to reflect the actual run. | ||
| # Task and parameter values in the example are fictional. | ||
|
|
||
| flow_id = autosklearn_amlb_flow.flow_id | ||
|
|
||
| parameters = [ | ||
| OrderedDict([("oml:name", "cores"), ("oml:value", 4), ("oml:component", flow_id)]), | ||
| OrderedDict([("oml:name", "memory"), ("oml:value", 16), ("oml:component", flow_id)]), | ||
| OrderedDict([("oml:name", "time"), ("oml:value", 120), ("oml:component", flow_id)]), | ||
| ] | ||
|
|
||
| task_id = 1408 # Iris Task | ||
| task = openml.tasks.get_task(task_id) | ||
| dataset_id = task.get_dataset().dataset_id | ||
|
|
||
|
|
||
| #################################################################################################### | ||
| # The last bit of information for the run we need are the predicted values. | ||
Bilgecelik marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| # The exact format of the predictions will depend on the task. | ||
| # | ||
| # The predictions should always be a list of lists, each list should contain: | ||
| # - the repeat number: for repeated evaluation strategies. (e.g. repeated cross-validation) | ||
| # - the fold number: for cross-validation. (what should this be for holdout?) | ||
| # - 0: this field is for backward compatibility. | ||
| # - index: the row (of the original dataset) for which the prediction was made. | ||
| # - p_1, ..., p_c: for each class the predicted probability of the sample | ||
| # belonging to that class. (no elements for regression tasks) | ||
| # Make sure the order of these elements follows the order of `task.class_labels`. | ||
| # - the predicted class/value for the sample | ||
| # - the true class/value for the sample | ||
| # | ||
| # When using openml-python extensions (such as through `run_model_on_task`), | ||
| # all of this formatting is automatic. | ||
| # Unfortunately we can not automate this procedure for custom flows, | ||
| # which means a little additional effort is required. | ||
Neeratyoy marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| # | ||
| # Here we generated some random predictions in place. | ||
| # You can ignore this code, or use it to better understand the formatting of the predictions. | ||
| # | ||
| # Find the repeats/folds for this task: | ||
| n_repeats, n_folds, _ = task.get_split_dimensions() | ||
| all_test_indices = [ | ||
| (repeat, fold, index) | ||
| for repeat in range(n_repeats) | ||
| for fold in range(n_folds) | ||
| for index in task.get_train_test_split_indices(fold, repeat)[1] | ||
| ] | ||
|
|
||
| # random class probabilities (Iris has 150 samples and 3 classes): | ||
| r = np.random.rand(150 * n_repeats, 3) | ||
| # scale the random values so that the probabilities of each sample sum to 1: | ||
| y_proba = r / r.sum(axis=1).reshape(-1, 1) | ||
| y_pred = y_proba.argmax(axis=1) | ||
|
|
||
| class_map = dict(zip(range(3), task.class_labels)) | ||
| _, y_true = task.get_X_and_y() | ||
| y_true = [class_map[y] for y in y_true] | ||
|
|
||
| # We format the predictions with the utility function `format_prediction`. | ||
| # It will organize the relevant data in the expected format/order. | ||
| predictions = [] | ||
| for where, y, yp, proba in zip(all_test_indices, y_true, y_pred, y_proba): | ||
| repeat, fold, index = where | ||
|
|
||
| prediction = format_prediction( | ||
| task=task, | ||
| repeat=repeat, | ||
| fold=fold, | ||
| index=index, | ||
| prediction=class_map[yp], | ||
| truth=y, | ||
| proba={c: pb for (c, pb) in zip(task.class_labels, proba)}, | ||
| ) | ||
| predictions.append(prediction) | ||
|
|
||
| #################################################################################################### | ||
| # Finally we can create the OpenMLRun object and upload. | ||
| # We use the argument setup_string because the used flow was a script. | ||
|
|
||
| benchmark_command = f"python3 runbenchmark.py auto-sklearn medium -m aws -t 119" | ||
| my_run = openml.runs.OpenMLRun( | ||
| task_id=task_id, | ||
| flow_id=flow_id, | ||
| dataset_id=dataset_id, | ||
| parameter_settings=parameters, | ||
| setup_string=benchmark_command, | ||
| data_content=predictions, | ||
| tags=["study_218"], | ||
| description_text="Run generated by the Custom Flow tutorial.", | ||
| ) | ||
| my_run.publish() | ||
| print("run created:", my_run.run_id) | ||
PGijsbers marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
|
||
| openml.config.stop_using_configuration_for_example() | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.