Postprocessing requires utility bills

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

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
ruby
Domain
data

Research direction

Start by locating the postprocessing entry point and the dataset handling that currently requires utility bills. Make utility bills optional while preserving postprocessing for datasets without them, and verify that unnecessary utility-bill data is no longer required for typical analyses.

Written by the indexing model from the issue text.

Description

postprocessing

Postprocessing requires utility bills in the dataset. Remove this dependence and make it optional, as utility bills at a lot to output data that is unnecessary for most analysis questions.

Dominant language
Ruby
Stars
54
Forks
28
Avg merge
3d 23h
Merged PRs (30d)
5

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a 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 NatLabRockies/ComStock

All issues in NatLabRockies/ComStock

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.