Commit 686363c0 authored by Jan Kotanski's avatar Jan Kotanski
Browse files

New upstream version 2.5.1.9

parent 01eb1517
......@@ -5,239 +5,6 @@ This file follows the formats and conventions from [keepachangelog.com]
## [Unreleased]
### Fixed
* Fix default macro parameter values in macroexecutor (#1153)
* Use `taurus.external.qt.compat.PY_OBJECT` in singal signatures instead of `object`
to avoid problems when using `builtins` from `future` (#1082)
## [2.8.0] 2019-07-01
### Added
* SEP2 - Improve integration of 1D and 2D experimental channels (#775):
* Possibility to report acquisition results in form of value references (in
the URI format) of 1D and 2D experimental channels:
* `Referable` base class to inherit from when developing a controller
plugin
* `ValueRef` and `ValueRefBuffer` Tango attributes and `value_ref` and
`value_ref_buffer` core attributes to propagate value references
proceeding from the controllers.
* Possibility to configure value referencing from the measurement group level
(_Ref Enabled_ and _Ref Pattern_ columns in expconf and
`value_ref_pattern` and `value_ref_enabled` configuration parameters) or
a single channel level (`ValueRefPattern` and `ValueRefEnabled` Tango
attributes) which both reach the controller plugin as axis parameters
`value_ref_pattern` and `value_ref_enabled`.
* Creation of Virtual Data Sets (VDS) for value references of _h5file_ scheme
in HDF5 file recorder.
* Possibility to still use pseudo counters based on 1D and 2D experimental
channels when value referencing is in use.
* Possibility to include 2D experimental channels in continuous acquisition
using value reporting (`ValueBuffer` Tango attribute to 2DExpChannel and
`value_buffer` core attribute)
* `VALUE_BUFFER_CODEC` and `VALUE_REF_BUFFER_CODEC` to sardanacustomsettings.
* Reintroduce `showscan online` to spock (#1042)
* Full support to *spock syntax* in loading sequences from files (#645, #672)
* Info in `lsmac` output about macros being overridden (#930, #947)
* Allow to configure timeout on pool element's (Taurus extensions) *go* methods e.g.
`move`, `count`, etc. (#992)
* Emulated hardware triggering between dummy counter/timer and trigger/gate elements
(#1100)
* Macro example demonstrating how to add an extra scan column with motor
positions shifted to the middle of the scan interval: `ascanct_midtrigger`
(#1105)
* Support to 7 axes geometry in `pa` macro (#1116)
* Protection to `showscan` when a non HDF5 file is getting opened (#1073)
* Auto-deploy to PyPI with Travis (#1113)
* Print output of `send2ctrl` macro only if it contains something (#1120)
* Add `DescriptionLength` view option for adjusting the `lsdef` macro description
(#1107, #1108)
* Add `ShowScanOnline` component to Taurus Qt extensions (#1042)
### Changed
* `Data` Tango attribute of experimental channels (CTExpChannel,
ZeroDExpChannel, OneDExpChannel, PseudoCounter) to `ValueBuffer` (SEP2, #775)
* Value buffer data structure format from `{"index": seq<int>, "data": seq<str>}`
to `{"index": seq<int>, "value": seq<str>}` (SEP2, #775)
* Default encoding of `ValueBuffer` and `ValueRefBuffer` attributes (SEP2, #775)
from JSON to pickle
* Mapping of Integer data type to Tango DevLong64 (#1083)
### Fixed
* Hanging scans by avoiding deepcopy of `DeviceProxy` (#1102)
* Restore motor parameters (vel, acc, dec) before going to start position in dNscact
macros (#1085)
* Calculation of nb_starts argument of `PrepareOne` method of timerable controllers
when software synchronization is in use (#1110)
* Interactive macros on Windows (#347)
* expconf when empty (unspecified) DataType (#1076)
* Output block of scan records which do not fit the console width (#924)
* Fix bug on exception popups in macroexecutor (#1079, #1088)
* Cyclic references between scan macros and GSF internals (#816, #1115)
* Enable expconf buttons (Reload and Apply) when local configuration was kept after
receiving external changes (#959, #1093)
* Avoid external changes pop-up when synchronizer is changed in the expconf by
removing global measurement group synchronizer (#1103)
* Show external changes pop-up in expconf when last measurement group is deleted
remotelly (#1099)
* Pop-up message when expconf configuration changed externally (#1094)
* Remove circlular references between the macro object and the FIO recorder (#1121)
### Deprecated
* Datasource Tango attribute, data_source core attributes and data_source
1D and 2D controller axis parameter (SEP2, #775).
### Removed
* `ValueBuffer` Tango attribute of 0D exp. channels deprecated in version
2.3.0. `AccumulationBuffer` attribute serves for the same need (SEP2, #775).
Exceptionally no major version bump is done cause it seems like this attribute
was not used programmatically in third party plugins/GUIs.
## [2.7.2] 2019-05-28
### Fixed
* Several issues with measurement group configuration and `epxconf` (#1090)
### Deprecated
* Measurement group configuration `timer` and `monitor` - there are no
equivalents, these roles are assigned based on the channel's order per each
of the synchronization types: trigger, gate and start (#1090)
## [2.7.1] 2019-03-29
### Fixed
* Do not read 1D and 2D experimental channels during software acquisition loop
reintroduced after fixing it in 2.6.0 (#1086).
## [2.7.0] 2019-03-11
### Added
* Possibility to directly acquire an experimental channel (without the need to define
a measurement group) (#185, #997, #1048, #1061)
* `IntegrationTime` (Tango) and `integration_time` (core) attributes to all experimental
channels
* `Timer` (Tango) and `timer` (core) attribute to all timerable experimental channels
* `default_timer` class attribute to all timerable controllers (plugins) to let them
announce the default timer axis
* Possibility to pass an experimental channel (now compatible only with timerable channels)
as a parameter of `ct` and `uct` macros in order to acquire directly on the channel (#1049)
* `Countable` element type that includes measurement group and experimental channels (#1049)
* `newfile` macro for setting `ScanDir`, `ScanFile` and `ScanID` env variables (#777)
* Warning message when hooks gets overridden with `Hookable.hooks` property (#1041)
* Acquisition macro examples (#1047)
### Fixed
* `expconf` warns only about the following environment variables changes: `ScanFile`,
`ScanDir`, `ActiveMntGrp`, `PreScanSnapshot` and `DataCompressionRank` (#1040)
* MeasurementGroup's Moveable attribute when set to "None" in Tango is used as None
in the core (#1001)
* Compatibility of measurement group plotting configurations created with
sardana < 2.4.0 and taurus < 4.3.0 (#1017, #1022)
* General Hook tests (#1062)
## [2.6.1] 2019-02-04
This is a special release for meeting the deadline of debian buster freeze (debian 10).
### Fixed
- String parameter editor in macroexecutor and sequencer (#1030, #1031)
- Documentation on differences between `Hookable.hooks` and `Hookable.appendHook`
(#962, #1013)
## [2.6.0] 2019-01-31
This is a special release for meeting the deadline of debian buster freeze (debian 10).
### Added
- New acquisition and synchronization concepts (SEP18, #773):
- Preparation of measurement group for a group of acquisitions is mandatory
(`Prepare` Tango command and `prepare` core method; `NbStarts` Tango
attribute and `nb_starts` core attribute; `count`, `count_raw` and
`count_continuous` methods in Taurus extension)
- Preparation of timerable controllers is optional (`PrepareOne` method)
- `SoftwareStart` and `HardwareStart` options in `AcqSynch` enumeration and
`Start` in `AcqSynchType` enumeration (the second one is available in
the `expconf` as synchronization option)
- `start` and `end` events in software synchronizer
- `PoolAcquisitionSoftwareStart` acquisition action
- `SoftwareStart` and `HardwareStart` synchronization in
`DummyCounterTimerController`
- Support to Qt5 for Sardana-Taurus widgets and Sardana-Taurus extensions (#1006,
#1009)
- Possibility to define macros with optional parameters. These must be the last
ones in the definition (#285, #876, #943, #941, #955)
- Possibility to pass values of repeat parameters with just one member without
the need to encapsulate them in square brackets (spock syntax) or list
(macro API) (#781, #983)
- Possibility to change data format (shape) of of pseudo counter values (#986)
- Check scan range agains motor limits wheneve possible (#46, #963)
- Workaround for API_DeviceTimedOut errors on MeasurementGroup Start. Call Stop
in case this error occured (#764).
- Optional measurement group parameter to `ct` and `uct` macros (#940, #473)
- Support to "PETRA3 P23 6C" and "PETRA3 P23 4C" diffractometers by means
of new controller classes and necessary adaptation to macros (#923, #921)
- Top LICENSE file that applies to the whole project (#938)
- Document remote connection to MacroServer Python process (RConsolePort Tango
property) (#984)
- sardana.taurus.qt.qtgui.macrolistener (moved from taurus.qt.qtgui.taurusgui)
- Documentation on differences between `Hookable.hooks` and `Hookable.appendHook`
(#962, #1013)
### Fixed
- Do not read 1D and 2D experimental channels during software acquisition loop
(#967)
- Make `expconf` react on events of environment, measurement groups and their
configurations. An event offers an option to reload the whole experiment
configuration or keep the local changes. `expconf` started with
`--auto-update` option will automatically reload the whole experiment
configuration (#806, #882, #988, #1028, #1033)
- Reload macro library overriding another library (#927, #946)
- Avoid final padding in timescan when it was stopped by user (#869, #935)
- Moveables limits check in continuous scans when moveables position attribute
has unit configured and Taurus 4 is used (quantities) (#989, #990)
- Hook places advertised by continuous scans so the `allowHooks` hint and the
code are coherent (#936)
- Macro/controller module description when module does not have a docstring
(#945)
- Make `wu` macro respect view options (#1000, #1002)
- Make cleanup (remove configuration) if spock profile creation was interrupted
or failed (#791, #793)
- Spock considers passing supernumerary parameters as errors (#438, #781)
- MacroServer starts without the Qt library installed (#781, #907, #908)
- Make `Description` an optional part of controller's properties definition (#976)
- Correcting bug in hkl macros introduced when extending macros for new
diffractometer types: angle order was switched
### Changed
- MacroButton stops macros instead of aborting them (#931, #943)
- Spock syntax and advanced spock syntax are considered as one in documentaion
(#781)
- Move pre-scan and post-scan hooks out of `scan_loop` method (#920, #922,
#933)
- Logstash handler from python-logstash to python-logstash-async (#895)
- Move `ParamParser` to `sardana.util.parser` (#781, #907, #908)
- SpockCommandWidget.returnPressed method renamed to onReturnPressed
- SpockCommandWidget.textChanged method renamed to onTextChanged
### Deprecated
- Measurement group start without prior preparation (SEP18, #773)
- Loadable controller's API: `LoadOne(axis, value, repeats)`
in favor of `LoadOne(axis, value, repeats, latency)` (SEP18, #773)
- Unused class `sardana.taurus.qt.qtgui.extra_macroexecutor.dooroutput.DoorAttrListener`
### Removed
- Support to Qt < 4.7.4 (#1006, #1009)
## [2.5.0] 2018-08-10
### Added
......@@ -312,11 +79,6 @@ This is a special release for meeting the deadline of debian buster freeze (debi
- `Controller.getUsedAxis` (Taurus device extension) in favor
of `Controller.getUsedAxes` (#609)
### Removed
- Signal `modelChanged()` from ParamBase class to use the call to
method onModelChanged directly instead
## [2.4.0] 2018-03-14
### Added
......@@ -709,13 +471,7 @@ Main improvements since sardana 1.5.0 (aka Jan15):
[keepachangelog.com]: http://keepachangelog.com
[Unreleased]: https://github.com/sardana-org/sardana/compare/2.8.0...HEAD
[2.8.0]: https://github.com/sardana-org/sardana/compare/2.8.0...2.7.2
[2.7.2]: https://github.com/sardana-org/sardana/compare/2.7.1...2.7.2
[2.7.1]: https://github.com/sardana-org/sardana/compare/2.7.0...2.7.1
[2.7.0]: https://github.com/sardana-org/sardana/compare/2.6.1...2.7.0
[2.6.1]: https://github.com/sardana-org/sardana/compare/2.6.0...2.6.1
[2.6.0]: https://github.com/sardana-org/sardana/compare/2.5.0...2.6.0
[Unreleased]: https://github.com/sardana-org/sardana/compare/2.5.0...HEAD
[2.5.0]: https://github.com/sardana-org/sardana/compare/2.4.0...2.5.0
[2.4.0]: https://github.com/sardana-org/sardana/compare/2.3.2...2.4.0
[2.3.2]: https://github.com/sardana-org/sardana/compare/2.3.1...2.3.2
......
Metadata-Version: 1.1
Metadata-Version: 1.2
Name: sardana
Version: 2.8.1.2
Version: 2.5.1.9
Summary: instrument control and data acquisition system
Home-page: http://www.sardana-controls.org
Author: Sardana Community
Author-email: sardana-devel@lists.sourceforge.net
Author: Tiago Coutinho et al.
Maintainer: Sardana Community
Maintainer-email: sardana-devel@lists.sourceforge.net
License: LGPL
Download-URL: http://pypi.python.org/packages/source/s/sardana
Description: Sardana is a Supervision, Control And Data Acquisition (SCADA) system for
......@@ -33,7 +34,7 @@ Classifier: Topic :: Scientific/Engineering
Classifier: Topic :: Software Development :: Libraries
Requires: PyTango (>=7.2.3)
Requires: itango (>=0.0.1)
Requires: taurus (>= 3.12)
Requires: taurus (>= 3.7.5)
Requires: lxml (>=2.1)
Requires: ordereddict
Provides: sardana
# How to release (draft)
This is a guide for sardana release managers: it details the steps for making
an official release, including a checklist of stuff that should be manually
tested.
## The release process
1. During all the development, use the Milestones to keep track of the intended
release for each issue.
2. Previous to the release deadline, re-check the open issues/PR and update
the assignation issues/PR to the release milestone. Request feedback from
the devel community.
3. Work to close all the PR/issues remaining open in the milestone. This can
be either done in develop or in a release branch called `release-XXX`
(where `XXX` is the milestone name, e.g. `Jul17`). If a release branch is
used, `develop` is freed to continue with integrations that may not be
suitable for this release. On the other hand, it adds a bit more work
because the release-related PRs (which are done against the `release-XXX`
branch), may need to be also merged to develop.
Note: the `release-XXX` branch *can* live in the sardana-org repo or on a
personal fork (in which case you should do step 4.v **now** to allow other
integrators to push directly to it).
4. Create the release branch if it was not done already in the previous step
and:
1. Review and update the CHANGELOG.md if necessary. See [this](http://keepachangelog.com).
2. Bump version using `bumpversion <major|minor|patch> && bumpversion release`
(use [semver](http://semver.org/) criteria to choose amongst `major`,
`minor` or `patch`. OPTIONAL: Sardana depends on Taurus, and the
required version of Taurus may need to be bumped as well. Taurus and
other dependencies are specified in: `setup.py` (requires list of
strings) and `src/sardana/requirements.py` (`__requires__` dictionary
and taurus.core value).
3. The version numbers used in the man pages of the Sardana scripts are
bumped (you may use `taurus/doc/makeman` script executing it from the
doc directory e.g. `sardana/doc`) and committing the changes.
4. In the code use version number instead of milestone in deprecation
warnings (if any) e.g. replace *Jul18* with *2.5.0*.
5. Create a PR to merge the `release-XXX` against the **`master`** branch
of the sardana-org repo
5. Request reviews in the PR from at least one integrator from each
participating institute. The master branch is protected, so the reviews need
to be cleared (or dismissed with an explanation) before the release can be
merged.
6. Perform manual tests (see checklist below). You may use the CI artifacts
(e.g., from appveyor) and post the results in the comments of the PR.
7. Once all reviews are cleared, update the date of the release in the
CHANGELOG.md, merge the PR and tag in master.
8. Merge also the `release-XXX` branch into develop, and bump the version of
develop with `bumpversion patch`
9. Release to PyPI **from a clean checkout** and using [twine](https://github.com/pypa/twine):
```
cd /tmp
git clone https://github.com/sardana-org/sardana.git -b <RELEASE_TAG>
cd sardana
python setup.py sdist bdist_wheel
twine upload dist/*
```
10. Complete GitHub release (upload artifacts, edit text)
11. Create news in www.tango-controls.org
1. On the News page click on Submit a news and fill up the form (if it doesn't work, try opening in new tab):
* Title: New Release Of Sardana X.X.X (Jan|JulXX)
* Ilustration: sardana or official logo (use png)
* Summary: short summary of the news (do not include the whole changelog here..)
* Categories: Release
2. After submitting click on Modify this content text of the area \<\<Content\>\> and provide detailes of the release e.g. changelog.
12. Notify mailing lists (sardana-users@lists.sourceforge.net, sardana-devel@lists.sourceforge.net, info@tango-controls.org)
## Manual test checklist
This is a check-list of manual tests. It is just orientative. Expand it
at will. This list assumes a clean environment with all Sardana dependencies
already installed and access to a Tango system with the TangoTest DS running.
Hint: this list can be used as a template to be copy-pasted on a release manual test issues
### Installation
- [ ] Install Sardana (on Linux from the tar.gz : `pip install <tarball_artifact_URL>`
and on Windows from MSI)
**Note:** On openSuse 11.1 there are problems with pip, try `python setup
.py install`
### Create testing environment and run testsuite
- [ ] Start Pool demo2. In a console do `Pool demo2`.
- [ ] Start MacroServer demo2 and connect to the Pool demo2.
In another console do: `MacroServer demo2`
- [ ] Set MacroServer's MacroPath to point to the macro examples.
In another IPython console do:
`PyTango.DeviceProxy('macroserver/demo2/1').put_property({'MacroPath':'<path_to_sardana_installation_dir>/macroserver/macros/examples'})`
**Note:** Remember to use OS path separator e.g. '/' on Linux and '\' on
Windows
- [ ] Restart MacroServer e.g. Ctrl+C in the MacroServer's console and
start it again.
- [ ] Create spock profile demo2. In another console do `spock --profile=demo2`
- [ ] In spock run `sar_demo` macro.
- [ ] Edit `<path_to_sardana_installation_dir>/sardanacustomsettings.py`
to point to the demo2 door e.g. `UNITTEST_DOOR_NAME = "door/demo2/1"`
- [ ] Run testsuite. In another console do `sardanatestsuite`
**Note:** On openSuse 11.1 and Windows there are known problems with
testsuite. Check previous release comments.
### Test Sardana using Spock and expconf
- [ ] Test interactive macros from spock e.g. `ask_for_moveable`, `ask_peak`
**Note**: On Windows there are known bugs.
- [ ] Execute `umvr` macro and verify that the position updates arrives.
- [ ] In expconf configure scan files by setting ScanDir to: `/tmp/` on Linux
`C:\Users\<username>\tmp` on Windows and ScanFile to: `demo1.h5, demo1.dat`.
- [ ] Configure online plot to show counters: On expconf GUI select for all
the counter channels, Plot Type 'Spectrum' and Plot Axes '\<mov\>'
- [ ] Configure snapshot group: with a motor and the `sys/tg_test/1/ampli`
attribute.
- [ ] Add the `sys/tg_test/1/double_scalar` attribute to the measurement
group.
- [ ] Open online plot.
- [ ] Set JsonRecorder to true. In spock do `senv JsonRecorder True`
- [ ] Run step scan
- [ ] Verify that records appear in spock output.
- [ ] Verify that records were stored in scan files.
- [ ] Verify that records were plotted on the online plot
- [ ] Run `showscan` and access to the last scan data.
- [ ] With `edmac` modify existing macro: `ask_peak` and run it to verify that the change
was applied.
- [ ] With `edmac` create a new macro in a new macro library:
`edmac my_macro <path_to_sardana_installation_dir>/macroserver/macros/examples/my_macros.py`
and run it.
**Note:** Remember to use OS path separator e.g. '/' on Linux and '\' on
Windows
### Test Sardana with TaurusGUI
- [ ] Create the GUI using this [guide](https://sourceforge.net/p/sardana/wiki/Howto-GUI_creation)
#### PMTV (PoolMotorTaurusValue)
- [ ] Move motors from the slit panel in absolute and relative modes.
- [ ] Show expert view.
- [ ] Show compact mode.
#### macroexecutor
- [ ] Execute `ascan` macro
- [ ] Pause it in the middel and resume
- [ ] Abort it
- [ ] Add it to favorites
- [ ] Run `lsm` macro
- [ ] Execute `ascan` from favorites
- [ ] Run `lsmac` macro
- [ ] Execute `ascan` from history
- [ ] Edit `dscan` macro in spock yellow line and run it
- [ ] Restart macroexecutor application
- [ ] Run `lsm` from history
- [ ] Run `ascan` from favorites
#### sequencer
- [ ] Add `ascan` macro to the sequence
- [ ] Add `lsct` macro as a `post-acq` hook of `ascan`
- [ ] Add `dscan` macro to the sequence
- [ ] Run the sequence
- [ ] Save sequence to a file
- [ ] Start new sequence
- [ ] Load sequence from a files
- [ ] Run the loaded sequence
#### sardanaeditor
**Note:** There are known bugs on CentOS and Windows
- [ ] Open sardanaeditor with macroserver name as argument.
- [ ] Browse macro libraries and open an existing macro.
- [ ] Edit existing macro and save & apply chaneges.
- [ ] Execute macro to see if changes were aplied.
- [ ] Create a new macro using template.
- [ ] Execute the newly created macro.
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.47.4.
.TH MACROSERVER "1" "June 2019" "MacroServer 2.8.0" "User Commands"
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.47.3.
.TH MACROSERVER "1" "August 2018" "MacroServer 2.5.0" "User Commands"
.SH NAME
MacroServer \- manual page for MacroServer 2.8.0
MacroServer \- manual page for MacroServer 2.5.0
.SH SYNOPSIS
.B usage:
\fI\,MacroServer instance_name \/\fR[\fI\,options\/\fR]
......
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.47.4.
.TH POOL "1" "June 2019" "Pool 2.8.0" "User Commands"
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.47.3.
.TH POOL "1" "August 2018" "Pool 2.5.0" "User Commands"
.SH NAME
Pool \- manual page for Pool 2.8.0
Pool \- manual page for Pool 2.5.0
.SH SYNOPSIS
.B usage:
\fI\,Pool instance_name \/\fR[\fI\,options\/\fR]
......
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.47.4.
.TH SARDANA "1" "June 2019" "Sardana 2.8.0" "User Commands"
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.47.3.
.TH SARDANA "1" "August 2018" "Sardana 2.5.0" "User Commands"
.SH NAME
Sardana \- manual page for Sardana 2.8.0
Sardana \- manual page for Sardana 2.5.0
.SH SYNOPSIS
.B usage:
\fI\,Sardana instance_name \/\fR[\fI\,options\/\fR]
......
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.47.4.
.TH DIFFRACTOMETERALIGNMENT "1" "May 2019" "diffractometeralignment 2.8.0" "User Commands"
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.47.3.
.TH DIFFRACTOMETERALIGNMENT "1" "August 2018" "diffractometeralignment 2.5.0" "User Commands"
.SH NAME
diffractometeralignment \- manual page for diffractometeralignment 2.8.0
diffractometeralignment \- manual page for diffractometeralignment 2.5.0
.SH SYNOPSIS
.B diffractometeralignment
\fI\,<model> \/\fR[\fI\,door_name\/\fR]
......
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.47.4.
.TH HKLSCAN "1" "May 2019" "hklscan 2.8.0" "User Commands"
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.47.3.
.TH HKLSCAN "1" "August 2018" "hklscan 2.5.0" "User Commands"
.SH NAME
hklscan \- manual page for hklscan 2.8.0
hklscan \- manual page for hklscan 2.5.0
.SH SYNOPSIS
.B hklscan
\fI\,<model> \/\fR[\fI\,door_name\/\fR]
......
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.47.4.
.TH MACROEXECUTOR "1" "May 2019" "macroexecutor 2.8.0" "User Commands"
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.47.3.
.TH MACROEXECUTOR "1" "August 2018" "macroexecutor 2.5.0" "User Commands"
.SH NAME
macroexecutor \- manual page for macroexecutor 2.8.0
macroexecutor \- manual page for macroexecutor 2.5.0
.SH SYNOPSIS
.B macroexecutor
[\fI\,options\/\fR]
......
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.47.4.
.TH SARDANATESTSUITE "1" "June 2019" "sardanatestsuite 2.8.0" "User Commands"
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.47.3.
.TH SARDANATESTSUITE "1" "August 2018" "sardanatestsuite 2.5.0" "User Commands"
.SH NAME
sardanatestsuite \- manual page for sardanatestsuite 2.8.0
sardanatestsuite \- manual page for sardanatestsuite 2.5.0
.SH DESCRIPTION
usage: sardanatestsuite [\-h] [\-e EXCLUDE_PATTERN] [\-\-version]
.PP
......
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.47.4.
.TH SEQUENCER "1" "May 2019" "sequencer 2.8.0" "User Commands"
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.47.3.
.TH SEQUENCER "1" "August 2018" "sequencer 2.5.0" "User Commands"
.SH NAME
sequencer \- manual page for sequencer 2.8.0
sequencer \- manual page for sequencer 2.5.0
.SH SYNOPSIS
.B sequencer
[\fI\,options\/\fR]
......
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.47.4.
.TH SPOCK "1" "May 2019" "spock 2.8.0" "User Commands"
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.47.3.
.TH SPOCK "1" "August 2018" "spock 2.5.0" "User Commands"
.SH NAME
spock \- manual page for spock 2.8.0
spock \- manual page for spock 2.5.0
.SH DESCRIPTION
=========
.IP
......@@ -248,14 +248,14 @@ The IPython profile to use.
\fB\-\-pylab=\fR<CaselessStrEnum> (InteractiveShellApp.pylab)
.IP
Default: None
Choices: [u'auto', u'gtk', u'gtk3', u'inline', u'nbagg', u'notebook', u'osx', u'qt', u'qt4', u'qt5', u'tk', u'wx']
Choices: [u'auto', u'agg', u'gtk', u'gtk3', u'inline', u'ipympl', u'nbagg', u'notebook', u'osx', u'pdf', u'ps', u'qt', u'qt4', u'qt5', u'svg', u'tk', u'widget', u'wx']
Pre\-load matplotlib and numpy for interactive use, selecting a particular
matplotlib backend and loop integration.
.PP
\fB\-\-matplotlib=\fR<CaselessStrEnum> (InteractiveShellApp.matplotlib)
.IP
Default: None
Choices: [u'auto', u'gtk', u'gtk3', u'inline', u'nbagg', u'notebook', u'osx', u'qt', u'qt4', u'qt5', u'tk', u'wx']
Choices: [u'auto', u'agg', u'gtk', u'gtk3', u'inline', u'ipympl', u'nbagg', u'notebook', u'osx', u'pdf', u'ps', u'qt', u'qt4', u'qt5', u'svg', u'tk', u'widget', u'wx']
Configure matplotlib for interactive use with the default matplotlib
backend.
.PP
......
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.47.4.
.TH UBMATRIX "1" "May 2019" "ubmatrix 2.8.0" "User Commands"
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.47.3.
.TH UBMATRIX "1" "August 2018" "ubmatrix 2.5.0" "User Commands"
.SH NAME
ubmatrix \- manual page for ubmatrix 2.8.0
ubmatrix \- manual page for ubmatrix 2.5.0
.SH SYNOPSIS
.B ubmatrix
\fI\,<model>\/\fR
......
File mode changed from 100644 to 100755
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment