Skip to content

sedimentation removal dynamic (for 0-d environments)#1722

Open
slayoo wants to merge 24 commits into
open-atmos:mainfrom
slayoo:deposition_removal
Open

sedimentation removal dynamic (for 0-d environments)#1722
slayoo wants to merge 24 commits into
open-atmos:mainfrom
slayoo:deposition_removal

Conversation

@slayoo
Copy link
Copy Markdown
Member

@slayoo slayoo commented Sep 30, 2025

No description provided.

@codecov
Copy link
Copy Markdown

codecov Bot commented Sep 30, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 87.05%. Comparing base (b688e1b) to head (a688815).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1722      +/-   ##
==========================================
+ Coverage   86.99%   87.05%   +0.05%     
==========================================
  Files         418      420       +2     
  Lines       10692    10739      +47     
==========================================
+ Hits         9302     9349      +47     
  Misses       1390     1390              

☔ 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.

@slayoo slayoo changed the title deposition removal dynamic (for 0-d environments) sedimentation removal dynamic (for 0-d environments) Sep 30, 2025
@github-actions
Copy link
Copy Markdown

Stale pull request message

@slayoo slayoo marked this pull request as ready for review May 30, 2026 14:28
builder.request_attribute("relative fall velocity")
assert builder.particulator.environment.mesh.n_dims == 0
self.particulator = builder.particulator
self.length_scale = np.cbrt(self.particulator.environment.mesh.dv)
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tluettm, in the Parcel environment, the dv is time-dependent, while here we use it in the register() method, hence only once at the start of the simulation. It is likely OK given this is just to derive a length scale, but I winder if not to move it to __call__ to avoid misleading location of this logic?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants