[daip] FRING problem in NEW and TST

[Eric Greisen]

Walter Alef wrote:
> Hi Eric,
> 
> This is getting more mysterious. When I switched back to TST and NEW this 
> morning the problem could not be repeated anymore! On our cluster where we 
> only have 31DEC10 and 31DE09 the problem is still repeatable. 
> 
> One thing I noticed is that when I changed the version to OLD, IN2NAME was 
> claimed to have an illegal character in it. (It does not do that now anymore 
> when I change versions.) But if a bad character was in IN2NAME why did TST 
> and NEW not complain about it?
> I had the same on the cluster AIPS installation. Another one I saw there was 
> an IN2CLASS which needed to be reset to ''. On the cluster we have an illegal 
> content of a variable occasionally even though we don't change the AIPS 
> version between sessions. I don't know whether this has any relation to the 
> problem. 
> 
> I could send you another file with 6 SN tables from different runs of FRING, 
> some of which show good results and some the wrong ones I described. Don't 
> know whether that would be on any help as long as the problem cannot be 
> provoked in a reliable way. I also have the message file which shows large 
> discrepancies between FFT search results and LSQ results for some IFs.

I wonder if we are having an adverb problem - I added PDVER on Sept 8, 
2010 and CHINC on December 31, 2009.  This makes the 09 and 10 versions 
have different adverbs which come before IN2NAME.  So a TGET of a 
31DEC09 run in 31DEC10 should get an error.  The adverbs will be shifted 
by 2 words.  This will move floats into chars and provoke the error you 
saw but it can also move chars into floats possibly producing an adverb 
that prints as 0.0 but tests as > 0.0.

Try a DEFAULT FRING and fill in all adverbs by hand.  If that produces 
an error let me know.  We are getting a report that the exhaustive 
baseline search algorithm is not working correctly in IFs 3 and 4 of a 4 
IF data set.  Perhaps that was being triggered by an unintended adverb??

Let me get to Adam's problem and see what can be discovered.

Eric Greisen