[daip] Re: tsm file format changes.

[Craig Walker]

I got mixed up with the previous message (see below).  TSM hasn't 
changed.  The problems that I point out are problems with VLOG, which
reads the TSM output and does some minor alterations, including introducing
the oddities that I point out below.  These oddities are in the .TSYS
file from VLOG.  Again, they are benign so there is no urgency for a fix.

Craig



> From cwalker Fri Jul  7 10:34:22 2000
> To: jwrobel, sblachman
> Subject: tsm file format changes.
> Cc: julvesta
> X-Sun-Charset: US-ASCII
> Status: RO
> 
> I am looking at a tsm output file (cal.vlba) file closely for the
> first time in a while and see that there have been some format
> changes in the Tsys section.  These changes I guess don't cause
> problems, but they are poor style.  Here is a quick sample yanked
> out of the middle of a file:
> 
> !  4  13mm D LCP  4 U 813.49MHz   8M  21817.49MHz  5.34
> TSYS  timeoff = 0.0  SC  FT = 1.0
> INDEX = 'R01', 'L01', 'R02', 'L02'/
> 025 17:53.050 173.5 189.9 184.6 192.2 ! 17.6
> 025 17:55.000 173.5 188.2 182.4 191.4 ! 18.0
> 025 17:56.750 172.7 188.3 182.6 189.2 ! 18.3
> !
> ! SC BW043D   3C84/0   025-17:57:30/025-18:03:00
> /
> !  1  13mm B RCP  1 U 805.49MHz   8M  24309.49MHz  3.99
> !  2  13mm D LCP  2 U 805.49MHz   8M  24309.49MHz  3.74
> !  3  13mm B RCP  3 U 813.49MHz   8M  24317.49MHz  3.89
> !  4  13mm D LCP  4 U 813.49MHz   8M  24317.49MHz  3.74
> TSYS  timeoff = 0.0  SC  FT = 1.0/
> 025 17:58.550 164.2 171.8 166.7 172.0 ! 18.6
> 025 18:00.500 161.8 169.3 164.7 170.7 ! 19.0
> 025 18:02.250 161.6 168.3 164.0 168.7 ! 19.3
> !
> !
> 
> What I don't like are:
>  1.  The lack of a space before the / in the TSYS and INDEX lines.
>      I worry that the parser might not separate the value from the /,
>      although I have not seen evidence that this is a problem.
>  2.  The fact that the / on a line of it's own, which is supposed
>      to terminate the preceeding list of Tsys's comes after the 
>      scan header line for the next scan.  Since the scan header line
>      is formally a comment (after the !), this is also benign, but
>      looks quite odd to someone used to dealing with KEYIN style
>      files - which includes most VLBIers because SCHED uses the same
>      parser.
> 
> I looked at a file from March 98 (chosen at random) and these 
> changes have crept in since then.  Since they seem to be benign,
> there is no rush to fix them.  But I think it would be a good
> idea to do so eventually.
> 
> Craig
> 


Here is what is in the cal file from tsm:

! SC BW043D   3C84/0   025-17:52:00/025-17:57:29
!  1  13mm B RCP  1 U 805.49MHz   8M  21809.49MHz  5.84
!  2  13mm D LCP  2 U 805.49MHz   8M  21809.49MHz  5.33
!  3  13mm B RCP  3 U 813.49MHz   8M  21817.49MHz  5.79
!  4  13mm D LCP  4 U 813.49MHz   8M  21817.49MHz  5.34
025 17:53.050 173.5 189.9 184.6 192.2 ! 17.6
025 17:55.000 173.5 188.2 182.4 191.4 ! 18.0
025 17:56.750 172.7 188.3 182.6 189.2 ! 18.3
!
! SC BW043D   3C84/0   025-17:57:30/025-18:03:00
!  1  13mm B RCP  1 U 805.49MHz   8M  24309.49MHz  3.99
!  2  13mm D LCP  2 U 805.49MHz   8M  24309.49MHz  3.74
!  3  13mm B RCP  3 U 813.49MHz   8M  24317.49MHz  3.89
!  4  13mm D LCP  4 U 813.49MHz   8M  24317.49MHz  3.74
025 17:58.550 164.2 171.8 166.7 172.0 ! 18.6
025 18:00.500 161.8 169.3 164.7 170.7 ! 19.0
025 18:02.250 161.6 168.3 164.0 168.7 ! 19.3

The single slash comes at the end of all SC inputs.