Material utility operations namespace

[ezrayst]

Response to #587. Computations and tests for:

• [x] mean p
• [x] deviatoric stress
• [x] deviatoric q
• [x] J2
• [x] J3
• [x] Lode angle theta
• [x] dp_dsigma
• [x] dq_dsigma
• [x] dj2_dsigma
• [x] dj3_dsigma
• [x] dtheta_dsigma

Upcoming work for next PR:

• [ ] Refactor NorSand
• [ ] Refactor Modified Cam Clay
• [ ] Refactor Mohr Coulomb

[codecov[bot]]

Codecov Report

Merging #600 into develop will increase coverage by 0.03%. The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           develop     #600      +/-   ##
===========================================
+ Coverage    96.82%   96.85%   +0.03%     
===========================================
  Files          116      118       +2     
  Lines        24860    25092     +232     
===========================================
+ Hits         24069    24301     +232     
  Misses         791      791              

Impacted Files	Coverage Δ
include/materials/material.h	100.00% <ø> (ø)
include/materials/material_utility.tcc	100.00% <100.00%> (ø)
tests/materials/material_utility_test.cc	100.00% <100.00%> (ø)
tests/functions/sin_function_test.cc	95.65% <0.00%> (-0.64%)	:arrow_down:
src/functions/sin_function.cc	100.00% <0.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update ce4008e...3fb832a. Read the comment docs.

[ezrayst]

I think I have addressed all the comments. Now, the namespace is called material but the file is still called material_utility.

Throwing some ideas here: material_functions, material_operations, materials (with s) if you want something short.

[ezrayst]

@kks32, how about the namespace name? should we keep them as material and the filenames as material_utility?

[kks32]

I'd go with materials for namespace and keep the filename as material_utilities.h?

[ezrayst]

Understood.