Hello Karl,
Thanks for fixing the problem. ex19 runs now in parallel on GPU
on the last petsc-dev versions.
I got another problem though but will create another thread.
PL
Hi Pierre,
>> I could reproduce the problem and also get some uninitialized variable
warnings in Valgrind. The debug vers
Hi Pierre,
> I tried to rebuild the optimized PETSc library by changing several
options and ran:
mpirun -np 2 ./ex19 -cuda_show_devices -dm_mat_type aijcusp -dm_vec_type
cusp
-ksp_type fgmres -ksp_view -log_summary -pc_type none
-snes_monitor_short -snes_rtol 1.e-5
Options used:
--with-pthread
Previously, I had noticed strange behaviour when running the GPU code with
the threadComm package. It might be worth trying to disable that code in
the build to see if the problem persists?
-Paul
On Tue, Jan 14, 2014 at 9:19 AM, Karl Rupp wrote:
> Hi Pierre,
>
>
> >> I could reproduce the probl
Hi Pierre,
>> I could reproduce the problem and also get some uninitialized variable
warnings in Valgrind. The debug version detects these errors, hence
you only see the errors in the debug build. For the optimized build,
chances are good that the computed values are either wrong or may
become w
On 01/14/14 16:41, Karl Rupp wrote:
Hi Pierre,
> I try running in parallel the ex19 test case on CPU and GPU:
OPT="_opt"
dir=/ccc/cont002/home/den/triou/Version_test_airain-hybrid/Trio_U/lib/src/LIBPETSC/petsc/linux$OPT/src/snes/examples/tutorials
option="-pc_type none -ksp_type fgmres -sn
Hi Pierre,
> I try running in parallel the ex19 test case on CPU and GPU:
OPT="_opt"
dir=/ccc/cont002/home/den/triou/Version_test_airain-hybrid/Trio_U/lib/src/LIBPETSC/petsc/linux$OPT/src/snes/examples/tutorials
option="-pc_type none -ksp_type fgmres -snes_monitor_short -snes_rtol
1.e-5 -log_s
