Difference between revisions of "SAS"

Latest revision as of 13:48, 15 September 2023

Description

SAS is a commercial integrated system for statistical analysis, data mining, and graphics as well as many enterprise oriented additional features. SAS cost and the breadth of SAS features means that both a significant monetary investment and a substantial time investment are required to master it. SAS 9.3 Documentation is vast. For research purposes the SAS 9.3 User's Guide is a thorough reference for the functions and procedures you may need to do the statistical analysis using SAS.

Environment Modules

Run module spider sas to find out what environment modules are available for this application.

System Variables

HPC_SAS_DIR - installation directory

Additional Information

Commands

SAS has a number of options:

-nodms : This stops SAS from using its GUI capability and goes into a text only mode.
-filelocks fail : This causes SAS to stop and print out an error when multiple sas processes try to use the same file.
-nonews: Prevents SAS from printing a useless header to the output.
-memsize xxxxM - specifies the total amount of memory that is available to each SAS session, and places an enforced limit on the amount of virtual memory that SAS can dynamically allocate at any one time.
-realmemsize xxxxM - sets the recommended upper limit on working memory for procedures that can use both memory and utility disk space, such as PROC SUMMARY and PROC SORT, so that they can avoid virtual memory thrashing.
-work $TMPDIR - the directory where SAS should store its temporary files. Using $TMPDIR will allow your program to run much faster and prevent any network-related file access issues that SAS is prone to run into.
-sysin file : Designate a file for SAS to load as its input.

Batch Submission

To do a batch submission of a SAS script use the -sysin command line option and write all of your SAS commands in a file. In this way you can submit jobs to the batch queue system to run your jobs on the cluster.

-work directory

SAS is a mature product with a long history behind it. In a modern high-performance environment it means that additional actions need to be taken to mitigate potential issues stemming from SASs focus on filesystem I/O instead of using memory.

For users of PHI and FERPA: It is particularly important to set your working directory to be in your project's PHI/FERPA configured directory in /blue when working with SAS. Writing files to /home or $TMPDIR could expose restricted data to unauthorized users.

Interactive Use

See GUI_Programs to learn how to run the Graphical SAS interface for short debugging sessions.

SLURM Script Examples

Expand to view script example.

#!/bin/bash
#
#SBATCH --name=sas_job
#SBATCH --output=sas_%j.out
#SBATCH --mail-type=END,FAIL #Only email summary and failure reports
#SBATCH --mail-user=your_email_address  # Where to send mail	
#SBATCH --ntasks=1                      # Run a single task
#SBATCH --cpus-per-task=1               # Run on a single cpu
                                        #  --can change this for more cores
#SBATCH --mem=1gb                       # Memory limit
#SBATCH --time=01:00:00                 # Run for up to one hour
date;hostname;pwd

module load sas

sas -memsize 1024M -nodms -nonews -work $TMPDIR -filelocks none -sysin sas.inp

@@ Line 1: / Line 1: @@
 __NOTOC__
 __NOEDITSECTION__
-[[Category:Software]][[Category:Statistics]]
+[[Category:Software]][[Category:Statistics]][[Category:Data Science]]
 <!-- ########  Template Configuration ######## -->
 {|
@@ Line 7: / Line 7: @@
 |{{#vardefine:app|sas}}
 |{{#vardefine:url|http://www.sas.com/}}
-<!--Compiler and MPI settings - OPTIONAL -->
-|{{#vardefine:intel|}} <!-- E.g. "11.1" -->
-|{{#vardefine:mpi|}} <!-- E.g. "openmpi/1.3.4" -->
-<!--Choose sections to enable - OPTIONAL-->
-|{{#vardefine:mod|1}} <!--Present instructions for running the software with modules -->
 |{{#vardefine:exe|1}} <!--Present manual instructions for running the software -->
 |{{#vardefine:conf|}} <!--Enable config wiki page link - {{#vardefine:conf|1}} = ON/conf|}} = OFF-->
@@ Line 26: / Line 21: @@
 SAS is a commercial integrated system for statistical analysis, data mining, and graphics as well as many enterprise oriented additional features. SAS cost and the breadth of SAS features means that both a significant monetary investment and a substantial time investment are required to master it. [http://support.sas.com/documentation/onlinedoc/stat/index.html#stat93 SAS 9.3 Documentation] is vast. For research purposes the [http://support.sas.com/documentation/cdl/en/statug/63962/HTML/default/viewer.htm#titlepage.htm SAS 9.3 User's Guide] is a thorough reference for the functions and procedures you may need to do the statistical analysis using SAS.
 <!--Modules-->
-{{#if: {{#var: mod}}|==Execution Environment and Modules==
+==Environment Modules==
-{{App_Module|app={{#var:app}}|intel={{#var:intel}}|mpi={{#var:mpi}}}}|}}
+Run <code>module spider {{#var:app}}</code> to find out what environment modules are available for this application.
-{{#if: {{#var: exe}}|==How To Run==
+==System Variables==
+* HPC_{{uc:{{#var:app}}}}_DIR - installation directory
+<!--Additional-->
+{{#if: {{#var: exe}}|==Additional Information==
 ===Commands===
 SAS has a number of options:
@@ Line 46: / Line 43: @@
 SAS is a mature product with a long history behind it. In a modern high-performance environment it means that additional actions need to be taken to mitigate potential issues stemming from SASs focus on filesystem I/O instead of using memory.
+{{Note|'''For users of PHI and FERPA:''' It is particularly important to set your working directory to be in your project's PHI/FERPA configured directory in <code>/blue</code> when working with SAS. Writing files to <code>/home</code> or <code>$TMPDIR</code> could expose restricted data to unauthorized users.|warn}}
 ===Interactive Use===
-To connect to a test node, for example test01, where you can run the graphical interface to SAS use the following or a similar command on a linux or MacOS X system:
+See [[GUI_Programs]] to learn how to run the Graphical SAS interface for short debugging sessions.
- ssh USER@test01.ufhpc -o ForwardX11=yes -o ForwardX11Trusted=yes -o ProxyCommand='ssh USER@submit.hpc.ufl.edu exec nc test01 %p'
-or add the following to your ~/.ssh/config file:
- Host test01
-    User USER
-    KeepAlive yes
-    ProxyCommand ssh USER@submit.hpc.ufl.edu exec nc test01 %p
-    ForwardX11 yes
-    ForwardX11Trusted yes
-where USER is your username. After editing ~/.ssh/config you can just run the following command to connect:
- ssh test01
-Once connected run
- module load sas
- sas
 |}}
 {{#if: {{#var: conf}}|==Configuration==
 See the [[{{PAGENAME}}_Configuration]] page for {{#var: app}} configuration details.|}}
-==PBS Script Examples==
+==SLURM Script Examples==
-===Sample Job Script===
+<div class="mw-collapsible mw-collapsed" style="width:90%; padding: 5px; border: 1px solid gray;">
+''Expand to view script example.''
+<div class="mw-collapsible-content" style="padding: 5px;">
 <pre>
 #!/bin/bash
 #
-#PBS -N Research
+#SBATCH --name=sas_job
-#PBS -o market.out
+#SBATCH --output=sas_%j.out
-#PBS -e market.err
+#SBATCH --mail-type=END,FAIL #Only email summary and failure reports
-#PBS -m abe
+#SBATCH --mail-user=your_email_address  # Where to send mail
-#PBS -M <EMAIL ADDRESS>
+#SBATCH --ntasks=1                      # Run a single task
-#PBS -l nodes=1:ppn=1
+#SBATCH --cpus-per-task=1               # Run on a single cpu
-#PBS -l pmem=1gb
+                                        #  --can change this for more cores
-#PBS -l walltime=01:00:00
+#SBATCH --mem=1gb                       # Memory limit
+#SBATCH --time=01:00:00                 # Run for up to one hour
+date;hostname;pwd
 module load sas
-cd /scratch/hpc/USERNAME
 sas -memsize 1024M -nodms -nonews -work $TMPDIR -filelocks none -sysin sas.inp
 </pre>
+</div>
+</div>
 {{#if: {{#var: policy}}|==Usage Policy==
 WRITE USAGE POLICY HERE (perhaps templates for a couple of main licensing schemes can be used)|}}