Using the ExtData/History tool: Difference between revisions
No edit summary |
No edit summary |
||
| Line 43: | Line 43: | ||
</pre> | </pre> | ||
The CAP in the application will run a clock from the BEG_DATE for the JOB_SGMT length at a HEARTBEAT_DT interval. ExtData, History, and the application component only run at the times listed in run time. This is a bit clunky but unfortunately History uses alarms which will only go off if a clock advances. This is very unfortunate as it adds confusion to the application. | The CAP in the application will run a clock from the BEG_DATE for the JOB_SGMT length at a HEARTBEAT_DT interval. ExtData, History, and the application component only run at the times listed in run time. This is a bit clunky but unfortunately History uses alarms which will only go off if a clock advances. This is very unfortunate as it adds confusion to the application. The cap specified an AGCM.rc, ExtData.rc and History.rc for that instance. | ||
An AGCM.rc for the application looks like this: | An AGCM.rc for the application looks like this: | ||
| Line 81: | Line 81: | ||
REF_TIME: 20040101 000000 | REF_TIME: 20040101 000000 | ||
</pre> | </pre> | ||
One possible use for this application could be to have CASE 1 of the application produce output via history and CASE 2 use that output as input for ExtData. Then we can compare what ExtData filled the import with against the computed values since we know in the previous case exactly what is in the files. For example we could use this to test if ExtDat is performing time interpolation correctly. | |||