User interface: OrcaWave model files

OrcaWave models are saved to either binary data files (.owd) or text data files (.yml).

Results from OrcaWave calculations are saved to binary results files (.owr), which can also be used to import the results of the diffraction analysis into OrcaFlex.

Binary and text data files

The principal differences between the two formats are as follows:

• Binary data files have stronger version compatibility features. Whilst we strive to achieve as much compatibility as possible for text data files across program versions, we cannot achieve the same level of compatibility as for binary data files. See below for more details on the compatibility features of each format.
• Text data files, as written by OrcaWave, contain only data that are active in the model. On the other hand, binary data files contain all data, active or not. The fact that the binary data file contains inactive data can be very useful and we would usually recommend that model building and development is performed using the binary data file.
• Text data files can be created without the use of OrcaWave, simply by entering text into a text editor. In general, we would not advocate this approach to model building. It may be a practical approach for very simple models, but more complex models are usually easier to build and inspect using the full capabilities and visualisation strengths of OrcaWave. On the other hand, text data files can be very effective when making minor changes to existing models. Using text data files for such minor variations of existing models makes it much easier to monitor just what has been changed, for example by using standard text differencing programs.
• Text data files are highly readable and self-documenting which makes them ideal for QA and archival purposes. Another application well suited to the use of text data files is automation via scripts that modify and/or generate data files.

Binary data file program version compatibility

As mentioned above, binary data files have strong version compatibility features. When OrcaWave opens a binary data file written by an earlier version of the program, it is usually able to ensure that the data are interpreted exactly as they were by previous versions. If it cannot do so, it reports an informative compatibility warning. Similarly, OrcaWave can report informative compatibility warnings if you open a binary data file written by a later version of the program. For these reasons we recommend that you use the binary data file to transfer models between different program versions.

Text data file program version compatibility

As mentioned above, text data files have weaker version compatibility features than binary data files. Text data files written by one version of OrcaWave may not be compatible with other OrcaWave versions. For example, text data files prepared with old program versions may not load in new program versions, or may load but be interpreted differently. This is the main reason we recommend using the binary data file for your model data and to use text data files principally for automation tasks.

In case you do need to open text data files prepared with a different version of OrcaWave, you should convert them by making use of the version compatibility afforded by the binary data file. A text data file written with OrcaWave version A can be converted to a text data file compatible with version B as follows:

• Make a backup of the original text data file.
• Using OrcaWave version A, open the text data file and save the resulting model to a temporary file in binary data file format.
• Using OrcaWave version B, open the temporary file and save the model in text data file format, replacing the original version.

This can be a cumbersome process, especially if you have a large number of files to convert. The process can be automated by the OrcaFlex text data file conversion utility.