[Halld-offline] priority groups for Hall D share of the batch farm
marki at jlab.org
Thu Feb 9 12:26:41 EST 2017
I've asked SciComp to return the priority settings back to where they
were before yesterday.
On 02/08/2017 02:44 PM, Mark Ito wrote:
> This is temporary, maybe for a few days.
> The high priority tasks right now are polarization measurements, from
> the rho (gzproj5) and from the TPOL (nsparks). Everything else takes a
> back seat.
> After these two projects are done, things go back to the way they were
> before, i. e., highpriority disappears.
> On 02/08/2017 02:34 PM, Sean Dobbs wrote:
>> Hi Alex,
>> I can understand having monitoring at a higher priority, but probably
>> the production jobs shouldn't be higher priority than calibration
>> jobs, since the monitoring/calibration of incoming data is the most
>> time-sensitive part of the chain.
>> On Wed, Feb 8, 2017 at 1:30 PM Alexander Austregesilo
>> <aaustreg at jlab.org <mailto:aaustreg at jlab.org>> wrote:
>> Hi Mark,
>> The gxproj1 account is doing the first offline monitoring run. I
>> not give it a lower priority then gxproj5, in case we run a full
>> production on 5 and take data at the same time. Maybe put them in the
>> same group?
>> On 02/08/2017 02:19 PM, Mark Ito wrote:
>> > We would like three priority groups with priority weighting as
>> > 1. highpriority 50%
>> > 2. production 33%
>> > 3. users 17%
>> > Membership:
>> > 1. gxproj5, nsparks
>> > 2. gxproj1, gxproj2, gxproj3, gxproj4, gxproj6
>> > 3. all other halld users
>> Halld-offline mailing list
>> Halld-offline at jlab.org <mailto:Halld-offline at jlab.org>
> marki at jlab.org, (757)269-5295
> Halld-offline mailing list
> Halld-offline at jlab.org
marki at jlab.org, (757)269-5295
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Halld-offline