GB . Obsreports . November2006January2007Report

Observing Reports - November and December, 2006 and January 2007

Reports for previous months are linked from the main obsreports page.

To report a problem with Astrid, use AstridReports

To submit a summary of your observing session, send an email to gbtobssum. To see previous emails, see the gbtobssum archives. You will need your username and gbtobssum mailing list password to view this.

If you would like to receive an email every time a staff astronomer adds a new Observing Report, or any time a member of Electronics or Software provides responses, click here (WebNotify) and add your name to the list.

Click on the header of any column to sort the log by that column's entries. Two clicks on the header does a reverse sort.

To edit this table, simply click "edit table" at the bottom of the page. You no longer need to edit the wiki page directly!

Entries are:

Date: Entered as yyyy-mm-dd (e.g. 2005-03-09)

- Project Code: The is the full project code for the observing session, e.g. AGBT04A_042_12
- Observer: Use last names only
- Support: Last name of support scientist (yourself, if you are observing w/o a support scientist)

- Description: A complete description of the problem, with all information that seems relevant, including the number of times the even occurred during observations; Attach any relevant set-up or observing scripts in this column
- Response: Response of the person(s) responsible for fixing/assessing the issue. These comments should be signed by the author.

No	Date	Project Code	Observer	Support Scientist	Description & Scheduling Blocks	Response
1	11/13/2006	TKA_13NOV06	Larry Morgan	Larry Morgan	When pointing/focusing with the Ka-band receiver the pointing scans are not handled correctly due to the lack of calibration information. However, the default data processing mode for these scans is 'beamswitched'. This needs to be changed to 'raw'. Otherwise the user needs to constantly select the option as the mode switches back to default between, and even during scans. In short, please change the default data processing mode for the Ka-band receiver to 'raw'.	I will look into this. AmyShelton
2	11/28/2006	AGBT05B_011_46	Toney Minter	Toney Minter	I had an break command in my script create a popup in astrid. I hit the 'yes' button and the popup went blank but did not go away. Astrid became unresponsive. I killed my astrid and tried to start a new one. I selected "work online with control" and this popup then went blank but did not go away with astrid being unresponsive. I notified the operator who restarted turtle.	Thanks for the report. Hopefully this will be resolved as part of the Astrid hangup investigation and related bug fixes. AmyShelton
3	11/30/2007	T_ZPEC_29NOV06	Harris	O'Neil	IF manager went into an error state due to the power levels being too high, yet the scan was still able to run. Am I mis-remembering things, or shouldn't the system prevent a scan from running because of the error state?	Yes, if the Manager in question is included in the Scan Coordinator. AmyShelton
4	12/05/2006	AGBT06C_051	Greenhill	Minter	The observer reported that a pop-up from a break command took two minutes to show up. The break was after a pointing and focus whose data displays showed up without any apparent delays. It is not know if the pop-up got hidden under other windows and it took 2 minutes to find it or if it really took 2 minutes for the pop-up to appear. The observer was observing remotely.	Unable to reproduce, but noted. The SDD is examing other issues related to dialog pop-ups. JoeBrandt
5	01/01/2007	AGBT05B_011	Minter	Minter	When configuring the spectral processor for pulsar observations I continually find that the configuration tool does not setup the spectral processor as requested on the first attempt. It takes a second running of my astrid script to get the spectral processor setup correctly. This is very repeatable. An example script can be found in /users/tminter/pulsar_abs_obs/template_obs.py with the configurations used being in /users/tminter/pulsar_abs_obs/pulsar_abs.config	I ran the scripts with Toney many times during maintenance on 01/02/2007 and we could not duplicate the problem. The next time he observes with these scripts, he will save the initial spectral processor configuration before he runs the script. This may provide us a clue as to how to duplicate it and the source of the problem. For the AGBT06B_19_33 session, ASTRID logs confimed that the config tool reported that the spectral processor was in a different state than expected after configuration. This excerpt is from the ASTRID log for this session: [08:30:53] Checking telescope [08:30:53] Warning: Configuration complete but inconsistencies were found between the M&C system and the configuration tool. Verify the configuration [08:30:53] (manager, parameter, expected value, actual value ) [08:30:53] ('SpectralProcessor', 'balance', 'NotBalance', 'Balance') [08:30:53] ('SpectralProcessor', 'atodLevMode', 'Immediately', 'ScanStart') [08:30:53] ('Rcvr1_2', 'tuning_frequency', '1420.405752', '1420.406') [08:30:53] ('SpectralProcessor', 'numSpectr', '1', '2') [08:30:53] ('SpectralProcessor', 'reqNumChan', '1024', '256') [08:30:53] ('SpectralProcessor.SpectralProcessorA', 'observeFreq,1', '1420405752.0', '1420000000') [08:30:53] ('SpectralProcessor.SpectralProcessorB', 'observeFreq,1', '1420405752.0', '1420000000') [08:30:53]
6	01/02/2007	AGBT06B_019_33	Minter	Minter	A repeat of #5.

-- ToneyMinter - 12 Feb 2007

Topic November2006January2007Report . { Edit | Attach | Ref-By | Printable | Diffs | r1.1 | More }

Revision r1.1 - 12 Feb 2007 - 15:01 GMT - ToneyMinter	Content copyright © 1999-2007 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.