Testing (May 15, 2014)

Goal:

  • Test recent VEGAS fixes for switching signals, blanking, and INTEGRAT

Plan:

  • with normalized manager
  • run mode 19 with no switching as fast as possible to see UTCDELTA
  • run mode 19 with doppler tracking, but not switching
  • run mode 19 with cal switching, but no doppler tracking
  • run mode 19 with cal switching and doppler tracking
  • run mode 19 with frequency switching, but no doppler tracking
  • run mode 19 with frequency switching and doppler tracking
  • with unnormalized manager
  • run mode 19 with no switching as fast as possible to see UTCDELTA
  • run mode 19 with doppler tracking, but not switching
  • run mode 19 with cal switching, but no doppler tracking
  • run mode 19 with cal switching and doppler tracking
  • run mode 19 with frequency switching, but no doppler tracking
  • run mode 19 with frequency switching and doppler tracking

Info:

  • TGBT13B_502_59 and _60 and _61

Log:

  • Session 59
  • Scans 1 and 2 are bogus.
  • Scan 3: INTEGRAT_Mode19_Nocal_nodoppler
  • not getting any data out. Waiting for Ray and Joe to see what's happening.
  • Scan 4: INTEGRAT_Mode19_Nocal_nodoppler -- running scan again for Ray and Joe to diagnose. Seems to have run okay.
  • Scan 5: INTEGRAT_Mode19_Nocal_doppler
  • Scan 6: INTEGRAT_Mode19_cal_nodoppler --- same problem as with scan 3. VEGAS in running mode, but everything else is stopped.
  • Ray and Joe are figuring things out
  • Scan 7: INTEGRAT_Mode19_cal_nodoppler -- re-running to see if we can reproduce problem. Yes it does.
  • Scan 8: INTEGRAT_Mode19_cal_nodoppler -- re-running to see if have a fix. scan seems to end fine. This scan produced data. It should not have because tint << than new blanking time, which is 357ms according to Joe's spreadsheet.
  • Scan 9: INTEGRAT_Mode19_cal_nodoppler -- 300s scan to make sure fix is okay.
  • Scan 10: INTEGRAT_Mode19_nocal_nodoppler --
  • Scan 11: INTEGRAT_Mode19_nocal_doppler --
  • Scan 12: INTEGRAT_Mode19_fsw_cal_nodoppler -- illegal configuration -- set swtype='fsw'
  • Scan 13: INTEGRAT_Mode19_fsw_cal_nodoppler
  • Scan 14: INTEGRAT_Mode19_cal_nodoppler -- changing the tint=1.43. new blanking time is 357ms. need to have 4x that for integration time to get half the data. -- set to topo to not doppler track, but dopplertrackfreq is set to a value. Is this causing it to dopplertrack?
  • Scan 15: INTEGRAT_Mode19_fsw_cal_nodoppler -- changed the tint=2*1.43 = 2.86s -- four phases
  • Scan 16: INTEGRAT_Mode19_fsw_cal_doppler -- changed the tint=2*1.43 = 2.86s -- four phases
  • Scan 17: INTEGRAT_Mode19_cal_nodoppler -- removed dopplertrackfreq from configuration to see if that helped. It didn't.
  • Scan 18: INTEGRAT_Mode19_cal_nodoppler -- changed source to 3C48 which doesn't have velocity in catalog.
  • Ray turned off normalizing in manager
  • Scan 19: INTEGRAT_Mode19_nocal_nodoppler --
  • Scan 20: INTEGRAT_Mode19_nocal_doppler
  • Scan 21: INTEGRAT_Mode19_cal_nodoppler
  • Scan 22: INTEGRAT_Mode19_cal_dopper
  • Talked to Anish. He had assumed tests would be done on normalized data.
  • Ray turned on normalizing in manager
  • Scan 23: INTEGRAT_Mode19_nocal_nodoppler --
  • Scan 24: INTEGRAT_Mode19_nocal_doppler
  • Scan 25: INTEGRAT_Mode19_cal_nodoppler
  • Scan 26: INTEGRAT_Mode19_cal_doppler
  • Scan 27: INTEGRAT_Mode19_fsw_cal_nodoppler
  • Scan 28: INTEGRAT_Mode19_fsw_cal_doppler
  • Scan 29: INTEGRAT_Mode4_cal_doppler
  • Scan 30: INTEGRAT_Mode4_fsw_cal_doppler

  • Changed to session 60
  • Scan 35-36: TsysMode10Track
  • Scan 37-39: TsysMode19Track
  • Scan 40-42: TsysMode24Track
  • Scan 43-45: TsysMode14Track

  • Switched to Jens' stuff
  • small configuration issues. insert vegas.subband=8??
  • turtle died while running script
  • OffTrack and TargetTrack cause system to fail.
  • Scan 46: Two track commands on the same location. scan ran, but astrid still thinks it's tracking. kauffmann_test
  • Scan 47&48: Twot rack commands. successful. kauffmann_test1

  • Switched to Ron Allen's stuff
  • They need to change spectrallineconfig to vegas_fs_aconfig
  • had to deal with the astrid remembers everything bullshit
  • changed sessions to 61
  • Scan 49: allen_oh

  • Playing around with Jens' configuration more
  • Why is ramps using such a big spread? We can only get 1.8 GHz.
  • Scan 52: ramps_beam_test. Looking at the RAMPS configuration. It looks like they get the same error message and have been ignoring it.
Topic revision: r3 - 2015-01-27, RichardPrestage
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding NRAO Public Wiki? Send feedback