Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Immersed boundary condition instead of forcing #130

Closed
wants to merge 784 commits into from

Conversation

simone-silvestri
Copy link
Collaborator

@simone-silvestri simone-silvestri commented Aug 13, 2024

To be merged only if the near-global example works with reasonable velocities

closes #128

simone-silvestri and others added 30 commits June 11, 2024 10:55
Co-authored-by: Gregory L. Wagner <wagner.greg@gmail.com>
Co-authored-by: Gregory L. Wagner <wagner.greg@gmail.com>
Co-authored-by: Gregory L. Wagner <wagner.greg@gmail.com>
Co-authored-by: Gregory L. Wagner <wagner.greg@gmail.com>
@simone-silvestri simone-silvestri added Run examples Add this label to generate docs with heavy GPU-accelerated examples 🚨 DO NOT MERGE 🚨 labels Aug 13, 2024
@glwagner
Copy link
Member

To be merged only if the near-global example works with reasonable velocities

closes #128

Why would it be different?

If its different there's a bug. We should also add a test to check for this this specifically in Oceananigans, since it has been discovered / is believed to be possible here.

@simone-silvestri
Copy link
Collaborator Author

The results here should tell us if this method works. A test in Oceananigans should definitely be added because it looks like this is untested

@glwagner
Copy link
Member

Why do you think it is possible they are different? Have you seen this before? Is there another example where this occurred?

@simone-silvestri
Copy link
Collaborator Author

I remember some time ago there was a problem with this method, but I would have to go back to look at what issue it was.
I guess it has been solved. I am being cautious because now that we have a global simulation running we don't want to break it so it is always good to look

  1. the wall time step per time step
  2. the validity of the of the outputs

@simone-silvestri simone-silvestri changed the title Immersed boudnary condition instead of forcing Immersed boundary condition instead of forcing Aug 13, 2024
@glwagner
Copy link
Member

I remember some time ago there was a problem with this method, but I would have to go back to look at what issue it was. I guess it has been solved. I am being cautious because now that we have a global simulation running we don't want to break it so it is always good to look

  1. the wall time step per time step
  2. the validity of the of the outputs

We shouldn't have to use such caution, because the code should not have so many bugs that things are so delicate. Can we figure out what the issue is? I don't think ImmersedBoundaryCondition has been developed lately. I'm not sure how the problem could have been solved.

Copy link

codecov bot commented Aug 13, 2024

Codecov Report

Attention: Patch coverage is 0% with 11 lines in your changes missing coverage. Please review.

Project coverage is 0.00%. Comparing base (41aa1e4) to head (4d580c0).
Report is 10 commits behind head on main.

Files with missing lines Patch % Lines
src/OceanSimulations/OceanSimulations.jl 0.00% 11 Missing ⚠️
Additional details and impacted files
@@          Coverage Diff          @@
##            main    #130   +/-   ##
=====================================
  Coverage   0.00%   0.00%           
=====================================
  Files         31      31           
  Lines       1740    1742    +2     
=====================================
- Misses      1740    1742    +2     

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

@simone-silvestri
Copy link
Collaborator Author

@glwagner
Copy link
Member

This PR lists 29 files changed but the title just states that bottom drag was implemented with ImmersedBoundaryCondition vs Forcing. Why are so many files changed?

@simone-silvestri
Copy link
Collaborator Author

because we have to merge the documentation PR


u_immersed_bc = ImmersedBoundaryCondition(bottom = u_immersed_drag)
v_immersed_bc = ImmersedBoundaryCondition(bottom = v_immersed_drag)
Copy link
Member

Choose a reason for hiding this comment

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

this is the only change I expected to see

@glwagner
Copy link
Member

There are 783 commits on this PR

@glwagner
Copy link
Member

Then put this PR to merge into that PR, not main

@simone-silvestri
Copy link
Collaborator Author

oops too late, I ve merged the documentation PR

@glwagner
Copy link
Member

glwagner commented Aug 14, 2024

Still 784 commits here. Maybe open a new PR with just the changes needed here?

@glwagner
Copy link
Member

glwagner commented Sep 5, 2024

@navidcy any idea why the preview for this isn't showing? Or where it might be?

@simone-silvestri
Copy link
Collaborator Author

Closed in favor of the new PR

@glwagner glwagner deleted the ss/immered-boundary-condition branch September 17, 2024 17:59
@glwagner glwagner restored the ss/immered-boundary-condition branch September 17, 2024 17:59
@glwagner
Copy link
Member

delete the branch?

@simone-silvestri simone-silvestri deleted the ss/immered-boundary-condition branch September 17, 2024 18:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🚨 DO NOT MERGE 🚨 Run examples Add this label to generate docs with heavy GPU-accelerated examples
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Why is bottom drag implemented as a forcing rather than ImmersedBoundaryCondition?
3 participants