![]() A manifest of file dependancies should be added.Ģ) An input item can only take one output (one provider).įor some inputs it makes perfectly sense that there can only be one provider, as e.g. A pure 32bit and a pure 64bit version will be generated. An attribute, something like "Processor_Architecture" should be added to XML file ( Windows, Linux, 32bit, 64bit. Probably also the configuration editor should be build in a 32 bit and 64 bit version. If the processor architecture is included in the OMI file, it will make component providers aware of the issue and address it, and it will let the configuration editor give a nice error message when loading a model with the wrong architecture. If the configuration editor tries to load a linkable component of another processor architecture, it fails with an ugly exception (either "can not find file" - it is there, but it is the wrong architecture, or "bad image format" - some underlying unmanaged dll is using the wrong architecture). Some models does work only in 64 bit or 32 bit mode. This means on a 64 bit machine it will by default run as 64 bit, and on a 32 bit machine it will run as 32 bit. The current configuration editor is build with the An圜PU (MSIL) set. The following observations was made:ġ) Processor architecture (MSIL/x86/AMD64/IA64) in OMI file and configuration editor (Jesper) I am currently working on porting the DHI OpenMI components to 2.0. Observations during working with the new standard (Stef) Maybe keep the documentation more or less as is, and only clearly describe the 'base' - 'timespace' leveling. Todo: Stef will take care about the Java documentation before the iEMSs conference on the 5th July. Looking for a volunteer to do this since I will be attending the iEMSs in Ottawa and not have time until mid July. Current source code is out-of-sync with C# version and needs to be updated. (Rob) No updates have been made since about two weeks, due to lack of time. But more of the OGC feature classes should probably also be included. Suggestions to/draft of a spatial extension to the standard.Ĭurrently only these interfaces/classes have been added, since that was the most obvious ones.This is exactly what the wrapper classes do. Make clear how use IElementSet to work with OGC formats - the review issue.Together with each interface there is a wrapper class that presents the class as an IElementSet. ISpatial2DRegularGrid | Spatial2DRegularGridĪll interfaces extend from the new ISpatialDefinition. ![]() ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |