>is it clear now what were the problems?
Yes it's clear now what the issue(s) was:
- the winGRASS-R-bridge looks for R installations in windows standard drive
and folders, i.e. C:\Program; R installations in non standard drives,
e.g. D:\Program... are not reckognized => standard R
Thanks Helmut for figuring it out! I was wondering is it clear now what
were the problems? I thought a summary might be useful if we encounter this
again...
Anna
On Sun, Dec 13, 2020 at 7:05 AM Helmut Kudrnovsky wrote:
> >Ok got it, I just had to run R as administrator and download it then. >I
>Ok got it, I just had to run R as administrator and download it then. >I
think everything works now. Helmut, I don't know how I can thank >you. I
hope we meet one day so that I can invite you to a coffee or >whatever you
wish
you're welcome. yes you have to install R packages as administrator to
Ok got it, I just had to run R as administrator and download it then. I
think everything works now. Helmut, I don't know how I can thank you. I
hope we meet one day so that I can invite you to a coffee or whatever you
wish.
Thank you so much, have a nice Sunday and stay healthy!
Best regards
I reinstalled it and whenever I want to install packages it says:
> install.packages(c("MuMIn", "lme4", "optparse", "rgrass7"))
Warnung in install.packages(c("MuMIn", "lme4", "optparse", "rgrass7"))
'lib = "C:/Program Files/R/R-4.0.3/library" ist nicht schreibbar
Would you like to use a
It's an R issue, not a GRASS issue.
Open R in a normal way.
library("MuMIn")
What does it report?
>The packages can also be found in the directory
That's only the temporary download folder, not the R package folder
-
best regards
Helmut
--
Sent from:
It seems like it, but it is already installed (see below).
The packages can also be found in the directory :
[image: image.png]
Still the error message says it's not installed.
R version 4.0.3 (2020-10-10) -- "Bunny-Wunnies Freak Out"
Copyright (C) 2020 The R Foundation for Statistical
Looks good so far! R/RScript is found and work
>Package MuMIn not found
What I have asked already in a previous mail. A needed R package isn't
installed.
-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Users-f3884509.html
Okay it is on C:/ now and I have run the module and at least the error
message changed! Thank you already for all your help!! But, now it says:
r.futures.potential input=sampling output=potential.csv
>the R path is: D:\Programme\R-4.0.3
Is it really D:\ and not C:\ ?
The winGRASS-R-bridge looks for R in C:\.
-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Users-f3884509.html
___
grass-user mailing
The content of C:\OSGeo4W64\etc\ini is:
- gdal
-libgeotiff
-libjpeg
-liblas
-msvcrt
-proj
-python-core
-rbatchfiles
The content of C:\OSGeo4W64\apps\rbatchfiles is
-#Rscript2
-ANNOUNCE
-batchfiles.md
-batchfiles.tex
-clip2r
-copydir
-COPYING
-el
LICENSE
-make-batchfiles.pdf
-movedir
-NEWS
-R
What is the content of C:\OSGeo4W64\etc\ini and C:\OSGeo4W64\Apps?
What is the path to your R installation?
Not sure what's going on as tested here on several win 10 boxes, and it
works on all of them.
-
best regards
Helmut
--
Sent from:
Hi Helmut,
I deleted everything and downloaded it again just as you said, with the
different batchfile. I still get the same error message (only with a
different path in the error message/see below) and there is still nothing
happening if I try to run R or Rscript in the Shell (no matter if Grass
[a hint to save message size:
- just open a windows command console,
- change to the relevant folder: e.g.
C:\Users\your user>cd C:\OSGeo4W64\etc\ini
C:\OSGeo4W64\etc\ini>
- do dir /b
C:\OSGeo4W64\etc\ini>dir /b
gdal.bat
libgeotiff.bat
libjpeg.bat
liblas.bat
msvcrt.bat
msys.bat
proj.bat
There is one more OSGeo folder on my Disc (I do not know why) which is
similarly empty:
[image: image.png]
Am Sa., 12. Dez. 2020 um 14:35 Uhr schrieb Tom Hackbarth <
txhackba...@gmail.com>:
> Hi Helmut,
>
> I have found the folder with the 18 files, but not the first one. The etc
> folder is
Hi Helmut,
I have found the folder with the 18 files, but not the first one. The etc
folder is almost empty in my case (see picture below).
[image: image.png]
Am Sa., 12. Dez. 2020 um 13:48 Uhr schrieb Helmut Kudrnovsky :
> >for a workaround:
>
> we're working to bring the
>for a workaround:
we're working to bring the R-winGRASS-bridge back to OSGeo4W
-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Users-f3884509.html
___
grass-user mailing list
grass-user@lists.osgeo.org
>run o-help for a list of available commands
>C:\>R
>Der Befehl "R" ist entweder falsch geschrieben oder
>konnte nicht gefunden werden.
>
>C:\>Rscript
>Der Befehl "Rscript" ist entweder falsch geschrieben oder
>konnte nicht gefunden werden.
>
>(that means it's been typed wrong or couldn't be
I have downloaded, installed and deleted the program now for so many times,
that there might be some residual data from before somewhere on my
computer. Could this be the problem?
Is there a way to properly uninstall all the programme data? I haven't been
able to find such a way as OSGeo4W or
Hi Helmut,
I have switched to the earlier rbatch version. But I still get the same
error message running r.futures.
This is what happens when I type R or Rscript in the Shell:
*run o-help for a list of available commandsC:\>RDer Befehl "R" ist
entweder falsch geschrieben oderkonnte nicht
>It is still not working and the error message is still the same.
install.packages(c("MuMIn", "lme4", "optparse", "rgrass7")) done?
I got a similar error message when MuMIn wasn't installed.
have you tried in OSGeo4W to switch to an earier rbatch version. then R
should be added automatically
>local R version: 4.03
and tested in
System Info
GRASS Version: 7.8.4
Code revision: d8fbd49af
Build date:
>regarding OSGeo4W-winGRASS, unfortunately there was a change in the rbatch
package recently which >breaks adding R to %PATH%
>
>*start OSGeo4W in advanced mode, type rbatch in the search window on the
top left
>* open the tree of "Command_Utilities" and "Libs" and choose version 149-4
instead of
vailable here.
kind regards
Helmut
Gesendet: Freitag, 11. Dezember 2020 um 10:19 Uhr
Von: "Tom Hackbarth"
An: "Helmut Kudrnovsky"
Betreff: Re: [GRASS-user] r.futures not working
Hi Helmut,
I tried it now on mac as well. I get to the same point.
C
Tom Hackbarth wrote
> Dear grass users,
>
> I am trying to work my way through the r.futures workshop (
> https://grasswiki.osgeo.org/wiki/Workshop_on_urban_growth_modeling_with_FUTURES#Potential_submodel),
> but as soon as I get to the point of using the first r.futures module -
>
Hi Tom,
On Thu, Dec 10, 2020 at 4:24 AM Tom Hackbarth wrote:
> Hi Anna,
>
> thanks for your answer.
>
> I reinstalled it already multiple times. I get the same error message
> every time though. I will try it on a mac tomorrow, but that is the last
> idea I have. Has there ever been a problem
On Wed, Dec 9, 2020 at 8:37 AM Tom Hackbarth wrote:
> Dear grass users,
>
> I am trying to work my way through the r.futures workshop (
> https://grasswiki.osgeo.org/wiki/Workshop_on_urban_growth_modeling_with_FUTURES#Potential_submodel),
> but as soon as I get to the point of using the first
Dear grass users,
I am trying to work my way through the r.futures workshop (
https://grasswiki.osgeo.org/wiki/Workshop_on_urban_growth_modeling_with_FUTURES#Potential_submodel),
but as soon as I get to the point of using the first r.futures module -
r.futures-potential I come to a dead end.
28 matches
Mail list logo
