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

DEMExample does not work with SPS viscosity #54

Open
erikvanettinger opened this issue Sep 25, 2019 · 3 comments
Open

DEMExample does not work with SPS viscosity #54

erikvanettinger opened this issue Sep 25, 2019 · 3 comments

Comments

@erikvanettinger
Copy link

DEMExample does not work with SPS viscosity. Particles are leaving the domain for no known reason.

@saltynexus
Copy link

Did you make any progress on this? If yes, please share. If no, can elaborate? Are you only changing the viscosity?

@erikvanettinger
Copy link
Author

erikvanettinger commented Feb 6, 2020 via email

@saltynexus
Copy link

I know this doesn't fix your problem, but I've been recently implementing a DEM and found some difficulties as well. Long story short, I got a reply back from Giuseppe Bilotta over on the GPU discourse (https://gpusph.discourse.group/t/dem-in-combination-with-other-geometries/99/5) and I was informed on how the DEM is constructed

One ways is “geometrically”: it doesn’t get filled with particles, but you need the ENABLE_DEM flag for the framework.

I don't know much about the SPS viscosity or how you're trying to use it, but I found when I tried to use an incompatible boundary model with the DEM, the particles fell through as well. To fix my problem, I had to choose a supported boundary model. So yes, it could very well be that the SPS viscosity is incompatible. However, there's hope in the near future. Giuseppe mentions that the DEM should theoretically be able to be modeled using particles instead of planar geometry. I know this would permit me to use the boundary model I'm interested in and it might also permit you to use the SPS viscosity. That being said, it was unclear to me if this feature is currently available or on the TODO list.

You can read more in the link I provided above and possibly express you interest in resolving the issue as well. That is assuming we share the same problem. The more people that share a common problem, the more likely it will move up the TODO list.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants