This is a hierarchical forecasting notebook demonstrating the use of the new hierarchical forecasting parameters for AutoML Forecasting.

If you are opening a PR for Official Notebooks under the notebooks/official folder, follow this mandatory checklist:

• [x] Use the notebook template as a starting point.
• [x] Follow the style and grammar rules outlined in the above notebook template.
• [ ] 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.
• [ ] 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 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.

Checklist for moving the notebook to the main repo:

• [x] Use the notebook template 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.
• [ ] 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 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.

If you are opening a PR for Notebooks under the official folder, follow this mandatory checklist:

• [x] Use the notebook template 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
• [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.
• [ ] This notebook has been added to the 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.

If you are opening a PR for Notebooks under the community folder:

• [ ] This notebook has been added to the CODEOWNERS file under the # Community Notebooks section, pointing to the author or the author's team.

If you are opening a PR for Community Content, and it will NOT be used on cloud.google.com/docs:

• [ ] Make sure your main Content Directory Name is descriptive, informative, and includes some of the key products and attributes of your content, so that it is differentiable from other content
• [ ] The main content directory has been added to the CODEOWNERS file under the # Community Content section, pointing to the author or the author's team.

If you are opening a PR for Community Content, and it will be used on cloud.google.com/docs:

• [ ] Make sure your main Content Directory Name is descriptive, informative, and includes some of the key products and attributes of your content, so that it is differentiable from other content
• [ ] Use the notebook template for all the notebooks in your content directory.
• [ ] Follow the style and grammar rules outlined in the above notebook template.
• [ ] Verify each notebook runs successfully in Colab since the automated tests cannot guarantee this even when it passes.
• [ ] Passes all the required automated checks
• [ ] You have consulted with a tech writer to see if tech writer review is necessary. If so, the content has been reviewed by a tech writer, and they have approved it.
• [ ] This content has been added (/moved) to the CODEOWNERS file under the # Official Community Content section (/from the # Community Content section), pointing to the author or the author's team.
• [ ] Each notebook cleans up any artifacts it has created (datasets, ML models, endpoints, etc) so as not to eat up unnecessary resources.

This PR contains a notebook which shows you how to build, deploy, and analyze predictions from a simple random forest model using tools like scikit-learn, Vertex AI, and the What-IF Tool (WIT) on a synthetic fraud transaction dataset to solve a financial fraud detection problem.

• [x] Use the notebook template 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.
• [ ] 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 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.

Adding in notebook for exploratory data analysis as part of "Data to AI" effort. See this Colab for what this notebook looks like after it is run: https://colab.research.google.com/drive/1JeNeMtj2A_5P5vo9wxSkrwHQM5JQSoAu. Submitting it with outputs shown since a lot of this about interactive visualization, which can inspire folks to use/read the notebook beyond just the code.

REQUIRED: Fill out the below checklists or remove if irrelevant

1. If you are opening a PR for Official Notebooks under the notebooks/official folder, follow this mandatory checklist:

• [x] Use the notebook template 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.
• [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 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.

If you are opening a PR for Official Notebooks under the notebooks/official folder, follow this mandatory checklist:

• [x] Use the notebook template 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.
• [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 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.

If you are opening a PR for Notebooks under the official folder, follow this mandatory checklist:

• [x] Use the notebook template 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.
• [ ] Passes all the required automated 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.
• [ ] This notebook has been added to the 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.

If you are opening a PR for Notebooks under the community folder:

• [ ] This notebook has been added to the CODEOWNERS file under the # Community Notebooks section, pointing to the author or the author's team.

If you are opening a PR for Community Content, and it will NOT be used on cloud.google.com/docs:

• [ ] Make sure your main Content Directory Name is descriptive, informative, and includes some of the key products and attributes of your content, so that it is differentiable from other content
• [ ] The main content directory has been added to the CODEOWNERS file under the # Community Content section, pointing to the author or the author's team.

If you are opening a PR for Community Content, and it will be used on cloud.google.com/docs:

• [ ] Make sure your main Content Directory Name is descriptive, informative, and includes some of the key products and attributes of your content, so that it is differentiable from other content
• [ ] Use the notebook template for all the notebooks in your content directory.
• [ ] Follow the style and grammar rules outlined in the above notebook template.
• [ ] Verify each notebook runs successfully in Colab since the automated tests cannot guarantee this even when it passes.
• [ ] Passes all the required automated checks
• [ ] You have consulted with a tech writer to see if tech writer review is necessary. If so, the content has been reviewed by a tech writer, and they have approved it.
• [ ] This content has been added (/moved) to the CODEOWNERS file under the # Official Community Content section (/from the # Community Content section), pointing to the author or the author's team.
• [ ] Each notebook cleans up any artifacts it has created (datasets, ML models, endpoints, etc) so as not to eat up unnecessary resources.

This tutorial demonstrates how to use Vertex AI for E2E MLOps on Google Cloud in production. This tutorial covers stage 1 : data management: get started with Dataflow.

• [x] Use the notebook template as a starting point.
• [x] Follow the style and grammar rules outlined in the above notebook template.
• [ ] 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.
• [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 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.

Added changes such as timestamp, removed colab references, added markup text mentioning usage of flag -q in a command for the file SDK_Custom_Container_Prediction

If you are opening a PR for Official Notebooks under the notebooks/official folder, follow this mandatory checklist:

• [x] Use the notebook template 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.
• [x] This notebook has been added to the 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.

If you are opening a PR for Official Notebooks under the notebooks/official folder, follow this mandatory checklist:

• [x] Use the notebook template 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.
• [ ] Passes all the required automated checks. You can locally test for formatting and linting with these instructions.
• [ ] 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.
• [ ] This notebook has been added to the CODEOWNERS file under # Official Notebooks section, pointing to the author or the author's team.
• [ ] The Jupyter notebook cleans up any artifacts it has created (datasets, ML models, endpoints, etc) so as not to eat up unnecessary resources.

If you are opening a PR for Community Notebooks under the notebooks/community folder:

• [ ] This notebook has been added to the CODEOWNERS file under the # Community Notebooks section, pointing to the author or the author's team.
• [ ] Passes all the required formatting and linting checks. You can locally test with these instructions.

If you are opening a PR for Community Content under the community-content folder:

• [ ] Make sure your main Content Directory Name is descriptive, informative, and includes some of the key products and attributes of your content, so that it is differentiable from other content
• [ ] The main content directory has been added to the CODEOWNERS file under the # Community Content section, pointing to the author or the author's team.
• [x] Passes all the required formatting and linting checks. You can locally test with these instructions.

Made minor changes to SDK_Custom_Training_Python_Package_Managed_Text_Dataset_Tensorflow_Serving_Container notebook

• [X] Use the notebook template 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.
• [ ] 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 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.

Expected Behavior

I expect to see in the contribution guide whether to open a PR or an issue to add a community example.

Actual Behavior

I cannot push my changes under community to another branch.

Here's the example I'd like to add https://github.com/OmaymaS/fastai_torch_models/tree/main/fastai_training_job

Add E2E notebook featuring Vertex Feature Store, Training and Prediction. This notebook is developed by our third vender, so we are committing to the community folder.

REQUIRED: Fill out the below checklists or remove if irrelevant

2. If you are opening a PR for Community Notebooks under the notebooks/community folder:

• [x] This notebook has been added to the CODEOWNERS file under the Community Notebooks section, pointing to the author or the author's team.

• [x] Passes all the required formatting and linting checks. You can locally test with these instructions.

Without this workaround, the command "from google.cloud import aiplatform as vertex_ai" fails due to the following issue:

https://github.com/googleapis/python-aiplatform/issues/1852

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.

REQUIRED: Fill out the below checklists or remove if irrelevant

1. If you are opening a PR for Official Notebooks under the notebooks/official folder, follow this mandatory checklist:

• [ ] Use the notebook template as a starting point.
• [ ] Follow the style and grammar rules outlined in the above notebook template.
• [ ] Verify the notebook runs successfully in Colab since the automated tests cannot guarantee this even when it passes.
• [ ] Passes all the required automated checks. You can locally test for formatting and linting with these instructions.
• [ ] 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.
• [ ] This notebook has been added to the CODEOWNERS file under the Official Notebooks section, pointing to the author or the author's team.
• [ ] The Jupyter notebook cleans up any artifacts it has created (datasets, ML models, endpoints, etc) so as not to eat up unnecessary resources.

2. If you are opening a PR for Community Notebooks under the notebooks/community folder:

• [ ] This notebook has been added to the CODEOWNERS file under the Community Notebooks section, pointing to the author or the author's team.
• [ ] Passes all the required formatting and linting checks. You can locally test with these instructions.

3. If you are opening a PR for Community Content under the community-content folder:

• [ ] Make sure your main Content Directory Name is descriptive, informative, and includes some of the key products and attributes of your content, so that it is differentiable from other content
• [ ] The main content directory has been added to the CODEOWNERS file under the Community Content section, pointing to the author or the author's team.
• [ ] Passes all the required formatting and linting checks. You can locally test with these instructions.

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | nbqa | ==1.5.3 -> ==1.6.0 | | | | |

Release Notes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

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.

REQUIRED: Fill out the below checklists or remove if irrelevant

1. If you are opening a PR for Official Notebooks under the notebooks/official folder, follow this mandatory checklist:

• [ ] Use the notebook template as a starting point.
• [ ] Follow the style and grammar rules outlined in the above notebook template.
• [ ] Verify the notebook runs successfully in Colab since the automated tests cannot guarantee this even when it passes.
• [ ] Passes all the required automated checks. You can locally test for formatting and linting with these instructions.
• [ ] 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.
• [ ] This notebook has been added to the CODEOWNERS file under the Official Notebooks section, pointing to the author or the author's team.
• [ ] The Jupyter notebook cleans up any artifacts it has created (datasets, ML models, endpoints, etc) so as not to eat up unnecessary resources.

2. If you are opening a PR for Community Notebooks under the notebooks/community folder:

• [ ] This notebook has been added to the CODEOWNERS file under the Community Notebooks section, pointing to the author or the author's team.
• [ ] Passes all the required formatting and linting checks. You can locally test with these instructions.

3. If you are opening a PR for Community Content under the community-content folder:

• [ ] Make sure your main Content Directory Name is descriptive, informative, and includes some of the key products and attributes of your content, so that it is differentiable from other content
• [ ] The main content directory has been added to the CODEOWNERS file under the Community Content section, pointing to the author or the author's team.
• [ ] Passes all the required formatting and linting checks. You can locally test with these instructions.

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.

REQUIRED: Fill out the below checklists or remove if irrelevant

1. If you are opening a PR for Official Notebooks under the notebooks/official folder, follow this mandatory checklist:

• [ ] Use the notebook template as a starting point.
• [ ] Follow the style and grammar rules outlined in the above notebook template.
• [ ] Verify the notebook runs successfully in Colab since the automated tests cannot guarantee this even when it passes.
• [ ] Passes all the required automated checks. You can locally test for formatting and linting with these instructions.
• [ ] 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.
• [ ] This notebook has been added to the CODEOWNERS file under the Official Notebooks section, pointing to the author or the author's team.
• [ ] The Jupyter notebook cleans up any artifacts it has created (datasets, ML models, endpoints, etc) so as not to eat up unnecessary resources.

2. If you are opening a PR for Community Notebooks under the notebooks/community folder:

• [ ] This notebook has been added to the CODEOWNERS file under the Community Notebooks section, pointing to the author or the author's team.
• [ ] Passes all the required formatting and linting checks. You can locally test with these instructions.

3. If you are opening a PR for Community Content under the community-content folder:

• [ ] Make sure your main Content Directory Name is descriptive, informative, and includes some of the key products and attributes of your content, so that it is differentiable from other content
• [ ] The main content directory has been added to the CODEOWNERS file under the Community Content section, pointing to the author or the author's team.
• [ ] Passes all the required formatting and linting checks. You can locally test with these instructions.