The diagfi.def Input File - Revision history

Emillour at 13:03, 30 April 2025

2025-04-30T13:03:23Z

2025-04-30T09:00:56Z

2025-03-05T13:02:07Z

‎diagfi.def format

2025-03-05T11:12:23Z

‎diagfi.def format

2023-08-02T01:50:26Z

2023-05-26T07:59:00Z

2023-03-20T16:07:59Z

2023-03-09T10:20:13Z

2022-07-27T14:21:13Z

2022-05-11T09:21:08Z

@@ Line 6: / Line 6: @@
 Each line of this ASCII file should contain the name (case sensitive!) of a variable to output.
-Note that the variable name to use is the one set in the code when calling the ''writediagfi'' or ''write_output'' routines. e.g.
+Note that the variable name to use is the one set in the code when calling the ''write_output'' routine. e.g.
 <syntaxhighlight lang="fortran">
-call writediagfi(ngrid,"temperature","temperature","K",3,zt)
+call write_output("temperature","atmospheric temperature","K",zt)
 </syntaxhighlight>
@@ Line 95: / Line 91: @@
 [[Category:Mars-Model]]
 [[Category:Mars-LMDZ]]

@@ Line 86: / Line 86: @@
 == Various related comments and remarks ==
 * If there is no ''diagfi.def'' file found at run-time, then '''ALL''' variables will be written in ''diagfi.nc'', which will rapidly become huge. You have been warned. Note however that it is a convenient way to have access to the names of all available variables that may be outputted in ''diagfi.nc''.
-* The rate at which the outputs are made in ''diagfi.nc'' is set by the ''ecritphy'' parameter which is usually set in the ''run.def'' file and expressed in terms of dynamical time steps.
+* The rate at which the outputs are made in ''diagfi.nc'' is set by the ''diagfi_output_rate'' parameter which is usually set in the ''callphys.def'' file and expressed in terms of physical time steps for the Generic PCM. For the Mars PCM, a different flag sets the ''diagfi.nc'' output rate using ''outputs_per_sol''.
 [[Category:Inputs]]

@@ Line 8: / Line 8: @@
 Note that the variable name to use is the one set in the code when calling the ''writediagfi'' or ''write_output'' routines. e.g.
 <syntaxhighlight lang="fortran">
-     call writediagfi(ngrid,"temperature","temperature","K",3,zt)
+call writediagfi(ngrid,"temperature","temperature","K",3,zt)
 </syntaxhighlight>
 or

@@ Line 6: / Line 6: @@
 Each line of this ASCII file should contain the name (case sensitive!) of a variable to output.
-Note that the variable name to use is the one set in the code when calling the ''writediagfi'' routine. e.g.
+Note that the variable name to use is the one set in the code when calling the ''writediagfi'' or ''write_output'' routines. e.g.
 <syntaxhighlight lang="fortran">
-      call writediagfi(ngrid,"temp","temperature","K",3,zt)
+      call writediagfi(ngrid,"temperature","temperature","K",3,zt)
 </syntaxhighlight>
-implies that the variable ''temp'' can be outputted in ''diagfi.nc''
+or
 == Example of ''diagfi.def'' file ==

@@ Line 1: / Line 1: @@
 The ''diagfi.def'' file is an optional file that is read by the GCM at run time. If it is present then it will dictate which fields will be included in the ''diagfi.nc'' output file.
-A clarification: generating the ''diagfi.nc'' output file is only possible when running with the lon-lat (LMDZ.COMMON) dynamical core.
+A clarification: generating the ''diagfi.nc'' output file is only possible when running with the lon-lat (LMDZ.COMMON) dynamical core (or in 1D), with the Generic or Mars physics packages.
 == ''diagfi.def '' format ==
@@ Line 88: / Line 88: @@
 [[Category:Generic-LMDZ]]
 [[Category:Generic-1D]]