rho # copy over the data so that the code has the correct # boundary values channel = memxbound1. copy () # just set all cells in the grid to the same values memxbound1. get_boundary_grid ( 'xbound1' ) # copy the grid to memory, so we can manipulate it easier memxbound1 = xbound1_grid. x_boundary_conditions = ( "interface", "outflow" ) # request the boundary grid # it will have shape of 4 x 20 x 10 (x, y, z) # as Athena has a 4 cell boundary depth xbound1_grid = instance. The z-axis boundary on the back side of the grid, often calledįrom amuse.lab import * instance = Athena () instance. The z-axis boundary on the front side of the grid, often called The y-axis boundary on the top side of the grid, often called The y-axis boundary on the bottom side of the grid, often called The x-axis boundary on the right side of the grid, often called The x-axis boundary on the left side of the grid, often called
The following picture shows all three boundary conditions for a oneīoundary conditions are defined by setting a boundary parameter forĮach boundary of the grid of a code. Sets the derivative of the flow variables with respect to the Implemented by copying the data of the cells connected to theīoundary into the boundary cells. Mirrors all grid variables in the boundary cells, often Opposite site of the grid to the boundary cells. Itself, often implemented by copying over the data at the Periodic boundaryĬonditions simulates as if the grid is connected to a copy of
To simulate periodically repeating problems. Each code in amuse will need to provide at least 3 kinds of boundary
0 kommentar(er)
