[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20000418: Hodo command in McIdas messes up map drawing (fix)

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: 20000418: Hodo command in McIdas messes up map drawing (fix)
  • Date: Tue, 18 Apr 2000 11:40:03 -0600
>From: Gilbert Sebenste <address@hidden>
>Organization: NIU
>Keywords: 200004141903.NAA13692 McIDAS-X 7.60 HODO BATCH

Gilbert,

>Found a bug, I believe, in the HODO program.

I found the cause of the bug and fixed it.  I then quickly added the
fix to the McIDAS addendum that I have been working on for the past
several days.

The problem was in the program SNDHODO (HODO runs SNDHODO):  the
program was saving zero values into the User Common locations used to
store graphic line information (dash pattern lengths, line widths,
etc.).  The writing of zero values to these locations only occurred
when SNDHODO processed a sounding that hand no (or too little) wind
information.  In this case, the program was writing values from
internal variables that had not yet been initialized with valid values
from User Common.  The change was a simple addition of logic to see
whether or not UC values had been saved upon program startup.  If they
had, then they are restored on exit.  If they hadn't, there is no
reason to restore them, so the code doing this is skipped.

I just announced the availability of the latest McIDAS addendum that
contains the fix for SNDHODO.  Please let me know if you have any
questions.

Tom