Skip to content

Commit 51666e9

Browse files
minor punctuation fixes
1 parent 3ab7a52 commit 51666e9

1 file changed

Lines changed: 5 additions & 4 deletions

File tree

src/docs/sphinx/blueprint_mesh.rst

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -619,7 +619,7 @@ To find out what the volume fractions are for each material for a specific eleme
619619
For example, for element 0, we take the 0th index of each array: ``background`` has a value of ``1.0``, ``circle_a`` has a value of ``0.0``, ``circle_b`` has a value of ``0.0``, and ``circle_c`` has a value of ``0.0``. To determine if a material is in a element, we must check that it has a nonzero volume fraction for that element. Therefore, we can infer that element 0 is 100% the ``background`` material, and the other materials are not present.
620620

621621
If we want to see the volume fractions for element 10, we go to the 10th index of each array: ``background`` has a value of ``0.0``, ``circle_a`` has a value of ``0.333333333333333``, ``circle_b`` has a value of ``0.333333333333333``, and ``circle_c`` has a value of ``0.333333333333333``.
622-
Therefore we can infer that element 10 is evenly split between the circle materials and there is no ``background`` material present.
622+
Therefore, we can infer that element 10 is evenly split between the circle materials and there is no ``background`` material present.
623623

624624
If we want to know the material ids of the materials in a specific element, we can examine the material map entry for each material in that element that has a volume fraction greater than ``0.0``.
625625
If no material map is present, we can infer the material id from the order of the material volume fraction arrays under the ``volume_fractions`` node.
@@ -1032,7 +1032,7 @@ This will create an output with the following information:
10321032
* mix_spec
10331033
* mixlen
10341034

1035-
Conduit also provides tools for creating/fetching material maps:
1035+
Conduit Blueprint also provides tools for creating/fetching material maps:
10361036

10371037
.. literalinclude:: ../../libs/blueprint/conduit_blueprint_mesh.hpp
10381038
:start-after: _matset_create_matmap_methods_start
@@ -1105,7 +1105,7 @@ This produces the following:
11051105
matset accessor 4 has field
11061106
matset accessor 4 has specset
11071107
1108-
We can also ask about general matset information:
1108+
We can also ask about general ``matset`` information:
11091109

11101110
.. code:: cpp
11111111
@@ -1126,7 +1126,7 @@ We can also ask about general matset information:
11261126
index_t num_mats = m_acc.num_mats();
11271127
11281128
Once we start writing loops over elements and materials, the indices of those loops matter.
1129-
An element index means something different depending on what matset layout we are working with, as does a material index.
1129+
An element index means something different depending on what ``matset`` layout we are working with, as does a material index.
11301130

11311131
* For a **multi-buffer** **element-dominant** material set
11321132

@@ -1156,6 +1156,7 @@ Here is an example of walking a material set and performing data retrieval using
11561156
.. code:: cpp
11571157
11581158
// for some matset `matset`, field `field`, and specset `specset`
1159+
11591160
MatsetAccessor m_acc = MatsetAccessor(matset, field, specset);
11601161
11611162
if (m_acc.is_element_dominant() && m_acc.is_multi_buffer())

0 commit comments

Comments
 (0)