The OP2 is still supported better, so I prefer that. H5 is easy to read, which is big, but doesn’t affect me much. You can certainly trick Nastran if you want. I’m definitely no expert in the MSC/NX HDF5, but from what I’ve seen of MSC’s format, it’s exactly the same as the OP2, which means it’s got the same limitations and complexity. You need Nastran punch files (.pch) to be placed back in the working directory to submit Bearing. If you’re using piecemeal data (you probably don’t need the component stresses or the directional cosines on the solids very often), then you can save some resources there. file so you can submit Nastran job on a different machine. stored on actual punch cards and then fed into a machine that would read. You’re streaming it off disk and SSDs are decently fast, but still 10-30x slower than RAM. A Python script that reads Nastran BDF file. HDF5 is better in that you don’t really need to load the data at all. If you use the same data over and over (e.g., nodes or in a GUI), it makes sense to store it in memory. If you’re not doing huge problems, it’s not really going to matter. Siemens has taken longer to add it to NX/Simcenter Nastran, but I haven’t compared the formats and I don’t have modern MSC Nastran, so it’s hard to support it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |