[overture] Re: 3d wing in a box
- From: Yongsheng Lian <yongshenglian@xxxxxxxxx>
- To: overture@xxxxxxxxxxxxx
- Date: Mon, 16 Nov 2009 12:55:42 -0500
Hi Bill,
I guess I have to go back to the original question I asked.
The code you gave works fine for thick airfoils with round leading
and trailing edge. I tried to reduce the thickness to a few percent,
2% for example, it did not get an overlapping grid. I noticed that
you use mapping from normal to get the volume grid. I looked at the
volume grid for both caps, the outer boundary surface are skewed.
This is very similar to the situation with o-grid when the airfoil is
thin. Is there a way the users can control the quality of the outer
boundary grid distribution?
Yongsheng
On Sun, Nov 15, 2009 at 11:25 PM, Bill Henshaw <henshaw@xxxxxxxx> wrote:
> Hi Yongsheng,
>
> Yongsheng Lian wrote:
>>
>> Bill,
>>
>> Here are two follow up questions.
>>
>> First, does the subroutine in MovingGrids.C move each movable
>> component simultaneously before update the whole grid or move one
>> (then update the grid) and move another (then update the grid again)?
>> For the 3-D wing case, since the caps need to move with the wing
>> together as a rigid body, it may cause some problems if they move
>> separately. If not, any suggestion to change the code?
>
> All grids are moved before the overlapping grid is regenerated.
>
>>
>> Second, what does DataPointMapping do? For the 3D wing case if I do
>> not use the datapointmapping, the command file failed to generate the
>> overlapping grid. If I turn it on, though there are several warnings,
>> it generates a grid.
>
> I am not sure what you are referring to. There was no DataPointMapping
> in the wing3d.cmd that I sent out. In any case it is always best to
> supply a specific command file that shows the problem.
>
> Regards,
> Bill.
>
>>
>> Thanks,
>> Yongsheng
>>
>>
>
>
Other related posts:
