This page includes a summary of differences to keep in mind when migrating jobs from other clusters to Pitzer.
Guidance for Oakley Users
Guidance for Owens Users
|pitzer (PER NODE)
|owens (PER NODE)
|Regular compute node
40 cores and 192GB of RAM
48 cores and 192GB of RAM
|28 cores and 125GB of RAM
|Huge memory node
48 cores and 768GB of RAM
(12 nodes in this class)
80 cores and 3.0 TB of RAM
(4 nodes in this class)
48 cores and 1.5TB of RAM
(16 nodes in this class)
Pitzer accesses the same OSC mass storage environment as our other clusters. Therefore, users have the same home directory, project space, and scratch space as on the Owens cluster.
Pitzer uses the same module system as Owens.
module load <package> to add a software package to your environment. Use
module list to see what modules are currently loaded and
module avail to see the modules that are available to load. To search for modules that may not be visible due to dependencies or conflicts, use
module spider .
You can keep up to on the software packages that have been made available on Pitzer by viewing the Software by System page and selecting the Pitzer system.
Like Owens, Pitzer supports three compilers: Intel, PGI, and gnu. The default is Intel. To switch to a different compiler, use
module swap intel gnu or
module swap intel pgi .
Pitzer also use the MVAPICH2 implementation of the Message Passing Interface (MPI), optimized for the high-speed Infiniband interconnect and support the Advanced Vector Extensions (AVX2) instruction set.
See the Pitzer Programming Environment page for details.
Below is a comparison of job limits between Pitzer and Owens:
|Up to 256 concurrently running jobs and/or up to 3240 processors/cores in use
|Up to 256 concurrently running jobs and/or up to 3080 processors/cores in use
|Up to 384 concurrently running jobs and/or up to 3240 processors/cores in use
|Up to 384 concurrently running jobs and/or up to 4620 processors/cores in use