from:	chris sedgwick 
to:	"Zhao, Jun-Hui" 
date:	Wed, Feb 7, 2018 at 12:34 PM
subject:	Re: MIRIAD WB5.0.7

Ah, thank you.

Chris

> On 7 Feb 2018, at 17:32, Zhao, Jun-Hui  wrote:
>
> Thanks, Chris.
> These are not typos. The file ${dt}_rx0.lsb actually contains dual frequency configurations produced from the rx0 and rx3 in the dual RX operation mode.
> The prefix ${dt}_rx0.lsb was generated by the program SMALOD according to the input parameters and the index of the first receiver in the data.
> The receiver in frequency configuration split data is distinguished by rx00  for RX 0 (230) and rx03 for RX 3 (240) in the content of the file names.
> Jun-Hui
>
> On Wed, Feb 7, 2018 at 12:16 PM, chris sedgwick  wrote:
>
>     Hi Jun-Hui
>
>     I noticed a couple of typos in in pre-processing step 2 script:
>
>     Line 142: rx0 should be rx3
>     Line 152: rx0 should be rx3
>
>     Chris
>
>
>
>
>>     On 6 Feb 2018, at 15:55, Zhao, Jun-Hui  wrote:
>>
>>     Hi Chris,
>>          Miriad now only supports the full-resolution original SWARM data but not for the SMARechunkered data.
>>     However, it should work if SMARechunkered data have the data structure as the original and no new
>>     data issues produced during the rechunking process.
>>
>>          I would recommend to use the original. The on-line data issues in the original data are repaired with the patches
>>     being implemented in SMALOD. If needs lower spectral resolutions, one can bin the spectral channels
>>     with UVAVER for the pre-processed data.
>>          Jun-Hui
>>
>>     On Tue, Feb 6, 2018 at 9:13 AM, chris sedgwick  wrote:
>>
>>         Hi Jun-Hui
>>
>>         Many thanks for your email and sample scripts.
>>
>>         One quick question - am I safe using data after using SMARechunker, or should I use the original data ?
>>
>>         Best wishes
>>         Chris
>>
>>