[evlatests] Project codes for test observations

[Scheduling Officer]

Why so, Bryan?  - Joan

***********************************************************************
EVLA/VLBA Scheduling Officers                         schedsoc at nrao.edu
NRAO, Socorro, New Mexico, USA       http://www.aoc.nrao.edu/~schedsoc/
***********************************************************************

On Thu, 18 Feb 2010, Bryan Butler wrote:

>
> this will not work when we wean ourselves from the legacy codes.
>
> 	-bryan
>
>
> Barry Clark wrote, On 2/16/10 14:18:
>> Joan suggests a format of T<subj>nnnn for project codes, where <subj>
>> is one of a list of subjects, and the nnnn she will assign, at first
>> on a basis of one number to a customer.  So if you want to make a
>> scheduling block with OPT, send along a one sentence description of
>> what you want to do to schedsoc, and we will reply with a code and
>> number.  (I suspect everybody will, at first, want a TOSRnnnn code,
>> OSR standing for "osro tests".)  That project code will do for all
>> further Scheduling Blocks you create that fit under your one sentence
>> description.
>> _______________________________________________
>> evlatests mailing list
>> evlatests at listmgr.cv.nrao.edu
>> http://listmgr.cv.nrao.edu/mailman/listinfo/evlatests
> _______________________________________________
> evlatests mailing list
> evlatests at listmgr.cv.nrao.edu
> http://listmgr.cv.nrao.edu/mailman/listinfo/evlatests
>