{"action":"opened","issue":{"url":"https://api.github.com/repos/idaholab/moose/issues/7130","repository_url":"https://api.github.com/repos/idaholab/moose","labels_url":"https://api.github.com/repos/idaholab/moose/issues/7130/labels{/name}","comments_url":"https://api.github.com/repos/idaholab/moose/issues/7130/comments","events_url":"https://api.github.com/repos/idaholab/moose/issues/7130/events","html_url":"https://github.com/idaholab/moose/issues/7130","id":157816619,"number":7130,"title":"Improve petsc interface","user":{"login":"WilkAndy","id":6676821,"avatar_url":"https://avatars.githubusercontent.com/u/6676821?v=3","gravatar_id":"","url":"https://api.github.com/users/WilkAndy","html_url":"https://github.com/WilkAndy","followers_url":"https://api.github.com/users/WilkAndy/followers","following_url":"https://api.github.com/users/WilkAndy/following{/other_user}","gists_url":"https://api.github.com/users/WilkAndy/gists{/gist_id}","starred_url":"https://api.github.com/users/WilkAndy/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/WilkAndy/subscriptions","organizations_url":"https://api.github.com/users/WilkAndy/orgs","repos_url":"https://api.github.com/users/WilkAndy/repos","events_url":"https://api.github.com/users/WilkAndy/events{/privacy}","received_events_url":"https://api.github.com/users/WilkAndy/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-06-01T03:33:52Z","updated_at":"2016-06-01T03:33:52Z","closed_at":null,"body":"Tagging @fdkong\r\n\r\n### Description of the enhancement or error report\r\n\r\nAt present i think that we can view all of petsc's options.  However, it would be great if we could:\r\n\r\n1. see what options are actually passed from moose to petsc\r\n2. have petsc crash or complain if the arguments passed are invalid\r\n3. be able to view the petsc options that petsc is actually using\r\n4. be able to list these things easily using myapp-opt --petsc_options (or whatever)\r\n5. myapp-opt -h not listing a whole lot of wierdo petsc stuff before the moose stuff.\r\n\r\nPerhaps all these are possible right now, but in the past i have been confused about what options petsc was receiving and using.\r\n\r\n### Rationale for the enhancement or information for reproducing the error\r\n\r\nImprove usability of moose in real-life applications (and decrease Andy's confusion)\r\n\r\n### Identified impact\r\n(i.e. Internal object changes, limited interface changes, public API change, or a list of specific applications impacted)\r\n\r\nchanges the output of moose in the obvious way.\r\n"}}
{"actor":{"display_login":"WilkAndy"}}