Dataset File Coverage Functionality Required

Open
#68 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
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
data-engineering

Research direction

Start by tracing the PostProcessing workflow and how the dataset_spec Start and End simulation years and months are read. Define the standalone assessment utility around detecting both under- and over-availability of datafiles, including support for past publications. Done means the utility can assess a dataset independently and report whether its files cover the specified range.

Written by the indexing model from the issue text.

Description

PostProcessing tolerates neither under- nor over-availability of datafiles, with respect to the Start and End sim-years/months defined in the dataset_spec. Although we need to address this issue as part of the warehouse automation, we also need the ability to support a standalone utility for such assessment, to address past publications and their amenability to support postprocessing.

Dominant language
Python
Stars
0
Forks
2
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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 E3SM-Project/datasm

All issues in E3SM-Project/datasm

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.