similar to: automatic SI prefixes as ticklabels on axis

Hi, i create two constants kilo and milli in [1]. These should be available after loading library(sitools) How should i export them and what have i done wrong? (Other suggestions for improving the package are welcome too) The ready to use .tar.gz and the source can be found on github [2,3] kind regatds, [1] https://github.com/jonasstein/sitools/blob/master/init.R [2]

Hi all, I am not exactly fluent in R and I got stuck with this. I would like to compare each elements of a vector A with any of the elements in Vector B. For some reasons it does not work. > StartDate = as.Date("01/10/2007", "%d/%m/%Y") > TimeSpan = seq(StartDate, by = 'days', length = length(myAverageCWVs$X1986)) > TickLabels = c("2007-10-01",

Hello, I've searched for help a lot and think I am close, but an still not able to place ticks and labels how I'd like in lattice's levelplot. I've come up with general reproducible code that gives the same problem as I'm having with real data: heat <- array(1:24,c(3,8)) require (lattice) ##basically I want a graph like this. depth y axis doesn't have ticks and

The Intel compiled version also fails the below test: > ###------------ Very big and very small > umach <- unlist(.Machine)[paste("double.x", c("min","max"), sep='')] > xmin <- umach[1] > xmax <- umach[2] > tx <- unique(outer(-1:1,c(.1,1e-3,1e-7)))# 7 values (out of 9) > tx <- unique(sort(c(outer(umach,1+tx))))# 11 values

Full_Name: Jörg Polzehl Version: 1.5.1 OS: Windows 2000 Submission from: (NULL) (193.175.148.198) When calculating MLE's in a variance component model using constrained optimization, i.e. optim(...,method="L-BFGS-B",...) I observed an inproper behaviour in cases where the likelihood function was evalueted at the constraint. Parameters and value of the function at the constraint

Hello, The following script allows for Weibull plots using R. Its output is similar to the output of the wblplot function (or weibplot function) in MATLAB. As opposed to the previously mentioned function it does not require proprietary software. Instead, it is based on R. My code also allows for a graphical visualization of weibull fitted data. In particular, data can be represented by a

How can I right justify the right-axis tick values? They appear in the example below as left-justified. I have tried several different ways and all fail in different ways. The example below creates the right axis tick value with no attempt at adjustment. alternates I have tried are 1. formatting the values. This doesn't work because they are in a proportional font and the blanks are too

Thank you, Clayton. It works now! Our debugger server responds "name:J28;generic:fp;bitsize:32;encoding:uint;format:hex;gcc:60;dwarf:60". And I also set other "generic" attributes like sp, pc, ra, arg1~arg8 to related registers. I dig a little and find llvm dwarf generator uses TargetRegisterInfo::getFrameRegister() to obtain frame base, and uses

Thank you, Clayton. This is very helpful. We use the LLDB specific GDB remote extensions, and our debugger server supports "qRegisterInfo" package. "reg 0x3c" is the frame pointer. In the example mentioned above, we have SP = FP - 40 for current call frame. And variable "a" is stored at address (FP + -24) from asm instruction [FP + -24] = R3;; Thus we can conclude

I have a Master's student working on a project which involves estimating parameters of a certain model via maximum likelihood, with the maximization being done via optim(). A phenomenon has occurred which I am at a loss to explain. If we use certain pairs of starting values for optim(), it simply returns those values as the ``optimal'' values, although they are definitely not