timeVaryingMappedFixedValue: large data mapping on complex inlet boundaries
Hi all,
it's been quite a long since my last post but well, I'm back again...My issue is basically the following: 1) I want to perform an HVAC simulation with chtMultiRegionFoam on a complex 3D domain (at the moment I have only one fluid domain, but some solid domains are to be added in the future) with multiple inlet sections of different shapes and positions in space; 2) for comparison purposes, the inlet conditions (velocity, temperature, turbulent quantities) have to be mapped from csv files previously generated by a STAR-CCM+ run involving a further domain upstream of the one considered here. 3) there is only a single csv file for all the inlets, containing values and coordinates information 4) values vary in time (e. g. for the velocities I have a csv which is valid from t=0 to t=5 s, another one from t=5 s to t=180 s etc.) 5) there are A LOT of values to map (above 100k points in space) What I have done till now is generating the OpenFOAM mesh with SHM, assigning a single patch name for all the inlets (though, as I said above, they are actually multiple and separated sections) and trying to set the timeVaryingMappedFixedValue bc for this "single" patch, using one of the csv and generating the text files in the required format and folders (I have previous successfull experiences with this bc, but on single simple-shaped inlet patches and with much less points to map). However, the case crashes already at the mesh decomposition stage with floating point exception, I've tried also different decomposition algorithms (hierarchical and scotch) but the result is the same (see code below, obtained with hierarchical). Code:
Create time 1) I'm working with OpenFOAM-2.2.x, latest available update 2) It is not a mesh-related problem, since with other inlet bcs (e. g. fixed uniform values) the case is decomposed and started without any issue 3) I have carefully cheked the points/values correspondence (for now I'm testing only the velocity mapping), and aside from the large number of points (115412, by the way) it seems to be all consistent with the required format. If someone can share some experience or advice about the topic, I will be very grateful Thank you in advance V. |
So, no hints/advices on this topic? I'm still stuck at the point described in my previous post...
|
|
Quote:
I saw your post and I think that you just have to add the "offset" entry in your syntax to get things work (or at least to overcome the specific issue you had reported). Try this one: inlet { type timeVaryingMappedFixedValue; setAverage 0; offset (0 0 0); } and see what happens. My problem is something different, It is not related to the syntax but, I guess, to the limits of this BC in handling complex/large sets of data which has to be mapped on geometrically non-trivial patches. Regards V. |
Thank you very much!
|
timeVaryingMappedFixedValue for multiple inlet
Hi,
I did a precursor simulation on a channel. Because of using blockMesh with clustered wall meshing the channel was split in two blocks. So inlet & Outlet consists of two patches. Now I want to use Code:
timeVaryingMappedFixedValue How can this be done is quickest way (without running simulations again at least)? |
Quote:
It seems that the pointToPointPlanarInterpolation tries to work out a coordinate system using your z-values so your z-values must change. In a 2D sim which was empty in z, I just duplicated each value with a slightly different z, and it worked fine. Hope this helps. |
Quote:
|
All times are GMT -4. The time now is 11:23. |