Back - FAQ Home

---

• My windows freeze when running a simulation
• D2D hangs with "waiting for main pane to initialize message"
• My data does not update
• My green times do not update
• My procedures do not display the data from the time I expected.

• My windows freeze when running a simulation? [top]

This is a common problem when using KDE as your desktop. Try running Gnome to eliminate this problem.

If you prefer to use KDE, there is a workaround for this behavior. You can get your windows to unfreeze by issuing the following commands at a shell prompt:

kde-reset

• D2D hangs with "waiting for main pane to initialize message"[top]

The problem is related to your local networking and machine name. Make sure that your /etc/hosts file is configured correctly or you are properly getting the IP and hostname information from another source.

• My data does not update [top]

Three different conditions can cause this behavior with D2D and WES.

1. Make sure you entered in the correct date and time in the simulation set up (this is very common, especially for evening events). If this date and time information is not correct, then WES will not make the correct data available to D2D to display.

2. Make sure that the D2D is not frozen. To do this, make sure "Use current real time" is selected after double-clicking on the D2D clock. When the D2D clock is frozen, it appears yellow in the lower right hand corner of the D2D display.

3. Make sure you have an up to date localization that matches the version with WES for your case. Usually re-localizing will solve this problem.

• My green times do not update [top]

Green times are registered by the notificationServer during a simulation. If you are looking at a case in d2d without running a simulation (i.e., only using start_awips without start_simulator), the green times do not exist because the notificationServer doesn't run unless the start_simulator or enhanced_case_review programs run. This isn't a problem, since the data can still be accessed by loading the products. Different products can be loaded at different times by using the freeze time option under Options-->Set Time, and entering in the time you want the loop to load to. Note that if you are running a simulation and you have the "Freeze time" mode enabled for static viewing (the D2D clock turns yellow), then loops may not update.

• My procedures do not display the data from the time I expected.[top]

Verify that this is your problem by comparing your procedure with raw data. Do this by loading the procedure in one D2D frame and loading similar data directly from a menu in another frame. If the data times do not agre, this answer may address your problem.

Unexpected data displays can result depending on when and how the procedure was created. In particular, the behavior depends on whether or not the D2D clock was set to a frozen time or not. When the time is frozen, the D2D clock is yellow.

When created, the procedure embeds within itself which clock setting was in effect. Thus, if the clock was frozen at a particular time when the procedure was created, the procedure will only show data from that time ... and only if that data has been made visible by the WES.

If the procedure was made when the clock was not frozen, D2D always displays the latest data currently available, even if the time is frozen when the procedure is used.