Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Which petsc version officially supported by the new version of libmesh (libmesh-1.3.0) ? #1775

Closed
Nilooab opened this issue Jul 1, 2018 · 11 comments

Comments

@Nilooab
Copy link

Nilooab commented Jul 1, 2018

Which petsc version officially supported by the new version of libmesh (1.3.0)?

@jwpeterson
Copy link
Member

Let's see... v1.3.0 was tagged April 9, 2018. The released version of PETSc at that time was technically 3.9, but only by a couple days. So I'd say it should support PETSc 3.8 but might also work with 3.9.

@Nilooab
Copy link
Author

Nilooab commented Jul 8, 2018

As I have tried PETSc3.7.7 is working. 3.8 and 3.9 could not support one of the examples!

@jwpeterson
Copy link
Member

3.8 and 3.9 could not support one of the examples!

Well don't leave us in suspense... which example was not working and what was the error message?

@Nilooab
Copy link
Author

Nilooab commented Jul 9, 2018 via email

@jwpeterson
Copy link
Member

I don't see any error message in what you pasted into your comment, possibly because it was too long for GitHub. Please post just the error instead of all of the output of 'make check'.

@Nilooab
Copy link
Author

Nilooab commented Jul 9, 2018 via email

@jwpeterson
Copy link
Member

Hmm... this error usually means you have PETSc compiled in debug mode, and we are attempting to modify a vector (usually the solution vector) at a time when it is not allowed. This is the first time I've seen the error in optimization_ex1, however.

@fdkong, I believe you have tested libMesh master and MOOSE with PETSc 3.9, but what about in debug mode?

@fdkong
Copy link
Contributor

fdkong commented Jul 9, 2018

I haven't tested PETSc in the debug mode for a while because we actually have similar issues in MOOSE, but I do not have a good idea to fix it.

@Nilooab
Copy link
Author

Nilooab commented Jul 10, 2018

I have compiled PETSc 3.7.7 in the same way, but I have not got this error!

@roystgnr
Copy link
Member

Thanks for the update! If your system is working with 3.7.7 then it's probably not a system specific problem, we're almost certainly doing something that we shouldn't be but that older PETSc is letting us get away with.

I'll build a PETSc 3.9.3 module today and see if I can replicate the failure.

@roystgnr
Copy link
Member

I dropped the ball on this, but it looks like it got redetected in #1889 and fixed in #1898.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants