This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
working_groups:ukurbangroup [2022/08/05 12:25] mhajji old revision restored (2022/07/19 12:19) |
working_groups:ukurbangroup [2022/08/05 12:26] mhajji old revision restored (2022/08/05 13:57) |
||
---|---|---|---|
Line 24: | Line 24: | ||
- Copy all the functions and archives needed to implement the procedure in your own directory. To do that, open a terminal and copy the following command: | - Copy all the functions and archives needed to implement the procedure in your own directory. To do that, open a terminal and copy the following command: | ||
<code bash> git clone https:// | <code bash> git clone https:// | ||
- | The copied files from the repository: https:// | + | After doing that, a folder called by default // |
- | After copying that repository, a list of different archives will appear. They are classified into **R scripts** (the principal script is named by // | + | In the folder //general//, a list of different archives will appear. They are classified into **R scripts** (the principal script is named by // |
- | At this point, | + | At this point, |
=== The configuration file === | === The configuration file === | ||
Line 38: | Line 38: | ||
The configuration file is an archive used as a setup structure, which means that the variables that appear in it can be changed and it will produce a different output. It is a separate file, so the main advantage is that can be modified without varying the rest of the scripts. The first step to begin consists of filling it. Notice that this is the __only archive__ that has to be modified in terms of your goal. Before starting to modify it, its shape would look like this: | The configuration file is an archive used as a setup structure, which means that the variables that appear in it can be changed and it will produce a different output. It is a separate file, so the main advantage is that can be modified without varying the rest of the scripts. The first step to begin consists of filling it. Notice that this is the __only archive__ that has to be modified in terms of your goal. Before starting to modify it, its shape would look like this: | ||
* Through the Rstudio visualization: | * Through the Rstudio visualization: | ||
- | {{ : | + | {{ : |
* Through the terminal. To do that, go to the directory where all archives copied from the repository are kept, and type the following (in this case, the visualization is done through the program MobaXterm): | * Through the terminal. To do that, go to the directory where all archives copied from the repository are kept, and type the following (in this case, the visualization is done through the program MobaXterm): | ||
<code bash> | <code bash> | ||
vi config_file.yml </ | vi config_file.yml </ | ||
- | {{ : | + | {{ : |
Now we are going to see what is and the implication of each of the items that have to be filled in the configuration file: | Now we are going to see what is and the implication of each of the items that have to be filled in the configuration file: | ||
- | * **// | + | * **// |
* **// | * **// | ||
* **// | * **// | ||
- | * **// | + | * **// |
* **// | * **// | ||
- | * **// | + | * **// |
- | * **// | + | * **//date_begin & date_end// |
- | * **// | + | |
- | * **// | + | * **// |
- | * | + | * **// |
- | * **// | + | * // |
- | * **// | + | |
- | * **// | + | |
+ | | ||
+ | | ||
* **// | * **// | ||
* **// | * **// | ||
- | * **// | + | * **// |
As a resume, notice that the user only has to do the following about the configuration file: | As a resume, notice that the user only has to do the following about the configuration file: | ||
- | * Choosing | + | * Choosing |
* Choosing one of the **// | * Choosing one of the **// | ||
* Choosing the Universal Kriging mode in terms of the covariates, the application, | * Choosing the Universal Kriging mode in terms of the covariates, the application, | ||
Line 78: | Line 80: | ||
Before applying the methodology and obtaining the results, is important to realize the structure of the folders that will appear to understand correctly the different outputs. The structure of the folders created by the code is always the same, and it is constructed at the first moment after applying any of the possible applications, | Before applying the methodology and obtaining the results, is important to realize the structure of the folders that will appear to understand correctly the different outputs. The structure of the folders created by the code is always the same, and it is constructed at the first moment after applying any of the possible applications, | ||
- | |||
- | Remember that the parallelization is carried out in terms of the day. We are applying the methodology on a mesh composed approximately of 49000 points, each hour of the period chosen. The output of this methodology is __daily__, which means that the output files are referred to each day. Thus, each file will contain the correction on the 49000 points, 24 times regarding the 24h of the day. Please, see the examples to visualize the outputs of this methodology. | ||
This is an example of the structure using the 2019 dataset : | This is an example of the structure using the 2019 dataset : | ||
{{ : | {{ : | ||
+ | |||
+ | Remember that the parallelization is carried out in terms of the day. We are applying the methodology on a mesh composed approximately of 49000 points, each hour of the period chosen. The output of this methodology is __daily__, which means that the output files are referred to each day. Thus, each file will contain the correction on the 49000 points, 24 times regarding the 24h of the day. Please, see the examples to visualize the outputs of this methodology. | ||
+ | |||
=== The main script and its explanation | === The main script and its explanation | ||
Line 100: | Line 103: | ||
* In the section **//caliope evaluation, mean and max//**, different scripts are used to prepare the files regarding the model (CALIOPE-Urban) output at the monitoring stations (caliope evaluation), | * In the section **//caliope evaluation, mean and max//**, different scripts are used to prepare the files regarding the model (CALIOPE-Urban) output at the monitoring stations (caliope evaluation), | ||
* In the section **// | * In the section **// | ||
- | * The section // | + | * The section // |
* In the section // | * In the section // | ||
- | * In the section **// | + | * In the section **// |
+ | * In the section **// | ||
Notice that the majority of the __// | Notice that the majority of the __// | ||
Line 108: | Line 112: | ||
=== Submitting jobs === | === Submitting jobs === | ||
- | *It is recommended to first take a look at the guidelines of the machines (NORD3v2 or Marenostrum4 -MN4- specifically) to familiarize yourself with this environment. | + | *It is recommended to first take a look at the guidelines of the machines (NORD3v2 or Marenostrum4 -MN4- specifically) to familiarize yourself with this environment |
To apply the methodology, | To apply the methodology, |