There are 2 ways to do this:
1) Below is an example of a 2D state variable declared in Registry.EM_COMMON:
state real T2 ij misc 1 - irhd "T2" "TEMP at 2"
To change it so that it no longer outputs in the normal history file, but from another output unit (e.g., io stream 3), this line would become:
state real T2 ij misc 1 - irh3d "T2" "TEMP at 2"
(simply add '3' after the letter 'h' in the 8th column). To do this for all 2D state variables, you will need to find those in the Registr.EM_COMMON file. You will also need to modify the namelist by adding the following in the &time_control section (modifying according to your particular case):
auxhist3_outname = "my_output_d<domain>_<date>"
auxhist3_interval = 30, 30,
frames_per_auxhist3 = 1000, 1000,
io_form_auxhist3 = 2
Since you changed the Registry, you will need to do a 'clean -a' and then reconfigure and recompile before running again.
2) This can also be done using the runtime I/O option (http://www2.mmm.ucar.edu/wrf/users/docs/user_guide_v4/v4.0/users_guide_chap5.html#runtimeio), which will allow you to make changes without having to recompile the code. You may need more computational time for production runs.
1) Below is an example of a 2D state variable declared in Registry.EM_COMMON:
state real T2 ij misc 1 - irhd "T2" "TEMP at 2"
To change it so that it no longer outputs in the normal history file, but from another output unit (e.g., io stream 3), this line would become:
state real T2 ij misc 1 - irh3d "T2" "TEMP at 2"
(simply add '3' after the letter 'h' in the 8th column). To do this for all 2D state variables, you will need to find those in the Registr.EM_COMMON file. You will also need to modify the namelist by adding the following in the &time_control section (modifying according to your particular case):
auxhist3_outname = "my_output_d<domain>_<date>"
auxhist3_interval = 30, 30,
frames_per_auxhist3 = 1000, 1000,
io_form_auxhist3 = 2
Since you changed the Registry, you will need to do a 'clean -a' and then reconfigure and recompile before running again.
2) This can also be done using the runtime I/O option (http://www2.mmm.ucar.edu/wrf/users/docs/user_guide_v4/v4.0/users_guide_chap5.html#runtimeio), which will allow you to make changes without having to recompile the code. You may need more computational time for production runs.