Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Cutoff times are unique per row.

Open
  • Is something wrong?
#12 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
machine-learning

Research direction

Start by tracing the problem definition entry point where cutoff times are assigned to dataset records, then follow how those values flow into feature matrix calculation. Determine how unique cutoff times and groups of records that can share a cutoff are represented. Done means the problem definition no longer creates unnecessary per-record cutoff times and the feature matrix calculation uses the improved values.

Written by the indexing model from the issue text.

Description

enhancement

Currently, problem definition returns a cutoff time for each record in the dataset based on what problem it is. Those times can be improved using 2 methods:

  • account only for unique cutoff times.
  • group records that can share a cutoff time together.

This improvement will transcend to the calculation of the feature matrix.

Dominant language
Python
Stars
124
Forks
22
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 MLBazaar/Cardea

All issues in MLBazaar/Cardea

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.