Re: [Yade-users] [Question #295309]: Use of GID for Yade
Question #295309 on Yade changed: https://answers.launchpad.net/yade/+question/295309 Status: Answered => Solved paula confirmed that the question is solved: Thanks Anton. -- 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 #295309]: Use of GID for Yade
Question #295309 on Yade changed: https://answers.launchpad.net/yade/+question/295309 Status: Open => Answered Anton Gladky proposed the following answer: Hi, the common way is to convert your surfaces to STL and then import them into Yade. GID is not supported by Yade due to its commercial nature. Cheerrs, Anton -- 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] [Yade-dev] Yade 2016.06a released
Dear Anton, Thank you so much for your update. It's the great news. We will work hard for the development of YADE in the future! Cheers, Thang Sent from my BlackBerry 10 smartphone. Original Message From: Anton Gladky Sent: Wednesday, 15 June 2016 05:00 To: yade-users@lists.launchpad.net Cc: yade-dev Subject: [Yade-dev] Yade 2016.06a released Dear Yade users and developers, After almost 8 months of development I am glad to announce the next Yade version 2016.06a. The complete changelog you will find as always at the end of this message. The versioning of releases is changed and now is in the form .MMx. Where x is the letter, which can be changed by minor updates in the stable releases. Thanks all for contributions! Anton == yade-2016.06a Tue, Jun 14 20:30:53 2016 +0200 Anton Gladky (88): Remove release. Clean some unused macroses (old wm3-stuff) Remove some global headers Raise minimal boost version to 1.47 Add -DNDEBUG if compiling in release mode Tiny code refactoring Clean some warnings and old stuff. Return removed header back. Fix warning in newer matplotlib. Drop old commented stuff in python-scrips. Remove flags and preSteps from scene Remove deprecated findBoundDispatcherInEnginesIfNoFunctorsAndWarn Remove PISC_DEBUG. Fix typo in installation sections of doce. Thanks to Jan. Export normal and viscous part of the visco-elastic contact Remove confusing part in installation part of documentation regarding Qt5. Fix typo in CMakeLists Tiny updates of examples of LudingPM. Fix compilation warnings. Update formatting in SpherePack Fix an order of calculation of c in SpherePack Fix some compilation warnings. Fix cappitalization typo in Lapack (case-sensitive in this case). Respect VTK6 in PotentialParticles. Add .travis.yml for CI. Remove version restriction on sphinx. Use trusty as build-env. Add -y parameter to apt-get install. Fix numpy import on travis. Fix segfault during save/load of CapViscModels Add one more check-script (capillary models) Fix typo in check-script. Fix crash in Ig2_Facet_Polyhedra_PolyhedraGeom vtkExporter: increase number of leading zeros to 8 Move implementation of methods of ForceContainer in cpp. Split implementation of ForceContainer in parallel and serial. Add zero-forces to the youngest body after simulation load. Closes LP:1560171 Drop parallel execution in replaceByClumps. Closes LP:1559098 Add import of polyhedras from the file. Add an opportunity to shift, scale and rotate imported polyhedrons Minor fixes in Polyhedra_splitter. Fix division by zero crash in Polyhedra Add CGAL_DISABLE_ROUNDING_MATH_CHECK, -frounding-math when CGAL is enabled. Fix some formatting issues. Non-invasive fixes in polyhedra_splitter. Get max-min coefs in polyhedra_splitter simpler. Use tuple as a parameter for SplitPolyhedraDouble Add check script for polyhedra crash. Use explicitly -DNDEBUG instead of CMAKE_CXX_FLAGS_RELEASE Check isnan in some coordinates before calling CGAL. Minor formatting fixes in Polyhedra. Add check-script for save/load of clumps. Disable checkPolyhedraCrush. It is unstable now. Fix checkPolyhedraCrush Remove polyhedra_utils import from "ymport" Add prefix std:: to isnan and isinf. Update checkPolyhedraCrush Update files for ppa-infrastructure. Undef NDEBUG in all polyhedra files. Add pause for checkSaveLoadClumps to escape race condition. Use variadic arguments in DynLibDispatcher. Fix crash in polyhedra, if maxFs=0. Fix checkPolyhedraCrush (remove qt) Remove unused functionality in Dispatcher. Set Qt5 by default. Add mathcmaker for normalCohesion and shearCohesion. Split QGLViewer.cmake on qt4 and qt5 versions. Add .gitattributes to ignore line endings. Migrate buildppa to python3. Replace some "#define"(s) by functions. Remove some machine-specific items in documentation. Add unit test for matchmaker. Replace vector by unordered_map data structure in Matchmaker. Minor fix in documentation. Replace some "defines" by functions. Remove numpy.hpp. Fix bug in polyhedra_splitter. Some cosmetic fixes in core-files. Enable C++14. Revert 2dc99 and ed8dcb. Use unordered_map instead of map for MapId2IntrT Use unordered_map only for Boost >= 1.56 Back to C++11. Revert using unordered_map in Body. Scale mass and inertia in spheresModify. Reduce size of flags in Bounds of InsertionSortCollider Fix bug in MatchMaker. Add RELEASE file. Bruno Chareyre (16): add labels to default engines for easier showcases fix ambiguous syntax, fixing https://bugs.launchpad.net/bugs/1514477 introduce 2nd edition of the documentation and contact for consuting (in homepage) update the webpage about citation with 2nd edition, add 1st edition as an external reference, update pdf metadata fix one DOI of the 2nd ed. documentation Add missing toctree's for the citable book versions fix typo in installation page fixed DOI fix some hyperlinks pointing to the old geo.hmg.inpg.fr declare mask attribute for FlowEngine, fixes a compile error
[Yade-users] [Question #295309]: Use of GID for Yade
New question #295309 on Yade: https://answers.launchpad.net/yade/+question/295309 Hey there! I want to know if I can transform surfaces from Cad using GID to use them later in Yade? . Thanks a lot!!! -- 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
[Yade-users] Yade 2016.06a released
Dear Yade users and developers, After almost 8 months of development I am glad to announce the next Yade version 2016.06a. The complete changelog you will find as always at the end of this message. The versioning of releases is changed and now is in the form .MMx. Where x is the letter, which can be changed by minor updates in the stable releases. Thanks all for contributions! Anton == yade-2016.06a Tue, Jun 14 20:30:53 2016 +0200 Anton Gladky (88): Remove release. Clean some unused macroses (old wm3-stuff) Remove some global headers Raise minimal boost version to 1.47 Add -DNDEBUG if compiling in release mode Tiny code refactoring Clean some warnings and old stuff. Return removed header back. Fix warning in newer matplotlib. Drop old commented stuff in python-scrips. Remove flags and preSteps from scene Remove deprecated findBoundDispatcherInEnginesIfNoFunctorsAndWarn Remove PISC_DEBUG. Fix typo in installation sections of doce. Thanks to Jan. Export normal and viscous part of the visco-elastic contact Remove confusing part in installation part of documentation regarding Qt5. Fix typo in CMakeLists Tiny updates of examples of LudingPM. Fix compilation warnings. Update formatting in SpherePack Fix an order of calculation of c in SpherePack Fix some compilation warnings. Fix cappitalization typo in Lapack (case-sensitive in this case). Respect VTK6 in PotentialParticles. Add .travis.yml for CI. Remove version restriction on sphinx. Use trusty as build-env. Add -y parameter to apt-get install. Fix numpy import on travis. Fix segfault during save/load of CapViscModels Add one more check-script (capillary models) Fix typo in check-script. Fix crash in Ig2_Facet_Polyhedra_PolyhedraGeom vtkExporter: increase number of leading zeros to 8 Move implementation of methods of ForceContainer in cpp. Split implementation of ForceContainer in parallel and serial. Add zero-forces to the youngest body after simulation load. Closes LP:1560171 Drop parallel execution in replaceByClumps. Closes LP:1559098 Add import of polyhedras from the file. Add an opportunity to shift, scale and rotate imported polyhedrons Minor fixes in Polyhedra_splitter. Fix division by zero crash in Polyhedra Add CGAL_DISABLE_ROUNDING_MATH_CHECK, -frounding-math when CGAL is enabled. Fix some formatting issues. Non-invasive fixes in polyhedra_splitter. Get max-min coefs in polyhedra_splitter simpler. Use tuple as a parameter for SplitPolyhedraDouble Add check script for polyhedra crash. Use explicitly -DNDEBUG instead of CMAKE_CXX_FLAGS_RELEASE Check isnan in some coordinates before calling CGAL. Minor formatting fixes in Polyhedra. Add check-script for save/load of clumps. Disable checkPolyhedraCrush. It is unstable now. Fix checkPolyhedraCrush Remove polyhedra_utils import from "ymport" Add prefix std:: to isnan and isinf. Update checkPolyhedraCrush Update files for ppa-infrastructure. Undef NDEBUG in all polyhedra files. Add pause for checkSaveLoadClumps to escape race condition. Use variadic arguments in DynLibDispatcher. Fix crash in polyhedra, if maxFs=0. Fix checkPolyhedraCrush (remove qt) Remove unused functionality in Dispatcher. Set Qt5 by default. Add mathcmaker for normalCohesion and shearCohesion. Split QGLViewer.cmake on qt4 and qt5 versions. Add .gitattributes to ignore line endings. Migrate buildppa to python3. Replace some "#define"(s) by functions. Remove some machine-specific items in documentation. Add unit test for matchmaker. Replace vector by unordered_map data structure in Matchmaker. Minor fix in documentation. Replace some "defines" by functions. Remove numpy.hpp. Fix bug in polyhedra_splitter. Some cosmetic fixes in core-files. Enable C++14. Revert 2dc99 and ed8dcb. Use unordered_map instead of map for MapId2IntrT Use unordered_map only for Boost >= 1.56 Back to C++11. Revert using unordered_map in Body. Scale mass and inertia in spheresModify. Reduce size of flags in Bounds of InsertionSortCollider Fix bug in MatchMaker. Add RELEASE file. Bruno Chareyre (16): add labels to default engines for easier showcases fix ambiguous syntax, fixing https://bugs.launchpad.net/bugs/1514477 introduce 2nd edition of the documentation and contact for consuting (in homepage) update the webpage about citation with 2nd edition, add 1st edition as an external reference, update pdf metadata fix one DOI of the 2nd ed. documentation
Re: [Yade-users] [Question #295301]: calculate external work in Uniaxial Strainer
Question #295301 on Yade changed: https://answers.launchpad.net/yade/+question/295301 Jan Stránský proposed the following answer: Hi Jabrane, you should put "this->dAX = dAX" to a place such that dAX is not changed afterwards. e.g. it is changed at https://github.com/yade/trunk/blob/master/pkg/dem/UniaxialStrainer.cpp#L106 So after line 121 (in the original file) it should be the correct position Jan 2016-06-14 19:47 GMT+02:00 Jan Stránský < question295...@answers.launchpad.net>: > Question #295301 on Yade changed: > https://answers.launchpad.net/yade/+question/295301 > > Jan Stránský proposed the following answer: > Hi Jabrane, > > But i have a question how do you know that dAX is a local variable ? > > > it just comes from how C++ works / is defined, nothing else. > > "Real dAX" in cpp file inside a function simply declares a local variable. > No matter if the class has a member with the same name. > > cheers > Jan > > > 2016-06-14 19:37 GMT+02:00 Yor1: > > > Question #295301 on Yade changed: > > https://answers.launchpad.net/yade/+question/295301 > > > > Yor1 posted a new comment: > > Hello Jerome and Jan > > > > Thank you of your response. > > > > Jerome, I simulate the tensile test with TriaxialStressController using a > > positive strainRate but i doesn't work. > > I get sigma=sigma2=sigma3=0 and that is anormal. > > > > Jan, your solution work but i can't have a definitive opinion until i > > calculate Wext. > > But i have a question how do you know that dAX is a local variable ? > > > > Best regards. > > Jabrane. > > > > -- > > 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 > > > > -- > 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 > -- 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 #295301]: calculate external work in Uniaxial Strainer
Question #295301 on Yade changed: https://answers.launchpad.net/yade/+question/295301 Yor1 posted a new comment: Hello Jan, The behavior of dAX is related to the line in which i put "this->dAX = dAX" In fact i put "this->dAX = dAX" just after https://github.com/yade/trunk/blob/master/pkg/dem/UniaxialStrainer.cpp#L95 and just after https://github.com/yade/trunk/blob/master/pkg/dem/UniaxialStrainer.cpp#L122 and i get different value of dAX. The question is where do I put "this->dAX = dAX" to get the real behavior? Best regards. Jabrane. -- 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 #295301]: calculate external work in Uniaxial Strainer
Question #295301 on Yade changed: https://answers.launchpad.net/yade/+question/295301 Jan Stránský proposed the following answer: Hi Jabrane, But i have a question how do you know that dAX is a local variable ? it just comes from how C++ works / is defined, nothing else. "Real dAX" in cpp file inside a function simply declares a local variable. No matter if the class has a member with the same name. cheers Jan 2016-06-14 19:37 GMT+02:00 Yor1: > Question #295301 on Yade changed: > https://answers.launchpad.net/yade/+question/295301 > > Yor1 posted a new comment: > Hello Jerome and Jan > > Thank you of your response. > > Jerome, I simulate the tensile test with TriaxialStressController using a > positive strainRate but i doesn't work. > I get sigma=sigma2=sigma3=0 and that is anormal. > > Jan, your solution work but i can't have a definitive opinion until i > calculate Wext. > But i have a question how do you know that dAX is a local variable ? > > Best regards. > Jabrane. > > -- > 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 > -- 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 #295301]: calculate external work in Uniaxial Strainer
Question #295301 on Yade changed: https://answers.launchpad.net/yade/+question/295301 Yor1 posted a new comment: Hello Jerome and Jan Thank you of your response. Jerome, I simulate the tensile test with TriaxialStressController using a positive strainRate but i doesn't work. I get sigma=sigma2=sigma3=0 and that is anormal. Jan, your solution work but i can't have a definitive opinion until i calculate Wext. But i have a question how do you know that dAX is a local variable ? Best regards. Jabrane. -- 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 #295301]: calculate external work in Uniaxial Strainer
Question #295301 on Yade changed: https://answers.launchpad.net/yade/+question/295301 Jan Stránský proposed the following answer: Hi Jabrane, you came to c++ variables and scopes [2]. to get correct behavior, one option is to change the declaration of dAX [1]. Currently (Real dAX=) it creates a new variable, unrelated to strainer.dAX. Just delete Real (i.e. assign directly dAX=...) and then dAX refers to the class member strainer.dAX. Another option is leave it as it is and add this->dAX = dAX; somewhere after dAX is computed. cheers Jan [1] https://github.com/yade/trunk/blob/master/pkg/dem/UniaxialStrainer.cpp#L95 [2] http://stackoverflow.com/questions/30494407/declaring-a-local-variable-within-class-scope-with-same-name-as-a-class-attribut 2016-06-14 17:37 GMT+02:00 Yor1: > New question #295301 on Yade: > https://answers.launchpad.net/yade/+question/295301 > > Hello Yade users ! > > I try to calculate the external work on a sample in tensile test. > In fact, i calculate the external work with this simple formulate > "Wext_incremental=AppliedForce*displacement_incremental". > I want to integrate this formulate in the sources UniaxialStrainer.cpp > In uniaxialStrainer.cpp the incremental displacement is calculated and > named "dAX". > In order to verify the behavior of incremental displacement, i define > "dAX" in uniaxialStrainer.hpp like this > ((Real,dAX,0,,"Current incremental displacement")) in the line 43 of > UniaxialStrainer.hpp > > My problem is that in the simulation of tensile test , dAX=0 during the > simulation. > I call dAX in the python script strainer.dAX > I don't understand where is the problem. > > https://github.com/yade/trunk/blob/master/pkg/dem/UniaxialStrainer.hpp > https://github.com/yade/trunk/blob/master/pkg/dem/UniaxialStrainer.cpp > > Best regards. > Jabrane. > > > -- > 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 > -- 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 #295301]: calculate external work in Uniaxial Strainer
Question #295301 on Yade changed: https://answers.launchpad.net/yade/+question/295301 Status: Open => Answered Jérôme Duriez proposed the following answer: Hello, You tried to modify the source code, that's it ? Did you also modify UniaxialStrainer.cpp in order to update this new variable "dAX" ? As a side note, did you consider to use TriaxialStressController ? In spite of its name, it should be possible to use it for uniaxial loadings. And TriaxialStressController provides already access to external work: https://yade-dem.org/doc/yade.wrapper.html#yade.wrapper.TriaxialStressController.externalWork Jerome -- 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
[Yade-users] [Question #295301]: calculate external work in Uniaxial Strainer
New question #295301 on Yade: https://answers.launchpad.net/yade/+question/295301 Hello Yade users ! I try to calculate the external work on a sample in tensile test. In fact, i calculate the external work with this simple formulate "Wext_incremental=AppliedForce*displacement_incremental". I want to integrate this formulate in the sources UniaxialStrainer.cpp In uniaxialStrainer.cpp the incremental displacement is calculated and named "dAX". In order to verify the behavior of incremental displacement, i define "dAX" in uniaxialStrainer.hpp like this ((Real,dAX,0,,"Current incremental displacement")) in the line 43 of UniaxialStrainer.hpp My problem is that in the simulation of tensile test , dAX=0 during the simulation. I call dAX in the python script strainer.dAX I don't understand where is the problem. https://github.com/yade/trunk/blob/master/pkg/dem/UniaxialStrainer.hpp https://github.com/yade/trunk/blob/master/pkg/dem/UniaxialStrainer.cpp Best regards. Jabrane. -- 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