QuickWave
software for electromagnetic design
Operating Regimes
Windows 32/x64, Linux
QuickWave is a multiplatform software package prepared in object-oriented C++ language under Qt (Qt is a multiplatform C++ GUI toolkit created and maintained by Trolltech). It works under Microsoft Windows 2000/XP/2003 Server/Vista operating systems (Windows 2000 Professional or Windows XP Professional are recommended).
Following the trends in hardware development, next to 32-bit version, QWED introduced 64-bit versions of QuickWave. For those users who already have computers with Windows 64-bit operating system, the 64-bit version of QuickWave will remove all software imposed limits on the size of the accessible memory. It will also increase the computing speed by 25% on average.
The 32-bit package works on 32 bits x86 based systems such as Microsoft Windows 2000/XP/2003 Server/Vista operating system (Windows 2000 Professional or Windows XP Professional recommended).
The 64-bit package works on 64 bits systems such as Microsoft Windows XP x64/2003 Server x64/Vista x64 operating system (Windows XP x64 recommended).
For possibilities of application on other platforms, please contact QWED directly at info@qwed.eu.
Following the trends in hardware development, next to 32-bit version, QWED introduced 64-bit versions of QuickWave. For those users who already have computers with Windows 64-bit operating system, the 64-bit version of QuickWave will remove all software imposed limits on the size of the accessible memory. It will also increase the computing speed by 25% on average.
The 32-bit package works on 32 bits x86 based systems such as Microsoft Windows 2000/XP/2003 Server/Vista operating system (Windows 2000 Professional or Windows XP Professional recommended).
The 64-bit package works on 64 bits systems such as Microsoft Windows XP x64/2003 Server x64/Vista x64 operating system (Windows XP x64 recommended).
For possibilities of application on other platforms, please contact QWED directly at info@qwed.eu.
Project structure export
QW-Editor has a possibility to export the project structure in the SAT file and open it in the SAT Viewer.
3D radiation pattern export
QW-Simulator has a possibility to export the 3D radiation pattern in the SAT file.
Project structure import from SAT
A converter from SAT format to UDO (interpreted by QW-Editor User Defined Object language) has been developed in collaboration with Vector Fields Ltd., UK. As a joint product of the two companies, it will form an optional and separately (but modestly!) priced module for the software. This converter has been designed so as to import any SAT files prepared by any ACIS(c)-compatible geometry modellers. However, we presume that its use will be exceptionally convenient in conjunction with VF Modeller, continuously enhanced by Vector Fields with specific media and port labels required by QuickWave.
Project structure import from DXF
A converter from DXF format to UDO (interpreted by QW-Editor User Defined Object language) has been developed and included in the software. Its practical applications will focus on (but not be limited to) importing metalisation shapes for planar circuits in QW-3D or corrugation shapes in QW-V2D.
Save as picture
The structure view from QW-Editor and simulation results, 3D radiation pattern, field distribution etc. from QW-Simulator can be saved to the picture as a BMP or PNG file.
QW-Editor has a possibility to export the project structure in the SAT file and open it in the SAT Viewer.
3D radiation pattern export
QW-Simulator has a possibility to export the 3D radiation pattern in the SAT file.
Project structure import from SAT
A converter from SAT format to UDO (interpreted by QW-Editor User Defined Object language) has been developed in collaboration with Vector Fields Ltd., UK. As a joint product of the two companies, it will form an optional and separately (but modestly!) priced module for the software. This converter has been designed so as to import any SAT files prepared by any ACIS(c)-compatible geometry modellers. However, we presume that its use will be exceptionally convenient in conjunction with VF Modeller, continuously enhanced by Vector Fields with specific media and port labels required by QuickWave.
Project structure import from DXF
A converter from DXF format to UDO (interpreted by QW-Editor User Defined Object language) has been developed and included in the software. Its practical applications will focus on (but not be limited to) importing metalisation shapes for planar circuits in QW-3D or corrugation shapes in QW-V2D.
Save as picture
The structure view from QW-Editor and simulation results, 3D radiation pattern, field distribution etc. from QW-Simulator can be saved to the picture as a BMP or PNG file.
CAD import-export
Freeze of state
Using freeze menu command and freeze tasker command user can save state of the QW- Simulator in the purpose to restore this state, view results for this state or continue calculations in the future. All QW- Simulator functions work in the same normal manner after defreeze operation. This is very convenient feature in many situations. Below there are typical scenarios:
| · | user wants to replace calculations from one computer to another |
| · | user wants to save time consuming calculations |
| · | user wants to present stable state of calculations for particular large project very quickly |
| · | etc. |
Note that for large projects user has to take into account amount of also large hard disk space used during freeze operation, which is approximately equal of the project RAM memory requirements.
Breakpoints
In standard operation QW-Simulator executes a sequence of tasks specified in the tasker (*.ta3) file. Tasker files generated by QW-Editor refer to one particular project. QW-Simulator is prepared to execute more complicated tasker files, including a variety of commands for saving results and field patterns, and possibly referring to several different projects.
Here let us explain how tasker files may be created. We may use either Breakpoints and dialogues of QW-Simulator or any text editor. The advantage of using the Breakpoints mechanism is that it ensures correct syntax of generated files and prompts the user to provide all the necessary information.
The notions of breakpoints and tasks will be used alternatively as the difference between the two is rather philosophical. Breakpoints are related to interactive operation of QW-Simulator and meant to suspend its action or save requested data at specific iteration points. Tasks are related to batch operation. The syntax of both is identical, however.
Here let us explain how tasker files may be created. We may use either Breakpoints and dialogues of QW-Simulator or any text editor. The advantage of using the Breakpoints mechanism is that it ensures correct syntax of generated files and prompts the user to provide all the necessary information.
The notions of breakpoints and tasks will be used alternatively as the difference between the two is rather philosophical. Breakpoints are related to interactive operation of QW-Simulator and meant to suspend its action or save requested data at specific iteration points. Tasks are related to batch operation. The syntax of both is identical, however.
For presented example the volume envelope (VolMax) of the Ez field is constructed for 50 iterations starting at iteration 1000, over the user-defined sub-volume (0..22, 0..20, 0..59), and saved in the file.
Sequence of tasks
In standard operation QW-Simulator executes a sequence of tasks specified in the tasker (*.ta3) file. Tasker files generated by QW-Editor refer to one particular project. QW-Simulator is prepared to execute more complicated tasker files, including a variety of commands for saving results and field patterns, and possibly referring to several different projects. For creating tasker files, Breakpoints mechanism is recommended.
In standard operation QW-Simulator executes a sequence of tasks specified in the tasker (*.ta3) file. Tasker files generated by QW-Editor refer to one particular project. QW-Simulator is prepared to execute more complicated tasker files, including a variety of commands for saving results and field patterns, and possibly referring to several different projects. For creating tasker files, Breakpoints mechanism is recommended.
Batch operation
Optimisation or grid search in a batch mode
Starting with version 7.0, it is possible to set up a batch job for making several consecutive runs of optimisation or grid search. Messages informing that QW-OptimiserPlus works in the Batch Run mode will appear in the Optimiser Info tab of the Simulation Log window.
Starting with version 7.0, it is possible to set up a batch job for making several consecutive runs of optimisation or grid search. Messages informing that QW-OptimiserPlus works in the Batch Run mode will appear in the Optimiser Info tab of the Simulation Log window.
Links to optimisers
Shape optimisation using Matlab
QW-OptimizerPlus available as a part of the QuickWave package is a useful and easy-to-use tool in optimisation projects where the goal is to optimise S-parameters or radiation pattern of a microwave structure by adjusting specified parameters of that circuit. However, when it comes to more complicated tasks like optimisation of a complex shape of some structure, Matlab and other computational environments may have an advantage over closed, highly-specialised tools like QW-OptimizerPlus.
Let us have a look at a rectangular waveguide mode converter as an example of such complex project. All files used in this example are included in the QuickWave installation and require that the user has an access to Matlab version 6.0 or newer. A mode converter is a lossless microwave structure in which the wave at the input propagates as the m-th mode but it reaches the output as the n-th mode, and the m ¹ n. It is also important to ensure that mode conversion is done efficiently or that the energy of the output mode is as close as possible to the energy of the input mode.
QW-OptimizerPlus available as a part of the QuickWave package is a useful and easy-to-use tool in optimisation projects where the goal is to optimise S-parameters or radiation pattern of a microwave structure by adjusting specified parameters of that circuit. However, when it comes to more complicated tasks like optimisation of a complex shape of some structure, Matlab and other computational environments may have an advantage over closed, highly-specialised tools like QW-OptimizerPlus.
Let us have a look at a rectangular waveguide mode converter as an example of such complex project. All files used in this example are included in the QuickWave installation and require that the user has an access to Matlab version 6.0 or newer. A mode converter is a lossless microwave structure in which the wave at the input propagates as the m-th mode but it reaches the output as the n-th mode, and the m ¹ n. It is also important to ensure that mode conversion is done efficiently or that the energy of the output mode is as close as possible to the energy of the input mode.
Designed by Janusz Rudnicki
Updated: March 19, 2008
The Ez field in the mode converter structure -
the starting shape
the starting shape
The Ez field in the mode converter structure -
the optimised shape
the optimised shape
Contenets of the Matlab script after the routine has converged to a solution
Comparison of the S21 curves of the starting case and optimised case
General view of the structure
Using the spline interpolation algorithm it is possible to design the shape of the waveguide wall in the Matlab environment based on a few parameters and transfer it to a QuickWave project through a text file. After its creation, the file can be opened by a UDO object which can draw a piece of the rectangular waveguide according to the shape description prepared by Matlab. If the UDO can additionally prepare ports, then one has a full project that can be modelled by the QW-Simulator.
Basic Heating Module
QWED has started the development of specialised versions of its QuickWave software, which obviate the above limitations of standard EM solvers, and facilitate faster and more accurate simulations of microwave power processes. Basic Heating Module for QuickWave (further referred to by an abbreviation QW-BHM) is the first module of the family. It provides a novel regime of operating the FDTD solver, with modification of media parameters as a function of dissipated energy. It also facilitates load rotation and heat flow analysis through the QW-HFM (Heat Flow Module) module. Starting with version 6.5, it provides a regime of automatic tuning of the source to the deepest in-band resonance.
However, when we take into account that a real heating process may require tens or even hundreds of heating steps, the interactive operation will become inconvenient. A batch mode is then recommended. Arbitrarily complex tasker files for controlling the batch mode can be created by the user using Breakpoints dialogue of QW-Simulator. Tasker files corresponding to the most popular options of running BHM can also be automatically exported by QW-Editor.
QWED has started the development of specialised versions of its QuickWave software, which obviate the above limitations of standard EM solvers, and facilitate faster and more accurate simulations of microwave power processes. Basic Heating Module for QuickWave (further referred to by an abbreviation QW-BHM) is the first module of the family. It provides a novel regime of operating the FDTD solver, with modification of media parameters as a function of dissipated energy. It also facilitates load rotation and heat flow analysis through the QW-HFM (Heat Flow Module) module. Starting with version 6.5, it provides a regime of automatic tuning of the source to the deepest in-band resonance.
However, when we take into account that a real heating process may require tens or even hundreds of heating steps, the interactive operation will become inconvenient. A batch mode is then recommended. Arbitrarily complex tasker files for controlling the batch mode can be created by the user using Breakpoints dialogue of QW-Simulator. Tasker files corresponding to the most popular options of running BHM can also be automatically exported by QW-Editor.
There are specific tasks for QW-BHM operations - family of Modify Media Parameters tasks with construction of average dissipated power pattern, updating the enthalpy and temperature patterns and re-calculating the parameters matrices.
Fluent mode in QW-HFM module
One of the development goals of the QW-HFM module has been providing a tool, which lets the user perform a coupled analysis of microwave heating problems but requires that the data needed for the simulation be prepared only once - in the QuickWave simulation package. With QW-HFM module it is possible to discretise a geometry using the QuickWave software, and use the same computational mesh (complete with thermal media properties and boundary conditions) in the Fluent CFD tool. Such an approach completely eliminates the need for interpolation of the data between the two codes, because Fluent software is based on FVM method (Finite Volume Method) which is similar to the modified FDTD algorithm implemented in QuickWave package. It also improves the accuracy of the overall solution and limits the chances for human mistakes.
The heat flow analysis performed with QW-HFM module run in the Fluent does not require any interaction with the user. The QW-HFM module extracts the lossy part of the project, which can contain multiple objects made of lossy media. Preserves the original mesh inside the extracted objects and creates the mesh for Fluent. The mesh is saved to a text file built according to the FDNEUT format that can be imported into the Fluent environment.
One of the development goals of the QW-HFM module has been providing a tool, which lets the user perform a coupled analysis of microwave heating problems but requires that the data needed for the simulation be prepared only once - in the QuickWave simulation package. With QW-HFM module it is possible to discretise a geometry using the QuickWave software, and use the same computational mesh (complete with thermal media properties and boundary conditions) in the Fluent CFD tool. Such an approach completely eliminates the need for interpolation of the data between the two codes, because Fluent software is based on FVM method (Finite Volume Method) which is similar to the modified FDTD algorithm implemented in QuickWave package. It also improves the accuracy of the overall solution and limits the chances for human mistakes.
The heat flow analysis performed with QW-HFM module run in the Fluent does not require any interaction with the user. The QW-HFM module extracts the lossy part of the project, which can contain multiple objects made of lossy media. Preserves the original mesh inside the extracted objects and creates the mesh for Fluent. The mesh is saved to a text file built according to the FDNEUT format that can be imported into the Fluent environment.
Fluent computational mesh (constructed for lossy sample)
On the walls of the extracted objects boundary conditions chosen by the user are imposed. In order to facilitate this process in case of Dirichlet or Convective boundary conditions, a set of additional text files is created containing temperature distribution at the boundaries. After the analysis has been completed it is saved to an intermediary text file which will be additionally post-processed by the QW-HFM module in order to convert it to the *.hfi data file. After the *.hfi file is ready the QW-HFM module quits and passes the control back to the QuickWave package. The QuickWave package reads the *.hfi file containing results of the computations done externally, updates the enthalpy field and proceeds with the simulation.
The Fluent’s main window popping up on screen during simulation has been provided so that the user is fully informed about the progress of the simulation. Also, the window may become handy in case of any problems with the simulation when the messages displayed there can make it much easier to understand the situation. However, in the majority of cases it is not needed and can be turned off by setting the FluentVisible option in the initialization file to “false”. After it has been done the Fluent window will not be displayed on screen. The default option is “true”.
A specialised phase-change model has also been implemented in the Fluent software. It assumes, however, that the H=f(T) curve of a medium has clearly defined solidus and liquidus temperatures, between which a phase-change occurs. This is not the case in majority of microwave heating problems involving food products, where a gradual change of the curve is rather observed. Because of these reasons, if the QW-HFM module works in the Fluent mode and the user sets the UseNonlinearModel option of the initialisation file to “true”, the QW-HFM does not make use of the Fluent’s phase-change model. Instead, it defines a medium by providing a specific heat vs. temperature data extracted from the H=f(T) curve. More information about the phase-change model implemented in Fluent can be found in the documentation of the tool.
A specialised phase-change model has also been implemented in the Fluent software. It assumes, however, that the H=f(T) curve of a medium has clearly defined solidus and liquidus temperatures, between which a phase-change occurs. This is not the case in majority of microwave heating problems involving food products, where a gradual change of the curve is rather observed. Because of these reasons, if the QW-HFM module works in the Fluent mode and the user sets the UseNonlinearModel option of the initialisation file to “true”, the QW-HFM does not make use of the Fluent’s phase-change model. Instead, it defines a medium by providing a specific heat vs. temperature data extracted from the H=f(T) curve. More information about the phase-change model implemented in Fluent can be found in the documentation of the tool.
Enthalpy field solution (displayed by Fluent)
Fluent window after the analysis has been run
QuickWave View Fields window containing the temperature field obtained from the new enthalpy field
Command line options
Sequence of tasks
Basic Heating Module
Optimisation or grid search in a batch mode
Sequence of tasks
Basic Heating Module
Optimisation or grid search in a batch mode
Command line options
It is possible to call QW-Editor and QW-Simulator from a command line with parameters.
The following options are possible for QW-Editor:
-pproject_name - starts the QW-Editor loading the specified project
-i - nforces iconised operation of QW-Editor
-e - instructs the QW-Editor to export the project
-q - quits the QW-Editor (reasonably, this should be preceded by export)
-m - instructs the QW-Editor to perform the Select Object-Modify operations on the object which has the same name as project. For reasonable application, the corresponding *.udo file describing this object (or some other *.udo and *.txt files called from within this file) should be previously modified by the user / optimiser.
-onumber_of_iterations - instructs the QW-Editor to further instruct the QW-Simulator to run the analysis for a specified number_of_iterations. The QW-Editor will comply by exporting modified files (modifications regarding RunIter instead of typical Run tasks, specified format of files for saving the results).
The following options are possible for QW-Simulator:
-h/? - starts the QW-Simulator, printing the description of available options in the Simulation Log.
-s file_name - starts the QW-Simulator, also performing File-Open and Run-Start commands on the file of specified name file_name.
-c file_name - starts the QW-Simulator, also performing File-Open and Run-Create commands on the file of specified name file_name.
-t file_name - starts the QW-Simulator, also performing File-Open and Run-Start commands on the file of specified name file_name. However, it does not open any application window. The user has no interaction possibilities, and also any graphical commands within in the tasker will be ignored. Thus for reasonable operation, this option should be used with a tasker file (*.ta3), and the tasker file should contain i.e Save_Results or Save_Antenna_Results tasks.
-v - starts the QW-Simulator, printing the version number in the Simulation Log.
-d - starts the QW-Simulator, printing the license date expiration and version limitations in the Simulation Log.
-l - locates the HASP dongle (-l1 enforces link to the local QW HASP dongle, -l3 enforces link of the network QW HASP dongle)
-o quiet_opt_options - starts the QW-Simulator in quiet mode (all warnings and errors are saved to the simwarnexit.txt file).
Unless otherwise specified, file_name denotes the name of a *.ta3, *.pa3, *.sh3 or *.sfr file, and its full path must be specified.
It is possible to call QW-Editor and QW-Simulator from a command line with parameters.
The following options are possible for QW-Editor:
-pproject_name - starts the QW-Editor loading the specified project
-i - nforces iconised operation of QW-Editor
-e - instructs the QW-Editor to export the project
-q - quits the QW-Editor (reasonably, this should be preceded by export)
-m - instructs the QW-Editor to perform the Select Object-Modify operations on the object which has the same name as project. For reasonable application, the corresponding *.udo file describing this object (or some other *.udo and *.txt files called from within this file) should be previously modified by the user / optimiser.
-onumber_of_iterations - instructs the QW-Editor to further instruct the QW-Simulator to run the analysis for a specified number_of_iterations. The QW-Editor will comply by exporting modified files (modifications regarding RunIter instead of typical Run tasks, specified format of files for saving the results).
The following options are possible for QW-Simulator:
-h/? - starts the QW-Simulator, printing the description of available options in the Simulation Log.
-s file_name - starts the QW-Simulator, also performing File-Open and Run-Start commands on the file of specified name file_name.
-c file_name - starts the QW-Simulator, also performing File-Open and Run-Create commands on the file of specified name file_name.
-t file_name - starts the QW-Simulator, also performing File-Open and Run-Start commands on the file of specified name file_name. However, it does not open any application window. The user has no interaction possibilities, and also any graphical commands within in the tasker will be ignored. Thus for reasonable operation, this option should be used with a tasker file (*.ta3), and the tasker file should contain i.e Save_Results or Save_Antenna_Results tasks.
-v - starts the QW-Simulator, printing the version number in the Simulation Log.
-d - starts the QW-Simulator, printing the license date expiration and version limitations in the Simulation Log.
-l - locates the HASP dongle (-l1 enforces link to the local QW HASP dongle, -l3 enforces link of the network QW HASP dongle)
-o quiet_opt_options - starts the QW-Simulator in quiet mode (all warnings and errors are saved to the simwarnexit.txt file).
Unless otherwise specified, file_name denotes the name of a *.ta3, *.pa3, *.sh3 or *.sfr file, and its full path must be specified.