healthycode: move metrics computation and scoring inside SCIO pipeline

Open
#25 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
35/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
jupyter-notebook
Domain
data

Research direction

Read the health pipeline and the metrics and scoring components it currently uses; the issue does not name their files or entry points, so locate them in the repository first. The goal is to compute metrics and scores directly in the SCIO pipeline without an extra library or image. Confirm the pipeline produces the same metrics and scores after that consolidation.

Written by the indexing model from the issue text.

Description

We have too many moving parts: the metrics and scoring should be streamline to have everything in one place, directly in the health pipeline and would not need an extra library/image

Dominant language
Jupyter Notebook
Stars
1
Forks
4
Avg merge
1d 17h
Merged PRs (30d)
4

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

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 aboutcode-org/healthycode

All issues in aboutcode-org/healthycode

Similar issues

More Data Engineering issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.