[evla-sw-discuss] C119420

[Bryan Butler]

hi pat,

this is a switch that tells obs2script to ignore the time in the comment card of 
the .OBS file, and assume that the script should start immediately when 
submitted, and use barry's java code (array.mjd()) to calculate the conversion 
between LST and UTC.

it has not been advertised very widely because it has not been tested very 
widely (it's been in place for two weeks).

i have not figured out the fundamental problem as to why obs2script failed on a 
file with a start time just before IAT midnight.

we had some email exchange on C119420 when it happened, but i didn't think it 
worth broader distribution.

	-bryan


On 11/20/06 08:13, Pat Van Buskirk wrote:
> Tom's report of an obs2script problem is documented below. We later 
> found out we needed to run with a -b option. Can someone please tell us 
> under what circumstances we need to use this option and if there are 
> other options we should know about.
> 
> Thanks for the help,
> Pat
> 
> 
> Phillip D. Hicks wrote:
>>    Work Order		:  C119420
>> 
>>  * WO Status		:  OPD
>>    Asset Number		:  
>>    Asset Short Desc	:  
>>    Asset Location		:  VLA-CB-ROOM C224
>>    Originator		:  Briscoe, Tom
>>  * Asset Status		:  
>>    Safety			:  N
>>    Plan Priority		:  3
>>    Origination Date	:  11/17/2006
>>    Due Date			:  11/17/2006
>>    Fault Code		:  FAILURE
>> 
>>    Work Requested		:  Failure: I attempted to load .obs
>> file in /users/evlaops/fetch/fetched/775b122.obs.  The file converted
>> and loaded without complaint but when it started it simply skipped
>> immediately through all the sources until it terminated.  Ken Sowinski
>> said that obs2script gave it the wrong date.  The file was originally
>> due to start just before IAT midnight.  I tried running obs2script by
>> hand, but the resulting script had the same sort of problem.  Ken
>> advised me to try running obs2script with an undocumented -b switch.
>> That created a script which seems to run properly.  The file I created
>> is /users/evlaops/fetch/fetched/tomout.evla.
>> 
>>    Employee ID		:  =>EVLA O/L
>>  * Completed (Y/N)	:  
>>  * Date (MM/DD/YYYY)	:  
>>  * Time worked		:  
>>  * Corrective Action	:  
>> 
>>  * Values required when email is returned.
>> 
>> 
>