** Attachment added: "Report"
https://bugs.launchpad.net/yade/+bug/1814052/+attachment/5234557/+files/report_v2.pdf
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1814052
Title:
** Attachment added: "Script"
https://bugs.launchpad.net/yade/+bug/1814052/+attachment/5234556/+files/simple_shear_bug.py
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1814052
Title:
makeCloud is a random generation of spheres [1]. Use the seed argument
if you want the same packing twice.
[1]https://yade-dem.org/doc/yade.pack.html
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
Hi,
On 1/31/19 9:28 AM, Jerome Duriez wrote:
What's this https://yade-dev.gitlab.io/trunk/ ?...
That's where the gitlab pipeline [1] is pushing the html generated from
master branch.
In fact the html output of *every* successful build can be accessed as
well (e.g. [2]), it was not the case
Hello,
Could it be related to that:
https://www.mail-archive.com/yade-dev@lists.launchpad.net/msg03562.html
even if you seem to use a single core?
Luc
Le 31/01/2019 à 10:47, Clerc Adriane a écrit :
> ** Attachment added: "Report"
>
>
I cannot find anywhere in your scripts where you are saving
scenes/packings, loading scenes/packings or resetting the scene.
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1814052
Title:
Hello,
> Sorry I forgot to underline the fact that my packing is the same for
each run.
please provide the exact script you are using. There is no packing loading in
the current script..
Or the information how you load the packing..
thanks
Jan
--
You received this bug notification because
Sorry I forgot to underline the fact that my packing is the same for
each run. I create it once and I load it 4 times, closing and opening
Yade between two runs.
** Attachment added: "packing"
https://bugs.launchpad.net/yade/+bug/1814052/+attachment/5234582/+files/simul_bug1
--
You received
Public bug reported:
In the framework of my PhD thesis, I use Yade and shear numerical simulations.
While using a script based on the periodic simple shear tutorial example given
on the web side, I noticed that my simulation is not reproducible : the
physical time, the controlling and the
Hi,
[1]https://yade-dev.gitlab.io/trunk/github.html?highlight=gitlab#pushing-changes-to-remote-repository
What's this https://yade-dev.gitlab.io/trunk/ ?...
Is our doc now located at that place, and no more at
https://yade-dem.org/doc/ ?...
Jérôme
--
Chargé de Recherche /
Please provide all necessary information to allow a developer to
reproduce your bug. For example, a running script, your method of yade
installation, and exact results that you are observing from said script.
--
You received this bug notification because you are a member of Yade
developers,
> Luc Sibille (luc-sibille) by one core I mean Yade is not running in
> parallel, so differences due to rounding in calculation should not
> exist, do they ?
Actually I cannot answer, I do not know sufficiently computers and Yade
(not sure for instance there are not any part of the computation in
>not running in parallel, so differences due to rounding in calculation
should not exist, do they ?
No.
That's why I closed, then re-opened the bug. :)
Let's see if someone can reproduce it.
Bruno
--
You received this bug notification because you are a member of Yade
developers, which is
I am able to reproduce the described behavior using both
makeCloud(seed=1) and regularHexa.
** Attachment added: "plots.zip"
https://bugs.launchpad.net/yade/+bug/1814052/+attachment/5234639/+files/plots.zip
--
You received this bug notification because you are a member of Yade
developers,
*In all cases I am executing yade -j1 mwe.py
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1814052
Title:
Unreproductible simulation (one core, one computer, one script) with a
tutorial example
Robert Caulk (rcaulk)and Jan Stránský (honzik), from the yade interface
the simulation can be saved and loaded, that is how I saved the initial
packing and I loaded it each time.
Luc Sibille (luc-sibille) by one core I mean Yade is not running in
parallel, so differences due to rounding in
Good finding (#14). Not a bug then, closing.
** Changed in: yade
Status: New => Invalid
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1814052
Title:
Unreproductible simulation (one core,
Public bug reported:
On newer linux versions the ipython keybindigs F12, F11,… to start
Controller, 3D View don't work.
This problem started for ipython versions above 5.0. We have a proposed
fix:
https://gitlab.com/yade-dev/trunk/merge_requests/51
But it behaves differently on each system
I think I have found the parameter which was making my simulation
unreproducible :
In the Pyrunner, the checker is working with "realtime"... I didn't know but
this the CPU time which can vary in function of how my computer is busy.
By replacing "realtime" by "iterPeriod", for a same packing
here is the packing
** Attachment added: "simple_shear_packing.py"
https://bugs.launchpad.net/yade/+bug/1814052/+attachment/5234712/+files/simple_shear_packing.py
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
20 matches
Mail list logo