-
-
Notifications
You must be signed in to change notification settings - Fork 155
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
NASA Nastran: element_code = 83? #583
Comments
Nastran 95 is not supported. I use Windows and as far as I know, nobody has built it for Windows. Some people have done it for Linux, but have not put the code online. Unless I have a working executable, I can't support it. |
I can understand. Apparently the Ubuntu terminal can be run on Windows 10 (https://www.microsoft.com/en-us/p/ubuntu/) but I don't have Win10 to test. On my ubuntu box I just installed the package from the debian repository (sudo apt-get install nastran). Maybe it would work on Win 10 this way... |
Oh, that does work. I didn't even think of trying that. Do you know who put that up (e.g., which github repository)? Do you have an example? The d01011a.inp file I tried does not make an op2. There is an nptp file that is binary, but it doesn't strangely follow the standard nastran format. |
Glad it works! ^Extent of possible build ownership and my awareness of the debian package. Here is my work in progress hobby, for example. You can see my DMAP Alters with the MSC flag. That generates a readable ("none") binary for your OP2 reader if I force model.post = -4, despite the -9 parameter flag. As far as I can tell from inspection, this is the following Nastran 95 element codes:
|
That’s not the build. That one is setup for VAX. I wonder if it’s Harry’s build. It’d be nice to find it and at least fix the required DMAP alter. I got the reader working. It supports rods, springs, dampers, CSHEAR, CBAR, and CTRIA3 at the moment. Some tests are broken and I’m out of town now, so it’ll be a few days. |
Great! The way I understand the optimal DMAP logic sequence is that the Alter for output2 should be applied at the SDR2 card for each unique SOL. (https://www.princeton.edu/~dynaflow/femgv/manuals/postnas/node24.htm) As to the source of the build, I found this: https://tracker.debian.org/pkg/nastran Cheers and happy holidays! |
Thanks! It's finally done! You can use:
or:
|
Wrote an output2 from the OS'd Nastran-95 on a SOL 1 static routine in hopes of importing it into pyNastran. I have CRODS and CTRIA3 in the model but only the CRODS seem to be imported so perhaps the CTRIA3 are being interpreted as HACAB (element code 83)?
The text was updated successfully, but these errors were encountered: