{"action":"created","issue":{"url":"https://api.github.com/repos/ga4gh/benchmarking-tools/issues/7","labels_url":"https://api.github.com/repos/ga4gh/benchmarking-tools/issues/7/labels{/name}","comments_url":"https://api.github.com/repos/ga4gh/benchmarking-tools/issues/7/comments","events_url":"https://api.github.com/repos/ga4gh/benchmarking-tools/issues/7/events","html_url":"https://github.com/ga4gh/benchmarking-tools/issues/7","id":115193165,"number":7,"title":"Can we call a \"superlocus\" a \"window\"?","user":{"login":"kghosesbg","id":6299530,"avatar_url":"https://avatars.githubusercontent.com/u/6299530?v=3","gravatar_id":"","url":"https://api.github.com/users/kghosesbg","html_url":"https://github.com/kghosesbg","followers_url":"https://api.github.com/users/kghosesbg/followers","following_url":"https://api.github.com/users/kghosesbg/following{/other_user}","gists_url":"https://api.github.com/users/kghosesbg/gists{/gist_id}","starred_url":"https://api.github.com/users/kghosesbg/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kghosesbg/subscriptions","organizations_url":"https://api.github.com/users/kghosesbg/orgs","repos_url":"https://api.github.com/users/kghosesbg/repos","events_url":"https://api.github.com/users/kghosesbg/events{/privacy}","received_events_url":"https://api.github.com/users/kghosesbg/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2015-11-05T02:05:44Z","updated_at":"2015-11-18T17:10:48Z","closed_at":null,"body":"From how a \"superlocus\" was defined to me during the NY meeting, I think the traditional term \"window\" may be more appropriate. The term \"window\" is a very standard term for any one doing serial processing and, to me, is more to the point than superlocus. Thanks!"},"comment":{"url":"https://api.github.com/repos/ga4gh/benchmarking-tools/issues/comments/157781453","html_url":"https://github.com/ga4gh/benchmarking-tools/issues/7#issuecomment-157781453","issue_url":"https://api.github.com/repos/ga4gh/benchmarking-tools/issues/7","id":157781453,"user":{"login":"jzook","id":2439798,"avatar_url":"https://avatars.githubusercontent.com/u/2439798?v=3","gravatar_id":"","url":"https://api.github.com/users/jzook","html_url":"https://github.com/jzook","followers_url":"https://api.github.com/users/jzook/followers","following_url":"https://api.github.com/users/jzook/following{/other_user}","gists_url":"https://api.github.com/users/jzook/gists{/gist_id}","starred_url":"https://api.github.com/users/jzook/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jzook/subscriptions","organizations_url":"https://api.github.com/users/jzook/orgs","repos_url":"https://api.github.com/users/jzook/repos","events_url":"https://api.github.com/users/jzook/events{/privacy}","received_events_url":"https://api.github.com/users/jzook/received_events","type":"User","site_admin":false},"created_at":"2015-11-18T17:10:48Z","updated_at":"2015-11-18T17:10:48Z","body":"Do you think we could be a bit more specific about the intention and still\ninclude all 3 tools?  Perhaps: \"a set of variants that intends to fully\ndescribe the variation within a contiguous reference region that may\ncontain complex variation with different representations.\"  It might also\nbe nice to have examples of more specifically how each of the tools defines\nit.\n\n\nOn Wed, Nov 18, 2015 at 11:33 AM Peter Krusche <notifications@github.com>\nwrote:\n\n> I am in favour of keeping superlocus also. We could define the superlocus\n> variants as a set of variants that intends to fully describe the variation\n> within a contiguous reference region. This should be general enough to\n> cover @bioinformed <https://github.com/bioinformed>'s maximal superloci,\n> hap.py's haplotype blocks and variant sets between sync points in vcfeval?\n>\n> —\n> Reply to this email directly or view it on GitHub\n> <https://github.com/ga4gh/benchmarking-tools/issues/7#issuecomment-157769724>\n> .\n>\n"}}