openclimatefix / openclimatefix/metnet

About the input data and the trained model

Open
#62 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
305
Forks
64
Avg merge
5d 4h
Merged PRs (30d)
1

Description

Hello everyone!
I would like to know what format the input data on the trained model still has. I found some information in this question #52 , but there are a number of clarifications. Is the following true for [batch, channels, timesteps, width, height]:

  1. Are the channels layers from GOES-16/18 ? (then what are these layers for the trained MetNet-2? Wind, humidity, temperature? In what order are they arranged in the tensor ?)
  2. Are the timesteps a grid that sets the prediction interval? (you can train for minutes, hours [1,3 or 6] by setting layers for these intervals [for three hours: {0, 3, 6, 9, 12, 15....}])
  3. Should the images be pre-cropped to the specified dimensions of 512x512 (256x256) and centered around the point of interest?
  4. What is the essence of the batch ? What data do they express in the input parameters? Are these pressure levels?

In general, it would be nice to make a more constructive example of running the model (what format and structure are the inputs and outputs in the trained example for MetNet-2).

Thanks in advance for the answer!

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 reviewing the clarifications in issue #52 and the linked trained MetNet-2 model. Document the input and output formats, including batch, channels, timesteps, dimensions, and an example of running the model; done means a newcomer can understand and reproduce the trained example.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, pytorch
Domain
documentation, machine-learning
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.