You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Update ghost cells after initialization (as opposed to assuming that initialization routines fill in ghost cells).
Supply stencil width as parameter - needed for optimizing packing and time interpolation.
Pass area and other metric terms across proc boundaries? Or recreate on the other side?
Which metric terms to compute? (for example, don't compute curvature on flat domain)
Avoid regridding machinery in the uniform case
Interpolation stencils do not require corner values
Solution update does not require corners
Use Gaussian quadrature to compute areas, or use bilinear approximation.
Turn off limiting in interpolation to check for invalid data in ghost cells.
Initialize all grid data to NANS (useful for debugging).
Minimum time step taken to complete time step for out style 1.
Output before or after regridding? i.e. Output on grid just used for last step, or on newly created grids for next step?
More flexibility in how to report errors. In addition to indicating whether or not to compute the error, the user should be able to supply number of error fields to compute (m_err?) Extra storage will be created only for these fields.
Supply method for adding additional variables to output files?
Generic debug option that the user can use to trigger debugging code.
Originally reported by: Donna Calhoun (Bitbucket: donnaaboise, GitHub: donnaaboise)
Several advanced options should be included :
The text was updated successfully, but these errors were encountered: