[daip] BPASS problem
Eric Greisen
egreisen at nrao.edu
Fri Jan 11 12:45:48 EST 2008
Luca Moscadelli writes:
> AIPS 1: STOKES 2 -1.0000000E+00 1.00 -1.0000000E+00 0.00
> AIPS 1: FREQ 1024 6.6682520E+09 1.00 1.9531250E+03 0.00
> AIPS 1: IF 1 1.0000000E+00 1.00 1.0000000E+00 0.00
> BALENT> BPASS1: BPCOPY: copied 29687 vis records for bandpass fitting
> BALENT> BPASS1: Determining solutions
> BALENT> BPASS1: Writing BP table 1
> BALENT> BPASS1: Time= 0/ 06 00 26 IFs= 1 - 1 Chann= 1 - 1024 Polzn=ALL
> BALENT> BPASS1: BASOLV: 907 flagged channels in IF 1
> BALENT> BPASS1: BASOLV: 966 flagged channels in IF 1
> BALENT> BPASS1: BPSOL: wrote 8 records to the BP table
> BALENT> BPASS1: ZABORS: signal 11 received
> BALENT> BPASS1: ABORT!
> >*** glibc detected *** BPASS1: free(): invalid next size (normal): 0x0a3a4570 ***
> AIPS 1: SOLTYPE 'R' Soln type,' ','L1','GCON',
> AIPS 1: 'R', 'L1R', 'GCOR'
> AIPS 1: REFANT 1 Reference antenna
> AIPS 1: OUTVERS 2 Output BP table version
> AIPS 1: 0 => a new table to be
> AIPS 1: generated.
> AIPS 1: BPASSPRM 1 0 Control information:
> AIPS 1: 0 0 1: if > 0 use only the
> AIPS 1: 0 0 autocorrelation data.
> AIPS 1: 0 0 2: print level - see help
> AIPS 1: 0 3 3: If > 0 do not divide data
> AIPS 1: 0 by source model
This is rather strange. You have requested auto-correlation BPs only
and if the baove inputs apply to the messages you sent you requested
table 2 - but the messages from BPASS say table 1 and include
an enormous fraction of the channels fully flagged. That flagged
message only occurs in the code for cross-correlation bandpasses.
Are you sure that these messages and the BPASS inputs go together?
The abort on free should not damage the results unless the task has
gone very wrong.
Eric Greisen
More information about the Daip
mailing list