<![CDATA[MYSTRAN Forum

<![CDATA[MYSTRAN Forum - MYSTRAN]]> https://www.mystran.com/forums/ Tue, 28 Apr 2026 10:51:49 +0000 MyBB <![CDATA[M3D Tutorials]]> https://www.mystran.com/forums/showthread.php?tid=113 Sun, 02 Mar 2025 03:16:56 +0000 Admin]]> https://www.mystran.com/forums/showthread.php?tid=113
https://www.espcomposites.com/1_M3D_Preliminary.mp4

https://www.espcomposites.com/2_M3D_Intro_1.mp4

https://www.espcomposites.com/3_M3D_Intro_2.mp4

https://www.espcomposites.com/4_M3D_Solid_Beam_1.mp4

https://www.espcomposites.com/5_M3D_Solid_Beam_2.mp4

https://www.espcomposites.com/6_M3D_Plate_With_Hole.mp4

https://www.espcomposites.com/7_M3D_Plat..._Holes.mp4

https://www.espcomposites.com/8_M3D_Truss_Script.mp4

https://www.espcomposites.com/9_M3D_Mate...erties.mp4]]>
https://www.espcomposites.com/1_M3D_Preliminary.mp4

https://www.espcomposites.com/2_M3D_Intro_1.mp4

https://www.espcomposites.com/3_M3D_Intro_2.mp4

https://www.espcomposites.com/4_M3D_Solid_Beam_1.mp4

https://www.espcomposites.com/5_M3D_Solid_Beam_2.mp4

https://www.espcomposites.com/6_M3D_Plate_With_Hole.mp4

https://www.espcomposites.com/7_M3D_Plat..._Holes.mp4

https://www.espcomposites.com/8_M3D_Truss_Script.mp4

https://www.espcomposites.com/9_M3D_Mate...erties.mp4]]> <![CDATA[MYSTRAN - History and Current Efforts (2025 Update)]]> https://www.mystran.com/forums/showthread.php?tid=112 Sat, 01 Mar 2025 13:05:54 +0000 Admin]]> https://www.mystran.com/forums/showthread.php?tid=112
https://www.espcomposites.com/MYSTRAN_Overview_2025.mp4]]>
https://www.espcomposites.com/MYSTRAN_Overview_2025.mp4]]> <![CDATA[1D Elements - Now Free]]> https://www.mystran.com/forums/showthread.php?tid=111 Wed, 12 Feb 2025 22:54:02 +0000 Admin]]> https://www.mystran.com/forums/showthread.php?tid=111 https://www.structuralfea.com

1D Elements© is a user friendly finite element pre/post processor that uses beam, rod, and spring elements in 2D space. It is Excel based and uses VBA (Visual Basic for Applications) to allow for advanced capability. 1D Elements is compatible with the included free MYSTRAN solver (similar to Nastran) or the MSC Nastran solver. This combination is a standard approach to finite element analysis (pre/post processer and a solver).]]> https://www.structuralfea.com

1D Elements© is a user friendly finite element pre/post processor that uses beam, rod, and spring elements in 2D space. It is Excel based and uses VBA (Visual Basic for Applications) to allow for advanced capability. 1D Elements is compatible with the included free MYSTRAN solver (similar to Nastran) or the MSC Nastran solver. This combination is a standard approach to finite element analysis (pre/post processer and a solver).]]> <![CDATA[Inertial relief in Mystran]]> https://www.mystran.com/forums/showthread.php?tid=109 Tue, 29 Oct 2024 03:05:05 +0000 Maxime56]]> https://www.mystran.com/forums/showthread.php?tid=109 <![CDATA[Composite orientation]]> https://www.mystran.com/forums/showthread.php?tid=108 Sat, 03 Aug 2024 12:30:52 +0000 trilbytim]]> https://www.mystran.com/forums/showthread.php?tid=108
It creates a .bdf file which does solve (hooray!), however the results aren't right (boohoo!). I've attached a very simple test file (.txt extension added to allow it's upload to this forum, remove to use). You can see from the PCOMP card (line 41 onwards) that I have the ply orientations all set to 45 degrees. Since this is unbalanced (there are no -45 plies) then there should be strong bend-twist coupling, so the deformed shape should show some twist, but it doesn't. Also if you manually change the values of the plies to all 0 or all 90 and re run then there is nothing like enough difference in the deflection. The difference in modulus between the two directions is about 20x, so the deflection should be an order of magnitude lower for the 0 degree case than the 90 degree case. However they're coming out very similar.

Something clearly isn't being applied correctly. I'm not sure if this is the element orientations, the PCOMP card or the MAT8 card. Any ideas, I'm a bit stumped?

.txt

FEMMeshGmsh.bdf.txt (Size: 1.74 KB / Downloads: 0) ]]>
It creates a .bdf file which does solve (hooray!), however the results aren't right (boohoo!). I've attached a very simple test file (.txt extension added to allow it's upload to this forum, remove to use). You can see from the PCOMP card (line 41 onwards) that I have the ply orientations all set to 45 degrees. Since this is unbalanced (there are no -45 plies) then there should be strong bend-twist coupling, so the deformed shape should show some twist, but it doesn't. Also if you manually change the values of the plies to all 0 or all 90 and re run then there is nothing like enough difference in the deflection. The difference in modulus between the two directions is about 20x, so the deflection should be an order of magnitude lower for the 0 degree case than the 90 degree case. However they're coming out very similar.

Something clearly isn't being applied correctly. I'm not sure if this is the element orientations, the PCOMP card or the MAT8 card. Any ideas, I'm a bit stumped?

.txt

FEMMeshGmsh.bdf.txt (Size: 1.74 KB / Downloads: 0) ]]> <![CDATA[Abaqus/CCX to MYSTRAN/Nastran Converter]]> https://www.mystran.com/forums/showthread.php?tid=106 Thu, 25 Jan 2024 13:52:31 +0000 Admin]]> https://www.mystran.com/forums/showthread.php?tid=106
ABAQUS to Nastran converter:
https://bor.gs/inp2nas/]]>
ABAQUS to Nastran converter:
https://bor.gs/inp2nas/]]> <![CDATA[Concern about RBE3]]> https://www.mystran.com/forums/showthread.php?tid=105 Thu, 25 Jan 2024 03:12:46 +0000 Victor]]> https://www.mystran.com/forums/showthread.php?tid=105
In my implementation, when I apply a moment load about the x axis, it causes the correct moment about x but also another moment about the y axis as shown in the attached picture. Note that the independent nodes are on an inclined face, not in a plane normal to the applied moment.

If you've used RBE3 before, would you expect this beam to bend as well as twist?

I'm suspicious of this because CalculiX has a similar issue with its moment loads on beams which are internally converted to MPCs similar to an RBE3.

.png

rbe3.png (Size: 27.95 KB / Downloads: 4) ]]>
In my implementation, when I apply a moment load about the x axis, it causes the correct moment about x but also another moment about the y axis as shown in the attached picture. Note that the independent nodes are on an inclined face, not in a plane normal to the applied moment.

If you've used RBE3 before, would you expect this beam to bend as well as twist?

I'm suspicious of this because CalculiX has a similar issue with its moment loads on beams which are internally converted to MPCs similar to an RBE3.

.png

rbe3.png (Size: 27.95 KB / Downloads: 4) ]]> <![CDATA[15.1.0 Update]]> https://www.mystran.com/forums/showthread.php?tid=104 Tue, 19 Dec 2023 14:50:01 +0000 borges]]> https://www.mystran.com/forums/showthread.php?tid=104
We separated this from 15.0 so people could have a "clean" release without this new feature, since verification efforts are still ongoing.

You can get the Windows and Linux binaries at https://github.com/MYSTRANsolver/MYSTRAN...tag/15.1.0 !]]>
We separated this from 15.0 so people could have a "clean" release without this new feature, since verification efforts are still ongoing.

You can get the Windows and Linux binaries at https://github.com/MYSTRANsolver/MYSTRAN...tag/15.1.0 !]]> <![CDATA[15.0 Released - Major Update]]> https://www.mystran.com/forums/showthread.php?tid=103 Tue, 19 Dec 2023 14:14:39 +0000 Admin]]> https://www.mystran.com/forums/showthread.php?tid=103 https://github.com/MYSTRANsolver/MYSTRAN/pull/9) and a quick summary is as follows:

All models in our current benchmark set now run without any illegal memory operations. So do other models that used to cause trouble, like cshear.bdf (part of the build verification suite) and large_shelled_beam.bdf (user-reported, I think). That doesn't mean results are necessarily correct. Not all bugs are memory bugs! But this update means that many models that used to trigger nondeterministic behaviour and/or crashes now run to completion. This way, we can actually get the results to verify they're correct, and also work on new features unencumbered by crashes.

------- SOME DETAILS --------

- ELMOFF was comparing QUAD4 areas to an uninitialized EPS1, causing it to think positive areas were negative. The fix: initialize EPS1 to be EPSIL(1) as everywhere else does.

- GPWG had some debug prints that tried to write the value of ITABLE before it was set. The fix: move the initialization of ITABLE a couple lines up.

- ANY_U_P_OUTPUT, a variable with all assignments and uses commented out, appeared on an IF statement, thus sometimes being read even though it was never set. The fix: comment it out of the IF statement as well.

- there was a faulty conditional in the SuperLU version we were using, causing crashes when the global stiffness matrix was singular. The fix: so we changed to a more recent state of their repository since the fix was recent.

- a small oversight in indexes used to print CSHEAR engineering forces in WRITE_ELEM_ENGR_FORCE caused a buffer to be read past the part that actually held values. The fix: make the indexes consistent with the initialized part.

- OP2 code in WRITE_ELEM_STRESSES forgot to set a value called STRESS_CODE, used to indicate what's about to be written. The fix: put in a placeholder value for now -- there's other placeholder values in that same subroutine anyway.

- a missing ELSE was causing a fatal error to be issued for valid models containing CSHEAR cards with a nonzero OCID. The fix: added the ELSE.

- the subroutine GET_KE_OFFSET was communicating the wrong shape of BUSH element parameters (KEO_BUSH) to a matrix operation (MATPUT). The fix: communicate the correct shape.

- a post-deallocation subroutine was being called for the matrix I2_GMN regardless of whether it had been just deallocated or not, triggering a bad read. The fix: move the call into the conditional for whether I2_GMN was just deallocated.

- the SCNUM vector, containing subcase numbers, was being allocated with the wrong size, resulting in an overflow when it was written to. In MODES solutions, the "subcases" are the number of requested eigenvectors. The fix: set LSUB, which determines the maximum number of subcases in the solution, as soon was we see the EIGR bulk data card "chosen" by the METHOD case control card during LOADB. This way, all subsequent (i.e. after LINK0) allocations of SCNUM will be the correct size. There are no writes to SCNUM that could overflow before, since we set the size before the limit is even communicated to the rest of the program.

- same as above, but for EIGRL cards and the OGROUT vector. The fix: same as above, but setting LSUB as soon as we see the right EIGRL card during LOADB.

- a debug write was reading from an uninitialized variable depending on the requested data. The fix: initialize it just like in similar requests.

- okay, so, when a BUSH element has negative OCID (or the continuation card is absent), that means we use the GA-GB line as the x-axis for computing offsets. However, when GA and GB coincide, that line can't be computed, but an attempt was being made to compute them anyway, resulting in some nasty memory bugs. The fix: detect zero-length BUSH elements with negative OCID and mark them as non-offset, thus avoiding the problematic computations.]]> https://github.com/MYSTRANsolver/MYSTRAN/pull/9) and a quick summary is as follows:

All models in our current benchmark set now run without any illegal memory operations. So do other models that used to cause trouble, like cshear.bdf (part of the build verification suite) and large_shelled_beam.bdf (user-reported, I think). That doesn't mean results are necessarily correct. Not all bugs are memory bugs! But this update means that many models that used to trigger nondeterministic behaviour and/or crashes now run to completion. This way, we can actually get the results to verify they're correct, and also work on new features unencumbered by crashes.

------- SOME DETAILS --------

- ELMOFF was comparing QUAD4 areas to an uninitialized EPS1, causing it to think positive areas were negative. The fix: initialize EPS1 to be EPSIL(1) as everywhere else does.

- GPWG had some debug prints that tried to write the value of ITABLE before it was set. The fix: move the initialization of ITABLE a couple lines up.

- ANY_U_P_OUTPUT, a variable with all assignments and uses commented out, appeared on an IF statement, thus sometimes being read even though it was never set. The fix: comment it out of the IF statement as well.

- there was a faulty conditional in the SuperLU version we were using, causing crashes when the global stiffness matrix was singular. The fix: so we changed to a more recent state of their repository since the fix was recent.

- a small oversight in indexes used to print CSHEAR engineering forces in WRITE_ELEM_ENGR_FORCE caused a buffer to be read past the part that actually held values. The fix: make the indexes consistent with the initialized part.

- OP2 code in WRITE_ELEM_STRESSES forgot to set a value called STRESS_CODE, used to indicate what's about to be written. The fix: put in a placeholder value for now -- there's other placeholder values in that same subroutine anyway.

- a missing ELSE was causing a fatal error to be issued for valid models containing CSHEAR cards with a nonzero OCID. The fix: added the ELSE.

- the subroutine GET_KE_OFFSET was communicating the wrong shape of BUSH element parameters (KEO_BUSH) to a matrix operation (MATPUT). The fix: communicate the correct shape.

- a post-deallocation subroutine was being called for the matrix I2_GMN regardless of whether it had been just deallocated or not, triggering a bad read. The fix: move the call into the conditional for whether I2_GMN was just deallocated.

- the SCNUM vector, containing subcase numbers, was being allocated with the wrong size, resulting in an overflow when it was written to. In MODES solutions, the "subcases" are the number of requested eigenvectors. The fix: set LSUB, which determines the maximum number of subcases in the solution, as soon was we see the EIGR bulk data card "chosen" by the METHOD case control card during LOADB. This way, all subsequent (i.e. after LINK0) allocations of SCNUM will be the correct size. There are no writes to SCNUM that could overflow before, since we set the size before the limit is even communicated to the rest of the program.

- same as above, but for EIGRL cards and the OGROUT vector. The fix: same as above, but setting LSUB as soon as we see the right EIGRL card during LOADB.

- a debug write was reading from an uninitialized variable depending on the requested data. The fix: initialize it just like in similar requests.

- okay, so, when a BUSH element has negative OCID (or the continuation card is absent), that means we use the GA-GB line as the x-axis for computing offsets. However, when GA and GB coincide, that line can't be computed, but an attempt was being made to compute them anyway, resulting in some nasty memory bugs. The fix: detect zero-length BUSH elements with negative OCID and mark them as non-offset, thus avoiding the problematic computations.]]> <![CDATA[New User facing issues]]> https://www.mystran.com/forums/showthread.php?tid=102 Tue, 12 Dec 2023 04:41:12 +0000 avi7]]> https://www.mystran.com/forums/showthread.php?tid=102

Code:
LINK  3 BEGIN

dgstrf() error returns INFO= 2101

L\U MB 6.750    total MB needed 7.648

 *ERROR  9903: SUPERLU SPARSE SOLVER HAS FAILED WITH INFO =         2101 IN SUBR SYM_MAT_DECOMP_SUPRLU CALLED BY SUBR LINK3

 CHECK F06 OUTPUT FILE FOR        1 FATAL MESSAGE(S)

 CHECK ERR OUTPUT FILE FOR        2 WARNING MESSAGE(S)

 Processing terminated. Check for error messages in output file:

 Test.F06

Note: The following floating-point exceptions are signalling: IEEE_UNDERFLOW_FLAG IEEE_DENORMAL

The error in .F06 is basically the same:

Code:
>> LINK  3 BEGIN

 *ERROR  9903: SUPERLU SPARSE SOLVER HAS FAILED WITH INFO =         2101 IN SUBR SYM_MAT_DECOMP_SUPRLU CALLED BY SUBR LINK3

Please tell me if there's something I need to change. The test case is very simple.]]>

Code:
LINK  3 BEGIN

dgstrf() error returns INFO= 2101

L\U MB 6.750    total MB needed 7.648

 *ERROR  9903: SUPERLU SPARSE SOLVER HAS FAILED WITH INFO =         2101 IN SUBR SYM_MAT_DECOMP_SUPRLU CALLED BY SUBR LINK3

 CHECK F06 OUTPUT FILE FOR        1 FATAL MESSAGE(S)

 CHECK ERR OUTPUT FILE FOR        2 WARNING MESSAGE(S)

 Processing terminated. Check for error messages in output file:

 Test.F06

Note: The following floating-point exceptions are signalling: IEEE_UNDERFLOW_FLAG IEEE_DENORMAL

The error in .F06 is basically the same:

Code:
>> LINK  3 BEGIN

 *ERROR  9903: SUPERLU SPARSE SOLVER HAS FAILED WITH INFO =         2101 IN SUBR SYM_MAT_DECOMP_SUPRLU CALLED BY SUBR LINK3

Please tell me if there's something I need to change. The test case is very simple.]]> <![CDATA[Femap model hard crash]]> https://www.mystran.com/forums/showthread.php?tid=101 Sat, 02 Dec 2023 20:41:01 +0000 borges]]> https://www.mystran.com/forums/showthread.php?tid=101
While working on K6ROT, I decided to run a simple Femap 2x2 flat plate model on MYSTRAN.

This triggers a nondeterministic crash: half of the runs yield a segfault, the other half finish with a fatal error when calling the SuperLU matrix factorization subroutine.

Of course, these decks were auto-generated by Femap, so they're nowhere near hand-crafted quality. Still, no deck, no matter how corrupt, should trigger an illegal memory access.

Attached are two version of the deck: the one exported from Femap as-is, and another with some slight changes to make it more affable to MYSTRAN (to no avail).

Something in this deck is causing MYSTRAN to pass bad data to SuperLU. I'm looking into what, how, and a fix -- but any input is appreciated.

Thanks!

.txt

plate_upforce.txt (Size: 3.98 KB / Downloads: 0)

.txt

plate_upforce_changed.txt (Size: 3.98 KB / Downloads: 0) ]]>
While working on K6ROT, I decided to run a simple Femap 2x2 flat plate model on MYSTRAN.

This triggers a nondeterministic crash: half of the runs yield a segfault, the other half finish with a fatal error when calling the SuperLU matrix factorization subroutine.

Of course, these decks were auto-generated by Femap, so they're nowhere near hand-crafted quality. Still, no deck, no matter how corrupt, should trigger an illegal memory access.

Attached are two version of the deck: the one exported from Femap as-is, and another with some slight changes to make it more affable to MYSTRAN (to no avail).

Something in this deck is causing MYSTRAN to pass bad data to SuperLU. I'm looking into what, how, and a fix -- but any input is appreciated.

Thanks!

.txt

plate_upforce.txt (Size: 3.98 KB / Downloads: 0)

.txt

plate_upforce_changed.txt (Size: 3.98 KB / Downloads: 0) ]]> <![CDATA[Mystran and Intel One API 2022]]> https://www.mystran.com/forums/showthread.php?tid=99 Wed, 09 Nov 2022 01:27:21 +0000 realbabilu]]> https://www.mystran.com/forums/showthread.php?tid=99
I just new at mystran this year.
For information Intel One API now is free for everyone. Including the Math Kernel Library ,and Vtune
The c++ compiler for compiling SuperLu and fortran compiler for compiling Mystran can be downloaded at https://www.intel.com/content/www/us/en/...nents.html
The MKL can be downloaded at https://www.intel.com/content/www/us/en/...nload.html
alternatively OpenBlas also can be used https://github.com/xianyi/OpenBLAS/relea...21-x64.zip
The Intel compiler required free Visual Studio Community https://visualstudio.microsoft.com/vs/community/
I still learn to create makefile using Cmake for VS and the GCC equations.com. so i jumped without CMAKE

A. USING Visual Studio Windows
Steps :
1. Compile SuperLu.Lib in SRC superlu with c_fortran_dgsvv.c with

Code:
icl -c *.c /O3 /Qpar

with modified Slu_cnames.h for creating obj, then

Code:
xilib /out:superlu.lib *.obj

compile with optimization like /QaxCORE-AVX2 for intel or /QxCORE-AVX2 for AMD may improve the speed, and /Qpar for parallel run
2. Create the StandardConsole / Quickwin Fortran project
3. Drag all fortran subroutine excluding the "Source\Modules\LAPACK\Unresolved_Externals_Problem" since we will use Openblas / MKL AND *.H files in include folder
to the Solution Explorer - Source Files
4. Edit GET_MYSTRAN_DIR.f90

Code:
CALL GETENV ( 'MYSTRAN_directory', MYSTRAN_DIR )

Code:
CALL get_environment_variable  ( 'MYSTRAN_directory', MYSTRAN_DIR )

Hope this call get_environment_variable is used in the next mystran, since it used also in gcc.
5. For mkl --> in Solution --> right click Properties » Configuration properties » Fortran » Use Intel MKL » Sequential or Parallel --> if /Qpar then Parallel
For OpenBlas drag Openblas.dll.a and with all *.h to the Solution Explorer - Source Files
compile with optimization like /QaxCORE-AVX2 for Intel or /QxCORE-AVX2 for AMD may improve the speed
6. For big problems, it could catch stack overflow, move all stack to heap.
in Solution --> Properties » Fortran » Configuration properties » Optimization » Heap Arrays » 0
7. You will get the exe file.

B. Using command line Intel compiler x64 enviroment
a. Get mystran latest source code put in d:\mystran --> d:\mystran\mystran-main\
a. Get superLu latest, put on SRC folder with FORTRAN d_fortran_dgssv.c and modified SLU_Cnames.h on SuperLu folder d:\mystran\mystran-main\superlu
b. Get into CMD command lines intel x64 Compiler
c. Get 2 Batch file to run in d:\mystran
compile_mystran_superlu_with_mkl_AVX2_Parallel.bat https://controlc.com/f266943f
mystran.rsp https://controlc.com/32578204
d. Get mystran.exe inside x64/Release

Questions
1. SuperLu-MT cant be used here, right?
2. Can i get the built MingW GCC makefile? that compiled in msys or mingw, so i can changed to be compiled in the equations mingw compiler

NOTE: Modified SLU_Cnames.h inside SRC SuperLU dir for Visual Fortran

Code:
/* Fortran interface */

#define c_bridge_dgssv_ C_BRIDGE_DGSSV

#define c_fortran_sgssv_ C_FORTRAN_SGSSV

#define c_fortran_dgssv_ C_FORTRAN_DGSSV

#define c_fortran_cgssv_ C_FORTRAN_CGSSV

#define c_fortran_zgssv_ C_FORTRAN_ZGSSV

]]>
I just new at mystran this year.
For information Intel One API now is free for everyone. Including the Math Kernel Library ,and Vtune
The c++ compiler for compiling SuperLu and fortran compiler for compiling Mystran can be downloaded at https://www.intel.com/content/www/us/en/...nents.html
The MKL can be downloaded at https://www.intel.com/content/www/us/en/...nload.html
alternatively OpenBlas also can be used https://github.com/xianyi/OpenBLAS/relea...21-x64.zip
The Intel compiler required free Visual Studio Community https://visualstudio.microsoft.com/vs/community/
I still learn to create makefile using Cmake for VS and the GCC equations.com. so i jumped without CMAKE

A. USING Visual Studio Windows
Steps :
1. Compile SuperLu.Lib in SRC superlu with c_fortran_dgsvv.c with

Code:
icl -c *.c /O3 /Qpar

with modified Slu_cnames.h for creating obj, then

Code:
xilib /out:superlu.lib *.obj

Code:
CALL GETENV ( 'MYSTRAN_directory', MYSTRAN_DIR )

Code:
CALL get_environment_variable  ( 'MYSTRAN_directory', MYSTRAN_DIR )

Code:
/* Fortran interface */

#define c_bridge_dgssv_ C_BRIDGE_DGSSV

#define c_fortran_sgssv_ C_FORTRAN_SGSSV

#define c_fortran_dgssv_ C_FORTRAN_DGSSV

#define c_fortran_cgssv_ C_FORTRAN_CGSSV

#define c_fortran_zgssv_ C_FORTRAN_ZGSSV

]]> <![CDATA[ABAQUS/CalculiX to NASTRAN/MYSTRAN Converter]]> https://www.mystran.com/forums/showthread.php?tid=98 Wed, 19 Oct 2022 05:29:41 +0000 Admin]]> https://www.mystran.com/forums/showthread.php?tid=98 <![CDATA[BANDIT Issue]]> https://www.mystran.com/forums/showthread.php?tid=97 Tue, 18 Oct 2022 20:58:07 +0000 Admin]]> https://www.mystran.com/forums/showthread.php?tid=97 https://gcc.gnu.org/wiki/GFortranStandards#Fortran_90) and later, as is the case with statement GOTO.

Initial Response:
Bandit is an odd one. A couple years ago we had problems with it so afaik we just removed it in essence. It’s a routine that is only used when you enact the banded solver and even then it only helps to optimize the matrix setup so the solution is faster and uses less memory. But that was far more important in the 70s/80s and not such a big deal now. For large problems, we use the superlu sparse solver anyway (so bandit would never come into play). We could totally remove anything to do with bandit and I would be ok with that. I think we may tried, but there were some loose ends so it sort of artificially resides in the program. But it would be nice to totally strip it out clean IMO.]]> https://gcc.gnu.org/wiki/GFortranStandards#Fortran_90) and later, as is the case with statement GOTO.

Initial Response:
Bandit is an odd one. A couple years ago we had problems with it so afaik we just removed it in essence. It’s a routine that is only used when you enact the banded solver and even then it only helps to optimize the matrix setup so the solution is faster and uses less memory. But that was far more important in the 70s/80s and not such a big deal now. For large problems, we use the superlu sparse solver anyway (so bandit would never come into play). We could totally remove anything to do with bandit and I would be ok with that. I think we may tried, but there were some loose ends so it sort of artificially resides in the program. But it would be nice to totally strip it out clean IMO.]]> <![CDATA[OP4 Discussion]]> https://www.mystran.com/forums/showthread.php?tid=96 Tue, 18 Oct 2022 20:55:50 +0000 Admin]]> https://www.mystran.com/forums/showthread.php?tid=96