Known issues

1. Launching a normalization job with the same conditions as a normalization fileset that is already in the norm fileset database does not work well. The job will run, but it does not create a new entry in the normalization fileset database. The normalization fileset that is already in the database must be deleted first.

2. When launching the offline GUI from the command line, run the process in the foreground. Do not run it with an ampersand (&). If the npctOfflineGui command is run in the background, the GUI will hang when a job is added to the batch system.

3. The GUI will not prevent the user from doing the following: Add a job to the batch system. While the job is queued up or running, go to the patient browser and delete the series associated with the job. Doing this will prevent the job from running successfully and can leave the GUI in an unknown state. If this happens, kill and restart the GUI to get back to a known good state.

4. Frames editor: When attempting to save a frames file for future use, a pop-up save dialog will open. If the user clicks on the frames editor dialog box prior to saving the frames file, the GUI can get into a funny state and the save dialog can become unresponsive. The way out of this is to close the frames editor dialog and then to close the save dialog.

5. On the data transfer panel the user must enter the password for the remote system once after restarting the GUI. If the password is entered incorrectly, two dialog boxes will open. The first will be titled ``OpenSSH'' and prompts the user to reenter the password. Do not enter the password and click the ``Cancel'' button. The second dialog box is a message window. Close this window.

   The user will be prompted for the password again the next time the ``Check for data'' button is clicked.