--
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 projectchron...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/projectchrono/730e41ac-b7d2-40cd-96da-a5472f9cbc1cn%40googlegroups.com.
Hi Ruochun,Thank you very much for the speedy and informative response. If/when I end up trying this, I will post any findings here. Apologies for another question, but has there been any parallelization testing on CPUs? If so, what were the results? Thanks in advance!All the best,Jared
Jared,
A couple of quick observations.
What you are asking for is not directly related to Chrono. This type of parallelization is what’s called HTC (high throughput computing) as opposed to HPC (high performance computing). The way you set up the multiple, independent parallel runs (multi-processing) to cover the “design space” is first and foremost dependent on the hardware you have available. The actual simulation software you use for these parallel runs (Chrono in this case) comes into play only insofar as you need to understand the resource requirements (cores, GPUs, memory, etc.) of each instance and how to best distribute the runs over the existing hardware so that you minimize contention for the same resource.
For Chrono-based simulations, the answer to the question above will depend on which Chrono module(s) you are using and the particular type of problem you are solving. We have done this in the past, with both CPU- and GPU-based Chrono modules, typically by running this on clusters (there’s only so much one can do with the hardware resources available on a desktop).
--Radu
--