This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Last revision Both sides next revision | ||
tools:ocean_postprocessing [2015/05/26 11:24] 127.0.0.1 external edit |
tools:ocean_postprocessing [2015/10/19 14:55] pbretonn |
||
---|---|---|---|
Line 25: | Line 25: | ||
Some more specifications: | Some more specifications: | ||
- | * The dependency between the diagnostics is handled, i.e. even if you ask for a diagnostic that depends on another | + | * The dependency between the diagnostics is handled, i.e. even if you ask for a diagnostic that depends on another |
- | * If you extend the number of members of an experiment or its forecast length, the output will be gathered on cfunas. Ex : You have already postprocessed for exp t001: 1) members 0-2 between leadtimes 1 and 36, 2) members 0 between leadtimes 37 and 60 If you process member 1-2 between leadtimes 37 and 60, you'll find on the nas a single output with members 0-2 between leadtimes 1 and 60 BUT : You have already postprocessed for exp t001: 1) members 0-2 between leadtimes 1 and 36, 2) members 0 between leadtimes 37 and 60 If you process member 2 between leadtimes 25 and 60, you'll find the two above files plus a new one with members 2 between leadtimes 25 and 60 on the nas | + | * If you extend the number of members of an experiment or its forecast length, the output will be gathered on esnas. Ex : You have already postprocessed for exp t001: 1) members 0-2 between leadtimes 1 and 36, 2) members 0 between leadtimes 37 and 60 If you process member 1-2 between leadtimes 37 and 60, you'll find on the nas a single output with members 0-2 between leadtimes 1 and 60 BUT : You have already postprocessed for exp t001: 1) members 0-2 between leadtimes 1 and 36, 2) members 0 between leadtimes 37 and 60 If you process member 2 between leadtimes 25 and 60, you'll find the two above files plus a new one with members 2 between leadtimes 25 and 60 on the nas |
ocean_pp.bash handles any range of leadtimes instead of complete years only. However, the max_moc diagnostic can not be computed if you do not have complete years since it is a diagnostic computed from annual means. | ocean_pp.bash handles any range of leadtimes instead of complete years only. However, the max_moc diagnostic can not be computed if you do not have complete years since it is a diagnostic computed from annual means. | ||
Line 58: | Line 58: | ||
* concat | * concat | ||
* gather_memb | * gather_memb | ||
+ | * vertmeanvar | ||
Line 73: | Line 74: | ||
* Sections raw_vars_ocean and raw_vars_ice allow to specify which 2D variables you want to extract: | * Sections raw_vars_ocean and raw_vars_ice allow to specify which 2D variables you want to extract: | ||
- | If " | + | If " |
If nothing is specified, it will extract all the 2D variables present in the input files. | If nothing is specified, it will extract all the 2D variables present in the input files. | ||
Otherwise, it will treat exclusively the variables listed. | Otherwise, it will treat exclusively the variables listed. | ||
Line 83: | Line 84: | ||
- | The link to the GIT repository is https://gitlab.cfu.local/cfu/ | + | The link to the GIT repository is https://earth.bsc.es/gitlab/es/ |
Line 89: | Line 90: | ||
- | The coordinator of this project | + | The coordinator of this project |
- | + | ||
- | Previous version of this page can be found here: http:// | + | |
==== Development ==== | ==== Development ==== | ||
Line 98: | Line 96: | ||
If you want to include a new diagnostic. Look for the @ signs in the common_ocean_post.txt then ocean_pp.bash and you'll find the locations where you have to include lines of code and some additional instructions so that everything works fine. Feel free to ask if something is not clear. To facilitate testing of new functions or of new options in existing functions, you can use the script named setup_development_oriol.bash in any working directory. | If you want to include a new diagnostic. Look for the @ signs in the common_ocean_post.txt then ocean_pp.bash and you'll find the locations where you have to include lines of code and some additional instructions so that everything works fine. Feel free to ask if something is not clear. To facilitate testing of new functions or of new options in existing functions, you can use the script named setup_development_oriol.bash in any working directory. | ||
- | |||
- | On this page (http:// | ||
If you want to make available the post-processing tools for new grids, you need to choose a flag for this new grid (such as Ec2.3_O1L42), | If you want to make available the post-processing tools for new grids, you need to choose a flag for this new grid (such as Ec2.3_O1L42), | ||
- | /cfu/ | + | /esnas/ |
for example for any other flags. Namely you need to prepare the files : | for example for any other flags. Namely you need to prepare the files : | ||
* depth.flag.txt | * depth.flag.txt | ||
Line 113: | Line 109: | ||
- | Download the repository folder to your computer ( git clone https://dev.cfu.local/ | + | Download the repository folder to your computer ( git clone https://earth.bsc.es/ |
Line 126: | Line 122: | ||
You can check the style guide for the ocean_diagnostics package [[tools: | You can check the style guide for the ocean_diagnostics package [[tools: | ||
- |