howtos:workwithdata:overview_of_reading_data
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
howtos:workwithdata:overview_of_reading_data [2011/05/26 14:49] marcus.williams |
howtos:workwithdata:overview_of_reading_data [2011/06/01 19:30] marcus.williams |
||
|---|---|---|---|
| Line 26: | Line 26: | ||
| In some special cases, additional pre-processing is performed using another language or tool (e.g. awk, PERL, R). Or, if the pre-processing task is sufficiently large and complex, a separate whatIf model framework might be developed (often called a //database// model). | In some special cases, additional pre-processing is performed using another language or tool (e.g. awk, PERL, R). Or, if the pre-processing task is sufficiently large and complex, a separate whatIf model framework might be developed (often called a //database// model). | ||
| - | The problem described here is encountered in the broader model development cycle - most intensively in the data assembly and calibration stage, involving historical data - but also during scenario creation with external forecasts and projections. The target objects are defined during the initial model design stage. | + | The problem described here is encountered at several points within the broader model development cycle - most intensively in the data assembly and calibration stage, involving historical data - but also during scenario creation with external forecasts and projections. The target objects are defined during the initial model design stage. |
| ===== Import "channels" ===== | ===== Import "channels" ===== | ||
| Line 35: | Line 35: | ||
| Most of the articles in this section are oriented towards ultimately getting data into diagram-based objects loaded in SAMM. | Most of the articles in this section are oriented towards ultimately getting data into diagram-based objects loaded in SAMM. | ||
| + | |||
| + | Point out some of the differences between the channels (e.g. stand-alone scripts don't have arrays of tool objects, indexes, etc; availability of informants) | ||
| ===== Considerations and best practices ===== | ===== Considerations and best practices ===== | ||
| Line 41: | Line 43: | ||
| * Document source data origins in the diagram (variable description and notes fields). | * Document source data origins in the diagram (variable description and notes fields). | ||
| * Name time dimensions explicitly. | * Name time dimensions explicitly. | ||
| + | * convention for index naming (e.g. t2010_2015) | ||
| + | * name time informants with data source in name (e.g. cs_t19762006) | ||
| * Import into objects (either diagram or view locals) in their native units of measure - i.e. no magic number conversion hacks. Let TOOL's built-in unit handling and conversion do all the work. | * Import into objects (either diagram or view locals) in their native units of measure - i.e. no magic number conversion hacks. Let TOOL's built-in unit handling and conversion do all the work. | ||
| * Where possible use //coordinate// data format. Explain why. Provide link. FIXME. | * Where possible use //coordinate// data format. Explain why. Provide link. FIXME. | ||
| * Describe other considerations for view vs. "growing" diagram logic vs. stand-along TOOL script pre-processor vs. database. | * Describe other considerations for view vs. "growing" diagram logic vs. stand-along TOOL script pre-processor vs. database. | ||
howtos/workwithdata/overview_of_reading_data.txt ยท Last modified: 2011/06/01 20:20 by marcus.williams
Page Tools
