Continuous kludge to keep pdivt > 0

[jonmaddock]

Ensure pdivt is kept positive continuously.

pdivt with continuous kludge:

And again, but with finer sampling resolution to show continuous nature:

[codecov-commenter]

Codecov Report

❌ Patch coverage is 0% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 31.21%. Comparing base (0ace3f9) to head (6262e53).
⚠️ Report is 469 commits behind head on main.

Files with missing lines	Patch %	Lines
process/physics.py	0.00%	1 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3579   +/-   ##
=======================================
  Coverage   31.21%   31.21%           
=======================================
  Files          83       83           
  Lines       19938    19938           
=======================================
  Hits         6223     6223           
  Misses      13715    13715           

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[mkovari]

I am bit concerned that you are redefining pdivt. If this code is ever run again then this change could be made repeatedly. Is there any chance of this happening?

[jonmaddock]

I am bit concerned that you are redefining pdivt. If this code is ever run again then this change could be made repeatedly. Is there any chance of this happening?

I'm not quite sure what you mean; if you mean non-idempotence, then this isn't an issue: each time the model is called (with the same values) pdivt is calculated from other values (in the lines immediately above this change) and this kludge is applied. The same value of pdivt results each time. Does that answer your question?