Add missing `Columns.Model` in `reco` processing to `VisualApp`

Open
  • Is something wrong?
#118 0 comments 0 reactions 0 assignees View on GitHub

@Adiutant is already working on this.

Since Dec 21, 2024.

  • #235 by @Adiutant — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
20/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
machine-learning

Research direction

The issue identifies missing Columns.Model handling in reco processing to VisualApp, but gives no file or test names. Start by tracing the VisualApp entry point and where reco processing reads Columns.Model; check for related tests. Done means processing uses a default model name when the column is missing. Pull request #235 is already open.

Written by the indexing model from the issue text.

Description

enhancement good first issue
Feature Description

If Columns.Model is missing in reco, the error is thrown. But we can handle this case by adding default model name

Why this feature?

More convenient for user

Additional context

No response

Dominant language
Python
Stars
457
Forks
55
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MTSWebServices/RecTools

All issues in MTSWebServices/RecTools

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.