Experimental channels organized in instruments are not correclty organized in the corresponding NeXus file defined by ScanFile.
If we have 3 Sardana elements (one motor, one ct and one zerod) and we set them from spock in the same instrument:
mot41.Instrument = '/ins1' ct34.Instrument = '/ins1' zerod33.Instrument = '/ins1'
and we set the scanFile:
senv ScanFile scanset.h5
We launch a scan and then we check the data stored in scanset.h5. The data of mot41, ct34 and zerod33 should be organized in a group named 'ins1' inside the hdf5. What we observe is that only the motor data of mot41, is inside the group 'ins1'.
The data about ct34 and zerod33 can only be found in the group containing the data of all elements (in flat); group called 'measurement'.
Moreover we have observed that restarting the Pool, the association of zerod33 to the Instrument '/ins1' disappears (this can be observed in jive). This association is not lost in the case of ct34 and in the case of mot41.
This observation has been done with current develop code
commit: caf6f97bd0ff9a0a
in machine suse121 64 bits
Python 2.7.2
ipython 0.11
Hi Marc,
We reproduced the behavior. You must to restart the Pool, MacroServer, Spock when:
Create a new instrument
Change an element (motor, counter, etc.) from one instrument to another.
If you don't restart the system (Pool, MacroServer, Spock) the changes will not have effect.
https://sourceforge.net/p/sardana/wiki/Howto-GUI_creation/
For that reason we will reject this ticket.
You can create a feature to apply the changes without to restart the system.
Best regards,
Roberto
Hi,
I agree with the rejection of this ticket, but I wonder (haven't checked) if the need for restarting the MS+Pool is documented somewhere. If not, I suggest to make a patch to the docs to mention the two cases (maybe in the docs related to instrument)
Ok, we reopen the ticket till we check the documentation.
The problem described in this ticket was already reported by Teresa in [#218], so I'm rejecting this one.
Since the concept of the Instruments is not documented at all, I have created a feature request for that [#396].
The information on the current need to restart the Sardana system in order to reflect the changes could be documented there as well (if not fixed earlier).
Related
OLD Tickets: #218
OLD Tickets: #396