restor: beam fit failed
Posted: Fri Sep 19, 2014 6:45 pm
Hi all,
I've been imaging some ATCA data recently and all goes well on my linux64 machine which is running MIRIAD built from source with some of the array sizes increased. However, when I run it on another linux64 machine running a binary installation of MIRIAD I get the error message "Beam fit failed" when I get to the restor task in my pipeline. Using the same map, beam and model created from the binary install but running restor on the source code install does not reproduce the error and the image is restored without an issue.
I had a quick look at the source to find out more about the error and it seems that this can happen when one of three things happen (from subs/nllsqu.for): a singular matrix is encountered, max number of iterations is exceeded, or it fails to find better solution. I don't think that the max number of iterations are being exceeded considering this is not a customisable parameter that I changed when compiling the source code install - but I could be wrong! I am unsure on what causes the other errors and would really appreciate some help.
At this time, I need to use the machine with the binary install for the imaging so simply using the working source install I have isn't an option. If you need the data products that are causing this error I can supply those on request (together they are quite large and I can't upload them right now).
Regards,
Andrew
I've been imaging some ATCA data recently and all goes well on my linux64 machine which is running MIRIAD built from source with some of the array sizes increased. However, when I run it on another linux64 machine running a binary installation of MIRIAD I get the error message "Beam fit failed" when I get to the restor task in my pipeline. Using the same map, beam and model created from the binary install but running restor on the source code install does not reproduce the error and the image is restored without an issue.
I had a quick look at the source to find out more about the error and it seems that this can happen when one of three things happen (from subs/nllsqu.for): a singular matrix is encountered, max number of iterations is exceeded, or it fails to find better solution. I don't think that the max number of iterations are being exceeded considering this is not a customisable parameter that I changed when compiling the source code install - but I could be wrong! I am unsure on what causes the other errors and would really appreciate some help.
At this time, I need to use the machine with the binary install for the imaging so simply using the working source install I have isn't an option. If you need the data products that are causing this error I can supply those on request (together they are quite large and I can't upload them right now).
Regards,
Andrew