{"action":"closed","issue":{"url":"https://api.github.com/repos/anujg1991/stringMLST/issues/7","repository_url":"https://api.github.com/repos/anujg1991/stringMLST","labels_url":"https://api.github.com/repos/anujg1991/stringMLST/issues/7/labels{/name}","comments_url":"https://api.github.com/repos/anujg1991/stringMLST/issues/7/comments","events_url":"https://api.github.com/repos/anujg1991/stringMLST/issues/7/events","html_url":"https://github.com/anujg1991/stringMLST/issues/7","id":178457779,"number":7,"title":"Given 'random' ST type when no k-mers match any allele","user":{"login":"Takadonet","id":64732,"avatar_url":"https://avatars.githubusercontent.com/u/64732?v=3","gravatar_id":"","url":"https://api.github.com/users/Takadonet","html_url":"https://github.com/Takadonet","followers_url":"https://api.github.com/users/Takadonet/followers","following_url":"https://api.github.com/users/Takadonet/following{/other_user}","gists_url":"https://api.github.com/users/Takadonet/gists{/gist_id}","starred_url":"https://api.github.com/users/Takadonet/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Takadonet/subscriptions","organizations_url":"https://api.github.com/users/Takadonet/orgs","repos_url":"https://api.github.com/users/Takadonet/repos","events_url":"https://api.github.com/users/Takadonet/events{/privacy}","received_events_url":"https://api.github.com/users/Takadonet/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2016-09-21T20:45:17Z","updated_at":"2016-10-19T13:25:26Z","closed_at":"2016-10-19T13:25:25Z","body":"When running the Strep pneu against the Listeria Mono. to see what a failure looks like I get the following result.\r\n\r\nNo k-mer matches were found for the sample . strain_R1_001.fastq and strain_R2_001.fastq.  Probable cause of the error:  low quality data/too many N's in the data\r\nSample  ST      Time\r\nstrain     344     15.88 \r\n\r\n\r\nNoticed in the code that the No k-mer match statement was followed by exit statement but it was commented out. I think reporting back to the user with N/A or no result would be best instead of just exiting . If someone is running in batch mode or combining individual results together, its very usefully to know which strain actually had no result. If they do not show up at all, then no idea if the software failed or because no k-mer found.\r\n"}}
{"actor":{"display_login":"ar0ch"}}