[evla-sw-discuss] Extensions to script for IDCAF info

Bryan Butler bbutler at nrao.edu
Thu Aug 24 17:25:59 EDT 2006


good point.  i'm no less nervous leaving it in the hands of the operators, however.

	-bryan


On 8/24/06 13:22, Barry Clark wrote:
>> From bbutler at nrao.edu  Thu Aug 24 13:13:19 2006
>> 
>> On 8/17/06 16:22, Barry Clark wrote:
>> > Proposal code.
>> > I suggest we get his by convention.  The Job ID is already present
>> > and used.  Operators have typically been entering the file name
>> > here, which contains the proposal code.  I suggest we ask them to
>> > put the proposal code first - that is, for example, entering the
>> > jobid as 'AH913.679<and maybe other stuff>' instead of the 
>> > '679H913.OBS' they have been using.
>> 
>> i believe that this should be explicitly set in the script rather than relying 
>> on something an operator types in.
>> 
>> from OBSERVE files we can always get it from the first line, and obs2script 
>> already parses it out.  it could easily be passed on from there.
>> 
>> 
> 
> Actually, the main reason I suggested having the operator do it is that 
> since we now have the proposal code dictating the proprietary release date,
> it makes me a little nervous leaving it in the hands of the observer.
> _______________________________________________
> evla-sw-discuss mailing list
> evla-sw-discuss at listmgr.cv.nrao.edu
> http://listmgr.cv.nrao.edu/mailman/listinfo/evla-sw-discuss



More information about the evla-sw-discuss mailing list