Update gsl path in Ranger option file to gsl 1.13

Create issue
Issue #326 closed
Bruno Mundim created an issue

Ranger config file has been updated recently, so I thought to bring to your attention that gsl library on Ranger now defaults to version 1.13.

Cheers, Bruno.

Keyword: Ranger
Keyword: option
Keyword: configuration
Keyword: gsl

Comments (8)

  1. Erik Schnetter
    • removed comment

    The default option list for Ranger is now ranger-intel11.cfg. This builds GSL with Cactus, using GSL 1.14. The old option list (ranger-mvapich2.cfg) still uses GSL 1.11.

    I am using the new option list. If you are still using the old option list and have tested GSL 1.13, then please send a patch.

  2. Bruno Mundim reporter
    • removed comment

    Thanks for letting us know of the new default. I will move to this new configuration file and will let you know if we face any problem.


  3. Bruno Mundim reporter
    • removed comment

    I forgot to ask: which thorn(s) use this new env variables defined at ranger-intel11.cfg?


    I see that ./CarpetLib/src/gdata.cc uses VECTORISE_ALIGNED_ARRAYS as a macro, but I am not sure which one uses VECTORISE. Is this documented somewhere?

    Also do these new variables mean we can drop -DKRANC_VECTORS in the CPPFLAGS?


  4. Erik Schnetter
    • removed comment

    The new defaults are chosen by the new ranger.ini file. I now realise that people won't pick up these changes unless they create a new configuration. That adds to the recent discussion on the SimFactory mailing list...

    The new settings VECTORISE etc. are used by a new version of LSUThorns/Vectors. Ian Hinder suggested this to improve the interface. We are currently working on incorporating vectorisation into Kranc (and thus McLachlan); after this is done I will update LSUThorns/Vectors. You can then drop the -DKRANC_VECTORS in CPPFLAGS.

  5. Ian Hinder
    • removed comment

    Either we should delete the old ranger-mvapich2.cfg optionlist, or we should apply Bruno's patch.

    Bruno, since the old file is still there, can you attach your patch to this ticket? Thanks

  6. Erik Schnetter
    • removed comment

    We should not delete this thorn list yet since it still works, and most people will not have switched over to the new one.

  7. Log in to comment