AnsweredAssumed Answered

Are you happy with the number of the Flow Simulation Solvers per SW session being reduced to only two,  regardless of the available number of CPUs?

Question asked by Boyko Tchavdarov on Jan 7, 2016
Latest reply on Jan 12, 2016 by Boyko Tchavdarov

This was the most surprising to me decision of Solid Works (NOT of Mentor Graphics who owns Flow Simulation Solver !).

It came with SW213 and it is still present. My explanation is that probably there was a problem to separate the Solver Thread  from SW session Thread (done with the same release ) with two runs in parallel (Flow Simulation Solver in batch mode),  otherwise I have no other reasonable explanation.


If so, then how many of you have a problem with the SW license that the two Threads needed to be separate? - Most of the companies have enough SW license and they can run the Flow Simulation Solver by one SW session and open another to do other job. Moreover, that the separation of the Threads does not function in the desired way:

- Very  often Solver crashes occurred (the first of the two run crashes) if both runs started on existing mesh (continued) (SW2103 -SW 2014 - I have not tried a  later version yet)

- If the SW session from which the Solver was lounged is closed then there is no way to save the results and closed the Solver prior the specified convergent criteria are met (?!)
   None of the other controls on the run are available either I(?!)

The  above two issues made the separation not functional at all, make it useless.

We need back the capability to run as many Flow Simulations in parallel as it is the number of the CPUs  - the case prior SW 2013. That was the MAIN cost saving advantage of Flow Simulation in Comparison with other Commercial CFD Codes. Since 2013 this advantage has gone.