Markus Zolliker 0eb68e54be validator should take resolution into account ...

also changed names: according to the meeting in 2019-01-16 we
decided to use absolute_resolution/relative_resolution
instead of _precision

Change-Id: I4a49bb745901b87c2aa2bc2728fd7a44026421e0
Reviewed-on: https://forge.frm2.tum.de/review/20321
Tested-by: JenkinsCodeReview <bjoern_pedersen@frm2.tum.de>
Reviewed-by: Enrico Faulhaber <enrico.faulhaber@frm2.tum.de>

2019-04-03 17:41:07 +02:00

bin

fix isort

2018-12-04 10:18:55 +01:00

ci

Fix typo

2019-03-26 09:34:32 +01:00

debian

[deb] Release v0.7.0

2019-03-28 13:46:08 +01:00

doc

rename framework methods to camelCase

2019-04-02 08:15:40 +02:00

etc

additional parameter properties

2018-12-18 16:53:49 +01:00

secop

validator should take resolution into account

2019-04-03 17:41:07 +02:00

secop_demo

rename framework methods to camelCase

2019-04-02 08:15:40 +02:00

secop_ess

remove support for declaring parameters/commands as accessibles

2019-03-29 08:46:14 +01:00

secop_mlz

rename framework methods to camelCase

2019-04-02 08:15:40 +02:00

test

validator should take resolution into account

2019-04-03 17:41:07 +02:00

.description

First checkin, base point for development

2016-06-13 15:49:23 +02:00

.gitattributes

First checkin, base point for development

2016-06-13 15:49:23 +02:00

.gitignore

revision of SECoP documentation

2017-11-03 08:46:20 +01:00

.pylintrc

pylintrc: increase allowed module length

2018-07-19 15:42:22 +02:00

Makefile

include isort target in Makefile

2019-03-26 10:42:53 +01:00

requirements-dev.txt

Makefile: add convenience targets.

2017-09-13 18:45:35 +02:00

requirements.txt

Fix requirements files.

2017-09-13 15:31:59 +02:00

setup.py

fix isort

2018-12-04 10:18:55 +01:00

Description

PSI local frappy repo, probably ahead of git/gerrit at MLZ

5.2 MiB

Languages

Python 99.9%