Lines of Code
[root]/Core/Grid/BoundaryConditions
| Author | Changes | Lines of Code | Lines per Change |
|---|---|---|---|
| Totals | 103 (100.0%) | 1161 (100.0%) | 11.2 |
| tsaad | 55 (53.4%) | 1046 (90.1%) | 19.0 |
| jas | 39 (37.9%) | 47 (4.0%) | 1.2 |
| harman | 3 (2.9%) | 38 (3.3%) | 12.6 |
| dav | 2 (1.9%) | 23 (2.0%) | 11.5 |
| jthornoc | 4 (3.9%) | 7 (0.6%) | 1.7 |
Warnings.
1 lines of code changed in 2 files:
memory leak cleanup
0 lines of code changed in 2 files:
add a test for interior boundary conditions. cleanup a few cout statements.
1 lines of code changed in 3 files:
Add support for specifying interior boundaries through the Uintah interface. A great use of this is to attach surface boundaries to intrusions.
usage:
* To specify an interior boundary through the input file, use the <InteriorFace> xml block. This is identical to the <Face> specification used for domain boundaries. Example:
<InteriorFace ellipse="x-" origin="0.2 0.5 0.5" major_radius="0.2" minor_radius="0.05" angle="270" name="my boundary">
<BCType var="Dirichlet" label="f" value="10.0"/>
</InteriorFace>
* The minus/plus face spec will determine which cell iterator is returned. For a minus spec, the iterator will return the cells that are to the minus side of the interior boundary. The opposite is true for a plus spec
* TO access the cell iterator, use: Patch::getInteriorBndBCDataArray(Patch::FaceType face). All other access methods used domain boundaries remain the same. See Wasatch::BCHelper.cc for a great example of how to access the BC data associated with an interior boundary
* Interior boundaries currently support all boundaries supported by the existing interface (except for a side boundary - use rectangle instead): rectangle, circle, annulus, ellipse.
Limitations:
* Does NOT handle unions/differences. While support for those can be added later, there is no clear way on how to combine boundaries with different boundary conditions. Note that this limitation also applies to the current domain boundary conditions.
* Interior boundaries MUST be parallel to domain boundaries. For example, you cannot specify an inclined interior boundary.
Algorithmic details:
For a given grid resolution, the interior boundary is moved to the closest face (or layer of nodes parallel to that boundary). If the interior
boundary coincides with a cell center, then it is moved to the face side (minus/plus) that is
specified through the input file. The face side (minus/plus) determines which cell iterator is
returned. For a minus boundary, the cells on the minus side are returned. For a plus boundary,
the cells on the plus side are returned.
864 lines of code changed in 31 files:
kill the virus that is causing the buildbot to fail. This complements my previous commit.
1 lines of code changed in 1 file:
here's another shot at fixing the boundary condition geometry objects. This is supposed to fix the leak. Note that the MPMICE burners may still fail.
18 lines of code changed in 2 files:
Revert "delete BCGeom objects from patches that they don't belong to. This gives us an extra level of security against using empty boundary iterators."
This reverts commit dbd3c523046bcc8ac5adf4d626b0aacab7fb838d.
0 lines of code changed in 2 files:
delete BCGeom objects from patches that they don't belong to. This gives us an extra level of security against using empty boundary iterators.
17 lines of code changed in 2 files:
1. Fix memory leak in ParticlesHelper.
2. Allow BCData to return a pointer to the BCValues to avoid a deep copy (which has caused another memory leak). getBCValues now returns a const pointer to the bc values. cloneBCValues is now used to indicate a deep copy is taking place.
Thanks to Jeremy for catching these leaks. This should fix the memory leaks in the Arches RT.
31 lines of code changed in 5 files:
This is a very minor commit.
M Core/Grid/Level.h
M Core/Parallel/Parallel.h
- Fix indentation.
M Core/Grid/BoundaryConditions/BCGeomBase.h
M Core/Grid/BoundaryConditions/BCGeomBase.cc
- Fix white space, line up variables.
- Remove 'const' from several return values as it doesn't make sense and icc gives a warning.
- All arguments for determineIteratorLimits() should be const (as none of them change or return anything).
- Remove superfluous ;s after some function definitions.
- Plase "template<>" on the preceding line from "class" per standard and consistency.
23 lines of code changed in 2 files:
allow BCGeomBase to store, compute, and return its surface area on the current patch. No reductions yet to compute total surface area across patches.
9 lines of code changed in 2 files:
This commit provides support for adding particles through boundaries using the ParticlesHelper and classic Uintah BC machinery. You will need to invoke two key functionalities in the ParticlesHelper:
(1) ParticlesHelper::needs_boundary_condition: a static function call to add the variables that require a boundary condition. These are the transported particle variables such as velocity, mass, size...
(2) ParticlesHelper::schedule_add_particles: make sure you call that AFTER ParticlesHelper::schedule_particle_relocation. This will add particles on a boundary as specified through the input file. The particles are placed randomly in the first interior cell of the domain, at the required boundary (circle, rectangle, face...).
We currently only support constant boundary values for the remaining particle variables. Support for other distribution will follow in the near future as I'd like it to provide a unified and easy to use interface through the input file.
2 lines of code changed in 1 file:
Add support for specifying boundary condition on Particles through the Uintah BC interface. This will set the stage for specifying particle injection through boundaries.
(1) Add appropriate ups_spec for Particle boundary conditions
(2) Add a struct to BCGeomBase to store particle-related specification
(3) propagate this information through Wasatch
(4) Add support for inelastic and partially elastic walls in Wasatch
103 lines of code changed in 4 files:
Fix memory leak.
18 lines of code changed in 1 file:
Reversing the previous delete. This was causing segfaults in other
tests. However, valgrind is reporting it still as a "leak". I believe
the RT will as well.
Cleaning up some memory issues in other parts of Arches.
1 lines of code changed in 1 file:
Cleaning up memory errors.
5 lines of code changed in 1 file:
is_BC_specified()
-fixed copy paste error when checking if both a periodic BC and a normal BC has been specified
0 lines of code changed in 2 files:
Updated copyright information.
29 lines of code changed in 38 files:
is_BC_specified() & BC_bulletproofing()
fixed flawed logic when circles/rectangles/annulus were
used in conjunction with a side.
38 lines of code changed in 1 file: