{"action":"created","issue":{"url":"https://api.github.com/repos/opesci/inversion/issues/1","repository_url":"https://api.github.com/repos/opesci/inversion","labels_url":"https://api.github.com/repos/opesci/inversion/issues/1/labels{/name}","comments_url":"https://api.github.com/repos/opesci/inversion/issues/1/comments","events_url":"https://api.github.com/repos/opesci/inversion/issues/1/events","html_url":"https://github.com/opesci/inversion/issues/1","id":139546313,"number":1,"title":"Models and data","user":{"login":"mloubout","id":5702350,"avatar_url":"https://avatars.githubusercontent.com/u/5702350?v=3","gravatar_id":"","url":"https://api.github.com/users/mloubout","html_url":"https://github.com/mloubout","followers_url":"https://api.github.com/users/mloubout/followers","following_url":"https://api.github.com/users/mloubout/following{/other_user}","gists_url":"https://api.github.com/users/mloubout/gists{/gist_id}","starred_url":"https://api.github.com/users/mloubout/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mloubout/subscriptions","organizations_url":"https://api.github.com/users/mloubout/orgs","repos_url":"https://api.github.com/users/mloubout/repos","events_url":"https://api.github.com/users/mloubout/events{/privacy}","received_events_url":"https://api.github.com/users/mloubout/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-03-09T11:07:55Z","updated_at":"2016-03-09T11:23:35Z","closed_at":null,"body":"What is the required format of this script for velocity models and data. How should the acquisition geometry be given?"},"comment":{"url":"https://api.github.com/repos/opesci/inversion/issues/comments/194248441","html_url":"https://github.com/opesci/inversion/issues/1#issuecomment-194248441","issue_url":"https://api.github.com/repos/opesci/inversion/issues/1","id":194248441,"user":{"login":"ggorman","id":5394691,"avatar_url":"https://avatars.githubusercontent.com/u/5394691?v=3","gravatar_id":"","url":"https://api.github.com/users/ggorman","html_url":"https://github.com/ggorman","followers_url":"https://api.github.com/users/ggorman/followers","following_url":"https://api.github.com/users/ggorman/following{/other_user}","gists_url":"https://api.github.com/users/ggorman/gists{/gist_id}","starred_url":"https://api.github.com/users/ggorman/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ggorman/subscriptions","organizations_url":"https://api.github.com/users/ggorman/orgs","repos_url":"https://api.github.com/users/ggorman/repos","events_url":"https://api.github.com/users/ggorman/events{/privacy}","received_events_url":"https://api.github.com/users/ggorman/received_events","type":"User","site_admin":false},"created_at":"2016-03-09T11:23:35Z","updated_at":"2016-03-09T11:23:35Z","body":"For the sake of a good abstraction I believe we need a generic class that provides a handle on the model and data. Within this we have to implement/instantiate the appropriate reader for each dataset (possibly pass it into the constructor). This way we can process different datasets without cluttering the top-level API.\r\n\r\nThus - for the sake of interoperability with your code I'm happy for you to tell me what your \"native\" format is. If you give me a 2D dataset along the lines we discussed yesterday then I'll implement a concrete implementation of a reader to illustrate this.\r\n\r\nRelated question - I have a seg y reader in but it currently does not have a good home as it's required in different places. Is this a good home for I/O in general as it is here that we also have to integrate with containers from other data frameworks (e.g. TensorFlow)."}}