Hi Alex,

>From what I know, the granular terrain or the related submodule Chrono::GPU 
is not wrapped in PyChrono. I'd mention that Chrono's DEM/granular support 
is moving towards being based on a new DEM package 
<https://github.com/uwsbel/DEM-Engine> that I'm working on, which can 
interface Chrono like its predecessor, but is faster and supports 
complex/various sized particles. You can have look at the movie of a 
simulation this solver generates 
<https://uwmadison.box.com/s/di19pxue36y6gtd1bn6nl3ay9tpvwbjk>. If this is 
something you are looking for, then we can discuss more details. This 
package however, is now in C++. Its Python wrapper is expected to be 
online, but it can take ~3 months.

About the "rectangle filled with particles" presentation, it is probably 
Chrono::Multicore, but I am not familiar with that.

Thank you!
Ruochun

On Wednesday, October 12, 2022 at 8:57:01 AM UTC-5 Alex S. wrote:

> Good morning! I am looking to implement a granular terrain using 
> PyChrono.  
>
> Searching through the demos/API, I see that several terrain types are 
> exposed in PyChrono (RigidTerrain, SCMDeformableTerrain, etc.), but I am 
> not able to find a function for initializing a granular terrain.  Is this 
> currently available in PyChrono?  
>
> Alternatively, I remember seeing a bullet point in one of the 
> ProjectChrono presentations that mentioned a helper method for initializing 
> a rectangle filled with particles that follow a specified particle size 
> distribution (for applications such as filling containers, etc.).  
> Unfortunately I seem to be unable to find this presentation again, but I 
> was wondering if this functionality currently available in PyChrono?
>
> Thank you for your help!
>

-- 
You received this message because you are subscribed to the Google Groups 
"ProjectChrono" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/projectchrono/1661f345-b236-4a77-8fa6-4c3758dea4a6n%40googlegroups.com.

Reply via email to