KNOWN ISSUES EDGCM VERSION: 4.0.

x

KNOWN ISSUES AND BUGS

1. Old versions of EdGCM MUST BE REMOVED from your computer before installing EdGCM 4.0.
If you have simulations to transfer from your old copy of EdGCM to EdGCM 4.0 please follow
the upgrade instructions on page 2 of this document before installing EdGCM 4.0. Launching
EdGCM 4.0 before removing old versions will corrupt the database.
2. When a run is selected in the Toolbars run list before the Setup Simulations window is opened
the data in the Setup Simulations window is not synced correctly. After opening Setup
Simulations always choose the desired run in the Toolbar to sync the form.
3. The play button on the toolbar is sometimes non-responsive. If this occurs, select a different run
in the run list, switch back to the desired run, and try again. If this fails, quitting EdGCM and
restarting usually fixes the problem.
4. In the Go menu, choosing Go > EdGCM 4D Folder opens the wrong folder IF you have placed
an alias of EVA in the EdGCM folder.
5. The Permissions and Cleanup functions have not been tested in EdGCM 4.0 yet.
6. The vector length in EVA-produced maps is not a function of cell size.

IMPORTANT: USING EDGCM 4.0 FOR THE FIRST TIME MAY INVOKE SECURITY WARNINGS

6. The first time you use each feature in EdGCM 4.0 (click any buttons in the Toolbar, Setup
Simulations, Analyze Output, EVA, etc.) there may be a delay that lasts up to 45 seconds before
an action occurs. This is because many buttons in EdGCM launch secondary applications that
run in the background. When programs are started for the first time on a Mac the operating
system brings up a security warning, usually something like: This is an application that was
downloaded from the internet. Are you sure you want to start it? For an unknown reason, many
of the programs used by EdGCM are taking 30-60 seconds to bring up this warning message.
Therefore, it may seem like nothing is happening after youve clicked a button. BE PATIENT and
wait to see if the security warning eventually comes up. If nothing happens after 60 seconds you
may need to try to quit and restart EdGCM. After each function of EdGCM has been used once,
and you have approved their use by clicking OK on the security warning, all features of EdGCM
should operate without warnings or delays.

UPGRADING FROM A PREVIOUS COPY OF EDGCM: INSTRUCTIONS

See page 2

CONTACTS:
Mark Chandler, mac59@columbia.edu
Linda Sohl, les14@columbia.edu
Jian Zhou, jz2455@tc.columbia.edu

KNOWN ISSUES EDGCM VERSION: 4.0.x

UPGRADING FROM AN OLDER VERSION OF EDGCM:

These steps are only necessary if you want to transfer simulations that you have previously run from
an old version of EdGCM. . If you have no simulations to transfer, simply delete the old EdGCM
folder before installing EdGCM 4.0.

1. Open your previous copy of EdGCM.

2. From the Window menu select Simulation Library and in the window that opens select a run
you want to transfer from the list (each run must be moved individually sorry!).
3. Click on the "Export" button at the bottom of the window and choose a name and location to
save the file.
4. Repeat steps 2 & 3 for each simulation you want to transfer.
5. Quit the old version of EdGCM.
6. Next move all of the desired run folders from the EdGCM/Output folder to another outside of
the EdGCM folder (the Desktop works fine). Note: if you want to transfer all the runs from your
old copy of EdGCM you can simply move the entire Output folder to the Desktop.
7. Now you can safely delete the old EdGCM folder.
8. Install the new version of EdGCM 4.0.
9. Open EdGCM 4.0 for the first time (double-click the EdGCM 4.0 alias in the EdGCM folder or
double-click the file EdGCM.4DB in the EdGCM:Database folder. If you have purchased a
license key, please enter it in the Registration window when asked; otherwise, continue in
demo mode.
10. Open the Simulation Library window from the Window menu.
11. Click the Import button at the bottom of the window and use the Open dialog box to choose the
.xml file that you wish to import.
12. A dialog box will appear identifying the run you are importing and, critically, whether or not it
is a duplicate of an existing run (which would then be overwritten if you choose to continue
with import). If you wish to continue, click the Import button.

CONTACTS:
Mark Chandler, mac59@columbia.edu
Linda Sohl, les14@columbia.edu
Jian Zhou, jz2455@tc.columbia.edu