I'm not sure I know what you mean by that. How do I run python and import bumpy? I apologize for my command line naivety.
Nic On Jan 14, 2015 9:10 AM, "Michael Joyce" <jo...@apache.org> wrote: > And if you run python and import numpy it does or doesn't fail? If it's > pointing to the Anaconda python when you ran the other command I'm not > really sure why it would fail on a numpy import =/ > > > -- Joyce > > On Wed, Jan 14, 2015 at 8:57 AM, nicpeder...@gmail.com < > nicpeder...@gmail.com> wrote: > >> Output of which python is >> >> /home/nic/climate/anaconda/bin//python >> >> >> Sent from my HTC phone. >> >> ----- Reply message ----- >> From: "Michael Joyce" <jo...@apache.org> >> To: "nic pederson" <nicpeder...@gmail.com> >> Cc: "dev@climate.apache.org" <dev@climate.apache.org>, " >> chris.a.mattm...@nasa.gov" <chris.a.mattm...@nasa.gov> >> Subject: New Student - Caltech-JPL Summer School on Big Data Analytics - >> Need Help Setting up OCW >> Date: Wed, Jan 14, 2015 8:47 AM >> >> Ok the second one leads me to believe that the wrong Python is getting >> used. Can you check that 'python' really is the anaconda python where numpy >> would be installed? Namely, what is the output of `which python` and can >> you manually run python and import numpy without an error? >> >> >> -- Joyce >> >> On Wed, Jan 14, 2015 at 8:39 AM, nic pederson <nicpeder...@gmail.com> >> wrote: >> >>> It didn't seem to like it. I also tried with sudo since it gave >>> permission errors. >>> >>> pastebin.com/LDbpgvWu >>> On Jan 14, 2015 8:29 AM, "Michael Joyce" <jo...@apache.org> wrote: >>> >>>> No it shouldn't matter where it's at. Was mostly just guessing where it >>>> might be off the top of my head to be honest =) >>>> >>>> >>>> -- Joyce >>>> >>>> On Wed, Jan 14, 2015 at 8:26 AM, nicpeder...@gmail.com < >>>> nicpeder...@gmail.com> wrote: >>>> >>>>> The basemap folder is in my home directory. Should I move it first? >>>>> >>>>> Nic >>>>> >>>>> Sent from my HTC phone. >>>>> >>>>> ----- Reply message ----- >>>>> From: "Michael Joyce" <jo...@apache.org> >>>>> To: "nicpeder...@gmail.com" <nicpeder...@gmail.com> >>>>> Cc: "dev@climate.apache.org" <dev@climate.apache.org>, " >>>>> chris.a.mattm...@nasa.gov" <chris.a.mattm...@nasa.gov> >>>>> Subject: New Student - Caltech-JPL Summer School on Big Data Analytics >>>>> - Need Help Setting up OCW >>>>> Date: Wed, Jan 14, 2015 6:47 AM >>>>> >>>>> Ok, that looks good. GEOS seems to have installed fine. >>>>> >>>>> If you go back into the directory where the install script downloaded >>>>> basemap we can try to do the install again. >>>>> It should be something like /path/to/climate/easy-ocw/basemap-1.0.7 >>>>> >>>>> Then using the Anaconda Python (be sure to check and make sure it's >>>>> not the system Python or the virtualenv Python with `which python`) run: >>>>> python setup.py install >>>>> >>>>> Then try the above basemap import to check the install. Go ahead and >>>>> post the install output here as well in case we need to debug something. >>>>> >>>>> >>>>> >>>>> -- Joyce >>>>> >>>>> On Tue, Jan 13, 2015 at 2:36 PM, nicpeder...@gmail.com < >>>>> nicpeder...@gmail.com> wrote: >>>>> >>>>>> Basemap test - output. >>>>>> >>>>>> pastebin.com/rrAzxHMu >>>>>> >>>>>> Nic >>>>>> >>>>>> >>>>>> >>>>>> ----- Reply message ----- >>>>>> From: "Michael Joyce" <jo...@apache.org> >>>>>> To: "nic pederson" <nicpeder...@gmail.com> >>>>>> Cc: "dev@climate.apache.org" <dev@climate.apache.org>, " >>>>>> chris.a.mattm...@nasa.gov" <chris.a.mattm...@nasa.gov> >>>>>> Subject: New Student - Caltech-JPL Summer School on Big Data >>>>>> Analytics - Need Help Setting up OCW >>>>>> Date: Tue, Jan 13, 2015 1:04 PM >>>>>> >>>>>> So, semi-good news is that you're helping me find some small bugs in >>>>>> the install script but unfortunately they're not what's causing your >>>>>> problem =) >>>>>> >>>>>> However, I also realized that I told you something wrong earlier. I >>>>>> told you to run >>>>>> >>>>>> sudo echo "export PATH=\"/home/nic/climate/anaconda/bin/:$PATH\"" >> >>>>>> ocw/bin/activate >>>>>> >>>>>> but that isn't going to do what we want. We're running the echo >>>>>> command with elevated privileges but we really want to do the concat with >>>>>> elevated perms. >>>>>> >>>>>> echo "export PATH=\"/home/nic/climate/anaconda/bin/:$PATH\"" | sudo >>>>>> tee ocw/bin/activate >>>>>> >>>>>> You could also put quotes around the original command I gave you >>>>>> (sudo " ... ") but that can get messy with the other quotes for the echo. >>>>>> You could also edit the file manually with nano (assuming it's installed) >>>>>> with `sudo nano /path/to/file`. But try the above and hopefully that'll >>>>>> work for you. >>>>>> >>>>>> Now, we have hopefully fixed the first issue but not the second >>>>>> issue. >>>>>> >>>>>> If it can't find basemap that means that the installation for it died >>>>>> somewhere. Unfortunately the install_log isn't helping (one of those >>>>>> bugs I >>>>>> mentioned) so we might need to debug manually. First thing to test is >>>>>> that >>>>>> basemap really can't be found and it's not a bug in the script. >>>>>> >>>>>> Try the following in a Python prompt: >>>>>> from mpl_toolkits.basemap import Basemap >>>>>> >>>>>> This is the test they use in the actual basemap docs to test an >>>>>> install. So if that doesn't work then basemap definitely isn't installed >>>>>> and it wasn't a problem with the *.py script you ran to test OCW. >>>>>> >>>>>> If the above failed, let's check to see if Geos got installed. Geos >>>>>> is a dependency for basemap that the install script handles first. Run >>>>>> the >>>>>> following >>>>>> >>>>>> ls /usr/local/lib | grep geos >>>>>> >>>>>> You should see some output. If you didn't then we need to install >>>>>> Geos manually. Luckily we can mostly just copy the install script >>>>>> verbatim >>>>>> and see if something breaks. There's a section in the install-ubuntu.sh >>>>>> script with a comment that says "#Install GEOS" that has the commands. >>>>>> Otherwise we need to run the next part for basemap. However, before you >>>>>> do >>>>>> either of those installs, let me know what the outputs from the above >>>>>> commands say and let me know if the new attempt at appending text works. >>>>>> >>>>>> We will get there eventually, stick with it =) >>>>>> >>>>>> >>>>>> >>>>>> -- Joyce >>>>>> >>>>>> On Tue, Jan 13, 2015 at 12:36 PM, nic pederson <nicpeder...@gmail.com >>>>>> > wrote: >>>>>> >>>>>>> It did seem to band aid that part, but now it can't find baseman. >>>>>>> Here's the terminal. >>>>>>> >>>>>>> pastebin.com/BSgt7BwW >>>>>>> >>>>>>> Nic >>>>>>> On Jan 13, 2015 12:07 PM, "Michael Joyce" <jo...@apache.org> wrote: >>>>>>> >>>>>>>> One more thing to try (and I suspect it would band-aid the problem): >>>>>>>> >>>>>>>> Start up the virtualenv, run the following command, and see if you >>>>>>>> can find the packages now. >>>>>>>> >>>>>>>> export PATH="/home/nic/climate/anaconda/bin/:$PATH" >>>>>>>> >>>>>>>> That's effectively what we're trying to get it to do by editing the >>>>>>>> script, but it's not cooperating with us. That should make it work, >>>>>>>> but you >>>>>>>> would have to do it every time you start up the environment which is >>>>>>>> terribly tedious. It also doesn't address the actual problem and that >>>>>>>> annoys me =D >>>>>>>> >>>>>>>> >>>>>>>> -- Joyce >>>>>>>> >>>>>>>> On Tue, Jan 13, 2015 at 12:02 PM, Michael Joyce <jo...@apache.org> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Hrm ok. That's even more strange. >>>>>>>>> >>>>>>>>> So the -e flag tells the script that you want it to install >>>>>>>>> virtualenv (if necessary), make a new virtualenv named 'ocw', and >>>>>>>>> install >>>>>>>>> some of the dependencies into there (namely the dependencies not >>>>>>>>> installed >>>>>>>>> by Anaconda). If you didn't pass this flag, it will have installed the >>>>>>>>> dependencies into your system python. From what I can tell you >>>>>>>>> probably did >>>>>>>>> pass this flag? It doesn't really matter, or at least shouldn't. It's >>>>>>>>> generally a good idea to not pollute the system Python as it can make >>>>>>>>> your >>>>>>>>> life a bit more difficult in the future when dealing with other Python >>>>>>>>> dependencies/packages. >>>>>>>>> >>>>>>>>> There's an install log that gets written when running the script. >>>>>>>>> Can you look for a file called "install_log" in the climate/easy-ocw/ >>>>>>>>> folder and post the output? That will help us debug this whenever I >>>>>>>>> find a >>>>>>>>> few spare minutes to take a look. >>>>>>>>> >>>>>>>>> >>>>>>>>> -- Joyce >>>>>>>>> >>>>>>>>> On Tue, Jan 13, 2015 at 11:28 AM, nic pederson < >>>>>>>>> nicpeder...@gmail.com> wrote: >>>>>>>>> >>>>>>>>>> Here's a link to what happens in terminal when I try that >>>>>>>>>> command... It doesn't ask for a password >>>>>>>>>> >>>>>>>>>> pastebin.com/hcMNqWAa >>>>>>>>>> >>>>>>>>>> Also, when I'm installing ocw originally, am I supposed to use >>>>>>>>>> the -e tag at the end of the command that executes the installation? >>>>>>>>>> Would >>>>>>>>>> that potentially cause these errors? >>>>>>>>>> >>>>>>>>>> Nic >>>>>>>>>> On Jan 13, 2015 10:51 AM, "Michael Joyce" <jo...@apache.org> >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> @Carl, absolutely. Once I figure out when I'll have some time >>>>>>>>>>> for a meeting I'll send out an email here so anyone can >>>>>>>>>>> participate. Always >>>>>>>>>>> happy to have more people stop by. >>>>>>>>>>> >>>>>>>>>>> @Nic The odd thing about what I'm seeing is that all the files >>>>>>>>>>> for virtualenv are owned by root. Perhaps even more strange is that >>>>>>>>>>> even if >>>>>>>>>>> that is the case, running `echo "export PATH=\" >>>>>>>>>>> /home/nic/climate/anaconda/bin/:$PATH\"" >> ocw/bin/activate` >>>>>>>>>>> (without the `'s of course) should work just fine. Is it possible >>>>>>>>>>> that the >>>>>>>>>>> password you typed for sudo was incorrect? >>>>>>>>>>> >>>>>>>>>>> @Both of you, something that may help you get up and running >>>>>>>>>>> potentially faster would be to use the VM. We have instructions on >>>>>>>>>>> how to >>>>>>>>>>> build the VM for you on our wiki. Consider checking that out at [1] >>>>>>>>>>> as well >>>>>>>>>>> while we try to figure out this problem, especially if getting >>>>>>>>>>> something up >>>>>>>>>>> and running urgently is key. >>>>>>>>>>> >>>>>>>>>>> [1] >>>>>>>>>>> https://cwiki.apache.org/confluence/display/CLIMATE/OCW+VM+-+A+Self+Contained+OCW+Environment >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- Joyce >>>>>>>>>>> >>>>>>>>>>> On Tue, Jan 13, 2015 at 9:00 AM, nicpeder...@gmail.com < >>>>>>>>>>> nicpeder...@gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> I'm with you on it being weird. Ok. Here's a link to that output >>>>>>>>>>>> >>>>>>>>>>>> pastebin.com/rA4P7eCh >>>>>>>>>>>> >>>>>>>>>>>> I'm not working on a VM. And the network is my own. >>>>>>>>>>>> >>>>>>>>>>>> Thanks, >>>>>>>>>>>> Nic >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Sent from my HTC phone. >>>>>>>>>>>> >>>>>>>>>>>> ----- Reply message ----- >>>>>>>>>>>> From: "Michael Joyce" <jo...@apache.org> >>>>>>>>>>>> To: "nic pederson" <nicpeder...@gmail.com> >>>>>>>>>>>> Cc: "chris.a.mattm...@nasa.gov" <chris.a.mattm...@nasa.gov>, " >>>>>>>>>>>> dev@climate.apache.org" <dev@climate.apache.org> >>>>>>>>>>>> Subject: New Student - Caltech-JPL Summer School on Big Data >>>>>>>>>>>> Analytics - Need Help Setting up OCW >>>>>>>>>>>> Date: Tue, Jan 13, 2015 7:34 AM >>>>>>>>>>>> >>>>>>>>>>>> More than happy to do a google hangout or something similar to >>>>>>>>>>>> try to resolve any issues you're having. Today is jam packed for me >>>>>>>>>>>> unfortunately so it would have to be a different day. Perhaps >>>>>>>>>>>> someone else >>>>>>>>>>>> will be able to help though. >>>>>>>>>>>> >>>>>>>>>>>> I find it odd that you're running into permission problems >>>>>>>>>>>> here. Are you running this in a VM or on a local system that you >>>>>>>>>>>> have >>>>>>>>>>>> control off? I'm not really sure why you wouldn't be able to edit >>>>>>>>>>>> something >>>>>>>>>>>> in your home dir unless root wrote something. Can you run "ls -l" >>>>>>>>>>>> on the >>>>>>>>>>>> ocw/bin directory and link the output? >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- Joyce >>>>>>>>>>>> >>>>>>>>>>>> On Mon, Jan 12, 2015 at 10:07 PM, nic pederson < >>>>>>>>>>>> nicpeder...@gmail.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Can we do a team viewer or some other remote control? I am >>>>>>>>>>>>> feeling a little deflated. >>>>>>>>>>>>> >>>>>>>>>>>>> N >>>>>>>>>>>>> On Jan 12, 2015 9:07 PM, "nic pederson" <nicpeder...@gmail.com> >>>>>>>>>>>>> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> When I run it from the easy-ocw folder, is says permission >>>>>>>>>>>>>> denied. When I run it with sudo, it says the same thing... >>>>>>>>>>>>>> On Jan 12, 2015 8:51 PM, "nic pederson" < >>>>>>>>>>>>>> nicpeder...@gmail.com> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> It returns: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> bash: ocw/bin/activate: No such file or directory >>>>>>>>>>>>>>> On Jan 12, 2015 8:35 PM, "Michael Joyce" <jo...@apache.org> >>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Try running the above command instead of using gedit. If it >>>>>>>>>>>>>>>> gives you permission denied try prepending "sudo " to the >>>>>>>>>>>>>>>> command and >>>>>>>>>>>>>>>> typing your admin password when prompted. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> -- Joyce >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Mon, Jan 12, 2015 at 8:23 PM, nic pederson < >>>>>>>>>>>>>>>> nicpeder...@gmail.com> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Ok. Opened it in gedit. Added the line to the end, but it >>>>>>>>>>>>>>>>> won't let me save. Says it's read only >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> N >>>>>>>>>>>>>>>>> On Jan 12, 2015 8:14 PM, "Michael Joyce" <jo...@apache.org> >>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> You could use an editor such as nano (not sure if this >>>>>>>>>>>>>>>>>> would be installed), emacs or vim (both of which would be >>>>>>>>>>>>>>>>>> potentially >>>>>>>>>>>>>>>>>> challenging for you to use most likely). >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> You should be able to run the following. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> echo "export PATH=\"/home/nic/climate/anaconda/bin/:$PATH\"" >>>>>>>>>>>>>>>>>> >> ocw/bin/activate >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> ">>" redirects input to the supplied output file. In this >>>>>>>>>>>>>>>>>> case the input is the result of running >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> echo "export PATH=\"/home/nic/climate/ >>>>>>>>>>>>>>>>>> anaconda/bin/:$PATH\"" >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> which is simply >>>>>>>>>>>>>>>>>> export PATH="/home/nic/climate/anaconda/bin/:$PATH" >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> And the output file is the activate script that we want >>>>>>>>>>>>>>>>>> to adjust. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Hopefully that helps a bit. If it doesn't work let me >>>>>>>>>>>>>>>>>> know. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> -- Joyce >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> On Mon, Jan 12, 2015 at 8:09 PM, nic pederson < >>>>>>>>>>>>>>>>>> nicpeder...@gmail.com> wrote: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> I didn't add the line above because I'm not quite sure >>>>>>>>>>>>>>>>>>> how. How do I edit the activate file? >>>>>>>>>>>>>>>>>>> On Jan 12, 2015 8:03 PM, "Michael Joyce" < >>>>>>>>>>>>>>>>>>> jo...@apache.org> wrote: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> That is the virtualenv one. The anaconda one should be >>>>>>>>>>>>>>>>>>>> /home/nic/climate/anaconda/bin/python. Note that if >>>>>>>>>>>>>>>>>>>> you added that line above you will need to deactivate and >>>>>>>>>>>>>>>>>>>> reactivate the >>>>>>>>>>>>>>>>>>>> virtualenv for it to take effect. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> If you want to test manually what I mentioned above you >>>>>>>>>>>>>>>>>>>> could try >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> 0. Deactivate the virtualenv (just to be safe) >>>>>>>>>>>>>>>>>>>> 1. initialize the virtualenv >>>>>>>>>>>>>>>>>>>> 2. run `export PATH="/home/nic/climate/ >>>>>>>>>>>>>>>>>>>> anaconda/bin/:$PATH"` >>>>>>>>>>>>>>>>>>>> 3. run `which python` and see what you get >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> -- Joyce >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> On Mon, Jan 12, 2015 at 7:55 PM, nic pederson < >>>>>>>>>>>>>>>>>>>> nicpeder...@gmail.com> wrote: >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> Which python produces >>>>>>>>>>>>>>>>>>>>> ~/climate/easy/easy-ocw/ocw/bin/python >>>>>>>>>>>>>>>>>>>>> On Jan 12, 2015 7:42 PM, "Michael Joyce" < >>>>>>>>>>>>>>>>>>>>> jo...@apache.org> wrote: >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> Ok not quite as confident now as I thought but try >>>>>>>>>>>>>>>>>>>>>> this. I think you might be running into an annoying >>>>>>>>>>>>>>>>>>>>>> little bug and/or a gap >>>>>>>>>>>>>>>>>>>>>> in the documentation here. Try adding this to the end of >>>>>>>>>>>>>>>>>>>>>> your >>>>>>>>>>>>>>>>>>>>>> ocw/bin/activate file and see if that fixes this. >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> 1. export >>>>>>>>>>>>>>>>>>>>>> PATH=/home/nic/climate/anaconda/bin:$PATH >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> I think we're missing an export of a path in the >>>>>>>>>>>>>>>>>>>>>> install script when you run a virtualenv and it's >>>>>>>>>>>>>>>>>>>>>> causing the wrong python >>>>>>>>>>>>>>>>>>>>>> to be called. You can check by running "which python" >>>>>>>>>>>>>>>>>>>>>> and see if you get >>>>>>>>>>>>>>>>>>>>>> the anaconda one or the virtualenv one. You want to be >>>>>>>>>>>>>>>>>>>>>> getting the anaconda >>>>>>>>>>>>>>>>>>>>>> one. Hopefully that's the problem/solution. >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> -- Joyce >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> On Mon, Jan 12, 2015 at 7:33 PM, Michael Joyce < >>>>>>>>>>>>>>>>>>>>>> jo...@apache.org> wrote: >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> Ah ok I think I know what the problem is. One second >>>>>>>>>>>>>>>>>>>>>>> to check and see. >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> -- Joyce >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> On Mon, Jan 12, 2015 at 7:25 PM, nic pederson < >>>>>>>>>>>>>>>>>>>>>>> nicpeder...@gmail.com> wrote: >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> Here is my bash >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> Pastebin.com/7ULyyng3 >>>>>>>>>>>>>>>>>>>>>>>> On Jan 12, 2015 7:12 PM, "Michael Joyce" < >>>>>>>>>>>>>>>>>>>>>>>> jo...@apache.org> wrote: >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> Trying running source ocw/bin/activate from >>>>>>>>>>>>>>>>>>>>>>>>> ~/climate/easy-ocw and see if that works >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> -- Joyce >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> On Mon, Jan 12, 2015 at 7:10 PM, nic pederson < >>>>>>>>>>>>>>>>>>>>>>>>> nicpeder...@gmail.com> wrote: >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> "source activate" when in >>>>>>>>>>>>>>>>>>>>>>>>>> ~/climate/easy-ocw/ocw/bin >>>>>>>>>>>>>>>>>>>>>>>>>> On Jan 12, 2015 7:05 PM, "Michael Joyce" < >>>>>>>>>>>>>>>>>>>>>>>>>> jo...@apache.org> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> Hey Nic, >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> What command are you using to start the >>>>>>>>>>>>>>>>>>>>>>>>>>> environment? >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> -- Joyce >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> On Mon, Jan 12, 2015 at 7:00 PM, >>>>>>>>>>>>>>>>>>>>>>>>>>> nicpeder...@gmail.com <nicpeder...@gmail.com> >>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>> Hi guys, >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>> I was still having trouble, so just did a fresh >>>>>>>>>>>>>>>>>>>>>>>>>>>> install of ubuntu. Everything went fine until I >>>>>>>>>>>>>>>>>>>>>>>>>>>> tried to activate OCW. I >>>>>>>>>>>>>>>>>>>>>>>>>>>> get an error that says "error: no environment >>>>>>>>>>>>>>>>>>>>>>>>>>>> provided" >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks again >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>> Nic >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>> Sent from my HTC phone. >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>> ----- Reply message ----- >>>>>>>>>>>>>>>>>>>>>>>>>>>> From: "Michael Joyce" <jo...@apache.org> >>>>>>>>>>>>>>>>>>>>>>>>>>>> To: "nic pederson" <nicpeder...@gmail.com> >>>>>>>>>>>>>>>>>>>>>>>>>>>> Cc: "dev@climate.apache.org" < >>>>>>>>>>>>>>>>>>>>>>>>>>>> dev@climate.apache.org>, " >>>>>>>>>>>>>>>>>>>>>>>>>>>> chris.a.mattm...@nasa.gov" < >>>>>>>>>>>>>>>>>>>>>>>>>>>> chris.a.mattm...@nasa.gov> >>>>>>>>>>>>>>>>>>>>>>>>>>>> Subject: New Student - Caltech-JPL Summer >>>>>>>>>>>>>>>>>>>>>>>>>>>> School on Big Data Analytics - Need Help Setting >>>>>>>>>>>>>>>>>>>>>>>>>>>> up OCW >>>>>>>>>>>>>>>>>>>>>>>>>>>> Date: Mon, Jan 12, 2015 2:32 PM >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>> You should be able to run "rm -r >>>>>>>>>>>>>>>>>>>>>>>>>>>> /home/nic/Learning/climate/anaconda" (without >>>>>>>>>>>>>>>>>>>>>>>>>>>> quotes and make sure I actually got that directory >>>>>>>>>>>>>>>>>>>>>>>>>>>> correct ;) >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>> Then you should be able to run the Anaconda >>>>>>>>>>>>>>>>>>>>>>>>>>>> script the same way the install-ubuntu.sh script >>>>>>>>>>>>>>>>>>>>>>>>>>>> does. Namely: >>>>>>>>>>>>>>>>>>>>>>>>>>>> bash Anaconda-1.9.2-Linux-x86_64.sh >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>> That .sh file should still be in the easy-ocw >>>>>>>>>>>>>>>>>>>>>>>>>>>> folder (assuming you ran ./install-ubuntu.sh from >>>>>>>>>>>>>>>>>>>>>>>>>>>> /climate/easy-ocw/). When >>>>>>>>>>>>>>>>>>>>>>>>>>>> you go through the install just make sure you put >>>>>>>>>>>>>>>>>>>>>>>>>>>> the directory where you >>>>>>>>>>>>>>>>>>>>>>>>>>>> want it instead of the default. From above I think >>>>>>>>>>>>>>>>>>>>>>>>>>>> you'll want: >>>>>>>>>>>>>>>>>>>>>>>>>>>> /home/nic/Learning/climate/ >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>> If you get stuck let us know! >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>> -- Joyce >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>> On Mon, Jan 12, 2015 at 2:08 PM, nic pederson < >>>>>>>>>>>>>>>>>>>>>>>>>>>> nicpeder...@gmail.com> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks for looking. That's exactly what I >>>>>>>>>>>>>>>>>>>>>>>>>>>>> did... What as the best way to wipe/reinstall? Im >>>>>>>>>>>>>>>>>>>>>>>>>>>>> fairly new to Linux and >>>>>>>>>>>>>>>>>>>>>>>>>>>>> command line in general. >>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>> Nic >>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Jan 12, 2015 1:51 PM, "Michael Joyce" < >>>>>>>>>>>>>>>>>>>>>>>>>>>>> jo...@apache.org> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Ok after looking around a bit and checking >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> your RC my guess is that you did something along >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> the lines of: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Ran install-ubuntu.sh >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Decided to move where Anaconda was installed >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> by cp-ing (or something) it somewhere else >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ... >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Ended up where we're at >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> If that is the case then I think your problem >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> is that you can't move Anaconda around after the >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> initial install. If you >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> want it in a different place you'll need to do >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> that at install-time. Check >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> this convo [1] for a bit more info. Basically >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> just reinstall Anaconda where >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> you want it and blow out the old install just to >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> be safe. The install >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> script forces you to install it in the default >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> location. Patches are more >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> than welcome to fix this ;) >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> If that's not what you did then what did you >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> do. Maybe a bit more info will get us pointed in >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> the right direction =) >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> You can also remove the following line from >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> your RC. This looks like an input error when >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> running install-ubuntu.sh >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 1. export >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> PYTHONPATH=~Learning/climate/easy-owc/install-ubuntu.sh:~Learning/climate/easy-owc/ >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> install-ubuntu.sh/ocw >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [1] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> https://groups.google.com/a/continuum.io/forum/#!msg/anaconda/LcaXE25qElM/VKWYghrjb98J >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> -- Joyce >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Mon, Jan 12, 2015 at 1:23 PM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> nicpeder...@gmail.com <nicpeder...@gmail.com> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> .bashrc >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> pastebin.com/P4Ux1XJm >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> "conda info" >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> bash: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> /home/nic/Learning/climate/anaconda/bin/conda: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> /home/nic/anaconda/bin/python: bad interpreter: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> no such file or directory >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Sent from my HTC phone. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ----- Reply message ----- >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> From: "Michael Joyce" <jo...@apache.org> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> To: "nic pederson" <nicpeder...@gmail.com> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Cc: "dev@climate.apache.org" < >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> dev@climate.apache.org>, " >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> chris.a.mattm...@nasa.gov" < >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> chris.a.mattm...@nasa.gov> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Subject: New Student - Caltech-JPL Summer >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> School on Big Data Analytics - Need Help >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Setting up OCW >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Date: Mon, Jan 12, 2015 12:58 PM >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Mkay. Can you please post your entire bashrc >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> (pastebin link would probably be best) and the >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> output of "conda info"? It >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> doesn't seem to be cooperating with regards to >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> where it should look for >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> conda packages. I'm thinking there's some >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> residual config from a previous >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> install or I'm forgetting something really >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> obvious. Worst case we might >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> need to blow out the entire Anaconda install >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> and redo it (FUN!). Hopefully >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> it's just something stupid in a config >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> somewhere we can update. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> -- Joyce >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Mon, Jan 12, 2015 at 12:51 PM, nic >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> pederson <nicpeder...@gmail.com> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> /home/nic/Learning/climate/anaconda/bin/conda >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Jan 12, 2015 12:47 PM, "Michael Joyce" < >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> jo...@apache.org> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Strange. When you run "which conda" what >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> do you see? >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> -- Joyce >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Mon, Jan 12, 2015 at 12:40 PM, nic >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> pederson <nicpeder...@gmail.com> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> That did it! Except now I cannot activate >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> OWC. When I activate, I get a line like: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> bash: (correct >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> path)/climate/anaconda/bin/conda: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> /home/nic/anaconda/bin/python: bad >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> interpreter: no such file or directory >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks again for your help. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Nic >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Jan 12, 2015 12:08 PM, "Michael Joyce" >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> <jo...@apache.org> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> No problem Nic, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> You should have a line in your bashrc >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> similar to the following. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> export PATH=~/Anaconda/bin:$PATH >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> If you replace the assumed path with the >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> location where Anaconda actually is you >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> should be golden. If that doesn't >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> fix if for you though let us know. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> -- Joyce >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Mon, Jan 12, 2015 at 12:00 PM, nic >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> pederson <nicpeder...@gmail.com> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks guys! That sounds about right. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> The missing module is numpy when owc is >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> activated. (It's filenames when >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> it's deactivated)... Also, I feel like I >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> may have made a bit of a mess of >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> the file structure in trying to >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> move/reinstall Anaconda a couple times. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks for all your help. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Nic >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Jan 12, 2015 11:23 AM, "Michael >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Joyce" <jo...@apache.org> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Hi Nic (and Chris), >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> I'm guessing from your question that >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> you are installing onto Ubuntu with the >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> last release of OCW (0.4). You >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> should be fine on 14.10, the old scripts >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> were only tested on 12.04 so we >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> list that explicitly. Of course there is >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> still a possibility that you might >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> run into some problems. If you're pulling >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> off the latest master then the >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Ubuntu script is tested on 12.04 and >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 14.04. What modules are failing for >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> you? If it's something like numpy/scipy >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> then you probably have an issue >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> with the location of the Anaconda bin and >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> your path. This could be a result >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> of Anaconda being installed in a >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> different spot than expected or it could >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> be a bug in the install scripts. If >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> you're having problems with some OCW >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> modules not importing then it probably a >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> problem with the PYTHONPATH not >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> being set as expected. Let us know what >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> problems you're seeing and I'm sure >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> we can get it sorted quickly. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> -- Joyce >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Mon, Jan 12, 2015 at 8:10 AM, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Mattmann, Chris A (3980) < >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> chris.a.mattm...@jpl.nasa.gov> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Hi Nic, thanks for your question and >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> am forwarding to the Apache >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> OCW list for some more help! >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Cheers, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Chris >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Chris Mattmann, Ph.D. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Chief Architect >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Instrument Software and Science Data >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Systems Section (398) >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> NASA Jet Propulsion Laboratory >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Pasadena, CA 91109 USA >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Office: 168-519, Mailstop: 168-527 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Email: chris.a.mattm...@nasa.gov >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> WWW: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> http://sunset.usc.edu/~mattmann/ >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Adjunct Associate Professor, Computer >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Science Department >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> University of Southern California, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Los Angeles, CA 90089 USA >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> -----Original Message----- >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> From: Nic <nicpeder...@gmail.com> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Date: Monday, January 12, 2015 at >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 8:08 AM >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> To: Chris Mattmann < >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> chris.a.mattm...@nasa.gov> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Subject: New Student - Caltech-JPL >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Summer School on Big Data Analytics - >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Need Help Setting up OCW >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >Hi Chris! >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >I'm really excited for this class, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> but I'm a little hung up on Day 1 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >installations. Long story short, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> I've setup PyLint and OCW, but OCW >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >seems to be unable to find some >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> modules. Could this be because I >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >installed files (i suspect anaconda) >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> in the wrong folders? >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >I'm running Ubuntu 14.10 (Lenovo >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> IdeaPad). I noticed that OCW install >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >instructions say that I should be >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> running 12.04. I have 14.10 installed. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >I'm trying to wipe and restart >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Ubuntu with 12.04 now, but am having >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >trouble getting it to boot. Can I >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> run 14.10 with OCW? >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >I've checked the discussion boards >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> and have done a bit of research >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >already, but not much fruit. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >Thanks so much and I look forward to >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> hearing from you, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >Nic Pederson >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >541.953.1520 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >@nicpederson >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>> >>>>> >>>> >> >
