Skip to content
This repository has been archived by the owner on Nov 3, 2021. It is now read-only.

experimental channels in measurement group not updated after removing with udefelem #1658

Open
yimli opened this issue Jul 13, 2021 · 2 comments

Comments

@yimli
Copy link
Collaborator

yimli commented Jul 13, 2021

Removing a channel with udefelem does not remove the channel information from the measurement group data source. Pool can not be restarted due to this issue afterwards. This issue can be reproduced at two places.

Example 1: A spock example can be seen as follows. After removing it, channel ct08 is still shown in the listed measurement group.

Door_test_1 [10]: lsmeas
  Active        Name   Timer Experim. channels       
 -------- ---------- ------- ------------------------
            mntgrp01    ct01 ct01, ct02, ct03, ct04  
    *       mntgrp02    ct01 ct01, ct02, ct03, ct04  
            mntgrp03    ct01 ct01, ct08              

Door_test_1 [11]: udefelem ct08

Door_test_1 [12]: lsmeas
  Active        Name   Timer Experim. channels       
 -------- ---------- ------- ------------------------
            mntgrp01    ct01 ct01, ct02, ct03, ct04  
    *       mntgrp02    ct01 ct01, ct02, ct03, ct04  
            mntgrp03    ct01 ct01, ct08      

Example 2:

  • same as example 1, udefelem a channel in spock
  • open expconf
  • the deleted channel is still listed in the corresponding mntgrp. If you try to delete it manually with "Remove Item", it will refuse and cause key error(can't find the channel in the available channels)
@reszelaz
Copy link
Collaborator

Hi @yimli,
Thanks for the detailed report. I think it should be much better handled with #1615. It won't remove the channel from the measurement group configuration automatically, but will prevent you from undefining the element. Then you would need to remove the channel from the measurement group manually. I think it is a reasonable solution to your problem. It would be great if you could test this PR. Many thanks!

@yimli
Copy link
Collaborator Author

yimli commented Jul 14, 2021

Thanks for your comment! I have tested it and it works well to solve this issue!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants