← Back to team overview

yade-dev team mailing list archive

Re: Block Generation, Contact Detection, Rock Bolt and Rock Lining

 

Dear Boon,
From now on I would suggest to communicate through the yade-dev mailing list. Packaging CLP _with_ Yade (if you really meant to include CLP in yade source) is not an option as it would progressively diverge from the main version. CLP should be installed independently of Yade via package manager, just like every other library yade is using.
Cheers
Bruno

On 09/12/2016 08:46 AM, Chia Weng Boon wrote:

Dear Jan,

Thanks for your reply. The codes developed during my PhD and based on integration efforts in March:


Potential Particles:

https://drive.google.com/open?id=0BzNu2_9w6dfwYmRYM25UdFhZRmc


Potential Blocks:

https://drive.google.com/open?id=0BzNu2_9w6dfwdlN4N0tEcDBoUnM


They should compile and run fine (March version). I would imagine further integration effort is desirable to maintain coherence of the programming style, but not mandatory for running the code, if time is limited for you. Of course packaging CLP with YADE in the next release might take some effort. Thanks Jan again.


Thanks,

Boon

------------------------------------------------------------------------
*From:* Jan Stránský <honzik.stransky@xxxxxxxxx>
*Sent:* Friday, September 9, 2016 8:16:56 PM
*To:* Chia Weng Boon
*Cc:* bruno.chareyre@xxxxxxxxxxxxxxx; s.utili@xxxxxxxxxxxxx; yade-dev@xxxxxxxxxxxxxxxxxxx; chiaweng@xxxxxxxxx; Chia Weng Boon *Subject:* Re: [Yade-dev] Block Generation, Contact Detection, Rock Bolt and Rock Lining
Dear all,
sorry for not responding, I am completely out of time until Sep 17. Then I hope I will have some time on this topic.

@Boon: for the sake of clarity, could you please send once more all the files that needs to be integrated (even if you have sent them already and did not do any changes from that time)?
thanks in advance :-)
maybe also those that are already implemented, I did some modifications but did not test them very much, I am afraid after my modifications the particles does not work as expected..

cheers
Jan


2016-09-07 1:22 GMT+02:00 Chia Weng Boon <booncw@xxxxxxxxxxx <mailto:booncw@xxxxxxxxxxx>>:

    Bruno,

    The one shared in January is a different algorithm called
    Potential Pariticles. It can accomodate a variety of shapes from
    rounded to polyhedral.  I can see that Jan has helped me clean the
    code and assisted in the Marching Cube display (Thanks Jan!).
    Previously I was relying on vtk files and displaying through
    ParaView. The algorithm is solved using conic optimisation. I
    commented out parts of the code where an external library Mosek is
    called. It is optional but highly recommended. Now the algorithm
    relies on the in house code I wrote for the conic solver.

    The code that I shared in March is different and is for polyhedral
    blocks which I call Potential Blocks. It relies on external
    libraries eg CLP. It is faster than Potential Particles. It comes
    with a suite of Block Generation, Rock bolt and lining routines.
    This is not available in trunk yet. Probably there is lots of
    cleaning to do. Its availability in trunk can be done in a
    progressive manner starting from just the Potential Blocks first.
    I am thinking Jan would perhaps be the best administrator to
    assist, if his time permits it since he had helped with uploading
    and cleaning of the PotentialParticle code previously.  Jan, would
    you be available to assist please? I know you are occupied with
    your PhD/postdoc work?

    Boon


    Get Outlook for Android <https://aka.ms/ghei36>




    On Wed, Sep 7, 2016 at 1:17 AM +0800, "Bruno Chareyre"
    <bruno.chareyre@xxxxxxxxxxxxxxx
    <mailto:bruno.chareyre@xxxxxxxxxxxxxxx>> wrote:



    On 09/06/2016 03:47 PM, Chia Weng Boon wrote:

    Dear Bruno,


    Yes it is working as expected.  I have shared the codes since
    March, but it is still not in the public domain.  So,  I was
    wondering if there are any difficulties faced by YADE's
    administrators to make it available.  I thought it could be the
    external library.

    What do you mean by "public domain"?
    As I see it the code is already publicly available for everyone as
    part of trunk since January (see e.g. [1] - thx. to Jan).
    Do I miss something?


      In fact, I had also shared the modifications to the
    Makefile how the library could be linked.  If it is shared, the
    user is supposed to compile his own version of CLP.

    That is not a very good point. Why not using the packaged version
    of CLP available through standard package manager (you don't
    compile your own firefox, then why compiling your own CLP?)?.

    Bruno

    [1]
    https://github.com/yade/trunk/commit/576941f605609384c32fb95c47e4e26225b0d6e8
    <https://github.com/yade/trunk/commit/576941f605609384c32fb95c47e4e26225b0d6e8>



    _______________________________________________
    Mailing list: https://launchpad.net/~yade-dev
    <https://launchpad.net/%7Eyade-dev>
    Post to     : yade-dev@xxxxxxxxxxxxxxxxxxx
    <mailto:yade-dev@xxxxxxxxxxxxxxxxxxx>
    Unsubscribe : https://launchpad.net/~yade-dev
    <https://launchpad.net/%7Eyade-dev>
    More help   : https://help.launchpad.net/ListHelp
    <https://help.launchpad.net/ListHelp>



--
_______________
Bruno Chareyre
Associate Professor
ENSE³ - Grenoble INP
Lab. 3SR
BP 53
38041 Grenoble cedex 9
Tél : +33 4 56 52 86 21
Fax : +33 4 76 82 70 43
________________

Email too brief?
Here's why! http://emailcharter.org


References