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.
Michael, Great! Glad to help. Best, Unidata IDV Support > I never thought to look at the hidden directories! I should know > better! Not only that, but I never thought to look for a .unidata > directory. > > And what-do-you-know; there it is! Our assumptions are usually the > poison pill of our misunderstanding! > > Got it! I wish I had thought of a ".unidata" directory. > > Thanks again. > > Michael > > > On Thu, 2014-01-16 at 13:21 -0700, Unidata IDV Support wrote: > > Michael, > > > > I think there may be some confusion about where the > > ~/.unidata/idv/DefaultIdv is located. The ~ character denotes your > > home directory (e.g., on linux /home/joeblow). Some IDV resources are > > kept in the .unidata directory in your home directory. Note it is a > > dot (or hidden) directory. Do an "ls -a" to see this hidden directory > > in your home directory. Once again if you follow these instructions > > exactly, and restart the IDV it should all work. > > > > cd ~/.unidata/idv/DefaultIdv > > wget https://www.rsmas.miami.edu/users/bmapes/pagestuff/idv.properties > > wget https://www.rsmas.miami.edu/users/bmapes/pagestuff/mapes.rbi > > > > Hopefully, I am not missing something obvious. > > > > Best Wishes, > > > > Unidata IDV Support > > > > > > > > > Hmmm. I think I see the problem. The installation does not include an > > > "idv.properties" file in the directory. Yet the Users Guide covered in > > > the tutorial (chapter 5.2.0) has a rather extensive "idv.properties" > > > file. > > > > > > My directory structure is /root/IDV_4.1/*.* but no /default file. > > > > > > So apparently my installation structure must be wrong. Mapes places > > > these two files in the /default directory. The first step is to remove > > > 4_1, reinstall it, then try again. > > > > > > Does that sound correct? Of course, the next question is, "Why did the > > > installation backfire?" I used the Linux installer (just as I have all > > > the other times.) > > > > > > Any suggestions? > > > > > > Michael > > > > > > On Thu, 2014-01-16 at 10:09 -0700, Unidata IDV Support wrote: > > > > Michael, > > > > > > > > Here is what I did: > > > > > > > > cd ~/.unidata/idv/DefaultIdv > > > > wget https://www.rsmas.miami.edu/users/bmapes/pagestuff/idv.properties > > > > wget https://www.rsmas.miami.edu/users/bmapes/pagestuff/mapes.rbi > > > > > > > > After I ran these commands and started the IDV, I could see the Mapes > > > > IDV collection without any difficulties in the IDV. Is that not what > > > > you are seeing? Remember, you have to restart the IDV to see the Mapes > > > > IDV collection. > > > > > > > > Best Wishes, > > > > > > > > Unidata IDV Support > > > > > > > > > I must admit I tried all of the methods noted on Brian Mapes' site > > > > > after > > > > > watching the videos. They look exciting but try as I might I could > > > > > not get them to show in my copy of IDV 4.1. I'm running a CentOS 5.9 > > > > > Linux parallel computer system, 6 Gb in each machine (only one has IDV > > > > > 4.1 installed), the hard drive system on each box is just over 1 Tb. > > > > > The IDV runs very well otherwise. > > > > > > > > > > In addition, I have used the IDV since 1.1 or some very early version > > > > > and regularly update it when they become available. > > > > > > > > > > Any suggestions? > > > > > > > > > > Michael Allen > > > > > Industrial Weather > > > > > 15248 40th Avenue North > > > > > Plymouth, MN 55446 (suburb of Minneapolis) > > > > > > > > > > E-mails: address@hidden > > > > > address@hidden > > > > > mobile: 763-245-1903 > > > > > > > > > > > > > > > > > > > > > > Ticket Details > > > > =================== > > > > Ticket ID: YUL-618483 > > > > Department: Support IDV > > > > Priority: Normal > > > > Status: Closed > > > > > > > > > > > > > > > > > > > > Ticket Details > > =================== > > Ticket ID: YUL-618483 > > Department: Support IDV > > Priority: Normal > > Status: Closed > > > > > > Ticket Details =================== Ticket ID: YUL-618483 Department: Support IDV Priority: Normal Status: Closed