2.1 Introduction
The following Sections of this User Guide present basic features of the QW-3D software on a set of examples. In the default QW‑3D installation, the examples are located in the directory:
<PUBLICDIR>\qw_examp\QW_3D\
The location of PUBLICDIR is defined in Installation.
A major part of this User Guide is concerned with “standard” examples, i.e., such that can be analysed with the basic QW-3D package. They are placed in a subdirectory:
<PUBLICDIR>\qw_examp\QW_3D\Standard
For example, if we refer to a project ..\Wgtocx\wgtocx1.pro, we mean the project found in the default installation at:
<PUBLICDIR>\qw_examp\QW_3D\Standard\Wgtocx\wgtocx1.pro.
In the case of custom installation the path should be modified accordingly.
QW-OptimiserPlus examples chapter concerns joint application of QW-3D with the optional QW-OptimiserPlus module. Examples discussed in that Section are located at:
<PUBLICDIR>\qw_examp\QW_3D\Opt_Plus
The examples use objects from different QW-3D libraries. In the defaultQW‑3D installation, standard libraries are located in subdirectories of the directory:
<INSTALLDIR>\elib
When a library object is added to the project, a full path to the proper library is recorded in the project (and its *.pro file). This direction will be used by QW-Editor to re-draw the object when the user modifies the object parameters. In *.pro files included in the installation, this full path is reduced to a relative one, so that a project from <PUBLICDIR>\qw_examp on the user’s computer will look for its libraries in <INSTALLDIR>\elib of the same installation. Hence in the installed examples, first modification of their objects proceeds smoothly.
Note that upon any Save command of QW-Editor, full paths to the applied library files will be recorded again. If the user moves *.pro files between computers, having different installation directories, or if the original <INSTALLDIR>\elib is uninstalled or re-installed, QW-Editor may be unable to find the file describing the object to be modified. An appropriate error message will appear. In such a case the user can indicate the proper path to the file describing the object using File-UDO paths command of QW-Editor. This command opens a dialogue window as presented in Fig.UG 2.1.2‑1 in which the paths to different libraries may be declared. At the next modification of the object the software will be sweeping these paths in search for the *.udo file of the modified object.
Fig.UG 2.1.2-1 Dialogue used to set paths to non-standard UDO libraries.
The project *.pro files include all information about the project geometry, media, input and output parameters as well as about layouts of QW-Editor windows which were previously open while editing this project. Consequently, when a particular project is loaded into QW-Editor, it will be displayed in the same windows of the same layouts as pasted into this User Guide. For example, Fig.UG 2.2.1-1 shows the display which should come up for ..\Wgtocx\wgtocx1.pro.
There is one exception to the rule. The 3D Windows of QW-Editor, such as the two windows on the right in ..\Wgtocx\wgtocx1.pro, appear nicely on the screen when grey background colour is chosen. Such settings have therefore been used for most of the examples and saved in *.pro files provided in the installation. On the other hand, white background colour is more economical and provides nicer pictures in print. Therefore QW-Editor displays included in this User Guide, such as Fig.UG 2.2.1-1, have been snapped after changing the 3D Windows background colour to white (even if grey background has been then saved in the *.pro file).
As regards QW-Simulator displays, layouts of the previously open windows are saved in projectname.en3 file in the project directory (with default settings of Preferences). For most of the examples, the *.en3 files are installed in the directories of their respective *.pro files. Thus, for example, the first View-Fields command during the simulation of the for ..\Wgtocx\wgtocx1.pro example should bring up the window as in Fig.UG 2.2.1-2. For the same reasons as above, background colour has been changed to white for pictures snapped and pasted into this User Guide.
One more change has been applied in displays of optimisation results in Section UG 2.15. Several windows are typically open during optimisation, for example, two objectives windows, one goal function window, and one Simulation Log window in the ..Opt_Plus\Horn3\horn3.pro example. Such an array of windows fits better into the screen space with cursor pane positioned at the bottom of each window. In the snapped pictures, such as Fig.UG 2.15.2-3, the Change Position option has been used for moving the cursor pane to the right hand side of the window, for better utilisation of the printing space.