tauruslib-users — taurus users mailing list

[Tauruslib-users] New release of Taurus 4.1.1 (Jul17)

[Carlos P. <cpa...@ce...>]

Hi all,

The new Taurus 4.1.1 has been released.

The source files, windows installers and an unofficial debian9 package can be 
downloaded from:

    https://github.com/taurus-org/taurus/releases/tag/4.1.1

The documentation is available at (notice the new installation instructions):

    http://www.taurus-scada.org

For a detailed list of changes, see the CHANGELOG:

    https://github.com/taurus-org/taurus/blob/master/CHANGELOG.md

...and the issue tracker:

    https://github.com/taurus-org/taurus/milestone/9?closed=1

You can also get the full log of commits, from your local git repo with:

    % git log 4.0.3..4.1.1

If you encounter problems installing or running this release, please
open an issue in :

    https://github.com/taurus-org/taurus/issues

Cheers!

Carlos (on behalf of the taurus developers)


PS: we also did a bug-fix release on the old 3.x series (no files uploaded to 
PyPI, use the git repo if you are interested in this one):

https://github.com/taurus-org/taurus/tree/3.7.4

-- 
+----------------------------------------------------+
 Carlos Pascual Izarra
 Scientific Software Coordinator
 Computing Division
 ALBA Synchrotron  [http://www.albasynchrotron.es]
 Carrer de la Llum 2-26
 E-08290 Cerdanyola del Valles (Barcelona), Spain
 E-mail: cpa...@ce...
 Phone: +34 93 592 4428
+----------------------------------------------------+

Re: [Tauruslib-users] taurusform "expert" attributes hide/display

[Carlos P. <cpa...@ce...>]

Hi, 

Yes, but you need to use another widget called TaurusAttrForm :

http://www.taurus-scada.org/en/latest/devel/api/taurus/qt/qtgui/panel/
_TaurusAttrForm.html

Check the following  (embarrassingly undocumented) methods:
TaurusAttrForm.setExpertView(bool)
TaurusAttrForm.setViewFilters(filterlist)
TaurusAttrForm.getViewFilters()

Note that while TaurusForm gets a list of attributes as its model (and then 
you would need to filter manually), TaurusAttrForm gets a device as its model.

I hope this helped,

Carlos

PS: since a few months ago, the preferred channel for questions about Taurus 
is via github issues ( https://github.com/taurus-org/taurus/issues )
This mailing list will be used mostly for announcements.


On Wednesday, June 14, 2017 11:43:51 AM CEST Alessandro Marassi wrote:
> Is there a way to hide or display the "expert" attributes from a device
> using taurusform?
> 
> thanks,
> alex
> 
> ----------------------------------------------------------------------------
> -- Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Tauruslib-users mailing list
> Tau...@li...
> https://lists.sourceforge.net/lists/listinfo/tauruslib-users


-- 
+----------------------------------------------------+
 Carlos Pascual Izarra
 Scientific Software Coordinator
 Computing Division
 ALBA Synchrotron  [http://www.albasynchrotron.es]
 Carrer de la Llum 2-26
 E-08290 Cerdanyola del Valles (Barcelona), Spain
 E-mail: cpa...@ce...
 Phone: +34 93 592 4428
+----------------------------------------------------+

[Tauruslib-users] taurusform "expert" attributes hide/display

[Alessandro M. <ma...@oa...>]

Is there a way to hide or display the "expert" attributes from a device using taurusform?

thanks,
alex

Re: [Tauruslib-users] [TaurusDesiner]

[Carlos P. <cpa...@ce...>]

Hi,

The taurusdesigner is just the standard designer with an extended catalog of 
(taurus) widgets.

Some taurus widgets (but not all) will have a `model` property that you can 
set directly in the designer (e.g. you can add a TaurusLabel to your widget in 
taurusdesigner and then look for its "model" property in the property editor 
and set it to "/sys/tg_test/1/ampli"). Then, when you run your widget (not 
within designer) the label will be updated with the changes in the given 
attribute.

... but I personally tend to set the models programmatically, when I do the 
rest of the logic, using the `.setModel()` setter that all Taurus widgets 
have.

Note that there is no list of available tango attributes in the designer (your 
development machine may not even have access to the same Tango host as your 
production machine, so the utility of this would be rather limited).

Instead, many widgets (forms, plots, etc) may allow you to change their models 
(e.g. the tango attributes they are connected to) at run time, by using the 
ModelChooser widget and/or drag&drop.

Finally: if you are starting with Taurus Programming, consider using the 
TaurusGUI framework and only using taurusdesigner to create specific widgets 
that you then use from a TaurusGUI.

Carlos

On Tuesday, April 11, 2017 2:59:12 PM CEST gu...@la... wrote:
> Dear taurus-members,
> 
> I have some difficulties to understand how one should use the taurusdesiner.
> Comparing to the « normal » Qt designer there are many new taurus widgets
> apps. My question is that I do not know how to attach a button, a plot etc
> to a tango variable … for example to /sys/tg_test/1 … If I use Jdraw for
> example, the list of tango variables appear on the left side of the panel.
> 
> 
> Many thanks for your help,
> 
> Cheers,
> Hayg


-- 
+----------------------------------------------------+
 Carlos Pascual Izarra
 Scientific Software Coordinator
 Computing Division
 ALBA Synchrotron  [http://www.albasynchrotron.es]
 Carrer de la Llum 2-26
 E-08290 Cerdanyola del Valles (Barcelona), Spain
 E-mail: cpa...@ce...
 Phone: +34 93 592 4428
+----------------------------------------------------+

[Tauruslib-users] [TaurusDesiner]

[<gu...@la...>]

Dear taurus-members,

I have some difficulties to understand how one should use the taurusdesiner. Comparing to the « normal » Qt designer there are many new taurus widgets apps.
My question is that I do not know how to attach a button, a plot etc to a tango variable … for example to /sys/tg_test/1 …
If I use Jdraw for example, the list of tango variables appear on the left side of the panel.


Many thanks for your help,

Cheers,
Hayg

[Tauruslib-users] New release of Taurus 4.0.3 (Jan17)

[Carlos P. <cpa...@ce...>]

Hi all,

The new Taurus 4.0.3 has been released.

The source files and windows installers can be downloaded from PyPI:

    http://pypi.python.org/pypi/taurus

The documentation is available at:

    http://www.taurus-scada.org

For a detailed list of changes, see the CHANGELOG:

    https://github.com/taurus-org/taurus/blob/master/CHANGELOG.md

And the issue tracker:

    https://github.com/taurus-org/taurus/milestone/1?closed=1

You can also get the full log of commits, from your local git repo with:

    % git log 4.0.1..4.0.3

If you encounter problems installing or running this release, please
open an issue in :

    https://github.com/taurus-org/taurus/issues

Or contact the mailing list:

    tau...@li...


Cheers!

Carlos (on behalf of the taurus developers)
-- 
+----------------------------------------------------+
 Carlos Pascual Izarra
 Scientific Software Coordinator
 Computing Division
 ALBA Synchrotron  [http://www.albasynchrotron.es]
 Carrer de la Llum 2-26
 E-08290 Cerdanyola del Valles (Barcelona), Spain
 E-mail: cpa...@ce...
 Phone: +34 93 592 4428
+----------------------------------------------------+

[Tauruslib-users] Taurus moved to GitHub

[Carlos P. <cpa...@ce...>]

We are happy to announce that the Taurus project has just finished its 
transition to GitHub.

Main changes:

- The old SourceForge Project page [1] is now considered obsolete. 

- The  official source code repository is now: 
    https://github.com/taurus-org/taurus

- The bugs and feature requests should now be reported as GitHub Issues [2]

- The code contribution rules changed. They are described in the
    CONTRIBUTING.md file [3]

For more details about the migration, see the TEP16 [4]

References:

[1] http://tauruslib.sourceforge.net/
[2] https://github.com/taurus-org/taurus/issues
[3] https://github.com/taurus-org/taurus/blob/develop/CONTRIBUTING.md
[4] http://www.taurus-scada.org/tep/?TEP16.md

[Tauruslib-users] TEP16 - Voting for CANDIDATE --> Accepted

[Carlos P. <cpa...@ce...>]

Hi all,

Finally the CANDIDATE implementation of the TEP16 (migration of Taurus to 
GitHub) is ready to be reviewed.

Please review the proposed changes in:

https://github.com/taurus-org/taurus/pull/1

... and discuss in that same Pull Request if you have any comment

Also, a representative from each institute should cast a vote regarding 
whether we should accept the TEP16 (please do it ASAP by commenting on the 
Pull Request itself).

Note that ACCEPTING TEP16, automatically moves TEP0 and TEP7 to OBSOLETE 
state.

Cheers,

PD: please note that the "service-agnostic URL for the TEPs" mentioned in the 
TEP16 will only work once we actually merge the Pull Request (i.e., do not 
worry about broken links until then)

Carlos

PD: in the eventuality that we do not accept the TEP16 , I would undo all the 
changes I did on SourceForge... but I hope that it is not necessary! ;)

-- 
+----------------------------------------------------+
 Carlos Pascual Izarra
 Scientific Software Coordinator
 Computing Division
 ALBA Synchrotron  [http://www.albasynchrotron.es]
 Carrer de la Llum 2-26
 E-08290 Cerdanyola del Valles (Barcelona), Spain
 E-mail: cpa...@ce...
 Phone: +34 93 592 4428
+----------------------------------------------------+

Re: [Tauruslib-users] Taurus ticket tracker moved to github

[Jan K. <jan...@de...>]

Hi Carlos,

Great. Thanks for moving Taurus and its forks into GitHub.

Cheers,
Jan 

On 11/15/16 15:06, Carlos Pascual wrote:
> Hi all,
> 
> As part of the preparations for migrating the Taurus project to GitHub [1], 
> the ticket tracker (bug reports and feature requests) has been migrated to:
> 
>  https://github.com/taurus-org/taurus/issues
> 
> Please use this new tracker for new tickets and for updates on existing 
> tickets (all tickets from SourceForge have been copied to GitHub). The old 
> tracker in SourceForge will be kept read-only for historical reference only, 
> and will not be updated.
> 
> Note that the GitHub issue numbers do *not* correspond to the old SourceForge 
> ticket numbers and that we, unfortunately, did not add a back-link to the 
> original ticket when creating the issues in GitHub. Therefore, the only way 
> (for now) to link the migrated tickets to their original source is by 
> searching on the title.
> 
> I hope you  enjoy the new system. If you have any comment on this migration, 
> please join the discussion at [1].
> 
> Carlos
> 
> References:
> [1] https://github.com/taurus-org/taurus/pull/1
> 
> 

[Tauruslib-users] Taurus ticket tracker moved to github

[Carlos P. <cpa...@ce...>]

Hi all,

As part of the preparations for migrating the Taurus project to GitHub [1], 
the ticket tracker (bug reports and feature requests) has been migrated to:

 https://github.com/taurus-org/taurus/issues

Please use this new tracker for new tickets and for updates on existing 
tickets (all tickets from SourceForge have been copied to GitHub). The old 
tracker in SourceForge will be kept read-only for historical reference only, 
and will not be updated.

Note that the GitHub issue numbers do *not* correspond to the old SourceForge 
ticket numbers and that we, unfortunately, did not add a back-link to the 
original ticket when creating the issues in GitHub. Therefore, the only way 
(for now) to link the migrated tickets to their original source is by 
searching on the title.

I hope you  enjoy the new system. If you have any comment on this migration, 
please join the discussion at [1].

Carlos

References:
[1] https://github.com/taurus-org/taurus/pull/1


-- 
+----------------------------------------------------+
 Carlos Pascual Izarra
 Scientific Software Coordinator
 Computing Division
 ALBA Synchrotron  [http://www.albasynchrotron.es]
 Carrer de la Llum 2-26
 E-08290 Cerdanyola del Valles (Barcelona), Spain
 E-mail: cpa...@ce...
 Phone: +34 93 592 4428
+----------------------------------------------------+

Re: [Tauruslib-users] [Sardana-users] Taurus 4.0.1, newest iPython and sar_demo command

[Jagoda S. <j....@pr...>]

Hi Zibi,

Thanx for the answer, we will install newest Sardana. Cool that there is 
a new release :)

 >>> Also don't be surprised about deprecation warnings when using this 
version of Sardana. They are there since we support the Taurus 3 version 
at the same time.

Don't worry, it won't bother us until those are just warnings, not errors ;)

 >>> PS. I see that you use spock on Windows. Don't you suffer bug-502 [2]?

Yea, it seems that it shows up in console. This ticket looks like a 
fresh one.

Greetings
Jagoda Sokół
Junior Software Developer
PREVAC sp. z o.o.

Phone: +48 32 459 20 00
Fax: +48 32 459 20 01
www.prevac.eu <http://www.prevac.eu>

Address: PL-44362 Rogow, ul. Raciborska 61, CEO: Dr.-Ing. Andreas Glenz, 
VAT ID: PL 6471782175, Regon: 273374884,
Companies Commercial Register No.: KRS 0000130401, Register Court: 
Gliwice, Basic capital: 619.800,00 PLN

THE INFORMATION TRANSMITTED IS INTENDED ONLY FOR THE PERSON OR ENTITY TO 
WHICH IT IS ADDRESSED AND MAY CONTAIN CONFIDENTIAL OR PRIVILEGED 
MATERIAL. ANY REVIEW, RETRANSMISSION, DISSEMINATION OR OTHER USE OF, OR 
TAKING OF ANY ACTION IN RELIANCE UPON, THIS INFORMATION BY PERSONS OR 
ENTITIES OTHER THAN THE INTENDED RECIPIENT IS PROHIBITED. IF YOU 
RECEIVED THIS IN ERROR, PLEASE NOTIFY THE SENDER AND DELETE THE MATERIAL 
FROM YOUR COMPUTER.

W dniu 2016-09-13 o 17:40, Zbigniew Reszela pisze:
> Hi Jagoda,
>
> Please try Sardana 2.1.0 that we have released today. The previous 
> versions were not supporting Taurus 4 yet.
> Just remember that from this version on, Sardana depends on itango >= 
> 0.1.4 [1].
> Also don't be surprised about deprecation warnings when using this 
> version of Sardana. They are there since we support the Taurus 3 
> version at the same time.
>
> I'm not aware about any issues with IPython 5.1. If you find any, 
> please fill in a bug in SF.
>
> Cheers,
> Zibi
>
> PS. I see that you use spock on Windows. Don't you suffer bug-502 [2]?
>
> [1] https://pypi.python.org/pypi/itango/0.1.4
> [2] https://sourceforge.net/p/sardana/tickets/502/
>
> On 09/13/2016 02:55 PM, Jagoda Sokół wrote:
>>
>> Hello Sardana & Taurus users ! :)
>>
>> We installed Taurus 4.0.1, iPython5.1.0, Sardana2.0.2 and following 
>> error showed up while trying to run sar_demo, but no error was shown 
>> when I downgraded iPython to 3.0 and Taurus to 3.6.
>>
>> Is there a possibility to run sar_demo with previously installed 
>> version of Taurus 4.0.1 and newest iPython? If some more information 
>> needed, please write back to me :)
>>
>> Console output:
>>
>> ~~~
>> C:\Users\m.sienczak>spock
>> MainThread     INFO     2016-09-13 14:21:06,411 TaurusRootLogger: 
>> Using "PyQt4" for Qt
>> C:\Python27\lib\site-packages\IPython\utils\traitlets.py:5: 
>> UserWarning: IPython.utils.traitlets has moved to a top-level 
>> traitlets package.
>>   warn("IPython.utils.traitlets has moved to a top-level traitlets 
>> package.")
>> C:\Python27\lib\site-packages\IPython\qt.py:13: ShimWarning: The 
>> `IPython.qt` package has been deprecated. You should import from 
>> qtconsole instead.
>>   "You should import from qtconsole instead.", ShimWarning)
>> MainThread     INFO     2016-09-13 14:21:06,648 
>> taurus.qt.qtgui.icon.icon: Setting Tango icon theme (from 
>> C:\Python27\lib\site-packages\taurus-4.0.1-py2.7.egg\taurus\qt\qtgui\icon\)
>> C:\Python27\lib\site-packages\IPython\config.py:13: ShimWarning: The 
>> `IPython.config` package has been deprecated. You should import from 
>> traitlets.config instead.
>>   "You should import from traitlets.config instead.", ShimWarning)
>> C:\Python27\lib\site-packages\IPython\core\interactiveshell.py:448: 
>> UserWarning: As of IPython 5.0 `PromptManager` config will have no 
>> effect and has been replaced by TerminalInteractiveShell.prompts_class
>>   warn('As of IPython 5.0 `PromptManager` config will have no effect'
>> Traceback (most recent call last):
>>   File "<string>", line 1, in <module>
>>   File "C:\Python27\lib\multiprocessing\forking.py", line 380, in main
>>     prepare(preparation_data)
>>   File "C:\Python27\lib\multiprocessing\forking.py", line 503, in prepare
>>     file, path_name, etc = imp.find_module(main_name, dirs)
>> ImportError: No module named spock
>> Spock 2.0.3 -- An interactive laboratory application.
>>
>> help      -> Spock's help system.
>> object?   -> Details about 'object'. ?object also works, ?? prints more.
>>
>> IPython profile: spockdoor
>>
>> Connected to Door_lab-01_1
>> [TerminalIPythonApp] WARNING | Error in loading extension: sardana.spock
>> Check your config files in C:\Users\m.sienczak\.ipython\profile_spockdoor
>> Traceback (most recent call last):
>>   File "C:\Python27\lib\site-packages\IPython\core\shellapp.py", line 
>> 246, in init_extensions
>>     self.shell.extension_manager.load_extension(ext)
>>   File "C:\Python27\lib\site-packages\IPython\core\extensions.py", 
>> line 85, in load_extension
>>     if self._call_load_ipython_extension(mod):
>>   File "C:\Python27\lib\site-packages\IPython\core\extensions.py", 
>> line 132, in _call_load_ipython_extension
>>     mod.load_ipython_extension(self.shell)
>>   File 
>> "C:\Python27\lib\site-packages\sardana\spock\ipython_01_00\genutils.py", 
>> line 818, in load_ipython_extension
>>     door = get_door()
>>   File 
>> "C:\Python27\lib\site-packages\sardana\spock\ipython_01_00\genutils.py", 
>> line 543, in get_door
>>     return _get_dev('door')
>>   File 
>> "C:\Python27\lib\site-packages\sardana\spock\ipython_01_00\genutils.py", 
>> line 531, in _get_dev
>>     taurus_dev = factory.getDevice(dev_name)
>>   File 
>> "C:\Python27\lib\site-packages\taurus-4.0.1-py2.7.egg\taurus\core\tango\tangofactory.py", 
>> line 292, in getDevice
>>     raise TaurusException("Invalid Tango device name '%s'" % dev_name)
>> TaurusException: Invalid Tango device name 
>> 'COMPNOT082W.PREVAC.EU.local:20000/Door/lab-01/1'
>>
>> In [1]: sar_demo
>> NameError: name 'sar_demo' is not defined
>> (For more detailed information type: python_error)
>>
>> In [2]:
>> ~~~
>>
>>
>> -- 
>> Greetings
>> Jagoda Sokół
>> Junior Software Developer
>> PREVAC sp. z o.o.
>>
>> Phone: +48 32 459 20 00
>> Fax: +48 32 459 20 01
>> www.prevac.eu <http://www.prevac.eu>
>>
>> Address: PL-44362 Rogow, ul. Raciborska 61, CEO: Dr.-Ing. Andreas 
>> Glenz, VAT ID: PL 6471782175, Regon: 273374884,
>> Companies Commercial Register No.: KRS 0000130401, Register Court: 
>> Gliwice, Basic capital: 619.800,00 PLN
>>
>> THE INFORMATION TRANSMITTED IS INTENDED ONLY FOR THE PERSON OR ENTITY 
>> TO WHICH IT IS ADDRESSED AND MAY CONTAIN CONFIDENTIAL OR PRIVILEGED 
>> MATERIAL. ANY REVIEW, RETRANSMISSION, DISSEMINATION OR OTHER USE OF, 
>> OR TAKING OF ANY ACTION IN RELIANCE UPON, THIS INFORMATION BY PERSONS 
>> OR ENTITIES OTHER THAN THE INTENDED RECIPIENT IS PROHIBITED. IF YOU 
>> RECEIVED THIS IN ERROR, PLEASE NOTIFY THE SENDER AND DELETE THE 
>> MATERIAL FROM YOUR COMPUTER.
>>
>>
>>
>> ------------------------------------------------------------------------------
>>
>>
>> _______________________________________________
>> Sardana-users mailing list
>> Sar...@li...
>> https://lists.sourceforge.net/lists/listinfo/sardana-users
>
> -- 
>
> ALBA Synchrotron <http://www.albasynchrotron.es>
>
> 	Zbigniew Reszela
> Computing & Controls Division
>
> ALBA SYNCHROTRON LIGHT SOURCE
> Carrer de la Llum 2-26 | 08290 | Cerdanyola del Vallès| Barcelona | 
> Spain <http://www.cells.es/en/about/coming-to-alba>
> (+34) 93 592 4407
> www.albasynchrotron.es <http://www.albasynchrotron.es>| 
> zre...@ce... <mailto:zre...@ce...> | legal notice 
> <https://www.cells.es/en/about/legal-notice>
>
> **Please, do not print this e-mail unless it is absolutely necessary.
> **Si heu rebut aquest correu per error, us informo que pot contenir 
> informació confidencial i privada i que està prohibit el seu ús. Us 
> agrairíem que ho comuniqueu al remitent i l'elimineu. Gràcies.
> Si ha recibido este correo por error, le informo de que puede contener 
> información confidencial y privada y que está prohibido su uso. Le 
> agradeceré que lo comunique a su remitente y lo elimine. Gracias.
> If you have received this e-mail in error, please note that it may 
> contain confidential and private information, therefore, the use of 
> this information is strictly forbidden. Please inform the sender of 
> the error and delete the information received. Thank you.
>

Re: [Tauruslib-users] [Sardana-users] Taurus 4.0.1, newest iPython and sar_demo command

[Zbigniew R. <zre...@ce...>]

Hi Jagoda,

Please try Sardana 2.1.0 that we have released today. The previous 
versions were not supporting Taurus 4 yet.
Just remember that from this version on, Sardana depends on itango >= 
0.1.4 [1].
Also don't be surprised about deprecation warnings when using this 
version of Sardana. They are there since we support the Taurus 3 version 
at the same time.

I'm not aware about any issues with IPython 5.1. If you find any, please 
fill in a bug in SF.

Cheers,
Zibi

PS. I see that you use spock on Windows. Don't you suffer bug-502 [2]?

[1] https://pypi.python.org/pypi/itango/0.1.4
[2] https://sourceforge.net/p/sardana/tickets/502/

On 09/13/2016 02:55 PM, Jagoda Sokół wrote:
>
> Hello Sardana & Taurus users ! :)
>
> We installed Taurus 4.0.1, iPython5.1.0, Sardana2.0.2 and following 
> error showed up while trying to run sar_demo, but no error was shown 
> when I downgraded iPython to 3.0 and Taurus to 3.6.
>
> Is there a possibility to run sar_demo with previously installed 
> version of Taurus 4.0.1 and newest iPython? If some more information 
> needed, please write back to me :)
>
> Console output:
>
> ~~~
> C:\Users\m.sienczak>spock
> MainThread     INFO     2016-09-13 14:21:06,411 TaurusRootLogger: 
> Using "PyQt4" for Qt
> C:\Python27\lib\site-packages\IPython\utils\traitlets.py:5: 
> UserWarning: IPython.utils.traitlets has moved to a top-level 
> traitlets package.
>   warn("IPython.utils.traitlets has moved to a top-level traitlets 
> package.")
> C:\Python27\lib\site-packages\IPython\qt.py:13: ShimWarning: The 
> `IPython.qt` package has been deprecated. You should import from 
> qtconsole instead.
>   "You should import from qtconsole instead.", ShimWarning)
> MainThread     INFO     2016-09-13 14:21:06,648 
> taurus.qt.qtgui.icon.icon: Setting Tango icon theme (from 
> C:\Python27\lib\site-packages\taurus-4.0.1-py2.7.egg\taurus\qt\qtgui\icon\)
> C:\Python27\lib\site-packages\IPython\config.py:13: ShimWarning: The 
> `IPython.config` package has been deprecated. You should import from 
> traitlets.config instead.
>   "You should import from traitlets.config instead.", ShimWarning)
> C:\Python27\lib\site-packages\IPython\core\interactiveshell.py:448: 
> UserWarning: As of IPython 5.0 `PromptManager` config will have no 
> effect and has been replaced by TerminalInteractiveShell.prompts_class
>   warn('As of IPython 5.0 `PromptManager` config will have no effect'
> Traceback (most recent call last):
>   File "<string>", line 1, in <module>
>   File "C:\Python27\lib\multiprocessing\forking.py", line 380, in main
>     prepare(preparation_data)
>   File "C:\Python27\lib\multiprocessing\forking.py", line 503, in prepare
>     file, path_name, etc = imp.find_module(main_name, dirs)
> ImportError: No module named spock
> Spock 2.0.3 -- An interactive laboratory application.
>
> help      -> Spock's help system.
> object?   -> Details about 'object'. ?object also works, ?? prints more.
>
> IPython profile: spockdoor
>
> Connected to Door_lab-01_1
> [TerminalIPythonApp] WARNING | Error in loading extension: sardana.spock
> Check your config files in C:\Users\m.sienczak\.ipython\profile_spockdoor
> Traceback (most recent call last):
>   File "C:\Python27\lib\site-packages\IPython\core\shellapp.py", line 
> 246, in init_extensions
>     self.shell.extension_manager.load_extension(ext)
>   File "C:\Python27\lib\site-packages\IPython\core\extensions.py", 
> line 85, in load_extension
>     if self._call_load_ipython_extension(mod):
>   File "C:\Python27\lib\site-packages\IPython\core\extensions.py", 
> line 132, in _call_load_ipython_extension
>     mod.load_ipython_extension(self.shell)
>   File 
> "C:\Python27\lib\site-packages\sardana\spock\ipython_01_00\genutils.py", 
> line 818, in load_ipython_extension
>     door = get_door()
>   File 
> "C:\Python27\lib\site-packages\sardana\spock\ipython_01_00\genutils.py", 
> line 543, in get_door
>     return _get_dev('door')
>   File 
> "C:\Python27\lib\site-packages\sardana\spock\ipython_01_00\genutils.py", 
> line 531, in _get_dev
>     taurus_dev = factory.getDevice(dev_name)
>   File 
> "C:\Python27\lib\site-packages\taurus-4.0.1-py2.7.egg\taurus\core\tango\tangofactory.py", 
> line 292, in getDevice
>     raise TaurusException("Invalid Tango device name '%s'" % dev_name)
> TaurusException: Invalid Tango device name 
> 'COMPNOT082W.PREVAC.EU.local:20000/Door/lab-01/1'
>
> In [1]: sar_demo
> NameError: name 'sar_demo' is not defined
> (For more detailed information type: python_error)
>
> In [2]:
> ~~~
>
>
> -- 
> Greetings
> Jagoda Sokół
> Junior Software Developer
> PREVAC sp. z o.o.
>
> Phone: +48 32 459 20 00
> Fax: +48 32 459 20 01
> www.prevac.eu <http://www.prevac.eu>
>
> Address: PL-44362 Rogow, ul. Raciborska 61, CEO: Dr.-Ing. Andreas 
> Glenz, VAT ID: PL 6471782175, Regon: 273374884,
> Companies Commercial Register No.: KRS 0000130401, Register Court: 
> Gliwice, Basic capital: 619.800,00 PLN
>
> THE INFORMATION TRANSMITTED IS INTENDED ONLY FOR THE PERSON OR ENTITY 
> TO WHICH IT IS ADDRESSED AND MAY CONTAIN CONFIDENTIAL OR PRIVILEGED 
> MATERIAL. ANY REVIEW, RETRANSMISSION, DISSEMINATION OR OTHER USE OF, 
> OR TAKING OF ANY ACTION IN RELIANCE UPON, THIS INFORMATION BY PERSONS 
> OR ENTITIES OTHER THAN THE INTENDED RECIPIENT IS PROHIBITED. IF YOU 
> RECEIVED THIS IN ERROR, PLEASE NOTIFY THE SENDER AND DELETE THE 
> MATERIAL FROM YOUR COMPUTER.
>
>
>
> ------------------------------------------------------------------------------
>
>
> _______________________________________________
> Sardana-users mailing list
> Sar...@li...
> https://lists.sourceforge.net/lists/listinfo/sardana-users

-- 

ALBA Synchrotron <http://www.albasynchrotron.es>

	Zbigniew Reszela
Computing & Controls Division

ALBA SYNCHROTRON LIGHT SOURCE
Carrer de la Llum 2-26 | 08290 | Cerdanyola del Vallès| Barcelona | 
Spain <http://www.cells.es/en/about/coming-to-alba>
(+34) 93 592 4407
www.albasynchrotron.es <http://www.albasynchrotron.es>| 
zre...@ce... <mailto:zre...@ce...> | legal notice 
<https://www.cells.es/en/about/legal-notice>

**Please, do not print this e-mail unless it is absolutely necessary.
**Si heu rebut aquest correu per error, us informo que pot contenir 
informació confidencial i privada i que està prohibit el seu ús. Us 
agrairíem que ho comuniqueu al remitent i l'elimineu. Gràcies.
Si ha recibido este correo por error, le informo de que puede contener 
información confidencial y privada y que está prohibido su uso. Le 
agradeceré que lo comunique a su remitente y lo elimine. Gracias.
If you have received this e-mail in error, please note that it may 
contain confidential and private information, therefore, the use of this 
information is strictly forbidden. Please inform the sender of the error 
and delete the information received. Thank you.

[Tauruslib-users] Taurus 4.0.1, newest iPython and sar_demo command

[Jagoda S. <j....@pr...>]

Hello Sardana & Taurus users ! :)

We installed Taurus 4.0.1, iPython5.1.0, Sardana2.0.2 and following 
error showed up while trying to run sar_demo, but no error was shown 
when I downgraded iPython to 3.0 and Taurus to 3.6.

Is there a possibility to run sar_demo with previously installed version 
of Taurus 4.0.1 and newest iPython? If some more information needed, 
please write back to me :)

Console output:

~~~
C:\Users\m.sienczak>spock
MainThread     INFO     2016-09-13 14:21:06,411 TaurusRootLogger: Using 
"PyQt4" for Qt
C:\Python27\lib\site-packages\IPython\utils\traitlets.py:5: UserWarning: 
IPython.utils.traitlets has moved to a top-level traitlets package.
   warn("IPython.utils.traitlets has moved to a top-level traitlets 
package.")
C:\Python27\lib\site-packages\IPython\qt.py:13: ShimWarning: The 
`IPython.qt` package has been deprecated. You should import from 
qtconsole instead.
   "You should import from qtconsole instead.", ShimWarning)
MainThread     INFO     2016-09-13 14:21:06,648 
taurus.qt.qtgui.icon.icon: Setting Tango icon theme (from 
C:\Python27\lib\site-packages\taurus-4.0.1-py2.7.egg\taurus\qt\qtgui\icon\)
C:\Python27\lib\site-packages\IPython\config.py:13: ShimWarning: The 
`IPython.config` package has been deprecated. You should import from 
traitlets.config instead.
   "You should import from traitlets.config instead.", ShimWarning)
C:\Python27\lib\site-packages\IPython\core\interactiveshell.py:448: 
UserWarning: As of IPython 5.0 `PromptManager` config will have no 
effect and has been replaced by TerminalInteractiveShell.prompts_class
   warn('As of IPython 5.0 `PromptManager` config will have no effect'
Traceback (most recent call last):
   File "<string>", line 1, in <module>
   File "C:\Python27\lib\multiprocessing\forking.py", line 380, in main
     prepare(preparation_data)
   File "C:\Python27\lib\multiprocessing\forking.py", line 503, in prepare
     file, path_name, etc = imp.find_module(main_name, dirs)
ImportError: No module named spock
Spock 2.0.3 -- An interactive laboratory application.

help      -> Spock's help system.
object?   -> Details about 'object'. ?object also works, ?? prints more.

IPython profile: spockdoor

Connected to Door_lab-01_1
[TerminalIPythonApp] WARNING | Error in loading extension: sardana.spock
Check your config files in C:\Users\m.sienczak\.ipython\profile_spockdoor
Traceback (most recent call last):
   File "C:\Python27\lib\site-packages\IPython\core\shellapp.py", line 
246, in init_extensions
     self.shell.extension_manager.load_extension(ext)
   File "C:\Python27\lib\site-packages\IPython\core\extensions.py", line 
85, in load_extension
     if self._call_load_ipython_extension(mod):
   File "C:\Python27\lib\site-packages\IPython\core\extensions.py", line 
132, in _call_load_ipython_extension
     mod.load_ipython_extension(self.shell)
   File 
"C:\Python27\lib\site-packages\sardana\spock\ipython_01_00\genutils.py", 
line 818, in load_ipython_extension
     door = get_door()
   File 
"C:\Python27\lib\site-packages\sardana\spock\ipython_01_00\genutils.py", 
line 543, in get_door
     return _get_dev('door')
   File 
"C:\Python27\lib\site-packages\sardana\spock\ipython_01_00\genutils.py", 
line 531, in _get_dev
     taurus_dev = factory.getDevice(dev_name)
   File 
"C:\Python27\lib\site-packages\taurus-4.0.1-py2.7.egg\taurus\core\tango\tangofactory.py", 
line 292, in getDevice
     raise TaurusException("Invalid Tango device name '%s'" % dev_name)
TaurusException: Invalid Tango device name 
'COMPNOT082W.PREVAC.EU.local:20000/Door/lab-01/1'

In [1]: sar_demo
NameError: name 'sar_demo' is not defined
(For more detailed information type: python_error)

In [2]:
~~~


-- 
Greetings
Jagoda Sokół
Junior Software Developer
PREVAC sp. z o.o.

Phone: +48 32 459 20 00
Fax: +48 32 459 20 01
www.prevac.eu <http://www.prevac.eu>

Address: PL-44362 Rogow, ul. Raciborska 61, CEO: Dr.-Ing. Andreas Glenz, 
VAT ID: PL 6471782175, Regon: 273374884,
Companies Commercial Register No.: KRS 0000130401, Register Court: 
Gliwice, Basic capital: 619.800,00 PLN

THE INFORMATION TRANSMITTED IS INTENDED ONLY FOR THE PERSON OR ENTITY TO 
WHICH IT IS ADDRESSED AND MAY CONTAIN CONFIDENTIAL OR PRIVILEGED 
MATERIAL. ANY REVIEW, RETRANSMISSION, DISSEMINATION OR OTHER USE OF, OR 
TAKING OF ANY ACTION IN RELIANCE UPON, THIS INFORMATION BY PERSONS OR 
ENTITIES OTHER THAN THE INTENDED RECIPIENT IS PROHIBITED. IF YOU 
RECEIVED THIS IN ERROR, PLEASE NOTIFY THE SENDER AND DELETE THE MATERIAL 
FROM YOUR COMPUTER.

Re: [Tauruslib-users] TaurusJDrawSynopticsView - problem

[Carlos P. <cpa...@ce...>]

Sorry for the late reply. I was on holidays ...

It looks like you need to install the ply python module, which is a dependency for the synoptics.

See a list of deps for the 3.x series in:
http://www.taurus-scada.org/en/3.7.3/users/getting_started.html#dependencies

And for Taurus4 in:
http://www.taurus-scada.org/en/stable/users/getting_started.html#dependencies

Cheers!

Carlos

On Thu 21 July 2016 11:41:14 Lukasz Zytniak wrote:
> Hello Carlos,
> 
> I apologize that I sent email only to Alba, I hoped that it is some
> minor problem, that can be fixed on fly.
 I launched taurusgui with
> `--taurus-log-level=debug` and '--fail-proof' flag, please check
> attachment. 
> Moreover, I found out that I have problem to import jdraw module from
> taurus.
 
> I installed taurus 3.7.3 with –egg
> 
> I tried also with script that you sent but with the same effect.
> 
> Do you have any advice for me?
> 
> Thank you in advance for your help.
> 
> Kind regards,
> Lukasz
> 
> 
> On 20/07/16 17:55, "Carlos Pascual" <cpa...@ce...> wrote:
> 
>     Hi Lukasz,
>     
>    
> 
+--------------------------------------------------------------------
> ----------------------------+
 Comment before the reply:
>     Please use the Taurus mailing list(s) for this type of questions
> rather 
 than contacting us directly. It is more convenient for us
> and it benefits the community.
>     I am CC-ing to the tauruslib-users list so that the reply can be
> useful 
 for other people as well.
>    
> 
+--------------------------------------------------------------------
> ----------------------------+
 
>     It looks like a problem with reading your synoptic file 
>     ("ufo_small_prevac") is preventing the synoptic to load. 
>     Make sure that the location of the file is ok.
>     
>     You may get more info by launching the taurusgui with 
>     `--taurus-log-level=debug`
>     
>     You can also confirm that your installation and, particularly, the
> 
 synoptic widget, is ok by running
>     `taurusgui example01 --fail-proof`
>     
>     (It should load a demo gui with a couple of synoptics, I just did
> that 
 on a fresh installation of taurus-3.7.3 and works fine for me.
> ) 
>     Another idea to have less noise while debugging: write a small
> script 
 that instantiates a TaurusJdrawSynopticView and loads your
> file. Something like:
>     
>     ~~~~
>     import sys
>     import taurus
>     taurus.setLogLevel(taurus.Debug)
>     
>     from taurus.qt.qtgui.application import TaurusApplication
>     from taurus.qt.qtgui.graphic import TaurusJDrawSynopticsView
>     
>     app = TaurusApplication()
>     w  = TaurusJDrawSynopticsView()
>     
>     fname = 'path/to/a/jdw/file' # <--put abs path to your file
>     
>     w.setModel(fname)
>     w.show()
>     sys.exit(app.exec_())
>     ~~~~
>     
>     I hope this helps. 
>     
>     Carlos
>     
>     On Wed 20 July 2016 14:56:02 Lukasz Zytniak wrote:
> 
>     > Hello,
>     > 
>     > I have probably easy to solve problem, I am using newest
>     > TangoBox with
 taurus 3.7.3 but when I tried to run my old
>     > TaurusGUI I get error: [cid:image001.png@01D1E2A7.96D8C720]
>     > 
>     > 
>     > Thank you in advance for your help.
>     > 
>     > Best regards,
>     > Lukasz
> 
>     
>     -- 

[Tauruslib-users] Taurus & data visualization from file

[Łukasz Ż. <luk...@uj...>]

Hello,

I have a question, is it possible to visualize data from CSV file using taurus?

Best regards,
Lukasz

Re: [Tauruslib-users] TaurusJDrawSynopticsView - problem

[Carlos P. <cpa...@ce...>]

Hi Lukasz,

+------------------------------------------------------------------------------------------------+
Comment before the reply: 
Please use the Taurus mailing list(s) for this type of questions rather 
than contacting us directly. It is more convenient for us and it benefits 
the community.
I am CC-ing to the tauruslib-users list so that the reply can be useful 
for other people as well.
+------------------------------------------------------------------------------------------------+

It looks like a problem with reading your synoptic file 
("ufo_small_prevac") is preventing the synoptic to load. 
Make sure that the location of the file is ok.

You may get more info by launching the taurusgui with 
`--taurus-log-level=debug`

You can also confirm that your installation and, particularly, the 
synoptic widget, is ok by running 
`taurusgui example01 --fail-proof`

(It should load a demo gui with a couple of synoptics, I just did that 
on a fresh installation of taurus-3.7.3 and works fine for me. )

Another idea to have less noise while debugging: write a small script 
that instantiates a TaurusJdrawSynopticView and loads your file. 
Something like:

~~~~
import sys
import taurus
taurus.setLogLevel(taurus.Debug)

from taurus.qt.qtgui.application import TaurusApplication
from taurus.qt.qtgui.graphic import TaurusJDrawSynopticsView

app = TaurusApplication()
w  = TaurusJDrawSynopticsView()

fname = 'path/to/a/jdw/file' # <--put abs path to your file

w.setModel(fname)
w.show()
sys.exit(app.exec_())
~~~~

I hope this helps. 

Carlos

On Wed 20 July 2016 14:56:02 Lukasz Zytniak wrote:
> Hello,
> 
> I have probably easy to solve problem, I am using newest TangoBox with
> taurus 3.7.3 but when I tried to run my old TaurusGUI I get error:
> [cid:image001.png@01D1E2A7.96D8C720]
> 
> 
> Thank you in advance for your help.
> 
> Best regards,
> Lukasz

-- 
+----------------------------------------------------+
 Carlos Pascual Izarra
 Scientific Software Coordinator
 Computing Division
 ALBA Synchrotron  [http://www.albasynchrotron.es]
 Carrer de la Llum 2-26
 E-08290 Cerdanyola del Valles (Barcelona), Spain
 E-mail: cpa...@ce...
 Phone: +34 93 592 4428
+----------------------------------------------------+

[Tauruslib-users] New releases for Jul16 (Taurus 4.0.1 and Taurus 3.7.3)

[Carlos P. <cpa...@ce...>]

Hi all,

Today we are announcing two simultaneous releases of Taurus:

- Taurus 4.0.1: the first official release for the 4.x series
- Taurus 3.7.3: a support release for the (now legacy) 3.x series

The source files and windows installers can be downloaded from PyPI:

    http://pypi.python.org/pypi/taurus


The documentation for both releases is available at:

    http://www.taurus-scada.org


Taurus 4.0.1 brings many changes. The most important are:

- Taurus core is now simpler and scheme-agnostic (tango is 
  now an optional dependency, and an scheme-agnostic API is available)
- Proper units support introduced (numerical attribute values are now 
  pint.Quantity objects)
- Model "fragments" support has been added
- The eval scheme is now much better (simpler and more powerful syntax)
- Epics scheme is now available
- taurus.qt now uses new-style PyQt signals (guiqwt3 is now supported)
- Icon resource files are no longer needed. Better Theme icon support
- Much larger and improved testsuite
- setuptools-based installer (pip now works without --egg)
- documentation has improved
- several old, deprecated and unused modules have been cleaned
- many more...

For a detailed list of changes, see the CHANGELOG:

    http://sf.net/p/tauruslib/taurus.git/ci/4.0.1/tree/CHANGELOG.md

And the issue tracker:

      http://sf.net/p/tauruslib/tickets/milestone/Jul16/

or, for a full log of commits, run (in your git repo):

      git log 3.7.0..4.0.1
      

Regarding backwards compatibility: Taurus 4.0.1 provides a backwards
compatibility API to facilitate the transition for applications created 
for taurus 3.x. Most applications should run with no or minor 
modifications in Taurus 4 and deprecation messages will be logged to 
help identifying the parts of the code that should be updated later on).
Only in very specific cases, where the compatibility cannot be handled 
automatically, the application may need to be modified in order to run 
on Taurus 4.

We encourage you to try your applications with this new release as soon 
as possible, and to report any issues found so that we can avoid a long 
transition time from 3.x to 4.x.
Please note that new features are likely to be implemented on the 4.x 
series only, and the 3.x support may be discontinued soon.


Regarding the 3.7.3 release, it is just a bugfix update with respect 
to the 3.7.0 released last January. It fixes bugs #260, #261, #269, 
#277 and #300 as well as few other issues for the 3.x series.


If you encounter problems with any of these releases, please
report them back to the taurus mailing list:

    tau...@li...

or put a ticket in the taurus project:

    http://sourceforge.net/p/tauruslib/tickets/
    

Cheers!

Carlos, (on behalf of the taurus developers)

-- 
+----------------------------------------------------+
 Carlos Pascual Izarra
 Scientific Software Coordinator
 Computing Division
 ALBA Synchrotron  [http://www.albasynchrotron.es]
 Carrer de la Llum 2-26
 E-08290 Cerdanyola del Valles (Barcelona), Spain
 E-mail: cpa...@ce...
 Phone: +34 93 592 4428
+----------------------------------------------------+

Re: [Tauruslib-users] Help to implement access control on TAURUS based application

[Carlos P. <cpa...@ce...>]

On Wed 8 June 2016 19:27:38 Kalyani wrote:
> Hi Carlos,
> 
> Thanks for your inputs. However I would like to discuss the first
> point.
> 
> We had explored Tango Access Control for implementing our
> authentication mechanism. The basic issue we faced for our
> application was the fact that Tango Access Control uses 'System Log
> In' name as the user name for authentication. Whereas, in our
> application we would have multiple user credentials under same system
> log in ( i.e the application user credentials are independent of the
> system log in user credentials). 

But without using the OS authentication, I find it very difficult (impossible?) to build anything 
even mildly secure. And IMHO, the false security is way worse than no security at all.


> Nevertheless, we thought of few
> workarounds to tackle this limitation but everything failed under
> multiple user login (at the same time on same machine) scenario. 
> Is there any way we could use Tango Access Control independent of the
> system log in?

I am afraid I know almost nothing about Tango Access Control . I  never used it. You may try 
asking in the tango mailing list/ forums

> 
> Having faced the above limitation, we had decided to look for
> authentication mechanism at GUI level itself. The options you
> provided are very insightful. We would explore them from our
> application perspective.

Just keep in mind the fact that the user will be able to copy and run modified versions of your 
GUI, so IMHO, the most you can do is to offer the convenience of choosing "profiles" (e.g. 
customised perspectives in a GUI), but you will have to accept that the user will be able to 
choose whatever profile he/she wants (and a application-level auth mechanism will hardly stop 
a determined used).

Cheers,


PS: if you want to continue this discussion, please reply to 
tau...@li... so that other people can also see it (note that if  you do 
not want to receive the list emails, you can always configure your registration as such)

> 
> -----Carlos Pascual <cpa...@ce...> wrote: -----
> To: tau...@li...
> From: Carlos Pascual <cpa...@ce...>
> Date: 06/08/2016 03:53PM
> Cc: Kalyani Thigale <kal...@tc...>
> Subject: Re: Help to implement access control on TAURUS based
> application
> 
> Hi Kalyani,
>  
> I hope you do not mind me posting my reply to the users mailing list.
> I think this is a topic that may interest other users as well, plus
> also maybe other users have implemented something apart of what it is
> distributed in Taurus. 
> See the rest of my reply below your question:
>  
> 
> On Wed 8 June 2016 10:59:30 Kalyani wrote:
> > We need to implement authentication mechanism in our control system
> > application based on TANGO framework. We are looking for user level
> > access control(Access for device server, devices and commands) at
> > TAURUS GUI level. Are there any tools or access control mechanism
> > provided by TAURUS. Could you please share the details with us. It
> > would be also helpful if you could share the details of any existing
> > control system that uses access control.  It would be great help for
> > us.
> 
>  
>  
> There are a few related mechanisms":
>  
> - You can interface with the Tango Access Control [1] via Taurus, but
> there are no specific taurus widgets for that (although maybe someone
> has already implemented them on their own). - TaurusGui [2] provides
> the "lock view" mechanism (to prevent inadvertent changes of
> appearance) as well as perspectives (which can be used for providing
> "basic" and "expert" modes in the GUI) - You can use filters in
> TaurusAttributeForm and TaurusCommandForm to avoid showing controls
> for arbitrary attributes or commands [3] - There is the
> TaurusLockButton [4] and the TangoDevice lock API [5] 
>  
> BUT, if what you are after is some kind of user authentication
> mechanism *at Taurus GUI level* that requires the user to
> authenticate before he/she can access a resource (e.g. to write a to
> certain attribute) and/or access parts of a GUI (e.g., to switch to a
> certain perspective, or to unlock the view), then you need to first
> consider the kind of (ab)use you want to protect against: 
> a) Unintentional access to resources (aka "dumb user inadvertently
> messing with some critical component") 
> b) Non-malicious but intentional attempt to bypass Taurus-based
> restrictions 
> c) Malicious attempts to disrupt/abuse the system
>  
>  
> Protecting against c) is, IMHO impossible in a Tango-based system.
> Tango is "by design" insecure (communications are not authenticated
> or otherwise protected, so they can be eavesdropped and tampered
> with). See [1]. 
> Protecting against b) **may** be possible but **only at Tango level**
> (i.e. using Tango Access Control). But note that this would be a
> protection at Tango level, not at Taurus GUI level. Keep in mind that
> a user facing a restriction in a Taurus GUI can always just copy the
> GUI code, edit it to bypass the restriction and run the modified code
> instead of the original. Furthermore, a user could just use PyTango,
> or jive to circumvent any Taurus-imposed restrictions. 
> So, this leaves us with only a) as a realistic "threat" to protect
> against at the Taurus level. And IMHO, confirmation messages that
> require some sort of "captcha" (e.g.: "This is may be dangerous. To
> confirm that you are really sure, please type 'yes please let me do
> it'") are more effective and easier to implement in this case than
> user authentication mechanisms. But if someone insists on going the

Re: [Tauruslib-users] Help to implement access control on TAURUS based application

[Carlos P. <cpa...@ce...>]

Hi Kalyani,

I hope you do not mind me posting my reply to the users mailing list. I think this is a topic that 
may interest other users as well, plus also maybe other users have implemented something 
apart of what it is distributed in Taurus.

See the rest of my reply below your question:

On Wed 8 June 2016 10:59:30 Kalyani wrote:
> We  need to implement authentication mechanism in our control system 
> application based on TANGO framework. We are looking for user level 
> access control(Access for device server, devices and commands) at
> TAURUS  GUI level. Are there any tools or access control mechanism
> provided by  TAURUS. Could you please share the details with us. It
> would be also  helpful if you could share the details of any existing
> control system  that uses access control.  It would be great help for
> us.


There are a few related mechanisms":

- You can interface with the Tango Access Control [1] via Taurus, but there are no specific taurus 
widgets for that (although maybe someone has already implemented them on their own).
- TaurusGui [2] provides the "lock view" mechanism (to prevent inadvertent changes of 
appearance) as well as perspectives (which can be used for providing "basic" and "expert" modes 
in the GUI)
- You can use filters in TaurusAttributeForm and TaurusCommandForm to avoid showing 
controls for arbitrary attributes or commands [3]
- There is the TaurusLockButton [4] and the TangoDevice lock API [5]


BUT, if what you are after is some kind of user authentication mechanism *at Taurus GUI level* 
that requires the user to authenticate before he/she can access a resource (e.g. to write a to 
certain attribute) and/or access parts of a GUI (e.g., to switch to a certain perspective, or to 
unlock the view), then you need to first consider the kind of (ab)use you want to protect against:

a) Unintentional access to resources (aka "dumb user inadvertently messing with some critical 
component")

b) Non-malicious but intentional attempt to bypass Taurus-based restrictions

c) Malicious attempts to disrupt/abuse the system


Protecting against c) is, IMHO impossible in a Tango-based system. Tango is "by design" insecure  
(communications are not authenticated or otherwise protected, so they can be eavesdropped 
and tampered with). See [1].

Protecting against b) **may** be possible but **only at Tango level** (i.e. using Tango Access 
Control). But note that this would be a protection at Tango level, not at Taurus GUI level. Keep 
in mind that a user facing a restriction in a Taurus GUI can always just copy the GUI code, edit it 
to bypass the restriction and run the modified code instead of the original. Furthermore, a user 
could just use PyTango, or jive to circumvent any Taurus-imposed restrictions.

So, this leaves us with only a) as a realistic "threat" to protect against at the Taurus level. And 
IMHO, confirmation messages that require some sort of "captcha" (e.g.: "This is may be 
dangerous. To confirm that you are really sure, please type 'yes please let me do it'")  are more 
effective and easier to implement in  this case than user authentication mechanisms.
But if someone insists on going the "user authentication way", I would suggest to use any of the 
existing python modules to interact with the OS authentication mechanisms (python-ldap, 
python-pam, etc) rather than implementing a naive home-made solution which may end up 
being a source of leaked passwords and give a false security feeling.


I hope this answer is useful. Note that I may have overlooked something. Please send any 
comments by replying on the mailing list.

Cheers,

Carlos

[1] See section 3.7 of http://ftp.esrf.fr/pub/cs/tango/tango_92.pdf
[2] http://www.taurus-scada.org/en/stable/users/ui/taurusgui.html#re-arranging-panels-moving-resizing-hiding
[3] http://www.taurus-scada.org/en/stable/devel/api/taurus/qt/qtgui/panel/_TaurusAttrForm.html#taurus.qt.qtgui.
panel.TaurusAttrForm
[4] 	http://www.taurus-scada.org/en/stable/devel/api/taurus/qt/qtgui/button/_TaurusLockButton.html
[5] http://www.taurus-scada.org/en/stable/devel/api/taurus/core/tango/_TangoDevice.html




-- 
+----------------------------------------------------+
 Carlos Pascual Izarra
 Scientific Software Coordinator
 Computing Division
 ALBA Synchrotron  [http://www.albasynchrotron.es]
 Carrer de la Llum 2-26
 E-08290 Cerdanyola del Valles (Barcelona), Spain
 E-mail: cpa...@ce...
 Phone: +34 93 592 4428
+----------------------------------------------------+

[Tauruslib-users] Qt5 support

[Carlos P. <cpa...@ce...>]

Hi all,

Many people are contacting us inquiring for our plans to support Qt5, so 
I think it is nice to give a public update about these plans.

We currently support PyQt4 only, but we are already working towards 
supporting PyQt5.

The main blocker for Qt5 is that in Taurus 3.x we had to support 
PyQt4.4, which does not support API2 or new-style signals (making it 
incompatible with PyQt5 [1]). 

Now, in the current development version (Taurus 4), we dropped the 
support for PyQt<4.8 and we freed ourselves to migrate everything to 
API2 and new-style signals, opening the door to Qt5 [2].

The migration of the signals is being worked on right now (thanks to the 
maxIV people!) [3]

Once the signals are migrated, we will have to deal with the other 
differences listed in [1], but we expect them to imply far less work than 
the refactoring of the signals.

As for when it will be finished, we would love to see it (at least 
partially) for the Jul16 milestone, and, in any case, within this year. 
But of course this depends also on how many people joins the effort [4].

Cheers,

Carlos

[1] http://pyqt.sf.net/Docs/PyQt5/pyqt4_differences.html
[2] http://sf.net/p/tauruslib/tickets/245/
[3] http://sf.net/p/tauruslib/tickets/187/
[4] I am sure you got the hint...   ;)


-- 
+----------------------------------------------------+
 Carlos Pascual Izarra
 Scientific Software Coordinator
 Computing Division
 ALBA Synchrotron  [http://www.albasynchrotron.es]
 Carrer de la Llum 2-26
 E-08290 Cerdanyola del Valles (Barcelona), Spain
 E-mail: cpa...@ce...
 Phone: +34 93 592 4428
+----------------------------------------------------+

[Tauruslib-users] Taurus 4 is now in the develop branch

[Carlos P. <cpa...@ce...>]

Hi all,

As you may know, we have been working for almost 3 years to implement 
the next major version of Taurus (version 4.x) in parallel with 
developing the 3.x version.

A very important milestone has been reached now with the promotion of 
version 4.x to the official develop branch.

Since the develop branch is the main base for new development, this 
means that any new features will from now on be added by default to the 
4.x versions, while 3.x will be "frozen" and mostly just see essential 
hotfixes.

The develop branch is also the base for the next official release, so  
hopefully the Jul16 release will already be of the 4.x series.

The official documentation still needs to be adapted (help wanted!), but 
the following "Taurus Enhancement Proposals" document the main 
changes from the 3.x to the 4.x:

http://sf.net/p/tauruslib/wiki/TEP3/
http://sf.net/p/tauruslib/wiki/TEP14/

We encourage you to try this new version and report any issues  or 
contribute changes to help us in getting taurus 4 ready for release as 
soon as possible.

Note: while the 4.x series is not 100% backwards-compatible with the 3.x 
series (hence the major version change), most 3.x based applications 
will work with 4.x out-of-the-box thanks to a compatibility layer that 
will log deprecation messages and hint ways to update the code to 4.x.

For testing, just check out the develop branch from the official git repo, 
or, alternatively, install with pip using:

~~~~~~~~~~~~~~~~~~
pip install --egg \  
   git+http://git.code.sf.net/p/tauruslib/taurus.git@develop
~~~~~~~~~~~~~~~~~~

Cheers,

Carlos (on behalf of the Taurus developers)


-- 
+----------------------------------------------------+
 Carlos Pascual Izarra
 Scientific Software Coordinator
 Computing Division
 ALBA Synchrotron  [http://www.albasynchrotron.es]
 Carrer de la Llum 2-26
 E-08290 Cerdanyola del Valles (Barcelona), Spain
 E-mail: cpa...@ce...
 Phone: +34 93 592 4428
+----------------------------------------------------+

Re: [Tauruslib-users] [tauruslib-devel] New release of Taurus 3.7.0 (Jan16)

[PICCA Frederic-E. <fre...@sy...>]

Hello carlos.

Thanks a lot

Do you have a script which can be run in order to test taurus during the build process or in the debian ci integration system ?

Cheers

Fred

[Tauruslib-users] New release of Taurus 3.7.0 (Jan16)

[Carlos P. <cpa...@ce...>]

Hi all,

The new Taurus release 3.7.0 (corresponding to the Jan16 milestone) is 
now available to download from PyPI  (source and windows installer):
    
    http://pypi.python.org/pypi/taurus/3.7.0

To install using pip, run:

    pip install taurus --egg

To install from source, download the tar.gz from pypi, untar and run:
    
    python setup.py install 


The documentation is available at:

    http://www.taurus-scada.org

The main improvements since taurus 3.6.0 (aka Jul15) are:
    
    - Added support for sqlite DB in Tango (ticket #148)
    - Fixed many usability bugs in TaurusTrend2D and other
      guiqwt-based widgets (#238, #240, #244, #247, #251, #258)
    - Fixed issues with "export to ASCII" feature of plots
    - Fixed issues with PLY optimization (#262)
    - "taurus-polling-period" argument works for evaluation
      attributes now too (#249)
    - many other bugs fixed
    
For a detailed list of solved issues, see:

      http://sf.net/p/tauruslib/tickets/milestone/Jan16/
    
or, for a full log of commits, run (in your git repo):

      git log 3.6.0..3.7.0

If you encounter problems installing or running this release, please
report them back to the taurus mailing list:

    tau...@li...

or put a ticket in the taurus project:

    http://sourceforge.net/p/tauruslib/tickets/

Cheers!

Carlos (on behalf of the taurus developers)


-- 
+----------------------------------------------------+
 Carlos Pascual Izarra
 Scientific Software Coordinator
 Computing Division
 ALBA Synchrotron  [http://www.albasynchrotron.es]
 Carrer de la Llum 2-26
 E-08290 Cerdanyola del Valles (Barcelona), Spain
 E-mail: cpa...@ce...
 Phone: +34 93 592 4428
+----------------------------------------------------+

Re: [Tauruslib-users] [tauruslib-user] taurustrend --use-archiving - problem

[Lukasz Z. <luk...@uj...>]

Hi Sergi,

This is output I got, following your steps:
> In [1]: attr = 'i-k01/vac/i-k01cab05-vac-ipcu1/pressure'
>
> In [2]: import PyTangoArchiving
> /home/tango/lib/python2.7/site-packages/setuptools-18.0.1-py2.7.egg/pkg_resources/__init__.py:1256: 
> UserWarning: /home/Operator/.python-eggs is writable by group/others 
> and vulnerable to attack when used with get_resource_filename. 
> Consider a more secure location (set with .set_extraction_path or the 
> PYTHON_EGG_CACHE environment variable).
>
> In [3]: rd = PyTangoArchiving.Reader()
> None.Reader.WARNING    2015-12-09 17:17:34.206    Unable to get DB 
> config at 1449677854.21, using Java Extractors.
> list index out of range
> None.Reader.INFO    2015-12-09 17:17:34.207    loading by 
> Noneextractor server_name
> None.Reader.INFO    2015-12-09 17:17:34.207 
>  get_devs_from_db(dserver/Noneextractor/*)
> None.Reader.INFO    2015-12-09 17:17:34.216 
>  get_devs_from_db(dserver/Noneextractor/*): no matches found.
> None.Reader.WARNING    2015-12-09 17:17:34.216    No server matches 
> with Noneextractor (family=Noneextractor).
> None.Reader.ERROR    2015-12-09 17:17:34.216    Impossible to retrieve 
> server for class TdbExtractor
> None.Reader.WARNING    2015-12-09 17:17:34.216    Try 
> ServersDict.load4class
> None.Reader.INFO    2015-12-09 17:17:34.219    No available extractors 
> found, PyTangoArchiving.Reader disabled
>
> In [4]: rd.is_attribute_archived(attr)
> None.Reader.WARNING    2015-12-09 17:17:44.653    Unable to get DB 
> config at 1449677864.65, using Java Extractors.
> list index out of range
> Out[4]: False
>
> In [5]: rd.get_attribute_values(attr,-3600)
> None.Reader.WARNING    2015-12-09 17:21:12.940    Unable to get DB 
> config at 1449678072.94, using Java Extractors.
> list index out of range
> None.Reader.INFO    2015-12-09 17:21:12.941    In 
> PyTangoArchiving.Reader.get_attribute_values: Archiving not available!
> Out[5]: []
>
> In [6]: 
In attachment you can find print screen from Mambo.

I am looking forward to hearing from you.

Best regards,
Lukasz Zytniak


W dniu 2015-11-23 o 10:01, Sergi Rubio pisze:
> Well, to check if your attribute is archived or not:
>
> > ipython
> # import PyTangoArchiving
> # attribute = 'a/b/c/d'
> # rd = PyTangoArchiving.Reader()
> # rd.is_attribute_archived(attribute)
>
> if the result is True, ask for the last hour values
>
> # rd.get_attribute_values(attribute,-3600)
>
> If the result is False or exception, please reply with your output
>
> To add the attribute to archiving:
>
> # hdb = PyTangoArchiving.ArchivingAPI('hdb') #or tdb for temporary 
> archiving
> # hdb.start_archiving(attribute) #To archive every minute
> # hdb.start_archiving(attribute,{'MODE_P':[15000]}) #To archive every 15s
>
> If it fails, reply to this email with your output. The arguments for 
> start_archiving
> are described in the ArchivingManager documentation.
>
> For using tdb you have to configure the DB maintenance/cleanup in your
> DB server, you can ask Soleil regarding that.
>
>
> Sergi Rubio
>
> On 11/23/2015 09:50 AM, Carlos Pascual wrote:
>> Hi Lukasz,
>>
>> As I said, I am personally not an expert on archiving. Sergi Rubio (in
>> CC)  is the author of the archiving support of TaurusTrend, so he may be
>> able to give better help.
>>
>> With my limited knowledge, all I can suggest is:
>> 1- make sure you use Soleil's archiving system (according to srubio, it
>> doesn't work with other archivers)
>> 2- make sure that your attribute (let's say "a/b/c/d") is configured in
>> the archiver and also that its values are really being archived (*)
>> 3- launch taurustrend a/b/c/d
>> 4- use the context menu to enable archiving (righ-click->use archiver)
>> 5- Now go to plot configuration (Right-click->plot configuration) and
>> disable the "Fixed-range scale" checkbox. Then enter a start value
>> previous to the time when you launched the trend (step 3). Apply and
>> Close the configuration dialog.
>>
>> You should be seeing archived values now.
>>
>> (*) Note: this is crucial, but it is where I cannot help you much since
>> I've never done this myself. I guess you can do a mysql query against
>> the DB, or use Mambo...
>>
>>
>>
>>
>> On Fri 20 November 2015 12:06:42 Lukasz Zytniak wrote:
>>> Hi Carlos,
>>>
>>> Please find in attachment printscreen from Astor, as I know we are
>>> using *external* archiver infrastructure.
>>> Still, I have problem with  taurustrend --use-archiving.
>>>
>>> Could you please help me?
>>>
>>> Best regards,
>>> Lukasz
>>>
>>> W dniu 2015-11-13 o 16:06, Carlos Pascual pisze:
>>>> (Note: the original message was sent to both devel and users list. I
>>>> reply only to the the users list to avoid duplication of messages)
>>>>
>>>> Hi,
>>>>
>>>> Since the feature is working without problems in Alba and you do not
>>>> give details of how you are trying it, I can only guess a very basic
>>>> explanation... please excuse me if my answer is too obvious:
>>>>
>>>> In order to use the archiving feature you need, first of all, to
>>>> have the values archived. That is, an *external* archiver
>>>> infrastructure is needed, and the attributes for which you wish to
>>>> access the archived values need to be configured for archiving.
>>>>
>>>> Sergi rubio may be able to give further hints...
>>>>
>>>> Cheers,
>>>> Carlos
>>>>
>>>> On Fri 13 November 2015 15:22:47 Lukasz Zytniak wrote:
>>>>> Hello All,
>>>>>
>>>>> I have a question about taurustrend --use-archiving, as you can
>>>>> find
>>>>> in attachment, it doesn't work.
>>>>> I tested it on new TangoBox9 and in control room at Solaris (we are
>>>>> using taurus-3.3.0).
>>>>> I didn't find any ticket
>>>>> (http://sourceforge.net/p/tauruslib/tickets/), so maybe I use it in
>>>>> wrong way or I don't know how to configure it? I found in
>>>>> documentation:
>>>>> http://www.taurus-scada.org/en/stable/users/ui/trend.html#accessing
>>>>> -ar chived-values
>>>>>
>>>>> I will be very gratefull for your help.
>>>>>
>>>>> Kind regards,
>>>>> Lukasz
>


-- 
Kind Regards,
Lukasz Zytniak

Control Software Engineer
---------------------------------------------------------------
Synchrotron Radiation Centre "Solaris"
Jagiellonian University
98 Czerwone Maki Street; 30-392 Krakow
mobile: +48 519 307 972
www.synchrotron.pl

[Tauruslib-users] Unexpected behavior of Taurus Labels

[Binit A. <bin...@tc...>]

Hi All, 

We have observed some unexpected behavior of Taurus Labels. 
Please find the attachment of screenshot, where we can see different Taurus Labels with same model giving different values. 
We have launched two instances of same application in the above scenario(with different style sheet- Probably that's not the problem). 


We have checked the values of those attributes, there it was showing "NO ALARMS". You can see in the right portion of the GUI. Where other Taurus Labels are behaving as expected. What will be the probable reasons so the we can explain these behaviors : 


    • Garbage values in Taurus Labels though attributes attached to them have valid values.' 
    • Different values in different Taurus Labels with same model . 


Setup details : OS: Fedora 19 
Tango 8.1.2 patched 
Taurus 3.4.0 
PyQt 4 
-- 
Thanks & Regards 
Binit Amin 
Assistant System Engineer 
TATA Consultancy Services 
Cellno: +91-7276974159 
Mailto: bin...@tc... 
Website: http://www.tcs.com 
=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. Thank you