Using the SatSim Gridded Component: Difference between revisions

Line 17:

The first is the directive <code>#define USE_COSP</code>, which is the default. This enables the use of the lidar, radar, ISCCP and MODIS simulators, and the post-simulator processing for COSP data, all of which are called in the <code>cosp</code> subroutine. The selection of these can be trimmed with boolean settings under the comment with "Switches".

If <code>USE_COSP</code> is left undefined, then <code>USE_ICARUS</code>, <code>USE_LIDAR</code>, <code>USE_RADAR</code>, and <code>USE_COSP_STATS</code> are automatically defined, causing the "bare" simulator routines to be used. These <code>#define</code> directives can be commented out individually. At the time of this writing the bare MODIS ~~simulator has~~ not been implemented. The results of all the simulators should be bit-identical to those of COSP: their purpose is to allow the implementation of a subgrid generator other than that of COSP, and to facilitate testing.

If <code>USE_COSP</code> is left undefined, then <code>USE_ICARUS</code>, <code>USE_LIDAR</code>, <code>USE_RADAR</code>, and <code>USE_COSP_STATS</code> are automatically defined, causing the "bare" simulator routines to be used. These <code>#define</code> directives can be commented out individually. At the time of this writing the bare MODIS and MISR simulators have not been implemented. The results of all the simulators should be bit-identical to those of COSP: their purpose is to allow the implementation of a subgrid generator other than that of COSP, and to facilitate testing.

Below the <code>#ifndef USE_COSP</code> is another preprocessing directive, <code>#define USE_MAPL_UNDEF</code>. This sets all of the "undefined" values to MAPL_UNDEF from the values used by COSP and the simulator routines, preventing problems in the GEOS-5 post-processing.

@@ Line 17: / Line 17: @@
 The first is the directive <code>#define USE_COSP</code>, which is the default.  This enables the use of the lidar, radar, ISCCP and MODIS simulators, and the post-simulator processing for COSP data, all of which are called in the <code>cosp</code> subroutine.  The selection of these can be trimmed with boolean settings under the comment with "Switches".
-If <code>USE_COSP</code> is left undefined, then <code>USE_ICARUS</code>, <code>USE_LIDAR</code>, <code>USE_RADAR</code>, and <code>USE_COSP_STATS</code> are automatically defined, causing the "bare" simulator routines to be used.   These <code>#define</code> directives can be commented out individually.  At the time of this writing the bare MODIS simulator has not been implemented.  The results of all the simulators should be bit-identical to those of COSP: their purpose is to allow the implementation of a subgrid generator other than that of COSP, and to facilitate testing.
+If <code>USE_COSP</code> is left undefined, then <code>USE_ICARUS</code>, <code>USE_LIDAR</code>, <code>USE_RADAR</code>, and <code>USE_COSP_STATS</code> are automatically defined, causing the "bare" simulator routines to be used.   These <code>#define</code> directives can be commented out individually.  At the time of this writing the bare MODIS and MISR simulators have not been implemented.  The results of all the simulators should be bit-identical to those of COSP: their purpose is to allow the implementation of a subgrid generator other than that of COSP, and to facilitate testing.
 Below the <code>#ifndef USE_COSP</code> is another preprocessing directive, <code>#define USE_MAPL_UNDEF</code>.  This sets all of the "undefined" values to MAPL_UNDEF from the values used by COSP and the simulator routines, preventing problems in the GEOS-5 post-processing.