These are some notes about NASTRAN, which may help to shed light about the state of NASTRAN-95:
-------------------------------

The FTC settlement with MSC resulted in the sale of UAI NASTRAN to a competitor. It wasn't made public. As I recall SDRC was the purchaser. They eventually were taken over by Siemens and UAI Nastran is part of their engineering software offering. The original NASA NASTRAN is still available but I don't know the details about that. 

The original Nastran was written in a subset of FORTRAN IV that would compile on IBM, CDC and Univac machines. Starting around 1979 <name omitted> led a project to put NASA Nastran on the Digital Equipment VAX computers running VMS. MSC complained about our doing what they had shown little interest in doing. MSC then did an updated version themselves that ran on VAX and other brands with FORTRAN 77 compilers. 

Meanwhile UAI also migrated their version to the VAX and other platforms including PCs running Windows. I provided the VAX computer UAI used for a lot of their debugging. You may recall that we had a rather rocky start with UAI Nastran but I helped them in various ways to use our VAX via a phone dial up connection (1200 baud!). Given the three hour difference in California time, the arrangement worked fairly well as they used our VAX after we went home. Eventually UAI's version worked as well as MSC's did. As you know, UAI had better sub structuring. Eventually MSC took over UAI and then CSA for good measure. Somebody (not us) sicced the FTC on them and that eventually led to the anti-trust trial that almost happened. The day before the trial, MSC folded and negotiated the settlement that led ultimately to the Siemens version.

EDIT: See this thread for the most current: https://www.mystran.com/forums/showthread.php?tid=2

This is the initial findings from an attempt at compiling with Intel (note: this was not the Admin's effort, but was done by someone else):
------------------------

So, I thought I'd give things a whirl and see what happened if I tried to compile and link using Intel Fortran integrated into Visual Studio 2019.  I presumed that at some point, you'd like to have it so it would compile and link using several different flavors of Fortran.  So, maybe a good thing to try.

I had a few compilation issues owing to minor differences between how Lahey and Intel view things, but got past them OK.  We can discuss that more at some later point.  Back in the day, I had developed some techniques to make my Fortran code mostly (but not completely) agnostic to the compiler vendor.

But, during the linking phase, I encountered several missing references.  They are noted in the attached file that Intel Fortran generated.

I suspect one of two possibilities occurred:

1. Not all of the source code was in the ZIP file that I downloaded.  (or perhaps I missed something somewhere).
2. I included some files in the link list that shouldn't have been included.  (I just included all the source code files I found in the directory hierarchy.) (I didn't try to un-ravel any of the Lahey-specific documents to try to discern what the link list actually was.)

https://www.mystran.com/misc/BuildLog.htm

NOTE FOR DEVELOPERS:

In the documentation package in this link ( https://www.mystran.com/forums/showthread.php?tid=39 ) there is a file called MYSTRAN-Source-Code-Structure.pdf, which gives a basic overview of the code structure.

------------------------------------------------------------------------------------------------------------------------------------------------------

This is a list of items for developers to consider. Developers are free take on any project they like. These are just some basic ideas:


SHORT TERM:
1. Improve the benchmark suite. This consists of adding more validated models that exercise the program and produce reliable results.

INTERMEDIATE:
1. Add a CBEAM element.

LONG TERM - PRE/POST
1. No current items.

LONG TERM - NONLINEAR
1. A nonlinear solver could be implemented.  For starters, a bisection method solution may be acceptable. Using the bisection method, I think geometric nonlinearity would be the easiest to develop and implement. Material nonlinearity could possibly be addressed after that. This would be similar to the MSC Nastran SOL 106, which has some basic nonlinear capabilities. A full nonlinear implementation (with contact, etc.) would probably be beyond the scope in the near term.

It is relevant to compare MYSTRAN to NASTRAN-95 and also discuss the state of NASTRAN-95.

-----------------------------------------------------

NASTRAN-95 (Advantages):
- More developed and includes aero and fluid elements.
- More history of use (more well known)
- The buckling solutions are more developed (MYSTRAN only supports beam elements for Eigen solutions).
- DMAP capability

NASTRAN-95 (Disadvantages):
- The user manual may need updates.
- Some of the element formulations are old (i.e. shells may exhibit shear locking).
- The code may be difficult to develop, but there may be a few developers who can work with it.
- The solver that is used may be outdated by today's standards (considering the solver is at least 25 years old).
- No PSHELL or PCOMP?

NASTRAN-95 (Unknowns):
- There appears to be some nonlinear analysis capability, but the extent is not known. Need to investigate the MATS1.

-----------------------------------------------------

MYSTRAN (Usability)
- A compiled version for Windows exists.
- Complete processes for compiling in Windows using open source tools.

MYSTRAN (Advantages)
- Perhaps the biggest advantage of MYSTRAN is developers should find it more user friendly.
- Created with more modern software and hardware in mind.
- User manual is complete and updated.
- Newer solvers can be incorporated with relative ease.

MYSTRAN (Disadvantages)
- Not as developed (less features) or well known as NASTRAN

This thread is considered to be outdated, but is kept for reference. For the most current source code and compiling instructions, see:
https://www.mystran.com/forums/showthread.php?tid=83


LAST EDIT: 4/19/2021

-----------------
SOURCE CODE
-----------------
Official GitHub: https://github.com/dr-bill-c/MYSTRAN
Note that there are NASA links for MYSTRAN, which should now point to www.mystran.com or https://github.com/dr-bill-c/MYSTRAN. There are other GitHub forks as well, but the official and most recent version is linked above.

For official versions of the source code (source code in a Zip file as opposed to the current GitHub): https://www.mystran.com/forums/showthread.php?tid=39

Note there is a 7 page document "MYSTRAN-Source-Code-Structure.pdf" that briefly describes the source code file structure within the "Documentation" in this link: https://www.mystran.com/forums/showthread.php?tid=39

------------------------------
12.0 and 12.1 COMPILING
------------------------------

The compiling process has changed since 11.2 because the SuperLU sparse solver has been incorporated.

-----Overall Notes (Compares Options)
IN WORK

-----Option 1 (Preferred Approach): CMake + gFortran (Widows and Linux)

https://www.mystran.com/compile/MYSTRAN_CMake_12.0.pdf
The following link is the original source of the above PDF:
https://gist.github.com/Bruno02468/4b58a...f2008698f5

Note that you will use the SuperLU sparse solver, which is part of the build. The above process directly uses v5.2.2, which is linked below for reference:
https://www.mystran.com/SuperLU/superlu_5.2.2.tar.gz

For reference, the original source for SuperLU is:
https://portal.nersc.gov/project/sparse/superlu/


-----Option 2 (Alternative): Code::Blocks + gFortran (Windows Instructions)
First, you need to address the SuperLU sparse solver, which is part of the build. To download the source code, we are using the version from this link:
https://portal.nersc.gov/project/sparse/superlu/
Source code direct link:
https://www.mystran.com/SuperLU/superlu_5.2.2.tar.gz

In Windows 10, you can compile SuperLU with this procedure, which requires CMake
https://www.mystran.com/SuperLU/Compile_SuperLU.pdf

The compiled SuperLU binaries are not provided because of the chance there can be an incompatibility. It is preferred to compile the yourself with the provided instructions above.

Step 2: How to use Code::Blocks with the SuperLU files for Windows
https://www.mystran.com/compile/MYSTRAN_...s_12.0.pdf

-------------------
BENCHMARK
-------------------

In order to benchmark a new build, you can run the DAT files here and compare the resulting ANS files to the ARC files. There is a batch file that allows you perform all the runs.
We are working on an Excel file that can do a detailed comparison on the numerical data. In the meantime, you verify that the resulting ANS file sizes are the same (or very similar) to the ARC files.
https://www.mystran.com/forums/showthread.php?tid=39


-------------------------------------------------
ANSIBLE ROLE FOR INSTALLING MYSTRAN
-------------------------------------------------
https://www.mystran.com/forums/showthread.php?tid=67

Dates are approximate:

COMPLETED ITEMS

- (9/20/2022) 14.0.1 Fixes a ELAS bug

- (9/7/2022) 14.0 Released. Compiling instructions were modifed.

- (9/1/2022) Major restructure - see this thread: https://www.mystran.com/forums/showthread.php?tid=83

- (2/13/2021) 12.1 fixes and error with the BUSH element.

- (2/13/2021) Brian Esp added the new MYSTRAN Benchmark Tool, which assists in the benchmarking process for new builds.

- (2/4/2021) 12.0 introduces a major feature, which is the SuperLU sparse solver. Prior versions only had the LAPACK banded solver option, which is not adequate for large DOF problems.

- (9/1/2020) The source code has been improved and no longer has OS specific files.

- (9/1/2020) Bill fixed an error that occurred when applying a pressure to shell elements.

- (9/1/2020) Bruno has made various contributions and we now have a process to compile MYSTRAN for Linux using CMake. Aspects of this were based on Cean's original makefile.

- (7/1/2020) Milesone: Brian reorganized the website, forum, links, and re-uploaded the project to GitHub. The project is more friendly for community development and can be compiled with open source tools.

- (6/20/2020) Cean Wang has created a process to compile MYSTRAN with CMake

- (6/20/2020) Brian completed the process to compile MYSTRAN with Code::Blocks and gFotran

- (5/10/2020) Robert and Brian have been able to compile MYSTRAN with the Intel compiler. We need to work on gFortran now.

- (11/25/2019) Bill added a GitHub version for MYSTRAN. This should now be the primary location for developers. This also includes the DOS and Perl files as well as Perl 3 and some additional instructions about compiling with the Lahey compiler.

- (11/9/2019) Bill has provided the relevant DOS batch files and perl scripts that he used to compile MYSTRAN with the Lahey Express compiler.

- (11/7/2019) Bill has converted the License from GNU GPL to the MIT License. The MIT license is much more permissive and will not tie the hands of developers. It only requires that the copyright be stated and that the author is acknowledged.