User Tools

Site Tools

Trace:
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 11:54]
acriado 		working_groups:ukurbangroup [2022/08/05 11:57]
acriado
Line 105: Line 105:
   * The section //**covariates**// is only used if the **//UK_mode//** is //UK2//, since refers to the microscale-LUR model. Two different scripts (sim_LUR_final & sim_LUR_performance) are employed to address its expected performance and the basemap, respectively.   * The section //**covariates**// is only used if the **//UK_mode//** is //UK2//, since refers to the microscale-LUR model. Two different scripts (sim_LUR_final & sim_LUR_performance) are employed to address its expected performance and the basemap, respectively.
   * In the section //**application**//, all the applications established by the user are made.   * In the section //**application**//, all the applications established by the user are made.
-  * In the section **//plots//**, the images are generated if the configuration's parameter //**plot_images**// is //TRUE//. The same for the section **//evaluation//**, where the specific operations about the paper are made if the parameter //paper// of the **//initial setting section//** of the current script is set to //TRUE//.+  * In the section **//plots//**, the images are generated if the configuration's parameter //**plot_images**// is //TRUE//.  
 +  * In the section **//evaluation//**, some statistical operations are carried out. If the year is 2019, the results for the paper regarding this methodology will be generated.
  
 Notice that the majority of the __//secondary operations//__ —for example preparing the observations or extracting the CALIOPE-Urban annual mean— are made in the first application of the user. It means that if the user wants to apply another configuration file, keeping the same period of time, and still using the same paths configuration, the corresponding files are already created based on another previous application and the secondary operations are not computed again. For this reason, a stable folder structure is made and documented. For example, 6h of computational time using 50 cores are needed to calculate the daily mean concentrations of CALIOPE-Urban for a whole year, which implies that those operations, along with the daily maximum ones, will require approximately 12 hours of computation in the first submission, but not for a second application. Notice that the majority of the __//secondary operations//__ —for example preparing the observations or extracting the CALIOPE-Urban annual mean— are made in the first application of the user. It means that if the user wants to apply another configuration file, keeping the same period of time, and still using the same paths configuration, the corresponding files are already created based on another previous application and the secondary operations are not computed again. For this reason, a stable folder structure is made and documented. For example, 6h of computational time using 50 cores are needed to calculate the daily mean concentrations of CALIOPE-Urban for a whole year, which implies that those operations, along with the daily maximum ones, will require approximately 12 hours of computation in the first submission, but not for a second application.
working_groups/ukurbangroup.txt · Last modified: 2022/09/23 09:10 by acriado

Page Tools

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki