-[Contributors and contact](#contributors-and-contact)
-[On-going work](#on-going-work)
...
...
@@ -171,7 +169,6 @@ Now it is time to run the AMBS workflow
2. Data Preprocessing: Crop the ERA 5-data (multiple years possible) to the region of interest (preprocesing step 1),
The TFrecord-files which are fed to the trained model (next workflow step) are created afterwards. Thus, two cases exist at this stage:
* **ERA 5 data**
```bash
[sbatch] ./preprocess_data_era5_step1.sh
[sbatch] ./preprocess_data_era5_step2.sh
...
...
@@ -179,7 +176,7 @@ The TFrecord-files which are fed to the trained model (next workflow step) are c
3. Training: Training of one of the available models with the preprocessed data.
Note that the `exp_id` is generated automatically when running `generate_runscript.py`.
***ERA 5 data**
```bash
[sbatch] ./train_model_era5_<exp_id>.sh
```
...
...
@@ -187,7 +184,7 @@ Note that the `exp_id` is generated automatically when running `generate_runscri
4. Postprocess: Create some plots and calculate the evaluation metrics for test dataset. <br>
Note that the `exp_id` is generated automatically when running `generate_runscript.py`.
* **ERA 5 data**
```bash
[sbatch] ./visualize_postprocess_era5_<exp_id>.sh
```
...
...
@@ -199,9 +196,26 @@ AMBS also provide the tool (called met_postprocess) for the users to compare dif
### Input and Output folder structure and naming convention
To succesfully runt the workflow and enable to track the result from each step, inputs and output directories, and the file name convention should be constructed as below:
The example of inputs structure for ERA5 dataset. In detail, the data is recoredly hourly and stored into two grib files. The file with postfix `*_ml.grb` consists of multi layers of the variables, whereas `_sf.grb` only include the surface data.
```
├── ERA5 dataset
│ ├── [Year]
│ │ ├── [Month]
│ │ │ ├── *_ml.grb
│ │ │ ├── *_sf.grb
│ │ │ ├── ...
│ │ ├── [Month]
│ │ │ ├── *_ml.grb
│ │ │ ├── *_sf.grb
│ │ │ ├── ...
The details can be found [name_convention](docs/structure_name_convention.md)
```
The root output directory should be set up when you run the workflow at the first time as aformentioned
The output strucutre for each step of the workflow along with the file name convention are described below:
```
├── ExtractedData
│ ├── [Year]
...
...
@@ -210,32 +224,69 @@ The details can be found [name_convention](docs/structure_name_convention.md)