Hi Eric<br> It dawned upon me a little late that your reference to "binary" <br> was associated with the UVSUB-ed file. I was assuming you <br> meant a fresh "binary" AIPS installation. <br><br> The data I am working on is at my location in the machine I <br>
am using AIPS on. Hence no "ftp" related issue here. I guess <br> I confused you by my usage of "FITTP-ed". I used it to indicate <br> that I had used task FITTP to take out the UVSUB-ed data <br> from AIPS. <br>
<br> PS: The UVDIF did not reveal any "difference" in the original <br> and the UVSUB-ed data. <br> Moreover, the same exercise was performed using a 31DEC09 <br> AIPS, and the output UVSUB (output using FITTP) file could <br>
be opened by MIRIAD without error. <br><br> The exercise I am talking about is: <br><br> AIPS:<br> -->CALIB_UVDATA <br> -->RUN AIPS UVSUB [In2name = point source] <br>
-->Output = Pt Source subtracted UVSUB DATA <br> --> RUN AIPS IMAGR [to image the UVSUB DATA above]<br> --> Output = image of the background (pt. source removed)<br>
--> RUN AIPS UVSUB [in2name = image of background <br> obtained from above step]<br> --> Output = UVDATA for the Point Source<br>
--> RUN AIPS FITTP to disk<br><br> MIRIAD:<br> -->RUN MIRIAD FITS [ with input file = the UVSUB data <br> that was written to disk using FITTP]<br>
--> ERROR about "illegal basline number"<br><br> regards<br>--wasim<br><br><div class="gmail_quote">On Wed, Aug 17, 2011 at 1:02 AM, Wasim Raja <span dir="ltr"><<a href="mailto:wasimraja81@gmail.com">wasimraja81@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Dear Eric, <br> I repeated the exercise in an already installed but different <br> version of AIPS (31DEC09). And MIRIAD did not crib this <br>
time !! <br><br> I will now have to "carefully" update my 31DEC10 AIPS without <br>
disturbing the AIPS disk-area! <br><br> Thanks a lot for your help. <br> regards<br><font color="#888888"> --wasim</font><div><div></div><div class="h5"><br> <br><br><div class="gmail_quote">On Tue, Aug 16, 2011 at 8:22 PM, Eric Greisen <span dir="ltr"><<a href="mailto:egreisen@nrao.edu" target="_blank">egreisen@nrao.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div>Wasim Raja wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
These are GMRT data (taken at 327 MHz that has circular hybrids).<br>
Miriad does not crib when I try to read the original data. The problem<br>
appears only on the UVSUB-ed data.<br>
</blockquote>
<br></div>
Try the FTP again using "binary" - that is the only suggestion I can make. Inside AIPS you can run UVDIF to check for baseline changes... (make the allowed flux difference large to avoid messages for that).<br>
<font color="#888888">
<br>
ERic Greisen<br>
</font></blockquote></div><br><br clear="all"><br></div></div><div><div></div><div class="h5">-- <br>Research Fellow (A&A)<br>Raman Research Institute<br>Bangalore--560080<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Research Fellow (A&A)<br>Raman Research Institute<br>Bangalore--560080<br>