{"action":"opened","issue":{"url":"https://api.github.com/repos/aowen87/BAR/issues/2684","repository_url":"https://api.github.com/repos/aowen87/BAR","labels_url":"https://api.github.com/repos/aowen87/BAR/issues/2684/labels{/name}","comments_url":"https://api.github.com/repos/aowen87/BAR/issues/2684/comments","events_url":"https://api.github.com/repos/aowen87/BAR/issues/2684/events","html_url":"https://github.com/aowen87/BAR/issues/2684","id":388919838,"node_id":"MDU6SXNzdWUzODg5MTk4Mzg=","number":2684,"title":"Detect and handle degenerate hex zoo elements in transform manager","user":{"login":"aowen87","id":11658578,"node_id":"MDQ6VXNlcjExNjU4NTc4","avatar_url":"https://avatars0.githubusercontent.com/u/11658578?v=4","gravatar_id":"","url":"https://api.github.com/users/aowen87","html_url":"https://github.com/aowen87","followers_url":"https://api.github.com/users/aowen87/followers","following_url":"https://api.github.com/users/aowen87/following{/other_user}","gists_url":"https://api.github.com/users/aowen87/gists{/gist_id}","starred_url":"https://api.github.com/users/aowen87/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/aowen87/subscriptions","organizations_url":"https://api.github.com/users/aowen87/orgs","repos_url":"https://api.github.com/users/aowen87/repos","events_url":"https://api.github.com/users/aowen87/events{/privacy}","received_events_url":"https://api.github.com/users/aowen87/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-12-08T12:55:41Z","updated_at":"2018-12-08T12:55:41Z","closed_at":null,"author_association":"OWNER","body":"This is something that should be optional and off by default because it would involve problem-sized work on every mesh a plugin hands back to VisIt.\r\n\r\nBut, in engineering world, its very common to handle zoo elements as degenerate hexs. For example a 4 node tet is 4 nodes followed by the same 4 nodes. \r\n\r\nAn engineering user had some mixcelltype meshes with all 8-node elements some of which are true hexahedra and some of which are tets stored as degenerate hexs and we don't handle this well.\r\n\r\nSince this is a faily common practice in engineering codes, it probably makes sense to have a transform operation that handles it. We could have controls to enable it (maybe in prefs though it is more like a global database read option). We could also have a data producer indicate its need by using some kind of a convention in the input file which would be easy to define for Silo format but may require effort for various other data formats.\n\n\n\n\n\n-----------------------REDMINE MIGRATION-----------------------\nThis ticket was migrated from Redmine. As such, not all \ninformation was able to be captured in the transition. Below is\na complete record of the original redmine ticket.\n\nTicket number: 3065\nStatus: Pending\nProject: VisIt\nTracker: Feature\nPriority: Normal\nSubject: Detect and handle degenerate hex zoo elements in transform manager\nAssigned to: \nCategory: \nTarget version: \nAuthor: Mark Miller\nStart: 04/10/2018\nDue date: \n% Done: 0\nEstimated time: \nCreated: 04/10/2018 07:07 pm\nUpdated: 05/10/2018 12:54 pm\nLikelihood: \nSeverity: \nFound in version: 2.12.3\nImpact: 2 - Low\nExpected Use: 3 - Occasional\nOS: All\nSupport Group: Any\nDescription:\n This is something that should be optional and off by default because it would involve problem-sized work on every mesh a plugin hands back to VisIt.\r\n\r\nBut, in engineering world, its very common to handle zoo elements as degenerate hexs. For example a 4 node tet is 4 nodes followed by the same 4 nodes. \r\n\r\nAn engineering user had some mix-cell-type meshes with all 8-node elements some of which are true hexahedra and some of which are tets stored as degenerate hexs and we don't handle this well.\r\n\r\nSince this is a faily common practice in engineering codes, it probably makes sense to have a transform operation that handles it. We could have controls to enable it (maybe in prefs though it is more like a global database read option). We could also have a data producer indicate its need by using some kind of a convention in the input file which would be easy to define for Silo format but may require effort for various other data formats.\n\nComments:\n\n"}}
{"actor":{"display_login":"aowen87"}}