Delete logs/README.md
Browse files- logs/README.md +0 -20
logs/README.md
DELETED
@@ -1,20 +0,0 @@
|
|
1 |
-
# Definition of terms and hyperparameters in configs
|
2 |
-
|
3 |
-
Data-driven models are indicated by the `_s2s` suffix (e.g., `unet_s2s`). In addition, within each data-driven model, the checkpoints and hyperparameter specifications are located within the `version_xx/lightning_logs`. The hyperparameters specify the following:
|
4 |
-
|
5 |
-
- `lead_time` (default: 1): arbitrary delta_t to finetune the model, for direct approach
|
6 |
-
- `n_step` (default: 1): number of autoregressive step, s, for autoregressive approach
|
7 |
-
- `only_headline`: if false, optimize for task 1; if true for task 2
|
8 |
-
- `batch_size`: the batch size used for training
|
9 |
-
- `train_years`: list of years used for training
|
10 |
-
- `val_years`: list of years used for validation
|
11 |
-
- `epochs`: number of epoch
|
12 |
-
- `input_size`: number of input channel
|
13 |
-
- `learning_rate`: update step at each iteration
|
14 |
-
- `model_name`: the name of the model used for consistency
|
15 |
-
- `num_workers`: number of workers used in dataloader
|
16 |
-
- `output_size`: number of output channel
|
17 |
-
- `t_max`: number of cosine learning rate scheduler cycle
|
18 |
-
|
19 |
-
In addition, in all models, there is a folder named `eval`. This contains individual `.csv` files for each metric (e.g., SpecDiv, RMSE). Within each file, it contains scores for all channels in question (e.g., the entire 60 for task 1, arbitrary n for task 2, or 48 for physics-based models) across 44-day lead time.
|
20 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|