Hello Helvi,
> we could compile the toolkit on MareNostrum4 without any further
> problems ("unset MPI" did the trick), and I want to run some further
> tests before providing the configuration script.
That sounds great. There are already (outdated) marenostrum files in
simfactory, you may just as well remove those (or re-use the file
names).> What is the standard way to include new configuration files into the > toolkit? Should I send it to someone in particular? Simplest is to "fork" the simfactory2 repo on bitbucket: https://bitbucket.org/simfactory/simfactory2/fork then add the new files, create a pull request https://bitbucket.org/simfactory/simfactory2/pull-requests/new and finally create an ET ticket linking to the pull request https://trac.einsteintoolkit.org/newticket . Ideally set the ticket status to "Review" so that it shows up. Yours, Roland -- My email is as private as my paper mail. I therefore support encrypting and signing email messages. Get my PGP key from http://pgp.mit.edu .
pgpcd6xykkaHa.pgp
Description: OpenPGP digital signature
_______________________________________________ Users mailing list [email protected] http://lists.einsteintoolkit.org/mailman/listinfo/users
