date:20171128

Re: [Yade-users] [Question #661215]: Record the rotation of polyhedra by VTK and plot the i vs rot

2017-11-28 Thread De zhang

Question #661215 on Yade changed:
https://answers.launchpad.net/yade/+question/661215

Status: Answered => Solved

De zhang confirmed that the question is solved:
Thanks Jan Stránský, 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 #661215]: Record the rotation of polyhedra by VTK and plot the i vs rot

2017-11-28 Thread Jan Stránský

Question #661215 on Yade changed:
https://answers.launchpad.net/yade/+question/661215

Status: Open => Answered

Jan Stránský proposed the following answer:
Hello,

thanks for the code, but please next time try to post a working
example..

> but I got nothing

because there are errors in your script (as the terminal should say),
see below

> BalRota=O.bodies[45].state.rot() # What's wrong with this line?

just do
BalRota=O.bodies[45].state.rot

.state.rot is an instance of Quaternion. The () after it should be
"TypeError: 'Quaternion' object is not callable"

>
plot.addData(Fz=Fz,w=W,br=BalRota,i=O.iter,unbalanced=unbalancedForce(),**O.energy)

I have tried plot.addData with a quaternion (like your br=BalRot) and got 
ValueError that quaternion is not allowed argument of plot.addData
you can try BalRota.toRotationMatrix()

then still you will need to update plot.plots, since you will not habe
'br' keys in plot.data, but 'br_xx', 'br_xy'

or perhaps define "rotation" in a different way..

cheers
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 #660585]: Why avoid reseting particle positions in DFNFlow?

2017-11-28 Thread Bruno Chareyre

Question #660585 on Yade changed:
https://answers.launchpad.net/yade/+question/660585

Bruno Chareyre posted a new comment:

On 11/27/2017 07:32 PM, Robert Caulk wrote:
>
> Trial and error show that there is indeed a stability threshold
> associated with the remesh interval. I suspect that the compressibility
> term in question (the one that is essentially ignored when we
> updatePositions=False), is increasing the maximum eigenvalues of our A
> matrix (since adding a term like this can only increase the distortion
> of the system). Higher eigenvalues means a lower required time step.
updatePositions=False means a one-way coupling, which is indeed more 
stable than updatePositions=True (two-way).
However the stability condition is in terms of timestep, not meshing 
frequency. The origin of the dependency vs. remeshing is unclear to me.

> I do see that Catalano looked at using a parameter based on pore volume
> change to control the retriangulation frequency (Eq. 5.13 of [1]).
Yes, but that is just an accuracy requirement, not related to stability. 
We never found instabilites by not remeshing.
For instance the oedometer.py consolidation will work like a charm if 
you make it run from begin to end with the same mesh.

> I suppose we could use a smaller threshold, but still, I'd
> rather just update as soon as cells perms are tricked.
You are right, "as soon as a crack occurs" is the best option. A problem 
is that in large problems it implies remeshing  virtually at every 
timestep, which is prohibitively expensive.

> I should also mention here that Catalano's max FlowEngine timestep based
> on particle density, diameter, and fluid viscosity (Eq. 4.20 of [1])
> seems to overestimate the time step by a couple orders of magnitude for
> my hydraulic fracture stimulations. Or perhaps I didn't implement it
> right...
In the settings of Catalano I believe the equation is correct, and 
Oedometer.py should confirm that.
I would have to understand your settings in more details. 
Permeable/impermeable matrix? compressible/incompressible fluid? update 
positions or not?
Are you really in a viscosity dominated regime (else the timestep is as 
determined by GlobalStiffnessTimeStepper)?


>
>> There is in fact no need to change the code to achieve "update positions 
>> always and re-triangulate never". It should be enough to set defTolerance<0, 
>> meshUpdateInterval=1e20 (*), updatePositions=True. Or does it give problems?
> This would not work in the current code, since the remeshing also goes
> through and checks for new cell perms to trick as bonds break
I was speaking of _not_ remeshing. :)
Just update cells volumes. It should happen if "defTolerance<0, 
meshUpdateInterval=1e20, updatePos=True".
Could you try that?

> I spent a good amount of time testing different methods for keeping a 
> special positionsBuffer for triangulation only, and allowing the other 
> positionsBuffers to keep doing their duty for updating volume changes.
It seems we have diverging visions of this question. From now on let's 
assume that we always have  updatePos=True.
In this situation positionsBuffer is updated at every iteration and it 
is used to determine the volume changes at each iteration.
Whether or not remeshing occurs is a completely different question, even 
if it uses the same "bufferized" data. The idea of having two distinct 
buffers is still another independent aspect related to task parallelism, 
and actually it provides only a limited speedup.

> I ran into some multithreading headaches for some methods, and just 
> annoying unexplainable bugs for others. Anyways, the current scheme 
> works if we just updatePositions and remesh at a shorter 
> interval...albeit at the expense of the Delaunay retriangulation only 
> (how much does Delauany triangulation even cost...doesn't seem like 
> much). 
Triangulation is fast compared to Cholesky factorization (CGAL also made 
the triangulation parallel recently, which I did not try to use yet). It 
means that tricking just one permeability without changing the mesh 
(thus implying a full new Cholesky decomposition - unless advanced 
methods enabling factors updates are applied) costs nearly the same as 
remeshing (which also implies one Cholesky pass).

Could you show a basic example script with your typical settings?

Cheers
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 #660590]: Loading and manipulating a saving file

2017-11-28 Thread amir

Question #660590 on Yade changed:
https://answers.launchpad.net/yade/+question/660590

amir posted a new comment:
Hi Jérôme,

>>> As another note which was not mentioned until now, I think it's also 
>>> important to realize that O.bodies.erase(b) will delete b's interactions in 
>>> a next step, according to the doc:
https://yade-dem.org/doc/yade.wrapper.html#yade.wrapper.BodyContainer.erase

So, this could be the reason that in the  1st iteration of 2nd
simulation I see interaction instead of 2.


>>It actually seems to me there is some unnecessary redundancy (like in this 
>>present sentence) using at the same time O.bodies.erase(), O.bodies.clear() 
>>and O.reset()

I agree. I forgot to remove O.bodies.erase(), O.bodies.clear(). I tried
the code without O.bodies.erase(), O.bodies.clear() and It works.

Thanks

-- 
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 #661215]: Record the rotation of polyhedra by VTK and plot the i vs rot

2017-11-28 Thread De zhang

New question #661215 on Yade:
https://answers.launchpad.net/yade/+question/661215

Dear everybody
I am going on simulating a process of compact ballast by a plate, I want to 
record the rotation of one ballast of the sample, and make the plot of i vs the 
rotation ,but I got nothing, the process was simply show below:

>from yade import qt,plot,utils,polyhedra_utils,ymport,export,pack,timing
>from yade import *
>import numpy

>## materials ##
>global gravel
>global steel
vglobal rubber
>gravel = PolyhedraMat()
>...omit

>## objects ##
># loading plate name 'laplt'
>global ldplt
>global ldpltheight
>#thickness of plate is 20mm
>ldpltheight=0.95
>ldplt=polyhedra_utils.polyhedra(steel,v=((-0.15,0,ldpltheight),(-0.075*sqrt(3),-0.075,ldpltheight),(-0.075,->0.075*sqrt(3),ldpltheight),...omit)
>O.bodies.append(ldplt) 

>O.bodies.append(utils.wall(0,axis=2,sense=1, material = steel)) 

>O.bodies.append(geom.facetCylinder(center=(0.0,0.0,0.15),radius=0.152,height=0.3,orientation=Quaternion((0,0,1),0),segmentsNumber=12,wallMask=4,angleRange=(0.0,2*pi),closeGap=False,radiusTopInner=0.0,radiusBottomInner=0.0,material=steel))
> #membrane of samples, radius=0.152>radius of loading plate 0.15 for 2mm

>O.bodies.append(geom.facetBunker((0,0,0.3),0.40,0.304,hBunker=0.3,hOutput=0.05,hPipe=0.05,orientation=Quaternion((0,0,1),0),segmentsNumber=12,wallMask=4,angleRange=(0,2*pi),closeGap=False,material=steel))
> #bunker for generate samples

>#global ballast_up
>ballast_up=polyhedra_utils.fillBox((-0.15,-0.15,0.4), 
>(0.15,0.15,0.7),gravel,sizemin=[0.025,0.025,0.025],sizemax=[0.05,0.05,0.05],ratio=[1,1,1],seed=4,mask=1)
>#global ballast_low
>ballast_low=polyhedra_utils.fillBox((-0.11,-0.11,0.0), 
>(0.11,0.11,0.4),gravel,sizemin=[0.025,0.025,0.025],sizemax=[0.05,0.05,0.05],ratio=[1,1,1],seed=4,mask=1)


>## engines ##
>O.engines=[
ForceResetter(),

InsertionSortCollider([Bo1_Polyhedra_Aabb(),Bo1_Wall_Aabb(),Bo1_Facet_Aabb()]),
InteractionLoop(
[Ig2_Wall_Polyhedra_PolyhedraGeom(), 
Ig2_Polyhedra_Polyhedra_PolyhedraGeom(), Ig2_Facet_Polyhedra_PolyhedraGeom()],
[Ip2_PolyhedraMat_PolyhedraMat_PolyhedraPhys(), 
Ip2_FrictMat_PolyhedraMat_FrictPhys()],
[Law2_PolyhedraGeom_PolyhedraPhys_Volumetric()],   # contact 
law -- apply forces #Bo1_Cylinder_Aabb()
),
NewtonIntegrator(damping=0.3,gravity=(0,0,-9.81)),
PolyhedraSplitter(iterPeriod=1,label='Splitter'), # allow splittering 
ballast

PyRunner(command="vtkExporter.exportPolyhedra(what=[('num','b.id'),('rotate','b.state.ori')])",realPeriod=10),
   ### What' s the problem of this VTK line???
PyRunner(command='checkUnbalancedI()',realPeriod=1,label='checker')
]

>vtkExporter = export.VTKExporter('postfalling/Jan-')

>O.dt=0.1*polyhedra_utils.PWaveTimeStep()

## selfdefine pyrunner attention the format of the language
>def checkUnbalancedI():
print "iter %d, time elapsed %f,  time step %.5e, unbalanced forces = 
%.5f"%(O.iter, O.realtime, O.dt, utils.unbalancedForce())
if O.iter<6000: return 
if unbalancedForce()>0.05: return

O.engines=O.engines+[PyRunner(command='addPlotData()',iterPeriod=50)]+[PyRunner(command='checkersieve()',iterPeriod=500)]
# next time, do not call this function anymore, but the next one 
(unloadPlate) instead
checker.command='cyclicloadingI()'


>def addPlotData():
Fz=265+135*sin((15/pi)*O.time)
#Fz=14350+10250*sin((15/pi)*O.time) 
#Fz=-O.forces.f(ldplt.id)[2]
W=-ldplt.state.pos[2]+ldplt.state.refPos[2]
BalRota=O.bodies[45].state.rot() # What's wrong 
with this line?

plot.addData(Fz=Fz,w=W,br=BalRota,i=O.iter,unbalanced=unbalancedForce(),**O.energy)
 

>def cyclicloadingI():
yade.timing.reset()
O.forces.setPermF(O.bodies[0].id,(0,0,-265-135*sin((15/pi)*O.time))) # 
130N to 400N

>def checkersieve():
polyhedra_utils.SieveCurve()
polyhedra_utils.SizeRatio()

#from yade import qt
qt.Controller()
V = qt.View()

#plot
plot.plots={'i':('unbalanced',),'w':('Fz',),'i':('br',)}
plot.plot()


## save and load ## 
O.wait()
#O.save('ballastCompact.yade.gz')
O.run(1)
O.wait()




-- 
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 #661159]: Bug while installing Yade from source code

2017-11-28 Thread Rémi Chassagne

Question #661159 on Yade changed:
https://answers.launchpad.net/yade/+question/661159

Status: Answered => Open

Rémi Chassagne is still having a problem:
Thanks for your help. I installed all the missing packages I found at the page 
: https://github.com/yade/yadedaily/blob/trusty/control
So I do not have any warning messages during the compilation configuration 
process. The output of cmake -DCMAKE_CXX_FLAGS=-frounding-math 
-DCMAKE_INSTALL_PREFIX=../install ../trunk is now :

-- Version is set to 2017-11-27.git-79e991c
-- GTS using gts-config /usr/bin/gts-config
-- Using GTS from /usr
-- 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, version: 3.2.1
-- Disable vectorization
-- Found VTK
-- Found OpenMP
-- GTS using gts-config /usr/bin/gts-config
-- Using GTS from /usr
-- Found GTS
-- Found GUI-Qt5-LIBS
-- GMP libs: /usr/lib/x86_64-linux-gnu/libgmp.so 
/usr/lib/x86_64-linux-gnu/libgmpxx.so
-- GMP libs: /usr/lib/x86_64-linux-gnu/libgmp.so 
/usr/lib/x86_64-linux-gnu/libgmpxx.so
-- Found CGAL
-- Found Cholmod in /usr/lib/x86_64-linux-gnu/libcholmod.so
-- Found OpenBlas in /usr/lib/libopenblas.so
-- Found Metis in /usr/lib/x86_64-linux-gnu/libmetis.so
-- Found GL2PS
LBMFLOW is still experimental, building and running LBM engine are at your own 
risk!
Yade will be installed to /home/remi/myYade/install
-- Suffix is set to -2017-11-27.git-79e991c
-- LIBRARY_OUTPUT_PATH is set to lib/x86_64-linux-gnu
-- runtimePREFIX is set to /home/remi/myYade/install
-- Use system gts version
-- ===
-- Yade configured with following features: Odeint VTK OpenMP GTS GUI-Qt5 CGAL 
PFVFLOW LINSOLV GL2PS LBMFLOW
-- Disabled features: CHOLMOD_GPU SPH DEFORM LIQMIGRATION MASK_ARBITRARY 
PROFILING PotentialParticles PotentialBlocks
-- Optimized build
-- ===
-- Configuring done
-- Generating done
-- Build files have been written to: /home/remi/myYade/build


I recompiled, but the bug is not fixed, the file img_rc.py is not found and the 
installation failed.
I have a warning during the compilation phase that occur several time but that 
I do not understand :

In file included from 
/usr/lib/python2.7/dist-packages/numpy/core/include/numpy/ndarraytypes.h:1761:0,
 from /home/remi/myYade/trunk/py/_polyhedra_utils.cpp:15:
/usr/lib/python2.7/dist-packages/numpy/core/include/numpy/npy_1_7_deprecated_api.h:15:2:
 warning: #warning "Using deprecated NumPy API, disable it by " "#defining 
NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION" [-Wcpp]
 #warning "Using deprecated NumPy API, disable it by " \
  ^

Rémi

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 #661159]: Bug while installing Yade from source code

2017-11-28 Thread Manfred Hampl

Question #661159 on Yade changed:
https://answers.launchpad.net/yade/+question/661159

Manfred Hampl requested more information:
Maybe missing package is / are

libvtk-java
libvtk5-dev

-- 
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 #661159]: Bug while installing Yade from source code

2017-11-28 Thread Marcus Moravia

Question #661159 on Yade changed:
https://answers.launchpad.net/yade/+question/661159

Status: Open => Answered

Marcus Moravia proposed the following answer:
Hi Rémi.

There are packages missing in your system. I am quite sure that the
cause of the problem is the lack of 'pyqt4-dev-tools'. You can see all
necessary packages for Ubuntu Trusty on:

https://github.com/yade/yadedaily/blob/trusty/control

Cheers!

Marcus

-- 
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 #661159]: Bug while installing Yade from source code

2017-11-28 Thread Rémi Chassagne

Question #661159 on Yade changed:
https://answers.launchpad.net/yade/+question/661159

Status: Needs information => Open

Rémi Chassagne gave more information on the question:
Thank you for your answer. Here is the output of cmake -DCMAKE_CXX_FLAGS
=-frounding-math -DCMAKE_INSTALL_PREFIX=../install ../trunk done in
"~/myYade/build/"

-- Version is set to 2017-11-27.git-8bae8f2
-- GTS using gts-config /usr/bin/gts-config
-- Using GTS from /usr
-- 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, version: 3.2.1
-- Disable vectorization
-- The imported target "vtkParseJava" references the file
   "/usr/bin/vtkParseJava"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
   "/usr/lib/vtk-5.8/VTKTargets.cmake"
but not all the files it references.

-- The imported target "vtkWrapJava" references the file
   "/usr/bin/vtkWrapJava"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
   "/usr/lib/vtk-5.8/VTKTargets.cmake"
but not all the files it references.

-- The imported target "vtkCommonJava" references the file
   "/usr/lib/jni/libvtkCommonJava.so.5.8.0"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
   "/usr/lib/vtk-5.8/VTKTargets.cmake"
but not all the files it references.

-- The imported target "vtkFilteringJava" references the file
   "/usr/lib/jni/libvtkFilteringJava.so.5.8.0"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
   "/usr/lib/vtk-5.8/VTKTargets.cmake"
but not all the files it references.

-- The imported target "vtkImagingJava" references the file
   "/usr/lib/jni/libvtkImagingJava.so.5.8.0"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
   "/usr/lib/vtk-5.8/VTKTargets.cmake"
but not all the files it references.

-- The imported target "vtkGraphicsJava" references the file
   "/usr/lib/jni/libvtkGraphicsJava.so.5.8.0"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
   "/usr/lib/vtk-5.8/VTKTargets.cmake"
but not all the files it references.

-- The imported target "vtkGenericFilteringJava" references the file
   "/usr/lib/jni/libvtkGenericFilteringJava.so.5.8.0"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
   "/usr/lib/vtk-5.8/VTKTargets.cmake"
but not all the files it references.

-- The imported target "vtkIOJava" references the file
   "/usr/lib/jni/libvtkIOJava.so.5.8.0"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
   "/usr/lib/vtk-5.8/VTKTargets.cmake"
but not all the files it references.

-- The imported target "vtkRenderingJava" references the file
   "/usr/lib/jni/libvtkRenderingJava.so.5.8.0"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained

Re: [Yade-users] [Yade-dev] Yade with CGAL 4.11

2017-11-28 Thread Janek Kozicki (yade-dev)

Uh, Bruno :-) I was thinking to ask you whether you have given my diff to Anton 
after you have modified it. Please do it, or just confirm that the one which I 
sent is good to go (which isn’t optimal due to too many #ifdefs as you 
mentioned earlier).

best regards
Janek

On 27 Nov 2017, 20:04 +0100, Anton Gladky , wrote:
> Hi all,
>
> is there any progress on fixing this issue? I have disabled CGAL for
> Debian builds, but it would be good to switch it on again.
>
> Also the stable Yade version is almost one year old. It is time to release
> something newer soon. If there are some volunteers to go through
> existing bugs on launchpad [1] and fix/close/react on some of them,
> it would be good.
>
> I will probably be able to prepare a release at the beginning of 2018.
>
> [1] https://bugs.launchpad.net/yade
>
> Best regards
>
> Anton
>
>
> 2017-11-07 19:35 GMT+01:00 Bruno Chareyre :
> >
> >
> > On 11/07/2017 06:47 PM, Janek Kozicki wrote:
> > >
> > > I just feel a little uneasy about cross_product of two
> > > (sphere-sphere) pairs ;)
> >
> >
> > Well... after admitting that spheres can be mutually orthogonal (which is
> > really the case) cross product is fine... :)
> > But you are right, here cross product is really ordinary cross_product.
> > Bruno
> >
> >
> >
> >
> > ___
> > Mailing list: https://launchpad.net/~yade-dev
> > Post to : yade-...@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~yade-dev
> > More help : https://help.launchpad.net/ListHelp
>
> ___
> Mailing list: https://launchpad.net/~yade-dev
> Post to : yade-...@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~yade-dev
> More help : https://help.launchpad.net/ListHelp
___
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 #661159]: Bug while installing Yade from source code

2017-11-28 Thread Jérôme Duriez

Question #661159 on Yade changed:
https://answers.launchpad.net/yade/+question/661159

Status: Open => Needs information

Jérôme Duriez requested more information:
Hi,

I think we will need the output of cmake in order for us to possibly
help you.

Jérôme

-- 
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 #661159]: Bug while installing Yade from source code

2017-11-28 Thread Rémi Chassagne

New question #661159 on Yade:
https://answers.launchpad.net/yade/+question/661159

Hello everyone,

I have a bug while installing YADE from source code. 
My system : Ubuntu 14.04.5 LTS
Yade version : Yade 2017-11-27.git-8bae8f2

I followed the instruction given in the tutorial :  
https://yade-dem.org/doc/installation.html#source-code
 - In my "home" I created a "myYade/" directory in which I did : git 
clone https://github.com/yade/trunk.git
 - I created the directories "build/" and "install/" in "myYade/"
 - in "myYade/build/" I configured the compilation : cmake 
-DCMAKE_CXX_FLAGS=-frounding-math -DCMAKE_INSTALL_PREFIX=../install ../trunk
 - I compiled : "make" (stilll in "myYade/build/")

Until here everything seems normal. The bug comes during the installation 
process. I did "make install" and the following bug occured : 
"
CMake Error at gui/cmake_install.cmake:88 (FILE):
  file INSTALL cannot find "/home/remi/myYade/build/img_rc.py".
Call Stack (most recent call first):
  cmake_install.cmake:197 (INCLUDE)


make: *** [install] Error 1
"

I tired to copy-paste "img_rc.py" from an older version already installed on my 
computer.
Doing again "make install" I have the same error but with "ui_controller.py". 
Again I did a copy-paste.
Now "make install" works.

If I try to launch Yade in "myYade/install/bin/" with 
./yade-2017-11-27.git-8bae8f2 and I have a segmentation fault :
"
Welcome to Yade 2017-11-27.git-8bae8f2 
Segmentation fault (core dumped)
"

If someone has an idea and can help me, I would be grateful.

Rémi

-- 
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 #660590]: Loading and manipulating a saving file

2017-11-28 Thread Jérôme Duriez

Question #660590 on Yade changed:
https://answers.launchpad.net/yade/+question/660590

Jérôme Duriez posted a new comment:
As another note which was not mentioned until now, I think it's also important 
to realize that O.bodies.erase(b) will delete b's interactions in a next step, 
according to the doc:
https://yade-dem.org/doc/yade.wrapper.html#yade.wrapper.BodyContainer.erase

It actually seems to me there is some unnecessary redundancy (like in
this present sentence) using at the same time O.bodies.erase(),
O.bodies.clear() and O.reset()

Jérôme

-- 
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 #661215]: Record the rotation of polyhedra by VTK and plot the i vs rot

Re: [Yade-users] [Question #661215]: Record the rotation of polyhedra by VTK and plot the i vs rot

Re: [Yade-users] [Question #660585]: Why avoid reseting particle positions in DFNFlow?

Re: [Yade-users] [Question #660590]: Loading and manipulating a saving file

[Yade-users] [Question #661215]: Record the rotation of polyhedra by VTK and plot the i vs rot

Re: [Yade-users] [Question #661159]: Bug while installing Yade from source code

Re: [Yade-users] [Question #661159]: Bug while installing Yade from source code

Re: [Yade-users] [Question #661159]: Bug while installing Yade from source code

Re: [Yade-users] [Question #661159]: Bug while installing Yade from source code

Re: [Yade-users] [Yade-dev] Yade with CGAL 4.11

Re: [Yade-users] [Question #661159]: Bug while installing Yade from source code

[Yade-users] [Question #661159]: Bug while installing Yade from source code

Re: [Yade-users] [Question #660590]: Loading and manipulating a saving file

13 matches

Site Navigation

Mail list logo

Footer information