Re: [Libmesh-users] Read/write solution vectors

[Paul T. B. <ptb...@gm...>]

Paper comes out after code. :)

On Tue, Nov 7, 2017 at 1:43 PM, Manav Bhatia <bha...@gm...> wrote:

> Very cool!
>
> Is there a paper you can point me to that discusses the foundations?
>
> -Manav
>
>
> On Nov 7, 2017, at 12:37 PM, Paul T. Bauman <ptb...@gm...> wrote:
>
>
>
> On Tue, Nov 7, 2017 at 1:33 PM, Manav Bhatia <bha...@gm...>
> wrote:
>
>> Aha!  Thanks for sharing this information.
>>
>> Are there any restrictions placed on the mesh type for this?
>> Structured/Unstructured?
>>
>
> Totally unstructured. (libMesh doesn't have any true structured
> representation after all. :) )
>
>
>> What about distribution of dofs? Like subdomain variables, etc.
>>
>
> This should all be fine. The main restriction is/will be that you cannot
> coarsen beyond the coarsest mesh you start with. So, the typical strategy
> will be to refine from your coarsest grid to generate the mesh hierarchy
> (uniform or adaptively refine). Part of this funding is also interacting
> with geometry, (but that will be over the next couple of years) so that you
> can start very coarse and then refine and respect the geometry.
>
>
>>
>> -Manav
>>
>> On Nov 7, 2017, at 12:11 PM, Paul T. Bauman <ptb...@gm...> wrote:
>>
>> On Tue, Nov 7, 2017 at 12:55 PM, Manav Bhatia <bha...@gm...>
>> wrote:
>>
>>>
>>> This is unrelated:  is there any activity concerning multigrid
>>> preconditioners within libMesh? I can certainly use Algebraic MG from
>>> PETSC, but what about geometric MG?
>>>
>>
>> Yes, we have a project going on this. We're debugging the pre-alpha
>> version and will be migrating into libMesh and generalizing (beyond H1
>> conforming elements) hopefully very soon. We will make a formal
>> announcement on the lists once it's more "beta" to help shake out the
>> interface for the users. It is being hooked into PETSc's DM infrastructure,
>> so PETSc will be required.
>>
>>
>>
>
>