Input\/output (I\/O) according to Dr. Paul Blelloch, director of aerospace analysis for ATA Engineering, in a presentation he gave at the Siemens CAE & Test Symposium back in October.<\/P><\/p>\n
We\u2019ll look at five easy ways you can improve performance in NX Nastran<\/A> starting with I\/O.<\/P><\/p>\n Set parameters within the RCF file, command line, or options window. Minimize the Front Size. Compare versions of NX Nastran. So there you have it. Have you found any ways to make NX Nastran faster? Let us know down in the comments below! <\/P><\/p>\n For more information on improving performance in NX Nastran<\/A>, read the full ENGINEERING.com article this post is based on, and check out Dr. Paul Blelloch\u2019s presentation from the 2014 Siemens CAE & Test Symposium<\/A> in which these tips\u2014and more!\u2014are located.<\/P><\/p>\n","protected":false},"excerpt":{"rendered":" NX Nastran can be optimized to run simulations faster, but how? If you think processor speed is the main factor you should consider, think again. Degrees of freedom (DOF) are also not as important to…<\/p>\n","protected":false},"author":53799,"featured_media":4593,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"spanish_translation":"","french_translation":"","german_translation":"","italian_translation":"","polish_translation":"","japanese_translation":"","chinese_translation":"","footnotes":""},"categories":[1],"tags":[],"industry":[],"product":[581],"coauthors":[],"class_list":["post-4592","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news","product-simcenter-nastran"],"featured_image_url":"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/6\/2019\/09\/Nastran-Best-Practices.jpg","_links":{"self":[{"href":"https:\/\/blogs.sw.siemens.com\/simcenter\/wp-json\/wp\/v2\/posts\/4592","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.sw.siemens.com\/simcenter\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.sw.siemens.com\/simcenter\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/simcenter\/wp-json\/wp\/v2\/users\/53799"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/simcenter\/wp-json\/wp\/v2\/comments?post=4592"}],"version-history":[{"count":1,"href":"https:\/\/blogs.sw.siemens.com\/simcenter\/wp-json\/wp\/v2\/posts\/4592\/revisions"}],"predecessor-version":[{"id":4597,"href":"https:\/\/blogs.sw.siemens.com\/simcenter\/wp-json\/wp\/v2\/posts\/4592\/revisions\/4597"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/simcenter\/wp-json\/wp\/v2\/media\/4593"}],"wp:attachment":[{"href":"https:\/\/blogs.sw.siemens.com\/simcenter\/wp-json\/wp\/v2\/media?parent=4592"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/simcenter\/wp-json\/wp\/v2\/categories?post=4592"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/simcenter\/wp-json\/wp\/v2\/tags?post=4592"},{"taxonomy":"industry","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/simcenter\/wp-json\/wp\/v2\/industry?post=4592"},{"taxonomy":"product","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/simcenter\/wp-json\/wp\/v2\/product?post=4592"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/simcenter\/wp-json\/wp\/v2\/coauthors?post=4592"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\n
\nLocate SCRATCH and SCR300 files on the fastest memory.
<\/STRONG>When it comes to I\/O, SCRATCH and SCR300 files have the most. These are going to be the areas you want to target in order to improve solving speed. Luckily you can specify a location within NX Nastran for high I\/O files. If you have a large amount of RAM (at least 128 GB), your best bet is to locate the files there. Another good option is a solid state drive (SSD).<\/P>
\n<\/LI>
\n<\/OL><\/p>\n
\n
\n
<\/STRONG>There are a few parameters that let you control the I\/O in NX Nastran. You\u2019ll want to use these when optimizing for speed. SCR controls how much data is written to the DBALL database compared to the SCRATCH and SCR300 files. The fastest option is SCR = YES. Everything will be written to the SCRATCH files, but beware! If you choose this option you can\u2019t restart. Smem lets you determine how much RAM to dedicate to the SCRATCH files. The more RAM, the faster your simulation will be.<\/P>
\n<\/LI>
\n<\/OL><\/p>\n
\n
\n
<\/STRONG>Front Size, or the maximum length of a non-zero column in a matrix after it is reordered, plays a big role in how long it takes to solve. The bigger the Front Size, the longer it will take, so you\u2019ll want to use the reordering algorithms in NX Nastran to minimize the Front Size of your model. NX Nastran will by default choose either the BEND or METIS algorithm based on the number of 3D elements in your model, but remember, the algorithms aren\u2019t perfect. If you\u2019re seeing slower speeds, you might want to try switching from one algorithm to the other.<\/P>
\n<\/LI>
\n<\/OL><\/p>\n<\/STRONG>4.<\/SPAN> Choose the right operating system.
<\/STRONG>Your operat<\/SPAN>ing system can also impact the amount of time a solve takes, so be sure to review all the <\/SPAN>options out there and choose the best one for your needs. NX Nastran typically performs better on Linux due to the way the OS handles memory, so Dr. Blelloch recommends Linux if you\u2019re looking to reduce your runtime.<\/SPAN><\/P><\/p>\n
\n
\n
<\/STRONG>Finally, understand the differences between versions of NX Nastran\u2014and know which version will be best at lowering your solve times. NX Nastran ILP has a few advantages over LP. For one, it has unlimited RAM. (Remember #1 where we talked about how important RAM is?) LP on the other hand has only 8GB RAM. Add to that the fact that ILP has 64-bit integers (compared to LP\u2019s 32-bit integers) and you start to see the benefit ILP offers you. More integers won\u2019t necessarily affect your runtime, but it will improve accuracy. <\/P>
\n<\/LI>
\n<\/OL>
\n<\/P>
\n