[daip] VLBAEOPS and INFILE.

[Craig Walker]

I'm using AIPS TST on a Mac with a midnight job a couple of weeks ago 
(just before previous message).  I'm not quite sure how recent my AIPS 
was in Feb.

Meanwhile, I need INFILE to do the EOP.  The aips data gathering schemes 
cannot penetrate my firewall etc at home.  So I log in at the AOC, ftp 
the files to the AOC, then copy them home.  Of course, CLCOR for EOP is 
pretty simple minded so I can just run it without much additional 
trouble.   Note that, if you are working on a whole series of 
observations, you can just download one EOP file and use it for all.

AIPS global variables used for different purposes in different programs 
has long been a weakness of the system.  There's probably not much to be 
done about that now.

Cheers,

Craig


On 11/12/2013 01:38 PM, Amy Mioduszewski wrote:
> I got rid of INFILE in VLBAEOPS after years of being badgered to do so.
> People would run VLBATECR before VLBAEOPS and the INFILE would be filled
> in with the wrong thing. I refused to change it because I figured people
> should look at their inputs, but did eventually cave because people
> started complaining to Eric. So I obviously didn't remove it from the
> EXPLAIN files. I did this last year, so unless you were using an old
> version of AIPS it should not have been there in February.
>
> Will fix the documentation.
>
> Amy
>
> R. Craig Walker wrote:
>> Something strange is going on with VLBAEOPS and INFILE. I have already
>> downloaded my file so I want to use INFILE. If you type "inp vlbaeops",
>> you get the input file specifications, but they do not include the INFILE
>> option. If you type "help vlbaeops", infile is the list of described
>> inputs.
>>
>> When I ran VLBAEOPS with INFILE specified, it tried to go to the net but
>> died because I don't have wget on my home Mac. I did a "list vlbaeops"
>> and don't see any evidence that it pays attention to INFILE until after
>> the download is done, and then it goes to the file in /tmp. The header
>> for VLBAEOPS does list INFILE as a valid input and the instructions for
>> how to deal with errors suggest using it. So did someone remove INFILE
>> from the actual proc, but not from all the documentation? Do I need to
>> run CLCOR directly (that will be muy immediate work-around)?
>>
>> This was apparently not an issue in February when I last ran VLBAEOPS on
>> the same data. My notes, from which I cut and pasted the inputs, don't
>> indicate any trouble running the routine.
>>
>> Cheers,
>>
>> Craig
>>
>>
>>
>> ---------------------------------------------------------------------
>> R. Craig Walker Array Operations Center
>> cwalker at nrao.edu National Radio Astronomy Observatory
>> Phone 575 835 7247 P. O. Box O
>> Fax 575 835 7027 Socorro NM 87801 USA
>> --------------------------------------------------------------web
>>
>>
>> _______________________________________________
>> Daip mailing list
>> Daip at listmgr.cv.nrao.edu
>> http://listmgr.cv.nrao.edu/mailman/listinfo/daip
>>

-- 
---------------------------------------------------------------------
     R. Craig Walker            Array Operations Center
     cwalker at nrao.edu           National Radio Astronomy Observatory
     Phone  575 835 7247        P. O. Box O
     Fax    575 835 7027        Socorro NM 87801   USA
---------------------------------------------------------------------