st somewhere else if we
@ drop launchpad?
@ B
Janek Kozicki (yade) said: (by the date of Tue, 29 Aug 2023 19:36:56 +0200)
> I am testing yade-dev mailing list. I can see latest Bruno's email in
> the mailing list archive:
>
> https://lists.launchpad.net/yade-dev/date.html
I am testing yade-dev mailing list. I can see latest Bruno's email in
the mailing list archive:
https://lists.launchpad.net/yade-dev/date.html
but I didn't receive it as email.
I wonder what's going on.
Janek
--
Janek Kozicki, PhD. DSc. Arch. Assoc. Prof.
Gdansk University of Technology (Gdans
Hi,
I created update Changelog MR for this:
https://gitlab.com/yade-dev/trunk/-/merge_requests/917/diffs
best regards
Janek
Anton Gladky said: (by the date of Mon, 16 Jan 2023 21:16:59 +0100)
> Dear all,
>
> as always at the beginning of the year we are preparing
> the stable Yade Release
> Bruno
>
>
> On 15/10/2022 15:55, Janek Kozicki (yade) wrote:
> > Great, let me know in case of problems :-))
> >
> > Janek
> >
> > Anton Gladky said: (by the date of Sat, 15 Oct 2022 14:48:28 +0200)
> >
> >> Thanks, Janek! It really
Great, let me know in case of problems :-))
Janek
Anton Gladky said: (by the date of Sat, 15 Oct 2022 14:48:28 +0200)
> Thanks, Janek! It really works!
>
> Anton
>
>
> Am Sa., 15. Okt. 2022 um 14:19 Uhr schrieb Janek Kozicki (yade) <
> jkozicki-y...@pg.edu.pl>
with the emphasis on the last entry: "/var/run/docker.sock:/var/run/docker.sock"
it was necessary to make the docker work in docker-prod.
The first two entries are the typical ccache stuff, which we use regularly.
best regards
Janek
Janek Kozicki (yade) said: (by the date of Sat, 15 Oct
Hi,
I have created a single group runner, called loop1-group-runner, in:
https://gitlab.com/groups/yade-dev/-/runners?runner_type[]=GROUP_TYPE
now it appears in every of our projects. Also there is a
yade-runner-01, last time I checked it ran out of disc space and
couldn't do any jobs. Maybe it
Bruno,
when you will be testing on ubuntu 2022.04, you should be also able
to launch the high precision ones:
yade-longdouble
yade-float128
yade-mpfr150
please give them a try.
best regards
Janek
--
Janek Kozicki, PhD. DSc. Arch. Assoc. Prof.
Gdansk University of Technology (Gdansk Tech)
Facul
Yes, good idea. Let's do this. It is so sad and crazy.
Janek
Bruno Chareyre said: (by the date of Thu, 3 Mar 2022 18:16:48 +0100)
> Hi guys,
>
> My heart is broken since the beginning of that war on Ukraine.
> I believe international cooperation is one of our value in the Yade
> community.
Thank you Anton for creating this list. I have just added a few more
items there, including some ideas which I had in mind for a long
time. Some of them are difficult, but doable.
https://gitlab.com/yade-dev/trunk/-/issues/251
This is the TODO list at which my students will start looking at on
Ma
I might have misplaced some merge request titles. Then please edit this list.
Short summary of 2022.01a release:
short title (Merge Request count)
Documentation (40 MRs)
clang-format & reorganize (21 MRs)
Bug fixes
Hello everyone,
We are holding dev meetings on zoom once every two months. 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 join next meeting.
It will be on Wednesday, March 16th at 11:00 CEST time.
Please reply in
nical Engineering
> Department of Civil and Environmental Engineering (DICA)
> Politecnico di Milano
> Piazza Leonardo da Vinci, 32 - 20133 Milan (IT)
> Skype: boschikatia
>
>
> Da: Yade-dev
> per conto di Deepak Kn
> Data: martedì, 9 novembre 2021 20:00
> A: Janek Ko
BTW, Klaus, here in Europe just three days ago we have switched to
winter time. That's one hour shift.
Janek Kozicki (yade) said: (by the date of Tue, 2 Nov 2021 15:32:27 +0100)
> Hello everyone,
>
> Just a reminder that tomorrow we have a developer zoom meeting at 11:0
Hello everyone,
Just a reminder that tomorrow we have a developer zoom meeting at 11:00 CET.
If someone yet uninvited wants to join I hope there's still time to
reply to this message to get the zoom link from Klaus.
best regards
Janek
--
--
Janek Kozicki, PhD. DSc. Arch. Assoc. Prof.
Gdansk Un
n a problem, I checked and I cannot find the email
> you talk about. Sorry for the unconvenience, as said in the last email,
> my gitlab account name: raphm1.
>
> Best regards,
>
> Raphaël
>
> Le 30/08/2021 à 16:03, Janek Kozicki (yade) a écrit :
> > Hi, I recal
Hi, I recall that month ago Bruno has sent you an email asking about
your gitlab account name.
best regards
Janek
Raphaël Maurin said: (by the date of Mon, 30 Aug 2021 15:08:35 +0200)
> Dear all,
>
> Following the question I asked some times ago on the users launchpad
> [1], can someone ad
You can create a fork on your own profile, then create a merge request
from your profile to yade-dev.
Then it will go though our pipeline, like for example this MR:
https://gitlab.com/yade-dev/trunk/-/merge_requests/511
I guess we need to update docs about this.
best regards
Janek
Daniel Kiraco
Cool! I am this guy: https://xkcd.com/1782/
I found some irssi-discord bridge plugins, will try them :-)
best regards
Janek
Robert Caulk said: (by the date of Thu, 6 May 2021 19:55:23 +0200)
> Hey Yade devs,
>
> A few of us were discussing the *idea of encouraging more collaboration*
> amo
<
> bruno.chare...@3sr-grenoble.fr>:
>
> >
> > On 06/03/2021 17:06, Janek Kozicki (yade) wrote:
> >
> > I am not exactly sure what you want to discuss,
> >
> > I don't know either LOL. That's more an announcement in advance so someone
>
Hi,
I am not exactly sure what you want to discuss, so I will answer
some random parts of your email, and you will see that I completely
misunderstood :)
Do you want to create some sort of packages with yade installed inside?
Anton is building .deb packages for various distros.
Do you want to ma
Hi Bruno,
There is a boost::mpi library built on top of OpenMPI, MPICH2, IntelMPI [0].
In the introduction [1] they say it's just a wrapper for OpenMPI,
MPICH2 and IntelMPI. By using boost you could have some extra safety.
Example [2]:
int main(int argc, char* argv[])
{
mpi::environment env(ar
Hi Gaël,
> p₃ = 1 - p₂ - p₃ (1c)
If p₃ was previously uninitialized (or zero). Then this equation must
be incorrect by definition, it uses p₃ on right side.
Ah, but in your photos [1] you wrote p₃ = 1 - p₁ - p₂. :-)
> I also think I might need the confirmation that t
> (It seems the yade project started using clang-format (or similar
> tool) sometime between e07e530 and 1b4ae97 so `diff` outputs half
> the file: not very helpful… 😆️)
Hi,
reformat with the same .clang-format file your old branch (*). Then
you will be back to meaningful diffs. I used this trick
This is an awesome team effort. Congratulations everyone. This year was
great, let's make the next one even better :)
cheers
Janek
Anton Gladky said: (by the date of Thu, 28 Jan 2021 19:58:35 +0100)
> Dear Yade users and developers,
>
> As always at the beginning of the year we are releasin
port for GUI dropdown menus.
===
Are the extra debian packages yade-long-double or yade-float128, maybe even
yade-mpfr150
even possible?
best regards
Janek
Janek Kozicki (yade) said: (by the date of Sun, 6 Dec 2020 00:26:03 +0100)
> Hi Anton,
>
> Do you think that you c
Hi Anton,
Do you think that you could also prepare yade-long-double or
yade-float128, maybe even yade-mpfr150 packages?
Better if all of them used ENABLE_MPFR, to avoid slow boost::cpp_bin_float.
It would work great to protect (via dpkg tests caused by changes in
other packages) our achievement
Hi, it is great that you move forward with packaging a new yade
release. I will take some time to write a bit in the release notes
link which you provided.
best regards
Janek
Anton Gladky said: (by the date of Thu, 12 Nov 2020 22:18:55 +0100)
> Dear Yade users and developers,
>
> As always
I confirmed in person. Issue resolved. Good luck!
We did plenty of work during the summer holidays, you will see in the latest
MRs and commits :)
cheers
Janek
Bruno Chareyre said: (by the date of Wed, 7 Oct 2020 11:57:33 +0200)
> Hi there,
>
> I've had a number of independent issues latel
Hi Luc,
your patch does not pass the pipeline:
https://gitlab.com/yade-dev/trunk/-/merge_requests/512/pipelines
feel free to correct it and open another merge request. It is now
possible to run pipelines for forked projects [1][2] so it is much
easier now for you to submit a merge request.
best
Bruno Chareyre said: (by the date of Mon, 18 May 2020 21:22:41 +0200)
> On Mon, 18 May 2020 at 19:16, Janek Kozicki (yade)
> wrote:
>
> > They are listed in the pipeline and marked as
> > success, but inside you only have "Skipping this test, because it
eaching step2 build-doc as fast as possible.
> 95% of the pipeline is a waste.
> Ok, maybe that's too specific and I should just trick gitlab.ci... but
> still, compiling with 5 number formats in the minimal build is a bit
> overkill maybe.
> B
>
>
>
> On Mon, 18 May
includes building doc now, do you confirm?
> Things change fast! (for good :)
> B
>
> On Mon, 18 May 2020 at 14:35, Janek Kozicki (yade)
> wrote:
>
> > Yes, we have a quick pipeline. Add the "WIP: " in front of the title.
> > It is being checked by th
Yes, we have a quick pipeline. Add the "WIP: " in front of the title.
It is being checked by the build system (searach for WIP in
gitlab-ci.yml file :), and some builds are cancelled if they start
with WIP:
cheers
Janek
Bruno Chareyre said: (by the date of Mon, 18 May 2020 12:51:33 +0200)
>
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! :)
> >>
&
Hi, welcome here! :)
Bruno is leading the MPI programming effort, I will let him do the honors ;)
BTW, he is in the middle of finishing the docs :)
best regards
Janek
Sacha Duverger said: (by the date of Thu, 14 May 2020 13:39:37 +0200)
> Hello,
>
> I’ve been using YADE since over a year
This might become useful someday, if gitlab.com will start having some problems:
https://git.pg.edu.pl/explore
plus the university's IT team is pretty responsive.
I didn't create yade-dev group there or anything (yet).
--
Janek Kozicki, PhD. DSc. Arch. Assoc. Prof.
Gdańsk University of Techno
OK, I think it is fixed in latest MR
https://gitlab.com/yade-dev/trunk/-/merge_requests/446
please try it.
Janek Kozicki (yade) said: (by the date of Fri, 20 Mar 2020 22:36:36 +0100)
> Hi Jerome,
>
> it is not on purpose. I find it annoying too. I will have a look :)
> I gues
Hi Jerome,
it is not on purpose. I find it annoying too. I will have a look :)
I guess it has got something with operator<< somewhere.
My university shifted to online courses, this takes more time than I
would like. I hope that soon I will manage to do some work with yade.
best regards
Janek
J
equests/438
:-))
> Thanks
> Bruno
>
> Le mar. 10 mars. 2020 20:28, Janek Kozicki (yade)
> a écrit :
>
> > Bruno Chareyre said: (by the date of Tue, 10 Mar 2020 13:10:24 +0100)
> > > That's what puzzled me in the first place. So deeply that I didn't da
Bruno Chareyre said: (by the date of Tue, 10 Mar 2020 13:13:47 +0100)
> Do you mean to reformat the whole repository?
yes, exactly. Sorry for so many merge requests (again). This time I
was thinking that maybe someone was working in ./core and not in ./lib
directory. Maybe I should have done
Bruno Chareyre said: (by the date of Tue, 10 Mar 2020 13:10:24 +0100)
> That's what puzzled me in the first place. So deeply that I didn't dare
> replying to the question. :)
Ah sorry, here's exactly what I meant:
qt5/GLViewer.cpp, function postSelection() was written by Anton in 2015-06-26
ärz 2020 um 23:07 Uhr schrieb Janek Kozicki (yade)
> :
> >
> > If we decided to remove qt4, then we need to decide which version of
> > GLViewer::postSelection(…) to use, because `meld gui/qt4 gui/qt5`
> > shows that this function is the only one that differs between the
If we decided to remove qt4, then we need to decide which version of
GLViewer::postSelection(…) to use, because `meld gui/qt4 gui/qt5`
shows that this function is the only one that differs between the two
directories.
Janek Kozicki (yade) said: (by the date of Sun, 8 Mar 2020 22:54:07
These last two merge requests have duplicate changes in both directories.
The changes are identical, because I did
git diff --staged > /tmp/z.patch
# edit file, replace qt5 with qt5
patch -p1 < /tmp/z.patch
but having two copies of same stuff isn't healthy. Does anyone still use qt4?
best
that part does not support HP.
> I think we can skip the float pipeline. :)
> Cheers
> Bruno
>
>
>
> On Sun, 1 Mar 2020 at 16:24, Janek Kozicki (yade)
> wrote:
>
> > Hi,
> >
> > The high precision tests are now running in the gitlab pipeline. An
Hi,
The high precision tests are now running in the gitlab pipeline. And
we can be sure that `double` are not getting by accident into master.
(except for the modules which are not supported by HP right now [1],
in there some `double` could sneak in)
This work also makes low-precision possible. I
We have met Jidong Zhao, the sudoDEM co-author, at the last yade
workshop. Perhaps we should ask him directly?
Bruno Chareyre said: (by the date of Thu, 27 Feb 2020 15:52:08 +0100)
> Dear Shiewei,
> I was trying to use and to check something in the source code of sudoDEM3D
> today.
> Howeve
gt; As far as I see, there is not benefit for us to replace boost::python,
> at least right now?
>
> Regards
>
> Anton
>
> Am So., 23. Feb. 2020 um 16:02 Uhr schrieb Janek Kozicki (yade)
> :
> >
> > > Another note: I just realized that the compilation benc
> Another note: I just realized that the compilation benchmarks might
> have not been fair, because I think that I added few more
> registrations (like Vector2c, or sth. like that) while doing pybind
> migration. I will compare again without these extra registrations.
OK, I have compared with the
Hi Anton
> sorry for delays, "real" life is taking much more time when we get older :)
please don't worry. I really appreciate all your hard work. I got a
little carried away, I'm sorry.
> > * I would rather avoid pybind11 switch in a rush, better give it a few
> > months
> Maybe I was not clea
r alternative ways to help you to integrate
> high-precision stuff.
>
> [1] https://ftp-master.debian.org/new.html
>
> Best regards
>
> Anton
>
> Am Fr., 21. Feb. 2020 um 22:30 Uhr schrieb Janek Kozicki (yade)
>
> :
> >
> > Hi Anton,
> >
>
OK, I will experiment a bit and see what it takes to switch to pybind11.
Janek
Janek Kozicki (yade) said: (by the date of Fri, 21 Feb 2020 22:30:04 +0100)
> Hi Anton,
>
> Yes, the number of defines in Serialization.hpp is crazy.
> Changing/removing them to use pybind11 would t
RAM.
>
> We should really have a look at pybind11 alternative, if it accelerates the
> compilation. But when I see Serialization.hpp, I am getting crazy from the
> number of "defines" there.
>
> Anton
>
> Am Fr., 21. Feb. 2020 um 17:04 Uhr schrieb Janek Koz
>
> The newer minieigen can now be polished, new version released and
> uploaded with no rush.
>
> [1] https://github.com/eudoxos/minieigen/pull/24
> [2] https://github.com/eudoxos/minieigen/pull/25
>
> Best regards
>
> Anton
>
> Am Mi., 19. Feb. 2020 um 22
yade high precision is not going to compile.
best regards
Janek
Janek Kozicki (yade) said: (by the date of Thu, 20 Feb 2020 21:57:54 +0100)
> Thank you Anton, this is very considerate of you.
>
> best regards
> Janek
>
> Anton Gladky said: (by the date of Thu, 20 Feb 20
ebian.
>
> The newer minieigen can now be polished, new version released and
> uploaded with no rush.
>
> [1] https://github.com/eudoxos/minieigen/pull/24
> [2] https://github.com/eudoxos/minieigen/pull/25
>
> Best regards
>
> Anton
>
> Am Mi., 19.
ve no enough permissions to do it.
>
> Regards
>
> Anton
>
> Am Mo., 17. Feb. 2020 um 13:18 Uhr schrieb Janek Kozicki (yade)
> :
> >
> > Hi,
> >
> > Vaclav has accepted my pull request to minieigen. The macro name is
> > now `_HIGH_PRECISION_SUPPOR
eanup.
best regards
Janek
[1] https://github.com/eudoxos/minieigen/pull/24
[2] https://github.com/eudoxos/minieigen
[3] https://gitlab.com/yade-dev
Janek Kozicki (yade) said: (by the date of Mon, 3 Feb 2020 15:48:19 +0100)
> In the attachment are the minimal minieigen patches:
>
>
Hi, we have moved to gitlab. The launchpad bugracker is not used. I have moved
this issue to: https://gitlab.com/yade-dev/trunk/issues/143
I tried to reproduce the error, and I have a lockup during doctests stage in
yade --test:
SpherePack_toSimulation (yade.pack)
Doctest: yade.pack.SpherePack
e_requests/383/diffs?commit_id=fff0dc8fda163d57f8816e61201660cd3b6a0a38
[4] https://gitlab.com/yade-dev/trunk/-/merge_requests/362
[5] https://gitlab.com/yade-dev/docker-yade/container_registry
Janek Kozicki (yade) said: (by the date of Mon, 27 Jan 2020 21:38:09 +0100)
> Hi Anton,
>
> > Can we a
in Yade tree many years
> ago and we managed to drop them, introducing minieigen packages.
> It would not be the best variant to put them in the source again.
>
> [1] https://gitlab.com/yade-dev/trunk/-/merge_requests/396
>
> Regards
>
> Anton
>
> Am Mo., 27. Jan. 202
.
thanks a lot for your work.
best regards
Janek
BTW, Anton did you notice that building debian package fails on
master due to missing python-gts?
https://gitlab.com/yade-dev/trunk/issues/139
Janek Kozicki (yade) said: (by the date of Mon, 13 Jan 2020 22:34:25 +0100)
> Hi, the c
Hi, the code for high precision is complete and passes all the tests.
I am writing documentation for this now, I will mention there:
- about VTK ↔ double compatibility
- about GLViewer ↔ double compatibility
- how to build and run high precision code
I have separated most of this work in to sever
urrently validating it and updating the documentation.
> > Can we fix a date, say : 13th Jan (coming monday ? )
> >
> > On Tue, Jan 7, 2020 at 12:53 PM Janek Kozicki (yade) <
> > jkozicki-y...@pg.edu.pl> wrote:
> >
> >> This is great. Thank yo
This is great. Thank you very much for your hard work!
Anton Gladky said: (by the date of Mon, 6 Jan 2020 21:04:35 +0100)
> Dear Yade developers,
>
> I am starting to tag the new release. It happens within the next few days.
>
> Regards
>
> Anton
>
> Am Di., 10. Dez. 2019 um 12:55 Uhr sc
Dear Pranjal,
we are currently having some problems with this server. Before it is
fixed you can use documentation locally, by installing yade-doc
package. Or by browsing an online backup on gitlab:
https://yade-dev.gitlab.io/-/trunk/-/jobs/394371575/artifacts/public/index.html
best regards
Jane
I started https://gitlab.com/yade-dev/trunk/merge_requests/368
to try to fix this problem with CGAL.
Janek Kozicki (yade) said: (by the date of Thu, 2 Jan 2020 21:45:29 +0100)
> Thanks for fixing this. Now I see another problem:
>
> CGAL is disabled on bullseye.
>
ladky said: (by the date of Wed, 1 Jan 2020 19:55:33 +0100)
> We can temporarily try to switch to debian:sid, where this
> problem is probably fixed a couple of days ago.
>
> Anton
>
> Am Di., 31. Dez. 2019 um 23:38 Uhr schrieb Janek Kozicki (yade)
> :
> >
>
> reading sources... [ 37%] introduction
> >
> >
> >
> >
> >
> >
> >
> >
> > Janek Kozicki (yade) said: (by the date of Mon, 30 Dec 2019 14:28:17
> > +0100)
> >
> > > Janek Kozicki (yade) said: (by the date of Mon, 3
-reference
reading sources... [ 32%] index-toctree-theory
reading sources... [ 33%] index-toctree_manuals
reading sources... [ 35%] installation
reading sources... [ 37%] introduction
Janek Kozicki (yade) said: (by the date of Mon, 30 Dec 2019 14:28:17 +0100)
> Janek Kozicki (y
Janek Kozicki (yade) said: (by the date of Mon, 30 Dec 2019 14:00:50 +0100)
> Regarding the version numbers I made an MR which workarounds the problem:
>
> https://gitlab.com/yade-dev/trunk/merge_requests/367
>
> I am not sure if that's the correct way to go. Isn'
ast commit in master:
https://gitlab.com/yade-dev/trunk/commit/0b6b10845892801b0893be211e011bdc1707f8cd/pipelines?ref=master
We can see when it stopped working.
Interestingly the libCGAL problem seems to disappear for now?
best regards
Janek
Janek Kozicki (yade) said: (by the date of S
I just noticed following problems after new bullseye image has been built:
ImportError: libCGAL.so.13: cannot open shared object file: No such
file or directory
Image was built 14h ago:
container registry: https://gitlab.com/yade-dev/docker-yade/container_registry
Also in the pipeline in one
Great that you found out. Sorry for not helping you with this, I was
too focused on high precision support.
Anton Gladky said: (by the date of Mon, 9 Dec 2019 21:48:47 +0100)
> The problem was really in python3.8 and ipython in Debian Sid.
>
> See:
>
> https://bugs.debian.org/946481
>
> A
A very simple explanation of how && works: do this command:
ls && ls /wrongdir && ls
Then do this command:
ls && ls && ls
You will see that in the first case the failure of 'ls /wrongdir'
prevented execution of last 'ls'. That's how && works. The next
command is executed only if the previous on
Bruno Chareyre said: (by the date of Mon, 21 Oct 2019 11:57:28 +0200)
> Hi Anton,
> It's not yet all clear to me how it will work.
> What would be the workflow in general for, let's say, a kdevelop/kate user?
> Edit, then "git-clang-format" before commit?
I pushed the script `scripts/clang-fo
It’s a great idea. And I’m surprised how personal it is for me :) Code
readability is top priority for me. I’m sure we will find the clang-format
settings which suits us.
Automatic checks if the recently touched files (e.g files from the current MR)
were reformatted will definitely help us. At
I remove trailing whitespace at the end of the line, provided that I am
changing this line for some *other* purpose.
I prefer to avoid changing lines only for the sake of formatting, because that
will eventually cause unwanted and unnecessary merge conflicts later.
Also I tend to add a newline
In case of problems, I mean :)
Janek Kozicki (yade) said: (by the date of Fri, 11 Oct 2019 15:47:27 +0200)
> BTW, I have also configured bullseye to use 7pak. Feel free to set others to
> use 7pak too.
>
>
> Janek Kozicki (yade) said: (by the date of Fri, 4 Oct 2019
BTW, I have also configured bullseye to use 7pak. Feel free to set others to
use 7pak too.
Janek Kozicki (yade) said: (by the date of Fri, 4 Oct 2019 16:30:18 +0200)
> The schedule to build images seems to have some problems:
>
> https://gitlab.com/yade-dev/docker-yade/pipeline_
t;>
> >>
> >>
> >> On Tue, 8 Oct 2019 at 10:56, William Chèvremont
> >> >> <mailto:william.chevrem...@univ-grenoble-alpes.fr>> wrote:
> >>
> >> Hi,
> >>
> >> @Janek
> >>
> >> Yes, I
Only a quick question to make sure - you have read
https://yade-dem.org/doc/prog.html#subclassing-c-types-in-python in
documentation?
best regards
Janek
___
Mailing list: https://launchpad.net/~yade-dev
Post to : yade-dev@lists.launchpad.net
Unsu
> How about *-dbgsym packages, with debug symbols?
I see that you tried to add it:
https://gitlab.com/yade-dev/trunk/commit/26147d8d55c1c77ae7d34139b1ff7ddd59ec19ca
But unfortunately we are hitting some hardcap limit on gitlab :(
Uploading artifacts...
./deb: found 12 matching files
The schedule to build images seems to have some problems:
https://gitlab.com/yade-dev/docker-yade/pipeline_schedules
however I have succesfully configures 7pak to be able to build these images. I
didn't test all of them, only the most "difficult" one:
https://gitlab.com/yade-dev/docker-yade/pip
Thank you for thanking me Anton :)
I am very happy that we all can work together so efficiently.
I have tested these instructions in chroots. It works! :)
How about *-dbgsym packages, with debug symbols?
best regards
Janek
Anton Gladky said: (by the date of Thu, 3 Oct 2019 07:42:09 +0200)
Hi Klaus, this looks very much like the errors which I have been fixing two
months ago. It seems that Robert and Luc were not aware that to compile with
CGAL 4.11 we have to use Tri.locate(CGT::Sphere(…)) and when writing ->point()
we should instead write ->point().point() (regardless of how sil
Awesome! Thank you! :-)
On 22 Feb 2018, 21:12 +0100, Anton Gladky , wrote:
> Dear Yade developers,
>
> the new minor Yade 2018.02b was released on 20-th of February.
> It allows us to compile Yade against CGAL_4.11 and fixes some
> bugs. Tarballs are available on GitHub [1] and Launchpad [2].
>
>
When it comes to documentation, for me it’s: never remove anything, always
improve :)
On 21 Feb 2018, 22:25 +0100, Robert Caulk , wrote:
> 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 Yad
This is awesome. Thank you very much. I have just compiled the latest version,
and I confirm that DEM-PFV test works.
Finding uninitialized variables can be a super difficult job, hence:
congratulations! And I must say that I am surprised why there was no warning
about this variable. I specific
he moment?
> > Bruno
> >
> >
> >
> > On 02/08/2018 06:35 PM, Anton Gladky wrote:
> > >
> > > Well, if we find a way to fix it within the next 2 weeks,
> > > I think there is a chance to get it pushed into Debian->Ubuntu.
> > >
>
This is a great effort, I saw you squashed dozens of bugs yesterday. Great!
Regarding compiling yade with CGAL 4.11, I can look into it on Saturday, if my
last patches didn't work for you? I am currently on a trip and have with me
just a small laptop. The last patches I've sent is what I current
Hi Robert,
I think that it’s a great idea. Especially if we could use it to directly
improve the documentation. I suppose that virtually everything that we could
write about using yade could be somehow fit into the sphinx docs. Like in
Jerome said, my specific answers to two of your questions a
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 +01
94 matches
Mail list logo