For a peak, I get the following message after the first two subscans: "No new corrections detected!" What is wrong?

FITS Writing Problems

Turtle complains that it may not be able to write the GO FITS file.

Usually when this happens, you will be returned to the command prompt and no application will be launched. There are several reasons why this error may occur, including not having write permissions in the directory you are trying to run from. You should see a message instructing you what to do to get turtle to start. If there are no messages, ask the operator to ssh to wind as monctrl, and RestartTurtle. Restart the turtle GUI and your scheduling blocks should be runnable..

Usually when this happens, you will be returned to the command prompt and no application will be launched. There are several reasons why this error may occur, including not having write permissions in the directory you are trying to run from. You should see a message instructing you what to do to get turtle to start. If there are no messages, ask the operator to ssh to wind as monctrl, and RestartTurtle. Restart the turtle GUI and your scheduling blocks should be runnable.

I had the system configured, but now it is complaining and/or by GO FITS files are missing

I had the system configured, but now it is complaining and/or by GO FITS files are missing/incomplete.

I aborted a scheduling block between slews. Now when I re-submit my scheduling block, the antenna insists on slewing to the incorrect source.

Problems with Submitting Scheduling Blocks

I get a dialog labeled "Syntax Error" that complains "wxTextCtrl instance has no attribute 'flush'"

This dialog is generated by the Scheduling Block Validator and indicates that you are either overquota or dangerously close. Remove some files in your directory and try again. Note: You do not need to restart your GUI.

This dialog is generated by the Scheduling Block Validator and is a known bug. Restart astrid (or turtle) and try again.

Problems with Submitting Scheduling Blocks

I get a dialog labeled "Syntax Error" that complains "wxTextCtrl instance has no attribute 'flush'"

-- AmyShelton - 05 Nov 2004

%META:TOPICPARENT{name="ObservingAPIExamples"}%

Turtle Troubleshooting

%META:TOPICPARENT{name="ObservingTools"}%

Observing Tools Troubleshooting

Turtle

Starting/Stopping/Running Turtle

I can't seem to get the Turtle GUI to start.

Problem: I can't seem to get the Turtle GUI to start.

Usually when this happens, you will be returned to the command prompt and no application will be launched. There are several reasons why this error may occur, including not having write permissions in the directory you are trying to run from. You should see a message instructing you what to do to get turtle to start. If there are no messages, ask the operator to ssh to wind as monctrl, and RestartTurtle. Restart the turtle GUI and your scheduling blocks should be runnable..

Solution: Usually when this happens, you will be returned to the command prompt and no application will be launched. There are several reasons why this error may occur, including not having write permissions in the directory you are trying to run from. You should see a message instructing you what to do to get turtle to start. If there are no messages, ssh to wind as monctrl. Once logged in, type RestartTurtle. Log out of wind. Restart the turtle GUI and your scheduling blocks should be runnable..

I moved by Scheduling Block from the job queue to the run queue on the Run tab, and it won't disappear from the run queue and run on the telescope. What do I do?

If this happens, there has likely been a disruption in communications between turtle and the control system. First, remove the Scheduling Block from the run queue by highlighting the Scheduling Block name, and then clicking the Remove button. Then, exit the turtle application. Ask the operator to ssh to wind as monctrl, and RestartTurtle. You will then be able to restart the turtle application and resume your observation.

Problem: My source name is not updating. What's wrong?

Solution: Right now, you need to set your source names manually. Add the following line to your turtle script as needed: SetValues("ScanCoordinator", {"source": "MySourceNameHere"})

I closed down the turtle application, and there is some rogue observation running - what do I do?

If you have exited the turtle application after promoting a Scheduling Block from the job queue to the run queue, and then asked the operator to restart turtle, the telescope will proceed to run the last observation you tried to submit. The solution is simple: remove all Scheduling Blocks from the run queue before you close the Turtle application.

Problem: I moved by Scheduling Block from the job queue to the run queue on the Run tab, and it won't disappear from the run queue and run on the telescope. What do I do?

I am not seeing state transistions (e.g. from "Activating" to "Ready or "Aborting") on the Turtle Monitor panel.

First, check on a status screen to make sure that there really are state transitions occurring in the control system. If there are, and the Turtle application is not picking them up, close the turtle GUI. Ask the operator to ssh to wind as monctrl, and RestartTurtle. Restart the turtle GUI and rerun your script. If the problem persists, restart Grail* on wind using TaskMaster and repeat this procedure.

Solution: If this happens, there has likely been a disruption in communications between turtle and the control system. First, remove the Scheduling Block from the run queue by highlighting the Scheduling Block name, and then clicking the Remove button. Then, exit the turtle application. Ask the operator to ssh to wind as monctrl, and RestartTurtle. You will then be able to restart the turtle application and resume your observation.

When I check the status of the processes running under TaskMaster on wind, I see that turtle.d shows Failure.

Close the turtle GUI. Ask the operator to ssh to wind as monctrl, and RestartTurtle. Restart the turtle GUI and rerun your script.

Problem: When doing a focus, my LFCs and Offsets are really huge - on the order of 20-80mm. What's wrong?*

I opened up more than one Turtle application and now none of them are operational, but my Scheduling Block is still running. What do I do?

Solution: It is required that you slew to your source before you attempt to focus. If you try to focus without first being on source, the telescope will try to focus at the last location stored in the antenna, which is probably not on your source. You will end up with LFCs that are extremely unreasonable and you will have little or no apparent signal in your data. For the rest of the details, go here.

First, ask the operator to abort your observation. Then, ask the operator to look up which processes your turtle applications are running under, and kill -HUP the process IDs. Ask the operator to ssh to wind as monctrl, and RestartTurtle, then you will be able to launch a new turtle application.

Problem: I closed down the turtle application, and there is some rogue observation running - what do I do?

Solution: If you have exited the turtle application after promoting a Scheduling Block from the job queue to the run queue, and then asked the operator to restart turtle, the telescope will proceed to run the last observation you tried to submit. The solution is simple: remove all Scheduling Blocks from the run queue before you close the Turtle application.

Configuration Problems

My source name is not updating. What's wrong?

Problem: I am not seeing state transistions (e.g. from "Activating" to "Ready or "Aborting") on the Turtle Monitor panel.

Solution: First, check on a status screen to make sure that there really are state transitions occurring in the control system. If there are, and the Turtle application is not picking them up, close the turtle GUI. Log on to wind as monctrl. Type RestartTurtle. Log out of wind. Restart the turtle GUI and rerun your script. If the problem persists, restart Grail* on wind using TaskMaster and repeat this procedure.

I had the system configured, but now it is complaining and/or by GO FITS files are missing

Problem: When I check the status of the processes running under TaskMaster on wind, I see that turtle.d shows Failure.

Problems with Pointing/Focus

When doing a focus, my LFCs and Offsets are really huge - on the order of 20-80mm. What's wrong?*

Solution: Close the turtle GUI. Log on to wind as monctrl. Type RestartTurtle. Log out of wind. Restart the turtle GUI and rerun your script.

Currently it is required that you slew to your source before you attempt to focus. If you try to focus without first being on source, the telescope will try to focus at the last location stored in the antenna, which is probably not on your source. You will end up with LFCs that are extremely unreasonable and you will have little or no apparent signal in your data. For the rest of the details, go here.

Problem: I can't get fits for my pointing and focus scans and the antenna seems have weird values for H and V.

I can't get fits for my pointing and focus scans and the antenna seems have weird values for H and V.

Solution: Close the turtle GUI. Log on to wind as monctrl. Type RestartTurtle. Log out of wind. Restart the turtle GUI and rerun your script. If the problem persists, restart Grail* on wind using TaskMaster and repeat this procedure.

I'm using a dual-beam receiver, and not seeing any pointing source.

Problem: Turtle seems to hang after a scan (e.g. Slew).

I did a peak/focus, but the X-axis on my GFM plot does not cover the range I was expecting.

For a focus, GFM correctly displays the result, but after a few seconds, a dialog box pops up, telling that turtle has not received an updated focus, and asking me if I want to abort the procedure. What should I do?

Solution: Close the turtle GUI. Log on to wind as monctrl. Type RestartTurtle. Log out of wind. Restart the turtle GUI and rerun your script. If the problem persists, restart Grail* on wind using TaskMaster and repeat this procedure.

On occasion, there is a communication error between GFM and Turtle on focus scans, and so Turtle does not see the new value that has been calculated. It the calculated offset is small, simply ignore the failed update, and continue with your scheduling block. If the calculated offset is significant, you should probably abort the current scheduling block, and ask the Operator to update the Y LFC with the value reported by GFM. If this persists for a session, you should put a "Break" in your scheduling block immediately after the focus. When Turtle complains about the failure to update, ask to continue. Then, when the observation pauses, ask the Operator to update the LPC before answering the dialog box from the "Break".

Problem: I opened up more than one Turtle application and now none of them are operational, but my Scheduling Block is still running. What do I do?

Antenna Control and Slewing Problems

I aborted a scheduling block between slews. Now when I re-submit my scheduling block, the antenna insists on slewing to the incorrect source.

Solution: First, ask the operator to abort your observation. Then, ask the operator to look up which processes your turtle applications are running under, and kill -HUP the process IDs. Then, ssh to wind as monctrl and type RestartTurtle. Log out of wind, and you will be able to launch a new turtle application.

We went to access (perhaps to switch receivers) and now the antenna is slewing to a wierd location and/or complaining about illegal values.

The desired co-ordinate system (e.g. J2000) does not appear to get resent to the antenna if turtle/grail believes it is already known. If the Operator has moved the antenna to access using CLEO, they may have left the co-ordinate system as "Encoder". In this case, when the next observation is scheduled through turtle, the antenna may interpret a J2000 position as an (az,el) position, causing the antenna to attempt to slew to an unexpected position, or complain about an illegal value (e.g. if a -ve declination is interpreted as a -ve elevation). In this case, ask the operator to first slew to your target J2000 position, leaving the co-ordinate system as J2000. Then turtle should correctly recover.

Turtle seems to hang after a scan (e.g. Slew).

Solution: First, check on a status screen to make sure that there really are state transitions occurring in the control system. If there are, and the Turtle application is not picking them up, restart Grail on wind using TaskMaster. Close the turtle GUI. Log on to wind as monctrl. Type RestartTurtle. Log out of wind. Restart the turtle GUI and rerun your script.

Solution: First, check on a status screen to make sure that there really are state transitions occurring in the control system. If there are, and the Turtle application is not picking them up, close the turtle GUI. Log on to wind as monctrl. Type RestartTurtle. Log out of wind. Restart the turtle GUI and rerun your script. If the problem persists, restart Grail* on wind using TaskMaster and repeat this procedure.

Solution: Restart Grail on wind using TaskMaster. Close the turtle GUI. Log on to wind as monctrl. Type RestartTurtle. Log out of wind. Restart the turtle GUI and rerun your script.

Solution: Close the turtle GUI. Log on to wind as monctrl. Type RestartTurtle. Log out of wind. Restart the turtle GUI and rerun your script. If the problem persists, restart Grail* on wind using TaskMaster and repeat this procedure.

Solution: Restart Grail on wind using TaskMaster. Close the turtle GUI. Log on to wind as monctrl. Type RestartTurtle. Log out of wind. Restart the turtle GUI and rerun your script.

Solution: Close the turtle GUI. Log on to wind as monctrl. Type RestartTurtle. Log out of wind. Restart the turtle GUI and rerun your script. If the problem persists, restart Grail* on wind using TaskMaster and repeat this procedure.

*NOTE on restarting Grail: Please perform turtle recovery prior to restarting Grail, and then restart Grail only if the problem persists. When doing so, please log the results. This will allow the SDD to separate turtle issues from Grail issues.

Solution: Usually when this happens, you will be returned to the command prompt and no application will be launched. There are several reasons why this error may occur, including not having monctrl@vortex in the gateway, or not having write permissions in the directory you are trying to run from. You should see a message instructing you what to do to get turtle to start. If there are no messages, ssh to wind as monctrl. Once logged in, type RestartTurtle. Log out of wind. Restart the turtle GUI and your scheduling blocks should be runnable..

Solution: Usually when this happens, you will be returned to the command prompt and no application will be launched. There are several reasons why this error may occur, including not having write permissions in the directory you are trying to run from. You should see a message instructing you what to do to get turtle to start. If there are no messages, ssh to wind as monctrl. Once logged in, type RestartTurtle. Log out of wind. Restart the turtle GUI and your scheduling blocks should be runnable..

Solution: Right now, you need to set your source names manually. INSERT SETVALUES HERE

Solution: Right now, you need to set your source names manually. Add the following line to your turtle script as needed: SetValues("ScanCoordinator", {"source": "MySourceNameHere"})

Solution: First, check on a status screen to make sure that there really are state transitions occurring in the control system. If there are, and the Turtle application is not picking them up, restart Grail on vortex using TaskMaster. Close the turtle GUI. Log on to wind as monctrl. Type RestartTurtle. Log out of wind. Restart the turtle GUI and rerun your script.

Solution: First, check on a status screen to make sure that there really are state transitions occurring in the control system. If there are, and the Turtle application is not picking them up, restart Grail on wind using TaskMaster. Close the turtle GUI. Log on to wind as monctrl. Type RestartTurtle. Log out of wind. Restart the turtle GUI and rerun your script.

Solution: Restart Grail on vortex using TaskMaster. Close the turtle GUI. Log on to wind as monctrl. Type RestartTurtle. Log out of wind. Restart the turtle GUI and rerun your script.

Solution: Restart Grail on wind using TaskMaster. Close the turtle GUI. Log on to wind as monctrl. Type RestartTurtle. Log out of wind. Restart the turtle GUI and rerun your script.

Solution: Restart Grail on vortex using TaskMaster. Close the turtle GUI. Log on to wind as monctrl. Type RestartTurtle. Log out of wind. Restart the turtle GUI and rerun your script.

Solution: Restart Grail on wind using TaskMaster. Close the turtle GUI. Log on to wind as monctrl. Type RestartTurtle. Log out of wind. Restart the turtle GUI and rerun your script.

Problem: When doing a focus, my LFCs and Offsets are really huge - on the order of 20-80mm. What's wrong?*

Solution: It is required that you slew to your source before you attempt to focus. If you try to focus without first being on source, the telescope will try to focus at the last location stored in the antenna, which is probably not on your source. You will end up with LFCs that are extremely unreasonable and you will have little or no apparent signal in your data. For the rest of the details, go here.

Turtle Troubleshooting

Turtle Troubleshooting

Problem: I can't seem to get the Turtle GUI to start.

Problem: I can't seem to get the Turtle GUI to start.

Problem: My source name is not updating. What's wrong?

Problem: My source name is not updating. What's wrong?

Problem: I moved by Scheduling Block from the job queue to the run queue on the Run tab, and it won't disappear from the run queue and run on the telescope. What do I do?

Problem: I moved by Scheduling Block from the job queue to the run queue on the Run tab, and it won't disappear from the run queue and run on the telescope. What do I do?

Problem: I closed down the turtle application, and there is some rogue observation running - what do I do?

Problem: I closed down the turtle application, and there is some rogue observation running - what do I do?

Problem: I am not seeing state transistions (e.g. from "Activating" to "Ready or "Aborting") on the Turtle Monitor panel.

Problem: I am not seeing state transistions (e.g. from "Activating" to "Ready or "Aborting") on the Turtle Monitor panel.

Problem: When I check the status of the processes running under TaskMaster on wind, I see that turtle.d shows Failure.

Problem: When I check the status of the processes running under TaskMaster on wind, I see that turtle.d shows Failure.

Problem: I can't get fits for my pointing and focus scans and the antenna seems have weird values for H and V.

Problem: I can't get fits for my pointing and focus scans and the antenna seems have weird values for H and V.

Problem: Turtle seems to hang after a scan (e.g. Slew).

Problem: Turtle seems to hang after a scan (e.g. Slew).

Problem: I opened up more than one Turtle application and now none of them are operational, but my Scheduling Block is still running. What do I do?

Problem: I opened up more than one Turtle application and now none of them are operational, but my Scheduling Block is still running. What do I do?

-- AmyShelton - 29 Oct 2004

-- AmyShelton - 05 Nov 2004

%META:TOPICPARENT{name="ObservingAPIBetaExamples"}%

%META:TOPICPARENT{name="ObservingAPIExamples"}%

%META:TOPICMOVED{by="NicoleRadziwill" date="1099590152" from="Data.ObservingAPIBetaTroubleshooting" to="Software.ObservingToolsTroubleshooting"}%

Observing API Beta Examples

Turtle Troubleshooting

TOC: No TOC in "Software.ObservingToolsTroubleshooting"

Problem: I am not seeing state transistions on the Turtle Monitor panel.

Problem: I can't seem to get the Turtle GUI to start.

Solution: Restart Grail on vortex using TaskMaster. Close the turtle GUI. Log on to wind as monctrl. Type RestartTurtle. Log out of wind. Restart the turtle GUI and rerun your script.

Solution: Usually when this happens, you will be returned to the command prompt and no application will be launched. There are several reasons why this error may occur, including not having monctrl@vortex in the gateway, or not having write permissions in the directory you are trying to run from. You should see a message instructing you what to do to get turtle to start. If there are no messages, ssh to wind as monctrl. Once logged in, type RestartTurtle. Log out of wind. Restart the turtle GUI and your scheduling blocks should be runnable..

Problem: I can't seem to get the Turtle GUI to start.

Problem: My source name is not updating. What's wrong?

Solution: Close the turtle GUI. Log on to wind as monctrl. Type RestartTurtle. Log out of wind. Restart the turtle GUI and rerun your script.

Solution: Right now, you need to set your source names manually. INSERT SETVALUES HERE

Problem: When I check the status of the processes running under TaskMaster on wind, I see that turtle.d shows Failure.

Problem: I moved by Scheduling Block from the job queue to the run queue on the Run tab, and it won't disappear from the run queue and run on the telescope. What do I do?

Solution: If this happens, there has likely been a disruption in communications between turtle and the control system. First, remove the Scheduling Block from the run queue by highlighting the Scheduling Block name, and then clicking the Remove button. Then, exit the turtle application. Ask the operator to ssh to wind as monctrl, and RestartTurtle. You will then be able to restart the turtle application and resume your observation.

Problem: I closed down the turtle application, and there is some rogue observation running - what do I do?

Solution: If you have exited the turtle application after promoting a Scheduling Block from the job queue to the run queue, and then asked the operator to restart turtle, the telescope will proceed to run the last observation you tried to submit. The solution is simple: remove all Scheduling Blocks from the run queue before you close the Turtle application.

Problem: I am not seeing state transistions (e.g. from "Activating" to "Ready or "Aborting") on the Turtle Monitor panel.

Solution: First, check on a status screen to make sure that there really are state transitions occurring in the control system. If there are, and the Turtle application is not picking them up, restart Grail on vortex using TaskMaster. Close the turtle GUI. Log on to wind as monctrl. Type RestartTurtle. Log out of wind. Restart the turtle GUI and rerun your script.

Problem: When I check the status of the processes running under TaskMaster on wind, I see that turtle.d shows Failure.

Problem: I can't get fits for my pointing and focus scans and the antenna seems have weird values for H and V.

Problem: I can't get fits for my pointing and focus scans and the antenna seems have weird values for H and V.

Problem: Turtle seems to hang after a scan (e.g. Slew).

Problem: Turtle seems to hang after a scan (e.g. Slew).

Problem: I opened up more than one Turtle application and now none of them are operational, but my Scheduling Block is still running. What do I do?

Solution: First, ask the operator to abort your observation. Then, ask the operator to look up which processes your turtle applications are running under, and kill -HUP the process IDs. Then, ssh to wind as monctrl and type RestartTurtle. Log out of wind, and you will be able to launch a new turtle application.

Solution: Restart Grail on vortex using TaskMaster and then rerun your turtle script.

Solution: Restart Grail on vortex using TaskMaster. Close the turtle GUI. Log on to wind as monctrl. Type RestartTurtle. Log out of wind. Restart the turtle GUI and rerun your script.

Solution: Restart Grail on vortex using TaskMaster and then rerun your turtle script.

Solution: Restart Grail on vortex using TaskMaster. Close the turtle GUI. Log on to wind as monctrl. Type RestartTurtle. Log out of wind. Restart the turtle GUI and rerun your script.

Solution: Restart Grail on vortex using TaskMaster and then rerun your turtle script.

Solution: Restart Grail on vortex using TaskMaster. Close the turtle GUI. Log on to wind as monctrl. Type RestartTurtle. Log out of wind. Restart the turtle GUI and rerun your script.

-- AmyShelton - 27 Oct 2004

-- AmyShelton - 29 Oct 2004

Solution: Restart Grail on vortex using TaskMaster.

Solution: Restart Grail on vortex using TaskMaster and then rerun your turtle script.

Solution: Restart turtle.d on wind using TaskMaster. Then rerun turtle-test.

Solution: Close the turtle GUI. Log on to wind as monctrl. Type RestartTurtle. Log out of wind. Restart the turtle GUI and rerun your script.

Solution: Stop ns, es, and turtle.d on wind using TaskMaster. Restart ns, es, and turtle.d on wind using TaskMaster in that order.

Solution: Close the turtle GUI. Log on to wind as monctrl. Type RestartTurtle. Log out of wind. Restart the turtle GUI and rerun your script.

Solution: Restart Grail on vortex using TaskMaster.

Solution: Restart Grail on vortex using TaskMaster and then rerun your turtle script.

-- AmyShelton - 18 Jul 2004

Problem: Turtle seems to hang after a scan (e.g. Slew).

Solution: Restart Grail on vortex using TaskMaster and then rerun your turtle script.

-- AmyShelton - 27 Oct 2004

Solution: Restart ns, es, and turtle.d on wind using TaskMaster in that order.

Solution: Stop ns, es, and turtle.d on wind using TaskMaster. Restart ns, es, and turtle.d on wind using TaskMaster in that order.

-- AmyShelton - 13 Jul 2004

-- AmyShelton - 18 Jul 2004

Solution: Restart turtle.d on wind using TaskMaster.

Solution: Restart turtle.d on wind using TaskMaster. Then rerun turtle-test.

Solution: Restart ns and es on wind using TaskMaster in that order.

Solution: Restart ns, es, and turtle.d on wind using TaskMaster in that order.

Problem: I got the following message in the CLEO message window "ScanCoordinator received an (ignored) activate while in Stopping" and the system isn't running scans any more.

Solution: Press the Start button on the CLEO scan coordinator window.

Problem: I can't get fits for my pointing and focus scans and the antenna seems have wierd values for H and V.

Problem: I can't get fits for my pointing and focus scans and the antenna seems have weird values for H and V.

-- AmyShelton - 09 Jul 2004

-- AmyShelton - 13 Jul 2004

Problem: I can't get fits for my pointing and focus scans and the antenna seems have wierd values for H and V.

Solution: Restart Grail on vortex using TaskMaster.

Problem: I got the following message in the CLEO message window "ScanCoordinator received an (ignored) activate while in Stopping" and the system isn't running scans any more.

Solution: Press the Start button on the CLEO scan coordinator window.

%META:TOPICINFO{author="AmyShelton" date="1089400032" format="1.0" version="1.1"}% %META:TOPICPARENT{name="ObservingAPIBetaExamples"}%

Observing API Beta Examples

Problem: I am not seeing state transistions on the Turtle Monitor panel.

Solution: Restart Grail on vortex using TaskMaster.

Problem: I can't seem to get the Turtle GUI to start.

Solution: Restart turtle.d on wind using TaskMaster.

Problem: When I check the status of the processes running under TaskMaster on wind, I see that turtle.d shows Failure.

Solution: Restart ns and es on wind using TaskMaster in that order.

-- AmyShelton - 09 Jul 2004