Fix nom_addLocalSectionDV in MPhys wrapper

[eytanadler]

Purpose

The parameters to addLocalSectionDV in the MPhys wrapper are passed without keyword arguments, which means they default to the order the keyword arguments were defined. As a result, the variables were getting mixed up when addLocalSectionDV was called and the answer was wrong.

This also fixes adding pointsets to children, which happens already in DVGeometry.addPointSet and doesn't need to be repeated in OM_DVGEO.nom_addPointSet.

Expected time until merged

1 day

Type of change

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (non-backwards-compatible fix or feature)
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no API changes)
• Documentation update
• Maintenance update
• Other (please describe)

Testing

Checklist

• I have run flake8 and black to make sure the Python code adheres to PEP-8 and is consistently formatted
• I have formatted the Fortran code with fprettify or C/C++ code with clang-format as applicable
• I have run unit and regression tests which pass locally with my changes
• I have added new tests that prove my fix is effective or that my feature works
• I have added necessary documentation

[A-CGray]

LGTM

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 67.04%. Comparing base (0cabf17) to head (8414c85).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #261      +/-   ##
==========================================
+ Coverage   67.03%   67.04%   +0.01%     
==========================================
  Files          47       47              
  Lines       12331    12326       -5     
==========================================
- Hits         8266     8264       -2     
+ Misses       4065     4062       -3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.