You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
nested domine
- Thread starter msvrwrf
- Start date
This post was from a previous version of the WRF&MPAS-A Support Forum. New replies have been disabled and if you have follow up questions related to this post, then please start a new thread from the forum home page.
hi
http://www2.mmm.ucar.edu/wrf/OnLineTutorial/CASES/NestRuns/ndown4.htm
This is the ndown process which am following those steps.
actually am doing climate runs in WRF followed by nesting ndown for that my first domine wrfout files is linking to where am running the main run
but my problem is my previous first domine files are over writing, in the above link they mention '' RENAME (or move) the original wrfout_d01_<date>* files to a new file name, or to another directory (to prevent them from being overwritten)'' like this
but my climate run outputs are taking too much of space in my server.
so is there any chance to change wrfoutput files of nesting ndown process?
thanks in advance.
http://www2.mmm.ucar.edu/wrf/OnLineTutorial/CASES/NestRuns/ndown4.htm
This is the ndown process which am following those steps.
actually am doing climate runs in WRF followed by nesting ndown for that my first domine wrfout files is linking to where am running the main run
but my problem is my previous first domine files are over writing, in the above link they mention '' RENAME (or move) the original wrfout_d01_<date>* files to a new file name, or to another directory (to prevent them from being overwritten)'' like this
but my climate run outputs are taking too much of space in my server.
so is there any chance to change wrfoutput files of nesting ndown process?
thanks in advance.
Hi,
There are a few options:
1) Rename the files. You could use some sort of quick command-line script like:
> foreach f (wrfout_d01*)
> mv $f $f.d01
> end
This would add a suffix *.d01 to the end of each of the original wrfout_d01 files.
2) Within your WRF running directory (or wherever you have enough space), create a new directory and place all of your original wrfout_d01* files in there:
> mkdir original_d01
> mv wrfout_d01* original_d01
3) Change the name of the "new" wrfout_d01* (actually d02) files by adding something like the following in the &time_control section of the namelist:
history_outname = 'new_wrfout_d<domain>_<date>'
(do not modify the syntax of "d<domain>_<date>". The model expects that exact syntax.
If you would like those to output to a different directory, then try:
history_outname = '/path_where_you_would_like_the_files/wrfout_d<domain>_<date>'
(obviously the path here would be your actual path - not one named "path_where_you_would_like_the_files."
There are a few options:
1) Rename the files. You could use some sort of quick command-line script like:
> foreach f (wrfout_d01*)
> mv $f $f.d01
> end
This would add a suffix *.d01 to the end of each of the original wrfout_d01 files.
2) Within your WRF running directory (or wherever you have enough space), create a new directory and place all of your original wrfout_d01* files in there:
> mkdir original_d01
> mv wrfout_d01* original_d01
3) Change the name of the "new" wrfout_d01* (actually d02) files by adding something like the following in the &time_control section of the namelist:
history_outname = 'new_wrfout_d<domain>_<date>'
(do not modify the syntax of "d<domain>_<date>". The model expects that exact syntax.
If you would like those to output to a different directory, then try:
history_outname = '/path_where_you_would_like_the_files/wrfout_d<domain>_<date>'
(obviously the path here would be your actual path - not one named "path_where_you_would_like_the_files."