User Tools

Site Tools


working_groups:ukurbangroup

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision Both sides next revision
working_groups:ukurbangroup [2022/08/05 12:26]
mhajji old revision restored (2022/08/05 13:57)
working_groups:ukurbangroup [2022/09/19 09:32]
acriado
Line 16: Line 16:
 __Meriem Hajji__, meriem.hajji@bsc.es __Meriem Hajji__, meriem.hajji@bsc.es
  
-===== First Steps ===== + 
 +===== Visualization ===== 
 + 
 +At this point, it is recommended to follow the tutorial using the Rstudio program to visualize the different scripts. 
 + 
 +===== First Steps : understanding the scripts ===== 
  
 To follow a basic tutorial using this methodology, please follow the next steps. The procedure is implemented using the R software.  To follow a basic tutorial using this methodology, please follow the next steps. The procedure is implemented using the R software. 
Line 25: Line 30:
 <code bash> git clone https://earth.bsc.es/gitlab/es/universalkriging.git </code> <code bash> git clone https://earth.bsc.es/gitlab/es/universalkriging.git </code>
 After doing that, a folder called by default //universalkriging// will appear with all the copied files from the repository: https://earth.bsc.es/gitlab/es/universalkriging.git. This will be the main folder, which contains the sub-folder //general// (the one with all scripts and data), and there the results will appear. All of this information will be mentioned again in the following steps.  After doing that, a folder called by default //universalkriging// will appear with all the copied files from the repository: https://earth.bsc.es/gitlab/es/universalkriging.git. This will be the main folder, which contains the sub-folder //general// (the one with all scripts and data), and there the results will appear. All of this information will be mentioned again in the following steps. 
- 
- 
  
 In the folder //general//, a list of different archives will appear. They are classified into **R scripts** (the principal script is named by //kriging_repository.R// , while the remaining R scripts are secondary scripts called by the principal one in different parts of the workflow), **folders** (they contain different types of information, required for some of the mentioned scripts), a **configuration file** (named by //config_file.yml// , used by initializing the methodology and launching it in terms of what procedure we would want, as it can be seen in the next steps) and **git-basic files** (README.md and LICENSE). In the folder //general//, a list of different archives will appear. They are classified into **R scripts** (the principal script is named by //kriging_repository.R// , while the remaining R scripts are secondary scripts called by the principal one in different parts of the workflow), **folders** (they contain different types of information, required for some of the mentioned scripts), a **configuration file** (named by //config_file.yml// , used by initializing the methodology and launching it in terms of what procedure we would want, as it can be seen in the next steps) and **git-basic files** (README.md and LICENSE).
- 
- 
- 
-At this point, it is recommended to follow the tutorial using the Rstudio program to visualize the different scripts. 
  
 === The configuration file === === The configuration file ===
  
-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, meaning that the variables that appear in it can be changed and 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:
 {{ :working_groups:configR.png?nolink&600 |}} {{ :working_groups:configR.png?nolink&600 |}}
Line 85: Line 84:
  
 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. 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  ===
working_groups/ukurbangroup.txt · Last modified: 2022/09/23 09:10 by acriado