from:	Zhao, Jun-Hui 
to:	Peter Teuben 
cc:	"smamiriad@cfa.harvard.edu" 
date:	Thu, Aug 4, 2016 at 5:07 PM
subject:	Re: SMA MIRIAD Bug Report

Hi Peter,

The miriad_WB is based on a combination of the latest or close to the latest distributions from various parties around, including CARMA.

Yes, your update for the 64 bits did solve the problem for most of the routines that are used in imaging but not for all,
which was helpful for us to develop Miriad for SMA wideband data.

Some uv routines are running into troubles for handling uv datasets with a large size of SMA uvdata; 
the algorithms in most of the users' interface routines in Fortran appear to assume the default integer type
which is 32bits for a 64 bits machine. We haven't got chance to go through all the Miriad routines yet.
For the time being,  we have made a detour to get around the 64bits integer issue with the C-routines along with implementing
a few critical Fortran routines that are needed in our pre-processing SMA data; with these routines we created a procedure
to separate the uv-data produced from hybrid ASIC and SWARM correlators into subsets while reduce the size of
SWARM datasets to be tolerant to  most of Miriad distributions ; thus users can continue to use the globally distributed, stable Miriad packages from ATNF,
CARMA, SMA as well as some  self-maintained Miriad (most of them stay on 32bits integer) from users or individual research groups
for Mac, Ubuntu, Suse, Fedora, centOS and etc. to reduce SMA data following their own way.

The temporary/tentative setup that we provided appears to have been working fine until some hardware issues in recent,
such as randomly re-configuring correlator due to failures of two crates occurred in the old ASIC machine at the SMA site
and frequently internal disk failures occurred on my desktop machine since early this year.
We are working on to fill these holes.


Jun-Hui
     
 


On Thu, Aug 4, 2016 at 12:54 PM, Peter Teuben  wrote:

    can you check how your $MIRSUBS/log.for differs from ours?  Our versions have never been sync'd in a while, and I remember a number of 64 bit issues that we solved that you may have not seen.

    I'm on the road, not back till the weekend, so my sleuthing is rather limited.



    On 08/04/2016 12:36 PM, Zhao, Jun-Hui wrote:
>     Hi Peter,
>     Sure, it would be great if you can help us take care of ubuntu issues.
>     Thanks,
>     Jun-Hui
>
>     On Thu, Aug 4, 2016 at 12:29 PM, Peter Teuben  wrote:
>
>         Jun-Hui,
>            I'm fairly certain I've seen this error before, it has to do with a 64 bit conversion that wasn't completed. Perhaps browsing through our CVS will help. I will admit if it was that error, I'm surprised it hasn't shown up before.
>
>         peter
>
>
>         On 08/04/2016 10:34 AM, Zhao, Jun-Hui wrote:
>>         Upon the limited resource allocated, we (the SMAMIRIAD group) are barely able to support Miriad for SMA on RedHat and centOS for the time being.
>>         Please check with other supporting teams at SMA.
>>              Jun-Hui
>>
>>         On Thu, Aug 4, 2016 at 4:42 AM,  wrote:
>>
>>             Below is the result of the form submission.  It was submitted by
>>              (klau1001@gmail.com) on Thursday, August 4, 2016 at 04:42:48
>>             ---------------------------------------------------------------------------
>>
>>             Logging to SMAMBugRpt
>>
>>             Bug Tracking No          52
>>
>>             User_Name: Kenny
>>
>>             Report_Type: Bug
>>
>>             Severity: Major
>>
>>             Priority: High
>>
>>             Linux: Ubuntu
>>
>>             Linux_Other:
>>
>>             Linux_Ver: Ubuntu 16.04
>>
>>             Kernel:
>>
>>             Hardware:
>>
>>             Occured_When: Task
>>
>>             Occured_Notes: SmaUvPlt: version 2.2 01-Jul-2013
>>
>>             Description: Received an unknown  unsolvable error
>>
>>             Terminal: $ smauvplt vis=M94NW_rx0.usb axis=time,ampl device=/xw nxy=1,1 yrange=0,300
>>             SmaUvPlt: version 2.2 01-Jul-2013
>>              Fatal Error smauvplt:  LogWrite: LogOpen never called
>>
>>
>>             Supplied_Code:
>>
>>             ---------------------------------------------------------------------------
>>
>>
>>         -- 
>>         You received this message because you are subscribed to the Google Groups "smamiriad" group.
>>         To unsubscribe from this group and stop receiving emails from it, send an email to smamiriad+unsubscribe@cfa.harvard.edu.
>
>
>         -- 
>         You received this message because you are subscribed to the Google Groups "smamiriad" group.
>         To unsubscribe from this group and stop receiving emails from it, send an email to smamiriad+unsubscribe@cfa.harvard.edu.
>