-
1
- #1
drk186
Aerospace
- Aug 1, 2009
- 5
O.K. First of all, I know this thread already exists, but I want to know what people these days prefer? I have 2.5 solid years of MSC.Patran experience and I thought it was the best pre/post processor that existed. I just recently started using FEMAP (4 months ago) at my new job and I was very impressed.
Some of the reasons why I prefer FEMAP over MSC.Patran are:
1) FEMAP interfaces well with Microsoft Excel. For example, you can copy over lists of elements/nodes as columns into Excel, do some data processing, then copy an updated list back into FEMAP. I find this a lot more difficult to deal with in Patran. FEMAP also seems to have a miniature spreadsheet capability (i.e. the Data Table) that is very helpful for post-processing.
2) Post-processing is incredibly easier with FEMAP (highly biased opinion). It is so easy to envelope all load cases in FEMAP.
3) The coloring scheme in FEMAP for the elements makes it a hell of a lot easier to visualize your model. Patran's coloring scheme sucks. I like how you could modify the coloring scheme by property which is very useful. Since I deal with a lot of composite materials, element orientation is something I need to constantly check and fix, and FEMAP does an amazing job at this, especially with defining bar element orientation vectors, element offsets, and releases.
These are just a few of my thoughts. Of course, NASTRAN or some other solver is the reason why we use PATRAN or FEMAP (or other pre.post processors such as Hypermesh & IDEAS). One weakness I find with FEMAP is that it's difficult to setup Frequency response analysis (large mass method) and I end up writing the NASTRAN deck manually.
Any thoughts, anyone? It is interesting to know what people think (particularly of the newer FEMAP and PATRAN versions) Your thoughts on other pre and post processors are welcome as well.
Thanks in advance.
Some of the reasons why I prefer FEMAP over MSC.Patran are:
1) FEMAP interfaces well with Microsoft Excel. For example, you can copy over lists of elements/nodes as columns into Excel, do some data processing, then copy an updated list back into FEMAP. I find this a lot more difficult to deal with in Patran. FEMAP also seems to have a miniature spreadsheet capability (i.e. the Data Table) that is very helpful for post-processing.
2) Post-processing is incredibly easier with FEMAP (highly biased opinion). It is so easy to envelope all load cases in FEMAP.
3) The coloring scheme in FEMAP for the elements makes it a hell of a lot easier to visualize your model. Patran's coloring scheme sucks. I like how you could modify the coloring scheme by property which is very useful. Since I deal with a lot of composite materials, element orientation is something I need to constantly check and fix, and FEMAP does an amazing job at this, especially with defining bar element orientation vectors, element offsets, and releases.
These are just a few of my thoughts. Of course, NASTRAN or some other solver is the reason why we use PATRAN or FEMAP (or other pre.post processors such as Hypermesh & IDEAS). One weakness I find with FEMAP is that it's difficult to setup Frequency response analysis (large mass method) and I end up writing the NASTRAN deck manually.
Any thoughts, anyone? It is interesting to know what people think (particularly of the newer FEMAP and PATRAN versions) Your thoughts on other pre and post processors are welcome as well.
Thanks in advance.