[GRASS-user] Re: Georectify problem

Adam Dershowitz, Ph.D., P.E. adershowitz at exponent.com
Wed Dec 2 13:15:08 EST 2009


I didn't install wxPython and neither did macports.

Macports is all installed in /opt/local and my .profile just adds that to my PATH and LIBRARY_PATH.  

I find it very odd that your build and William's build are finding different versions of python (and neither is the apple one).

By the way, if I run either of them, and then at the command line I run python, I do see the expected one.  In other words, yours reports Python 2.5.4 found. but then if I type python it shows 2.6.1, (while Williams reports 2.6.4)

How are you searching for python?  Are you not just using the typical path from .profile?

--Adam



On Dec 2, 2009, at 9:34 AM, Michael Barton wrote:

> Did you install wxPython? Did Macports?
> 
> I understand how MacPorts works in this regard. Fink does the same thing, though you can opt not to install dependencies and can also install binaries that might need the dependencies (i.e., only needed to compile). This is a Linux-like package installer model. It is handy but can have problems playing nicely with other unix software installed on your system outside of the MacPorts (or Fink) package hierarchy. I know that both try to wall off their stuff into separate areas, but sometimes it doesn't work.
> 
> To try and overcome the complications of having more than one Python version and more than one wxPython version, both William and I now include a wxPython build in our GRASS binaries. However, I'm not sure what will happen in a situation like yours. Hopefully my binary will work.
> 
> You might need to search out and look at your various system configuration files and see if any of them refer to the MacPorts Python. These normally live in your home folder and the etc folder. They begin with a ".", so are invisible unless you run something like Invisibility Toggler.app, use Text Wrangler's open hidden function, or use the command line utilties.
> 
> Files to look for include .profile and .bashrc. There might be others too depending on how MacPorts manages setting system configurations.
> 
> Michael
> ____________________
> C. Michael Barton
> Director, Center for Social Dynamics & Complexity
> Professor of Anthropology, School of Human Evolution & Social Change
> Arizona State University
> 
> Phone: 480-965-6262
> Fax: 480-965-7671
> www: www.public.asu.edu/~cmbarton, http://csdc.asu.edu
> 
> 
> 
> 
> 
> 
> 
> On Dec 2, 2009, at 10:24 AM, Adam Dershowitz, Ph.D., P.E. wrote:
> 
>> For each port that you install with macports it determines what other ports are necessary.  Macports project has taken the attitude that they always want to use their own version of code so that changes by Apple won't break other specific dependencies, which has happened to them a number of times.  That leads to most ports working well, but can lead to other problems, so their are some pluses and minus to this approach.  But, that is the current approach, and if I were to try to force uninstall any python stuff, it would break other ports.  Apple actually has 2.6.1 installed, while macports installs 2.6.4.
>> That said, python_select just changes links and moves files around so that only one version of python is "visible" and the others are hidden, except to explicit paths.  And I have confirmed that from the command line using python_select does change which version gets used.
>> So, according to macports, I have python2.5 python2.6 and python26-apple installed right now, but only the apple version should be visible, so I doubt that this is causing the problem.
>> 
>> --Adam
>> 
>> 
>> 
>> On Dec 2, 2009, at 9:11 AM, Michael Barton wrote:
>> 
>>> If you have a second python and it is in your python path, you'll have trouble. Do you know what the Macports "python_select" script does?
>>> 
>>> You really don't need to install any extra Python because your Mac already comes with Python 2.6, the most up-to-date of the 2.x series. It should not be necessary to run anything downloaded from MacPorts as any Python app should use the system Python unless it needs an earlier version. If MacPorts is installing 2.3 or 2.4 this could be a pretty big headache since GRASS requires at least 2.4 and possibly 2.5 or above to run its wxPython GUI (we've tried not to break 2.4 compatibility but I haven't tested it). I've heard of other people having trouble with conflicts from MacPorts. I uses to use Fink but ran into some of the same issues. And by now I don't really need it since many applications are now available on the Mac in a more native way. You might try getting rid of the MacPorts Python and see if GRASS run--and if MacPorts Python apps still run.
>>> 
>>> Michael
>>> ____________________
>>> C. Michael Barton
>>> Director, Center for Social Dynamics & Complexity
>>> Professor of Anthropology, School of Human Evolution & Social Change
>>> Arizona State University
>>> 
>>> Phone: 480-965-6262
>>> Fax: 480-965-7671
>>> www: www.public.asu.edu/~cmbarton, http://csdc.asu.edu
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> On Dec 2, 2009, at 10:00 AM, Adam Dershowitz, Ph.D., P.E. wrote:
>>> 
>>>> I do have python installed as I have a bunch of things installed with macports and some of them depend on it and so installed it as part of the builds.  So I can't really get rid of it.  But, as part of macports, I do have python_select, which is a small port that allows me to switch which python is active and I am currently using the Apple installed Python 2.6, not one of the Macport installed versions.  So I don't think that is the problem....?
>>>> I am downloading one of your builds to test out right now.
>>>> 
>>>> Thanks,
>>>> 
>>>> --Adam
>>>> 
>>>> 
>>>> 
>>>> On Dec 2, 2009, at 8:53 AM, Michael Barton wrote:
>>>> 
>>>>> Did you install Python yourself? If so, you will need to get rid of it. I know how to do so with 10.5, but am not sure of 10.6. William might be able to offer guidance on this.
>>>>> 
>>>>> If you did not install a separate Python, I'm not sure what the problem is. But you can try one of my builds. They work with Snow Leopard on at least one student machine I know of. I've posted very recent binaries for 6.4, 6.5, and 7.0.
>>>>> 
>>>>> http://www.public.asu.edu/~cmbarton/files/grass_mac
>>>>> 
>>>>> Michael
>>>>> ____________________
>>>>> C. Michael Barton
>>>>> Director, Center for Social Dynamics & Complexity
>>>>> Professor of Anthropology, School of Human Evolution & Social Change
>>>>> Arizona State University
>>>>> 
>>>>> Phone: 480-965-6262
>>>>> Fax: 480-965-7671
>>>>> www: www.public.asu.edu/~cmbarton, http://csdc.asu.edu
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> On Dec 2, 2009, at 9:44 AM, Adam Dershowitz, Ph.D., P.E. wrote:
>>>>> 
>>>>>> Sorry, Mac 10.6.2 using William Kyngesburye's binary builds.
>>>>>> 
>>>>>> --Adam
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> On Dec 2, 2009, at 8:35 AM, Michael Barton wrote:
>>>>>> 
>>>>>>> What OS platform?
>>>>>>> 
>>>>>>> Michael
>>>>>>> ____________________
>>>>>>> C. Michael Barton
>>>>>>> Director, Center for Social Dynamics & Complexity
>>>>>>> Professor of Anthropology, School of Human Evolution & Social Change
>>>>>>> Arizona State University
>>>>>>> 
>>>>>>> Phone: 480-965-6262
>>>>>>> Fax: 480-965-7671
>>>>>>> www: www.public.asu.edu/~cmbarton, http://csdc.asu.edu
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> On Dec 2, 2009, at 9:34 AM, Adam Dershowitz, Ph.D., P.E. wrote:
>>>>>>> 
>>>>>>>> I did try it, but I can't currently get it to run.  My guess is that it is an issue of the current built of GRASS that I am using (6.4 RC5-3 on a 64 bit machine):
>>>>>>>> 
>>>>>>>> g.gui wxpython
>>>>>>>> Traceback (most recent call last):
>>>>>>>> File "/Applications/GRASS-6.4.app/Contents/MacOS/etc/wxpython/wxgui.py", line 55, in <module>
>>>>>>>> import gui_modules.globalvar as globalvar
>>>>>>>> File "/Applications/GRASS-6.4.app/Contents/MacOS/etc/wxpython/gui_modules/globalvar.py", line 59, in <module>
>>>>>>>> import wx
>>>>>>>> File "/Applications/GRASS-6.4.app/Contents/MacOS/etc/python/wx/__init__.py", line 45, in <module>
>>>>>>>> from wx._core import *
>>>>>>>> File "/Applications/GRASS-6.4.app/Contents/MacOS/etc/python/wx/_core.py", line 4, in <module>
>>>>>>>> import _core_
>>>>>>>> ImportError: dlopen(/Applications/GRASS-6.4.app/Contents/MacOS/etc/python/wx/_core_.so, 2): no suitable image found.  Did find:
>>>>>>>> 	/Applications/GRASS-6.4.app/Contents/MacOS/etc/python/wx/_core_.so: mach-o, but wrong architecture
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> --Adam
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> On Dec 2, 2009, at 6:47 AM, Michael Barton wrote:
>>>>>>>> 
>>>>>>>>> Important to note that this will not work with Windows, since Windows doesn't run x11 unless you the Cygwin unix emulator.
>>>>>>>>> 
>>>>>>>>> Have you tried georectification with the new wxPython GUI?
>>>>>>>>> 
>>>>>>>>> Michael
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> On Dec 1, 2009, at 11:20 PM, grass-user-request at lists.osgeo.org wrote:
>>>>>>>>> 
>>>>>>>>>> Date: Wed, 02 Dec 2009 15:01:23 +1100
>>>>>>>>>> From: Richard Chirgwin <rchirgwin at ozemail.com.au>
>>>>>>>>>> Subject: [GRASS-user] Re: Georectify problem
>>>>>>>>>> To: grass-user at lists.osgeo.org
>>>>>>>>>> Message-ID: <4B15E693.1010909 at ozemail.com.au>
>>>>>>>>>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>>>>>>>>>> 
>>>>>>>>>> Adam,
>>>>>>>>>> 
>>>>>>>>>> If all else fails, work with a command line process ... I've never had
>>>>>>>>>> happy experiences with the purely GUI rectification.
>>>>>>>>>> 
>>>>>>>>>> i.group (groupname) (mapname)
>>>>>>>>>> i.target (groupname) Target_Location Target_Mapset
>>>>>>>>>> d.mon X0
>>>>>>>>>> i.points (groupname) - this launches the GCP capture GUI (old style,
>>>>>>>>>> X-windows but it works!)
>>>>>>>>>> i.rectify (groupname) extension="something" order=(polynomial order)
>>>>>>>>>> 
>>>>>>>>>> RC
>>>>>>>>> 
>>>>>>>>> _______________________________________________
>>>>>>>>> grass-user mailing list
>>>>>>>>> grass-user at lists.osgeo.org
>>>>>>>>> http://lists.osgeo.org/mailman/listinfo/grass-user
>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>>> 
>>> 
>> 
> 



More information about the grass-user mailing list