similar to: R: one bananna aov() question

Hi, I am stuck on something for a couple days, I am almost about to give up. This looks simple, but I can't figure out. I hope I can get some help here. I am trying to do some symbolic and numerical derivations. Let me explain the problem. Let's say, I have a matrix as follows: > load <- matrix(c(3,0,1,4,1,3),nrow=3,ncol=2,byrow=TRUE) > > load [,1] [,2] [1,] 3 0

I'm using specify.model for the sem package. I can't figure out how to represent the residual errors for the observed variables for a CFA model. (Once I get this working I need to add some further constraints.) Here is what I've tried: model.sa <- specify.model() F1 -> X1,l11, NA F1 -> X2,l21, NA F1 -> X3,l31, NA F1 -> X4,l41, NA F1 -> X5, NA, 0.20

This will be a git feature in git 2.23 (in Q3 2019). It will allow git blame to ignore revisions with --ignore-rev, which the user can even specify in their git config. Relevant git blame documentation change: https://github.com/git/git/blob/ae3f36dea16e51041c56ba9ed6b38380c8421816/Documentation/blame-options.txt#L113-L125 Relevant git config documentation change:

Hi, I tried compiling llvm-gcc front end by giving the configure commands : $ ../llvm-gcc4-2.0.source/configure --enable-checking --enable-languages=c --target=arm-none-linux But I am getting the following kind of assembeler errors when I do "make $BUILDOPTIONS" /tmp/ccYAgFFY.s: Assembler messages: /tmp/ccYAgFFY.s:36: Error: junk at end of line, first unrecognized character is

Hi, In sanitizer code we have two notions of stack unwinders: fast and slow. [1] In the context of sanitizers, stack unwinding is most often for printing error reports that include a stack trace. I am currently trying to fix an issue that is related to some platforms (Darwin) only supporting the fast unwinder, but calling code not being aware of that possibility. My mental model was that

On Tue, Jun 20, 2017 at 05:04:53PM +0300, Pavel Butsykin wrote: > I noticed that raw is intentionally used as image format for appliance > image. So I would like to ask, is there any reason to use raw as image > format for appliance? The simple answer is because we create the appliance image (it's an ext2/3/4 filesystem) using e2fsprogs, and that library wouldn't know how to

On Tue, Jun 20, 2017 at 06:34:28PM +0300, Pavel Butsykin wrote: > On 20.06.2017 17:47, Richard W.M. Jones wrote: > >On Tue, Jun 20, 2017 at 05:04:53PM +0300, Pavel Butsykin wrote: > >>I noticed that raw is intentionally used as image format for appliance > >>image. So I would like to ask, is there any reason to use raw as image > >>format for appliance? >

On Tue, Jun 20, 2017 at 06:48:16PM +0300, Pavel Butsykin wrote: > On 20.06.2017 18:41, Richard W.M. Jones wrote: > >On Tue, Jun 20, 2017 at 06:34:28PM +0300, Pavel Butsykin wrote: > >>On 20.06.2017 17:47, Richard W.M. Jones wrote: > >>>On Tue, Jun 20, 2017 at 05:04:53PM +0300, Pavel Butsykin wrote: > >>>>I noticed that raw is intentionally used as image

Thank you for the explanation, Ben! I realized I didn’t give enough context for my question: As you noted, the slow/fast unwinder can only do its work if there is enough (runtime) information. Otherwise stack printing usually does exactly what you suggested: printing the one frame corresponding to the recent pc. When I asked if “platforms are required to at least support one kind of unwinder” I

Hey gang. Jed noticed an issue with the ''dependency''/''dependencies'' macro the other day when working on the Collective wiki. Namely, if you make RedCloth a dependency Merb gets a little cranky. I think I have this figured out when doing some mods to Collective today too. However, before I go trying to fix this in Merb, I wanted to run this by the community.

1. A program can use SSE instructions only if both CPU and OS support SSE. Currently libFLAC tests both CPU and OS for this support, but is it really necessary? Maybe CPU check is enough? Operating systems that don't support SSE (Win95, WinNT 4.0, Linux kernel 2.2 (iirc), ...) are really outdated now. Removing OS check will greatly simplify src/libFLAC/cpu.c. 2. "configure" build

On 9 January 2015 at 11:46, Martin Maechler wrote: | (I've seen .. but not investigated other cases where Travis | would barf about things that were fine for me). I often file that under "Travis has a screw loose for sticking with Ubuntu 12.04". It's a fantastic service, but it has its warts. "Word" is that at some point they'll switch to a new release "at

Erik de Castro Lopo wrote: > lvqcl.mail wrote: >> now. Removing OS check will greatly simplify src/libFLAC/cpu.c. > > That makes sense. Should I post a patch that removes OS check and keeps only CPU check? >> 2. >> "configure" build system adds -msse2 option by default. It means that >> x86 (32-bit) library won't work on older, non-SSE2

Hi folks, Here is the current interface: sink(file=NULL, append=FALSE, type = c("output", "message"), split=FALSE) However, reading the implementation there is implicit assumption that type is a single character value: https://github.com/wch/r-source/blob/trunk/src/library/base/R/sink.R#L23 I'm finding this very confusing as the interface is giving a default value of a

On Tue, Jul 12, 2016 at 04:48:06PM +0800, Baochuan Wu wrote: > Thanks Pino for quick response. > Actually I use the libguestfs APIs in C++ program. Following your idea, I > think I should try guestfs_set_network for this. Yes this is correct. Calling: guestfs_set_network (g, 1); should enable the network inside the appliance. For further tips on using yum, have a look at how

Hi, I'm using SparkR and R won't read the promises from the SparkR package, only if I run lazyLoad manually. .libPaths(c(file.path(Sys.getenv("SPARK_HOME"), "R", "lib"), .libPaths())) print(.libPaths()) # [1] "/private/tmp/spark-1.5/spark-1.5.0-SNAPSHOT-bin-hadoop2.6/R/lib" # [2] "/usr/local/lib/R/3.2/site-library" # [3]

Hi Logan/All, I have added a check for the sg_dma_len == 0 : """ } __sgt_iter(struct scatterlist *sgl, bool dma) { struct sgt_iter s = { .sgp = sgl }; + if (sgl && sg_dma_len(sgl) == 0) + s.sgp = NULL; if (s.sgp) { ..... """ at location [1]. but it doens't fix the problem. You're right though, this

The logs here: > checking for python... /opt/python/x86_64/3.1.1/bin/python3 > checking Python version... 3.1 > checking for PYTHON... no > checking for PYTHON... no > checking Python prefix... /opt/python/x86_64/3.1.1 > checking for Python site-packages path... /opt/python/x86_64/3.1.1/lib/python3.1/site-packages > checking for Python extension suffix (PEP-3149)... .so >

lvqcl.mail wrote: > 1. > A program can use SSE instructions only if both CPU and OS support SSE. > Currently libFLAC tests both CPU and OS for this support, but is it really > necessary? Maybe CPU check is enough? Operating systems that don't support > SSE (Win95, WinNT 4.0, Linux kernel 2.2 (iirc), ...) are really outdated > now. Removing OS check will greatly simplify

On Wed, Feb 7, 2018 at 12:01 PM, Ville Syrjälä <ville.syrjala at linux.intel.com> wrote: > On Wed, Feb 07, 2018 at 06:28:42PM +0200, Ville Syrjälä wrote: >> On Sun, Feb 04, 2018 at 06:50:45PM -0500, Ilia Mirkin wrote: >> > In case anyone's curious about 30bpp framebuffer support, here's the >> > current status: >> > >> > Kernel: >>