Re: [Yade-users] [Question #643660]: A simple question on interactionDetectionFactor
Question #643660 on Yade changed: https://answers.launchpad.net/yade/+question/643660 Huihuang Xia confirmed that the question is solved: Thanks Robert Caulk, that solved my question. -- You received this question notification because your team yade-users is an answer contact for Yade. ___ Mailing list: https://launchpad.net/~yade-users Post to : yade-users@lists.launchpad.net Unsubscribe : https://launchpad.net/~yade-users More help : https://help.launchpad.net/ListHelp
Re: [Yade-users] [Question #643660]: A simple question on interactionDetectionFactor
Question #643660 on Yade changed: https://answers.launchpad.net/yade/+question/643660 Status: Answered => Solved Huihuang Xia confirmed that the question is solved: Thanks Luc and Robert, you solved my problem. -- You received this question notification because your team yade-users is an answer contact for Yade. ___ Mailing list: https://launchpad.net/~yade-users Post to : yade-users@lists.launchpad.net Unsubscribe : https://launchpad.net/~yade-users More help : https://help.launchpad.net/ListHelp
Re: [Yade-users] [Question #643878]: Uniaxial strainer source
Question #643878 on Yade changed: https://answers.launchpad.net/yade/+question/643878 Status: Open => Answered Jérôme Duriez proposed the following answer: Hi, Let say you want to strain your sample along "x" axis, and that the sample spans along this axis from xMin to xMax UniaxialStrainer does this by directly imposing some opposite x velocities to these two set of bodies (negIds and posIds) that locate at or around xMin, and xMax (at, or around, since you would usually take some thickness for this layer of controlled bodies) - negIds being the bodies located at x = xMin - while posIds are at xMax With respect to your question, all these bodies should belong to plans that are perpendicular to the x axis. Hoping the situation is now clearer to you, would you have a specific suggestion to rephrase the doc at [1,2,3], in case this doc was unclear ? [1] https://yade-dem.org/doc/yade.wrapper.html#yade.wrapper.UniaxialStrainer [2] https://yade-dem.org/doc/yade.wrapper.html#yade.wrapper.UniaxialStrainer.negIds [3] https://yade-dem.org/doc/yade.wrapper.html#yade.wrapper.UniaxialStrainer.posIds -- You received this question notification because your team yade-users is an answer contact for Yade. ___ Mailing list: https://launchpad.net/~yade-users Post to : yade-users@lists.launchpad.net Unsubscribe : https://launchpad.net/~yade-users More help : https://help.launchpad.net/ListHelp
Re: [Yade-users] [Question #452277]: FlowEngine producing segmentation fault after removing particles
Question #452277 on Yade changed: https://answers.launchpad.net/yade/+question/452277 Antoine Wautier posted a new comment: Maybe, however I will not be able to do it in a close future... The solution I found (when the swap increase too much) is simply to save the simulation, close YADE, relaunch YADE, reload the saved file and resume the simulation. -- You received this question notification because your team yade-users is an answer contact for Yade. ___ Mailing list: https://launchpad.net/~yade-users Post to : yade-users@lists.launchpad.net Unsubscribe : https://launchpad.net/~yade-users More help : https://help.launchpad.net/ListHelp
Re: [Yade-users] [Question #644029]: Inspect button not working
Question #644029 on Yade changed: https://answers.launchpad.net/yade/+question/644029 Status: Answered => Open Jason Hsin is still having a problem: I have the same problem in the empty yade session as well.. -- You received this question notification because your team yade-users is an answer contact for Yade. ___ Mailing list: https://launchpad.net/~yade-users Post to : yade-users@lists.launchpad.net Unsubscribe : https://launchpad.net/~yade-users More help : https://help.launchpad.net/ListHelp
Re: [Yade-users] [Question #452277]: FlowEngine producing segmentation fault after removing particles
Question #452277 on Yade changed: https://answers.launchpad.net/yade/+question/452277 Status: Open => Answered Bruno Chareyre proposed the following answer: I guess a "reset" function to FlowEngine would solve the problem. Do you think you could implement it? B -- You received this question notification because your team yade-users is an answer contact for Yade. ___ Mailing list: https://launchpad.net/~yade-users Post to : yade-users@lists.launchpad.net Unsubscribe : https://launchpad.net/~yade-users More help : https://help.launchpad.net/ListHelp
Re: [Yade-users] [Question #452277]: FlowEngine producing segmentation fault after removing particles
Question #452277 on Yade changed: https://answers.launchpad.net/yade/+question/452277 Status: Answered => Open Antoine Wautier is still having a problem: Hi, Thanks for the quick reply. I already tried "del flow1". I get an error "NameError: name 'flow1' is not defined" however if I type just after "flow1" I still get "". I also tried to redefine new engines with the same label 'flow'. However if I repeat the operation many times and track the memory linked to my process with htop it increases continuously. Antoine -- You received this question notification because your team yade-users is an answer contact for Yade. ___ Mailing list: https://launchpad.net/~yade-users Post to : yade-users@lists.launchpad.net Unsubscribe : https://launchpad.net/~yade-users More help : https://help.launchpad.net/ListHelp
Re: [Yade-users] [Question #644029]: Inspect button not working
Question #644029 on Yade changed: https://answers.launchpad.net/yade/+question/644029 Status: Open => Answered Bruno Chareyre proposed the following answer: I have no idea personally. Could be that it needs a few changes to work with Qt5. Is it a problem related to a particular simulation or do you have the same problem in empty yade sessions? B -- You received this question notification because your team yade-users is an answer contact for Yade. ___ Mailing list: https://launchpad.net/~yade-users Post to : yade-users@lists.launchpad.net Unsubscribe : https://launchpad.net/~yade-users More help : https://help.launchpad.net/ListHelp
Re: [Yade-users] [Question #644029]: Inspect button not working
Question #644029 on Yade changed: https://answers.launchpad.net/yade/+question/644029 Status: Answered => Open Jason Hsin is still having a problem: Hi Bruno, Thanks for the reply, I've just installed the yadedaily, however, the inspect button still won't work. Any idea i can fix the problem? Thanks Jason -- You received this question notification because your team yade-users is an answer contact for Yade. ___ Mailing list: https://launchpad.net/~yade-users Post to : yade-users@lists.launchpad.net Unsubscribe : https://launchpad.net/~yade-users More help : https://help.launchpad.net/ListHelp
Re: [Yade-users] [Question #452277]: FlowEngine producing segmentation fault after removing particles
Question #452277 on Yade changed: https://answers.launchpad.net/yade/+question/452277 Status: Open => Answered Bruno Chareyre proposed the following answer: Hi, You could try "del flow1", but I'm really not sure it will effectively free memory. I'm also really not sure it is a problem. There is no reason to increment the label string as it is done in the example. Did you really observe a memory leak? Bruno -- You received this question notification because your team yade-users is an answer contact for Yade. ___ Mailing list: https://launchpad.net/~yade-users Post to : yade-users@lists.launchpad.net Unsubscribe : https://launchpad.net/~yade-users More help : https://help.launchpad.net/ListHelp
Re: [Yade-users] [Question #644029]: Inspect button not working
Question #644029 on Yade changed: https://answers.launchpad.net/yade/+question/644029 Status: Open => Answered Bruno Chareyre proposed the following answer: Hello, I would suggest to first try yadedaily, the most recent version. There is no real good in using an older version usually. Bruno -- You received this question notification because your team yade-users is an answer contact for Yade. ___ Mailing list: https://launchpad.net/~yade-users Post to : yade-users@lists.launchpad.net Unsubscribe : https://launchpad.net/~yade-users More help : https://help.launchpad.net/ListHelp
Re: [Yade-users] [Question #452277]: FlowEngine producing segmentation fault after removing particles
Question #452277 on Yade changed: https://answers.launchpad.net/yade/+question/452277 Status: Solved => Open Antoine Wautier is still having a problem: Hi, Following the solution given by Bruno to my question above, I would like to raise a new issue. Indeed, I noticed that while resetting the list of engines, the old engines not in O.engines list anymore are still stored in memory which will cause memory leak. For instance if you do O.engines=[FlowEngine(label='flow1')] O.engines=[FlowEngine(label='flow2')] and then type in python flow1, it returns The engine is not use anymore but still exist. I was wondering whether there is a way to force deletion of unused engines. Thank you in advance for your help Best Antoine -- You received this question notification because your team yade-users is an answer contact for Yade. ___ Mailing list: https://launchpad.net/~yade-users Post to : yade-users@lists.launchpad.net Unsubscribe : https://launchpad.net/~yade-users More help : https://help.launchpad.net/ListHelp
