Package: peng
DescriptionThis package provides engineering-related classes and functions, including:A waveform class that is a first-class object:>>>importcopy,numpy,peng>>>obj_a=peng.Waveform(...indep_vector=numpy.array([1,2,3]),...dep_vector=numpy.array([10,20,30]),...dep_name='obj_a'...)>>>obj_b=obj_a*2>>>print(obj_b)Waveform:obj_a*2Independentvariable:[1,2,3]Dependentvariable:[20,40,60]Independentvariablescale:LINEARDependentvariablescale:LINEARIndependentvariableunits:(None)Dependentvariableunits:(None)Interpolatingfunction:CONTINUOUS>>>obj_c=copy.copy(obj_b)>>>obj_a==obj_bFalse>>>obj_b==obj_cTrueNumerous functions are provided (trigonometric,
calculus, transforms, etc.) and creating new functions that operate on
waveforms is simple since all of their relevant information can be accessed
through propertiesHandling numbers represented in engineering notation, obtaining
their constituent components and converting to and from regular
floats. For example:>>>importpeng>>>x=peng.peng(1346,2,True)>>>x'   1.35k'>>>peng.peng_float(x)1350.0>>>peng.peng_int(x)1>>>peng.peng_frac(x)35>>>str(peng.peng_mant(x))'1.35'>>>peng.peng_power(x)EngPower(suffix='k',exp=1000.0)>>>peng.peng_suffix(x)'k'Pretty printing Numpy vectors. For example:>>>from__future__importprint_function>>>importpeng>>>header='Vector: '>>>data=[1e-3,20e-6,30e+6,4e-12,5.25e3,-6e-9,70,8,9]>>>print(...header+peng.pprint_vector(...data,...width=30,...eng=True,...frac_length=1,...limit=True,...indent=len(header)...)...)Vector:[1.0m,20.0u,30.0M,...70.0,8.0,9.0]Formatting numbers represented in scientific notation with a greater
degree of control and options than standard Python string formatting.
For example:>>>importpeng>>>peng.to_scientific_string(...number=99.999,...frac_length=1,...exp_length=2,...sign_always=True...)'+1.0E+02'InterpreterThe package has been developed and tested with Python 2.7, 3.5, 3.6 and 3.7
under Linux (Debian, Ubuntu), Apple macOS and Microsoft WindowsInstalling$pipinstallpengDocumentationAvailable atRead the DocsContributingAbide by the adoptedcode of conductFork therepositoryfrom GitHub and
then clone personal copy[1]:$github_user=myname$gitclone--recurse-submodules\https://github.com/"${github_user}"/peng.gitCloning into 'peng'...
...$cdpeng||exit1$exportPENG_DIR=${PWD}$The package uses two sub-modules: a set of custom Pylint plugins to help with
some areas of code quality and consistency (under thepylint_pluginsdirectory), and a lightweight package management framework (under thepypkgdirectory). Additionally, thepre-commit frameworkis used to perform various pre-commit code
quality and consistency checks. To enable the pre-commit hooks:$cd"${PENG_DIR}"||exit1$pre-commitinstallpre-commit installed at .../peng/.git/hooks/pre-commit$Ensure that the Python interpreter can find the package modules
(update the$PYTHONPATHenvironment variable, or usesys.paths(),
etc.)$exportPYTHONPATH=${PYTHONPATH}:${PENG_DIR}$Install the dependencies (if needed, done automatically by pip):Cog(2.5.1 or newer and older than 3.0.0)Coverage(4.5.3 or newer)Decorator(4.4.0 or newer)Docutils(0.14 or newer)Funcsigs(Python 2.x only, 1.0.2 or newer)Inline Syntax Highlight Sphinx Extension(0.2 or newer)Numpy(1.16.2 or newer)Pexdoc(1.1.4 or newer)Pmisc(1.5.8 or newer)PyParsing(2.3.1 or newer)Pydocstyle(3.0.0 or newer)Pylint(Python 2.x: 1.9.4 or newer, Python 3.x: 2.3.1 or newer)Pytest(4.3.1 or newer)Pytest-coverage(2.6.1 or newer)Pytest-pmisc(1.0.7 or newer)Pytest-xdist(optional, 1.26.1 or newer)ReadTheDocs Sphinx theme(0.4.3 or newer)Scipy(1.2.1 or newer)Shellcheck Linter Sphinx Extension(1.0.8 or newer)Six(1.12.0 or newer)Sphinx(1.8.5 or newer)Tox(3.7.0 or newer)Virtualenv(16.4.3 or newer)Implement a new feature or fix a bugWrite a unit test which shows that the contributed code works as expected.
Run the package tests to ensure that the bug fix or new feature does not
have adverse side effects. If possible achieve 100% code and branch
coverage of the contribution. Thorough package validation
can be done via Tox and Pytest:$PKG_NAME=pengtoxGLOB sdist-make: .../peng/setup.py
py27-pkg create: .../peng/.tox/py27
py27-pkg installdeps: -r.../peng/requirements/tests_py27.pip, -r.../peng/requirements/docs_py27.pip
...
  py27-pkg: commands succeeded
  py35-pkg: commands succeeded
  py36-pkg: commands succeeded
  py37-pkg: commands succeeded
  congratulations :)$Setuptoolscan also be used
(Tox is configured as its virtual environment manager):$PKG_NAME=pengpythonsetup.pytestsrunning tests
running egg_info
writing peng.egg-info/PKG-INFO
writing dependency_links to peng.egg-info/dependency_links.txt
writing requirements to peng.egg-info/requires.txt
...
  py27-pkg: commands succeeded
  py35-pkg: commands succeeded
  py36-pkg: commands succeeded
  py37-pkg: commands succeeded
  congratulations :)$Tox (or Setuptools via Tox) runs with the following default environments:py27-pkg,py35-pkg,py36-pkgandpy37-pkg[3]. These use
the 2.7, 3.5, 3.6 and 3.7 interpreters, respectively, to test all code in
the documentation (both in Sphinx*.rstsource files and in
docstrings), run all unit tests, measure test coverage and re-build the
exceptions documentation. To pass arguments to Pytest (the test runner) use
a double dash (--) after all the Tox arguments, for example:$PKG_NAME=pengtox-epy27-pkg---n4GLOB sdist-make: .../peng/setup.py
py27-pkg inst-nodeps: .../peng/.tox/.tmp/package/1/peng-1.0.11.zip
...
  py27-pkg: commands succeeded
  congratulations :)$Or use the-aSetuptools optional argument followed by a quoted
string with the arguments for Pytest. For example:$PKG_NAME=pengpythonsetup.pytests-a"-e py27-pkg -- -n 4"running tests
...
  py27-pkg: commands succeeded
  congratulations :)$There are other convenience environments defined for Tox[3]:py27-repl,py35-repl,py36-replandpy37-replrun the
Python 2.7, 3.5, 3.6 and 3.7 REPL, respectively, in the appropriate
virtual environment. Thepengpackage is pip-installed by Tox when
the environments are created.  Arguments to the interpreter can be
passed in the command line after a double dash (--).py27-test,py35-test,py36-testandpy37-testrun Pytest
using the Python 2.7, 3.5, 3.6 and 3.7 interpreter, respectively, in the
appropriate virtual environment. Arguments to pytest can be passed in
the command line after a double dash (--) , for example:$PKG_NAME=pengtox-epy27-test---xtest_peng.pyGLOB sdist-make: .../peng/setup.py
py27-pkg inst-nodeps: .../peng/.tox/.tmp/package/1/peng-1.0.11.zip
...
  py27-pkg: commands succeeded
  congratulations :)$py27-test,py35-test,py36-testandpy37-testtest code
and branch coverage using the 2.7, 3.5, 3.6 and 3.7 interpreter,
respectively, in the appropriate virtual environment. Arguments to
pytest can be passed in the command line after a double dash (--).
The report can be found in${PENG_DIR}/.tox/py[PV]/usr/share/peng/tests/htmlcov/index.htmlwhere[PV]stands for2.7,3.5,3.6or3.7depending
on the interpreter used.Verify that continuous integration tests pass. The package has continuous
integration configured for Linux, Apple macOS and Microsoft Windows (all viaAzure DevOps).Document the new feature or bug fix (if needed). The script${PENG_DIR}/pypkg/build_docs.pyre-builds the whole package
documentation (re-generates images, cogs source files, etc.):$"${PENG_DIR}"/pypkg/build_docs.py-husage: build_docs.py [-h] [-d DIRECTORY] [-r]
                     [-n NUM_CPUS] [-t]

Build peng package documentation

optional arguments:
  -h, --help            show this help message and exit
  -d DIRECTORY, --directory DIRECTORY
                        specify source file directory
                        (default ../peng)
  -r, --rebuild         rebuild exceptions documentation.
                        If no module name is given all
                        modules with auto-generated
                        exceptions documentation are
                        rebuilt
  -n NUM_CPUS, --num-cpus NUM_CPUS
                        number of CPUs to use (default: 1)
  -t, --test            diff original and rebuilt file(s)
                        (exit code 0 indicates file(s) are
                        identical, exit code 1 indicates
                        file(s) are different)Footnotes[1]All examples are for thebashshell[2]It is assumed that all the Python interpreters are in the executables
path. Source code for the interpreters can be downloaded from Python’s mainsite[3](1,2)Tox configuration largely inspired byIonel’s codelogLicenseThe MIT License (MIT)Copyright (c) 2013-2019 Pablo Acosta-SerafiniPermission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the “Software”), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
.. CHANGELOG.rst
.. Copyright (c) 2013-2019 Pablo Acosta-Serafini
.. See LICENSE for detailsChangelog1.0.11 [2019-06-11]: Fixed ReadTheDocs build1.0.10 [2019-06-10]: Updated development dependencies1.0.9 [2019-03-22]: Documentation and dependency update1.0.8 [2019-03-08]: Speedup loading of large Touchstone files (Patch submitted
by github/sotw1957). Minor other code style changes.1.0.7 [2019-03-08]: Dropped support for Python 2.6, 3.3 and 3.4. Updates
to support newest versions of dependencies. Abstracted package management to
a lightweight framework1.0.6 [2016-02-11]: Package build enhancements and fixes1.0.5 [2016-02-09]: Python 3.6 support1.0.4 [2016-09-19]: Fixed Touchstone read function for “MA” and “DB” formats
where the angles were incorrectly treated as being in radians1.0.3 [2016-07-29]: Fixed resolution loss when writing Touchstone files1.0.2 [2016-07-25]:Frequency vector is now always in Hertz regardless of unit used in
Touchstone fileMinor documentation bug fixes1.0.1 [2016-06-11]: Minor documentation build bug fix1.0.0 [2016-05-12]: Final release of 1.0.0 branch1.0.0rc1 [2016-05-11]: Initial commit, forked a subset from putil PyPI
package