Changes between Version 16 and Version 17 of CodeChanges

Timestamp:

10/12/12 11:26:14 (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. {{{get_element_material_number_from_cloud()}}}[[BR]]
- This subroutine should create an array of {{{nelem}}} x {{{nmat}}} (?), fill that array with the number of cloud particles of a given material for each element and assign the element material number based on some criteria. In general, the procedure would be
+ 2. {{{find_material_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
   * Loop through all cloud particles
   * 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
-  * After looping through all cloud particles, loop through all elements
-  * For a given element, check associated material number distribution list
+ 3. {{{get_element_material_number_from_cloud.f90}}}[[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()}}})
   * Look for index of max value
-   * Look for 'ties'. Do a count on the value at the index found above. If that number is >1, we have a tie.
+  * Look for 'ties'. Do a count on the value at the index found above. If that number is >1, we have a tie.
   * Based on the info above, make a decision on which material number should be used (Things to consider: Majority rule, how to handle ties, etc.)
   * Call {{{make_matrix.f90}}} using the material number from the decision
+
 
 ''Record of code changes by routine''