Fix semantics of permeability assignment
Calling code relies on permeability tensors being stored in column major order (row index cycling the most rapidly). Honour that requirement. The previous assignment implied row major ordering (column index cycling the most rapidly). This, however, is a pedantic rather than visible change because the surrounding code enforces symmetric tensors whence both orderings produce the same results when the array is viewed contiguously.
This commit is contained in:
parent
fd57d547a7
commit
194b6eda7a
@ -126,7 +126,7 @@ namespace Opm
|
||||
for (int i = 0; i < dim; ++i) {
|
||||
for (int j = 0; j < dim; ++j, ++kix) {
|
||||
// K(i,j) = (*tensor[kmap[kix]])[glob];
|
||||
permeability_[off + kix] = (*tensor[kmap[kix]])[glob];
|
||||
permeability_[off + (i + dim*j)] = (*tensor[kmap[kix]])[glob];
|
||||
}
|
||||
// K(i,i) = std::max(K(i,i), perm_threshold);
|
||||
permeability_[off + 3*i + i] = std::max(permeability_[off + 3*i + i], perm_threshold);
|
||||
|
Loading…
Reference in New Issue
Block a user