similar to: qt with df<1 (repost)

Hello, The function qt returns NaN for degrees of freedom <1. For example: > qt(0.5,0.5) [1] NaN Warning message: In qt(p, df, lower.tail, log.p) : NaNs produced But qt(0.5,0.5) should be 0, since the distribution is symmetric. > pt(0,0.5) [1] 0.5 It actually fails with any value, as long as df<1. Is this a bug, or is there some fundamental reason why this cannot be computed?

Full_Name: Jens Lund Version: Version 1.7.0 (2003-04-16) OS: Win NT 4.0 SP 6 Submission from: (NULL) (193.3.225.210) As the T distribution is symmetrical around 0 qt(0.5,df) should return 0 for any df. However for df close to 1 it seems to have problems as seen by: qt(0.5,seq(1,1.1,by=0.0001)) For example: > qt(0.5,1.01) [1] -0.2300470 Higher df as df=1.1 (and up to approx df=1.7) seem

Full_Name: Gerard Torrent Version: R version 2.8.0 (2008-10-20) OS: Linux 2.6.27.5-41.fc9.x86_64 #1 SMP Submission from: (NULL) (85.52.227.233) In some cases qt complains about NaNs and don't gives the correct result: > qt(0.1,, 0.1) [1] NaN Warning message: In qt(p, df, lower.tail, log.p) : NaNs produced But the result can be found: > pt(-1.60443e+06, 0.1) [1] 0.09999997 If I

I was experimenting yesterday with a binomial make.link option for estimating student t binary response models, tentatively called gossit, and I noticed eventually that the R qt function doesn't like df < 1. Vaguely recalling that Splus didn't seem to mind such weirdness, I checked on our soon to be defunct Splus6.2 and sure enough, it produced plausible answers instead of R's

Dear developers, There's a small bug in print.fitdistr that can cause output to be printed twice, but only if print is called explicitly: > fit<-fitdistr(rt(1000,3),"t") There were 11 warnings (use warnings() to see them) > fit m s df -0.02181723 1.00145296 3.13723878 ( 0.03865057) ( 0.03999447) ( 0.33298377) > print(fit)

Hello, If I make a plot, say something simple like plot( runif(100) ) then the origin (0,0) is not at the bottom-left corner of the box surrounding the plot. The axis limits are "padded" slightly. This is ordinarily a good feature, because it makes plots look better. But now I would like to make a plot with the origin exactly on the bottom left. Through trial and error, I have

Hello, I'm learning to use Sweave, and I've run into a problem: sometimes, when entering long lines of input and using long variable names, Sweave will not insert linebreaks in a way that respects the width setting. This causes undesirable overflows into the margins in the latex file. For example, consider the following document (adapted from the GLM example): \documentclass{article}

Hello, I am trying to calculate and plot mean and confidence intervall for a set of data. This is the code that I am currently using: means <- sapply(data, mean, na.rm=TRUE) n <- sapply(data,length) stdev <- sqrt(sapply(data, var, na.rm=TRUE)) ciw <- qt(0.98, n) * stdev / sqrt(n) par(mgp=c(2,0.6,0), las=2, fin=c(7,3), mai=c(1,0.5,0.2,0.2), cex=0.8) plotCI(x=means, uiw=ciw,

help(qt) states that: "ncp non-centrality parameter delta; currently except for rt(), only for abs(ncp) <= 37.62" so I would expect that calling qt with non-centrality parameter exceeding 37.62 should fail, instead e.g. calling > mapply(function(x) qt(p = 0.9, df = 55, ncp = x),35:45) gives: [1] 40.21448 41.35293 42.49164 43.68862 44.82945 45.97048 47.11170 48.25310 [9]

.. checking for wnck_window_has_name... yes checking for METACITY... yes checking for Qt headers... /opt/qt/include checking for Qt libraries... no configure: creating ./config.status .. .. gnome: no kde: no .. I have tried to compile kde window decorator, but "configure" don't check my Qt installation and it don't have a option to specify the path. Thanks for your

Hi! It seems that i made some changes that make xconfig to not work .. the problem is that not matter what QTDIR i select i receive the same errors that start with : adrian at sevcenco: linux-2.6.37 $ make O=/home/adrian/kernel/kernel_out xconfig GEN /home/adrian/kernel/kernel_out/Makefile HOSTCXX scripts/kconfig/qconf.o /usr/lib64/qt4/include/Qt3Support/q3toolbar.h:45: error:

Hi, After a few modifications in the makefiles, I successfully compiled the Qt device (written by Deepayan Sirkar) for OS X 10.4.9 on a Powerbook. However when loading into R If i remove this line from zzz.R in qtutils/R grDevices::deviceIsInteractive("QT") and then install >library(qtutils) loads fine and the QT() calls returns a QT window, however, if i switch to

Hi, I have been playing with Qt recently, and have the beginnings of a Qt device. Unfortunately, I haven't been able to make it work as an R package yet (I know the device code works because I can use it from a GUI where R is embedded). Trying to package it, I have managed to get it to a stage where typing > library(qtdevice) > QT() will open up a new window, but then control

On 28/11/18 01:24, Akemi Yagi wrote: > On Tue, Nov 27, 2018 at 5:47 AM Toralf Lund <toralf.lund at pgs.com> wrote: >> I'm using CentOS 7 for development of software that is sometimes used on >> Red Hat Enterprise Linux 7. I conjunction with an update of one of the >> applications, I asked some Red Hat users to install the Qt 4 Assistant >> application via the

hi, i want to build a Qt front-end GUI which communicates with R, and i am not sure what i should use for the interface. There seems to be many ways: R.dll, Rinside, Rcpp, RQt, Rtools... . what is the best way? please advice. basically what i want to do is that, the Qt GUI will allow users to make selection and enter numbers, these inputs will be fed to R, already written .R files will perform

Hello, I am developing an application using Qt framework and C++. I want to use R as statistics engine of my application. After doing some search on internet; I came to the conclusion that RCPP, MPI with RInside is what I need. The next logical task was to quickly tryout "qtdensity" project of RInside, for understanding the build and other settings. I hit some roadblock here and got

Taking a look ahead at your QT (OSX version) work, you have Theora Encoding and Decoding on the list. This could be very beneficial as many times the only way to get a constant frame-rate out of QT is to export (and for DV video recorded in QT, this can be a large issue). Another major issue is that the video coming from DV (at least the sources I have used) is almost always

The solution post is here: http://lists.r-forge.r-project.org/pipermail/rcpp-devel/2012-November/004771.html In the paragraph: I did need however to install Rcpp and RInside from source, and with the same compiler used to compile qtdensity (otherwise I would get additional linker errors). As I had trouble getting the (Cygwin-based) g++ shipped with Rtools to work with Qt, I used instead the

I'm using CentOS 7 for development of software that is sometimes used on Red Hat Enterprise Linux 7. I conjunction with an update of one of the applications, I asked some Red Hat users to install the Qt 4 Assistant application via the qt-assistant package (which is used by a "help" function in our software.) It seemed like there was no such package in the Red Hat package set,

Hello, Everyone. Just few notes for everyone, who wants to build Qt with llvm. Everything was tested with shiny-new Qt 4.2.2 (X11 version) and llvm-gcc4 & LLVM from head. Instructions written here should also work on 1.9 release, as I've tested Qt build last time just before 1.9 release. 1. Specs Qt uses it's own configuration and build system called "qmake". We should