Re: [Yade-users] [Question #631403]: 'make' error during compilation
Question #631403 on Yade changed: https://answers.launchpad.net/yade/+question/631403 Status: Open => Answered Anton Gladky proposed the following answer: Hi, as far as I remember, there was a bug in gcc. Your code falis to compile due to VTK. If you do not need VTK just disable it: -DENABLE_VTK=0. Another option is to update your system, maybe it is fixed already. Regards 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 #626656]: gravity deposition computation time
Question #626656 on Yade changed: https://answers.launchpad.net/yade/+question/626656 Bruno Chareyre proposed the following answer: Changing the units keeps the problem unchanged. It is correct, and helpless. 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
[Yade-users] [Question #631403]: 'make' error during compilation
New question #631403 on Yade: https://answers.launchpad.net/yade/+question/631403 Hello everybody, I am installing “Yade 2017.01a” by compiling source code in ubuntu 14.04 (64bit). It reports errors when I execute 'make'. All the prerequisites have been installed. Process of cmake: hjz@hjz-System-Product-Name:~/myyade/build$ cmake -DCMAKE_INSTALL_PREFIX=/home/hjz/myyade/install /home/hjz/myyade/trunk-2017.01 -- The C compiler identification is GNU 4.8.4 -- The CXX compiler identification is GNU 4.8.4 -- Check for working C compiler: /usr/bin/cc -- Check for working C compiler: /usr/bin/cc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ -- Check for working CXX compiler: /usr/bin/c++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Found PythonInterp: /usr/bin/python (found version "2.7.6") -- Try OpenMP C flag = [-fopenmp] -- Performing Test OpenMP_FLAG_DETECTED -- Performing Test OpenMP_FLAG_DETECTED - Success -- Try OpenMP CXX flag = [-fopenmp] -- Performing Test OpenMP_FLAG_DETECTED -- Performing Test OpenMP_FLAG_DETECTED - Success -- Found OpenMP: -fopenmp -- Looking for Q_WS_X11 -- Looking for Q_WS_X11 - found -- Looking for Q_WS_WIN -- Looking for Q_WS_WIN - not found -- Looking for Q_WS_QWS -- Looking for Q_WS_QWS - not found -- Looking for Q_WS_MAC -- Looking for Q_WS_MAC - not found -- Found Qt4: /usr/bin/qmake-qt4 (found version "4.8.6") -- Found PkgConfig: /usr/bin/pkg-config (found version "0.26") -- Version is set to 2017.01a -- Looking for XOpenDisplay in /usr/lib/x86_64-linux-gnu/libX11.so;/usr/lib/x86_64-linux-gnu/libXext.so -- Looking for XOpenDisplay in /usr/lib/x86_64-linux-gnu/libX11.so;/usr/lib/x86_64-linux-gnu/libXext.so - found -- Looking for gethostbyname -- Looking for gethostbyname - found -- Looking for connect -- Looking for connect - found -- Looking for remove -- Looking for remove - found -- Looking for shmat -- Looking for shmat - found -- Looking for IceConnectionNumber in ICE -- Looking for IceConnectionNumber in ICE - found -- Found X11: /usr/lib/x86_64-linux-gnu/libX11.so -- Found OpenGL: /usr/lib/x86_64-linux-gnu/libGL.so -- GTS using gts-config /usr/bin/gts-config -- Using GTS from /usr -- Found GL2PS: /usr/lib/libgl2ps.so -- Found CGAL: /usr/include/CGAL, /usr/lib/libCGAL.so -- Found NumPy: version "1.8.2" /usr/lib/python2.7/dist-packages/numpy/core/include -- Found Loki: /usr/include -- GCC Version >= 4.8. Adding -ftrack-macro-expansion=0 and -save-temps -- Boost version: 1.54.0 -- Found the following Boost libraries: -- python -- thread -- filesystem -- iostreams -- regex -- serialization -- system -- date_time -- Boost_VERSION: 105400 -- Boost_LIB_VERSION: 1_54 -- Boost_INCLUDE_DIRS: /usr/include -- Boost_LIBRARIES: /usr/lib/x86_64-linux-gnu/libboost_python.so/usr/lib/x86_64-linux-gnu/libboost_thread.so/usr/lib/x86_64-linux-gnu/libboost_filesystem.so/usr/lib/x86_64-linux-gnu/libboost_iostreams.so/usr/lib/x86_64-linux-gnu/libboost_regex.so/usr/lib/x86_64-linux-gnu/libboost_serialization.so/usr/lib/x86_64-linux-gnu/libboost_system.so/usr/lib/x86_64-linux-gnu/libboost_date_time.so/usr/lib/x86_64-linux-gnu/libpthread.so -- Found Eigen3: /usr/local/include/eigen3 (Required is at least version "2.91.0") -- Found BZip2: /usr/lib/x86_64-linux-gnu/libbz2.so (found version "1.0.6") -- Looking for BZ2_bzCompressInit in /usr/lib/x86_64-linux-gnu/libbz2.so -- Looking for BZ2_bzCompressInit in /usr/lib/x86_64-linux-gnu/libbz2.so - found -- Found ZLIB: /usr/lib/x86_64-linux-gnu/libz.so (found version "1.2.8") -- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython2.7.so (found version "2.7.6") -- Found Eigen3, version: 3.3.3 -- Disable vectorization -- Found VTK -- Found OpenMP -- GTS using gts-config /usr/bin/gts-config -- Using GTS from /usr -- checking for one of the modules 'glib-2.0' -- Found GLib2: glib-2.0 /usr/include/glib-2.0;/usr/lib/x86_64-linux-gnu/glib-2.0/include -- Looking for include file glib/gregex.h -- Looking for include file glib/gregex.h - not found -- Found GTS -- Found GLUT: /usr/lib/x86_64-linux-gnu/libglut.so -- Found QGLVIEWER-qt5: /usr/include/QGLViewer -- Found GUI-Qt5-LIBS -- GMP libs: /usr/lib/x86_64-linux-gnu/libgmp.so /usr/lib/x86_64-linux-gnu/libgmpxx.so -- Found GMP: /usr/include/x86_64-linux-gnu -- GMP libs: /usr/lib/x86_64-linux-gnu/libgmp.so /usr/lib/x86_64-linux-gnu/libgmpxx.so -- Found CGAL -- Found Cholmod: /usr/lib/libcholmod.so -- Found OpenBlas: /usr/lib/libopenblas.so -- Found Metis: /usr/include/metis -- Found Cholmod -- Found OpenBlas -- Found Metis -- Found GL2PS LBMFLOW is still experimental, building and running LBM engine are at your own risk! Yade will be installed to /home/hjz/myyade/install -- Suffix is set to -2017.01a -- LIBRARY_OUTPUT_PATH is set to lib/x86_64-linux-gnu -- runtimePREFIX is set to /home/hjz/myyade/install -- Found
Re: [Yade-users] [Question #631147]: fail to check the permF I applied
Question #631147 on Yade changed: https://answers.launchpad.net/yade/+question/631147 Status: Open => Answered Jan Stránský proposed the following answer: Hello, I have tried it on a minimal example and worked for me without problem. Please provide (as small as possible) script, which reproduce the problem and also how you run it, operating system and version of yade you use. Thanks Jan -- 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 #626656]: gravity deposition computation time
Question #626656 on Yade changed: https://answers.launchpad.net/yade/+question/626656 guilhem posted a new comment: Ok, many thanks. Yes, lot of people largely reduce stifness. Does someone have the experience supposing 1mm=1m in the simulation. For purely dynamic considerations, is it correct? BR -- 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 #269576]: how detect force applied on beam
Question #269576 on Yade changed: https://answers.launchpad.net/yade/+question/269576 Michal Nitka posted a new comment: Hi! I've just read an article and I have some questions that you may really know the answer, please read it here http://wildon.intellirant.com Hope this helps, Yade-users -- 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 #631227]: Porosity of a packing with overlapped particles
Question #631227 on Yade changed: https://answers.launchpad.net/yade/+question/631227 Status: Answered => Open Huihuang Xia is still having a problem: Thanks Klaus, I have tried your method, this approach works really good. Here is another question, Can I use this method to calculate the porosity of an irregular packing? Choosing a sub-volume from a irregular packing can give a result as precise as the whole volume? FW your reply, regards, Huihuang -- 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 #631227]: Porosity of a packing with overlapped particles
Question #631227 on Yade changed: https://answers.launchpad.net/yade/+question/631227 Status: Open => Answered Klaus Thoeni proposed the following answer: Hi, you should use utils.voxelPorosity [1] instead of utils.porosity(), this works fine for overlapping particles. HTH Klaus [1] https://yade- dem.org/doc/yade.utils.html?highlight=voxelporosity#yade._utils.voxelPorosity -- 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 #631227]: Porosity of a packing with overlapped particles
New question #631227 on Yade: https://answers.launchpad.net/yade/+question/631227 Hi, I defined a function to calculate the porosity of a packing with lots of overlapped particles, because the build-in function "utils.porosity()" always got a negative one. This question (https://answers.launchpad.net/yade/+question/404363) gave me some useful hints. My own function has a serious error, that is my function always got a same porosity whatever the growFactor is. Here is my code segment: from yade import utils from yade import pack from yade import qt mat1 = O.materials.append(FrictMat(young=5.0e7,poisson=0.25,density=2640.0,frictionAngle=radians(18))) pred = pack.inAlignedBox((0,0,0),(0.01,0.01,0.01)) dim = pred.dim() packing = regularHexa(pred, radius=0.0005,gap=0,material=mat1) O.bodies.append(packing) # grow particles in order to get lower porosity growFactor = 1.5 utils.growParticles(growFactor) def overlappedPorosity(totVol,density): totVol = dim[0]*dim[1]*dim[2] mass = sum([b.state.mass for b in O.bodies])*pow(growFactor,-3) return (totVol - mass/density)/totVol print 'The porosity of this packing is:',overlappedPorosity(dim[0]*dim[1]*dim[2],O.materials[0].density) # 3D view and controller try: qt.Controller() qt.View() except: pass In my function, ''mass = sum([b.state.mass for b in O.bodies])*pow(growFactor,-3)'', because after the packing was generated, the radius of each particle in packing was magnified by growFactor using growParticles. Any useful advice will be highly appreciated. Thanks in advance, Huihuang Xia -- 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