{"action":"opened","issue":{"url":"https://api.github.com/repos/Kitware/SMTK/issues/151","labels_url":"https://api.github.com/repos/Kitware/SMTK/issues/151/labels{/name}","comments_url":"https://api.github.com/repos/Kitware/SMTK/issues/151/comments","events_url":"https://api.github.com/repos/Kitware/SMTK/issues/151/events","html_url":"https://github.com/Kitware/SMTK/issues/151","id":69884976,"number":151,"title":"Universal group operator","user":{"login":"yumin","id":234233,"avatar_url":"https://avatars.githubusercontent.com/u/234233?v=3","gravatar_id":"","url":"https://api.github.com/users/yumin","html_url":"https://github.com/yumin","followers_url":"https://api.github.com/users/yumin/followers","following_url":"https://api.github.com/users/yumin/following{/other_user}","gists_url":"https://api.github.com/users/yumin/gists{/gist_id}","starred_url":"https://api.github.com/users/yumin/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/yumin/subscriptions","organizations_url":"https://api.github.com/users/yumin/orgs","repos_url":"https://api.github.com/users/yumin/repos","events_url":"https://api.github.com/users/yumin/events{/privacy}","received_events_url":"https://api.github.com/users/yumin/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-04-21T16:01:48Z","updated_at":"2015-04-21T16:01:48Z","closed_at":null,"body":"We need a universal group operator across all types of sessions. This op will handle various grouping operations, such as create/delete group, modify group (add/remove entities). The group may have different constraints on its membership and its relationship with the entities. We have something in discrete (PR #149), but it is limited to the discrete modeling kernel. This new op should match closely with the smtk group capability. Here is some comment for that PR from @vibraphone \r\n\r\nQUOTE\r\nThere are bits set aside in smtk/model/EntityTypeBits.h to mark groups as partitions or covers but there are no tests to enforce these rules — in part because there are no operators to construct the initial set of groups that form the partition or cover or manipulate the groups after their creation. Note that using groups this way requires 2 levels of groups: a toplevel group with the PARTITION or COVER bit set and child groups that collectively define the membership.\r\n\r\nThe 2-level groups are required so that partitions/covers do not have to encompass all entities in a model manager or session. Instead, operators should just verify that the membership of the toplevel group before and after a group operation is unchanged.\r\nENDQUOTE"}}