@giuseppe.bilotta Thanks for your help! One last thing on this subject…
I was following the logic presented in the “DEMExample.cu” where it appears to follow the “geometric” approach. The framework is set to “ENABLE_DEM” and the DEM is added using “addDEM”, “addDEMFluidBox”, etc. In this case, you are correct in saying that it is only supported with the “LJ_BOUNDARY” model. This was a “bug” that I reported because I personally don’t think the DEM concept should not be limited to a specific boundary.
That being said, I was originally working with the “DUMMY_BOUNDARY” (no DEM) and I did notice that the boundary is a bit smoother. I would like to continue to use this boundary model, but I also require a DEM. You said above that there is another way to implement the DEM? In my experience, I get critical errors if I don’t “ENABLE_DEM” while calling other DEM routines. Can you elaborate a bit more on how I can create the DEM using method 2 you mentioned? I know what “FT_BORDER” does, but I don’t know what routine to pass this to. I should reiterate that my DEM can not be built from primitives, hence why I’m trying to use this functionality. If I can get the DEM to work with the “DUMMY_BOUNDARY”, it would be great.