<div dir="ltr"><div dir="ltr">Satish, can you tell me how I might configure SuperLU_dist w/o this _OPENMP ?<br></div><div>Thanks,</div><div>Mark</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jan 21, 2021 at 11:57 PM Xiaoye S. Li <<a href="mailto:xsli@lbl.gov" target="_blank">xsli@lbl.gov</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div style="font-family:verdana,sans-serif;font-size:small;color:rgb(0,0,0)">All the OpenMP calls are surrounded by<br></div><div style="font-family:verdana,sans-serif;font-size:small;color:rgb(0,0,0)"><br></div><div style="font-family:verdana,sans-serif;font-size:small;color:rgb(0,0,0)">#ifdef _OPENMP</div><div style="font-family:verdana,sans-serif;font-size:small;color:rgb(0,0,0)">...</div><div style="font-family:verdana,sans-serif;font-size:small;color:rgb(0,0,0)">#endif</div><div style="font-family:verdana,sans-serif;font-size:small;color:rgb(0,0,0)"><br></div><div style="font-family:verdana,sans-serif;font-size:small;color:rgb(0,0,0)">You can disable openmp during Cmake installation, with the following:</div><div style="font-family:verdana,sans-serif;font-size:small;color:rgb(0,0,0)"> -Denable_openmp=FALSE</div><div style="font-family:verdana,sans-serif;font-size:small;color:rgb(0,0,0)">(the default is true)</div><div style="font-family:verdana,sans-serif;font-size:small;color:rgb(0,0,0)"><br></div><div style="font-family:verdana,sans-serif;font-size:small;color:rgb(0,0,0)">(I think Satish knows how to do this with PETSc installation)</div><div style="font-family:verdana,sans-serif;font-size:small;color:rgb(0,0,0)"><br></div><div style="font-family:verdana,sans-serif;font-size:small;color:rgb(0,0,0)">-------</div><div style="font-family:verdana,sans-serif;font-size:small;color:rgb(0,0,0)">The reason to use mixed MPI & OpenMP is mainly less memory consumption, compared to pure MPI. Timewise probably it is just slightly faster. (I think that's the case with many codes.)</div><div style="font-family:verdana,sans-serif;font-size:small;color:rgb(0,0,0)"><br></div><div style="font-family:verdana,sans-serif;font-size:small;color:rgb(0,0,0)"><br></div><div style="font-family:verdana,sans-serif;font-size:small;color:rgb(0,0,0)">Sherry</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jan 21, 2021 at 7:20 PM Mark Adams <<a href="mailto:mfadams@lbl.gov" target="_blank">mfadams@lbl.gov</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jan 21, 2021 at 10:16 PM Barry Smith <<a href="mailto:bsmith@petsc.dev" target="_blank">bsmith@petsc.dev</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><br><div><br><blockquote type="cite"><div>On Jan 21, 2021, at 9:11 PM, Mark Adams <<a href="mailto:mfadams@lbl.gov" target="_blank">mfadams@lbl.gov</a>> wrote:</div><br><div><div dir="ltr">I have tried it and it hangs, but that is expected. This is not something she has prepared for.<div><br></div><div>I am working with Sherry on it.<div><br>And she is fine with just one thread and suggests it if she is in a thread. <br><br></div><div>Now that I think about it, I don't understand why she needs OpenMP if she can live with OMP_NUM_THREADS=1.</div></div></div></div></blockquote><div><br></div> It is very possible it was just a coding decision by one of her students and with a few ifdef in her code should would not need the OpenMP but I don't have the time or energy to check her code and design decision.</div></div></blockquote><div><br></div><div>Oh yea there OMP calls like omp_num_threads() that need something. There is probably a omp1.h file somewhere in the world like our serial MPI.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div><br></div><div> Barry</div><div><br><blockquote type="cite"><div><div dir="ltr"><div><div><br></div><div>Mark</div><div><br></div></div></div><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jan 21, 2021 at 9:30 PM Barry Smith <<a href="mailto:bsmith@petsc.dev" target="_blank">bsmith@petsc.dev</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><br><div><br><blockquote type="cite"><div>On Jan 21, 2021, at 5:37 PM, Mark Adams <<a href="mailto:mfadams@lbl.gov" target="_blank">mfadams@lbl.gov</a>> wrote:</div><br><div><div dir="ltr">This did not work. I verified that MPI_Init_thread is being called correctly and that MPI returns that it supports this highest level of thread safety.<div><br></div><div>I am going to ask ORNL. <div><br></div><div>And if I use:</div><div><br><div>-fieldsplit_i1_ksp_norm_type none<br>-fieldsplit_i1_ksp_max_it 300</div><div><br></div><div>for all 9 "i" variables, I can run normal iterations on the 10th variable, in a 10 species problem, and it works perfectly with 10 threads.</div><div><br></div><div>So it is definitely that VecNorm is not thread safe.<br><div><br></div><div>And, I want to call SuperLU_dist, which uses threads, but I don't want SuperLU to start using threads. Is there a way to tell superLU that there are no threads but have PETSc use them?</div></div></div></div></div></div></blockquote><div><br></div> My interpretation and Satish's for many years is that SuperLU_DIST has to be built with and use OpenMP in order to work with CUDA. </div><div><br></div><div><div> def formCMakeConfigureArgs(self):</div><div> args = config.package.CMakePackage.formCMakeConfigureArgs(self)</div><div> if self.openmp.found:</div><div> self.usesopenmp = 'yes'</div><div> else:</div><div> args.append('-DCMAKE_DISABLE_FIND_PACKAGE_OpenMP=TRUE')</div><div> if self.cuda.found:</div><div> if not self.openmp.found:</div><div> raise RuntimeError('SuperLU_DIST GPU code currently requires OpenMP. Use --with-openmp=1')</div><div><br></div><div>But this could be ok. You use OpenMP and then it uses OpenMP internally, each doing their own business (what could go wrong :-)).</div><div><br></div><div>Have you tried it?</div><div><br></div><div> Barry</div><div><br></div><div><br></div><blockquote type="cite"><div><div dir="ltr"><div><div><div><div><br></div><div>Thanks,</div><div>Mark</div></div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jan 21, 2021 at 5:19 PM Mark Adams <<a href="mailto:mfadams@lbl.gov" target="_blank">mfadams@lbl.gov</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">OK, the problem is probably:<div><br><div>PetscMPIInt PETSC_MPI_THREAD_REQUIRED = MPI_THREAD_FUNNELED;<br></div></div><div><br></div><div>There is an example that sets:</div><div><br></div><div>PETSC_MPI_THREAD_REQUIRED = MPI_THREAD_MULTIPLE;<br></div><div><br></div><div>This is what I need.</div><div><br></div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jan 21, 2021 at 2:26 PM Mark Adams <<a href="mailto:mfadams@lbl.gov" target="_blank">mfadams@lbl.gov</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jan 21, 2021 at 2:11 PM Matthew Knepley <<a href="mailto:knepley@gmail.com" target="_blank">knepley@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr">On Thu, Jan 21, 2021 at 2:02 PM Mark Adams <<a href="mailto:mfadams@lbl.gov" target="_blank">mfadams@lbl.gov</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr">On Thu, Jan 21, 2021 at 1:44 PM Matthew Knepley <<a href="mailto:knepley@gmail.com" target="_blank">knepley@gmail.com</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr">On Thu, Jan 21, 2021 at 11:16 AM Mark Adams <<a href="mailto:mfadams@lbl.gov" target="_blank">mfadams@lbl.gov</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Yes, the problem is that each KSP solver is running in an OMP thread (So at this point it only works for SELF and its Landau so it is all I need). It looks like MPI reductions called with a comm_self are not thread safe (eg, the could say, this is one proc, thus, just copy send --> recv, but they don't)</div></blockquote><div><br></div><div>Instead of using SELF, how about Comm_dup() for each thread?</div></div></div></blockquote><div><br></div><div>OK, raw MPI_Comm_dup. I tried PetscCommDup. Let me this.</div><div>Thanks, </div></div></div></blockquote><div><br></div><div>You would have to dup them all outside the OMP section, since it is not threadsafe. Then each thread uses one I think.</div></div></div></blockquote><div><br></div><div>Yea sure. I do it in SetUp.</div><div><br></div><div>Well that worked to get <b>different Comms</b>, finally, I still get the same problem. The number of iterations differ wildly. This two species and two threads (13 SNES its that is not deterministic). Way below is one thread (8 its) and fairly uniform iteration counts.</div><div><br></div><div>Maybe this MPI is just not thread safe at all. Let me look into it.</div><div>Thanks anyway,</div><div><br></div><div> 0 SNES Function norm 4.974994975313e-03<br>In PCFieldSplitSetFields_FieldSplit with -------------- link: 0x80017c60. Comms pc=0x67ad27c0 ksp=<b>0x7ffe1600</b> newcomm=0x8014b6e0<br>In PCFieldSplitSetFields_FieldSplit with -------------- link: 0x7ffdabc0. Comms pc=0x67ad27c0 ksp=<b>0x7fff70d0</b> newcomm=0x7ffe9980<br> Linear fieldsplit_e_ solve converged due to CONVERGED_RTOL iterations 282<br> 1 SNES Function norm 1.836376279964e-05<br> Linear fieldsplit_e_ solve converged due to CONVERGED_ATOL iterations 19<br> 2 SNES Function norm 3.059930074740e-07<br> Linear fieldsplit_e_ solve converged due to CONVERGED_ATOL iterations 15<br> 3 SNES Function norm 4.744275398121e-08<br> Linear fieldsplit_e_ solve converged due to CONVERGED_ATOL iterations 4<br> 4 SNES Function norm 4.014828563316e-08<br> Linear fieldsplit_e_ solve converged due to CONVERGED_RTOL iterations 456<br> 5 SNES Function norm 5.670836337808e-09<br> Linear fieldsplit_e_ solve converged due to CONVERGED_ATOL iterations 2<br> 6 SNES Function norm 2.410421401323e-09<br> Linear fieldsplit_e_ solve converged due to CONVERGED_ATOL iterations 18<br> 7 SNES Function norm 6.533948191791e-10<br> Linear fieldsplit_e_ solve converged due to CONVERGED_RTOL iterations 458<br> 8 SNES Function norm 1.008133815842e-10<br> Linear fieldsplit_e_ solve converged due to CONVERGED_ATOL iterations 9<br> 9 SNES Function norm 1.690450876038e-11<br> Linear fieldsplit_e_ solve converged due to CONVERGED_ATOL iterations 4<br> 10 SNES Function norm 1.336383986009e-11<br> Linear fieldsplit_e_ solve converged due to CONVERGED_RTOL iterations 463<br> 11 SNES Function norm 1.873022410774e-12<br> Linear fieldsplit_e_ solve converged due to CONVERGED_RTOL iterations 113<br> 12 SNES Function norm 1.801834606518e-13<br> Linear fieldsplit_e_ solve converged due to CONVERGED_ATOL iterations 1<br> 13 SNES Function norm 1.004397317339e-13<br> Nonlinear solve converged due to CONVERGED_SNORM_RELATIVE iterations 13<br></div><div><br></div><div><br></div><div><br></div><div><br></div><div> 0 SNES Function norm 4.974994975313e-03<br>In PCFieldSplitSetFields_FieldSplit with -------------- link: 0x6e265010. Comms pc=0x56450340 ksp=0x6e2168d0 newcomm=0x6e265090<br>In PCFieldSplitSetFields_FieldSplit with -------------- link: 0x6e25bc40. Comms pc=0x56450340 ksp=0x6e22c1d0 newcomm=0x6e21e8f0<br> Linear fieldsplit_e_ solve converged due to CONVERGED_RTOL iterations 282<br> 1 SNES Function norm 1.836376279963e-05<br> Linear fieldsplit_e_ solve converged due to CONVERGED_RTOL iterations 380<br> 2 SNES Function norm 3.018499983019e-07<br> Linear fieldsplit_e_ solve converged due to CONVERGED_RTOL iterations 387<br> 3 SNES Function norm 1.826353175637e-08<br> Linear fieldsplit_e_ solve converged due to CONVERGED_RTOL iterations 391<br> 4 SNES Function norm 1.378600599548e-09<br> Linear fieldsplit_e_ solve converged due to CONVERGED_RTOL iterations 392<br> 5 SNES Function norm 1.077289085611e-10<br> Linear fieldsplit_e_ solve converged due to CONVERGED_RTOL iterations 394<br> 6 SNES Function norm 8.571891727748e-12<br> Linear fieldsplit_e_ solve converged due to CONVERGED_RTOL iterations 395<br> 7 SNES Function norm 6.897647643450e-13<br> Linear fieldsplit_e_ solve converged due to CONVERGED_RTOL iterations 395<br> 8 SNES Function norm 5.606434614114e-14<br> Nonlinear solve converged due to CONVERGED_SNORM_RELATIVE iterations 8<br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div><br></div><div> Matt</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div> Matt</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jan 21, 2021 at 10:46 AM Matthew Knepley <<a href="mailto:knepley@gmail.com" target="_blank">knepley@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr">On Thu, Jan 21, 2021 at 10:34 AM Mark Adams <<a href="mailto:mfadams@lbl.gov" target="_blank">mfadams@lbl.gov</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">It looks like PETSc is just too clever for me. I am trying to get a different MPI_Comm into each block, but PETSc is thwarting me:</div></blockquote><div><br></div><div>It looks like you are using SELF. Is that what you want? Do you want a bunch of comms with the same group, but independent somehow? I am confused.</div><div><br></div><div> Matt</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div> if (jac->use_openmp) {<br> ierr = KSPCreate(MPI_COMM_SELF,&ilink->ksp);CHKERRQ(ierr);<br>PetscPrintf(PETSC_COMM_SELF,"In PCFieldSplitSetFields_FieldSplit with -------------- link: %p. Comms %p %p\n",ilink,PetscObjectComm((PetscObject)pc),PetscObjectComm((PetscObject)ilink->ksp));<br> } else {<br> ierr = KSPCreate(PetscObjectComm((PetscObject)pc),&ilink->ksp);CHKERRQ(ierr);<br> }<br></div><div><br></div><div>produces:</div><div><br></div><div>In PCFieldSplitSetFields_FieldSplit with -------------- link: 0x7e9cb4f0. Comms 0x660c6ad0 0x660c6ad0<br>In PCFieldSplitSetFields_FieldSplit with -------------- link: 0x7e88f7d0. Comms 0x660c6ad0 0x660c6ad0<br></div><div><br></div><div>How can I work around this?</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jan 21, 2021 at 7:41 AM Mark Adams <<a href="mailto:mfadams@lbl.gov" target="_blank">mfadams@lbl.gov</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jan 20, 2021 at 6:21 PM Barry Smith <<a href="mailto:bsmith@petsc.dev" target="_blank">bsmith@petsc.dev</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><br><div><br><blockquote type="cite"><div>On Jan 20, 2021, at 3:09 PM, Mark Adams <<a href="mailto:mfadams@lbl.gov" target="_blank">mfadams@lbl.gov</a>> wrote:</div><br><div><div dir="ltr">So I put in a temporary hack to get the first Fieldsplit apply to NOT use OMP and it sort of works. <div><br></div><div>Preonly/lu is fine. GMRES calls vector creates/dups in every solve so that is a big problem. </div></div></div></blockquote><div><br></div> It should definitely not be creating vectors "in every" solve. But it does do lazy allocation of needed restarted vectors which may make it look like it is creating "every" vectors in every solve. You can use -ksp_gmres_preallocate to force it to create all the restart vectors up front at KSPSetUp(). </div></div></blockquote><div><br></div><div>Well, I run the first solve w/o OMP and I see Vec dups in cuSparse Vecs in the 2nd solve. </div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div><br></div><div> Why is creating vectors "at every solve" a problem? It is not thread safe I guess?</div></div></blockquote><div><br></div><div>It dies when it looks at the options database, in a Free in the get-options method to be exact (see stacks). </div><div><br></div><div>======= Backtrace: =========<br>/lib64/libc.so.6(cfree+0x4a0)[0x200021839be0]<br>/gpfs/alpine/csc314/scratch/adams/petsc/arch-summit-opt-gnu-cuda-omp/lib/libpetsc.so.3.014(PetscFreeAlign+0x4c)[0x2000002a368c]<br>/gpfs/alpine/csc314/scratch/adams/petsc/arch-summit-opt-gnu-cuda-omp/lib/libpetsc.so.3.014(PetscOptionsEnd_Private+0xf4)[0x2000002e53f0]<br>/gpfs/alpine/csc314/scratch/adams/petsc/arch-summit-opt-gnu-cuda-omp/lib/libpetsc.so.3.014(+0x7c6c28)[0x2000008b6c28]<br>/gpfs/alpine/csc314/scratch/adams/petsc/arch-summit-opt-gnu-cuda-omp/lib/libpetsc.so.3.014(VecCreate_SeqCUDA+0x11c)[0x20000052c510]<br>/gpfs/alpine/csc314/scratch/adams/petsc/arch-summit-opt-gnu-cuda-omp/lib/libpetsc.so.3.014(VecSetType+0x670)[0x200000549664]<br>/gpfs/alpine/csc314/scratch/adams/petsc/arch-summit-opt-gnu-cuda-omp/lib/libpetsc.so.3.014(VecCreateSeqCUDA+0x150)[0x20000052c0b0]<br>/gpfs/alpine/csc314/scratch/adams/petsc/arch-summit-opt-gnu-cuda-omp/lib/libpetsc.so.3.014(+0x43c198)[0x20000052c198]<br>/gpfs/alpine/csc314/scratch/adams/petsc/arch-summit-opt-gnu-cuda-omp/lib/libpetsc.so.3.014(VecDuplicate+0x44)[0x200000542168]<br>/gpfs/alpine/csc314/scratch/adams/petsc/arch-summit-opt-gnu-cuda-omp/lib/libpetsc.so.3.014(VecDuplicateVecs_Default+0x148)[0x200000543820]<br>/gpfs/alpine/csc314/scratch/adams/petsc/arch-summit-opt-gnu-cuda-omp/lib/libpetsc.so.3.014(VecDuplicateVecs+0x54)[0x2000005425f4]<br>/gpfs/alpine/csc314/scratch/adams/petsc/arch-summit-opt-gnu-cuda-omp/lib/libpetsc.so.3.014(KSPCreateVecs+0x4b4)[0x2000016f0aec]<br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div><br><blockquote type="cite"><div><div dir="ltr"><div>Richardson works except the convergence test gets confused, presumably because MPI reductions with PETSC_COMM_SELF is not threadsafe.</div></div></div></blockquote><div><br></div><blockquote type="cite"><div><div dir="ltr"><div><br></div><div>One fix for the norms might be to create each subdomain solver with a different communicator.</div></div></div></blockquote><div><br></div> Yes you could do that. It might actually be the correct thing to do also, if you have multiple threads call MPI reductions on the same communicator that would be a problem. Each KSP should get a new MPI_Comm. </div></div></blockquote><div><br></div><div>OK. I will only do this.</div><div><br></div></div></div>
</blockquote></div>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div>What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead.<br>-- Norbert Wiener</div><div><br></div><div><a href="http://www.cse.buffalo.edu/~knepley/" target="_blank">https://www.cse.buffalo.edu/~knepley/</a><br></div></div></div></div></div></div></div></div>
</blockquote></div>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div>What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead.<br>-- Norbert Wiener</div><div><br></div><div><a href="http://www.cse.buffalo.edu/~knepley/" target="_blank">https://www.cse.buffalo.edu/~knepley/</a><br></div></div></div></div></div></div></div></div>
</blockquote></div></div>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div>What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead.<br>-- Norbert Wiener</div><div><br></div><div><a href="http://www.cse.buffalo.edu/~knepley/" target="_blank">https://www.cse.buffalo.edu/~knepley/</a><br></div></div></div></div></div></div></div></div>
</blockquote></div></div>
</blockquote></div>
</blockquote></div>
</div></blockquote></div><br></div></blockquote></div></div>
</div></blockquote></div><br></div></blockquote></div></div>
</blockquote></div>
</blockquote></div></div>