Date: Tue, 9 Nov 2010 08:27:22 -0500 (EST)
From: Jun-Hui Zhao 
To: Glen Petitpas 
Cc: Ken Young , Ramprasad Rao 
Subject: Re: data won't load in miriad now

Hi Glen and Ram,
    The updated version (1.1.2) would have no problems to
read the three files.

SmaLod: version 3.4-beta 13-October-10
double-band patch................DbP version 1.1.2.-beta: 2010-10-13

    Please install the updated version (1.1.2) of SMA Miriad for 4GHz
(http://www.cfa.harvard.edu/sma/miriad/download/).
    Please let me know if the problems persist.

    Jun-Hui

On Mon, 8 Nov 2010, Glen Petitpas wrote:

>
> Hi
>
> As of last Tuesday, I cannot open the bandwidth doubled data
> anymore.
> I am using miriad (newest test version SmaLod: version 3.1-beta
> 26-July-10) on "rtdchilo2" in Hilo.
>
> It has been working fine (with the exception of a few strange correlator
> setups which set s1=0) but as of last Tuesday I cannot load BDA data
> into miriad.
>
> The current installation of miriad will still load data *prior* to last
> Monday,
> so I suspect there is something different about the data files themselves.
>
> I am worried something got fiddled with on the last testing night and not
> set straight.
>
> 101101_04:14:41 loads fine
> 101103_02:48:04 loads with old miriad because it was single BW data
> 101103_12:12:23 loads fine
> 101104_02:52:47 doesn't load at all
> 101104_14:23:29 doesn't load at all
> 101105_03:19:14 doesn't load at all
> (everything since doesn't load)
>
> When it doesn't load, here is what I get (basically nothing).....
> ---------------------------
> rtdchilo2:gpetitpa[quickLook] 58 % smalod
> in=/sma/rtdata/science/mir_data/101104_14:23:29 out=test rxif=-1
> sideband=0 nscans=1
> SmaLod: version 3.1-beta 26-July-10
> double-band patch................DbP version 1.1.0.-beta: 2010-07-28
> open output file.
> *********************************
> *  Observing Date: 2010 Nov 04  *
> *********************************
> rtdchilo2:gpetitpa[quickLook] 59 %
> --------------------------------
>
> Any feedback is welcome as I am now back to not being able to run
> my pipeline script again
>
> Cheers
> Glen
>