Skip to content

Clarification w.r.t FillBoundary vs. FillPatch #4112

@desjardi

Description

@desjardi

Hello,

I'm working on an amrcore-based code, taking heavy inspiration from the fortran ADVECTION_F example. In that example, the main scalar (phi) being solved is defined without ghost cells, but at each time step, a phiborder array is defined with ghost cells, and filled from phi data using FillPatch. I think that it makes sense to me: it's efficient and flexible.

I'm interested in another strategy, where phi itself is defined with some ghost cells. At the end of a time step, I can update the interior of phi, but would then need to update the ghost cells. It seems to me that FillBoundary may do that (i.e., focus on updating only the ghost cells while leaving the interior alone), but I'm not too sure how it works. I would expect it to fill ghost cells at a level based on both that level and a coarser level, and involving boundary conditions as well. Yet, the FillBoundary routine doesn't seem to be as rich as the FillPatch routine.

Basically, my question is: is there such a thing as a FillPatch routine which works only on the ghost cells? Or is there something fundamentally problematic with what I'm proposing to do?

Thanks a lot for any guidance on this!

Olivier

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions