Jobs submitted to the general farm of batch systems at SLAC will be scheduled to run according to a cross-queue user-based fairshare priority system. There is more information here www.slac.stanford.edu/comp/unix/package/lsf/currdoc/lsf_admin/index.htm about this kind of scheduling. The priority of a user's job is dynamically determined based on various factors such as the number of jobs the user has across all the queues in the fairshare, their resource consumption, the number of shares belonging to the user's fairshare group, etc. The general farm fairshare queue structure can be viewed with the command /usr/local/bin/bqueues -l short. This is an example of what the relevant part of the output from that command looks like at the time of this writing:
renata@rhel6-64g $ bqueues -l short
-- This is the default queue.
SCHEDULING POLICIES: FAIRSHARE BACKFILL
FAIRSHARE_QUEUES: short medium long atlasq atl-analq
USER_SHARES: [atlasgrp, 37875] [babarAll, 7859] [cdmsALL, 2000] [exoprodgrp, 1500] [exousergrp, 550] [geantgrp, 3874] [glastdata, 854] [glastgrp, 366] [glastusers, 25320] [hpsprodgrp, 1000] [lcd, 600] [lcdprodgrp, 1100] [luxlz, 3500] [rpgrp, 500] [theorygrp, 4257] [AllUsers, 16086]
HOSTS: genfells+1 hequfarm+1 dolefarm+1 kisofarm+1 bulletfarm/
Jobs submitted by a user that is not a member of any usergoup will get the priority of the AllUsers group. Jobs submitted by a user that is a member of a fairshare group may also get the priority of AllUsers if the priority of AllUsers happens to be higher than that of his own group at the time his job is submitted.