JuliaAI / JuliaAI/MLJModelInterface.jl
human_name vs Base.nameof
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 39
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
I am wondering on the relationship (or lack there of) between Base.nameof and MMI.human_name.
Should Base.nameof on model instances fall back to MMI.human_name?
It is the function i tried to use first when i wanted a name for a model instance
The ModelingToolkit ecosystem uses Base.nameof to provide names for things.
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.
Research direction
Start by reviewing the definitions and current uses of Base.nameof and MMI.human_name in MLJModelInterface.jl, then inspect how model-instance names are consumed across the MLJ and ModelingToolkit ecosystems. Done requires an agreed relationship between the two naming functions and a documented or tested behavior for model instances.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100