Signalintegrity

Latest version: v1.4.1

Safety actively analyzes 682387 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 5 of 6

1.1.1

As mentioned in the last release notes, the internals of the project file were completely restructured in that release. That release had the temporary capability of reading the old file format, but when projects were saved, they were saved in the new format. In this release, all capability of reading the old file structure has been removed.

**If you have old project files with the extension .xml, before installing this release, you should install version 1.1.0, read in all of your old project files and save them. Only when all of your project files that you want have the .si extension, should you install this release**

The major feature add in this release is that of using projects as parts and waveforms. As you know, there are four major applications currently of the software. Two of them, system s-parameter calculations and de-embedding applications produce s-parameters as results. De-embedding and s-parameter __project__ files can now be placed in your schematics as parts. The other two applications, virtual probing and simulation produce waveforms. These waveforms can now be placed in your schematic as voltage or current sources.

To place an s-parameter producing project in your schematic, select a file device, and browse or name the project file (instead of an .sXp file) and during the calculation, it will calculate the s-parameters and use them in your schematic.

To place a waveform producing project in your schematic, place a current source, voltage source, or virtual probe measurement probe in your schematic. browse to or enter the name of a project file (instead of a waveform .txt file). You will see a new entry appear that allows you to enter the waveform name from the project - this must be the name of one of the output probes in that project.

* A few bugs were fixed in this release, including some labels disappearing and overall stability improvements.

* In the schematic editor, you can now use the arrow keys to move parts, wires and groups of parts around. You will see the focus set on the schematic canvas when parts are selected, indicating the keyboard is now bound to the canvas. You can also use the arrow keys to pan.

* During the work on this release, I found some issues with part placement, rotation, and pin numbering. These were quite disconcerting and led me to create proper part pictures, along with alternates with different pin locations, for all of the amplifiers. If you hadn't been using transconductance, transresistance, or current amplifiers, you will not notice any difference. If you were, your projects won't work properly (they didn't before, either, in the case of the transconductance amplifier).

* If you use TikZ output - which I use for the book I'm writing, you will now find that the text is perfectly placed now - previously, some readjustment was necessary. Now TikZ output pictures can be placed directly into LaTeX documents. And if you use reference designators with $ surrounding the text, they will even be printed in math mode.

* Now, in the calculation properties, you will see the base sample period and the user sample period.

1.1.0

In this release, the project file has been internally restructured. This is due to the fact that the previous project file suffered from the following problems:
* It was a direct image of the internal configuration of the devices which was loaded verbatim into the device properties. This meant
* It had a lot of redundant information that is taken care of internally by the software (and was therefore larger than necessary).
* It did not adapt well to changes in the software that would have automatically changed certain behavior. An example of this is the pictures of the parts, which in some cases was incorrect in the old project files as corrections were made to the software).
* It was xml all on one line and could not be viewed at all by other than an xml viewer.

The new format is more compact, can be viewed in a text editor, and the default extension is now .si (as opposed to the old .xml). This means that you can now associate .si files with SignalIntegrity and the application will now open these files, assuming your operating system has been properly configured.

Also, now a file (for example named project.si), can now be opened by typing, on the command line:

SignalIntegtrity project

In the future, s-parameter files will also open this way.

Currently, when a project file is opened, the dialog shows only files with the extension .si, but for now, you can switch this to .xml and open your old xml files, if you have them. All project files are now saved only in the new format with the .si extension.

Since this restructuring made such a mess of the underlying code, support for the xml format will be fleeting. It will probably be removed in the next release. As the SignalIntegrity repository is not currently publicly available, the impact of this change is thought to be relatively small, but the bottom line is that you will need to at least open all of your xml files and save them again, thus converting them using this software release.

This very impacting internal change has been tested with the full suite of unit tests. This provided good coverage that projects in the old format behaved identically in the new format insofar as they produced the same netlists, calculation results, etc., but the UI was also impacted by these changes and this could not be tested exhaustively. I made the decision that it was time to make the jump to the new format. Enter any bugs you find, but do use this version.

1.0.5

This minor release includes three major new features:
* It is now possible to install the software in the regular manner (i.e. 'pip install .' or 'python setup.py install'. This capability eluded the developer up to now.
* The _help_ _system_ _keys_ are now in a file on the internet, along with the help system (instead of on the disk with the installation). These keys are late binding, meaning they are read only when you access the help system, and since the are along with the help system, this means that the help system can be updated completely independently from software version updates and still retain the proper indexing.
* Numerical capabilities have been added that allow the solution for _diabolical_ problems. These include:
* Simulations with current and differential probes, but no absolute ground reference.
* Situations where some components have no absolute ground reference at certain frequencies.
* S-parameter solutions with loops of wire and such were some internal waves, voltage, or currents cannot be calculated, but the port conditions can still be solved for.

The best example of this is the calculation of s-parameters with two parallel wires.
This numerical capability is controlled through a new preference called _TrySVD_ and is still considered experimental, as it can produce incorrect answers in cases like voltage sources connected directly to ground.

1.0.4

This is the fourth minor release of SignalIntegrity, but it has some really major changes in that it will now run on both Python 2.7.x distributions and Python 3.6.x distributions (and assumedly higher).

For now and probably for a long time, support will be maintained for working on both Python 2 and 3.

The intensive 1000 unittests pass on both Python 2 and 3, although Python 3 spews future deprecation warnings. All of the manageable ones have been fixed, but one warning remains (although repeats over and over during coverage testing) about the matrix class. This warning is flat out wrong, and I can't seem to figure out how to suppress this. The tests all pass, however.

The preferences file is now streamlined and some new preferences added, namely the ability to utilize the plot cursors in matplotlib, which turn out to be somewhat problematic sometimes. This release will clear your old preferences - sorry about that - they will be set to the default. This will not happen in future releases.

In converting to Python 3, a few bugs were found and fixed. Of interest is schematic part rotation. They now always rotate about the center. This fix might break some existing schematics containing rotated amplifiers - although all of the examples have been fixed.

More test coverage was added. All part pictures are covered along with the spline class (which also involved some bug fixing).

See [Installation](https://github.com/TeledyneLeCroy/SignalIntegrity/wiki/Installation) for installation instructions.

1.0.3

This is the same as the last minor release, but the last minor release did not work properly on Windows machines - the app worked, but not scripted solutions including the tests.

See [Installation](https://github.com/TeledyneLeCroy/SignalIntegrity/wiki/Installation) for installation instructions.

1.0.2

changed the name to its final name SignalIntegrity.

The old name was too cute and was taken anyway. When this is finally released to the world, it can be submitted on PyPI with the new name.

See [Installation](https://github.com/TeledyneLeCroy/SignalIntegrity/wiki/Installation) for installation instructions.

Page 5 of 6

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.