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.
Hi Paul, re: check for misplaced files (e.g., FrameN.M, etc.) > I did as you requested and still have the same problem. Hmm... re: > If I were to use the keywords EU=BREF rather than EU=DREF everything works > fine (except I am using an odd enhancement.) Question: - did you install the new enhancements included in the Unidata McIDAS addendum? Installing means that they get either linked or copied from the source directory (~mcidas/mcidas2009/data) to the installation directory (~mcidas/data). If DREF.ET is not located in any directory in your MCPATH, it will not be usable. BREF.ET is evidently in a directory in your MCPATH (should be in ~mcidas/data), and so it is usable. If you did not install the addendum updates, you will need to run the installation 'make' invocations: <as 'mcidas'> cd ~mcidas/mcidas2009/src make install.bin install.data Better yet: cd ~mcidas/mcidas2009/src make install.all Cheers, Tom -- **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: BLE-176037 Department: Support McIDAS Priority: Normal Status: Closed