pyNastran Discuss

Piero, I'm impressed. You made it further than I probably would have on Linux! The setup script

David, The model was build using OpenVSP, which can be found: http://openvsp.org/, which a very user

I was able to read a very large model that used about 40 GB of ram. The limit is your hardware.

That one worked. That said, the program seemed to run before -- even though the pyside2 threw an

Thanks, Steve. "The function does not apply WTMASS." This is what I was looking for. Clark

Clark, I pushed a new build pyNastranGUI_1.5.0-dev4-644cd28a0_2025-1-20 that fixes that

The easiest way to do it is to flip to the specific result that you're interested in before

Ah, thanks for clarifying that. I also tried pulling the geometry data from a punch file but had

Oh yeah…that'll do it! The binary debug is a separate file. It can tell you things like if

Hi Steve, I thought I just posted a message here, but don't see it in the message list, so

Hi Steve, I could find some time figuring out this issue. I used to calculate psd through frf, but

Steve, Nice work! Thanks for getting on this. It seems to work ok. I'll pass it on to the

I don't use Anaconda, so I might not be the best person to help with that. It does non-standard

> op2_results.stress.ctria3_composite_stress[5] -> ctria3_composite_stress[5], you can then

It is a positive definite eigenvalue check. Maybe I'm misunderstanding the requirement; but how

Thank you! I figured the capital letter of the "N" corrected the error and it now works

I came across this issue which suggested that I should be able to calculate the OLOAD Resultant by

Hi Steve, Thank you for you answer! I did not expect that PyNastran was calculating anything there, I

Thank you for the quick reply. I will parse myself. Thank you! I will also search for the function to

Comps is not redundant. Refc does not need to be the same as comps and generally is not. It needs to

Brian, You want the punch=True flag in read_bdf On Fri, Jul 19, 2024 at 6:20 PM Brian C <cfespie@

Those are the best kind of errors! On Mon, Jul 15, 2024 at 2:33 AM Martin Merkl <martin.merkl.cz@

Thank you Steven for the detailed replies. I keep learning more good stuff about PyNastran. On Friday

Thank you Steven! I'm looking into that. Cody On Friday, June 28, 2024 at 10:18:11 AM UTC-5

Please start a new thread. On Thu, Jun 27, 2024 at 2:45 PM Cody Godines <codyg...@gmail.com>

I cannot reproduce your issue using the latest dev version or 1.4.1. op2_results.stress.

Sure. Please find attached the updated zip. On Tue, Jun 11, 2024 at 7:34 AM steve <mesheb82@gmail.

Hello, Thanks for the latest version, it doesn't crash anymore but as you assumed my goal was to

What do you think are the best ways to learn pyNastran? This documentation (link) Debugging mode in

Brian, No. You directly delete it from elements, so/properties: del model.elements[eid] Most of the

The outputs of the op2 are the same as the f06. A few things are removed (eg, solid element principal

Oh, sorry I finally saw this! You got caught by the new spam filter. RMS is surprisingly tricky to

This is a mainly a bug fix release. There's also a couple of new acoustic cards and MSC's