keysight

keysight is a Python 3.4+ package providing modules and helpers to work with data files from Keysight Technologies (formerly Agilent/HP) test equipment.

Dependencies

Runtime Dependencies

• numpy

Development Dependencies

• invoke
• nose
• unipath

Support Keysight Equipment

Spectrum Analyzers

Below are the modules available in the keysight package and the compatible equipment for each module:

• n9340: N9340 spectrum analyzer
• e4411b: E4411B, E4402B spectrum analyzers

Contributing

Use the following commands to create a Python 3.9.9 virtualenv using pyenv and pyenv-virtualenv, install the requirements in the virtualenv named keysight, and list the available Invoke tasks.

$ brew install pyenv pyenv-virtualenv
$ pyenv install 3.13
$ pyenv virtualenv 3.13 keysight
$ pyenv activate keysight
$ pip install -U pip
$ pip install -r requirements.txt
$ inv -l

Sample CSV and other data files

Currently, the only sample files tested are the CSV files from a N9340B and E4411B spectrum analyzer. If you have other data files saved from a Keysight/Agilent/HP piece of test equipment and are willing to share it, please open an issue or submit a pull request to let us know.

Submitting Pull Requests

keysight is developed using Scott Chacon's GitHub Flow. To contribute, fork keysight, create a feature branch, and then submit a pull request. GitHub Flow is summarized as:

• Anything in the master branch is deployable
• To work on something new, create a descriptively named branch off of master (e.g., new-oauth2-scopes)
• Commit to that branch locally and regularly push your work to the same named branch on the server
• When you need feedback or help, or you think the brnach is ready for merging, open a pull request.
• After someone else has reviewed and signed off on the feature, you can merge it into master.
• Once it is merged and pushed to master, you can and should deploy immediately.

Testing

License

keysight is released under the MIT license. Please see the LICENSE.txt file for more information.