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

[AWIPS #CRU-314958]: CAVE Install Issue

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: [AWIPS #CRU-314958]: CAVE Install Issue
  • Date: Thu, 29 Jul 2021 09:47:41 -0600
Hi there,

> I am attempting to follow the instructions as shown in the following URL:
> http://unidata.github.io/awips2/install/install-cave/#method-2-direct-windows-install

> I am stuck on step 5 of Method 2: Direct Windows Install. When I enter "pip
> install numpy==1.15.1" or "pip install jep==3.8.2" I receive the following
> error:[see attached]

> I have found the lines mentioned in the errors; however, I am not aware of
> what to do after that point. Do you have any suggestions on how to fix
> this? The only discrepancy that I can find between what I am doing and the
> instructions is that I am using v16.9.9 Visual Studio 2019. I do not know
> how to force v16.9.6 like in the instructional video -- or if that would
> even fix this issue.

I'm sorry the installation is giving you problems.  When you installed the 
Visual
Studios Build Tools, did you still scroll to the bottom, in the right hand 
panel,
and select the VS 2015 C++ build tools package?

Thanks.

--Shay Carter

She/Her/Hers
AWIPS Software Engineer
UCAR - Unidata

If you're interested, please feel free to fill out a survey about the support 
you receive: 
https://docs.google.com/forms/d/e/1FAIpQLSeDIkdk8qUMgq8ZdM4jhP-ubJPUOr-mJMQgxInwoAWoV5QcOw/viewform

Ticket Details
===================
Ticket ID: CRU-314958
Department: Support AWIPS
Priority: Normal
Status: Open
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.