Skip to content
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

Object detection: The data path is blank on the Train page when choosing Coco Json file. #2623

Closed
v-Hailishi opened this issue May 9, 2023 · 1 comment
Assignees
Labels
Priority:2 Work that is important, but not critical for the release Reported by: Test
Milestone

Comments

@v-Hailishi
Copy link

v-Hailishi commented May 9, 2023

System Information (please complete the following information):
Windows OS: Windows-11-Enterprise-22H2
ML.Net Model Builder 2022: 17.16.0.2325801 (Main Build)
Microsoft Visual Studio Enterprise: 2022(17.5.4)
.Net: 6.0

Describe the bug

  • On which step of the process did you run into an issue:
    The data path is blank on the Train page when choosing Coco Json file.

TestMatrix
od-cats (1).zip

To Reproduce
Steps to reproduce the behavior:

  1. Select Create a new project from the Visual Studio start window.
  2. Choose the C# Console App (.NET Core) project template.
  3. Add model builder by right click on the project.
  4. Select Object detection scenario.
  5. On the Environment page, Choose Azure.
  6. On Data page, choose the "Coco" data source.
    image
  7. On the Train page, you will see that the data path is blank.

Expected behavior
The data path should be displayed well on the Train page.

Screenshot
image

Additional context

@v-Hailishi v-Hailishi added Priority:2 Work that is important, but not critical for the release Reported by: Test labels May 9, 2023
@v-Hailishi v-Hailishi changed the title The browsing file path cannot be displayed when creating the mbconfig file for the first time after updated to the new version of Model Builder. Object detection: The data path is blank on the Train page when choosing Coco Json file. May 9, 2023
@LittleLittleCloud LittleLittleCloud self-assigned this May 15, 2023
@LittleLittleCloud LittleLittleCloud added this to the May 2023 milestone May 15, 2023
@v-Hailishi
Copy link
Author

The bug has been fixed on the latest main build 17.16.0.2326503.
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority:2 Work that is important, but not critical for the release Reported by: Test
Projects
None yet
Development

No branches or pull requests

2 participants