[CIG-SEISMO] techniques for generating large meshes with CUBIT

[Brad Aagaard]

Emanuele-

Thanks for the quick reply. It looks like you are using

   refine node in volume VOLUMEID numsplit 1 bias 1.0 depth 1

for your refinement. I am not sure this will be any different than the

   refine node in group GROUPID depth 1

which we have been using but we will give a try and see. We are also 
investigating whether breaking up a single refine command into multiple 
refine commands over smaller geometric regions will reduce the memory 
use; this will only help if the memory usage is proportional to the 
number of cells being refined and not the total number of cells.

Thanks,
Brad



On 01/21/2011 08:22 AM, emanuele casarotti wrote:
> Hi Brad,
>
> You can give a try to geocubit: a collection of Python script that Are
> in seismo repository (3D/specfem3d/*Emanuele/geocubit).
> I will add shortly the manual
>
> Regards
> Emanuele Casarotti
>
>
> On Friday, January 21, 2011, Brad Aagaard<baagaard at usgs.gov>  wrote:
>> Hi all:
>>
>> We are running into some issues generating large meshes (few million hex
>> cells) for PyLith using CUBIT. We want a mesh in which some regions have
>> a finer resolution mesh and have been using
>>
>> refine node in REFINEGROUP depth 1
>>
>> to refine the mesh in the desired regions. We appear to be running out
>> of memory on a machine with 16GB of RAM when the number of cells gets to
>> be more than about a few million.
>>
>> If anyone has experience generating a hex (or tet) mesh with 5-10
>> million cells or more using CUBIT in which some regions have a finer
>> resolution, I would appreciate learning what procedure you used and how
>> much memory was required.
>>
>> Thanks,
>> Brad
>> _______________________________________________
>> CIG-SEISMO mailing list
>> CIG-SEISMO at geodynamics.org
>> http://geodynamics.org/cgi-bin/mailman/listinfo/cig-seismo
>>
>