Subject: Marine Geospatial Ecology Tools (MGET) help
Text archives
| From: | "Jason Roberts" <> |
|---|---|
| To: | <> |
| Cc: | <> |
| Subject: | RE: help with RPy and R 2.7.2 |
| Date: | Tue, 7 Apr 2009 17:30:54 -0400 |
Hi Eric,
As you have discovered, rpy must be recompiled every time a new version of R
comes out. The rpy developers have not been keeping up with this so it can be
difficult to access newer versions of R if you are not able to recompile it
yourself.
Our toolbox (MGET) incorporates a private copy of rpy. We recompile it every
time a new version of R comes out, and plan to do so as long as MGET
continues to rely on rpy and we have funding to continue its development. You
are welcome to download our recompilations of rpy's Python extension modules
from here:
https://code.env.duke.edu/projects/mget/browser/MGET/Trunk/PythonPackage/src/GeoEco/AssimilatedModules/rpy/lib
Note that, at this time, we are only building rpy (and MGET) for 32-bit
Windows and Python 2.4 and 2.5. In the future, we may expand to other
platforms, although we have no immediate plans to do so. We will likely start
building for Python 2.6 sometime in 2009.
Because rpy cannot be run from an in-process Python script in ArcGIS 9.3, we
are considering replacing rpy with rpy2 or tweaking our own version of rpy to
allow this to work. Once we take either of these courses of action, it is
likely you will no longer be able to rely on us for Python extension modules
for new versions of R. If we go with rpy2, we will abandon rpy. If we tweak
our own copy of rpy, we will likely eliminate the requirement that rpy be
recompiled with new versions of R, but our new design will not be compatible
with the public version of rpy.
If you would like to build rpy yourself, you might be able to learn from this
document:
https://code.env.duke.edu/projects/mget/browser/MGET/Trunk/PythonPackage/src/GeoEco/AssimilatedModules/rpy/src-rpy-1.0.3/BUILDING_FOR_GEOECO.txt
Hope this helps,
Jason
-----Original Message-----
From:
[mailto:]
Sent: Tuesday, April 07, 2009 4:02 PM
To:
Subject: help with RPy and R 2.7.2
I am in the preliminary stages of creating a toolbox in ArcGIS that links (via
RPy) to a package in R 2.7.2. Unfortunately, while I am able to link into R
2.7.0 via RPy, the package I need was developed under R 2.7.2. Suggestions I
came across elsewhere said to recompile RPy with R 2.7.2 which will create the
_rpy2072 module. I'm not really a programmer, so I'm looking for some
instructions that'll allow me to do this. Any ideas?
Thanks,
-Eric
As you have discovered, rpy must be recompiled every time a new version of R
comes out. The rpy developers have not been keeping up with this so it can be
difficult to access newer versions of R if you are not able to recompile it
yourself.
Our toolbox (MGET) incorporates a private copy of rpy. We recompile it every
time a new version of R comes out, and plan to do so as long as MGET
continues to rely on rpy and we have funding to continue its development. You
are welcome to download our recompilations of rpy's Python extension modules
from here:
https://code.env.duke.edu/projects/mget/browser/MGET/Trunk/PythonPackage/src/GeoEco/AssimilatedModules/rpy/lib
Note that, at this time, we are only building rpy (and MGET) for 32-bit
Windows and Python 2.4 and 2.5. In the future, we may expand to other
platforms, although we have no immediate plans to do so. We will likely start
building for Python 2.6 sometime in 2009.
Because rpy cannot be run from an in-process Python script in ArcGIS 9.3, we
are considering replacing rpy with rpy2 or tweaking our own version of rpy to
allow this to work. Once we take either of these courses of action, it is
likely you will no longer be able to rely on us for Python extension modules
for new versions of R. If we go with rpy2, we will abandon rpy. If we tweak
our own copy of rpy, we will likely eliminate the requirement that rpy be
recompiled with new versions of R, but our new design will not be compatible
with the public version of rpy.
If you would like to build rpy yourself, you might be able to learn from this
document:
https://code.env.duke.edu/projects/mget/browser/MGET/Trunk/PythonPackage/src/GeoEco/AssimilatedModules/rpy/src-rpy-1.0.3/BUILDING_FOR_GEOECO.txt
Hope this helps,
Jason
-----Original Message-----
From:
[mailto:]
Sent: Tuesday, April 07, 2009 4:02 PM
To:
Subject: help with RPy and R 2.7.2
I am in the preliminary stages of creating a toolbox in ArcGIS that links (via
RPy) to a package in R 2.7.2. Unfortunately, while I am able to link into R
2.7.0 via RPy, the package I need was developed under R 2.7.2. Suggestions I
came across elsewhere said to recompile RPy with R 2.7.2 which will create the
_rpy2072 module. I'm not really a programmer, so I'm looking for some
instructions that'll allow me to do this. Any ideas?
Thanks,
-Eric
Archives powered by MHonArc.