Filip Tsai

Hi Sergejs, Linux has 32 GB, Window has 8 GB. The output I get is: istart= 0 iend = 0 ---------- NumCalc started: 31/1/2022 10:6:40 ---------- 3D analysis Job title: TestWindows4 Step 1, Frequency = 25 Hz terminate called after throwing an instance of 'std::bad_array_new_length' what(): std::bad_array_new_length and the outcome in NC.out is in the attached file. In Command prompt (Wndows) with current directory being at the folder of target NumCalc I use the command "mingw32-make all". Best Regards,...

Hi Fabian, Let me try to explain the situation after some additional testing. The computer that can compute any model I have tested is a Linux computer. Unfortunately, no matter how I try to change the maximum iteration, NumCalc persists to keep the maximum iteration from 1500, exceeding the newly pushed NumCalc from Wolfgang of 250. The second computer is a Windows computer, which is significantly slower than the Linux computer in terms of computation. It can handle sphere models but also my intended...

Hi Fabian, I do not know the problem, however, when I tested a simple model (sphere) on another computer the maximum iteration works. Unfortunately, when I test my intended model on that computer, NumCalc send me the message: std::bad_alloc, which I did not see before. Best Regards, Filip

Hi Fabian, I do not know the problem, however, when I tested a simple model (sphere) on another computer the maximum iteration works. Unfortunately, when test my intended model on that computer, NumCalc send me the message: std::bad_alloc, which I did not see before. Best Regards, Filip

Hi Fabian, Yes, I used a freshly built NumCalc. To ensure nothing went wrong yesterday, I tested again to compile NumCalc, unfortunately with a similar outcome of exceeding the maximum iteration. Best Regards, Filip

Hi Fabian, According to NC.out it does not work, when I use NumCalc -nitermax 10 I get: CGS solver: number of iterations = 118, relative error = 5.26102e-10 Best Regards, Filip

Hi Fabian, After some more testing, it seems like moving the senor away from the model can solved the problem, however, moving it too far can also cause NumCalc to reach maximum iteration. Best Regards, Filip

Hi Fabian, After some testing, it seems like moving the senor 1.5 mm away from the model solved the problem by following the link you provided. However, my attempts to change the maximum iteration did not bear any fruit. Therefore, while my issue seems to be solved my question formulation has not been solved yet. Consequently, I do not know how to decide the status of this ticket. Best Regards, Filip