Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/LabPy/labpy-discussion/issues/23 below:

Catalog the python lab automation landscape · Issue #23 · LabPy/labpy-discussion · GitHub

• Pricing

To consolidate efforts, it's important to get an overview of the different available packages. These should be analysed w.r.t. various parameters (to be defined, but things like maintenance status, activity level, maturity, design goals, scope of features, number of instrument drivers, automated test availability, ...).

Edit: Spreadsheet can be found here!
(Ethercalc has moved, link fixed 2021-01-09; site seems to be slow)

Since this is quite the large task, I have, as a first step, compiled a list of any packages mentioned in the discussion in pymeasure/pymeasure#53, as well as some from my notes:

• https://github.com/ralph-group/pymeasure
• https://www.github.com/Galvant/InstrumentKit
• https://github.com/LabPy/lantz
• https://github.com/pyvisa/pyvisa
• https://github.com/python-ivi/python-ivi
• https://github.com/BBN-Q/Auspex
• https://github.com/dursobr/Pythics and https://github.com/avelo/Pythics
• https://github.com/Exopy/i3py and https://github.com/Exopy/exopy
• https://github.com/QCoDeS/Qcodes
• https://github.com/heeres/qtlab (Inspiration for QCodes)
• https://github.com/pazzarpj/Fixate
• https://github.com/pyinstruments/pyinstruments
• https://github.com/masonlab/labdrivers
• https://github.com/Ulm-IQO/qudi
• https://github.com/LaboratoireMecaniqueLille/crappy
• https://github.com/mabuchilab/Instrumental
• https://github.com/PALab/place
• https://github.com/uetke/experimentor
• https://github.com/MatthieuDartiailh/HQCMeas (superceded by Exopy)
• https://itom.bitbucket.io/
• https://github.com/p3trus/slave
• https://github.com/wking/pycomedi
• https://pythonhosted.org/PyDAQmx/
• https://github.com/ni/nidaqmx-python
• https://github.com/NSLS-II/bluesky
• https://github.com/NSLS-II/ophyd

Preliminary list of things to note (i.e. columns in a spreadsheet) when testing packages

• Name
• One-sentence/paragraph description (e.g. from Github project description or README)
• Homepage
• Documentation URL
• nr. of commits/age, e.g. 5542/4y
• Date of latest commit
• Test system (approx. number of tests), e.g. pytest(700)
• scope: instrument/hardware communication?
• scope: live control of instruments?
• scope: running predefined procedures?
• scope: GUI/presentation layer?
• number of instrument drivers available
• types of compatible instruments (text based, register map, vendor DLL, COM protocol,...)
• unit support? (library used), e.g. yes(pint)
• License
• ... please suggest additional useful things to know.

tinix84, FilipDominec and jakeoghwagnerpeer and untzag

You can’t perform that action at this time.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4