-
-
Notifications
You must be signed in to change notification settings - Fork 156
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
grid type 10 error #802
Comments
What is the full error? I'm not sure how you're getting there.
…On Tue, Oct 8, 2024 at 2:08 AM Vybornak2 ***@***.***> wrote:
Hello,
I was trying to use pyNastran to read my OptiStruct results. Everything
went well until I tried it on model with contact. This error has been
caused by nodes that have been in contact as I found out. I actually do not
understand this issue much, since I was not really aware of different grid
types.
Error:
def recast_gridtype_as_string(self, grid_type):
"""
converts a grid_type integer to a string
Point type (per NX 10; OUG table; p.5-663):
-1, Harmonic Point (my choice) -> ' ' = 538976288 (as an integer)
=1, GRID Point
=2, Scalar Point
=3, Extra Point
=4, Modal
=5, p-elements, 0-DOF
-6, p-elements, number of DOF
"""
try:
grid_type_str = GRID_TYPE_INT_TO_STR[grid_type]
except KeyError:
if grid_type in NULL_GRIDTYPE: # 32/64 bit error...
warnings.warn(''.join(self.get_stats()))
raise RuntimeError(f'grid_type={grid_type!r}')
return grid_type_str
RuntimeError: grid_type=10
------------------------------
I actually do not need contact forces here. Only stress values at shell
elements are of interest to me.
1. Are there any ways of avoiding this error?
2. As I would specify for bdf file to read certain keywords, can I
specify this for op2? How? (I couldn't find it in documentation)
------------------------------
If there is not workaround I wouldn't mind helping with this if you would
provide some clarification. But it also depends on the scale of such task
:).
—
Reply to this email directly, view it on GitHub
<#802>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAICUWJH25XWVXROIXQCBILZ2OOHFAVCNFSM6AAAAABPRWZJGWVHI2DSMVQWIX3LMV43ASLTON2WKOZSGU3TENJYGI3TENY>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Hello, I am sorry. Here is a full trace:
|
Try turning off pandas (build_dataframe=False). I don't know why Optistruct uses that gridtype, but contact has never been tested with it. |
Hello, I did run Actually I found out, that building dataframe using pyNastran turned out to be very slow for me, so I am not utilizing this option. I am actually not sure why. DataFrame itself looks very nice though. I am not sure if that is just nature of things with pandas when multiindexing, or if there is something else slowing up the process. So I am building a bit simper Df myself from np.ndarrays. |
Hello,
I was trying to use pyNastran to read my OptiStruct results. Everything went well until I tried it on model with contact. This error has been caused by nodes that have been in contact as I found out. I actually do not understand this issue much, since I was not really aware of different grid types.
Error:
I actually do not need contact forces here. Only stress values at shell elements are of interest to me.
If there is not workaround I wouldn't mind helping with this if you would provide some clarification. But it also depends on the scale of such task :).
If implementation/solution would be not possible at the moment, would it be possible to at least implement some custom error that could be caught?
The text was updated successfully, but these errors were encountered: