skipped-directives.txt

PBS_ARRAY_INDEX=1

# Lines preceded by "#PBS" are directives for Torque/PBS

#SBATCH'/'#SBATCH'/gI' matrix${countf}

## Lines "#SBATCH" configure the job resources

SBATCH ${sbatchQueue}

copy all #PBS headers

## slurm option lines start with #SBATCH

SBATCH

 Torque (PBS) directives "#PBS" start here:  

 Lines that begin with #SBATCH specify commands to be used by SLURM for scheduling. They are not comments.

FLUXIONFindingExtraWINotice="Buscando interfaces inalámbricas extrañas..."

PBS	…

# Submit job to "Open" allocation if next line begins #PBS

SBATCH flags for building the $script_name_build script. Press 'q' when finished."

PBS .*nodes=.*:ppn=" $tmpscript > /dev/null ; then

#SBATCH SLURM_UMASK=022 

 submission file when preceeded by '#SBATCH'. These lines will be

BSUB –R “span[ptile=40]” ### ask for 40 cores per node

SBATCH ${sbatchMailTo}

###PBS_ARRAY_INDEX=5

 Des paramètres sbatch peuvent être spécifiés dans ce fichier sous la forme : #SBATCH <param>

#PBS depend=afterok:<jobid>:<jobid>

SBATCH _c          10

SBATCH gpu

PBS

 Remove SLURM #SBATCH tags

## Slurm option lines start with #SBATCH 

You can control the resources and scheduling with '#SBATCH' settings

PBS  output=para.out

 Remove LSF #BSUB tags

PBS "$MEMREQUEST                                     >>$sgeFile

 Multiple hashes, like `##SBATCH`, are comments and ignored.

## Any lines started with #PBS are not comments,

 Script directive: #PBS                                                                       #

 The #PBS must be used to specify Torque options

#                   b) Lines that begin with #SBATCH will be ignored by the interpreter and read by the job scheduler 

 with #SBATCH are actually commands to the SLURM scheduler.

 If we have #PBS commands or #SGE commands

 The lines starting with #PBS are queuing system flags:

SBATCH hetjob

PBS " $MEMREQUEST                                      >>$sgeFile

BSUB 

 **** Put all #SBATCH directives above this line! ****

 NOTE: Lines starting with "#SBATCH" are valid SLURM commands or statements,

SBATCH ${sbatchTime}

SBATCH $flag" >> run_image.sh

 Reference the PBS Pro User Guide for #PBS directive options.

#PBS_NUM_PPN=20

FLUXDATA_DEVNAME=""

OAR_JOB_ID=project_name #may not work

SBATCH" ]]; then

 use ##SBATCH 

SBATCH ${sbatchOutputFilename}

 中间不可以有非 #SBATCH 开头的行

SBATCH __mail_type END

 like "##PBS" are considered "commented out" by the batch system

 Lines starting with #SBATCH specify options for the scheduler.

 #PBS_ARRAY_INDEX=1

SBATCH $flag" >> run_image_stats.sh

            A line beginning with #PBS is a PBS directive.

PBS or #SGE. condor_qsub will parse the batch file

  Code is allowed after this point.  No more #SBATCH lines will be recognized.

 or example setting.  Lines starting with "##PBS" are ignored; to enable

        A line beginning with #PBS is a PBS directive.

 file that collects all '^#PBS ' lines inside the given job

SBATCH flags for building the morphometric stats workflow script. Press 'q' when finished."

 Note that "#SBATCH" is not a comment, but "# SBATCH" is (note the space after "#")

PBS .*mpiprocs" $tmpscript > /dev/null ; then

BSUB ${lsf}

PBS   [whatever other options]

 You can control the resources and scheduling with '#SBATCH' settings

PBS "$MEMREQUEST                        >>$sgeFile

SBATCH 

PBS .*nodes" $tmpscript > /dev/null ; then

#PBS_ARRAY_INDEX=10

FLUXDATA_DEVNAME=$(get_dev_from_label ${LUKS_PREFIX_LABEL}${FLUXDATA_LABEL})

SBATCH __job_name  gpt

SBATCH	...

PBS .*select[^,]*mem' $tmpscript > /dev/null ; then

“#SBATCH” directives that convey submission options:

but, if we do that, we get rid of all #PBS options that user might be setting inside main..

PBS .*select[^,]*model' $tmpscript > /dev/null ; then

COBALT 'getenv(MAIL_ARG)'

BSUB –R "span[ptile=4]"

BSUB "span[ptile=16]"

PBS_o_WORKDIR;

 The following are embedded QSUB options. The syntax is #PBS (the # does

FLUXIONFindingExtraWINotice="Trova interfacce extra wireless..."

PBS 

 Other commands must follow all #SBATCH directives...

 Other commands must follow all #SBATCH directives.

"#SBATCH" directives that convey submission options:

PBS ?N test_matlab

 cannot have any shell script command before #SBATCH clause, not even vars declaration

 Lines that do not start with # or #SBATCH are commands that will run.

PBS_ARRAY_INDEX=20

 Torque directives (#PBS) must always be at the start of a job script!

       A line beginning with #PBS is a PBS directive.

 Script directive: #SBATCH                                                                                                    #

SBATCH –gres=gpu:rtx3080:1

SBATCH: For more info see https://docs.alliancecan.ca/wiki/Mist

 Put #PBS in front of one of the following queues that you have access to

SBATCH" $0

OAR_JOB_ID=12236582

PBS	–N blast	

OAR_JOB_ID=12239573

 a comment.  If you need to comment out an #SBATCH line 

 sbatch will read any lines that start with "#SBATCH" and will

# Submit job to "Open" allocation if the next line begins with #PBS rather than ##PBS

PBS "$MEMREQUEST                         >>$sgeFile

 comment out a directive you must add another # to the start: ##PBS.

SBATCH: Job submission will be attempted despite warnings.

 (it has #PBSs from above)

PBS_NUM_PPN=4

SBATCH ${sbatchSSD}

       while those starting with "#" and "##SBATCH" are comments.  Uncomment

BSUB $HOME/err

# Lines starting with #SBATCH are read by Slurm. Lines starting with ## are comments.

PBS .*select" $tmpscript > /dev/null ; then

PBS" $main >> _main

PBS .*ncpus" $tmpscript > /dev/null ; then

SBATCH __mail_user zzangmane@snu.ac.kr

PBS $rargs

 tmp file for job script contents (used for '#PBS' parsing)

SBATCH gputest

PBS	–j	oe	

PBS_JOBID=1365082.nid11293

PBS"

 Options to sbatch start with '#SBATCH'. To disable an option, change

 the interpreter.  Lines beginning with #SBATCH are directives

PBS'

FLUXNAMEFILE[@]} > 0 ]]

 Lines beginning with #SBATCH are special commands to configure the job.

SBATCH $flag" >> run_image_sub.sh

FLUXBOX_VERSION=\"\([^\"]\+\)\"#FLUXBOX_VERSION=\"${FLUXBOX_VERSION}\"#" \

SBATCH flags for building the preprocessing workflow script. You should enter the array flag here. Press 'q' when finished."

FLUX_CAPACITOR_VERSION=1.6.1

#SBATCH'/'#SBATCH'/gI' matrix${count}

 Lines that begin with #SBATCH specify commands to be used by SLURM for scheduling

*#PBS}

SBATCH packjob

参数在脚本中可以加上前缀“#SBATCH”指定，和在命令参数中指定功能一致，如果脚本中的参数和命令指定的参数冲突，则命令中指定的参数优先级更高。在此处指定后可以直接sbatch ./run.sh 提交。

PBS " $MEMREQUEST                                 >>$sgeFile

#PBS_O_WORKDIR = "${PBS_O_WORKDIR}/artificial_intelligence/repos/fdir"

 2. #SBATCH directives

SBATCH ${sbatchCpusPerTask}

 NOTE: lines that begin with "#PBS" are not interpreted by the shell but ARE

BSUB cwd $wd

 adding a second # (e.g. ##SBATCH lines will not be processed

SBATCH XXXextra5XXX

###PBS JOB OPTIONS

 Note anything after #SBATCH is a command

SBATCH XXXqueueXXX

SBATCH __time      96:00:00

PBS '

# ALL SBATCH COMMANDS WILL START WITH #SBATCH ##

PBS M kartshy@gmail.com

PBS @qopts@

 A Slurm batch file is, in short, a Bash script with some special comments that start with "#SBATCH".

PBS Job

 submit an PBS script based on the #PBS resources specified below.

#PBS_O_WORKDIR=$(pwd)

SBATCH WARNING:

FLUXBOX {{{

 sbatch scripts must specify `#SBATCH` directives prior to any regular command.

SBATCH ${sbatchNTasks}

 The lines that start with #SBATCH are read by slurm to set up the job

PBS_NUM_PPN=$NSLOTS

SBATCH ${parsable}

 Script directive: #BSUB                                                                                      #

SBATCH" $main >> _jobheader || true

SBATCH ${sbatchMailAlerts}

PBS $resources

 like "##PBS" are considered "commented out" by the batch system 

 IMPORTANT: The lines beginning #PBS various queuing parameters, they are not simple comments

BSUB \$1 \$2"

 Need to use variables OUTSIDE of this script, #SBATCH doesn't support variables: https://help.rc.ufl.edu/doc/Using_Variables_in_SLURM_Jobs

 IMPORTANT: The lines beginning #PBS set various queuing parameters, they are not simple comments

SBATCH flags for building the script. Press 'q' when finished."

 The #PBS must be used to specify PBS Pro options

COBALT_JOBSIZE=1

       "##SBATCH" line means to remove one # and start with #SBATCH to be a

PBS_QUE = '1nd'#PBS_QUE = '${queue}'#g" > Template/Source/run_config_tmp.inc

PBS .*ngpus" $tmpscript > /dev/null ; then

SBATCH ${additionalSlurmOptions}" >> "${submissionScript}"

 General conditions are set by what follows #SBATCH lines  

PBS" $main >> _jobheader || true

BSUB –J MPIJob ### set the job Name

 Typcially, the # represents a comment.However, #SBATCH is

 The lines starting with #BSUB are interpreted by the Resource Manager (RM) as lines that contain options for the RM

#PBS configure

SBATCH $flag" >> $script_name_build

PBS directives' 1>&2

SBATCH ${sbatchScratchStorage}

 Use #SBATCH <option>=<value> to configure. Do not uncomment lines with #SBATCH

BSUB XXXextra5XXX

PBS_O_WORKDIR

PBS does not appear to have an easily accesible env variable for this

PBS  ngpus=1

PBS_ARRAYID=22

FLUX_INGRID_PATH=${FLUX_ROOT_PATH}/nd34

 Check each line in the file to see if they start with #PBS or #SGE

 Option                        | Values                             | #SBATCH only | Export only |

PBS_JOBID and JOBID is empty/not set

## Slurm option lines start with #SBATCH

 If a script is specified, it will only help gives further options to PBS with the #PBS directives.

## #SBATCH directives need to be in the first part of the jobscript

 User should set shell variables and #PBS settings below:

SBATCH $job_option\n"

## slurm job options: line must begin with '#SBATCH'

SBATCH XXXextra4XXX

SBATCH: 2 warnings were found.

PBSnodeFile=`cat $PBS_NODEFILE`

 NOTE: lines that begin with "#PBS" are not interpreted by the shell but ARE 

 The commands for slurm start with #SBATCH

SBATCH'

I don't want not finding any #PBS to fail

 Any other commands must follow the #SBATCH directives

SBATCH XXXextra3XXX

### (Remember for Slurm #SBATCH, one # is active, two or

BSUB cwd /gpfs/projects/cek26

 Parameters for slurm (don't remove the # in front of #SBATCH!)

# Submit job to "Open" allocation if next line begins #PBS (rather than ##PBS)

SBATCH [whatever other options]

   Submit as an Sbatch job (edit Sbatch arguments in the #SBATCH directives

#the following lines starting with `#SBATCH` are directives to the scheduling system, slurm

SBATCH" $slurmScript >> $job || true >> $job

## sbatch configuration parameters must start with #SBATCH and must precede any other commands.

PBS ...

# Do not put any commands or blank lines before the #SBATCH lines

# Please note that anything after the characters "#SBATCH" on a line

 with "#SBATCH " followed by flags that would otherwise be passed on

PBS " $MEMREQUEST                   >>$sgeFile

   Submit as a Cobalt job (edit Cobalt arguments in the #COBALT directives

## Note: No commands may be executed until after the #PBS lines

COBALT {{ sched_flags }}

 at the beginning of the script, lines beginning with "#SBATCH" are read by

PBS –q workq

SBATCH __gpus      1

SBATCH __mem       20G

PBS ");

SBATCH ${sbatchMemory}

BSUB"

PBS \$1 \$2"

 Any other commands must follow all #SBATCH directives...

SBATCH ${sbatchJobName}