Warm/cold/hot scenarios for cross-validation and splitters

Open
#99 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python

Research direction

The issue does not name files, tests, or an entry point. Start by reading the validation pipeline and cross-validation and splitter APIs to find where warm, cold, and hot scenarios would fit. The issue gives no acceptance criteria, so the expected behavior and definition of done need clarification.

Written by the indexing model from the issue text.

Description

enhancement
Feature Description

Support for different scenarios in our validation pipelines

Why this feature?

Real world challenge

Additional context

No response

Dominant language
Python
Stars
457
Forks
55
PR merge metrics
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.