{"action":"opened","issue":{"url":"https://api.github.com/repos/aowen87/TicketTester/issues/2657","repository_url":"https://api.github.com/repos/aowen87/TicketTester","labels_url":"https://api.github.com/repos/aowen87/TicketTester/issues/2657/labels{/name}","comments_url":"https://api.github.com/repos/aowen87/TicketTester/issues/2657/comments","events_url":"https://api.github.com/repos/aowen87/TicketTester/issues/2657/events","html_url":"https://github.com/aowen87/TicketTester/issues/2657","id":390074587,"node_id":"MDU6SXNzdWUzOTAwNzQ1ODc=","number":2657,"title":"Issues with big quads","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-12T05:48:48Z","updated_at":"2018-12-12T05:48:48Z","closed_at":null,"author_association":"OWNER","body":"I've attached data, session file to this ticket to demonstrate issues with big quads (e.g. quads that are way bigger than a pixel). See attached picture. This is a case where all the nodal values are zero except the center value which is 10.0. !{width:300px}big_quads.jpg! In the attached picture, the cases are, left to right... Left: Big quads where VisIt decides diagonals, Middle: Big quads but re-interpolated onto a finer mesh to show what the underlying piecewise linear function **should** look like Right: Big quads where I decided the diagonals. On each picture, I show pseudocolor in gray scale and contours in red. Note following artifacts of left image... * The pc shading is assymetric even though the underlying function is symmetric * The contours don't even don't even extend into half of all the quads. Note that contours in left image more closely match correct image (middle) for contours closer to the middle but less closely match for controus near the outside. OTOH, the reverse is true for the right image contours. Mark\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: 2904\nStatus: Pending\nProject: VisIt\nTracker: Bug\nPriority: High\nSubject: Issues with big quads\nAssigned to: \nCategory: \nTarget version: \nAuthor: Mark Miller\nStart: 08/30/2017\nDue date: \n% Done: 0\nEstimated time: \nCreated: 08/30/2017 06:38 pm\nUpdated: 09/19/2017 06:52 pm\nLikelihood: 3 - Occasional\nSeverity: 4 - Crash / Wrong Results\nFound in version: 2.12.3\nImpact: \nExpected Use: \nOS: All\nSupport Group: Any\nDescription:\n I've attached data, session file to this ticket to demonstrate issues with big quads (e.g. quads that are way bigger than a pixel). See attached picture. This is a case where all the nodal values are zero except the center value which is 10.0. !{width:300px}big_quads.jpg! In the attached picture, the cases are, left to right... Left: Big quads where VisIt decides diagonals, Middle: Big quads but re-interpolated onto a finer mesh to show what the underlying piecewise linear function **should** look like Right: Big quads where I decided the diagonals. On each picture, I show pseudocolor in gray scale and contours in red. Note following artifacts of left image... * The pc shading is assymetric even though the underlying function is symmetric * The contours don't even don't even extend into half of all the quads. Note that contours in left image more closely match correct image (middle) for contours closer to the middle but less closely match for controus near the outside. OTOH, the reverse is true for the right image contours. Mark\n\nComments:\n\n"}}
{"actor":{"display_login":"aowen87"}}