Triage for Orbit Planner problems
---------------------------------

1) OP Fails without feedback/hangs/doesn't run.

a) Could try recycling APT if it used to work.

b) Find out what platform they are running on:

If linux laptop and they are away from their home institution,
it could be the hard coded host name in the /etc/sysconfig/network file.
Have them try getting rid of all but the machine name while they are away.
(This ones fails getting the Trans version and you can see the problem
in the IOR file.)

If Mac G5 find another machine. (Maxes CPU and never finishes.)
(This is most likely no longer a problem.)

If RH9, Fedora, SuSe9, or RH Enterprise suggest: 
      env LD_ASSUME_KERNEL=2.2.5 ./APT
(This is no longer a problem starting with APT 14.0)

c) Other things to check:

Site installation? Could be network delays. Try reinstalling locally.

Moved home directory recently? Try removing ~/.OrbitPlanner.


If none of that works, request APT's debug output as well as asking 
for Trans output (with file write date stamp):

 ~/.OrbitPlanner/transOutput.log
 ~/.OrbitPlanner/optrans.ior
 
2) Pop up that tells you to restart APT.

Restart APT. :)

3) Pop up that tells you to check the validity of
the proposal.

(This is a failure in the Trans Search.) 

If there are not any diagnostics to fix, try
refreshing Trans (or close and reopen proposal). 

If that doesn't clear things up, get a copy of the proposal.

4) Diagnostic about failure.

(This is a failure in the Trans COSI propagation.)

Could refresh Trans (or close and reopen proposal).
Get the diagnostic and a copy of the proposal.


How to collect the debug:
-------------------------

  - Edit the file runAPT.lax 
     (this file is in the directory where you installed APT)

   - Change the lines:

	lax.stderr.redirect=
   		to
	lax.stderr.redirect=apt.err
  		and
	lax.stdout.redirect=
   		to
	lax.stdout.redirect=apt.out

   - Save the file.

   - Rerun APT and recreate the problem.

   - Mail me the apt.err and apt.out files that you will find
     in the installation directory directly to me (not to help desk)

Note that you cannot do this with a site installation because you
can't edit the lax file. In that case you have to:

   -  Figure out what shell you are using.

      echo $SHELL

   -  Set the LAX_DEBUG environment variable to true.

      If your shell is tcsh or csh then:

      setenv LAX_DEBUG true

      otherwise:

      LAX_DEBUG=true
      export LAX_DEBUG

   -  Rerun APT and recreate the problem.

   -  Cut and paste the debug from the screen into an e-mail
      and send it directly to me (no to help desk)
      
      
On the Mac you go to Applications/Utilities/console to get the console
log and while in console if you click:  File/Open/ you can look for any
crash logs too. Send them directly to me (not to help desk)