Skip to content

Commit

Permalink
Correct IOR and CT controller docstrings
Browse files Browse the repository at this point in the history
  • Loading branch information
ovallcorba committed Jan 9, 2024
1 parent 6772348 commit b43355d
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 6 deletions.
6 changes: 3 additions & 3 deletions sardana_tango/ctrl/TangoAttrCTCtrl.py
Original file line number Diff line number Diff line change
Expand Up @@ -141,11 +141,11 @@ class TangoAttrCTController(ReadTangoAttributes, CounterTimerController):
+) TangoAttribute - Tango attribute to retrieve the value of the counter
+) Formula - Formula to evaluate using 'VALUE' as the tango attribute value
As examples you could have:
ch1.TangoExtraAttribute = 'my/tango/device/attribute1'
ch1.TangoAttribute = 'my/tango/device/attribute1'
ch1.Formula = '-1 * VALUE'
ch2.TangoExtraAttribute = 'my/tango/device/attribute2'
ch2.TangoAttribute = 'my/tango/device/attribute2'
ch2.Formula = 'math.sqrt(VALUE)'
ch3.TangoExtraAttribute = 'my_other/tango/device/attribute1'
ch3.TangoAttribute = 'my_other/tango/device/attribute1'
ch3.Formula = 'math.cos(VALUE)'
"""

Expand Down
6 changes: 3 additions & 3 deletions sardana_tango/ctrl/TangoAttrIORCtrl.py
Original file line number Diff line number Diff line change
Expand Up @@ -76,9 +76,9 @@ class TangoAttrIORController(IORegisterController):
Each IORegisters _MUST_HAVE_ extra attributes:
+) TangoAttribute - Tango attribute to retrieve the value of the IORegister
As examples you could have:
ch1.TangoExtraAttribute = 'my/tango/device/attribute1'
ch2.TangoExtraAttribute = 'my/tango/device/attribute2'
ch3.TangoExtraAttribute = 'my_other/tango/device/attribute1'
ch1.TangoAttribute = 'my/tango/device/attribute1'
ch2.TangoAttribute = 'my/tango/device/attribute2'
ch3.TangoAttribute = 'my_other/tango/device/attribute1'
Each IORegisters _MAY_HAVE_ extra attributes:
+) Labels - Human readable tag followed to the corresponding position
(integer) value.
Expand Down

0 comments on commit b43355d

Please sign in to comment.