CTETRA, CHEXA, CPENTA with varying number of midnodes are not handled properly

umvarma / pynastran

Automatically exported from code.google.com/p/pynastran

1 stars 0 forks source link

CTETRA, CHEXA, CPENTA with varying number of midnodes are not handled properly #140

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago


Identification numbers of connected grid points can be Integer >= 0 or blank.
The blank case is not properly handled in pyNastran.

Original issue reported on code.google.com by nils...@googlemail.com on 11 Feb 2014 at 1:36

Attachments:

model1_sim1-solution_1.bdf

GoogleCodeExporter commented 9 years ago

I see it's definitely a problem.  I'll look into it.

Can you also attach the NX QRG and DMAP guide?  There are some NX specific 
things (e.g. CPYRA) that pyNastran doesn't support.

Original comment by mesheb82 on 11 Feb 2014 at 6:03

GoogleCodeExporter commented 9 years ago

AFAIK, CPYRA elements must be complete wrt to midnodes.

Original comment by nils...@googlemail.com on 3 Mar 2014 at 10:34

GoogleCodeExporter commented 9 years ago

Same problem 
nid = None (field #9) on card must be an integer (not blank).
card=[u'CPENTA', 809907, 11195140, 800005, 800023, 800095, 800007, 800025, 
800097, None, None, None, None, None, None, 806129, None, 806087]

It is obviously field#9 in a continuation line.

Thanks

Original comment by andrew1s...@gmail.com on 6 Mar 2015 at 9:27

GoogleCodeExporter commented 9 years ago

this issue has been fixed in the trunk

closing...will add a new ticket for CYPRA elements (see #175)

Original comment by mesheb82 on 6 Mar 2015 at 10:54

Changed title: _CTETRA, CHEXA, CPENTA with varying number of midnodes are not handled properly _
Changed state: Fixed

GoogleCodeExporter commented 9 years ago

https://code.google.com/p/pynastran/issues/detail?id=175

Original comment by mesheb82 on 6 Mar 2015 at 10:54