{"action":"created","issue":{"url":"https://api.github.com/repos/rupertford/melody/issues/6","repository_url":"https://api.github.com/repos/rupertford/melody","labels_url":"https://api.github.com/repos/rupertford/melody/issues/6/labels{/name}","comments_url":"https://api.github.com/repos/rupertford/melody/issues/6/comments","events_url":"https://api.github.com/repos/rupertford/melody/issues/6/events","html_url":"https://github.com/rupertford/melody/issues/6","id":204887879,"number":6,"title":"Some kind of id for run instances","user":{"login":"jimboid","id":12526320,"avatar_url":"https://avatars.githubusercontent.com/u/12526320?v=3","gravatar_id":"","url":"https://api.github.com/users/jimboid","html_url":"https://github.com/jimboid","followers_url":"https://api.github.com/users/jimboid/followers","following_url":"https://api.github.com/users/jimboid/following{/other_user}","gists_url":"https://api.github.com/users/jimboid/gists{/gist_id}","starred_url":"https://api.github.com/users/jimboid/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jimboid/subscriptions","organizations_url":"https://api.github.com/users/jimboid/orgs","repos_url":"https://api.github.com/users/jimboid/repos","events_url":"https://api.github.com/users/jimboid/events{/privacy}","received_events_url":"https://api.github.com/users/jimboid/received_events","type":"User","site_admin":false},"labels":[{"id":482742859,"url":"https://api.github.com/repos/rupertford/melody/labels/question","name":"question","color":"cc317c","default":true}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":7,"created_at":"2017-02-02T14:24:18Z","updated_at":"2017-02-03T16:47:00Z","closed_at":null,"body":"When working on the domain specific side (ie in the launcher method) it might be helpful if there is some sort of instance identifier passed in that we could use for generating files with names that match a parameter sweep instance. \r\n\r\nThis could in future also be used in the results processing so that the returned information can be tagged against the correct set of parameters (I'm just thinking about passing data around here). Basically this is probably more about readability so one doesn't have to go digging around in input/log files to find the one they might be interested in.\r\n\r\nFurther down the line if things such as asynchronous execution and perhaps even a pretty front end become a desired feature then these id's will form a decent basis for keeping data together.\r\n\r\nI have implemented a kinda rough way of doing this in the gromacs example where I simply generate a random string of numbers as and identifier which I then tack onto file names (to retain raw outputs, as in some programs useful hints come out in the logs) I then append this id back into the results data which I guess can then be used downstream in any results processing.\r\n\r\nThe problem with the method I have implemented is that there is an off chance that the same random string gets generated twice thus overwriting a set of files, I could prevent this with more checking and further regens. But my feeling is that this is cumbersome to code with lots of reinventing the same wheel when we could provide this through melody itself.\r\n\r\nWould this be a massive change? Does this make sense?"},"comment":{"url":"https://api.github.com/repos/rupertford/melody/issues/comments/277298638","html_url":"https://github.com/rupertford/melody/issues/6#issuecomment-277298638","issue_url":"https://api.github.com/repos/rupertford/melody/issues/6","id":277298638,"user":{"login":"rupertford","id":7383165,"avatar_url":"https://avatars.githubusercontent.com/u/7383165?v=3","gravatar_id":"","url":"https://api.github.com/users/rupertford","html_url":"https://github.com/rupertford","followers_url":"https://api.github.com/users/rupertford/followers","following_url":"https://api.github.com/users/rupertford/following{/other_user}","gists_url":"https://api.github.com/users/rupertford/gists{/gist_id}","starred_url":"https://api.github.com/users/rupertford/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rupertford/subscriptions","organizations_url":"https://api.github.com/users/rupertford/orgs","repos_url":"https://api.github.com/users/rupertford/repos","events_url":"https://api.github.com/users/rupertford/events{/privacy}","received_events_url":"https://api.github.com/users/rupertford/received_events","type":"User","site_admin":false},"created_at":"2017-02-03T16:46:59Z","updated_at":"2017-02-03T16:46:59Z","body":"OK, we're coming to a consensus. Unless there are any objections I'll go with strings \"1\", \"2\" etc but these are just unique identifiers and the values could change in the future e.g. we might decide to go with a uuid(), so user code should not attach any meaning to the strings. I'll make this clear in the documentation that is ... err ... coming.\r\n"}}
{"actor":{"display_login":"rupertford"}}