<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Fri, Jul 6, 2018 at 7:30 PM Smith, Barry F. <<a href="mailto:bsmith@mcs.anl.gov">bsmith@mcs.anl.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"><br>
Mark,<br>
<br>
We should get your arch-titan-opt64idx-pgi.py into the master branch of PETSc in config/examples if there is not something equivalent there already.<br></blockquote><div><br></div><div>I do not recall if I did anything special for Titan, aprun and compilers is about all I see. maybe '<span style="background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">--known-mpi-shared-libraries=1</span>' was added, otherwise it looks like a cloned config file. I did comment out cmake after learning that I could load the module. Maybe make a note in this file as I did here</div><div><br></div><div><div>#!/usr/bin/env python</div><div>if __name__ == '__main__':</div><div> import sys</div><div> import os</div><div> sys.path.insert(0, os.path.abspath('config'))</div><div> import configure</div><div> configure_options = [</div><div> '--COPTFLAGS=-fast',</div><div> '--CXXOPTFLAGS=-fast',</div><div> '--FOPTFLAGS=-fast',</div><div> '--with-ssl=0',</div><div> '--with-batch=0',</div><div> '--with-mpiexec=aprun',</div><div> '--download-fblaslapack',</div><div># '--download-superlu',</div><div> '--with-openmp',</div><div> '--prefix=/ccs/proj/env003/petscv3.9-titan-opt64-pgi',</div><div> '--download-hypre',</div><div> '--download-metis',</div><div> '--with-hwloc=0',</div><div> '--download-parmetis',</div><div># '--download-cmake', // use: module load cmake</div><div> '--with-cc=cc',</div><div># '--with-clib-autodetect=0',</div><div> '--with-cxx=CC',</div><div># '--with-cxxlib-autodetect=0',</div><div> '--with-fc=ftn',</div><div># '--with-fortranlib-autodetect=0',</div><div> '--with-shared-libraries=0',</div><div> '--known-mpi-shared-libraries=1',</div><div> '--with-x=0',</div><div> '--with-64-bit-indices=1',</div><div> '--with-debugging=0',</div><div> 'PETSC_ARCH=arch-titan-opt64-pgi',</div><div> ]</div><div> configure.petsc_configure(configure_options)</div><div>~ </div></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">
<br>
Also is the .py file different for summit? I would expect so, we should get that into config/examples also.<br></blockquote><div><br></div><div>And and same with summit, this still has cmake, which I assume could be removed if you load the cmake module:</div><div><br></div><div><div>#!/usr/bin/env python</div><div>if __name__ == '__main__':</div><div> import sys</div><div> import os</div><div> sys.path.insert(0, os.path.abspath('config'))</div><div> import configure</div><div> configure_options = [</div><div> '--COPTFLAGS=-g',</div><div> '--CXXOPTFLAGS=-g',</div><div> '--FOPTFLAGS=-g',</div><div> '--with-ssl=0',</div><div> '--with-batch=0',</div><div># '--with-mpiexec=aprun',</div><div># '--download-superlu',</div><div># '--with-threadcomm',</div><div># '--with-pthreadclasses',</div><div># '--with-openmp',</div><div> '--prefix=/ccs/proj/env003/petscv3.7-dbg64-summit-pgi',</div><div># '--download-hypre',</div><div> '--download-metis',</div><div> '--with-hwloc=0',</div><div> '--download-parmetis',</div><div> '--download-cmake',</div><div> '--with-cc=mpicc',</div><div># '--with-fc=0',</div><div># '--with-clib-autodetect=0',</div><div># '--with-cxx=mpiCC',</div><div># '--with-cxxlib-autodetect=0',</div><div> '--with-fc=mpif90',</div><div># '--with-fortranlib-autodetect=0',</div><div> '--with-shared-libraries=0',</div><div> '--known-mpi-shared-libraries=1',</div><div> '--with-x=0',</div><div> '--with-64-bit-indices',</div><div> '--with-debugging=1',</div><div> 'PETSC_ARCH=arch-summit-dbg64-pgi',</div><div> ]</div><div> configure.petsc_configure(configure_options)</div><div>~ </div></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">
<br>
Thanks<br>
<br>
Barry<br>
<br>
<br>
> On Jul 6, 2018, at 6:19 PM, Mark Adams <<a href="mailto:mfadams@lbl.gov" target="_blank">mfadams@lbl.gov</a>> wrote:<br>
> <br>
> Todd, I've been building PETSc on Titan and SUMMIT for users. cray-petsc has been hosed for a while. I put my most recent configure file in:<br>
> <br>
> /ccs/proj/env003/arch-titan-opt64idx-pgi.py<br>
> <br>
> This is a public space. My builds are here also. You run with, for instance,<br>
> <br>
> make PETSC_DIR=/ccs/proj/env003/petscv3.9-opt64-pgi PETSC_ARCH=""<br>
> <br>
> There are several other builds in there that you can use. I now see that I don't have the machine name in the directory name, yuck. But this and a v3.7 version are recent and work (on Titan).<br>
> <br>
> Mark<br>
> <br>
> <br>
> On Fri, Jul 6, 2018 at 6:47 PM Smith, Barry F. <<a href="mailto:bsmith@mcs.anl.gov" target="_blank">bsmith@mcs.anl.gov</a>> wrote:<br>
> <br>
> I know Mark Adams has tried recently; without limited success.<br>
> <br>
> As always the big problem is facilities removing accounts, such as Satish's, so testing gets difficult.<br>
> <br>
> But yes, we want to support Titan so have users send configure.log/make.log to <a href="mailto:petsc-maint@mcs.anl.gov" target="_blank">petsc-maint@mcs.anl.gov</a><br>
> <br>
> Barry<br>
> <br>
> <br>
> > On Jul 6, 2018, at 12:45 PM, Munson, Todd <<a href="mailto:tmunson@mcs.anl.gov" target="_blank">tmunson@mcs.anl.gov</a>> wrote:<br>
> > <br>
> > <br>
> > Barry,<br>
> > <br>
> > Have you tested petsc compilation on titan? Is there a config example<br>
> > for that machine?<br>
> > <br>
> > Apparently titan died and when they brought it back up, the petsc install<br>
> > was fracked, so some ORNL users are trying to compile petsc locally<br>
> > rather than wait for the facilities people.<br>
> > <br>
> > Thanks, Todd<br>
> > <br>
> <br>
<br>
</blockquote></div></div>