* changed according to boiler plate requirements
* ran linter test
* changed according to boilerplate requirements
* linter test
* changed file based on boilerplate requirements
* linter test
* biolerplate requirements
* linter test
* changes based on boilerplate
* linter test
* added os library
* linter test
* textual corrections
* linter test
* biolerplate chnages
* linter test
* bioler plate changes
* linter test
Co-authored-by: gcf-merge-on-green[bot] <60162190+gcf-merge-on-green[bot]@users.noreply.github.com>
**REQUIRED:** Add a summary of your PR here, typically including why the change is needed and what was changed. Include any design alternatives for discussion purposes.
Hardcoded gcpc version because it fails in newer versions. And this is a request from model eval swe team to hardcode the version.
**REQUIRED:** Fill out the below checklists or remove if irrelevant
1. If you are opening a PR for `Official Notebooks` under the [notebooks/official](https://togithub.com/GoogleCloudPlatform/vertex-ai-samples/tree/main/notebooks/official) folder, follow this mandatory checklist:
- [x] Use the [notebook template](https://togithub.com/GoogleCloudPlatform/vertex-ai-samples/blob/main/notebooks/notebook_template.ipynb) as a starting point.
- [x] Follow the style and grammar rules outlined in the above notebook template.
- [x] Verify the notebook runs successfully in Colab since the automated tests cannot guarantee this even when it passes.
- [x] Passes all the required automated checks. You can locally test for formatting and linting with these [instructions](https://togithub.com/GoogleCloudPlatform/vertex-ai-samples/blob/main/CONTRIBUTING.md#code-quality-checks).
- [x] You have consulted with a tech writer to see if tech writer review is necessary. If so, the notebook has been reviewed by a tech writer, and they have approved it.
- [x] This notebook has been added to the [CODEOWNERS](https://togithub.com/GoogleCloudPlatform/vertex-ai-samples/blob/main/notebooks/official/CODEOWNERS) file under the `Official Notebooks` section, pointing to the author or the author's team.
- [x] The Jupyter notebook cleans up any artifacts it has created (datasets, ML models, endpoints, etc) so as not to eat up unnecessary resources.
**Error from regression test**:RuntimeError: Job failed with:
code: 9
message: "The DAG failed because some tasks failed. The failed tasks are: [model-deploy].; Job (project_id = python-docs-samples-tests, job_id = 2073372166241386496) is failed due to the above error.; Failed to handle the job: {project_number = 1012616486416, job_id = 2073372166241386496}"
Changes made:
Just ran notebook in local. It ran fine. Updated notebook according to template
- [X] Use the [notebook template](https://togithub.com/GoogleCloudPlatform/vertex-ai-samples/blob/main/notebooks/notebook_template.ipynb) as a starting point.
- [X] Follow the style and grammar rules outlined in the above notebook template.
- [X] Verify the notebook runs successfully in Colab since the automated tests cannot guarantee this even when it passes.
- [X] Passes all the required automated checks. You can locally test for formatting and linting with these [instructions](https://togithub.com/GoogleCloudPlatform/vertex-ai-samples/blob/main/CONTRIBUTING.md#code-quality-checks).
- [ ] You have consulted with a tech writer to see if tech writer review is necessary. If so, the notebook has been reviewed by a tech writer, and they have approved it.
- [X] This notebook has been added to the [CODEOWNERS](https://togithub.com/GoogleCloudPlatform/vertex-ai-samples/blob/main/notebooks/official/CODEOWNERS) file under the `Official Notebooks` section, pointing to the author or the author's team.
- [X] The Jupyter notebook cleans up any artifacts it has created (datasets, ML models, endpoints, etc) so as not to eat up unnecessary resources.
<br>
Reduce boilerplate for sdk-custom-image-classification-online.ipynb notebook
- [X] Use the [notebook template](https://togithub.com/GoogleCloudPlatform/vertex-ai-samples/blob/main/notebooks/notebook_template.ipynb) as a starting point.
- [X] Follow the style and grammar rules outlined in the above notebook template.
- [X] Verify the notebook runs successfully in Colab since the automated tests cannot guarantee this even when it passes.
- [X] Passes all the required automated checks. You can locally test for formatting and linting with these [instructions](https://togithub.com/GoogleCloudPlatform/vertex-ai-samples/blob/main/CONTRIBUTING.md#code-quality-checks).
- [ ] You have consulted with a tech writer to see if tech writer review is necessary. If so, the notebook has been reviewed by a tech writer, and they have approved it.
- [X] This notebook has been added to the [CODEOWNERS](https://togithub.com/GoogleCloudPlatform/vertex-ai-samples/blob/main/notebooks/official/CODEOWNERS) file under the `Official Notebooks` section, pointing to the author or the author's team.
- [X] The Jupyter notebook cleans up any artifacts it has created (datasets, ML models, endpoints, etc) so as not to eat up unnecessary resources.
<br>
**REQUIRED:** Add a summary of your PR here, typically including why the change is needed and what was changed. Include any design alternatives for discussion purposes.
<br>
1. Boilerplate changes.
2. Added code for deleting experiment otherwise its throwing experiment name already exist.
<br><br><br>
**REQUIRED:** Fill out the below checklists or remove if irrelevant
1. If you are opening a PR for `Official Notebooks` under the [notebooks/official](https://togithub.com/GoogleCloudPlatform/vertex-ai-samples/tree/main/notebooks/official) folder, follow this mandatory checklist:
- [X] Use the [notebook template](https://togithub.com/GoogleCloudPlatform/vertex-ai-samples/blob/main/notebooks/notebook_template.ipynb) as a starting point.
- [X] Follow the style and grammar rules outlined in the above notebook template.
- [X] Verify the notebook runs successfully in Colab since the automated tests cannot guarantee this even when it passes.
- [X] Passes all the required automated checks. You can locally test for formatting and linting with these [instructions](https://togithub.com/GoogleCloudPlatform/vertex-ai-samples/blob/main/CONTRIBUTING.md#code-quality-checks).
- [ ] You have consulted with a tech writer to see if tech writer review is necessary. If so, the notebook has been reviewed by a tech writer, and they have approved it.
- [X] This notebook has been added to the [CODEOWNERS](https://togithub.com/GoogleCloudPlatform/vertex-ai-samples/blob/main/notebooks/official/CODEOWNERS) file under the `Official Notebooks` section, pointing to the author or the author's team.
- [X] The Jupyter notebook cleans up any artifacts it has created (datasets, ML models, endpoints, etc) so as not to eat up unnecessary resources.
<br>
**REQUIRED:** Add a summary of your PR here, typically including why the change is needed and what was changed. Include any design alternatives for discussion purposes.
<br>
Boilerplate changes.
<br><br><br>
**REQUIRED:** Fill out the below checklists or remove if irrelevant
1. If you are opening a PR for `Official Notebooks` under the [notebooks/official](https://togithub.com/GoogleCloudPlatform/vertex-ai-samples/tree/main/notebooks/official) folder, follow this mandatory checklist:
- [X] Use the [notebook template](https://togithub.com/GoogleCloudPlatform/vertex-ai-samples/blob/main/notebooks/notebook_template.ipynb) as a starting point.
- [X] Follow the style and grammar rules outlined in the above notebook template.
- [X] Verify the notebook runs successfully in Colab since the automated tests cannot guarantee this even when it passes.
- [X] Passes all the required automated checks. You can locally test for formatting and linting with these [instructions](https://togithub.com/GoogleCloudPlatform/vertex-ai-samples/blob/main/CONTRIBUTING.md#code-quality-checks).
- [ ] You have consulted with a tech writer to see if tech writer review is necessary. If so, the notebook has been reviewed by a tech writer, and they have approved it.
- [X] This notebook has been added to the [CODEOWNERS](https://togithub.com/GoogleCloudPlatform/vertex-ai-samples/blob/main/notebooks/official/CODEOWNERS) file under the `Official Notebooks` section, pointing to the author or the author's team.
- [X] The Jupyter notebook cleans up any artifacts it has created (datasets, ML models, endpoints, etc) so as not to eat up unnecessary resources.
<br>
* Update notebooks/official/matching_engine/README.md
* Update region tag formatting
* Update README.md format for single notebook
* Remove horizontal-rules for single notebook
* adds the custom tabular classification evaluation notebook
* removes json import
* ran linter test
* fixes the model serving code and adds image
* ran linter test
* adds notebook to the codeowners file
* addresses the review comments: updates text, adds headings
* ran linter test
* boiler-plate reduction, addresses the review comments, adds a constant for table id
* ran linter test
* updates the installation step
* ran linter test
* removes the --user flag while installation
* ran linter test
Co-authored-by: Soheila Zangeneh <49654056+soheilazangeneh@users.noreply.github.com>
Checklist for moving the notebook to the main repo:
- [x] Use the [notebook template](https://togithub.com/GoogleCloudPlatform/vertex-ai-samples/blob/main/notebooks/notebook_template.ipynb) as a starting point.
- [x] Follow the style and grammar rules outlined in the above notebook template.
- [x] Verify the notebook runs successfully in Colab since the automated tests cannot guarantee this even when it passes.
- [x] Passes all the required automated checks. You can locally test for formatting and linting with these [instructions](https://togithub.com/GoogleCloudPlatform/vertex-ai-samples/blob/main/docs/contributing.md#code-quality-checks).
- [ ] You have consulted with a tech writer to see if tech writer review is necessary. If so, the notebook has been reviewed by a tech writer, and they have approved it.
- [x] This notebook has been added to the [CODEOWNERS](https://togithub.com/GoogleCloudPlatform/vertex-ai-samples/blob/main/docs/CODEOWNERS) file under `# Official Notebooks` section, pointing to the author or the author's team.
- [x] The Jupyter notebook cleans up any artifacts it has created (datasets, ML models, endpoints, etc) so as not to eat up unnecessary resources.
* text correction made
* ran linter
* modified file
* ran linter
* updated file
* ran linter
* addressed comments
* ran linte
* changing component and parameter names as per new gcpc 1.0.26
* ran linter
* updated notebook as per new package changes
* modified notebook
* ran linter
Co-authored-by: Soheila Zangeneh <49654056+soheilazangeneh@users.noreply.github.com>
Co-authored-by: Andrew Ferlitsch <aferlitsch@google.com>
* Cloud Storage bucket permission issues resolved
* Cloud Storage bucket permission issues resolved
* ran linter test
* DAG issues
* linter test
* textual corrections
* ran linter test
* added service account for pipeline job
* ran linter test
Co-authored-by: Andrew Ferlitsch <aferlitsch@google.com>
* added model evaluation component
* linter test cases
* linter test cases
* model_name param issues resolved
* linter test case
* import issues resloved
* linter test cases
* made review changes
* made review changes
* ran linter test
* made review changes
* made review changes
* made review changes
* linter test
* ran linter test
* made review changes
* ran linter test
* made review changes
* ran linter test
* linter test
* review changes
* ran linter test
* added The links for Colab, Github and Workbench
* added The links for Colab, Github and Workbench
* ran linter test
* added The links for Colab, Github and Workbench
* ran linter test
* added The links for Colab, Github and Workbench
* ran linter test
* notebook title changed
* ran linter test
* text changes and made review changes
* ran linter test
* made review changes
* linter test
* made review changes
* linter test
* content changes
* ran linter test
* textual corrections and links
* ran linter test
* changed function names bases on latest gcpc version
* ran linter test
* changed function names bases on latest gcpc version
* linter test
* ran linter test
* updated arguments in ModelEvaluationClassificationOp based on new version
* ran linter test
Co-authored-by: Ivan Cheung <ivans.mailbox@gmail.com>
Co-authored-by: Andrew Ferlitsch <aferlitsch@google.com>
Co-authored-by: Soheila Zangeneh <49654056+soheilazangeneh@users.noreply.github.com>
* adds the custom-model-bq-io-batch-prediction-pipeline notebook to the official folder
* removes the unused libraries and variables
* ran linter test
* adds a raise exception statement to prevent auto-test check as this notebook is just to serve as a template
* resolves review comments: fixes names, removes trailing comma, fixes link format
* removes the raise excpetion step
* ran linter test
* cleans up code, explains sections and renames the notebook
* removes unused variable batch_predict_task
* removes unnecessary imports
* ran linter test
* updates the dependencies
* ran linter test
Co-authored-by: Andrew Ferlitsch <aferlitsch@google.com>
* file modified
* ran linter
* model evaluation metrics are printed
* ran linter
* notebook modified
* ran linter
Co-authored-by: Andrew Ferlitsch <aferlitsch@google.com>
* upgrades gcpc to latest, adds minor textual corrections
* ran linter test
* minor textual corrections
* ran linter test
* fixes sentence cases, unnecessary capitalizations, article corrections and sentence corrections
* ran linter test
* renames the ground_truth_column argument in classificationeval component to target_field_name as per version 1.0.26 and updates the reference link
* ran linter test
* upgrades gcpc to latest, adds minor textual corrections
* ran linter test
* minor textual corrections
* ran linter test
* fixes sentence cases, unnecessary capitalizations, article corrections and sentence corrections
* ran linter test
* renames the ground_truth_column argument in classificationeval component to target_field_name as per version 1.0.26 and updates the reference link
* ran linter test
* fixes the prediction_score_column unsupported error, adds class_labels field, adds the targetfieldremover component, minor structural/textual updates
* ran linter test & updates the image
* removes unnecessary newline
* ran linter test
Co-authored-by: Soheila Zangeneh <49654056+soheilazangeneh@users.noreply.github.com>
Co-authored-by: Andrew Ferlitsch <aferlitsch@google.com>
* Custom pytorch text sentiment classification
* Ran linter test
* Added creating predictor directory
* ran linter test
* Creating python package files from the notebook
* Ran linter test
* cleans up the pytorch-text-classification notebook, renames the directory and removes unnecessary files
* ran linter test
* rectifies the python test version
* ran linter test
* removes the python version line
* ran linter test
* restores the README.md file for official folder
* minor textual edits
* ran linter test
* updates notebook structure, removes unnecessary print statements, moves import statements to one cell, textual updates
* ran linter test
* corrects the Colab link
* ran linter test
* addresses review comments: grammatical/textual corrections
* ran linter test
Co-authored-by: krishr2d2 <krishna.movva@springml.com>
Co-authored-by: Andrew Ferlitsch <aferlitsch@google.com>
* Made Minor changes
* Ran Linter test
* Made minor changes
* ran linter test
* Madesome Minor changes
* Ran linter test
* Made some minor changes
* Ran linter test
Co-authored-by: Andrew Ferlitsch <aferlitsch@google.com>
* added uuid and textual correction
* ran linter test
* made one cell for pip installations
* ran linter test
Co-authored-by: Andrew Ferlitsch <aferlitsch@google.com>
* made text corrections
* ran linter
* modified notebook
* modified notebook
* ran linter
* modified installation step
* ran linter
* updated component name and parameters
* ran linter
* ran linter
Co-authored-by: Soheila Zangeneh <49654056+soheilazangeneh@users.noreply.github.com>
Co-authored-by: Andrew Ferlitsch <aferlitsch@google.com>
* updates featurestore name with uuid to avoid name collisions, elaboration, textual corrections
* ran linter test
* addresses review comments: adds headings + textual corrections
* ran linter test
Co-authored-by: Andrew Ferlitsch <aferlitsch@google.com>
