<html><head></head><body>Thanks. Good to hear.<br><br><div class="gmail_quote">On April 20, 2015 3:36:25 PM EDT, Eric Greisen <egreisen@nrao.edu> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">On 04/15/2015 01:50 PM, Bob Garwood wrote:<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> Hi Eric,<br /><br /> We've seen some changes in DBCON as used by the GBT pipeline in the TST<br /> version. These may indicate long standing mis-uses of pseudo-uvdata to<br /> hold GBT data prior to gridding with SDGRD but at any rate, TST is<br /> currently unusable by the GBT pipeline so we need to sort out what the<br /> fix is before TST becomes NEW next year.<br /><br /> We get calibrated GBT data into AIPS by converting SDFITS files to<br /> random group/pseudo-uvdata using a program that Glen Langston wrote<br /> called idlToSdfits (that we have the code for, but haven't done much<br /> work inside it since Glen left NRAO). For multi-beam data, we calibrate<br /> the beams separately, producing a separate SDFITS file, and then a<br /> separate uvfits file which we read into aips and!
then
use DBCON in aips<br /> to produce one data set to be used by SDGRD. The DBCON step now fails<br /> in the TST version of AIPS, producing either this message:<br /><br /> DBCON1: UVPGET: RANDOM PARMS NOT ALL THERE: 0 1 0 -1 2 -1 -1 -1 -1 -<br /> 1 -1 -1<br /><br /><br /> or this ...<br /><br /> DBCON1: I CAN ONLY HANDLE STANDARD FORMS OF STOKES AXES<br /><br /><br /> We believe both of these errors have to do with the STOKES axis,<br /> depending on what idlToSdfits has done.<br /><br /> In the first case, the input SDFITS files are all single polarization<br /> and so the STOKES axis (which is the 3rd axis in the uvfits file) is just<br /> NAXIS3 = 1<br /> CRVAL3 = -1<br /> CRPIX3 = 1<br /> CDELT3 = -1<br /><br /> And DBCON is being asked to combine 2 of those.<br /><br /> In the second case, idlToSdfits has combined 2 polarizations so the<br /> STOKES axis has 2 elements on it and looks like this:<br /> NAXIS3 = 2<br /> CRVAL3 = -1<b!
r />
CRPIX3 = 1<br /> CDELT3 = -1<br /><br /> Using "imh" in AIPS, the "uv" data files all reflect those values from<br /> the original fits files.<br /><br /> Any advice on how we should proceed (e.g. modifying the output of<br /> idlToSdfits) would be appreciated. Thanks.<br /><br /> Bob<br /></blockquote><br /><br />A MNJ tomorrow will fix the DBCON issues.<br /><br />Eric<br /></pre></blockquote></div></body></html>