-
Notifications
You must be signed in to change notification settings - Fork 44
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
Subsurface spill #127
Comments
Thanks for testing this! I confess that these features have not had the testing they deserve, but should work. However, we recently had some updates to the gridded package that may have improved this. @jay-hennen: was the bug with elements being both subsurface and on the surface fixed in gridded? So the first step is to make sure you have up to date code: be sure to use the main branch at this point. Then make sure that you've updated the requirements. Moving on to the issues:
The only thing that should move them up is the RiseVelocity Mover -- try running with only that, and/or with it turned off, to see where the problem is.
If you have massive vertical movement, then you may not see the vertical diffusion at all.
They should never leave the surface. and with surface_is_allowed=False, they should reach the surface and then stay there.
That should be reasonable. What time step are you using? Suggestions for debugging:
|
Dear Chris, Thank you for your feedback. I use the main branch (installed about 2 weeks ago) and I have updated all the requirements, as suggested. The first experiment was turning off all the movers and random walks, including the rise velocity. The particles (n=10) were released at 50 m depth and remain in the same (x,y) spot during the 2-day simulation, as expected, but surprisingly, they all go upward instantaneously, from 50 to 0 m depth, despite no rise velocity was set (see panel a). The time step is 60 minutes. Later I will post the script and the associated files. Thanks again! |
well, that sure seems like a bug! When you post your scripts, we'll take a look.
and that too :-( Stay tuned. |
Hello Chris, https://drive.google.com/drive/folders/1Q6c_m49_x8ffBbHcEaEdfpyMyIyFY6II?usp=sharing |
One issue I noticed is your depth value is negative. The spill depth needs to be positive, |
@coconnor8 Thank you for the contribution! I have two more doubts about this subsurface spill case. The second doubt is regarding the weathering processes. When I activate them I obtained the following error: *The same code and files can be used to try to reproduce them. Thank you! |
The first one looks like a bug on our end. The water density was removed from the class but not from the schema. |
Hello everyone!
I am wondering if something is missing when running a subsurface oil spill case. I obtained the same solution whether the particles were released at 18 or 100 m depth (or even any depth). Actually, the particles upwelled instantaneously to the surface despite tridimensional currents were provided (Please, check the figure below).
In addition, the figure below shows the map of trajectories until two days after the oil spill added with the RiseVelocityMover and Random_Mover_3D. As seen, in the left panel (with surface_is_allowed=True), the same exact path is obtained when compared with the previous figure when these two options weren't enabled. Whereas in the right panel (surface_is_allowed=False), it seems that all particles go upward "bouncing in the air". (btw, vertical_diffusion_coef_above_ml=10)
Could you please provide me with more details about the situation I have just described?
On the other hand, when I try to include weathering processes I obtained the following warning:
"....spreading.py:665: RuntimeWarning: invalid value encountered in double_scalars
thickness = (data['bulk_init_volume'][s_mask][0] /"
and when I check the .csv output file there are only zero values regarding the quantity evaporated, dispersed, and sedimentation.
However, when I use surface_point_line_spill rather than subsurface_plume_spill, it runs smoothly. Any thoughts?
Thank you in advance
Regards
Rodrigo M.
The text was updated successfully, but these errors were encountered: