{"action":"created","issue":{"url":"https://api.github.com/repos/SteveDoyle2/pyNastran/issues/308","repository_url":"https://api.github.com/repos/SteveDoyle2/pyNastran","labels_url":"https://api.github.com/repos/SteveDoyle2/pyNastran/issues/308/labels{/name}","comments_url":"https://api.github.com/repos/SteveDoyle2/pyNastran/issues/308/comments","events_url":"https://api.github.com/repos/SteveDoyle2/pyNastran/issues/308/events","html_url":"https://github.com/SteveDoyle2/pyNastran/issues/308","id":159750197,"number":308,"title":"MSC Nastran 2016, HDF5, reader for PyNastran","user":{"login":"saullocastro","id":3889819,"avatar_url":"https://avatars2.githubusercontent.com/u/3889819?v=4","gravatar_id":"","url":"https://api.github.com/users/saullocastro","html_url":"https://github.com/saullocastro","followers_url":"https://api.github.com/users/saullocastro/followers","following_url":"https://api.github.com/users/saullocastro/following{/other_user}","gists_url":"https://api.github.com/users/saullocastro/gists{/gist_id}","starred_url":"https://api.github.com/users/saullocastro/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/saullocastro/subscriptions","organizations_url":"https://api.github.com/users/saullocastro/orgs","repos_url":"https://api.github.com/users/saullocastro/repos","events_url":"https://api.github.com/users/saullocastro/events{/privacy}","received_events_url":"https://api.github.com/users/saullocastro/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":7,"created_at":"2016-06-11T01:55:25Z","updated_at":"2017-12-17T04:31:08Z","closed_at":"2017-07-11T05:37:03Z","author_association":"CONTRIBUTOR","body":"MSC Nastran 2016 started using the HDF5 format as a new output option (Nastran saves it as a `.h5` file)\n\nI tested it and it is very straightforward to implement a `.h5` reader using PYTables (http://www.pytables.org/index.html).\n\nFor example, to read the output of a node diplacement one should do something like:\n\n```\nimport tables\n\nh5 = tables.open_file('nastran_output.h5')\nh5.NASTRAN.RESULT.NODAL.DISPLACEMENT[0]\n```\n\nto get something like:\n\n```\n[nodeid, [T1, T2, T3, R1, R2, R3], subcase index]\n```\n\nI am suggesting this as a new line of development in PyNastran. What do you guys think?\n"},"comment":{"url":"https://api.github.com/repos/SteveDoyle2/pyNastran/issues/comments/352231251","html_url":"https://github.com/SteveDoyle2/pyNastran/issues/308#issuecomment-352231251","issue_url":"https://api.github.com/repos/SteveDoyle2/pyNastran/issues/308","id":352231251,"user":{"login":"SteveDoyle2","id":1059417,"avatar_url":"https://avatars1.githubusercontent.com/u/1059417?v=4","gravatar_id":"","url":"https://api.github.com/users/SteveDoyle2","html_url":"https://github.com/SteveDoyle2","followers_url":"https://api.github.com/users/SteveDoyle2/followers","following_url":"https://api.github.com/users/SteveDoyle2/following{/other_user}","gists_url":"https://api.github.com/users/SteveDoyle2/gists{/gist_id}","starred_url":"https://api.github.com/users/SteveDoyle2/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/SteveDoyle2/subscriptions","organizations_url":"https://api.github.com/users/SteveDoyle2/orgs","repos_url":"https://api.github.com/users/SteveDoyle2/repos","events_url":"https://api.github.com/users/SteveDoyle2/events{/privacy}","received_events_url":"https://api.github.com/users/SteveDoyle2/received_events","type":"User","site_admin":false},"created_at":"2017-12-17T04:31:08Z","updated_at":"2017-12-17T04:31:08Z","author_association":"OWNER","body":"Your module is very cool.  I'm very interested to see how our packages can work together.\r\n\r\nI'm not sure about the best way to interface (e.g., a separate package or just a single one), but that's solvable.  I guess backing up a little, as is, there is:\r\n  1. BDF and OP2 capability that is standalone\r\n  2. examples\r\n  3. some converters that I find useful (e.g., STL to BDF)\r\n  4. a GUI capability that requires the previous three and implements it's own vectorized BDF reader (which would be better using your package).\r\n\r\nSo if pyNastran was split, it's could be 1/2 or 1/2/3.  If it's 1 or 1/2, that might be annoying to install.  I'd also like to avoid circular dependencies between our packages, so either we just merge them or split up pyNastran.  Thoughts?\r\n\r\nRegarding using your package, I guess my first question is do you have some examples?  I'm tried to figure out how to use it (e.g., read a BDF, get the XYZs from the nodes, modify them and write the new deck).\r\n\r\nAlso, I saw you have a BDF_LINES entry.  Is that supposed to be the full deck or just the unparsed data?  Is that updated when you modify data and write it back out?"}}
{"actor":{"display_login":"SteveDoyle2"}}