[Yade-dev] Website down?

Anyone else able to reach yade-dem.org ___ Mailing list: https://launchpad.net/~yade-dev Post to : yade-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~yade-dev More help : https://help.launchpad.net/ListHelp

[Yade-dev] Yade short-course for Thermo-Hydro-Mechanical couplings

Hello Yade users and devs, You are all invited to a 3-day short-course in Amsterdam, Netherlands on 20/06/22-22/06/22 covering the theory and practical implementation of fluid and thermal couplings in particulate systems. We have limited space, so please register early to avoid missing the

Re: [Yade-dev] R: yade-dev team tomorrow's zoom meeting reminder

Please everyone, keep in mind you can follow directly the agenda and find most up to date zoom links on our discord: https://discord.gg/rku35YXZJd -rc On Wed, Nov 10, 2021 at 10:00 AM Katia Boschi wrote: > Dear Janek, > > > > I would be interested too. > > Thank you, > > > > Katia > > > >

[Yade-dev] Introducing Yade discord beta

Hey Yade devs, A few of us were discussing the *idea of encouraging more collaboration* among Yade devs and the idea came up to create a central server for chatting about various topics and exchanging ideas. Discord seems to be a good candidate for this since we can organize the server into

[Yade-dev] Yade Technical Archive - call for materials

Hey Yade devs, Got Yade stuff lying around? Yade Technical Archive (YTA) is looking for *seminar presentations*, *papers*, *technical notes*, or* course materials* about Yade. Send us your Yade materials and we will: - *proofread* it for english, - *format* it into the standard YTA latex

Re: [Yade-dev] [Question #692441]: OpenFOAM YADE coupling iterations

Question #692441 on Yade changed: https://answers.launchpad.net/yade/+question/692441 Status: Expired => Needs information Robert Caulk changed the question status: Maybe more information can be provided. Changing status. -- You received this question notification because your team Y

Re: [Yade-dev] [Question #692441]: OpenFOAM YADE coupling iterations

Question #692441 on Yade changed: https://answers.launchpad.net/yade/+question/692441 Robert Caulk posted a new comment: I guess we would need more clarification of what evidence you are using to see the difference in "iterations." However, I am not familiar with openFOAM coupling so

Re: [Yade-dev] [Question #692315]: Calculation time definition

Question #692315 on Yade changed: https://answers.launchpad.net/yade/+question/692315 Status: Expired => Answered Robert Caulk changed the question status: Changing to answered to avoid launchpad janitor. Maybe someone will answer someday. -- You received this question notification beca

Re: [Yade-dev] Joining yade-dev team

> > [1] : > https://gitlab.com/yade-dev/trunk/-/blob/master/examples/mpi/testMPI_3D.py > [2] : > https://gitlab.com/yade-dev/trunk/-/blob/master/examples/mpi/testMPI_3D_bisection.py > > > On 14 May 2020, at 15:43, Robert Caulk wrote: > > Out of curiosity,

Re: [Yade-dev] Joining yade-dev team

Out of curiosity, why are you using domaindecomposition.py instead of bisectionDecomposition.py? On Thu, May 14, 2020 at 2:39 PM Janek Kozicki (yade) < jkozicki-y...@pg.edu.pl> wrote: > Hi, welcome here! :) > > Bruno is leading the MPI programming effort, I will let him do the honors > ;) > BTW,

[Yade-dev] Removing trailing white space, yay or nay?

Hey yade devs, Lately I’ve been letting my editor automatically remove trailing white space in the files I’m working on. The benefit to doing this can be disputed, but it seems most people agree that trailing white space is undesirable because it can create unwanted commit noise and interfere

Re: [Yade-dev] all bugs moved from launchpad to gitlab issues

Very nice, Janek :-). Not sure about disabling launchpad bugs. Who “owns” yade launchpad? Le mar. 5 févr. 2019 à 22:28, Janek Kozicki a écrit : > Can we disable reporting new bugs in launchpad interface and redirect > to gitlab? > > Janek Kozicki said: (by the date of Tue, 5 Feb 2019

Re: [Yade-dev] [Bug 1814286] Re: Various LaTeX symbols missing in Yade documentation

It’s ok to merge that full commit including flowboundingsphere. I will make a new merge request with the periodic insertion images. Le mar. 5 févr. 2019 à 19:15, Janek Kozicki <1814...@bugs.launchpad.net> a écrit : > I think rebasing will work now :) Unless Robert will happen to have a >

[Yade-dev] [Bug 1814286] Re: Various LaTeX symbols missing in Yade documentation

Alright, I think I figured out the problem. See [1] and the solution [2]. He adds the latex macros (\def, \let, \newcommand, etc) to his layout.html. I will try this today and report back :-) [1]https://github.com/sphinx-doc/sphinx/issues/726

[Yade-dev] [Bug 1814286] Re: Various LaTeX symbols missing in Yade documentation

>>Hmm, this search in Buster indicates that pngmath is still there, am I missing something? I guess it exists without support based on this warning thrown by make doc: "WARNING: sphinx.ext.pngmath has been deprecated. Please use sphinx.ext.imgmath instead." Have you tried replacing \def with

[Yade-dev] [Bug 1814286] Re: Various LaTeX symbols missing in Yade documentation

Strange, I tried reverting that commit [1] and the problem persisted. [1] https://gitlab.com/yade-dev/trunk/commit/34fb5ffef -- You received this bug notification because you are a member of Yade developers, which is subscribed to Yade. https://bugs.launchpad.net/bugs/1814286 Title: Various

[Yade-dev] [Bug 1814286] Re: Various LaTeX symbols missing in Yade documentation

I am unable to identify the source of the problem. I tried reverting [1] and [2], but the problem persists. I tried changing delimiters, I tried replacing \def with \newcommand (despite the fact that we should not have to, see #12), but the problem persists. It is worth reiterating that all PDF

[Yade-dev] [Bug 1814286] Re: Various LaTeX symbols missing in Yade documentation

According to [1], \def and \let should both work fine with mathjax [1]http://docs.mathjax.org/en/latest/tex.html#tex-commands I think this has something more to do with the the delimiters [2]. Testing now, will report back. [2] http://docs.mathjax.org/en/latest/tex.html#defining-tex-macros --

Re: [Yade-dev] Migration to gitlan - moving bugs to issues on gitlab?

Am I missing a subscription? I’m only receiving these messages once. Le ven. 1 févr. 2019 à 23:08, Janek Kozicki a écrit : > > A mixed option could be to move bugs to gitlab and keep Q on LP, hence > > separating them even more. > > Now I lean towards thinking that this might make some sense. >

[Yade-dev] [Bug 1814286] Re: Various LaTeX symbols missing in Yade documentation

Yes, Mathjax seems cleaner. Does it result in better resolution of math on the web. The old equations used to look grainy with pngmath iirc. Is there a way to test changes and their effect on the website without merging to develop branch? -- You received this bug notification because you are a

[Yade-dev] [Bug 1814286] Re: Various LaTeX symbols missing in Yade documentation

Ah, it is probably worth moving away from pngmath. I guess we just need to rewrite the \defs to accommodate mathjax? -- You received this bug notification because you are a member of Yade developers, which is subscribed to Yade. https://bugs.launchpad.net/bugs/1814286 Title: Various LaTeX

[Yade-dev] [Bug 1814286] Re: Various LaTeX symbols missing in Yade documentation

Ok, after downloading the artifacts from the build, the PDF is built perfectly fine. This must be an issue on the HTML decoding webside, or something like that. -- You received this bug notification because you are a member of Yade developers, which is subscribed to Yade.

[Yade-dev] [Bug 1814286] Re: Various LaTeX symbols missing in Yade documentation

In fact, it looks like the compiler is ignoring \defs. For example: \Dtcr [1] is defined by: \def\Dtcr{\Dt_{\rm cr}} Meanwhile other typical latex symbols are printing fine. https://yade-dev.gitlab.io/trunk/formulation.html#estimation-of-by-wave-propagation-speed -- You received this bug

[Yade-dev] [Bug 1814286] [NEW] Various LaTeX symbols missing in Yade documentation

Public bug reported: See [1]. Looks like the builder is missing some important LaTeX libraries. [1] https://yade-dev.gitlab.io/trunk/formulation.html#variables ** Affects: yade Importance: Undecided Status: New -- You received this bug notification because you are a member of

[Yade-dev] [Bug 1814052] Re: Unreproductible simulation (one core, one computer, one script) with a tutorial example

*In all cases I am executing yade -j1 mwe.py -- You received this bug notification because you are a member of Yade developers, which is subscribed to Yade. https://bugs.launchpad.net/bugs/1814052 Title: Unreproductible simulation (one core, one computer, one script) with a tutorial example

[Yade-dev] [Bug 1814052] Re: Unreproductible simulation (one core, one computer, one script) with a tutorial example

I am able to reproduce the described behavior using both makeCloud(seed=1) and regularHexa. ** Attachment added: "plots.zip" https://bugs.launchpad.net/yade/+bug/1814052/+attachment/5234639/+files/plots.zip -- You received this bug notification because you are a member of Yade developers,

[Yade-dev] [Bug 1814052] Re: Unreproductible simulation (one core, one computer, one script) with a tutorial example

I cannot find anywhere in your scripts where you are saving scenes/packings, loading scenes/packings or resetting the scene. -- You received this bug notification because you are a member of Yade developers, which is subscribed to Yade. https://bugs.launchpad.net/bugs/1814052 Title:

[Yade-dev] [Bug 1814052] Re: Unreproductible simulation (one core, one computer, one script) with a tutorial example

makeCloud is a random generation of spheres [1]. Use the seed argument if you want the same packing twice. [1]https://yade-dem.org/doc/yade.pack.html -- You received this bug notification because you are a member of Yade developers, which is subscribed to Yade.

[Yade-dev] [Bug 1814052] Re: Unreproductible simulation (one core, one computer, one script) with a tutorial example

Please provide all necessary information to allow a developer to reproduce your bug. For example, a running script, your method of yade installation, and exact results that you are observing from said script. -- You received this bug notification because you are a member of Yade developers,

[Yade-dev] [Bug 1813550] [NEW] FlowEngine memory leak - 600 Mb/hr

led=1 from yade import timing print "starting oedometer simulation" O.run(200,1) timing.stats() ## Make more steps to see the convergence to the stationnary solution ** Affects: yade Importance: High Assignee: Robert Caulk (rcaulk) Status: Fix Committed ** Description cha

[Yade-dev] [Bug 1813550] Re: FlowEngine memory leak - 600 Mb/hr

flow.reuseOrdering functionality makes a copy of the factor for efficient reuse. Algorithm was not freeing unnecessary copies. Fixed with: line 173 FLowBoundingSphereLinSolv.ipp: if (!multithread && factorExists && useSolver==4){ if (getCHOLMODPerfTimings) gettimeofday

Re: [Yade-dev] Trouble building from source on Ubuntu 18.04

Usually, we direct these types of questions to the Q forum ( https://answers.launchpad.net/yade). Looking at the cmake warning: CMake Warning at /usr/share/cmake-3.10/Modules/FindQt4.cmake:620 (message): /usr/bin/qmake-qt4 reported QT_INSTALL_LIBS as "/usr/lib/x86_64-linux-gnu" but QtCore

Re: [Yade-dev] Potential Blocks and Potential Particles - Documentation

>>Is there any practical preference between .rst or latex files? 2 more cents: If you are focused on a practical tutorial/guide, it is really best to write it in .rst so it can be easily added to the website (and version controlled as Jerome points out). If, on the other hand, you want to

[Yade-dev] [Bug 1810283] Re: Wiki homepage broken

https://www.yade-dem.org/wiki/Yade works just fine for me. Might've been on their side as you suggest. -- You received this bug notification because you are a member of Yade developers, which is subscribed to Yade. https://bugs.launchpad.net/bugs/1810283 Title: Wiki homepage broken Status in

Re: [Yade-dev] Migrating to GitLab

>> If you asked me it is probably time to move everything (incl. code, Q, bug tracking etc.) >> If source code was migrated, same question for bug tracking and answers? I looked into this. From what I can tell, GitLab only offers issue tracking, which is analgous to bug tracking on LP. Issue

Re: [Yade-dev] Migrating to GitLab

Hello, I agree with a migration to GitLab for all the points already mentioned. It seems the impact on the Yade project can only be positive if I am reading these emails correctly. I find Anton's review especially compelling - there is nothing like a glowing recommendation from someone who has

[Yade-dev] [Bug 1804621] Re: bodyNumInteractionsHistogram broken

Thanks Jerome, I guess I did not understand the original proposal to only change the argument type of bodyNumInteractionsHistogram. Seems to be a better solution than changing each of the other functions I pointed out. -- You received this bug notification because you are a member of Yade

[Yade-dev] [Bug 1804621] Re: bodyNumInteractionsHistogram broken

It seems the only option is to go through and fix these functions manually. Let's just make sure we find everything that needs to be fixed before committing the fix. Can you verify the list below and also look through the trunk to see if there are any other unintended effects? Looking through

[Yade-dev] Buildbot failure

Hello Yade devs, It seems the buildbot's tmp/ directory might be in need of cleaning or restructuring considering the current error (which is preventing a full build): mktemp: failed to create directory via template '/tmp/xvfb-run.XX': Too many links Tough to say what the problem really is

Re: [Yade-dev] Building Documentation

I see. Hmm, can you share some of the warnings you notice during compilation? (especially the "final" one)? On Mon, Oct 22, 2018 at 11:44 AM Eulitz, Alexander < alexander.eul...@iwf.tu-berlin.de> wrote: > Sorry, I indeed did make doc in build folder :( > > &g

Re: [Yade-dev] Building Documentation

path/to/buildfolder/doc/sphinx/_build/html > > > > In install/share/doc/yade-version/yade.pdf there is just the yade logo but > nothing else. > > Cheers, > > Alex > > > > *Von:* Yade-dev [mailto:yade-dev-bounces+alexander.eulitz= > iwf.tu-berlin...@lists.launc

Re: [Yade-dev] Building Documentation

Hello Alex and Jerome, Just to clarify, you are running make doc from inside your build folder, right? When I run make doc after running make install, the yade.pdf appears in install/share/doc/yade-version/yade.pdf, as described in the yade install webpage. Cheers, Robert On Mon, Oct 22, 2018

[Yade-dev] [Bug 1604266] Re: yade not working prpoperly on Ubuntu/Kubuntu 16.04

Thanks Bruno. I confirm that your patch fixed the problem on my computer running VM 16.04. I should point out that in the end, the common denominator of people running into this problem was that they were all using a virtual machine. -- You received this bug notification because you are a

[Yade-dev] [Bug 1790167] Re: JCFPM: "neverErase" modifies the simulated behavior while it should not

>> I always get the same curve when running the simulation with the same packing (with either neverErase=True or neverErase=False). I don't face the problem you mentioned Robert... >> Ok, I re-ran your scripts with -j1 (instead of -j6), and sure enough, I am able to replicate results

[Yade-dev] DFNFlow check script and trickPerm uncertainty fix

Hello, I am working on a check test for DFNFlow in which I use pressure and aperture as pass criteria. However, I want this check script to be a repeatable baseline for DFNFlow, so I'd like to remove/replace the existing uncertainty associated with tricking permeability. If this change may affect

[Yade-dev] [Bug 1790167] Re: JCFPM: "neverErase" modifies the simulated behavior while it should not

I am also curious as to why we see changes in these curves between replicates (even for neverErase=False), despite our use of a constant sphere packing... -- You received this bug notification because you are a member of Yade developers, which is subscribed to Yade.

[Yade-dev] [Bug 1790167] Re: JCFPM: "neverErase" modifies the simulated behavior while it should not

> I noticed that running the exact same simulation (with same initial packing) gives different behaviors I ran your script multiple times but I am having trouble identifying the different stress-strain behaviors you mention. What exactly is different? Is it the post failure part of the curve (I

[Yade-dev] [Bug 1665973] Re: Triaxial Cohesive

Closing: Seti likely switched from TriaxialCompressionEngine to TriaxialStressController. This is a bug with the deprecated TCE, so it is filed as "Won't fix'. ** Changed in: yade Status: New => Won't Fix ** Changed in: yade Assignee: (unassigned) => Robert Caulk (rcaul

Re: [Yade-dev] : Compilation on K/Ubuntu 18.04

Hey Klaus, Thanks for taking time to look at this, I’m sorry I missed your first email about this. Actually we have not updated DFNflow for CGAL 4.11 yet. The commit is fine, the key change that is fixing compilation is: #define DFNFlow Being commented out. I will push the change commenting

[Yade-dev] [Bug 1759633] Re: The Code is crashed when there are two balls with same position and radius

Hello, Will you please provide a minimal working example to demonstrate this bug [1]? Cheers, Robert [1]https://yade-dem.org/wiki/Howtoask -- You received this bug notification because you are a member of Yade developers, which is subscribed to Yade. https://bugs.launchpad.net/bugs/1759633

Re: [Yade-dev] [Yade-users] [Question #665387]: Compile error JointedCohesiveFrictionalPM

? Cheers, Robert On Tue, Mar 13, 2018 at 2:06 AM, William Chèvremont < william.chevrem...@univ-grenoble-alpes.fr> wrote: > Thanks Robert, that solved my issue. > > Le 12/03/2018 à 18:27, Robert Caulk a écrit : > > Hey Will, > > Looks like Thomas Chauve is encountering

Re: [Yade-dev] [Yade-users] [Question #665387]: Compile error JointedCohesiveFrictionalPM

manually or, more simply, by changing the default > behavior of git once for all (on a given machine): > git config branch.autosetuprebase always > > Please always consider the above command before any commit to yade trunk. > > Cheers > > Bruno > > > > On 03/09/2018

[Yade-dev] Adding a pdf to the website

Hello devs, I noticed the Yade website is hosting some thesis pdf files [1][2], I assume these are added by ftp. Who has the ftp credentials for adding additional files? Is there a way to allow other developers ftp access to the website files?

Re: [Yade-dev] cholmod / GPU integration

Thank you, Bruno I had no way of testing this without installing 14.04 specifically for that problem, so I appreciate you helping me solve it. *So an obvious solution was to add a #if (CHOLMOD_GPU == 1) before the useGPU line [1]. * * It seems to fix the compile problem. Does it seem ok for

Re: [Yade-dev] Ip2_FrictMat_FrictMat_FrictPhys doc

Hello Jérôme, I support clarifying the meaning of particle young in the class reference as you suggest. There is no doubt that newcomers to DEM and Yade confuse micro young's modulus with macro young's modulus all the time. I would vote for clarifying the general doc instead of full removal of

Re: [Yade-dev] Odp: Re: Yade for LTS Ubuntu 18.04

are...@grenoble-inp.fr> wrote: > > > On 02/13/2018 10:12 AM, Robert Caulk wrote: > >> I’m running into deeper problems than I expected on this solver bug fix. >> I need some more time to trouble shoot. >> > Let me know, I can also try some things. I have been abl

Re: [Yade-dev] Odp: Re: Yade for LTS Ubuntu 18.04

gt; > Bruno > > > > On 02/12/2018 06:52 PM, Robert Caulk wrote: > > Yes! We should be able to replace the Eigen cholmod interface entirely > with the existing direct cholmod solver (useSolver=4). Right now the > #ifdefs are configured for the special GPU build but I will

Re: [Yade-dev] Odp: Re: Yade for LTS Ubuntu 18.04

Yes! We should be able to replace the Eigen cholmod interface entirely with the existing direct cholmod solver (useSolver=4). Right now the #ifdefs are configured for the special GPU build but I will generalize it today and commit it so that it can be used without GPU compilation flags. Cholmod is

[Yade-dev] Yade related publication?

Hey Yade Devs, I am wondering if we have the demand to create a Yade related white paper publication. The publication would document very Yade specific functionalities and I imagine some papers might even highlight pieces code. I think the format would be very flexible, some releases might be 3

Re: [Yade-dev] [Bug 1734653] Re: DFN+fluid compressibility not using the correct reference volume

Ok, I finally got some time to digest this. Thank you for pointing this out, Bruno, it may have pretty severe impacts on DFNFlow simulations. In my opinion, we would just *add* the crack volume to the original pore volume. Let me see if I can explain why I think this: It seems we need to agree

Re: [Yade-dev] Yade with CGAL 4.11

Could this be the source of the strange PFV behaviors, Luc? On Thu, Nov 2, 2017 at 1:22 PM, Anton Gladky wrote: > Hi all, > > it looks like Yade is not compatible with the new CGAL 4.11 and > it blocks the upload of new CGAL into the Debian [1]. > > It would be good if

Re: [Yade-dev] Compilation issue with cholmod_common.useGPU

ter cmake. > > On 09/28/2017 05:24 PM, Robert Caulk wrote: > > Oh yes, I will fix this today. Thank you for pointing this out! > > On Thu, Sep 28, 2017 at 1:53 AM Bruno Chareyre < > bruno.chare...@3sr-grenoble.fr> wrote: > >> Hi Robert, >> It seems there is a vers

Re: [Yade-dev] Compilation issue with cholmod_common.useGPU

Oh yes, I will fix this today. Thank you for pointing this out! On Thu, Sep 28, 2017 at 1:53 AM Bruno Chareyre < bruno.chare...@3sr-grenoble.fr> wrote: > Hi Robert, > It seems there is a version issue with cholmod. I'm guessing the > "useGPU" parameter is only in a specific version. > Or is it

Re: [Yade-dev] buildbot failure in Yade on yade-full

Does anyone know why the doc keeps failing to build over the past week or so? Error: mktemp: failed to create directory via template '/tmp/xvfb-run.XX': Too many links On Sun, Aug 6, 2017 at 6:03 PM, wrote: > The Buildbot has detected a failed build on builder

Re: [Yade-dev] yade on windows 10

These were my exact thoughts when I read the same news. I plan to experiment with my new windows 10 computer next week and report back. On Thu, Jul 13, 2017 at 11:52 AM, Bruno Chareyre < bruno.chare...@3sr-grenoble.fr> wrote: > Hello devs, > I recently heard that windows 10 was now embedding a

Re: [Yade-dev] buildbot failure in Yade on yade-full

A quick search suggests this is likely due to insufficient RAM + swap. Is it possible a simple reboot will fix this problem? Does the buildbot reboot itself? On Fri, May 12, 2017 at 5:20 AM, Janek Kozicki wrote: > Wow, we got: > > c++: internal compiler error: Killed (program

Re: [Yade-dev] buildbot failure in Yade on yade-full

ures and should > not fail to compile or to crash. I did not look into your changes, but I > think > you need to add a couple of #ifdef guards to make it compilable. > > Best regards > > Anton > > > 2017-05-02 21:45 GMT+02:00 Robert Caulk <rca...@eng.ucsd.edu>

Re: [Yade-dev] buildbot failure in Yade on yade-full

compilation of features that are considered "default" in addition to a stripped down build? In this case, the entire LINSOLV package is not compiled and tested by the buildbot after every commit. Best, Robert On Tue, May 2, 2017 at 10:55 AM, Robert Caulk <rca...@eng.ucsd.edu> wr

Re: [Yade-dev] buildbot failure in Yade on yade-full

/f6970362d9e6e866e8adbc8cbea18e54f677f785 [2] https://yade-dem.org/buildbot/builders/yade-full/builds/3979/steps/compile/logs/stdio On Tue, May 2, 2017 at 9:58 AM, Robert Caulk <rca...@eng.ucsd.edu> wrote: > Very sorry, taking care of this now. > > On Tue, May 2, 2017 at 10:51 AM, <bui

Re: [Yade-dev] buildbot failure in Yade on yade-full

Very sorry, taking care of this now. On Tue, May 2, 2017 at 10:51 AM, wrote: > The Buildbot has detected a failed build on builder yade-full while > building yade. > Full details are available at: > https://yade-dem.org/buildbot/builders/yade-full/builds/3979 > >

[Yade-dev] [Bug 1687355] Re: FlowEngine + compressible flow + multithread does not work

** Package changed: ubuntu => yade -- You received this bug notification because you are a member of Yade developers, which is subscribed to Yade. https://bugs.launchpad.net/bugs/1687355 Title: FlowEngine + compressible flow + multithread does not work Status in Yade: Fix Committed Bug

[Yade-dev] [Bug 1687355] Re: FlowEngine + compressible flow + multithread does not work

** Changed in: yade Status: New => Fix Committed ** Project changed: yade => ubuntu ** Changed in: ubuntu Assignee: (unassigned) => Robert Caulk (rcaulk) -- You received this bug notification because you are a member of Yade developers, which is subscribed to Ya

[Yade-dev] [Bug 1687355] [NEW] FlowEngine + compressible flow + multithread does not work

Public bug reported: Hello yade community, I've noticed that multithread does not work with the compressible flow scheme [4]. My debugging points to [1] where we are setting up the system of linear equations. For the compressible scheme, we need the cell volumes initialized to build our system

[Yade-dev] [Bug 1604266] Re: yade not working prpoperly on Ubuntu/Kubuntu 16.04

This explains why I am not encountering this issue with the 16.04 LTS server version. -- You received this bug notification because you are a member of Yade developers, which is subscribed to Yade. https://bugs.launchpad.net/bugs/1604266 Title: yade not working prpoperly on Ubuntu/Kubuntu

[Yade-dev] [Bug 1666339] Re: DFNflow crashes for compiled trunk but not non-optimized debug compiled trunk

Hey Bruno, The compiler does not let me compile if I remove the pass-by-reference as you suggest. I have yet to run into another issue w.r.t this bug, so we can stick with the "magic" fix for now :-). Thank you for the assistance and for committing the fix. Best, Robert -- You received this

[Yade-dev] [Bug 1665973] Re: Triaxial Cohesive

Is there a reason you are trying to use TriaxialCompressionEngine instead of TriaxialStressController? TCE is deprecated. -- You received this bug notification because you are a member of Yade developers, which is subscribed to Yade. https://bugs.launchpad.net/bugs/1665973 Title: Triaxial

[Yade-dev] [Bug 1666339] Re: DFNflow crashes for compiled trunk but not non-optimized debug compiled trunk

First, thank you Bruno for the tips and please excuse my developing understanding of C++, CGAL, and YADE source. >If your idea was correct the current code would not work at all, you >need to include in the picture the fact that this same code actually >works for us without problem. I should

[Yade-dev] [Bug 1666339] Re: DFNflow crashes for compiled trunk but not non-optimized debug compiled trunk

I've narrowed it down to the cell1 and cell2 declarations. These objects are not playing nicely with CGAL's is_infinite, mirror_index, and neighbor functions. Here is my working theory: The cell1 and cell2 handles originate down at the facet_circulator on line 195 where an arbitrary facet is

[Yade-dev] [Bug 1666339] [NEW] DFNflow crashes for compiled trunk but not non-optimized debug compiled trunk

Public bug reported: Distro: Xenial 16.04LTS Yade Version: yade-2017-0207.git-11c276f Compilation: default compilation with debug flags and '#define DFNFLOW' uncommented in DFNFlow.cpp Summary: DFNFlowEngine crashes for compiled yade-2017-0207.git-11c276f sources. The segmentation fault also

Re: [Yade-dev] Using YADE with cloud computing - guide

entation. > > It is better to ask an opinion of other Yade`s developers, how to > proceed with it. > > Best regards > > Anton > > > 2016-12-29 18:35 GMT+01:00 Robert Caulk <rca...@eng.ucsd.edu>: > > Dear YADE devs, > > > > I recently spent some ti