fix object detection notebook example on dataset fetch in build CI and improve header documentation #2424
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.
Description
The object detection notebook with RAI was just merged. When trying to add another notebook example, I found that the object detection notebook started failing when registering a dataset, because it was already registered in a previous run against the test workspace used:
Link to build failure:
https://github.com/Azure/azureml-examples/actions/runs/5446414448/jobs/9907120291?pr=2423
To fix this build issue, the notebook should be following the logic of other notebooks, which is to have a try/except around the dataset fetch logic and simply get the dataset if it already exists in the test workspace instead of trying to add it.
In addition to the fix for the notebook CI test failures, I also added a title and documentation header at the top of the notebook similar to the other RAI notebooks to be consistent.
Checklist