{"action":"created","issue":{"url":"https://api.github.com/repos/StrikeNP/trac_test/issues/704","repository_url":"https://api.github.com/repos/StrikeNP/trac_test","labels_url":"https://api.github.com/repos/StrikeNP/trac_test/issues/704/labels{/name}","comments_url":"https://api.github.com/repos/StrikeNP/trac_test/issues/704/comments","events_url":"https://api.github.com/repos/StrikeNP/trac_test/issues/704/events","html_url":"https://github.com/StrikeNP/trac_test/issues/704","id":330468288,"node_id":"MDU6SXNzdWUzMzA0NjgyODg=","number":704,"title":"Design the port of plotgen to python (Trac #704)","user":{"login":"StrikeNP","id":2577059,"node_id":"MDQ6VXNlcjI1NzcwNTk=","avatar_url":"https://avatars0.githubusercontent.com/u/2577059?v=4","gravatar_id":"","url":"https://api.github.com/users/StrikeNP","html_url":"https://github.com/StrikeNP","followers_url":"https://api.github.com/users/StrikeNP/followers","following_url":"https://api.github.com/users/StrikeNP/following{/other_user}","gists_url":"https://api.github.com/users/StrikeNP/gists{/gist_id}","starred_url":"https://api.github.com/users/StrikeNP/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/StrikeNP/subscriptions","organizations_url":"https://api.github.com/users/StrikeNP/orgs","repos_url":"https://api.github.com/users/StrikeNP/repos","events_url":"https://api.github.com/users/StrikeNP/events{/privacy}","received_events_url":"https://api.github.com/users/StrikeNP/received_events","type":"User","site_admin":false},"labels":[{"id":958019852,"node_id":"MDU6TGFiZWw5NTgwMTk4NTI=","url":"https://api.github.com/repos/StrikeNP/trac_test/labels/Migrated%20from%20Trac","name":"Migrated from Trac","color":"FFFFFF","default":false},{"id":958019578,"node_id":"MDU6TGFiZWw5NTgwMTk1Nzg=","url":"https://api.github.com/repos/StrikeNP/trac_test/labels/enhancement","name":"enhancement","color":"a2eeef","default":true},{"id":958126856,"node_id":"MDU6TGFiZWw5NTgxMjY4NTY=","url":"https://api.github.com/repos/StrikeNP/trac_test/labels/nieznan3@uwm.edu","name":"nieznan3@uwm.edu","color":"FFFFFF","default":false},{"id":958019856,"node_id":"MDU6TGFiZWw5NTgwMTk4NTY=","url":"https://api.github.com/repos/StrikeNP/trac_test/labels/post_processing","name":"post_processing","color":"FFFFFF","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":{"url":"https://api.github.com/repos/StrikeNP/trac_test/milestones/10","html_url":"https://github.com/StrikeNP/trac_test/milestone/10","labels_url":"https://api.github.com/repos/StrikeNP/trac_test/milestones/10/labels","id":3408887,"node_id":"MDk6TWlsZXN0b25lMzQwODg4Nw==","number":10,"title":"Improve Plotgen","description":null,"creator":{"login":"StrikeNP","id":2577059,"node_id":"MDQ6VXNlcjI1NzcwNTk=","avatar_url":"https://avatars0.githubusercontent.com/u/2577059?v=4","gravatar_id":"","url":"https://api.github.com/users/StrikeNP","html_url":"https://github.com/StrikeNP","followers_url":"https://api.github.com/users/StrikeNP/followers","following_url":"https://api.github.com/users/StrikeNP/following{/other_user}","gists_url":"https://api.github.com/users/StrikeNP/gists{/gist_id}","starred_url":"https://api.github.com/users/StrikeNP/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/StrikeNP/subscriptions","organizations_url":"https://api.github.com/users/StrikeNP/orgs","repos_url":"https://api.github.com/users/StrikeNP/repos","events_url":"https://api.github.com/users/StrikeNP/events{/privacy}","received_events_url":"https://api.github.com/users/StrikeNP/received_events","type":"User","site_admin":false},"open_issues":11,"closed_issues":40,"state":"open","created_at":"2018-06-07T20:05:39Z","updated_at":"2018-06-09T23:46:32Z","due_on":null,"closed_at":null},"comments":2,"created_at":"2018-06-07T23:18:51Z","updated_at":"2018-06-09T23:46:41Z","closed_at":null,"author_association":"OWNER","body":"We are porting plotgen's matlab scripts to python!\n\nThis ticket is purely planning porting plotgen to python.\n1. Are there any major changes needed, or is it primarily syntax?\n1. There will be no streamlining or refactoring, purely porting.  If any portions of code could be improved, make a note in ticket:702.\n1. Still using the original perl wrapper, what needs to be done to the interface between perl and matlab to make it work with python?\n1. Where will we be locating the new Plotgen?  Its own repository or within CLUBB?\n1. What else do we need to be aware of?\n\nSome resources for Matlab to Python conversion:\nhttp://wiki.scipy.org/NumPy_for_Matlab_Users\n\nAttachments:\n\n\nMigrated from http://carson.math.uwm.edu/trac/clubb/ticket/704\n```json\n{\n    \"status\": \"new\", \n    \"changetime\": \"2015-05-28T17:06:59\", \n    \"description\": \"We are porting plotgen's matlab scripts to python!\\n\\nThis ticket is purely planning porting plotgen to python.\\n1. Are there any major changes needed, or is it primarily syntax?\\n1. There will be no streamlining or refactoring, purely porting.  If any portions of code could be improved, make a note in ticket:702.\\n1. Still using the original perl wrapper, what needs to be done to the interface between perl and matlab to make it work with python?\\n1. Where will we be locating the new Plotgen?  Its own repository or within CLUBB?\\n1. What else do we need to be aware of?\\n\\nSome resources for Matlab to Python conversion:\\nhttp://wiki.scipy.org/NumPy_for_Matlab_Users\", \n    \"reporter\": \"nieznan3@uwm.edu\", \n    \"cc\": \"vlarson@uwm.edu, raut@uwm.edu, weberjk@uwm.edu\", \n    \"resolution\": \"\", \n    \"_ts\": \"1432832819272216\", \n    \"component\": \"post_processing\", \n    \"summary\": \"Design the port of plotgen to python\", \n    \"priority\": \"major\", \n    \"keywords\": \"plotgen\", \n    \"time\": \"2014-06-16T23:32:48\", \n    \"milestone\": \"Improve Plotgen\", \n    \"owner\": \"nieznan3@uwm.edu\", \n    \"type\": \"enhancement\"\n}\n```\n"},"comment":{"url":"https://api.github.com/repos/StrikeNP/trac_test/issues/comments/396006926","html_url":"https://github.com/StrikeNP/trac_test/issues/704#issuecomment-396006926","issue_url":"https://api.github.com/repos/StrikeNP/trac_test/issues/704","id":396006926,"node_id":"MDEyOklzc3VlQ29tbWVudDM5NjAwNjkyNg==","user":{"login":"StrikeNP","id":2577059,"node_id":"MDQ6VXNlcjI1NzcwNTk=","avatar_url":"https://avatars0.githubusercontent.com/u/2577059?v=4","gravatar_id":"","url":"https://api.github.com/users/StrikeNP","html_url":"https://github.com/StrikeNP","followers_url":"https://api.github.com/users/StrikeNP/followers","following_url":"https://api.github.com/users/StrikeNP/following{/other_user}","gists_url":"https://api.github.com/users/StrikeNP/gists{/gist_id}","starred_url":"https://api.github.com/users/StrikeNP/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/StrikeNP/subscriptions","organizations_url":"https://api.github.com/users/StrikeNP/orgs","repos_url":"https://api.github.com/users/StrikeNP/repos","events_url":"https://api.github.com/users/StrikeNP/events{/privacy}","received_events_url":"https://api.github.com/users/StrikeNP/received_events","type":"User","site_admin":false},"created_at":"2018-06-09T23:46:41Z","updated_at":"2018-06-09T23:46:41Z","author_association":"OWNER","body":"Trac update at 2014/06/24 at 17:35\n\nvlarson@uwm.edu commented:\n\nReplying to [comment:2 nieznan3@…]:\n> 4.  The more I think about it, the more it makes sense to locate the new plotgen within the CLUBB repository, where it always has been.  This means all the old version history will still be there and easily available for when we get to the step of streamlining plotgen.  I'd like to create a folder under branches/ for development of plotgen as, until we finish the first part of the conversion, it will not actually be functional code.\n\nOK, sounds good.\n\nUsually we just do development on the trunk as long as it doesn't break anything.\n\nWhat will happen to the current version of plotgen when the new version is ready to release?  I was assuming that we would replace the MATLAB files in source:clubb/trunk/postprocessing/plotgen with python equivalents.  Could we just add new python files to that directory, and when they are ready, svn delete the MATLAB files?  I believe that will still save the history of the MATLAB files, even if they don't appear in a current checkout of the repository.\n\n"}}
{"actor":{"display_login":"StrikeNP"}}