yade-users team mailing list archive

[matthias <question233320@xxxxxxxxxxxxxxxxxxxxx>]

Question #233320 on Yade changed:
https://answers.launchpad.net/yade/+question/233320

matthias  posted a new comment:
i think at this point, we should examine the impact of that data types.
so please propose somewhat like a model, number of spheres and
iterations,...

this is my proposal : 
- maybe 5000 sphere are flowing out of an hopper over maybe 150000 iterations.  not more sphere because of computation time.
- defining a objective Function. this function must defined on all spheres, if its depends on only some sphere, the functions values are too noisy. the values of #25 ware generated in the following way: 
i defined a plane a little bit below the hopper. every i iterations (for i  \in {1...50}) is measure which sphere passed the plane and store that timestamp (or iteration number). in the end of a run i calculate the std-dev on this set. 

\                 / 
 \******/
  \*****/
   \****/
    \***/
      **
  -------    <- measure timestamp here
     ++

this objective function should represent how 'compact' the spheres are
flowing out.

during a run could Fmean logged or somelike other...
maybe 50 or 100 replications per data type (wich 2 threads, because more threads have too much overhead [and 8 threads are much slower then 4 threads, using real parallel algorithms are a quiet good idea]) should be enough.

what do you think about this?

-- 
You received this question notification because you are a member of
yade-users, which is an answer contact for Yade.