Use of salvus_mesher

[Ben Fernando]

Hi, 

I was wondering whether it was possible to use salvus_mesher without installing all of salvus_wave? 

When following these instructions here: https://gitlab.com/Salvus/salvus_mesher/blob/master/README.md and using the 'python -m pymesher.tests' tests line, I get the error 'No module named salvus_wave.shape_mappings'.

I've tried to install salvus_wave anyway to see if that fixes the problem, but get another error when trying to configure petsc: "     UNABLE to CONFIGURE with GIVEN OPTIONS    (see configure.log for details):

-------------------------------------------------------------------------------

Mismatched single quotes in C library string". 

Any ideas? Sorry if this is just me being thick! 

Best

Ben 

[Michael Afanasiev]

Hi Ben,

I'll let the mesher developers answer the question about an independent install, but I believe that issue with PETSc is fixed with the current commit we give on our website. Can you run 'git status' in the petsc source directory? It should say HEAD detached at 0c7851c55c. If it does not, can you run git checkout 0c7851c55cba8e40da5083f79ba1ff846acd45b2 in that directory and see if it fixes the problem?

Cheers,

Mike.

--
You received this message because you are subscribed to the Google Groups "Salvus" group.
To unsubscribe from this group and stop receiving emails from it, send an email to salvus+un...@googlegroups.com.
To post to this group, send email to sal...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/salvus/f3049172-42c1-4920-97ab-a93ceb772e7f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Martin van Driel]

Hi Ben,

you only need the python bindings of salvus wave not the main code. There should be no dependency on petsc there.

Details on salvus.io under 'Python Support Modules'

Anyway, we only need this dependency in two places that are likely not crucial to most users, so we should allow to run the tests without this dependency.

Cheers,
Martin

To view this discussion on the web visit https://groups.google.com/d/msgid/salvus/5B063906-B7F0-43E9-A788-B4A2D9B39E8C%40gmail.com.

[Lion Krischer]

Hi Ben,

the mesher only needs the Python bindings from salvus_wave - no need to install PETSc for it. Just follow the first couple of steps here:

https://salvus.io/installation/#python-support-modules

You need the Python bindings to salvus_wave, pyexodus, and salvus_mesher.

Cheers!

Lion

To view this discussion on the web visit https://groups.google.com/d/msgid/salvus/5B063906-B7F0-43E9-A788-B4A2D9B39E8C%40gmail.com.

[Ben Fernando]

Hi Mike, 

Thanks, here’s what I have now:

MacBook-Pro-4:~ benfernando$ cd petsc

MacBook-Pro-4:petsc benfernando$ git status

HEAD detached at 0c7851c

Untracked files:

  (use "git add <file>..." to include in what will be committed)

petsc/

salvus_wave/

nothing added to commit but untracked files present (use "git add" to track)

MacBook-Pro-4:petsc benfernando$ git checkout 0c7851c55cba8e40da5083f79ba1ff846acd45b2

HEAD is now at 0c7851c... bib: fix URL for StarForest note

MacBook-Pro-4:petsc benfernando$ git status

HEAD detached at 0c7851c

Untracked files:

  (use "git add <file>..." to include in what will be committed)

petsc/

salvus_wave/

nothing added to commit but untracked files present (use "git add" to track)

Which still returns the same error (mismatched single quotes in c library string).

Thanks 

Ben 

[Michael Afanasiev]

Hi Ben,

Strange, usually that commit fixed the problem. If you still need PETSc (which as per the discussion below shouldn't be needed for the mesher), you can try adding --with-clib-autodetect=0 --with-cxxlib-autodetect=0 --with-fortranlib-autodetect=0 to the PETSc configure options... this usually helps as well.

Ref: http://lists.mcs.anl.gov/pipermail/petsc-users/2013-July/017847.html.

Let us know if that helps,

Mike.