{"action":"created","issue":{"url":"https://api.github.com/repos/westpa/westpa/issues/26","repository_url":"https://api.github.com/repos/westpa/westpa","labels_url":"https://api.github.com/repos/westpa/westpa/issues/26/labels{/name}","comments_url":"https://api.github.com/repos/westpa/westpa/issues/26/comments","events_url":"https://api.github.com/repos/westpa/westpa/issues/26/events","html_url":"https://github.com/westpa/westpa/issues/26","id":181585110,"number":26,"title":"More specific error handling, in general","user":{"login":"ajoshpratt","id":9011779,"avatar_url":"https://avatars.githubusercontent.com/u/9011779?v=3","gravatar_id":"","url":"https://api.github.com/users/ajoshpratt","html_url":"https://github.com/ajoshpratt","followers_url":"https://api.github.com/users/ajoshpratt/followers","following_url":"https://api.github.com/users/ajoshpratt/following{/other_user}","gists_url":"https://api.github.com/users/ajoshpratt/gists{/gist_id}","starred_url":"https://api.github.com/users/ajoshpratt/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ajoshpratt/subscriptions","organizations_url":"https://api.github.com/users/ajoshpratt/orgs","repos_url":"https://api.github.com/users/ajoshpratt/repos","events_url":"https://api.github.com/users/ajoshpratt/events{/privacy}","received_events_url":"https://api.github.com/users/ajoshpratt/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/westpa/westpa/labels/enhancement","name":"enhancement","color":"84b6eb"}],"state":"open","locked":false,"assignee":{"login":"ajoshpratt","id":9011779,"avatar_url":"https://avatars.githubusercontent.com/u/9011779?v=3","gravatar_id":"","url":"https://api.github.com/users/ajoshpratt","html_url":"https://github.com/ajoshpratt","followers_url":"https://api.github.com/users/ajoshpratt/followers","following_url":"https://api.github.com/users/ajoshpratt/following{/other_user}","gists_url":"https://api.github.com/users/ajoshpratt/gists{/gist_id}","starred_url":"https://api.github.com/users/ajoshpratt/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ajoshpratt/subscriptions","organizations_url":"https://api.github.com/users/ajoshpratt/orgs","repos_url":"https://api.github.com/users/ajoshpratt/repos","events_url":"https://api.github.com/users/ajoshpratt/events{/privacy}","received_events_url":"https://api.github.com/users/ajoshpratt/received_events","type":"User","site_admin":false},"assignees":[{"login":"ajoshpratt","id":9011779,"avatar_url":"https://avatars.githubusercontent.com/u/9011779?v=3","gravatar_id":"","url":"https://api.github.com/users/ajoshpratt","html_url":"https://github.com/ajoshpratt","followers_url":"https://api.github.com/users/ajoshpratt/followers","following_url":"https://api.github.com/users/ajoshpratt/following{/other_user}","gists_url":"https://api.github.com/users/ajoshpratt/gists{/gist_id}","starred_url":"https://api.github.com/users/ajoshpratt/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ajoshpratt/subscriptions","organizations_url":"https://api.github.com/users/ajoshpratt/orgs","repos_url":"https://api.github.com/users/ajoshpratt/repos","events_url":"https://api.github.com/users/ajoshpratt/events{/privacy}","received_events_url":"https://api.github.com/users/ajoshpratt/received_events","type":"User","site_admin":false}],"milestone":null,"comments":2,"created_at":"2016-10-07T04:54:09Z","updated_at":"2016-10-07T13:19:21Z","closed_at":null,"body":"Hi all,\r\n\r\nI've started working on a branch, https://github.com/westpa/westpa/tree/error_handling, to build in an error module that can we call to in order to throw cleaner error messages when a simulation fails for whatever reason.  I'd call this work exploratory in nature, thus far.\r\n\r\nIt suppresses the normal python error output (useful for debugging and development/developers only), and supplies its own list of kwarg formatted strings.  To add new error messages, we'd simply add them into the errors.py file, import into the relevant file, and call report_error/report_segment_error.\r\n\r\nI've tried to anticipate where a simulation normally fails, and why, and provide specific feedback as to what the user may want to check (as well as important paths).  For the executable propagator, it hooks in to the standard error stream and sends the last 10 lines or so into the main log file.  It also (currently) suppresses all 'duplicate' errors, but I want to put in the ability to change this.\r\n\r\n* NOTE: Catching stderr has the side effect of forcing us to write stderr and stdout from a segment into the seglog file at different times, but I think the tradeoff is worth it in terms of debugging simulations.\r\n\r\nAttached is an example of the output it might produce.  I've taken a test simulation, and made my runseg.sh fail out (by calling the wrong binary).\r\n\r\nI started with what I think are the most common failure points for people, but I want to expand this further.  Any feedback at this stage would be appreciated (disagreements on architecture, error handling, etc; there's a little nastiness in how the pcoord_loader is calling this, at the moment, to get it to play nice with bstates/istates and the regular segments that I'd like to rewrite).\r\n\r\n[west.txt](https://github.com/westpa/westpa/files/515257/west.txt)\r\n\r\nAdam\r\n"},"comment":{"url":"https://api.github.com/repos/westpa/westpa/issues/comments/252249761","html_url":"https://github.com/westpa/westpa/issues/26#issuecomment-252249761","issue_url":"https://api.github.com/repos/westpa/westpa/issues/26","id":252249761,"user":{"login":"mczwier","id":2816036,"avatar_url":"https://avatars.githubusercontent.com/u/2816036?v=3","gravatar_id":"","url":"https://api.github.com/users/mczwier","html_url":"https://github.com/mczwier","followers_url":"https://api.github.com/users/mczwier/followers","following_url":"https://api.github.com/users/mczwier/following{/other_user}","gists_url":"https://api.github.com/users/mczwier/gists{/gist_id}","starred_url":"https://api.github.com/users/mczwier/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mczwier/subscriptions","organizations_url":"https://api.github.com/users/mczwier/orgs","repos_url":"https://api.github.com/users/mczwier/repos","events_url":"https://api.github.com/users/mczwier/events{/privacy}","received_events_url":"https://api.github.com/users/mczwier/received_events","type":"User","site_admin":false},"created_at":"2016-10-07T13:19:21Z","updated_at":"2016-10-07T13:19:21Z","body":"Though \"rogue sed command\" is the best phrase/band name I've heard in a\nlong time, I'm inclined not to impose a character limit. Line breaks make\nit harder to parse errors programmatically for those users inclined to do\nso (sed proficiency notwithstanding). That's just my opinion though. Others\ncan/should weigh in as well.\n\nOn Thu, Oct 6, 2016 at 11:55 PM, Adam J. Pratt <notifications@github.com>\nwrote:\n\n> Also: I haven't bothered with formatting messages to keep the lines within\n> a character limit, but any feedback on that would be appreciated (stick\n> with 80? Go with 1000? Remove all line breaks with a rogue sed command?)\n>\n> —\n> You are receiving this because you are subscribed to this thread.\n> Reply to this email directly, view it on GitHub\n> <https://github.com/westpa/westpa/issues/26#issuecomment-252152924>, or mute\n> the thread\n> <https://github.com/notifications/unsubscribe-auth/ACr4JNjOPo09XN-EHK2ztCeaekXYTxNdks5qxdC5gaJpZM4KQrOV>\n> .\n>\n"}}
{"actor":{"display_login":"mczwier"}}