leap-stc / leap-stc/ClimSim

Replicating Hu et al. data generation / preprocessing should be easier

Open
#103 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Jupyter Notebook
Stars
164
Forks
54
PR merge metrics
No merged PRs in 30d

Description

I am trying to replicate the data processing in Hu et al. but it's proving to be tricky. Should I be using "V4" inputs? The variables in data.utils (e.g. v4_inputs) are not actually described. For example, what are the "tm" variables, e.g. "tm_state_t_dyn"? I could not find these variables in the table of the ClimSim paper either.

Also, how do I preprocess the inputs in the same way as Hu et al. ? The only input preprocessing I found in data.utils is using a variant of min-max, but not all inputs in Hu et al. were normalized using min-max, some of used x/std and some used 1 - exp(-λx).

Should I first run ds_input = (ds_input - data.input_mean)/(data.input_max - data.input_min) and then manually preprocess select variables using the other two methods? But won´t the above command normalize everything with min-max?

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.

Research direction

Start by reading data.utils, especially the v4_inputs and tm_state_t_dyn definitions, then compare them with the Hu et al. preprocessing description and the ClimSim paper table. Document the meaning of the variables, identify the intended input version, and describe the complete preprocessing sequence so replication produces the expected inputs.

Written by the indexing model from the issue text.

Assessment

Tech stack
jupyter-notebook
Domain
data
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.