With all write statements commented out in BANDIT, no bdf SEQGP entries will be generated and therefore no grid re-sequencing will occur. Maybe a more acceptable option would be just to remove BANDIT from MYSTRAN but everyone must realize that, without grid re-sequencing, problem size can be severely limited. However, this may make it obvious that the addition of a sparse solver, where BANDIT won't be needed anymore, is imperative.
BTW, NASTRAN-95 uses a modified version of the original BANDIT code (modified to fit the NASTRAN code style and I/O)
Let me know if the rest of you want to remove BANDIT and I will take care of it. I had thought the only issue was with the file open status=replace but it appears it is more than that when we consider OS's other than Windows
BTW, NASTRAN-95 uses a modified version of the original BANDIT code (modified to fit the NASTRAN code style and I/O)
Let me know if the rest of you want to remove BANDIT and I will take care of it. I had thought the only issue was with the file open status=replace but it appears it is more than that when we consider OS's other than Windows