For end users, the following links are for the most current official version:

NOTE: For the following Documentation Zip file, the Install manual is outdated. We are working on an update. For the time being, just place MYSTRAN.exe in the same location as the file you want to run and type "mystran file.ext" where "file.ext" is the full name of the file.

Version 11.0
Windows EXE - https://www.mystran.com/versions/MYSTRAN_11.0.zip
Documentation - https://www.mystran.com/documentation/MY...2_2020.zip
Test Runs - https://www.mystran.com/versions/MYSTRAN...stRuns.zip

Additional files not commonly used by end users:
Source Code (in Zip Form as opposed to GitHub form - direct download) - https://www.mystran.com/versions/MYSTRAN...Source.zip
Test Problem Hand Calculations (60MB) - www.mystran.com/documentation/MYSTRAN_Test_Problem_Hand_Calculations.pdf

For version 11.0 and after, the default compiling procedure uses Code::Blocks and gFortran (instructions for compiling MYSTRAN are here: https://www.mystran.com/forums/showthread.php?tid=2)

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

The most current source code for developers (as opposed to end users) is on GitHub ( https://github.com/dr-bill-c/MYSTRAN ). Note that there are other versions of MYSTRAN via NASA links and GitHub, but those are older versions. The official and most recent version is linked above.

EDIT: See also this thread: https://www.mystran.com/forums/showthread.php?tid=2

Cean Wang has created the files necessary to use CMake. He has also provided instructions in the link below. Note that the source code he used is an example and we will be updating the source code and it will be added to GitHub.

https://mystran.com/compile/CMake.zip

Also, as an FYI, we now have instructions for how to compile MYSTRAN with Code::Blocks. That will be provided once we upload the latest source code on GitHub.

The documentation is controlled by specific developers (as opposed to by the general community).

For the most recent documentation, see this thread: https://www.mystran.com/forums/showthread.php?tid=39

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

The following is a list of pending modifications/updates (all updates are current as of 7/12/2020)

http://www.mystran.com/documentation/ToDo_Updates.doc

If you wish to request documentation updates, contact Bill Case at the email listed at https://www.mystran.com/

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

Prior Corrections:
http://www.mystran.com/documentation/Corrected.doc

One idea is to create a CaculiX to MYSTRAN converter. This may be useful since some pre-processors support CalculiX. While it is better if the if the preprocessor adds native support for MYSTRAn, this might be a more practical solution and is more versatile (automatically support multiple platforms). pyNastran can be used a post once Steve adds OP2 output to MYSTRAN.

Here are some notes from Harry Schaeffer about using C::B to build CalculiX. There is also some history about NASTRAN and some notes about NASTRAN-95. Some of the information here may be useful for building NASTRAN-95 and MYSTRAN.

https://www.mystran.com/misc/Calculix_an...Blocks.pdf

A few months ago, Guido Dhondt (developer of CalculiX), mentioned that he was looking into the PaStiX sparse solver. This solver seems to be a great option since it is modern, still being developed, and is open source. I recently contacted him about it and here are his comments (he said it is OK to post his comments here). I also contacted the authors of PaStiX some time ago and they said they are willing to help us incorporate it.

---

I had an IT-student to work on PaStiX for his master thesis. He finished two months ago. He took the standard version of PaStiX, however, he also did some improvements in PaStiX specifically for CalculiX. We had a test suite of 7 examples, between 700,000 and 5,000,000 equations. The results:

- the solver alone was a factor 4 to 13 faster than Pardiso
- the complete CalculiX-calculation was a factor 3 to 8 faster than with Pardiso.

PaStiX will be available in the next CalculiX-release. We are still working on some special cases. Since we changed PaStiX and it is not sure that these changes will be included by the originators of PaStiX we may have to include the modified version on our homepage.

There is one caveat: these accelarations only become true if you have a really good graphical card, let's say a card costing about 8,000 Euro. I have a GeForce GTX 1060 6GB Graphical card in my private computer, with this GPU CalculiX is slower with PaStiX (if you use the GPU).

---

I think high on the list of things to do is to add the PaStix Solver to MYSTRAN.

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

I will create detailed instructions later, but for now, this is one option that seems to be very close.

1. You can use Code::Blocks in the same way as Visual Studio. I also tried CBFortran, but it seems to be 32-bit and was much slower when reading in the source files.

http://www.codeblocks.org/downloads/26

Download "codeblocks-20.03mingw-setup.exe". This will add the Fortran compilers in the CodeBlocks install directory.

2. Download this modified 10.31 source code, which has some minor modifications from 10.31.
https://www.mystran.com/misc/Source.zip

For reference, here are the modifications that were made (you don't need to do this if you download from the above link)

- Delete the BANDIT directory
- In GET_COMMAND_LINE.f90, comment out INTRINSIC GETCL in line 46
- In GET_COMMAND_LINE.f90, change "CALL GETCL ( FILNAM )" to "CALL GET_COMMAND_ARGUMENT ( 1, FILNAM )"
- In MYSTRAN.f90, line 128, change OPEN(SC1,CARRIAGECONTROL='FORTRAN') to OPEN(SC1)
- In MYSTRAN.f90, for the line that says :  "PERCENT_CHANGE(LOAD_ISTEP,NL_ITER_NUM) = 1.0D2*(UG_NORM(LOAD_ISTEP,NL_ITER_NUM) - UG_NORM(LOAD_ISTEP,NL_ITER_NUM-1))    &" delete a space before the "&" character.

3.
- In Code::Blocks, start a new project. You don't need to select a compiler now.
- Under settings/compiler/Toolchain Executables, click the GNU Fortran Compiler and point to this directory, C:\Program Files\CodeBlocks\MinGW. Then, replace the first 3 EXE files with with gfortran.exe (or the 64 bit MinGW)
- Right click the project name in the tree and add all 10.31 directory recursively. You may also want to put the in a directory that has a short and simple path. In my case this took about 10 min so you may need to be patient.
- In Project/Build Options/Search Directories, select the INCLUDE directory location under both "Compiler" and "Linker" tabs. Also, check both the Debug and Release tabs. Otherwise, it will not find debug.h and stat.h
- Build/Rebuild

ISSUE:
At this point, Intel would normally compile, but I am not having success. At the end is says "Execution of 'X.. failed", where X is the compiler (Execution of 'mingw32-gfortran.exe...or Exectution of 'gfortran.exe..., etc). A google search has not helped to resolve it.

Upon closing CodeBlocks and then reopening it, I get a different error related to Pentium-II. That seems to be resolved by just clicking Settings/Compiler/Toolchain Executables and selecting the GNU Fortran compiler. But this is odd behavior!

For reference, here is the Makefile associated with this attempt. I changed the path to C:\A instead of C:\Source though in an attempt to shorten fix it (though that did not work).
https://www.mystran.com/misc/Makefile

And here is the build log for reference.
https://www.mystran.com/misc/M5_build_log.html

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

Using Visual Studio/Intel Fortran, here are the changes that can be made to the 10.31 on GitHub (they are minor). This may be useful if you are trying to compile with gFortran since similar changes may need to be made. This is a smaller list than in 10.2 and removes the MKL dependencies. It also removes BANDIT, which was causing a problem and is not necessary. We can restore BANDIT later.

1. OPTIONAL - Commented out reference to CDIR$ NEXTSCALAR on lines 4477 and 4479 of LAPACK_BLAS_AUX.f. This does not cause an error in Lahey or Intel so it seems optional.

2. Commented out INTRINSIC GETCL in line 46 of GET_COMMAND_LINE.f90

3. Commented out INTRINSIC GETENV in line 44 of GET_MYSTRAN_DIR.f90

4a (OPTION 1). In GET_COMMAND_LINE.f90, change "CALL GETCL ( FILNAM )" to "CALL GET_COMMAND_ARGUMENT ( 1, FILNAM )"

-------------------------------FOR REFERENCE (OLD)-------------------------------------------------------------

4b (OPTION 2). Remove GETCL.f90 (if it exists) and replace it with K2_GETCL.f90 (linked below)

https://www.mystran.com/docs/K2_GETCL.f90

Notes from Harry Schaeffer:


1. The IFP should be thrown away. I suggest marrying pynastan code and sqlite. Steve has done a lot of work in writing code for parsing and validating bulk data. These data can then be written to sglite tables.

2. Write interface routines to replace the geom1, 2, etc files. The code that implements the bulk data items still expects to find the internal bulk data codes.

3. The MPL should be replaced so that it is easier add new modules.

4.The checkpoint/restart must be replaced with a database restart.

5. Several helper fortran modules such as a scratch file manager would be useful.

6. Rethink the startup code.

7. Remove and replace the eigen and solve routines.

EDIT: BANDIT has been restored in Version 11.0

BANDIT is desired (although not mandatory) if we continue to have a "banded" solver. Although the LAPACK routines, which are optimized for banded matrices, will work on matrices that are not banded, it could result in excessive solution times. Once we get a sparse solver the only use of the banded solver will be as a backup in case the sparse solver fails.

Starting with 10.3, we decided to depreciate BANDIT because it was causing compiling errors. It can be added back later once those errors are resolved.

To add BANDIT back in, download the following ZIP file:
https://www.mystran.com/docs/BANDIT.zip