?
(input parameters are the same for both programs ... see
caller_two-spheres-jumping.dat for PFC and two-spheres.py for YADE)
Regards,
Christian Jakob
To manage notifications about this bug go to:
https://bugs.launchpad.net/yade/+bug/806944/+sub
flyback height, then in YADE (see log-files
in the attachment).
Can someone tell me why there is a difference in the flyback height?
(input parameters are the same for both programs ... see
caller_two-spheres-jumping.dat for PFC and two-spheres.py for YADE)
Regards,
Christian Jakob
** Affects
for both programs ... see
caller_two-spheres-jumping.dat for PFC and two-spheres.py for YADE)
Regards,
Christian Jakob
To manage notifications about this bug go to:
https://bugs.launchpad.net/yade/+bug/806944/+subscriptions
___
Mailing list: https
values of flyback height, then in YADE (see log-files
in the attachment).
Can someone tell me why there is a difference in the flyback height?
(input parameters are the same for both programs ... see
caller_two-spheres-jumping.dat for PFC and two-spheres.py for YADE)
Regards,
then in YADE (see log-files
in the attachment).
Can someone tell me why there is a difference in the flyback height?
(input parameters are the same for both programs ... see
caller_two-spheres-jumping.dat for PFC and two-spheres.py for YADE)
Regards,
Christian Jakob
To manage notific
r both programs ... see
caller_two-spheres-jumping.dat for PFC and two-spheres.py for YADE)
Regards,
Christian Jakob
To manage notifications about this bug go to:
https://bugs.launchpad.net/yade/+bug/806944/+subscriptions
___
Mailing list: https://
the attachment).
Can someone tell me why there is a difference in the flyback height?
(input parameters are the same for both programs ... see
caller_two-spheres-jumping.dat for PFC and two-spheres.py for YADE)
Regards,
Christian Jakob
To manage notifications about this bug go to:
https
caller_two-spheres-jumping.dat for PFC and two-spheres.py for YADE)
Regards,
Christian Jakob
To manage notifications about this bug go to:
https://bugs.launchpad.net/yade/+bug/806944/+subscriptions
___
Mailing list: https://launchpad.net/~yade-dev
Post
FC and two-spheres.py for YADE)
Regards,
Christian Jakob
To manage notifications about this bug go to:
https://bugs.launchpad.net/yade/+bug/806944/+subscriptions
___
Mailing list: https://launchpad.net/~yade-dev
Post to : yade-dev@lists.lau
in the attachment).
Can someone tell me why there is a difference in the flyback height?
(input parameters are the same for both programs ... see
caller_two-spheres-jumping.dat for PFC and two-spheres.py for YADE)
Regards,
Christian Jakob
To manage noti
parameters are the same for both programs ... see
caller_two-spheres-jumping.dat for PFC and two-spheres.py for YADE)
Regards,
Christian Jakob
To manage notifications about this bug go to:
https://bugs.launchpad.net/yade/+bug/806944/+subscriptions
height?
(input parameters are the same for both programs ... see
caller_two-spheres-jumping.dat for PFC and two-spheres.py for YADE)
Regards,
Christian Jakob
To manage notifications about this bug go to:
https://bugs.launchpad.net/yade/+bug/806944/+subscriptions
calculations were performed during this speed test. The same
geometries, parameters and model specifications were used for both
programs.
With kind regards,
Christian Jakob
TU Bergakademie Freiberg
Institut für Geotechnik / Geotechnical Institute
Gustav-Zeuner-Str. 1,
D-09596 Freiberg / Germany
** Attachment added: "python script to reproduce yade crash"
https://bugs.launchpad.net/bugs/845456/+attachment/2375764/+files/macropore.py
--
You received this bug notification because you are a member of Yade
developers, which is the registrant for Yade.
https://bugs.launchpad.net/bugs/8454
Public bug reported:
Hi,
I want to delete some particles to create a macropore within a particle cloud.
This is done with O.bodies.erase(ID) and works well for hertz model.
The crash occurs, when calculation starts again after deleting a body with the
capillary model (CapillaryPhys).
Regards,
GREAT! It works now, thank you very very much!
Zitat von Anton Gladky <845...@bugs.launchpad.net>:
> Christian,
>
> could you, please, check r2931?
> It should be fixed there.
>
> Anton.
>
> ** Changed in: yade
>Importance: Wishlist => Medium
>
> ** Changed in: yade
>Status: Confirme
Public bug reported:
Now I am using yade version bzr-2958 and the bug, that was fixed by version
bzr-2931 occurs again.
See here:
https://bugs.launchpad.net/yade/+bug/845456
christian
** Affects: yade
Importance: Undecided
Status: New
--
You received this bug notification becaus
@bruno: i will try that
@anton: yes
--
You received this bug notification because you are a member of Yade
developers, which is the registrant for Yade.
https://bugs.launchpad.net/bugs/891540
Title:
yade crash after deleting body with capillary model (again)
Status in Yet Another Dynamic Eng
Ok, I found out, that the script from #845456 works with
O.dt=0.5*utils.PWaveTimeStep()
, but not with this engine:
GlobalStiffnessTimeStepper(active=1,timeStepUpdateInterval=5,timestepSafetyCoefficient=0.8,
defaultDt=4*utils.PWaveTimeStep()),
(segmentation fault)
--
You received this bug not
It is fixed! Thank you very much, Anton!
Have a nice weekend.
--
You received this bug notification because you are a member of Yade
developers, which is the registrant for Yade.
https://bugs.launchpad.net/bugs/891540
Title:
yade crash after deleting body with capillary model (again)
Status
Public bug reported:
If I set neverErase=True Yade crashes with following output:
O.run(3000,True)
Runtime
** Attachment added: "dont forget to copy the 10 files for CapillaryPhys to the
place where you start the script"
https://bugs.launchpad.net/bugs/897237/+attachment/2611278/+files/macropore_neverErase.py
--
You received this bug notification because you are a member of Yade
developers, which
While using O.dt=0.5*utils.PWaveTimeStep() instead of GSTS I get
1681 FATAL yade.ThreadRunner /home/me/YADE/yade/core/ThreadRunner.cpp:31 run:
Exception occured:
Body #0 has velocity=
I tried to fix the kn and ks:
if (uN<0) {
if (neverErase) {
phys->kn = 0.0;
phys->ks = 0.0;
phys->shearForce = phys->normalForce = Vector3r::Zero();
}
else {scene->interactions->requestEra
thank you very much anton, i get some error messages, but it works.
3945 ERROR yade.InteractionContainer
/home/me/YADE/yade/core/InteractionContainer.cpp:55 erase:
InteractionContainer::erase: attempt to delete non-existent interaction
##43+380
3945 ERROR yade.
I tried another script without facets (using aabbWalls) and without changing
particle radii,
it crashes after 5 or 6 steps (when neverErase=True):
5468 FATAL yade.ThreadRunner /home/me/YADE/yade/core/ThreadRunner.cpp:31 run:
Exception occured:
... This leads to another question:
Where is the calculation of the rupture distance? I could not find it in
Law2_ScGeom_CapillaryPhys_Capillarity.cpp.
Does this mean, that the capillary force is calculated only for real contacts
(when uN>0)?
It should be created even before particles come in
Thanks Bruno, my script is now working without crash.
--
You received this bug notification because you are a member of Yade
developers, which is the registrant for Yade.
https://bugs.launchpad.net/bugs/897237
Title:
bug in neverErase?!
Status in Yet Another Dynamic Engine:
New
Bug descrip
** Attachment added: "script to reproduce timestep-bug"
https://bugs.launchpad.net/bugs/901146/+attachment/2622745/+files/timestep-bug.py
--
You received this bug notification because you are a member of Yade
developers, which is the registrant for Yade.
https://bugs.launchpad.net/bugs/901146
Public bug reported:
Timesteps increase potentially until the maximum of double is reached.
The bug can be related to makeCloud and/or GlobalStiffnessTimeStepper.
See attachment for further details. After generating the particle cloud click
on "Play" button to see the effect.
** Affects: yade
Thanks Anton, problem solved.
--
You received this bug notification because you are a member of Yade
developers, which is the registrant for Yade.
https://bugs.launchpad.net/bugs/901146
Title:
timestep-bug
Status in Yet Another Dynamic Engine:
New
Bug description:
Timesteps increase pote
Another problem occurs, when I remove numbers of particles (num=-1).
example:
sp=pack.SpherePack();
sp.makeCloud((x_cl,y_cl,z_cl),(x_cu,y_cu,z_cu),psdSizes=dia,psdCumm=phi_,distributeMass=True)
Then only particles with the minimum particle size (dia[0]) are
generated (after >1 hour generation tim
** Changed in: yade
Status: New => Fix Committed
--
You received this bug notification because you are a member of Yade
developers, which is the registrant for Yade.
https://bugs.launchpad.net/bugs/901146
Title:
timestep-bug
Status in Yet Another Dynamic Engine:
Fix Committed
Bug de
> There are so many parameters combinations in makeCloud that I overlooked one.
> How did you manage to hit the one that was not expected? ;)
There are so many users of Yade. Why is it me who is trapping in all
bugs?
I was wondering, because the one who wrote .../scripts/test/psd.py
should have
Public bug reported:
After saving my model and load it, this error occurs:
File "/home/me/YADE/YADE2981/bin/yade-bzr2981", line 183, in runScript
execfile(script,globals())
File "3-settling.py", line 5, in
O.load(save_file_name2)
RuntimeError: Scene::postLoad: Internal inconsistency,
Ok, now I found out, that O.load() is not compatible with Antons
function (udpSph, see attachment).
** Attachment added: "o.load-bug.tar.gz"
https://bugs.launchpad.net/yade/+bug/903111/+attachment/2636190/+files/o.load-bug.tar.gz
--
You received this bug notification because you are a member
Thanks, problem solved.
** Changed in: yade
Status: New => Fix Committed
--
You received this bug notification because you are a member of Yade
developers, which is the registrant for Yade.
https://bugs.launchpad.net/bugs/903111
Title:
O.load() gives error message
Status in Yet Anothe
*raise-up-my-hand*
I would like to test all scripts for the bzr-version and would try to
fix the error- and warning-messages. I think this is very important
improvement of yade for beginners. If I have time I will begin next
week.
Regards,
Christian.
Zitat von Bruno Chareyre :
Hi the
Public bug reported:
This bug is related to a question.
https://answers.launchpad.net/yade/+question/190529
I attached a script to reproduce the bug, when fusionDetection=True and
hertz model is used. The bug occurs, when contacts are created. In the
script I created two fixed particles and one
** Attachment added: "script to reproduce the bug"
https://bugs.launchpad.net/bugs/966186/+attachment/2947726/+files/check-fusion-detection-bug.py
--
You received this bug notification because you are a member of Yade
developers, which is the registrant for Yade.
https://bugs.launchpad.net/bu
Thank you for your comment. If I set a higher shear modulus (1e6 instead
of 1e5) this script does not crash, but in my other model I use 3e7 and
it crashes too, when it gets dynamic. First I will increase shear
modulus also for this model, but later it should be fixed.
Does anyone has an idea how
Zitat von Bruno Chareyre :
Anton, Christian,
I just realized that I should have accepted the pending merge request in
git interface already.
There are so many screens and links there that I'm still a bit lost...
Oh, I thought I am the only one, who feels like that ...
I start to see the imp
Branch: refs/heads/master
Home: https://github.com/yade/trunk
Commit: 412ff603f2d8e728e1420144a5b123f8e9e9703c
https://github.com/yade/trunk/commit/412ff603f2d8e728e1420144a5b123f8e9e9703c
Author: Christian Jakob
Date: 2012-03-27 (Tue, 27 Mar 2012)
Changed paths:
M pkg
Public bug reported:
This bug is related to a question:
https://answers.launchpad.net/yade/+question/191904
Using multi-threading option in yade leads to instabilities, that are caused by
indeterminism.
To reproduce the bug, download attached file, extract and run 1-generation.py.
You will get
** Attachment added: "files to reproduce bug"
https://bugs.launchpad.net/bugs/987164/+attachment/3099697/+files/multi-threading-bug.tar.gz
--
You received this bug notification because you are a member of Yade
developers, which is the registrant for Yade.
https://bugs.launchpad.net/bugs/98716
Branch: refs/heads/master
Home: https://github.com/yade/trunk
Commit: cbff7d67ab3a0ef02c07caf45dbc028b1a5e4eea
https://github.com/yade/trunk/commit/cbff7d67ab3a0ef02c07caf45dbc028b1a5e4eea
Author: Christian Jakob
Date: 2012-04-23 (Mon, 23 Apr 2012)
Changed paths:
M pkg
Thank you anton for this link, it is very helpful in understanding the
basic of this problem. What I do not understand is, that it leads to
totally different results within a very low number of steps (in this
case within ~30.000 steps).
--
You received this bug notification because you are a memb
Public bug reported:
The bug occurs, when a save file is created with utils.saveVars()
utils.saveVars('wall_ids',id_tmp_walls=id_tmp_walls)
O.save('save-postloadbug.yade')
, loaded afterwards in another file
O.load('save-postloadbug.yade')
utils.loadVars('wall_ids')
id_tmp_walls = yade.params.w
** Attachment added: "to reproduce post-load-bug"
https://bugs.launchpad.net/bugs/987731/+attachment/3101559/+files/post-load-bug.tar.gz
--
You received this bug notification because you are a member of Yade
developers, which is the registrant for Yade.
https://bugs.launchpad.net/bugs/987731
problem solved with define WallMat new, before erasing a body:
WallMat=O.bodies[id_tmp_walls].material
O.bodies.erase(id_tmp_walls)
So it is no bug, right?
** Changed in: yade
Status: New => Invalid
--
You received this bug notification because you are a member of Yade
developers, which
I tested the script without facets, it is still unstable, this time even
without multithreading ...
I also detected, that some particles have accelerated rotations after
relaxation step (without calm() function).
So the problem seems to come from the hard overlaps while generating the
particles
So from your comments I would assume that 1e-6 is a good value in my
case ...
--
You received this bug notification because you are a member of Yade
developers, which is the registrant for Yade.
https://bugs.launchpad.net/bugs/987164
Title:
bug with multithreading
Status in Yet Another Dynami
calculation is not ready yet :(
be patient, i will report when it is ready
maybe this blowing-up method is better reffered to calculation times ...
hm
--
You received this bug notification because you are a member of Yade
developers, which is the registrant for Yade.
https://bugs.launchpad.net/b
I found a way to get it in a stable condition with calm() function.
After that no calm function is active and the model behaves like this,
when running it three times (100k steps):
me@debian ~/YADE/my-yade-projects/09-converted-PFC-model >yadetest -j2 test.py
actual porosity: 45.478219 percent,
Public bug reported:
I detected a memory leak in the capillary model. When running several millions
of steps (after ca. 2 days calc. time) my RAM is full (Note, that I have 32 GB,
which should be enough for 600 particles ;) and swap also begin to fill.
In line 91 of capillary model there is a co
Branch: refs/heads/master
Home: https://github.com/yade/trunk
Commit: 1bea7e3c3c229468a3a5d208e79b71ef4b9d9107
https://github.com/yade/trunk/commit/1bea7e3c3c229468a3a5d208e79b71ef4b9d9107
Author: Christian Jakob
Date: 2012-05-07 (Mon, 07 May 2012)
Changed paths:
M pkg
only way for us
all to know what happens in Yade without diving into the code.
If you type "git push" (without the -m) it pops up an editor where you
can type plain text. Don't hesitate to type detailed descriptions there.
Cheers.
Bruno
On 08/05/12 08:00, Christian Jakob wrote:
Branch: refs/heads/master
Home: https://github.com/yade/trunk
Commit: 0acac2bc19abaf2cd539a52331e3b34abe3693a1
https://github.com/yade/trunk/commit/0acac2bc19abaf2cd539a52331e3b34abe3693a1
Author: Christian Jakob
Date: 2012-05-10 (Thu, 10 May 2012)
Changed paths:
M pkg
** Changed in: yade
Status: New => Fix Committed
--
You received this bug notification because you are a member of Yade
developers, which is the registrant for Yade.
https://bugs.launchpad.net/bugs/995874
Title:
memory leak in Law2...Capillarity
Status in Yet Another Dynamic Engine:
Public bug reported:
I tried to make a pour cone test to measure repose angle of my sand
grains. I used clumped spheres and CohFrictMat with alphaKr = 1e8. To
reproduce use the script in the attachment and execute 00-MASTER.py and
wait. CAUTION it can cause a crash of your operating system!
It wo
** Attachment added: "script to reproduce bug, CAUTION it can lead to crash of
your system!"
https://bugs.launchpad.net/bugs/997931/+attachment/3141110/+files/pour-cone-test-bug.tar.gz
--
You received this bug notification because you are a member of Yade
developers, which is the registrant
there.
Cheers.
Bruno
On 08/05/12 08:00, Christian Jakob wrote:
Branch: refs/heads/master
Home: https://github.com/yade/trunk
Commit: 1bea7e3c3c229468a3a5d208e79b71ef4b9d9107
https://github.com/yade/trunk/commit/1bea7e3c3c229468a3a5d208e79b71ef4b9d9107
Author: Christian Jakob
After an "aptitude upgrade", where some qt libraries were updated, the
crash did not happen again. So I think it was not yade related crash.
** Changed in: yade
Status: New => Invalid
--
You received this bug notification because you are a member of Yade
developers, which is the registran
I have the same problem on Debian Wheezy (KDE).
With 2012-05-10.git-b6236a0 it works well on Debian Squeeze (KDE) ...
--
You received this bug notification because you are a member of Yade
developers, which is the registrant for Yade.
https://bugs.launchpad.net/bugs/1009500
Title:
Problem wit
Public bug reported:
hi,
i have a model with some clumps inside. now i want to create a clump,
that contains some spheres and some of the existing clumps. but the
function O.bodies.clump(bodylist[:]) is not working in this case, i can
only clump spheres together, not clumps. to override this, one
** Attachment added: "script for clump existing clumps"
https://bugs.launchpad.net/yade/+bug/1017367/+attachment/3211705/+files/clump-clumps.py
--
You received this bug notification because you are a member of Yade
developers, which is the registrant for Yade.
https://bugs.launchpad.net/bugs/
I successfully compiled yade (2012-07-04.git-cc040a1) with cmake. As
Anton said cmake needs a new library (libxi-dev on debian squeeze). I
edited the installation wiki [1] for debian. Please check if in ubuntu
the needed library has the same name and update the wiki for ubuntu
installation.
trail and error ;-)
However, I never had this problem. It seems the error is during runtime,
right?
Klaus
On Wed, 4 Jul 2012 07:48:52 PM Christian Jakob wrote:
I successfully compiled yade (2012-07-04.git-cc040a1) with cmake. As
Anton said cmake needs a new library (libxi-dev on debian squeeze).
Many thanks, it is working perfectly!
--
You received this bug notification because you are a member of Yade
developers, which is the registrant for Yade.
https://bugs.launchpad.net/bugs/1017367
Title:
clump existing clumps
Status in Yet Another Dynamic Engine:
Fix Released
Bug description
Public bug reported:
Hi,
I need a "calm function" for my generation process. In python code it
looks like this:
def calm():
for b in O.bodies:
if isinstance(b.shape,Sphere) or b.isClump:
b.state.vel = Vector3(0,0,0)
Thank you for your help.
I think I did it, but there is a compilation warning:
/home/me/YADE/trunk/pkg/dem/Shop.cpp: In static member function ‘static Real
Shop::calm(const boost::shared_ptr&, int)’:
/home/me/YADE/trunk/pkg/dem/Sh
Jan and Anton, are you twins?
... you are giving same answer at the same time ^^
--
You received this bug notification because you are a member of Yade
developers, which is the registrant for Yade.
https://bugs.launchpad.net/bugs/1026073
Title:
"calm function" inside source code
Status in Ye
Branch: refs/heads/master
Home: https://github.com/yade/trunk
Commit: a9f3750f5917ef9cbe59358e7196c53a42235b53
https://github.com/yade/trunk/commit/a9f3750f5917ef9cbe59358e7196c53a42235b53
Author: Christian Jakob
Date: 2012-07-19 (Thu, 19 Jul 2012)
Changed paths:
M pkg
Public bug reported:
VTKRecorder should export boxes for post processing with Paraview.
** Affects: yade
Importance: Wishlist
Status: New
** Changed in: yade
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Yade
developers, wh
I would try to implement, if it is not too complicated ... Surely need
some help on it!
--
You received this bug notification because you are a member of Yade
developers, which is the registrant for Yade.
https://bugs.launchpad.net/bugs/1026474
Title:
visualize boxes in paraview
Status in Yet
I already started ...
for facets vtkTriangle is used, but boxes are cuboids. There is no vtkCuboid
for that, so what to do?
Divide the cuboid into rectangles and use vtkRectangle?
--
You received this bug notification because you are a member of Yade
developers, which is the registrant for Yade
Do we need this boxesCells for vtk?
It should contain id of the body and id of the points (in this case 8 points
per body). I dont know how to implement it, in interactions intrsCells is based
on vtkLine (2 points), while in facets facetsCells is based on vtkTriangle (3
points). So what to do wi
** Attachment added: "test script for this bug"
https://bugs.launchpad.net/yade/+bug/1026474/+attachment/3228567/+files/export-boxes.py
--
You received this bug notification because you are a member of Yade
developers, which is the registrant for Yade.
https://bugs.launchpad.net/bugs/1026474
Great job Anton!
I think it is the best way to handle boxes with vtk exporter.
--
You received this bug notification because you are a member of Yade
developers, which is the registrant for Yade.
https://bugs.launchpad.net/bugs/1026474
Title:
visualize boxes in paraview
Status in Yet Another
** Attachment added: "test if calm function works correctly"
https://bugs.launchpad.net/yade/+bug/1026073/+attachment/3241948/+files/testing-calm-function.py
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.
calm function is not working yet (see attachment)
it seems it does not set velocities to zero, I can see no effect at all ... ?!
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1026073
Title:
"calm
Ah, ok. Works fine with braces ;)
** Changed in: yade
Status: New => Fix Released
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1026073
Title:
"calm function" inside source code
Status in
Public bug reported:
When clump members are erased, but clump still exists, a segmentation
fault occurs (see attachment).
** Affects: yade
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Ya
** Attachment added: "script to reproduce bug"
https://bugs.launchpad.net/bugs/1031644/+attachment/3244426/+files/erase-clumpmembers-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/1031644
To fix it uncomment line 53 ...
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1031644
Title:
erase clumpmembers leads to segfault, when clump was not erased
Status in Yet Another Dynamic Engine:
Public bug reported:
Hi,
It would be very helpful, if there would be an "extra" value for every
body. This value can be set by the user. It must be a very fexible value
(bool, int, float, vector, array, etc.).
Example:
I create a clump, which consists of two hardly overlapping spheres and
somet
Zitat von Jan Stránský :
Hello Christian,
sorry if I misunderstood your question, but would you like to achieve this?
Yade [1]: b = utils.sphere((1,1,1),1)
Yade [2]: O.bodies.append(b)
-> [2]: 0
Yade [3]: b.extra = 4
Yade [4]: b.extra
-> [4]: 4
Yade [5]: b.extra = Vector3(1,2,3)
Yade
I have the same message on my Debian Wheezy (on Squeeze message does not
occur).
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1019349
Title:
RuntimeWarning: to-Python converter for
boost::share
For further explanation (my first ideas):
We could first make an easy-to-implement feature, later it could be extended.
Lets say we just want to let extra variable be int or float. Also for the
start, there is
only one extra value allowed for one body (as said, later we can extend if
needed)...
> I guess Christian has in mind to use e.g. clump volume in some c++
algorithm (right?), else there is little interest in adding variables to
bodies.
No, in my example I need clump volume to calculate porosity. This is done in
python code.
But I dont know what other users want to do with their ex
Public bug reported:
I detected a memory leak in O.bodies.erase, when facets were erased (spheres
are erased without memory leak!).
In the attachment you will find two files, where you can reproduce the bug.
1. Open a terminal with three tabs.
2. Run top or htop in the first terminal tab
3. In t
** Attachment added: "bug-mem-leak-facets.zip"
https://bugs.launchpad.net/bugs/1041084/+attachment/3274767/+files/bug-mem-leak-facets.zip
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1041084
Ti
When you insert another O.run(5,True) after creating the facets, the
memory leak is still there and also much higher, than without it!
Also I get a crash :o
Running script memoryleak-erase-facets.py
Message from syslogd@debian at Aug 24 10:56:01 ...
kernel:[1542691.744027] EDAC MC0: UE row 0, c
Thank you Anton for the explanation.
Why is memory not purged after erasing a body?
Is it possible to clear memory from erased bodies?
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1041084
Title:
>b = utils.facet()
>id = O.bodies.append(b)
>O.bodies.erase(id)
>b=0
>
>You can try such approach. Maybe it will help.
No, this is unfortunately not solving the problem...
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs
Hi all,
Also we should check out example scripts again, because some contact
laws are no more available and also because of the new time step
algorithm. There I detected a problem in one of my own scripts (it
seems to freeze calculation). Until now I dont know whats wrong, I
will check it
Public bug reported:
I tried to deactivate GlobalStiffnessTimeStepper in O.engines with
GlobalStiffnessTimeStepper.dead=True
or with
GlobalStiffnessTimeStepper.active=False
, but this commands will not deactivate it.
To solve the problem one just have not to declare it in O.engines.
** Affec
I provide more information on this topic, maybe its really just a script
syntax problem ...
O.engines=[
ForceResetter(),
InsertionSortCollider([Bo1_Sphere_Aabb(),Bo1_Facet_Aabb(),Bo1_Box_Aabb()]),
InteractionLoop(
[Ig2_Sphere_Sphere_ScGeom(),Ig2_Facet_Sphe
Aaahh, thank you very much Bruno.
Problem solved with using label = 'ts' instead of label = 'TimeStepper'.
> Never name an object with an uppercase, if you want to avoid this kind
of problem.
ok, got it.
--
You received this bug notification because you are a member of Yade
developers, which i
Branch: refs/heads/master
Home: https://github.com/yade/trunk
Commit: 55851518e58f5817e0ef493a3222bc61cdda82db
https://github.com/yade/trunk/commit/55851518e58f5817e0ef493a3222bc61cdda82db
Author: Christian Jakob
Date: 2012-10-05 (Fri, 05 Oct 2012)
Changed paths:
M
1 - 100 of 301 matches
Mail list logo
