start_panel_strip |
end_panel_strip |
Genesys 2015.08 Release Notes |
Spectrasys now supports frequency dependent behavioral models. It enables vendor spreadsheet frequency, temperature, and bias dependent nonlinear parameters such as 1dB compression, IP3 and IP2 to be conveniently used in the RF system simulation without the need to write custom equations. Spectrasys will automatically interpolate the multi-dimensional data defined by a muli-tab spreadsheet or System MDIF file for the component such as a power amplifier, for its correct characteristics at the frequency, temperature and bias used in simulation.
There are two modes of operation: 1) Normal or manual data entry or 2) Dataset or file based. When the simulator runs, spectrums are obviously created at various frequencies. With this feature, the characteristics of these spectrum will be a function of the frequency dependent parameters.
See the Frequency Dependency section for additional information.
In this mode users can conveniently enter frequencies and parameter values at those frequencies.This entry method also supports mixed parameter fixed and vector values. For example, if there is no frequency dependent data for a particular parameter the simulator will use the fixed value for all frequencies.
See the Supported Models for details on which models are supported for this mode.
When this mode is selected RF amplifier model data will automatically be extracted from a spreadsheet file (File > Import > Sys-Parameter Files > .csv, Excel or File > Import > ADS Files > System MDIF File ) that will automatically be imported onto the workspace tree. Multiple independent variables like temperature and power supply voltage can be supported in this mode when using an Excel file with data configured on multiple tabs.
See the Supported Models for details on which models are supported for this mode.
A frequency dependent library has been created in conjunction with MiniCircuits. Their library consists of both system level behavioral nonlinear frequency dependent models and passive linear S parameter models. Currently, there are 105 models.
A frequency dependent library has been created in conjunction with Analog Devices, Inc. Their library consist of system level behavioral nonlinear frequency dependent amplifier models. Currently, there are 88 models in the library.
AM to PM can be specified on the amplifier models, nonlinear block model, and the mixer models. There are 3 modes of operation: 1) Off, 2) Point Derivative, 3) Data Points. For the Point Derivative implementation, the user specifies the power level of a an AM / PM derivative and the value of the derivative. For the Data Points implementation a list of phase values are specified along with the power levels of those points. For more information, see Spectrasys AM to PM.
Frequency dependent behavioral model data may be stored and imported via a Keysight Sys-Parameter files can be imported into a dataset. The Sys-Parameters format is very flexible and can be implemented in a spreadsheet, csv, or MDIF files. Multiple sheets are used to represent multidimensional data.
For more information, see Importing Keysight Sys-Parameter Files.
ADS files such as GMDIF, MDIF, S2D, and P2D file import is supported. There are some limitations as Genesys does not have the ADS models that use these files directly. GMDIF and MDIF import support has been optimized around importing behavioral data for simulation so there are some aspects of these files that may not be imported fully. Since Genesys does not have a Data Access Component (DAC), you can import the data into a dataset. Moreover, a new getinterpdata function can be used to extract the data of interest that can be used elsewhere in the product.
For more information, see ADS File Import.
Since Genesys does not have a Data Access Component (DAC) we import the data into a dataset and a new getinterpdata function can be used to extract the data of interest that can be used elsewhere in the product. This is powerful multidimensional interpolator that can extract data from a multidimensional dataset.
For more information on getinterpdata, please visit getinterpdata (Engineering Language) or getinterpdata (MATLAB Script).
An ambient temperature parameter Ta has been added to all models. When this value is empty the analysis temperature is used during simulation otherwise it will use the value specified. When an analysis is ran it will set the global temperature variable called TEMPERATURE. This value is then used by models with empty values. For linear devices the ambient temperature is used to calculate thermal noise. For all non linear devices the ambient temperature is used to calculated all non linear temperature dependent parameters including thermal noise.
The following illustrates a few sample MATLAB scripts for creating 3D graphs:
[xx,yy] = meshgrid(-1:.1:1,-1:.1:1); % a built-in Matlab Script expression
zz = xx.^2+yy.^2;
graph1 = graph_figure ('First Cartesian graph with wireframe'); % create a graphing object
graph1. add_mesh_data (xx,yy,zz,'salad_bowl_mesh'); % a 3D mesh plot with mesh grid is displayed
graph1. set_title ('Image of a salad bowl mesh'); % Title of the graph
graph1. set_label_x ('X Range'); % label for X-axis
graph1. set_label_y ('Y Range'); % label for Y-axis
graph1. set_label_z ('Z Range'); % label for Z-axis
graph2 = graph_figure ('Cartesian graph without wireframe');
graph2. add_surface_data (xx,yy,zz,'salad_bowl_surface'); % a 3D surface plot is displayed; explicitly name the trace with the 4th (an optional) argument
graph2. set_title ('Image of a salad bowl surface'); % Title of the graph can be set after the image is created
[theta,phi] = meshgrid(linspace(-pi,pi,88),linspace(-pi/2,pi/2,69));
rho = 0.1 + sin(4*theta).*sin(2*phi);
graph3 = graph_figure ('First spherical graph');
graph3. add_spherical_data (theta,phi,rho,'sphr_16_lobe'); % a 3D spherical plot is displayed.
graph3. set_title ('8+8 lobes'); % Title of the graph
[x4,y4,z4]=sph2cart(theta,phi,rho); % a built-in Matlab Script expression
graph4 = graph_figure ('Spherical graph transformed to Cartesian graph');
graph4. add_mesh_data (x4,y4,z4); % a 3D mesh plot.
[a5,e5,r5]=cart2sph(x4,y4,z4); % a built-in Matlab Script expression
graph5 = graph_figure ('Spherical graph back again');
graph5. add_spherical_data (a5,e5,r5,'eight_lobe'); % a 3D spherical plot.
graph5. set_title ('8-lobe spherical'); % Title of the graph
graph6 = graph_figure ('Two images in one');
graph6. add_mesh_data (x4,y4,z4, 'tr_6a'); % image #1
graph6. add_mesh_data (xx,yy,zz, 'tr_6b'); % image #2
graph6. set_title ('Two 3D Shapes'); % Title of the graph
See 3D Graphing for additional information.
Avago components have been provided with required X-Parameter data files in the form of Avago X parameter library. Using the provided X-Parameter files, you can perform non-linear simulations in Genesys. To learn more about using these parameters, watch the X Parameter Library video available in your Genesys installation. These components are available in the Avago XP Parts library. They are extracted with 1-Tone X-Parameter files. Note that you must download the X-parameter files and install them at the standard location. These files are provided as self-extracting zip files. Refer to Using X-Parameter Libraries for detailed instructions on how to download and install the X parameter library.
MATLAB Script replaces the Math Language expression engine that was syntax compatible with MATLAB. MATLAB Script provides the scripting engine which is the same as MATLAB, and a limited subset of MATLAB functions to be used for equations and parameter expressions. You do not need to buy any license to use MATLAB Script engine and its functions.
Starting in Genesys 2015.08 release, MATLAB Script allows you to use your MATLAB. The supported MATLAB version is 2014a and later. You can use your MATLAB installation (MATLAB 2014a or later) from a workspace equation, a design equation, or the command prompt by switching to “Use MATLAB” in the right click menu. The corresponding MATLAB licenses are required when you use your MATLAB installation. Once you start to use your MATLAB from within Genesys, the corresponding MATLAB licenses will be held for the remainder of the Genesys session, and released on exit.
Starting in Genesys 2015.08 release, the equation debugger supports MATLAB Script equations.
MATLAB Script allows you to use external .m functions from a specified directory. The default MATLAB function directory is $HOME\Genesys\MATLAB. You can change the directory by using Tools > Options... > Directories > MATLAB Functions. In MATLAB Script mode, you can use external .m functions from the specified directory inside Genesys. However, .p functions, MATLAB classdef files and MATLAB script files are not supported in MATLAB Script mode. When switching to use MATLAB, you can use external functions and classdef files (in .m or .p) from the specified directory (Tools > Options... > Directories > MATLAB Functions) and from your MATLAB search path inside Genesys. The following tables show the supported context:
| .m File Content | Use MATLAB Script | Use MATLAB 2014a and later |
|---|---|---|
| function | supported | supported |
| classdef | not supported | supported |
| script | not supported | not supported |
| .p File Content | Use MATLAB Script | Use MATLAB 2014a and later |
|---|---|---|
| function | not supported | supported |
| classdef | not supported | supported |
| script | not supported | not supported |
| File Location | Use MATLAB Script | Use MATLAB 2014a and later |
|---|---|---|
| Tools > Options... > Directories > MATLAB Functions | supported | supported |
| MATLAB search path | not supported | supported |
In Genesys, workspace variables, design variables, and dataset variables support the " double precision floating point, 32 bit integer, unitcode strings, boolean, and complex numbers in double precision floating point " datatypes for serialization and deserialization. In MATLAB Script, you can use functions such as double, single, uint8, uint16, uint32, uint64, int8, int16, int32, int64, and logical to cast a variable to a specific datatype and precision. Within a MATLAB Script equation evaluation, the datatype is preserved. However, when a MATLAB Script variable is transferred to Genesys for storage, the variable is converted to one of the supported datatypes that can hold the value without losing the data. Once the variable is converted, it remains in the converted datatype when passing into MATLAB Script again.
In general, a value class can be transferred from a retail MATLAB equation (or command prompt) to a Genesys workspace and can be used later in another retail MATLAB equation (or command prompt). An example of the value class is ‘gf’ (Galois field array). On the other hand, a handle class has a reference to the actual object, and may not expect to work when transferring across the boundary between retail MATLAB and Genesys. The general guideline is to use handle classes just within a retail MATLAB equation, that is, create the handle class variable in the equation, delete, and clear the handle class variable before the end of the equation. For example:
a=tcpip('127.0.0.1',22);
fopen(a);
fwrite(a,3); % use the tcpip object
fclose(a);
delete(a);
clear a; |
You can use the 'isvalid' function of the handle class to test whether a variable is a valid handle. For MATLAB 2014b and later, you can use the 'ishghandle' function to test whether a variable is a valid Handle Graphics object.
In general, the performance of the equation system is comparable to the previous releases. You can even observe performance improvement in certain cases, for example, using heavy "for" loops or using computation intensive functions like "conv". However, due to architectural difference in MATLAB Script, you may observe performance degradation in the following conditions:
|
The following are the features in MATLAB Script that behave differently compared to Math Language (supported in releases prior to Genesys 2012.01):
|
The default equation language in Genesys is still Engineering Language , same as the previous releases. You can optionally switch to MATLAB Script or MATLAB in a workspace equation, a design equation, or the command prompt using the right click menu. |
The use model of equations has been updated to more closely align with the MATLAB use model.
Workspace tree equations now behave like scripts. The variables defined in them have workspace-wide scope (no matter where in the workspace hierarchy the equation is located) and so they can be used anywhere in the workspace (other tree equations, schematics, design equations, graphs, tables). Workspace tree equation variables are shown in the Workspace Variables viewer. You can enable Workspace Variables viewer from the menu bar (View > Workspace Variables).
A global Command Prompt is now available for equation scripting. The Command Prompt can access all Workspace Variables . The results of command prompt expressions execution are shown immediately in the Command Prompt as well as in the Workspace Variables viewer.
In previous releases, a Workspace tree equation window contained an equation script editor, a variable viewer showing the variables defined in the equations, and a command prompt. Now a workspace tree equation window is just an equation script editor. Variables created from a Workspace tree equation are now shown in the Workspace Variables viewer. The global Command Prompt replaces the local equation window ones compared to the previous releases.
Similarly, a design equation window is now just an equation editor for the design. Design parameters (defined in the Parameters tab of a design) and variables created in a design equation are now shown in the Design Variables viewer. The Design Variables viewer displays the variables of the design that is currently in focus (active window) or the design that was last in focus (if the current active window is not a design). You can enable Design Variables viewer from the menu bar (View > Design Variables).
A design has its own Design Variables scope; the Design Variables (including design parameters and the variables defined in the design equation) are only accessible within the design. The design variables are automatically cleared before the design equation is evaluated.
Specifically, for the MATLAB Script language, a function object is provided to define a MATLAB Script function. A Workspace tree equation or a design equation that uses MATLAB Script can only define a script. However, it can not define functions. For more details, see Using Equations and Functions in a Workspace. Note that the use model of defining and using a function in Engineering Language remains the same as in the previous Genesys releases.
If multiple workspaces are opened at the same time using the same instance of Genesys and these workspaces contain different definitions of the same MATLAB Script function, the behavior is undefined due to function name conflict. In this case, do not allow multiple open workspaces (Tools > Options > General) and reopen the workspace that you want to work on. |
Workspace Variables resolve an ambiguous situation where multiple Workspace tree equations can define the same variable with different values. In the previous release, the variable that is going to be used during an evaluation is undefined (assuming the equations that define the same variable are in scope). Now, the variable value is uniquely defined by the last equation that evaluates it and the value is displayed in the Workspace Variables viewer. The tooltip and "Go to definition" context menu can also be used to identify which equation defined the workspace variable.
Following are the tips specifically related to the equation use model update. See Tips for Effective Equation Writing for more details.
A new tutorial video, Equations_EngLang_and_MATLAB_Script, is created for introducing the new equation use model.
All variables have global scope even though they may exist in different equation blocks or located at different positions in the workspace tree. Furthermore, variables are persistent and are not removed until cleared by the user. Renaming a variable is a good example where the old variable name will still persist until cleared manually unless the equations were not executed between the renaming steps. |
If you have existing VB scripts that access equation variables through Application.Manager.<Workspace Name>.<Equation Name>.VarBlock, you need to change it to Application.Manager.<Workspace Name>.WorkspaceVariables.VarBlock. |
The use model of how a part parameter is evaluated has been updated to resolve the confusion between "Use MKS" and "Use Display" in previous releases. The "Use MKS" and "Use Display" options (provided at the top of the variable viewer frame of an equation window) have been removed from the product. In this release, when a part parameter has units and a variable (or an expression) is used to set its value, the following rules are used for parameter evaluation:
See Using Variables or Design Parameters to Set Part Parameters for more details.
The workspace file format has been changed to improve file integrity due to all backward incompatible use model changes made in this release. The workspaces created using the previous Genesys releases are automatically converted when they are opened. The original workspace is not modified unless you overwrite it by saving (File > Save) the converted workspace.
| The workspaces created using Genesys 2014.03 and later are incompatible with 2012.01 and prior releases. |
When an old format workspace is loaded and converted you will see an Information message in the Errors window notifying you that a conversion has happened. If there are any errors encountered during the conversion, a Conversion Log note object is created on the workspace tree; this note contains details about the conversion errors encountered. |
When loading old XML libraries such as Design, Part, Equation libraries, a dialog box is automatically displayed to convert the old XML library to the new format. You will need to provide a name for the new library and the converted library will be automatically loaded. The old libraries remain unchanged so you can still load them in previous versions. You can also run the conversion tool (see below) outside the product to convert your XML libraries to the new format.
A command line utility program, WorkspaceConversionTool.exe, is provided to convert multiple workspaces and XML libraries in a directory. The workspace conversion tool can be found in the <Genesys_Install_Directory>\bin directory.
The command line syntax of the conversion tool is like: WorkspaceConversionTool.exe "SourcePath" "DestinationPath".
For example: WorkspaceConversionTool.exe "C:\Examples\WorkspaceA_For2012_01.wsx" "C:\Examples\Converted\ConvertedWorkspaceA_For2015_08.wsg"
The conversion tool also works with directories. All workspaces in the source directory and any sub-directories are converted to the destination directory. Non-workspace files in the source directory are copied to the destination directory.
For example: WorkspaceConversionTool.exe "C:\Examples\MyWorkspaces" "C:\Examples\ConvertedWorkspaces"
The workspace conversion tool converts the following items to match the new use model in the current product:
Convert workspace tree Equation object that defines a Math Language function to a workspace tree Function object that defines a MATLAB Script function. The workspace conversion tool only handles the case where the first valid line in the original equation defines a function. If an equation block defines multiple functions, then only the first function will be converted to a function object. The other function(s) will exist only in the local scope of the converted function.
Convert setunits and getunits in Math Language to setdisplayunit and getdisplayunit in MATLAB Script. It also converts the old unit specification in setunits to the new unit specification in setdisplayunit.
Convert tuning syntax =? in Math Language to tune in MATLAB Script.
If there is a "clear" function call at the top of a MATLAB Script equation, the line will be commented out because it is no longer recommended to do so in the current version. Workspace tree equations share the same Workspace Variables. Putting "clear" at the top of a workspace tree equation is going to clear all workspace variables, including the ones defined in other workspace tree equations. Since design variables are always cleared before a design equation is evaluated, there is no need to put "clear" at the top of a MATLAB Scriptdesign equation.
The workspace conversion cannot preserve the behavior for the following cases and will report conversion errors or warnings after loading the converted workspace.
If a Math Language equation should be converted to a MATLAB Script function object, but the function name is already in use by another workspace tree object then the function object will not be created. The equation object cannot be renamed to another workspace tree object with the same name.
The unit use model has been updated since Genesys 2014.03 and is not compatible with 2012.01 and prior versions. The workspace conversion tool can convert prior workspaces to match the new unit behavior for most cases. However, here are the limitations:
A non-linear digital step attenuator part, model, and schematic symbol has been added.
A limiter part, model, and schematic symbol have been added. There is a new shipping example \Limiters\Limiter Basics.wsg showing the characteristics of the limiter.
All models that need a reference impedance now use a common parameters called Zref. In the past some models used Zo or ParamZ.
The models that were updated are:
The Multisource now supports a Frequency Comb source as well as a few Digital Modulation sources. The Multisource will now allow users the ability to mark a signal as an undesired signal. This gives users the ability to create interfering signals from the same Multisource where desired signals are created. The Multisource now supports frequency dependent port impedance.
The mixer models have a new parameter called Input Port (InPort) that is used to identify the primary input port of the mixer. This information is necessary to improve the S parameter accuracy of the mixer. The linear mixer model now support Conversion Gain in the forward direction and RF to IF Isolation in the reverse direction. This enables higher accuracy load impedances seen on the mixer input port due to varying mixer load impedances.
In simulation intensive workspaces like sweeps, monte carlo, and optimization of the a system design the simulation speed can generally be improved by turning off the 'Use Volterra Model' option located on the Calculate tab of the System Analysis. Turning off this option can decrease intermod accuracy. |
Current and voltage power supply parameters have been added to the active behavioral models. DC power supply measurements have been added to the main system analysis dataset that show users power supply requirements for the entire design. This includes the calculated DC supply power.
Added an SFDR parameter to the ADC that sets the level harmonics generated by the ADC.
Added ability for ADC spurs to be set either in dBc or dBFS.
Improved the ADC doc.
Improved the residual phase noise of the amplifier to only work on desired input spectrum and harmonics created from desired spectrum.
Fixed many issues with cascaded X parameters models.
Improved the accuracy of Phase Noise Channel Power (PNCP) measurement.
Improved the accuracy of Output Saturation Power (EOPSAT and OPSAT) measurements.
Add noise figure parameter to all SDATA_NL models
These videos can be found in Genesys by selecting Help > Tutorial Videos.
Old .wsp and .sch Workspace File Formats The .wsp and .sch workspace file formats (which are over 10 years old) are not supported anymore. To load an old workspace, you must first load it in Genesys 2012.01 and save it as a .wsx file and load that into Genesys 2014.03. If you don't have a copy of Genesys 2012.01 and need to install it, download it from our website.
We have created a simple tool called 'WSP to WSX Converter.exe' that will aid in bulk file conversions. This tool uses an installed version of Genesys 2012.01 to do the conversion. This tool allows the user to point to a .wsp input directory and a .wsx output directory. The tool can be found in the bin directory of the install. i.e. C:\Program Files\Genesys 2015.08\bin\WSP to WSX Converter.exe. Documentation for the tool is located in the startup screen of the tool.
Under the File menu, the Send as Email option has been obsoleted. Instead, you can simply attach a saved workspace to your email.
Workaround: Disable antivirus and other related programs on your system before installing. You can enable them once the installation is complete.