[StefanoSic]

Good day,

I am fairly new to FineMarine and have still got a few hiccups in some of the computations I have been running.

I had completed a set of computations for a 35m vessel and realised that the viscous layers were not added correctly, so I went to change that and started having issues with the solver crashing.

I believed it to be a mesh quality issue and so I refined several areas, until the mesh quality check brought back a favourable result. 2/3 Computations then ran and completed thereafter but the third proved more troublesome, this one included actuator disks.

I tried further refining the mesh but this did not help my case. I analysed the monitor and saw an odd occurrence. Visible in the Residuals and 'Fx' mainly, there were large spikes every few iterations: Seen in Capture 1-4.

Captures 1 and 2 are from a computation using a much smaller timestep of about 0.003s and Captures 3 and 4 are using the standard timestep of 0.0124s.

I read through the documentation and saw the section recommending fixes for spikes in the forces, seen in the monitor and that is why I changed my timestep size. I also tried increasing the acceleration ramp from 1s to 1.5s but with no visible difference.

With my last computation, using the standard timestep and a 1.5s ramp, the solver did not crash, however, while the computation would normally be finished overnight, this morning it was only on about 3500 Iterations, compared to the normal 7500 it should have reached. So I believe it is also running slower than usual for some reason.

The 'Fx' had seemingly converged and so I stopped the computation early and inspected the results to find a very odd free surface. Seen in Capture5, the wake is very short and in previous computations of this scenario, prior to adjusting the viscous layers, the wake was better represented and far larger. It also seems as if the free surface is "Stuck" to the fore section of the vessel, rising as high as the deck.

I'm not sure why the free-surface appears this way and I'm not sure if it is related to the spikes seen in the monitor during computation. Has anybody had a similar experience to this, specifically the spikes, and do you have a potential solution?

Thank you.


Capture.JPG

Capture2.JPG

Capture3.JPG

Capture4.JPG

Capture5.jpg