search for: laterally

Displaying 20 results from an estimated 36131 matches for "laterally".

Did you mean: lateral
2010 Jul 28
1
Help with specifiying random effects in lmer - psychology experiment
<!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4; mso-font-charset:0; mso-generic-font-family:roman; mso-font-pitch:variable; mso-font-signature:-1610611985 1107304683 0 0 159 0;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable;
2016 Jan 25
2
Version of SFTP
The link http://www.greenend.org.uk/rjk/sftp/sftpversions.html On Mon, Jan 25, 2016 at 11:07 AM, Maria Shalet <mshalet at gmail.com> wrote: > Dear Developers, > In the Open SSH package, we have only V3 of sftp. Here the > mode of transfer is only binary. > > According to the below link I find there are later versions > of the SFTP protocol that
2013 Sep 19
2
[LLVMdev] [Polly] Move Polly's execution later
Hi Tobias, I am trying to move Polly later. LLVM provides some predefined ExtensionPointTy: EP_EarlyAsPossible, EP_ModuleOptimizerEarly, EP_LoopOptimizerEnd, EP_ScalarOptimizerLate, ... Currently Polly uses "EP_EarlyAsPossible" to run as early as possible. As what you suggested: >Instead of removing canonicalization passes, I believe we may want to >move
2013 Sep 19
0
[LLVMdev] [Polly] Move Polly's execution later
On 09/19/2013 04:46 PM, Star Tan wrote: > Hi Tobias, > > > I am trying to move Polly later. > > > LLVM provides some predefined ExtensionPointTy: > EP_EarlyAsPossible, > EP_ModuleOptimizerEarly, > EP_LoopOptimizerEnd, > EP_ScalarOptimizerLate, > ... > > > Currently Polly uses "EP_EarlyAsPossible" to run as early as
2008 Aug 08
2
[LLVMdev] llvm.org: out of disk space?
I just tried to update a bugzilla PR, and got the following unpleasant message: > Insufficient disk space; try again later Insufficient disk space; > try again later returntosender: cannot select queue for bugzilla- > daemon Insufficient disk space; try again later returntosender: > cannot select queue for postmaster putbody: write error: No space > left on device Error
2004 Aug 04
1
pxelinux (2.08 or later) on VMware
Hi, pxelinux(2.08 or later) waits forever after "boot:" prompt on vmware (4.52). pxelinux(2.07) works. After I comment out DO_IDLE in ui.inc (2.08 or later), it works. but I'm not sure why... (vmware bug?) Thanks, Kaz --- ui.inc.orig Wed Aug 4 00:58:38 2004 +++ ui.inc Wed Aug 4 01:07:39 2004 @@ -60,7 +60,7 @@ cmp dx,ax ; Has the timer
2020 Jan 15
2
Phabricator -> GitHub PRs?
On Wed, 15 Jan 2020 at 23:19, David Blaikie <dblaikie at gmail.com> wrote: > I don't think creating a new thread (or series of N threads) because an early patch in a series necessitate some refactoring of later patches is ideal - while patch series can/should be avoided where reasonable (& if the series is small enough/the framing/design is obvious enough, you can hold on to the
2009 Dec 28
10
samba 3.3 for opensuse 10.2
Hallo and Merry Christmas to all! I need the rpm-files of samba 3.3 or later for opensuse 10.2. The repo isn?t available any more, so can anybody help me here? Thanks in advance! Peter
2019 Jan 23
4
Curl spec file
Hi, I saw this spec file for curl-7.29: https://git.centos.org/blob/rpms!curl.git/c7/SPECS!curl.spec And was wondering if you have one for a later version. And if not, how hard is it to modify the existing one to support later versions. Thanks! Roee.
2012 Aug 21
1
Error: ReadItem: unknown type 98, perhaps written by later version of R
Hi, I am running a large number of jobs (thousands) in parallel (linux OS 64bit), R version 2.14.1 (2011-12-22), Platform: x86_64-redhat-linux-gnu (64-bit). Up to yesterday everything ran fine with jobs in several blocks (block1, block2 etc) of submission. They are sent to an LSF platform to handle the parallel submission. Today I see that only one of the blocks (the 19) has not finished
2006 Nov 25
3
[LLVMdev] Zion Out Of Disk Space!
All, Commits aren't taking right now because apparently Zion is out of disk space: cvs commit utils/findmisopt Checking in utils/findmisopt; /var/cvs/llvm/llvm/utils/findmisopt,v <-- findmisopt new revision: 1.9; previous revision: 1.8 done Insufficient disk space; try again later Insufficient disk space; try again later returntosender: cannot select queue for llvm Insufficient disk
2004 Nov 16
2
R 2.0.0 Installation Problem
I and my students have been having an odd problem with this release, which is that packages are disappearing. After installation the package is found with the library command, but later in the same session or in a later session, the library command returns a not found error. Then later it is back. Happening on both Windows and OS X, mostly but not entirely with Bioconductor packages. David
2015 Jun 10
2
[LLVMdev] should InstCombine preserve @llvm.assume?
Hi, I have some WIP that leverages @llvm.assume in some optimization passes other than InstCombine. However, it doesn't work yet because InstCombine removes @llvm.assume calls that are useful for later optimizations. For example, given define i32 @foo(i32 %a, i32 %b) { %sum = add i32 %a, %b %1 = icmp sge i32 %sum, 0 call void @llvm.assume(i1 %1) ret i32 %sum } "opt
2010 Jan 20
2
[LLVMdev] [LLVMDev] Is it possible to implement target specific optimizations which can be applied after instruction selection or later?
Dear developers. My question is the same as the title. Is there any way to implement target specific optimizations after instruction selection or later? I cannot find any related document. Please let me know. Thanks in advance. Minwook Ahn -------------- next part -------------- An HTML attachment was scrubbed... URL:
2010 Feb 16
1
megatec_usb[17249]: Reconnecting to UPS failed; will retry later
after I starting battery test on my laptop I see in my logs some error and ups (IPPON Smart Power Pro 1400. usb interface) isn't monitoring now [ippon] driver = megatec_usb port = auto desc = "local" Feb 16 23:22:09 f37 upsd[17150]: Instant command: stlk at 127.0.0.1 did test.battery.start on ippon Feb 16 23:22:12 f37 megatec_usb[17249]: ser_get_line: Device detached? (error
2004 May 23
2
Re: problem and maybe bug in 2.08 and later with vmware 4.5.1
>I found a problem with pxelinux in 2.08 and 2.09pre13 when working with >vmware 4.5.1 (the latest with builtin support fpr pxe-boot). With 2.07 and >2.01 it works without problems. But when trying the later versions there is >trouble. I reach pxeboot.msg >and it shows fine but when I try to choose an image it dosent give keyboard >feedback (first I thought it had hanged) but
2003 Sep 28
6
NAT/SIP solution?
Greetings, I was wondering if somebody is working on a solution to the NAT/SIP-issues? It seems to me that the problem has been identified, is that correct? Just hoping that someone with more skills will provide us with a solution sooner or later... Regards, Stig -------------- next part -------------- An HTML attachment was scrubbed... URL:
2012 May 12
5
Help with writing data to csv
I am trying to write data to csv but I am having issues with the separations. Basically I have some results that I get with R that I copied and pasted into word and then saved as .txt I want to write the results to csv because it's easier to make tables in word (all I would have to do is copy and paste into a table, instead of typing everything out). I am able to write the data to the
2013 Jan 08
15
[LLVMdev] Using C++'11 language features in LLVM itself
It's seems like a quiet and peaceful day, lets stir things up a bit :) How crazy would it be for us to start using basic C++'11 language features (but not C++'11 library features) in LLVM: things like auto, rvalue-refs, lambdas, etc? I think that we can keep things well defined with a few simple requirements: language features must be supported by MSVC 2010 and later, some version of
2015 Dec 03
4
7.2 kernel panic on boot
On 03/12/2015 13:33, Jonathan Billings wrote: > On Thu, Dec 03, 2015 at 09:29:21AM +0000, Duncan Brown wrote: >> Hi All >> >> After upgrading to 7.2, I'm getting an immediate kernel panic on boot >> >> Dropping back to 3.10.0-229.20.1.el7.x86_64 and the system boots fine >> >> How can I go about diagnosing the problem here? > It'd probably