0000047: Not possible todo a calibrator in LineMode
All Projects | CNI | DZB | equalizer | IVC/ADC | LFFE | MFFE | Puma | Puma 2 | RFI | RT | submission | system time | Tadu | Time/LO | TMS | VLBI

Main | My View | View Issues | Change Log | Docs
  

Viewing Issue Simple Details [ Jump to Notes ] [ Issue History ] [ Print ]
ID Category Severity Reproducibility Date Submitted Last Update
0000047 [TMS] tweak always 31-07-08 09:32 14-06-10 07:55
Reporter Jurjen Sluman View Status public  
Assigned To Hans van Someren Greve
Priority normal Resolution fixed  
Status closed  
Summary 0000047: Not possible todo a calibrator in LineMode
Description It is not possible to observe a calibrator in linemode.
In STFMA it is possible to prepare a calibrator in linemode.
When using option 9 to see what the TMSsetting will be,
we see that, for the LineMode items, the values are incorrect.
Output of optie 9 (partly):
-----------------------------------------
FW1.Mode = line
FW1.RestFrequency = 0.000000 MHz
FW1.TrackingSpeed0 = 0.000000
FW1.VelocDefinition = const
FW1.ConversionType = const
FW1.TopoFreqTime = 0.000000
-----------------------------------------

it should be something like:
-----------------------------------------
FW1.Mode = line
FW1.RestFrequency = 1420.405752 MHz
FW1.TrackingSpeed0 = 0.000000
FW1.VelocDefinition = bary
FW1.ConversionType = optical
FW1.TopoFreqTime = 54678.360291
-----------------------------------------
Additional Information By renaming the (well known) calibrator name to another name it works.
example:
3C286 does NOT work
T_3C286 does work
Attached Files

- Relationships

- Notes
(0000055)
Jurjen Sluman
12-08-08 09:41

 The change allows the user to use standard calibrator names (like
3C147) for line observations.

There is however a small penalty.
So far the program assumed, that if the default observation was a line
observation, and you specified a Fieldname equal to a name which was
present in the calibrator list file, you wanted to specify a
calibration observation for the line observation.
That is now no longer the case.

If the default observation is a line observation, then in the menu

************************************************
* DZB configuration parameters *
************************************************

Corr board mask (Hexadec. Order:Unit 31..0) FFFFFFFF
ADC unit available mask (Order: Unit 7...0) 11111111
Taper code US/HN/MS4/HM/TR/MB US
Parameter (alfa) for taper function 0.00
Correlator bit mode (1,2) 2
Use hardware DZB phase switching ? YE
Mod. point of phaseswitching (FE,IVC,BOTH) FE
Phase switch step size (degr) (90,180,270) 180
Phase switch pattern code (0=Walsh) 0
Noise source switch code ? 0
Pattern : 0000000110000000
Total Power gating mode (0,1,2,3) 0
Use LOFAR test station (WHAT) ? NO
Frequency tracking required ? YE
Number of IVC subbands to use 1

Specification ok ? YE

You will always see
Frequency tracking required ? YE

If you want to specify a calibrator for the line observation than you
have to set :

Frequency tracking required ? NO

then the program will recognize that it is a line calibrator, and will
automatically set the proper sky frequency, etc.

PS
As i am not quite sure about the specification conventions observers
use, i would like to ask you to test this thouroughly on line and
calibration for line observations.
 
(0000065)
Jurjen Sluman
19-08-08 07:02

 An observation was done and it worked well. (10803922_S0_T0).
Also the output of option 9 (stfma) is correct:
-----------------------------------------
FW1.Mode = line
FW1.RestFrequency = 1420.405752 MHz
FW1.TrackingSpeed0 = 1000.000000
FW1.VelocDefinition = bary
FW1.ConversionType = optical
FW1.TopoFreqTime = 54698.305682
-----------------------------------------
 

- Issue History
Date Modified Username Field Change
31-07-08 09:32 Jurjen Sluman New Issue
31-07-08 09:34 Jurjen Sluman Assigned To  => Hans van Someren Greve
31-07-08 09:34 Jurjen Sluman Status new => assigned
12-08-08 09:41 Jurjen Sluman Note Added: 0000055
12-08-08 09:41 Jurjen Sluman Status assigned => testing
12-08-08 09:41 Jurjen Sluman Resolution open => fixed
19-08-08 07:02 Jurjen Sluman Note Added: 0000065
19-08-08 07:02 Jurjen Sluman Status testing => resolved
14-06-10 07:55 Arno Schoenmakers Status resolved => closed