Why leads UDS_FLUX Example from User Guide to wrong results?
Hi all,
Instead of using the default flux term I want to use my own flux term now. I want to modify the velocity later and so on... Now I started testing the DEFINE_UDS_FLUX example and I noticed, that for velocity =0 at the beginning of my Inlet-Velocity-SIgnal the example ends in wrong results. I use a simple 1D case with 10 cells. left-side is UDS-Inlet with UDS-specified-Value=0.02939, right side is UDS-Outlet with Flux=0. in The middle of Domain I have 2 Cells with a source for UDS. I notice weird behavior on the left side at Inlet for velocity in my domain =0. The UDS Value is becoming too large then. I do not know how to avoid this, but I cannot negelect this behavior. The code from User Guide: Code:
DEFINE_UDS_FLUX(my_uds2_flux, f, t, i) //RETURNS MASS FLOW RATE THROUGH A GIVEN FACES |
It seems like the 3D case works just fine but 1D is not correct after initialization. It has to be something with the code or missing information from initialization. But I initialize in the same way I do with 3d.
|
Hi schwaral. I am facing the same problem in 3D. The UDS_FLUX Example gives me wrong results. Have you managed to solve that problem?
|
All times are GMT -4. The time now is 00:56. |