[Yade-dev] Law2_ScGeom_CapillaryPhys_Capillarity code workflow for erased interactions

also applies to Law2_ScGeom_CapillaryPhys_Capillarity1 [😉] [1]: https://github.com/yade/trunk/blob/master/pkg/dem/Law2_ScGeom_CapillaryPhys_Capillarity.cpp#L156 [2]: https://github.com/yade/trunk/blob/master/pkg/dem/Law2_ScGeom_CapillaryPhys_Capillarity.cpp#L164 ------

[Yade-dev] TriaxialStressController.externalWork sign

ample). Since we use the Force acting on the boundaries together with the boundaries velocities. Agree to revert this sign ? Jerome ------ Jerome Duriez, Research Associate University of Calgary, Dpt of Civil Engineer

Re: [Yade-dev] TriaxialStressController.externalWork sign

cation for TriaxialStressController.externalWork (http://w... · yade/trunk@6a9b617<https://github.com/yade/trunk/commit/6a9b6178ebade3c6d5ea6cbcdf439a9f20073648> github.com ...ww.mail-archive.com/yade-dev@lists.launchpad.net/msg12083.html) Thanks, Jerome -----

Re: [Yade-dev] TriaxialStressController.externalWork sign

al but I would not oppose any further changes ! ---------- Jerome Duriez, Research Associate University of Calgary, Dpt of Civil Engineering +1 403 220 7367 From: Yade-dev on behalf of Bruno Chareyre Sent: July-28-16 11:06 AM To: yade-d

[Yade-dev] Capillary scripts

s not include any capillary interactions at the moment, though ?) ------ Jerome Duriez, Research Associate University of Calgary, Dpt of Civil Engineering +1 403 220 7367 /

Re: [Yade-dev] Capillary scripts

? -- Jerome Duriez, Research Associate University of Calgary, Dpt of Civil Engineering +1 403 220 7367 From: Yade-dev on behalf of Jerome Duriez Sent: September-08-16 6:02 PM To: Yade dev Subject: [Yade-dev

Re: [Yade-dev] Capillary scripts

for suggestion ! Jerome ---------- Jerome Duriez, Research Associate University of Calgary, Dpt of Civil Engineering +1 403 220 7367 From: Yade-dev on behalf of Klaus Thoeni Sent: September-13-16 8:58 PM To: yade-dev@lists.launchpad.n

Re: [Yade-dev] Capillary scripts

Yes, they were coded by myself, indeed. -- Jerome Duriez, Research Associate University of Calgary, Dpt of Civil Engineering +1 403 220 7367 From: Anton Gladky Sent: September-14-16 1:14 PM To: Jerome Duriez

Re: [Yade-dev] Capillary scripts

Law2. With one new simulation script example and another old one, moved here ------ Jerome Duriez, Research Associate University of Calgary, Dpt of Civil Engineering +1 403 220 7367 From: Yade-dev on behalf

Re: [Yade-dev] [Branch ~yade-pkg/yade/git-trunk] Rev 3932: Friendlier BibTex entries for 2015 doc. To avoid Smilauer and et al in manuscripts

ublications on Yade — Yade 2016-08-24.git-0557faf ...<https://www.yade-dem.org/doc/publications.html> www.yade-dem.org Publications on Yade¶ This page should be a relatively complete list of publications on Yade itself or done with Yade. If you publish something, do not hesitate to ...

Re: [Yade-dev] [Branch ~yade-pkg/yade/git-trunk] Rev 3932: Friendlier BibTex entries for 2015 doc. To avoid Smilauer and et al in manuscripts

ny "joke" ? Jerome ---------- Jerome Duriez, Research Associate University of Calgary, Dpt of Civil Engineering +1 403 220 7367 From: Yade-dev on behalf of Bruno Chareyre Sent: September-26-16 4:12 AM To: yade-dev@lists.launchpad.net Subject: Re: [Yade-d

Re: [Yade-dev] [Branch ~yade-pkg/yade/git-trunk] Rev 3937: Update citing_yade.bib

To conclude, I think reverting was not appropriate here, could you please re-revert ? Thanks ! Jerome -- Jerome Duriez, Research Associate University of Calgary, Dpt of Civil Engineering +1 403 220 7367

Re: [Yade-dev] [Branch ~yade-pkg/yade/git-trunk] Rev 3953: Introduce Network::surfaceSolidThroatInPore() for partial solid surfaces per half-throat

lly enabled the TWOPHASEFLOW compilation) "error: 'class CGT::FlowBoundingSphere > >' has no member named 'surfaceSolidPore'" Thanks, Jerome [*] https://github.com/yade/trunk/blob/master/lib/triangulation/FlowBoundingSphere.ipp#L750 --------

Re: [Yade-dev] Frequency of documentation update

Has there been / is there / will there be changes on that side ? (Looking at the build log, I'm just seeing the last build was indeed November 1st, several commits ago) [*] https://yade-dem.org/buildbot/ <https://yade-dem.org/buildbot/> --------

Re: [Yade-dev] Frequency of documentation update

Last build was November 3rd (with many build requests pending since), sorry for the typo... From: Yade-dev on behalf of Jerome Duriez Sent: November 16, 2016 11:51 AM To: Yade dev Subject: Re: [Yade-dev] Frequency of documentation update Sorry guys, but the

[Yade-dev] FlowEngine.ipp.in: return values of volumeCell*()

fv/FlowEngine.ipp.in#L413 [4] https://github.com/yade/trunk/blob/master/pkg/pfv/FlowEngine.ipp.in#L412 ---------- Jerome Duriez, Research Associate University of Calgary, Dpt of Civil Engineering +1 403 220 7367 __

Re: [Yade-dev] FlowEngine.ipp.in: return values of volumeCell*()

Ok, I indeed figured out since, that my crashes are (obviously ?) not related with this difference. Thanks for the information though, Jerome -- Jerome Duriez, Research Associate University of Calgary, Dpt of Civil Engineering +1 403 220

Re: [Yade-dev] Frequency of documentation update

//yade-dem.org/doc/ -- Jerome Duriez, Research Associate University of Calgary, Dpt of Civil Engineering +1 403 220 7367 From: Yade-dev on behalf of Jerome Duriez Sent: November 16, 2016 11:51 AM To: Yade dev Subje

Re: [Yade-dev] [Branch ~yade-pkg/yade/git-trunk] Rev 4040: update of the JCFPM particle model with new or adapted functionalities to record number of cracks...

s for new "damageIndex" vs old "tensBreakRel" and "shearBreakRel". It seems to me we're losing information here. What were your motivations for these changes ? Cheers, Jérôme -- Jerome Duriez, Resea

[Yade-dev] No more commit emails ? (no more gitHub/trunk import into Launchpad)

ications were useful from my point of view) Jerome [*] http://www.mail-archive.com/yade-dev@lists.launchpad.net/msg12405.html ------ Jerome Duriez, Research Associate University of Calgary, Dpt of Civil Engineer

[Yade-dev] Removing one check (regression) test

e source before I push this regression script removal ? Thanks, Jerome ---------- Jerome Duriez, Research Associate University of Calgary, Dpt of Civil Engineering +1 403 220 7367 ___ Mailing list: https://l

[Yade-dev] Meaning/Doc of ViscoFrictPhys in connection with Law2_ScGeom6D_NormalInelasticityPhys_NormalInelasticity

n the docstring) ? Jerome [*] https://yade-dem.org/doc/yade.wrapper.html#yade.wrapper.ViscoFrictPhys ------ Jerome Duriez, Research Associate University of Calgary, Dpt of Civil Engineering +1 403 220

Re: [Yade-dev] Removing one check (regression) test

erome ------ Jerome Duriez, Research Associate University of Calgary, Dpt of Civil Engineering +1 403 220 7367 From: Yade-dev on behalf of Bruno Chareyre Sent: June 28, 2017 1:53 AM To: yade-dev@lists.launchpa

Re: [Yade-dev] 2nd Yade-DEM workshop

scussion... Jerome ------ Jerome Duriez, Research Associate University of Calgary, Dpt of Civil Engineering +1 403 220 7367 From: Yade-dev on behalf of Bruno Chareyre Sent: July 13, 2017 10:13 AM To: Yade developers Subject: [Ya

Re: [Yade-dev] 2nd Yade-DEM workshop

'Azur, along the Mediterranean). Thoughts ? Jerome ------ Jerome Duriez, Research Associate University of Calgary, Dpt of Civil Engineering +1 403 220 7367 From: Yade-dev on behalf of Bruno Chareyre Sen

Re: [Yade-dev] 2nd Yade-DEM workshop

Jérôme Le 04/09/2017 à 18:21, Jerome Duriez a écrit : Hi there, I 'm now in my new position (notwithstanding the used email address) in french institute Irstea. It seems my new boss is very open to the idea of such a workshop, probably including for what concerns his wallet.

Re: [Yade-dev] 2nd Yade-DEM workshop

s at Uni Twente, July 22-26 2019. Another international conference people might be attending is SolMech 2018, 27-31 Aug in Warsaw. Thanks again for organising this. Klaus On Fri, 29 Sep 2017 01:11:33 PM Jerome Duriez wrote: Dear all; Attached is a very first draft of a possible "Call&qu

[Yade-dev] YADE builds manually caused by unknown ?

Hi there, Out of curiosity, is there actually someone who is asking the buildbot to perform so much builds (of old revisions ?) ? I'm referring here to the kind of builds [1] for which we got (quite often) this kind of email [2] The fact that the "Revision" and "Got Revision" fields are often

Re: [Yade-dev] 2nd YADE workshop: Aix-en-Provence (France), April 26-27, 2018

Dear YADE users and developers, A gentle reminder on the second YADE workshop: *Discrete-based modeling of multi-scale coupled problems* to be held in *Aix-en-Provence* (south of France), on *April 26-27*, 2018. Deadline for *abstract submission* has just been extended to *February 2*, while

Re: [Yade-dev] Yade related publication?

Hi Robert, Regarding your last two specific questions, my personal answers are "no". Regarding, the general idea of your proposal, maybe I may refer you to a YADE-related paper published in SoftwareX (a journal aiming to give some credit to code development "per se" in scientific research, tha

[Yade-dev] Mathjax for math output in doc ?

Hi, When I locally build the doc for my local YADE versions (launching "make doc" from the build folder, and browsing afterwards doc/sphinx/_build/html/ in this build folder), all maths latex commands do not display properly in the local html pages I get. Typing $k_n$ (or directly :math:`k_n`)

Re: [Yade-dev] Mathjax/imgmath for math output in doc ?

/ext/math.html#module-sphinx.ext.imgmath -- Chargé de Recherche / Research Associate Irstea, RECOVER 3275 route de Cézanne – CS 40061 13182 Aix-en-Provence Cedex 5 FRANCE +33 (0)4 42 66 99 21 A free DEM conference in April: https://2ndyadeworkshop.sciencesconf.org/ On 20/02/2018 10:45, Jerome

Re: [Yade-dev] Mathjax/imgmath for math output in doc ?

/ Research Associate Irstea, RECOVER 3275 route de Cézanne – CS 40061 13182 Aix-en-Provence Cedex 5 FRANCE +33 (0)4 42 66 99 21 A free DEM conference in April: https://2ndyadeworkshop.sciencesconf.org/ On 20/02/2018 10:56, Jerome Duriez wrote: The equations from https://yade-dem.org/doc/ actually lo

[Yade-dev] Ip2_FrictMat_FrictMat_FrictPhys doc

Hi, After seeing Yet Another Doubts on "young" meaning / Ip2_FrictMat_FrictMat_FrictPhys contact model (a PhD student in my institute), I'm proposing to explicitly mention the underlying equations in the doc, once for all. The corresponding would-be diff appears at the end of the email, you ma

Re: [Yade-dev] Ip2_FrictMat_FrictMat_FrictPhys doc

https://2ndyadeworkshop.sciencesconf.org/ On 22/02/2018 17:04, Bruno Chareyre wrote: Hi Jérôme, I am not in favor of removing some documentation, thank you for asking. In my view such patch would be a regression. I don't understand the motivation, see below. On 02/21/2018 05:59 PM, Jerom

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

Hi, I can not reproduce --test and --checks failures on my machine. And it seems similar failures already occured with previous commits. I'll assume for now there is no problem with my last commit https://github.com/yade/trunk/commit/12ed7b43ebfe25d5566950dce2d0e489519359c1... Let me know

Re: [Yade-dev] Cmake !find metis and cholmod

Hi Bruno, I can compile 2018-05-22.git-f538da1 (I just "git pulled") without any problem. Here are some of my cmake outputs, for info: -- 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.

[Yade-dev] Use of boost::python::extract() in Engine::action()

Hi, In connection with the bug [*], I'm trying to familiarize myself with boost::python. As an example, I would like to extract in the c++ world a python integer, something I can achieve outside YADE but not within: When building my own c++ program (see the attached testBP.cpp) the two foll

Re: [Yade-dev] Python 2 removal

Hi Anton, I'd consider this idea, ie I have some time and motivation, and no knowledge.. :-) Moreover / instead possible personal efforts, I could also look into the possibility proposing a dedicated internship to some IT (with an emphasis on the "I") student. Since I do not have a precise p

Re: [Yade-dev] About pastebin and data files in launchpad questions

Hi all, I agree Bruno with your description of the annoying extra efforts that are required to try to help with such questions. As far as I am concerned, I do not try downloading things and help in these cases... My first suggestion would be to further push users to propose (for real !!!) mi

[Yade-dev] Why _utils.hpp and Shop.hpp ? Shop::getPorosity vs Shop__getPorosity

Hi, What is the reason for having (for instance) Shop__getPorosity() in py/_utils.hpp/cpp and Shop::getPorosity() in pkg/dem/Shop.hpp / Shop_01.cpp ? I can see the latter has "scene" as an argument [1] in addition to "volume" (contrary to the former [2]), but probably this could be removed

Re: [Yade-dev] Why _utils.hpp and Shop.hpp ? Shop::getPorosity vs Shop__getPorosity

ost::python tricks, which IMO should be placed in a separate file, so py/_utils.*pp would stay anyway (although it could be cleaner). cheers Jan [1] https://github.com/yade/trunk/blob/master/py/_utils.cpp#L111 2018-07-16 11:21 GMT+02:00 Jerome Duriez <mailto:jerome.dur...@irstea.fr&g

[Yade-dev] Dynamic vs Fixed for bodies utils functions

Hi, As you may know, the Python (utils module) functions for creating bodies make a more or less redundant use of the two "dynamic" and "fixed" boolean parameters. It seems to me both are usually accepted with different behaviors: - for sphere() and box(), both are passed to _commonBodySetup

Re: [Yade-dev] Dynamic vs Fixed for bodies utils functions

aning (or is it already clear that fixed == !dynamic everywhere?), then it is easy to make both accepted through aliasing. Removing one of the two seems awkward based on your summary. Cheers B Le jeu. 26 juil. 2018 18:07, Jerome Duriez <mailto:jerome.dur...@irstea.fr>> a écrit : Hi,

[Yade-dev] Shop::aabbExtrema() : from boost::python::tuple return type to std::vector ?

Hi again, I would like changing in pkg/dem/Shop*pp the py::tuple aabbExtrema() [*] to std::vectoraabbExtrema() (keeping obviously the Python exposure). I think this would - make the Shop C++ files one (small) step closer from the ideal situation discussed at https://www.mail-archive.com/y

Re: [Yade-dev] Shop::aabbExtrema() : from boost::python::tuple return type to std::vector ?

n a vector<>. I would point out that the implementation of this function looks sloppy in various other ways: - dereferencing body pointer without checking it - dynamic cast - only works for spheres Isn't there a more generic extrema function somewhere? I'm wondering. Bruno On

Re: [Yade-dev] Shop::aabbExtrema() : from boost::python::tuple return type to std::vector ?

std::pair, Eigen::Matrix1, 0, 3, 1> > -- Chargé de Recherche / Research Associate Irstea, RECOVER 3275 route de Cezanne – CS 40061 13182 Aix-en-Provence Cedex 5 FRANCE +33 (0)4 42 66 99 21 On 13/08/2018 11:33, Jerome Duriez wrote: See this commit. <https://github.com/yad

[Yade-dev] Compilation (cmake) options Doc

Hi, In the source installation doc [*] I'm proposing to directly point towards https://github.com/yade/trunk/blob/master/CMakeLists.txt for a list of compilation options, instead of having the paragraph "The following options are available: [...]" In the current state, there are at least thr

Re: [Yade-dev] Compilation (cmake) options Doc

ed to produce a self-contained printable document. If some content is removed from this document it is clearly a regression. Bruno (*) e.g. "(an updated list can be retrieved _here_)" On 09/03/2018 02:51 PM, Jerome Duriez wrote: Hi, In the source installation doc [*] I'm propos

Re: [Yade-dev] Building Documentation

Hi Alex, At least, I get the same behavior as you, here. Cheers, Jérôme -- Chargé de Recherche / Research Associate Irstea, RECOVER 3275 route de Cezanne – CS 40061 13182 Aix-en-Provence Cedex 5 FRANCE +33 (0)4 42 66 99 21 On 10/10/2018 18:05, Eulitz, Alexander wrote: Hi, I just tried

Re: [Yade-dev] Buildbot failure

Hi Robert, My understanding of these failures was rather there was read/write permission problems on the buildbot ? [*] As you probably know, the buildbot is in Grenoble 3SR lab, and only Bruno and remi.caillet...@3sr-grenoble.fr (but Rémi is no more at 3SR if I understood correctly ?...) co

[Yade-dev] Mathr::ZERO_TOLERANCE vs Mathr::EPSILON

Hello, Out of curiosity, why do we have both Mathr::ZERO_TOLERANCE and Mathr::EPSILON in the code [*] ? I would understand they're both intended to give an expected magnitude of rounding errors. (Note that ZERO_TOLERANCE is hardcoded as 1e-20, while EPSILON is ~ 2e-16 here) Both are used t

Re: [Yade-dev] Mathr::ZERO_TOLERANCE vs Mathr::EPSILON

ly wrong: if (std::abs(cn1) <= Mathr::ZERO_TOLERANCE ) cn1=0; If it's small let it be small. No need to make it zero. And since cn1 is not dimensionless it implies that currently the accuracy depends on a specific choice of units... Bruno Bruno On 11/15/18 3:54 PM, Jerome Dur

Re: [Yade-dev] Migrating to GitLab

Hello everyone, In terms of Gitlab vs Github Lazyness would tend to make me think to stay on github to avoid the need for adaptation (at least registering a new account on gitlab I guess ?), but this is not a real opinion. Hence some questions. Would we have

Re: [Yade-dev] [Yade-users] [Question #676841]: the definition of porosity

As for me, I subscribe to Bruno's presentation: better speak in terms of normal component of relative displacement between centers. Jérôme -- Chargé de Recherche / Research Associate Irstea, RECOVER 3275 route Cezanne – CS 40061 13182 Aix-en-Provence Cedex 5 FRANCE +33 (0)4 42 66 99 21 On

Re: [Yade-dev] Migrating to GitLab

Hi, Trying to (somewhat, at least) follow the discussion, I'd come back to The main branches * master * develop Definitely. in connection with the above-mentioned web post [1]. Thus, a question: What would be the purpose splitting / the definition of "master" and "develop" ?

Re: [Yade-dev] Migrating to GitLab

[..] with master-develop approach. [..] you really need to know, why do you need it. Thanks for feedback Anton, that's my point :-) Considering that a develop->master step still needs to be clarified, with different opinions at the moment between Bruno (below) and Janek (07/01/2019 à 17:31 ema

Re: [Yade-dev] Migrating to GitLab

On 08/01/2019 17:50, Bruno Chareyre wrote: On Tue, 8 Jan 2019 at 09:56, Jerome Duriez <mailto:jerome.dur...@irstea.fr>> wrote: let's maybe try to avoid switching from only one branch to more than three ?... We have already 19 branches on github/yade/trunk, plus

Re: [Yade-dev] Migrating to GitLab

Hi Bruno, Thank you for everything. It was a reason for new ways of doing things (the merge requests, in particular), it's maybe time to ask what does YADE development (if not "we") may expect as investment from Grenoble "in exchange" ? Good hopes to maintain all that we have in spite of possi

Re: [Yade-dev] Migrating to GitLab

Cedex 5 FRANCE +33 (0)4 42 66 99 21 On 17/01/2019 18:12, Bruno Chareyre wrote: On 1/17/19 5:53 PM, Jerome Duriez wrote:  it's maybe time to ask what does YADE development (if not "we") may expect as investment from Grenoble "in exchange" ? Who is expecting something, fr

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

Is there any practical preference between .rst or latex files? In my opinion : - .rst files, and being somehow part of the doc, as we see it on https://yade-dem.org/doc, is much more visible and much easier to maintain (by different people, in particular) : it's under git version control fo

Re: [Yade-dev] gitlab work cycle

Hi, [1]https://yade-dev.gitlab.io/trunk/github.html?highlight=gitlab#pushing-changes-to-remote-repository What's this https://yade-dev.gitlab.io/trunk/ ?... Is our doc now located at that place, and no more at https://yade-dem.org/doc/ ?... Jérôme -- Chargé de Recherche / Research

Re: [Yade-dev] Fixing the examples

Hello, As for jointedCohesiveFrictionalPM, gravityBis.py is working and is intended to replace gravityLoading.py + packInGtsSurface.py. While identificationSpheresOnJoint.py is not supposed to be called for itself, and could be replaced by identifBis.py (the latter being used by gravityBis.p

Re: [Yade-dev] [Yade-users] [Question #678982]: about TriaxialStressController

Hi, Regarding [*] and the comment "|the mask is the integer whose binary representation is xyz" at|[**], do we agree that - 3 = 11 = 011 in binary [***] (and not 110) ?And that 1 = 001 (and not 100 as in [**]) - and that the comment at [**] should read "|the mask is the integer whose binar

[Yade-dev] Deploy stage in Gitlab's pipeline

Hello, What is the deploy stage in Gitlab's pipeline ? (which fails in the last changes on trunk-exp [*] just because deploy does not apply to trunk-exp ?) I thought it should be defined in .gitlab-ci.yml but it's not ? Thanks, Jérôme [*] https://gitlab.com/yade-dev/trunk-exp/commit/538c7

[Yade-dev] Web doc reflecting another branch than master ?

Hi, As of now, https://yade-dev.gitlab.io/trunk/ tells me it describes "Yade version 2019-03-19.git-a36504b / 2019-03-19.git-a36504b" As a matter of fact, https://yade-dev.gitlab.io/trunk/installation.html#prerequisites mentions as required packages "libopenmpi-dev libopenmpi1.10 openmpi-bin

Re: [Yade-dev] Web doc reflecting another branch than master ?

trunk/commit/e2900d8552e7875623ef32ec0a20ad038e2469b3 On Tue, 19 Mar 2019 at 10:54, Jerome Duriez <mailto:jerome.dur...@irstea.fr>> wrote: Hi, As of now, https://yade-dev.gitlab.io/trunk/ tells me it describes "Yade version 2019-03-19.git-a36504b / 2019-03-19.git

[Yade-dev] Updating Launchpad (Code) page

Hi, I think https://code.launchpad.net/yade (reached eg after cliking on "Code" at the top of https://launchpad.net/yade) clearly needs to be updated: - it still mentions about bazaar (I even can not remember when we left this tool...) - it also still mentions about gitHub... Obviously, so

Re: [Yade-dev] Call for testing, updated yadedaily packages

Hi, Here (Ubuntu 18.04 Bionic) *** Your instructions worked like a charm (I already had yadedaily package). I now have (note just the VERSIONYADEREPLACE that may need to be replaced) jerome.duriez@AXP17003:~$ yadedaily Welcome to Yade VERSIONYADEREPLACE Using python ve

Re: [Yade-dev] Call for testing, updated yadedaily packages

On 05/07/2019 14:07, Janek Kozicki wrote: I should write about this process in the developer documentation also. I actually just understood more (hopefully) what these dockers are.. And I just realized the docker files like this one

Re: [Yade-dev] Python inheritance

Hi, For your information, I also faced at some point segfaults with boost::python stuff during O.run() and not O.step() : https://www.mail-archive.com/yade-dev@lists.launchpad.net/msg13223.html (I never really solved / understood it.. If you know e.g. boost mutex more than me -- that won't b

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

I remove trailing whitespace at the end of the line, provided that I am changing this line for some *other* purpose. Sounds good to me, as far (not much ?...) as I'm concerned. -- Chargé de Recherche / Research Associate Irstea, RECOVER 3275 route Cezanne – CS 40061 13182 Aix-en-Provence Ce

Re: [Yade-dev] AddressSanitizer is enabled in the CI-pipeline

Hi, you can see in the pipeline Is there yet an example in recent pipeline jobs ? I looked at that job from ASAN merge request #331 and could not see anything new. What's the exact workflow ? Running --test and --check and look for some err

Re: [Yade-dev] AddressSanitizer is enabled in the CI-pipeline

Ah, it seems it's basically /make_asan/ jobs in the /build/ part of our pipelines... Found it.. On 12/11/2019 10:02, Jerome Duriez wrote: Hi, you can see in the pipeline Is there yet an example in recent pipeline jobs ? I looked at that job <https://gitlab.com/yade-dev/trun

Re: [Yade-dev] Call for testing, updated yadedaily packages

el/equipes/jerome-duriez On 27/06/2019 21:15, Anton Gladky wrote: Dear all, yadedaily packages are being under renovation at the moment. And now they need to be tested. I want to ask you to do it and give a feedback. 3 Distributions are supported: - Debian Buster - Debian Stretch - Ubuntu 18

[Yade-dev] Vector outputs in LOG macros vs cout

nterest to that question ! ;-) Jérôme -- Chargé de Recherche / Research Associate Inrae, RECOVER 3275 route Cezanne – CS 40061 13182 Aix-en-Provence Cedex 5 FRANCE +33 (0)4 42 66 99 21 https://www6.paca.inrae.fr/recover/membres-du-laboratoire/pages-personnell

[Yade-dev] Vector3 unsigned int

/ Research Associate Inrae, RECOVER 3275 route Cezanne – CS 40061 13182 Aix-en-Provence Cedex 5 FRANCE +33 (0)4 42 66 99 21 https://www6.paca.inrae.fr/recover/membres-du-laboratoire/pages-personnelles/jerome-duriez ___ Mailing list: https://launchpad.n

Re: [Yade-dev] Vector3 unsigned int

search Associate Inrae, RECOVER 3275 route Cezanne – CS 40061 13182 Aix-en-Provence Cedex 5 FRANCE +33 (0)4 42 66 99 21 https://www6.paca.inrae.fr/recover/membres-du-laboratoire/pages-personnelles/jerome-duriez On 08/04/2020 16:49, Bruno Chareyre wrote: Hi Jérôme, Out of curiosity, do you have concrete

[Yade-dev] Sign convention O.energy['gravWork']

te Cezanne – CS 40061 13182 Aix-en-Provence Cedex 5 FRANCE +33 (0)4 42 66 99 21 https://www6.paca.inrae.fr/recover/membres-du-laboratoire/pages-personnelles/jerome-duriez ___ Mailing list: https://launchpad.net/~yade-dev Post to : yade-dev@list

Re: [Yade-dev] Sign convention or name O.energy['gravWork']

13182 Aix-en-Provence Cedex 5 FRANCE +33 (0)4 42 66 99 21 https://www6.paca.inrae.fr/recover/membres-du-laboratoire/pages-personnelles/jerome-duriez On 20/04/2020 10:25, Jerome Duriez wrote: Hi, Is there a consensus (outside myself) for the extra minus sign in O.energy['gravWork'], c

Re: [Yade-dev] Sign convention or name O.energy['gravWork']

ANCE +33 (0)4 42 66 99 21 https://www6.paca.inrae.fr/recover/membres-du-laboratoire/pages-personnelles/jerome-duriez On 28/04/2020 16:27, Bruno Chareyre wrote: Hi Jérôme, I feel like it is a question of perspective, and undecidable overall. Is it work by gravity or work against gravity? You can

Re: [Yade-dev] [PATCH] correct Law2_ScGeom_ViscElPhys_Basic documentation to match source code, see https://answers.launchpad.net/yade/+question/691021

elles/jerome-duriez On 20/07/2020 20:49, Daniel Kiracofe wrote: Please find attached a quick patch to correct Law2_ScGeom_ViscElPhys_Basic documentation to match source code, per discussion https://answers.launchpad.net/yade/+question/691021 (apologies for the delay between the launchpad questio

[Yade-dev] Wiki FAQ

zanne – CS 40061 13182 Aix-en-Provence Cedex 5 FRANCE +33 (0)4 42 66 99 21 https://www6.paca.inrae.fr/recover/membres-du-laboratoire/pages-personnelles/jerome-duriez ___ Mailing list: https://launchpad.net/~yade-dev Post to : yade-dev@lists.lau

Re: [Yade-dev] Wiki FAQ

e.fr/recover/membres-du-laboratoire/pages-personnelles/jerome-duriez On 21/07/2020 16:00, Jan Stránský wrote: I also would not entirely delete the page / content. maybe they should go somewhere else, but where? one option is to put them to the source code in the .rst format and create a ne

Re: [Yade-dev] Wiki FAQ

-laboratoire/pages-personnelles/jerome-duriez On 22/07/2020 11:03, Bruno Chareyre wrote: Thanks. I would keep that one too (even for myself): === I would like to add a new page to YADE wiki. How can I do it? === B On Wed, 22 Jul 2020 at 09:22, Jerome Duriez <mailto:jerome.dur...@inrae.fr>&

[Yade-dev] GitLab repo archives

. Do you confirm my observations ? Was that on purpose ? Jérôme -- Chargé de Recherche / Research Associate INRAE, RECOVER 3275 route Cezanne – CS 40061 13182 Aix-en-Provence Cedex 5 FRANCE +33 (0)4 42 66 99 21 https://www6.paca.inrae.fr/recover/membres-du-laboratoire/pages-personnelles/jerome

Re: [Yade-dev] GitLab repo archives

) Thanks ! -- Chargé de Recherche / Research Associate INRAE, RECOVER 3275 route Cezanne – CS 40061 13182 Aix-en-Provence Cedex 5 FRANCE +33 (0)4 42 66 99 21 https://www6.paca.inrae.fr/recover/membres-du-laboratoire/pages-personnelles/jerome-duriez On 15/10/2020 15:28, Bruno Chareyre wrote:

Re: [Yade-dev] New Yade version, beginning of January 2021

miss that train. Jérôme -- Chargé de Recherche / Research Associate INRAE, RECOVER 3275 route Cezanne – CS 40061 13182 Aix-en-Provence Cedex 5 FRANCE +33 (0)4 42 66 99 21 https://www6.paca.inrae.fr/recover/membres-du-laboratoire/pages-personnelles/jerome-duriez On 12/11/2020 22:18, Anton Glad

[Yade-dev] Post Doc position particles' shape

regards, Jérôme Duriez -- Chargé de Recherche / Research Associate INRAE, RECOVER 3275 route Cezanne – CS 40061 13182 Aix-en-Provence Cedex 5 FRANCE +33 (0)4 42 66 99 21 https://www6.paca.inrae.fr/recover/membres-du-laboratoire/pages-personnelles/jerome-duriez

Re: [Yade-dev] Post Doc position particles' shape

Dear Yade devs, Attachment finally is at https://stratus.irstea.fr/f/5ef9fde069f24c35ba66/?dl=1 ... (Not sure it was my mistake here or some Launchpad feature -- https://bugs.launchpad.net/launchpad/+bug/244673 ?) Sorry again, Jérôme On 02/12/2020 09:34, Jerome Duriez wrote: Dear Yade

Re: [Yade-dev] Introducing Yade discord beta

zanne – CS 40061 13182 Aix-en-Provence Cedex 5 FRANCE +33 (0)4 42 66 99 21 https://www6.paca.inrae.fr/recover/membres-du-laboratoire/pages-personnelles/jerome-duriez On 06/05/2021 19:55, Robert Caulk wrote: Hey Yade devs, A few of us were discussing the *idea of encouraging more collaboration*

Re: [Yade-dev] Dev meeting next week

-personnelles/jerome-duriez On 15/07/2021 11:13, Bruno Chareyre wrote: Dear Yade devs, For a few months now some of us started holding meetings to discuss dev aspects. We figured it would be good to gather more of the devs in these meetings, so if you are interested and available you are welcome to

Re: [Yade-dev] Submitting Yade to an "Open Software" prize (FYI)

Hi guys, Good news, I'm willing to join. Best, -- Chargé de Recherche / Research Associate INRAE, RECOVER 3275 route Cezanne – CS 40061 13182 Aix-en-Provence Cedex 5 FRANCE +33 (0)4 42 66 99 21 https://www6.paca.inrae.fr/recover/membres-du-laboratoire/pages-personnelles/jerome-durie

Re: [Yade-dev] Yade vs. war in Ukraine

3275 route Cezanne – CS 40061 13182 Aix-en-Provence Cedex 5 FRANCE +33 (0)4 42 66 99 21 https://www6.paca.inrae.fr/recover/membres-du-laboratoire/pages-personnelles/jerome-duriez On 03/03/2022 18:16, Bruno Chareyre wrote: Hi guys, My heart is broken since the beginning of that war on Ukrai

Re: [Yade-dev] [deprecated list] [svn] r1527 - trunk/pkg/dem

Janek Kozicki a écrit : jduriez at BerliOS said: (by the date of Thu, 25 Sep 2008 19:19:58 +0200) - Add of the paragraph for the CL1Relationships, which was forgotten, in the corresponding SConscript Did you remember to 'svn add' the CL1Relationships.cpp .hpp and commit it?

Re: [Yade-dev] ContactLaw1

Václav S a écrit : Jerome, I am sorry, but how about some more meaningful name instead of "ContactLaw1"? I am even more sorry than you but I have sincerely not much idea. As I wrote it in the files this law is in fact quite similar to the CohesiveFrictionnalContactLaw. The differences are

Re: [Yade-dev] r1527 - trunk/pkg/dem

Janek Kozicki a écrit : Do you have this commit email somewhere? Unfortunately not... I added : - a preprocessor named "SimpleShear" whose aim was to replace "DirectShearCis" (comment in this last one to let notice it) - Engines adapted to this preprocessor to simulate constant normal dis

Re: [Yade-dev] ContactLaw1

About merging "ContactLaw1" in "CohesiveFrictionalContactLaw", an other problem would be : - My "ContactLaw1" uses relationsships and interactions different from the one of "CohesiveFrictionalContactLaw". Especially, in the interactions I use I have to store such things as a "unmax" (the maximum

Re: [Yade-dev] ContactLaw1

(Sorry for the private email Vaclav, this one was not intentional) Václav Šmilauer a écrit : Hi there, I implemented ElasticContactLaw2 (for ilustration) that behaves like ElasticContactLaw (except that all contact are cohesive (don't break) and there is no moment rotation law) and uses new Sph

Re: [Yade-dev] Incomprehensible crash

Vincent Richefeu a écrit : The following is the beginning of the console log: It's better if you send the whole message. It seems hard to believe but some of us succeed in understanding something from it ! Jerome ___ Mailing list: https://launc

  1   2   3   >