| /petsc/src/sys/fileio/ |
| H A D | mpiuopen.c | 156 PetscErrorCode PetscPOpen(MPI_Comm comm, const char machine[], const char program[], const char mod… in PetscPOpen() argument 168 if (PetscPOpenMachine[0] || (machine && machine[0])) { in PetscPOpen() 173 PetscCall(PetscStrlcat(command, machine, sizeof(command))); in PetscPOpen() 221 PetscErrorCode PetscPOpenSetMachine(const char machine[]) in PetscPOpenSetMachine() argument 224 if (machine) { in PetscPOpenSetMachine() 225 PetscCall(PetscStrncpy(PetscPOpenMachine, machine, sizeof(PetscPOpenMachine))); in PetscPOpenSetMachine()
|
| H A D | smatlab.c | 27 PetscErrorCode PetscStartMatlab(MPI_Comm comm, const char machine[], const char script[], FILE **fp) in PetscStartMatlab() argument 39 PetscCall(PetscPOpen(comm, machine, "/usr/ucb/ps -ugxww | grep matlab | grep -v grep", "r", &fd)); in PetscStartMatlab() 52 PetscCall(PetscPOpen(comm, machine, command, "r", &fd)); in PetscStartMatlab() 57 PetscCall(PetscPOpen(comm, machine, "xterm -display ${DISPLAY} -e matlab -nosplash", "r", fp)); in PetscStartMatlab()
|
| /petsc/src/sys/classes/viewer/impls/socket/ |
| H A D | send.c | 313 PetscErrorCode PetscViewerSocketOpen(MPI_Comm comm, const char machine[], int port, PetscViewer *la… argument 318 PetscCall(PetscViewerSocketSetConnection(*lab, machine, port)); 414 PetscErrorCode PetscViewerSocketSetConnection(PetscViewer v, const char machine[], int port) argument 423 if (machine) PetscAssertPointer(machine, 2); 435 if (!machine) { 439 PetscCall(PetscStrncpy(mach, machine, sizeof(mach)));
|
| /petsc/doc/manual/ |
| H A D | matlab.md | 86 PetscViewerSocketOpen(MPI_Comm,char *machine,int port,PetscViewer *v); 90 machine if the MATLAB interactive session is running on the same machine 100 `PetscStartMatlab(MPI_Comm,char *machine,char *script,FILE **fp)`; 101 where `machine` and `script` may be `NULL`. It is also possible to 127 PetscMatlabEngineCreate(MPI_Comm comm,char *machine,PetscMatlabEngine *e); 130 where `machine` is the name of the machine hosting MATLAB (`NULL` 189 If you are running PETSc on a cluster (or machine) that does not have a license for MATLAB, you mig… 190 `head node` of the cluster or some other machine accessible to the cluster using the `-matlab_engin…
|
| H A D | performance.md | 7 CPU sockets per node. We focus on machine-related performance 67 one can obtain on the given machine (not necessarily a shared memory 89 On this machine, one should expect a speed-up of typical memory 140 recommended placement of a 8-way parallel run on a four-socket machine 145 machine, in which each CPU consists of six cores and supports 220 practical peak of about 50 GB/sec available on the machine. If, however, 326 processor machine in the preceding example may be relatively insensitive 356 processor topology of your machine. We cannot fully address the second 683 including the cache behavior, other users on the machine, etc. Below we 690 the machine’s memory. One way to estimate the amount of memory used [all …]
|
| H A D | regressor.md | 6 machine learning tasks at a higher level of abstraction than a purely algebraic "solvers" view. 12 model, following standard parlance in the machine-learning community.
|
| H A D | dmbase.md | 6 (in both human and machine time) of connecting the solvers to the mathematical models and discretiz…
|
| H A D | tests.md | 47 Depending on your machine’s configuration running the full test suite
|
| /petsc/doc/miscellaneous/ |
| H A D | saws.md | 19 different machine, pass the name of that machine to the browser.
|
| H A D | codemanagement.md | 23 on a different machine that uses a different compiler. 58 on your machine. Otherwise, you can run each process in a separate 91 - Develop your code on the simplest machine to which you have access. 97 PETSc code is completely portable, switching to a parallel machine 99 logging into another machine -- there are no code or makefile
|
| /petsc/lib/petsc/bin/maint/ |
| H A D | toclapack.sh | 643 /* SLAMCH determines single precision machine parameters. */ 1657 /* eps = relative machine precision */ 1659 /* base = base of the machine */ 1775 /* DLAMC1 determines the machine parameters given by BETA, T, RND, and */ 1782 /* The base of the machine. */ 1790 /* be a reliable guide to the way in which the machine performs */ 2009 /* DLAMC2 determines the machine parameters specified in its argument */ 2016 /* The base of the machine. */ 2024 /* be a reliable guide to the way in which the machine performs */ 2038 /* The smallest normalized number for the machine, given by */ [all …]
|
| /petsc/doc/manualpages/MANSECHeaders/ |
| H A D | DMPatch | 3 …aptive refinement calculated in serial using patches that fill the local machine. It is currently …
|
| H A D | PetscRegressor | 4 statistical (or machine) learning regression (prediction of continuous numerical values, including …
|
| /petsc/doc/community/ |
| H A D | roadmap.md | 12 …derivative information and making it available to the user and machine learning software such as P…
|
| /petsc/src/ts/tutorials/ |
| H A D | extchem.example.1 | 5 # If your machine is not connected to the internet you must obtain the two files below and store
|
| H A D | h2_10sp.inp | 4 # If your machine is not connected to the internet you must obtain the two files below and store
|
| /petsc/doc/developers/contributing/ |
| H A D | index.md | 36 - [Install Git](https://git-scm.com/downloads) if it is not already installed on your machine, then… 52 - If you already have a clone on your machine of the PETSc repository you would like to reuse
|
| H A D | pipelines.md | 30 …line consists of "Stages" each with multiple "Jobs". Every job is one configuration on one machine. 82 … you will see an error from `make checkbadSource`. Always run `make checkbadSource` on your machine
|
| H A D | developingmr.md | 120 - {any}`Run the full test suite <sec_runningtests>` on your machine. 126 - Run the source checkers on your machine.
|
| /petsc/doc/install/ |
| H A D | install_tutorial.md | 16 your machine): 102 With all dependencies installed, navigate to a suitable directory on your machine and pull 103 the latest version of the PETSc library to your machine with git. The following commands 166 - Setting various known machine quantities for PETSc to use such as known integral sizes, 184 directory of your machine), but do accept environment variables as input.
|
| H A D | install.md | 226 machine). Once the tarfile is downloaded, the path to this file can be specified to 454 Cannot run executables created with C. If this machine uses a batch system 608 Produces the directories (on an Apple macOS machine) `$PETSC_DIR/arch-darwin-c-debug` and 664 An NVIDIA GPU is **required** to use [CUDA]-accelerated code. Check that your machine
|
| /petsc/src/sys/objects/ |
| H A D | init.c | 663 char machine[128]; in PetscOptionsCheckInitial_Private() local 664 PetscCall(PetscOptionsGetString(NULL, NULL, "-popen_machine", machine, sizeof(machine), &flg1)); in PetscOptionsCheckInitial_Private() 665 if (flg1) PetscCall(PetscPOpenSetMachine(machine)); in PetscOptionsCheckInitial_Private()
|
| /petsc/doc/changes/ |
| H A D | 215.md | 16 - Added support for Cray SX-6 vector machine
|
| H A D | 231.md | 76 accurate/low-overhead on a machine - then use: --with-timer=mpi]
|
| /petsc/src/sys/classes/viewer/impls/mathematica/ |
| H A D | mathematica.c | 338 PetscErrorCode PetscViewerMathematicaOpen(MPI_Comm comm, int port, const char machine[], const char… in PetscViewerMathematicaOpen() argument 345 PetscCall(PetscViewerMathematicaSetLinkHost(*v, machine)); in PetscViewerMathematicaOpen()
|