similar to: Extracting factor columns from a data frame

Displaying 20 results from an estimated 6000 matches similar to: "Extracting factor columns from a data frame"

2005 Mar 09
4
[LLVMdev] Recursive Types using the llvm support library
----- Original Message ----- From: "Chris Lattner" <sabre at nondot.org> To: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> Sent: Tuesday, March 08, 2005 6:31 PM Subject: Re: [LLVMdev] Recursive Types using the llvm support library > On Tue, 8 Mar 2005, Vladimir Merzliakov wrote: > >>>> An example where something really simple like the
2009 Nov 16
1
extracting values from correlation matrix
Hi! All, I have 2 correlation matrices of 4000x4000 both with same row names and column names say cor1 and cor2. I have extracted some information from 1st matrix cor1 which is something like this: rowname colname cor1_value a b 0.8 b a 0.8 c f 0.62 d k 0.59 - - -- -
2004 Jun 24
0
[LLVMdev] Using -noexternals option of NightlyTest.pl
On Thu, 24 Jun 2004, Vladimir Merzliakov wrote: > > check out the tree over anon cvs yet. Reid do you know? > :pserver:anon at llvm-cvs.cs.uiuc.edu:2401/var/cvs/llvm work for me > > Waiting test results... Great! It might take a while. The tester takes about 6 hours to run on a 2proc 3.0ghz Xeon box :) But that's with spec95/2k and povray included. -Chris --
2004 Jun 24
1
[LLVMdev] Using -noexternals option of NightlyTest.pl
> On Thu, 24 Jun 2004, Vladimir Merzliakov wrote: > > > At this moment I use > > "gmake TEST=nightly" command line to run night tester > > > > What I must specific and where to disable SPEC run (i don't have it) > > I think that it's currently a bug that this does not automatically happen. > > > I known about new NightlyTest.pl option:
2004 Jun 25
0
[LLVMdev] Using -noexternals option of NightlyTest.pl
On Fri, 25 Jun 2004, Vladimir Merzliakov wrote: > Result night tester run at FreeBSD 5.1 accessable by URL > http://npt.cc.rsu.ru/testresults-X86-FreeBSD/index.html > I can't guaranty run it per day base, sorry. Okay, sounds great. I added it to the page with a note to that effect: http://llvm.cs.uiuc.edu/testresults/ Thanks a lot for volenteering to run it. Also, if you notice
2004 Nov 02
0
[LLVMdev] Problems with nighttest FeatureTests
Vladimir Merzliakov wrote: > Hi! > > As I can see all nighttesters listed at > http://llvm.cs.uiuc.edu/testresults/ have problem with > FeatureTests at 2004-11-01/2004-11-02 test run. > > In my case i manualy terminate nighttest script after 12 hours work. > > It problem resolved? > > Vladimir Hi Vladimir, I assume you're talking about the FreeBSD run.
2004 Nov 02
2
[LLVMdev] Problems with nighttest FeatureTests
> Vladimir Merzliakov wrote: > >> Hi! >> >> As I can see all nighttesters listed at >> http://llvm.cs.uiuc.edu/testresults/ have problem with >> FeatureTests at 2004-11-01/2004-11-02 test run. >> >> In my case i manualy terminate nighttest script after 12 hours work. >> >> It problem resolved? >> >> Vladimir > > Hi
2004 Nov 08
0
[LLVMdev] Dejagnu Support Added (+ problems with build LLVM at FreeBSD)
On Mon, 2004-11-08 at 00:16, Vladimir Merzliakov wrote: > > I'm asking for people (especially those running nightly testers) to give > > Dejagnu a try. > > I will do. > > But last 2 days (after > http://mail.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20041101/020279.html ) > LLVM broken at FreeBSD: > > In file included from Path.cpp:27: >
2004 Dec 01
0
[LLVMdev] Outdated information in CFEBuildInstrs.html
Vladimir Merzliakov wrote: > http://llvm.cs.uiuc.edu/docs/CFEBuildInstrs.html have lines: > > Add the directory containing the tools to your PATH. > % set path = ( `cd llvm/tools/Debug && pwd` $path ) > > In my LLVM object directory at LLVM build (obj != src) > obj/tools/Debug don't exist (instead exist obj/Debug) > > Also i recheck obj == src case with same
2005 Mar 08
0
[LLVMdev] Recursive Types using the llvm support library
On Tue, 8 Mar 2005, Vladimir Merzliakov wrote: >>> An example where something really simple like the line below was output >>> would be perfect. >>> >>> %struct.linked_list = type { %struct.linked_list*, %sbyte* } >> >> Use something like this: >> >> PATypeHolder StructTy = OpaqueType::get(); >> std::vector<const
2005 Mar 09
0
[LLVMdev] Recursive Types using the llvm support library
On Wed, 9 Mar 2005, Vladimir Merzliakov wrote: > I create test program and assert failed in it: > > { \2 *, sbyte * } > Assertion failed: (!NewSTy->isAbstract()), function main, file > /usr/home/wanderer/work/LLVMTest/obj/../src/tools/tool/Test.cc, line 28. > > Testcase source attached. Thanks, that definitely is a bug. Patch here:
2005 Mar 10
1
[LLVMdev] new llvm-testresults mailing list
On Thu, 2005-03-10 at 04:13, Vladimir Merzliakov wrote: > Also I found some inconsistent at http://llvm.cs.uiuc.edu/testresults/ page: > all hardware platform names is bold except Alpha. Really? Are you sure? ;) Andrew
2005 Mar 21
0
[LLVMdev] Recursive Types using the llvm support library
On Wed, Mar 09, 2005 at 04:05:32PM +0300, Vladimir Merzliakov wrote: > >>Is assert(!NewSTy->isAbstract()) must pass after this line? > > > >In this case, yup. > > > I create test program and assert failed in it: > > { \2 *, sbyte * } How do I decode the \2 in this? I am creating types through this interface and I get quite a mess seen below. And this is
2004 Sep 05
3
[LLVMdev] POST MORTEM: llvm-test changes
Okay, I'll have to fix NightlyTest.pl not to use shell script syntax that isn't universal. Look for a commit soon. Reid. On Sun, 2004-09-05 at 13:31, Vladimir Merzliakov wrote: > > Bash 2.05b on Linux handles this fine. I was asking what > > your "default" system shell is on FreeBSD. Probably /bin/sh, right? > > Perhaps you can: > > > >
2004 Jun 24
0
[LLVMdev] Using -noexternals option of NightlyTest.pl
On Thu, 24 Jun 2004, Vladimir Merzliakov wrote: > At this moment I use > "gmake TEST=nightly" command line to run night tester > > What I must specific and where to disable SPEC run (i don't have it) I think that it's currently a bug that this does not automatically happen. > I known about new NightlyTest.pl option: -noexternals > But what I must do for
2005 Mar 21
2
[LLVMdev] Recursive Types using the llvm support library
On Sun, 20 Mar 2005, John Carrino wrote: > On Wed, Mar 09, 2005 at 04:05:32PM +0300, Vladimir Merzliakov wrote: >>>> Is assert(!NewSTy->isAbstract()) must pass after this line? >>> >>> In this case, yup. >>> >> I create test program and assert failed in it: >> >> { \2 *, sbyte * } > > How do I decode the \2 in this? I am
2004 Sep 05
2
[LLVMdev] POST MORTEM: llvm-test changes
Actually, I'm talking about the shell that Perl invokes. When you run the NightlyTest.pl script, it uses Perl. The system() function in Perl invokes the "standard" shell to execute the command provided as the argument to system(). In NightlyTest.pl, I have changed the program to check out both the regular llvm CVS module as well as the llvm-test module. This command is what is
2007 Jan 05
3
Dovecot's deliver trouble (...probably bug?)
Hello everybody! I am a Linux admin trying to move my mail system based on qmail to the software which is more spam-protected: exim4 + dovecot-1.0rc15 + pgsql . I've downloaded and rebuild dovecot from src.rpm (for fc4). During the testing stage I've discovered two troubles: 1) the problem with deliver (...I'm not sure it's a really bug). Here is relevant part of my
2004 Nov 03
2
[LLVMdev] Problems with nighttest FeatureTests
I think there is a very similar situation with the PowerPC/Mac OS X nightly tests. Over each of the past few nights, something has been filling up the process table, causing me to be unable to log in. The nightly tester wrote out regression test and feature test logs featuring hundreds of "Resource temporarily unavailable" errors from fork(), so I assume it's the qmtest
2017 Jan 26
2
Critical XRay fixes for Arm32
I'm wondering why the lit tests didn't catch this as part of testing rc1 on ARM. On Thu, Jan 26, 2017 at 11:25 AM, Serge Rogatch <serge.rogatch at gmail.com> wrote: > XRay is tested automatically on build-bots with tests in LLVM and > compiler-rt . Or are you asking for manual testing instructions? > Of these 2 patches, the compiler-rt patch depends on LLVM patch because