similar to: "Couldn't find function par"

Full_Name: Frank Sch?ffer Version: 2.3.1 OS: Ubuntu 6.10 (Edgy Eft) Submission from: (NULL) (86.56.0.173) frank at darwin:~$ R R : Copyright 2006, The R Foundation for Statistical Computing Version 2.3.1 (2006-06-01) ISBN 3-900051-07-0 R ist freie Software und kommt OHNE JEGLICHE GARANTIE. Sie sind eingeladen, es unter bestimmten Bedingungen weiter zu verbreiten. Tippen Sie 'license()'

>>>>> Martin Maechler >>>>> on Tue, 8 Sep 2020 10:40:24 +0200 writes: >>>>> Hugh Parsonage >>>>> on Tue, 8 Sep 2020 18:08:11 +1000 writes: >> I can only reproduce on Windows, but reliably (both 4.0.0 and 4.0.2): >> $> R --vanilla >> x <- c(0L, -2e9:2e9) >> # > Segmentation

On Tue, 8 Sep 2020, Hugh Parsonage wrote: > Thanks Martin. On further testing, it seems that the segmentation > fault can only occur when the amount of obtainable memory is > sufficiently high. On my machine (admittedly with other processes > running): > > $ R --vanilla --max-mem-size=30G -e "x <- c(0L, -2e9:2e9)" > Segmentation fault > > $ R --vanilla

I can only reproduce on Windows, but reliably (both 4.0.0 and 4.0.2): $> R --vanilla x <- c(0L, -2e9:2e9) # > Segmentation fault Tried to reproduce on Linux but the above worked as expected. Not an issue merely with the length of the vector; for example, x <- rep_len(1:10, 1e10) works, though the altrep vector must be long to reproduce: x <- c(0L, -1e9:1e9) #ok Segmentation

>>>>> luke-tierney >>>>> on Tue, 8 Sep 2020 09:42:43 -0500 (CDT) writes: > On Tue, 8 Sep 2020, Martin Maechler wrote: >>>>>>> Martin Maechler >>>>>>> on Tue, 8 Sep 2020 10:40:24 +0200 writes: >> >>>>>>> Hugh Parsonage >>>>>>> on Tue, 8 Sep 2020

Dear list-reader, by running the following script: library(zoo) sessionInfo() search() packageDescription("zoo") data(EuStockMarkets) dax <- as.zoo(EuStockMarkets[1:10, "DAX"]) daxr <- diff(log(dax)) identical(as.vector(qnorm(daxr)), qnorm(coredata(daxr))) qqnorm(coredata(daxr)) qqnorm(daxr) qqnorm() produces an error: > qqnorm(daxr) Fehler in if (xi == xj) 0L

Hello, err dump [1], perhaps related [2]. Also $ sudo chown -R xyz:staff ~/R # sudo su; su xyz; groups web-content staff Not just vim-R-plugin -problem anymore, more pkg -installation -prob, doubting perms/group -issue but fixed them in accordance by Dirk's hints. What is the problem in installing packages? -- Regards, Henri Losoi -- [1] http://pastie.org/4577538 [2]

>>>>> Hugh Parsonage >>>>> on Tue, 8 Sep 2020 18:08:11 +1000 writes: > I can only reproduce on Windows, but reliably (both 4.0.0 and 4.0.2): > $> R --vanilla > x <- c(0L, -2e9:2e9) > # > Segmentation fault > Tried to reproduce on Linux but the above worked as expected. Not an > issue merely with the length of

Thanks Martin. On further testing, it seems that the segmentation fault can only occur when the amount of obtainable memory is sufficiently high. On my machine (admittedly with other processes running): $ R --vanilla --max-mem-size=30G -e "x <- c(0L, -2e9:2e9)" Segmentation fault $ R --vanilla --max-mem-size=29G -e "x <- c(0L, -2e9:2e9)" Error: cannot allocate vector

On Tue, 8 Sep 2020, Martin Maechler wrote: >>>>>> Martin Maechler >>>>>> on Tue, 8 Sep 2020 10:40:24 +0200 writes: > >>>>>> Hugh Parsonage >>>>>> on Tue, 8 Sep 2020 18:08:11 +1000 writes: > > >> I can only reproduce on Windows, but reliably (both 4.0.0 and 4.0.2): > > >> $> R

Unfortunately I only get [Thread 21752.0x4aa8 exited with code 3221225477] [Thread 21752.0x4514 exited with code 3221225477] [Thread 21752.0x3f10 exited with code 3221225477] [Inferior 1 (process 21752) exited with code 030000000005] (I'm guessing I would need to build an instrumented version of R, or can R be debugged using gdb with an off-the-shelf installation?) On Wed, 9 Sep 2020 at

This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --27464147-1968795515-1164715405=:5670 Content-Type: TEXT/PLAIN; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: 8BIT You need to re-install packages when you update R, as it says in the rw-FAQ. Use update.packages(checkBuilt=TRUE) to

On 9/8/20 4:48 PM, Hugh Parsonage wrote: > Unfortunately I only get > > [Thread 21752.0x4aa8 exited with code 3221225477] > [Thread 21752.0x4514 exited with code 3221225477] > [Thread 21752.0x3f10 exited with code 3221225477] > [Inferior 1 (process 21752) exited with code 030000000005] > > (I'm guessing I would need to build an instrumented version of R, or > can R

The R signon banner includes this statement: Natural language support but running in an English locale Should that not say 'National' instead of 'Natural'? Meaning that LOCALE support is enabled, not that the interface understands human language? Please ignore this and forgive me if this is an inappropriate post. I am a N00B in R. [[alternative HTML version deleted]]

>>>>> Paul McQuesten <mcquesten at gmail.com> >>>>> on Thu, 31 Aug 2017 18:48:12 -0500 writes: > Actually, I do agree with you about Microsoft. > But they have so many users that their terminology should not be ignored. > Here are a few more views: >

The way it's phrased now makes it seem that English is not a Natural language ("Natural language support *but* running in an English locale"). Why not just state: "running in an English locale" and leave it with that? Better to leave something out than to be unclear (being correct formally does not always mean being clear to all users). -M Op vr 1 sep. 2017 om 11:00

Actually, I do agree with you about Microsoft. But they have so many users that their terminology should not be ignored. Here are a few more views: https://www.ibm.com/support/knowledgecenter/ssw_aix_71/com.ibm.aix.performance/natl_lang_supp_locale_speed.htm https://docs.oracle.com/cd/E23824_01/html/E26033/glmbx.html

Just leave it, I think. Some nations have 4 national languages (as Martin will know), some languages are not national, and adopted children often do not speak their native (=born) language... I suspect someone already put a substantial amount of thought into the terminology. -pd > On 1 Sep 2017, at 09:45 , Martin Maechler <maechler at stat.math.ethz.ch> wrote: >

Hello, i'm a newbie of the really fantastic "R" , but have some problems to define Missing Values from Spss-Files which i import with the read.spss(data) command ! What should i do to recode i.e. the values 9,99 & 999 to NA. Something like this x <- c(9,99,999,NA) x==NA ...do not what i want, because the data.frame show the values 9,99 & 999 and not NA in this fields ?

Trey, The Compaq NC7770 PCI-X Gigabit Server Adapter supports PXE: http://www.compaq.com/products/servers/networking/NC7770/ This NIC will be available next month. Also, our strategy is to support PXE on all ProLiant server embedded NICs (10/100/1000) beginning with G2 (generation2) models. Also, most existing DL and all BL servers currently support PXE on their embedded (10/100) NICs. Let