problem with 3D pressure solver
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- hpc, testing-qa
Research direction
Reproduce the failures with the pcg program and cubicrayleigh using Rayleigh_run() and Nusselt_run(). Start with the MultigridMixedTest and PCGTest diagnostics, then run the CTest suite to compare the NaN, dead loop, and segmentation-fault behavior. Done means the 3D pressure solver converges and both failing tests pass.
Written by the indexing model from the issue text.
Description
What steps will reproduce the problem?
1. run pcg program
2. run cubicrayleigh with Rayleigh_run()
3. run cubicrayleigh with Nusselt_run()
What is the expected output? What do you see instead?
None of them converged, and the while loop is dead
Message similar to:
[INFO] Sol_MultigridPressure3DBase::do_fmg - error after 3 iterations: L2 =
0.000000 (221243.654747x), Linf = 0.000000 (-nanx)
There is a "nan", which likely lead to segmentation faults or dead loop
What version of the product are you using? On what operating system?
Ubuntu 10.04LTS 64bit, CUDA 3.2, GTX460 Fermi
Please provide any additional information below.
I have noticed that two of the 18 unit tests failed due to segmentation faults
and it should be related to 3D pressure solver.
The unit test diagnostic info is as below.
******************************************************************
The following tests FAILED:
12 - MultigridMixedTest (SEGFAULT)
17 - PCGTest (SEGFAULT)
Errors while running CTest
make: *** [test] Error 8
******************************************************************
Thanks!
Original issue reported on code.google.com by yush...@gmail.com on 28 Nov 2010 at 5:03
- Dominant language
- Cuda
- Stars
- 6
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ExpectationMax/opencurrent
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
ExpectationMax/opencurrent#23 · 1 comment ·
-
all tests failed Openauto-migrated Priority-Medium Type-Defect
Difficulty 4/5 3-5 days Newbie friendliness 25/100
ExpectationMax/opencurrent#20 · 1 comment ·
-
auto-migrated Priority-Medium Type-Defect
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
auto-migrated Priority-Medium Type-Defect
Difficulty 4/5 3-5 days Newbie friendliness 28/100
-
auto-migrated Priority-Medium Type-Defect
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
ExpectationMax/opencurrent#17 · 1 comment ·
All issues in ExpectationMax/opencurrent
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
canonical/slurmutils#82 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
C++ Enhancement Examples
Difficulty 2/5 1-3 hours Newbie friendliness 84/100