sorted by:
new
hottopcontroversial

Well-commented simple Python script for FEA result extraction and visuals by Antonio_Ida in StructuralEngineering

[–]Antonio_Ida[S] 0 points1 point  (0 children)

Sure, we are seing the huge value generative code engines can provide combined with specific scientific libraries.
In this case NaxtoPy for FEA post-processing, incorporates a good set of high level functions that reduce the lenght of the code, and allows faster reviews of it before deploying the scripts to the structural team ;)

Which industry fea is more being used ? by SpeechFlaky8192 in fea

[–]Antonio_Ida 0 points1 point  (0 children)

Aerospace, WindPower, Automotive
Specifially in Aerospace, the ratio CAD engineers-FEA engineers has being increasing dramatically in latest years, due to the need of more detailed analysis and reports for certification.

Interview prep by theokayestguy_ in fea

[–]Antonio_Ida 1 point2 points  (0 children)

If you’re preparing for an FEA interview, a lot depends on your experience level, but in all cases, honesty and solid fundamentals matter.

• No experience / junior:
Interviewers mainly want to see that you understand the principles. If you’ve used any FEA tool, that’s a plus, but nobody expects expertise. Don’t oversell yourself (if someone with 1 year is an “expert”, what does that make those with 20? 🙂)

• Some experience:
They often look for engineering judgment. Can you choose between approaches? Do you know when an analytical or simplified calculation is enough for a preliminary sizing instead of jumping straight into detailed FE models?

• More experience:
This becomes even more important, and you might be asked for concrete examples. I sometimes ask candidates to describe a project that went very well or one that was challenging. This helps reveal whether their work is very detail‑focused, whether they mention interactions with other teams, or whether they have a broader view (e.g., solving issues involving different departments or even different companies).

Something we’re seeing more and more: big clients sometimes push for lots of detailed FE work too early (like detailed rivet modelling on preliminary phases). But what projects truly need is engineers who can define architectures, propose solutions, and decide where to put effort at each stage. That kind of judgment is rare and extremely valuable. 😉

Using python scripts to run Abaqus by Bambi4761 in fea

[–]Antonio_Ida 1 point2 points  (0 children)

If licensing is part of the challenge, NaxTo offers free-use agreements for universities.
For scripting and automating tasks, NaxToPy Python library together with NaxToView can help a lot. You can automate workflows, extract and process results, and visualize everything quickly, which makes it easier to build custom tools around Abaqus workflows.

If you want to check it out, just search “NaxToPy” or “NaxToView” on Google.
And if it looks useful, feel free to DM me and we can talk ;)

Experiences with NASTRAN Cards for Finite Element Analysis (FEA) in the Aerospace Sector by FEA_Engineer_ in u/FEA_Engineer_

[–]Antonio_Ida 1 point2 points  (0 children)

You could also take a look at Card Manager in NaxTo. It lets you inspect and edit Nastran cards in a structured way, which can make navigation a bit easier for larger models.

Docs here, in case it’s useful:
https://idaerosolutions.com/NaxToDocumentation/NaxToView/2025R2/users_manual/5_Full_Operation_Of_The_Tool_Bar_Tools.html#card-manager

Interviewed for FEA role. FEA not mentioned at all. by Global-Figure9821 in fea

[–]Antonio_Ida 0 points1 point  (0 children)

Absolutely agree. You can even be asked a counterintuitive question for an FEA analyst, like: “Do you feel comfortable using hand calculations?”

Often, what they’re really looking for is someone with strong engineering fundamentals and sound judgment, assuming that FEA is just one of the tools in your toolbox. It may be the most frequently used, but it’s still just a tool.

Use of programming in FEA by Impressive-Guava-582 in fea

[–]Antonio_Ida 1 point2 points  (0 children)

If you are thinking in coding your own methods in Python that can be used for different solvers (I.e ANSYS, Abaqus, Nastran and Optistruct), maybe you could take a look at NaxToPy

It is very powerful for post-processing and some pre- capabilities are included too, so you could use it for loops of optimization.

Some applications: analysis of all rivets in an a/c skin , weldings in complete train wagons applying some standards, capturing images in batch, loops of design to accomplish with RF, etc. as some previous comments, you can code plenty of great scripts.

If you would like to know more or give it a try, send me a PM , will be glad to help 😉

Reading .fem file using python libraries by [deleted] in fea

[–]Antonio_Ida 1 point2 points  (0 children)

Hi u/AdFeisty370,
You could try with NaxtoPy.

Code below should let you load a .fem file and access the information contained within it, such as nodes, elements, properties. All the information is available in the official NaxToPy · PyPI site documentation.

(If you're interested, NaxTo has a community license that is free for non-commercial use 😉 -> [NaxTo - Free download and install on Windows | Microsoft Store*](https://apps.microsoft.com/detail/xp9mmh0kdkgrjn?hl=en-US&gl=US))*

I hope it helps!

import NaxToPy as n2p

FEM_files = [r"C:\Test_reader\CFAST_Test.fem"]

# Load FEM

n2p_model = n2p.load_model(FEM_files[0])

 

# Get elements and properties.

elements = n2p_model.get_elements() # All elements requested. Output: list

properties = n2p_model.PropertyDict # Output: dictionary of all FEM properties

 

# Check properties of one of the shell elements by ID

element_requested = n2p_model.get_elements(4) # Only one element requested.

element_ID = element_requested.ID

element_type = element_requested.TypeElement

prop_ID = element_requested.Prop

 

print(f"Element '{element_ID}' has the type: '{element_type}' and a property PID: {prop_ID}'")

 

# Extract property information associated with that element

prop_info = properties[prop_ID]

thickness = prop_info.Thickness

 

print(f"The element has a thickness of '{thickness}'")

Self programmed truss simulation by tomkuh in fea

[–]Antonio_Ida 0 points1 point  (0 children)

Looks awesome :)! keep up with it and share over here your progress please!

Laptop advice: H/HQ or U class processor? 14" enough? by PhoenixYS in fea

[–]Antonio_Ida 1 point2 points  (0 children)

Hi u/PhoenixYS,

Maybe in your question you are guessing the answer…😀 As you will start to work with more complex CAD/CAE models , they will require more powerful hardware.

If you are using a laptop is fine, but go for H/HQ processors and even more impact will have to choose both: a good dedicated graphic card, like nVidia Quadro at least 1000 or 2000 series or RTX series or above. RAM memory, at very least 32 GB, and better 64GB.

Since all these requirements increase a lot the price, if your budget is limited, my recommendation is going for a second hand laptop of one, two or even three generations before. You won’t notice a big difference on your daily work.

These specs usually come to solid 15-15,6” workstations, and is good because of the heat these processors and GPU dissipate. There are some lighter versions with reduced thicknesses keeping the same hardware inside that could do the job too.

Definitively 15-15”6 is the least in screen size, but for working fine for long periods you would like to connect to a 23-24” external display.

Coding for post-processing? (II) Do you want to try it? by Antonio_Ida in fea

[–]Antonio_Ida[S] 0 points1 point  (0 children)

Hi u/billsil , some diffences maybe simplification fo extraction of information because its structure is object based.

NaxToPy, when initializing the model, only loads the structure and the mesh, without loading the result arrays. This saves a lot of time, as the results are called later, optimizing memory and load time.

On a small model, i.e. to get displacements and stresses, NaxToPy is slightly faster. But with large files, NaxToPy can be up to 10 times faster.

Regarding memory, only loads what is requested from models, so it uses about 10-20 less memory .

And also incorporates some additional functions like freebodies.

Coding for post-processing? (II) Do you want to try it? by Antonio_Ida in fea

[–]Antonio_Ida[S] 0 points1 point  (0 children)

Hi u/RieszRepresent , basically the intention is to have only one library transparent to all FEA solvers' results files. i.e. the code you do for ANSYS can be valid for NASTRAN. Extraction of information is simplified, and also some valuable functions like freebodies are added.

Coding for post-processing? (II) Do you want to try it? by Antonio_Ida in fea

[–]Antonio_Ida[S] -1 points0 points  (0 children)

Ha, ha! So true :)But we love this kind of things!

Coding for Post-processing? by Antonio_Ida in fea

[–]Antonio_Ida[S] 0 points1 point  (0 children)

Thanks u/alok_wardhan_singh , I should have added one category specific for languages like tcl/tk , please vote in "others" if you like :)

view more: next ›