Changes between Version 19 and Version 20 of CodeChanges

Timestamp:

11/16/12 09:58:57 (12 years ago)

Author:

dv615747

Comment:

--

CodeChanges

@@ -18 +18 @@
   * In not, do nothing
   * Should surfaces that are flagged for removal be removed within this subroutine or outside of it??? Should the corresponding LSFs be removed as well, and should {{{params%ns}}} be redefined to be the original value minus the number of removed surfaces???
- 2. {{{find_material_numbers_from_cloud()}}}[[BR]]
+ 2. {{{find_mat_numbers_from_cloud()}}}[[BR]]
  This subroutine should create an array of {{{nelem}}} x {{{nmat}}} (?) and fill that array with the number of cloud particles of a given material for each element. In general, the procedure would be
   * Allocate an array that is {{{nelem}}} x {{{nmat}}} (or {{{nelem}}} x {{{nlsf}}}???); initialize to zero
@@ -24 +24 @@
   * Find which element contains a given particle
   * Increment the material number index for the element in the 2D array created above using the cloud particle material number
- 3. {{{get_element_material_number_from_cloud()}}}[[BR]]
+ 3. {{{get_element_mat_number_from_cloud()}}}[[BR]]
  This subroutine will operate on a given element (called from {{{make_cut.f90}}}??) to assign the element material number based on some criteria. The procedure would be
   * For a given element, check associated material number distribution list (from {{{find_material_numbers_from_cloud()}}})