search for: l11

...matrix, and assign the matrix elements to these objects. These objects will be also an element of another matrix. l <- matrix(nrow=nrow(load),ncol=ncol(load)) for(i in 1:nrow(load)) { for(j in 1:ncol(load)) { l[i,j]=paste("l",i,j,sep="")}} > l [,1] [,2] [1,] "l11" "l12" [2,] "l21" "l22" [3,] "l31" "l32" > l11 [1] 3 > l12 [1] 0 > l21 [1] 1 > l22 [1] 4 > l31 [1] 1 > l32 [1] 3 Let's say, I need to take the derivative of (l11*l21+l12*l22) with respect to l11,l12,l21,l22,l31,l32. &g...

...lwut.s ---- lolwut.s ---------------------------- .file "lolwut.bc" .text .globl lolwut .align 2 .type lolwut,%function lolwut: @ @lolwut .fnstart @ BB#0: @ %entry @APP ldr r1, .Ltmp0 .align 2 .Ltmp0: .long ".L11" ".L11": @NO_APP bx lr .Ltmp1: .size lolwut, .Ltmp1-lolwut ------------------------------------------ Somehow, the forward referenced label at 1: in the original assembly is getting mangled when its constant pool entry is created (the bad character is a 0x02 hex). In previou...

Hi everyone thanks for the replies. The issue was NOT a font problem; I deliberately chose ll1 and l11 as examples of easily confused variable names (evidently these were too easily confused ;-). The code snippet was written as intended, and increment() contained a deliberate, highlighted, bug. I was asking for guidance on avoiding/finding this sort of coding error. That was why I wrote "#bu...

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 F2 -> X1,l12, NA F2 -> X2,l22, NA F2 -> X3,l32, NA F2 -> X4,l42, NA F2 -> X6, NA, 0.25 F1 <-> F2,g12, 1 F1 <-> F1,g11, 1 F2 <-> F2,g22, 1 X...

Hi I recently found a bug that was isomorphic to the following: ll1 <- 2 increment <- function(x) { l11 <- 1 return(x+ll1) #bug here } Of course, R is obeying the scoping rules just fine, but I'm evidently not setting the do.what.I.mean.not.what.I.say variable correctly. Now, how do I avoid making this type of error? ... and what is the best tool for tracking it down? -- Robin Hankin...

...just avoid in our specs? I noticed, for example, that one of our projects consistently segfaulted on this line: /vendor/plugins/rspec/lib/spec/mocks/message_expectation.rb:41: [BUG] Segmentation fault Any pointers greatly appreciated. cheers, Matt [1]http://eigenclass.org/hiki/rcov+FAQ#l11 [2]http://eigenclass.org/hiki/rcov-0.8.1 ---- http://blog.mattwynne.net http://songkick.com In case you wondered: The opinions expressed in this email are my own and do not necessarily reflect the views of any former, current or future employers of mine. -------------- next part ----------...

...s to write classes, using S3 ou S4 models. And it seems that S4 is the best model, so I thing I should use this one. I´m new user of R and I´m searched on the net some information about creating new classes. I found this document: http://www.biostat.harvard.edu/courses/individual/bio271/lectures/L11/S4Objects.pdf If someone knows some docs about creating our own classes, could please, post its url at here ? More one question... It seems that some documents about S can be applyed to R. How do you know if you can use this documentation using R ? I´m asking this because some stufs I was looking...

....voltage returned by the UPS is a constant 24.0 V, regardless of the actual battery voltage. Here's what I was thinking of: https://github.com/networkupstools/nut-ddl/blob/8995562a0253e980d36f6bdddfe09c9f2c866657/Cyber_Power_Systems/Cyber_Power_Systems__CP1500PFCLCD__usbhid-ups__2.7.1__01.dev#L11-L13 "CyberPower states that battery voltage is not supported in this model of UPS. [CP1500PFCLCD; circa 2014] It's not even shown in their 'PowerPanel' software."

Hi, looking through the key specification, you can see that its the second field in the key file: https://github.com/openssh/openssh-portable/blob/master/PROTOCOL.key#L11 It looks like there is no convenient way to get this information with openssh cli, but given that the file format is just base64 encoded, you can read it out with something like this: $ cat /tmp/rsa | head -n -1 | tail -n +2 | base64 -d | hexdump -C | head -n 2 00000000 6f 70 65 6e 73 73 68 2d...

...-2.71 2.26 -1.11 ... $ y.l6 : num NA NA NA NA NA NA -0.21 -2.28 -2.71 2.26 ... $ y.l7 : num NA NA NA NA NA NA NA -0.21 -2.28 -2.71 ... $ y.l8 : num NA NA NA NA NA NA NA NA -0.21 -2.28 ... $ y.l9 : num NA NA NA NA NA NA NA NA NA -0.21 ... $ y.l10: num NA NA NA NA NA NA NA NA NA NA ... $ y.l11: num NA NA NA NA NA NA NA NA NA NA ... $ y.l12: num NA NA NA NA NA NA NA NA NA NA ... I have: > insample <- 1:179 > outsample <- 180:191 To help you see what is going on: > D[outsample,] y y.l1 y.l2 y.l3 y.l4 y.l5 y.l6 y.l7 y.l8 y.l9 y.l10 y.l11 y.l12 180 NA 8.81 8.53 5....

Hi, the attached example works with bfd-ld and with gold, but not with lld: $ cat rodatareloc.s ... .align 16 leaq .JTab(%rip), %r10 jmp *(%r10, %rdx, 8) ... .section .rodata .JTab: .quad .L00, .L01, .L02, .L03, .L04, .L05, .L06, .L07 .quad .L08, .L09, .L10, .L11, .L12, .L13, .L14, .L15, .L16 $ gcc -o rodatareloc.s.o -c rodatareloc.s $ lld -o rodatareloc.so -shared rodatareloc.s.o ld: error: rodatareloc.s.o:(.rodata+0x0): can't create dynamic relocation R_X86_64_64 against local symbol in readonly segment defined in rodatareloc.s.o Changing the sect...

On Monday 04 January 2010 05:16:40 Jeffrey Yasskin wrote: > On Sun, Jan 3, 2010 at 10:50 PM, Jon Harrop <jon at ffconsultancy.com> wrote: > > LLVM's TCO already handles mutual recursion. > > Only for fastcc functions Yes. > compiled with -tailcallopt, right? If you use the compiler, yes. > http://llvm.org/docs/CodeGenerator.html#tailcallopt > > I believe

On Sun, Jan 3, 2010 at 10:50 PM, Jon Harrop <jon at ffconsultancy.com> wrote: > On Monday 04 January 2010 03:33:06 Simon Harris wrote: >> On 04/01/2010, at 3:01 PM, Jon Harrop wrote: >> > I am certainly interested in tail calls because my HLVM project relies >> > upon LLVM's tail call elimination. However, I do not understand what tail >> > calls LLVM

...br label %l2 <snip> I get the following error: llvm-as: test.ll:578,0: test.ll:578: error: syntax error, unexpected LABELSTR, expecting LOAD or STORE while reading token: 'l6:' Why is this label unexpected? Situation 2: More than 1 label is used to refer to the same location (l11 in this case): <snip> PredicateEqualZero3: br label %l1 PredicateNotEqualZero3: l11: l2: ret i32 1 <snip> I get the same error: llvm-as: test.ll:706,0: test.ll:706: error: syntax error, unexpected LABELSTR, expecting LOAD or STORE while reading token: 'l11:' If this...

Hi, On LLVM 5.0 (current trunk), fadd/fsub and fmul that are both marked with `contract` or `fast` can be merged to a fma instruction by the backend. I'm wondering about the exact semantic of this new flag as well as `fast` and in particular, would it be valid to do this when only the `fadd`/`fsub` (and not the `fmul`) is marked with `contract` or at least `fast`. The reasoning is that doing

Hello, I didn't give enough information when I sent an query before, so I'm trying again with a more detailed explanation: In this data set, each patient has a different number of measured variables (they represent tumors, so some people had 2 tumors, some had 5, etc). The problem I have is that often in later cycles for a patient, tumors that were originally measured are now missing (or

...is a constant 24.0 V, regardless of > the actual battery voltage. > > Here's what I was thinking of: > > > https://github.com/networkupstools/nut-ddl/blob/8995562a0253e980d36f6bdddfe09c9f2c866657/Cyber_Power_Systems/Cyber_Power_Systems__CP1500PFCLCD__usbhid-ups__2.7.1__01.dev#L11-L13 > > "CyberPower states that battery voltage is not supported in this model of > UPS. [CP1500PFCLCD; circa 2014] > It's not even shown in their 'PowerPanel' software." -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://ali...

Hello, I have made a new version of NHW.This one has more neatness and more precision for -l4 to -l11 quality settings, which are the general-purpose compression settings.It is actually just one parameter better tuning based on my visual evaluations (no real new developments... it was 14 months now that I did not develop the NHW Project...). Files size is just a little bigger, but we can still sav...

On Mon, 22 Jan 2024, Jakub Jelen wrote: > Hi, > looking through the key specification, you can see that its the second > field in the key file: > > https://github.com/openssh/openssh-portable/blob/master/PROTOCOL.key#L11 > > It looks like there is no convenient way to get this information with > openssh cli, but given that the file format is just base64 encoded, > you can read it out with something like this: > > $ cat /tmp/rsa | head -n -1 | tail -n +2 | base64 -d | hexdump -C | head -n 2 >...

I'm writing some code that does a bit of introspection of R6 classes and am wondering about the "classname" parameter. Its the first parameter to the "R6Class" class generator generator function, and the few examples I've looked at on CRAN set it the same as the name of the generator function, for example, from the docs: Queue <- R6Class("Queue", .....)