AutoML doesn't use the default namespace of the project
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- csharp
- Domain
- machine-learning
Research direction
Start by tracing the AutoML class-generation step after Train/Evaluate and compare the generated namespace with the project's default namespace from project properties. Reproduce the listed workflow and inspect the generated classes. Done when they use the project's default namespace with dots and remain compatible with partial extensions.
Written by the indexing model from the issue text.
Description
System Information (please complete the following information):
- Model Builder Version (available in Manage Extensions dialog): 17.19.2.2511501
- Visual Studio Version : 17.14.9
Describe the bug
- On which step of the process did you run into an issue: Train/Evaluate
- Clear description of the problem:
When generating classes, AutoML doens't use the default namespace of the project, but uses the name of the project and replace the dots with underscore
To Reproduce
Steps to reproduce the behavior:
- Create a new model, specify the data and train the model
- Click on next, it will generate the classes for the model and asks for a reload of the project
- The classes generated contain the wrong namespace
Expected behavior
Expected behaviour is to use the default namespace as defined in the project properties
Additional context
Not a blocking issue, just a cohesive thing. By default, in .Net, namespaces don't contain underscores, they contain dots. And if we want to extend the generated classes, we can create our own file to add additionnal properties/methods (thanks to the usage of partial classes) to our model. But the namespace in that file is the default namespace, whereas the generated classes by AutoML is not.
- Dominant language
- Dockerfile
- Stars
- 285
- Forks
- 66
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dotnet/machinelearning-modelbuilder
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 10/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
dotnet/machinelearning-modelbuilder#3087 · 4 comments ·
-
GS Tutorial
Difficulty 4/5 3-5 days Newbie friendliness 35/100
dotnet/machinelearning-modelbuilder#3085 · 2 comments ·
-
y Open
Difficulty 5/5 Over a week Newbie friendliness 10/100
All issues in dotnet/machinelearning-modelbuilder
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
vllm-project/vllm#57974 · 4 comments ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
torchgeo/torchgeo-bench#400 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
open-compass/VLMEvalKit#1698 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100