Author
Abstract
It is commonly necessary in analysis and other activities involving models to work at two or more levels of resolution. Resolution is a relative concept, but at any given level one may think of increasing resolution (e.g., to gain greater insight about phenomenology) or decreasing resolution (e.g., to produce something more comprehensible and more appropriate for policy analysis or operational decision support). Sometimes one can calibrate lower‐resolution models with higher‐resolution models and, to some extent, vice versa. Ideally, models (or integrated model families) would be built from the outset with variable‐resolution capability. Often, however, we find ourselves having to do cross‐resolution work by linking existing models that were not designed to be connected. Although there are software techniques for connecting dissimilar models, these techniques do not guarantee that it is substantively meaningful to do so. Similarly, while many workers have found off‐line methods for tuning one model of an alleged family to be at least somewhat consistent with another model of the family, the consistency is sometimes more apparent than real. To put it differently, taking existing models with varied resolutions and declaring them to constitute a hierarchical family is sometimes quite misleading because the models are not integrated nor can they be integrated readily. Further, even when means for relating the models sensibly have been developed (either off‐line methods or model‐connection methods), doing so may involve complex, tedious, error‐prone, and expensive calibration efforts. This article describes building models with variable‐resolution capability. It also describes generic substantive challenges in connecting models developed independently, and recommends that such model‐connection activities be guided by design work to identify how the models would have been developed in the first place if their subsequent integration had been a goal. This approach can make it possible to connect the models usefully and comprehensively with one set of adaptations rather than a series of incremental patches. In other cases it may convince users to commission the building of a new variable‐resolution model by demonstrating that the existing models will never work together well. The article also describes a particular design method called integrated hierarchical variable‐resolution modeling (IHVR). which is very helpful when it is feasible. It greatly clarifies relationships among levels of resolutions. © 1995 John Wiley & Sons, Inc.
Suggested Citation
Paul K. Davis, 1995.
"An introduction to variable‐resolution modeling,"
Naval Research Logistics (NRL), John Wiley & Sons, vol. 42(2), pages 151-181, March.
Handle:
RePEc:wly:navres:v:42:y:1995:i:2:p:151-181
DOI: 10.1002/1520-6750(199503)42:23.0.CO;2-M
Download full text from publisher
Corrections
All material on this site has been provided by the respective publishers and authors. You can help correct errors and omissions. When requesting a correction, please mention this item's handle: RePEc:wly:navres:v:42:y:1995:i:2:p:151-181. See general information about how to correct material in RePEc.
If you have authored this item and are not yet registered with RePEc, we encourage you to do it here. This allows to link your profile to this item. It also allows you to accept potential citations to this item that we are uncertain about.
We have no bibliographic references for this item. You can help adding them by using this form .
If you know of missing items citing this one, you can help us creating those links by adding the relevant references in the same way as above, for each refering item. If you are a registered author of this item, you may also want to check the "citations" tab in your RePEc Author Service profile, as there may be some citations waiting for confirmation.
For technical questions regarding this item, or to correct its authors, title, abstract, bibliographic or download information, contact: Wiley Content Delivery (email available below). General contact details of provider: https://doi.org/10.1002/(ISSN)1520-6750 .
Please note that corrections may take a couple of weeks to filter through
the various RePEc services.