[evlatests] Project codes for test observations

[Bryan Butler]

because projects won't be denoted by XYnnnn any more.  they'll be 
denoted by VLAYYT-nnn where YY is last two digits of year, T is 
trimester, and nnn is the number assigned in order of reception by the 
PST.  something that would fit with that scheme would either need a 
replacement for YYT or nnn.  either that or we allow multiple formats 
for the project code, which i'm against.

	-bryan


Scheduling Officer wrote, On 2/18/10 15:34:
> 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
>>