Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Completed and In-Work Items
#1
COMPLETED ITEMS

- (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.

- (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/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.

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

IN-WORK ITEMS

- Vittorio is looking into compiling MYSTRAN with gFortran.

- Although we are not quite ready, Steve Doyle has agreed to add OP2 output to MYSTRAN. This will be be a great benefit since there a few programs that can post-process OP2, including Steve's pyNastran.

- We are investigating various sparse solvers. We previously looked at BCSLIB-EXT, but the cost is relatively high and it appears there may be other solvers that are just as good (if not better). The SPOOLES solver is an option, but it seems to be relatively slow compared to other options. PARDSIO with Intel MKL is an option, but requires an Intel compiler and the user must also download the Intel MKL. PARDISO 6 is more improved than PARDISO MKL, but requires the user download a free license every year. PaStiX may be the best option since it is modern and free. We can take a page from CalculiX and see how their investigation is going since they looking at other solvers. CalculiX has historically used SPOOLES, but recently added an option for the PARDISO MKL.

- Brian is developing an automated tool that will compare the know test files (static and Eigen analysis) to a new set created by a compiled EXE. This tool should be run after compiling to ensure that no errors were introduced.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)