00:02:06 @ http://www.bartleby.com/61/17/C0621700.html 00:02:13 A: cool. The American Heritage® Dictionary of the English Language: Fourth Edition. 2000. from sbp 00:02:30 A:|Bartleby takes on the word "cool" 00:02:32 titled item A 00:02:36 bijan (bparsia@login7.isis.unc.edu) has joined #swhack 00:02:48 A::"""Jazz musicians who used the term are responsible for its popularization during the 1940s. As a slang word expressing generally positive sentiment, it has stayed current (and cool) far longer than most such words.""" 00:02:50 commented item A 00:02:52 wb, bijan 00:02:57 *** bijan has quit IRC ("Leaving") 00:02:57 wow, he leaves really abruptly :-) 00:02:57 last time, I thought I'd pissed him off or something 00:05:23 How's your clone coming? 00:05:32 I haven't really worked on it all that much 00:05:46 I don't quite understand it's limitations and capabilities. 00:05:47 I've been distracted with lots of annoying little things, that I can't even remember doing 00:05:57 that's alright: neither do I 00:06:02 Heh. 00:06:15 Have you benched against CWM? 00:06:46 I'm too scared to. Actually, rm ran a large query through it, and it sat there for like ten minutes before he crashed it. CWM ran it in under 5 seconds 00:06:54 Heh. 00:06:56 Oh well. 00:07:08 Get Computing with logic 00:07:37 ah, that's what you recommended to me before... well, next time I splurge on some books :-) 00:08:01 Hmm... I need a place to scrawl such things. The problem is, give me ten minutes and I will have forgotten it 00:08:20 did you write your own n3 parser? 00:08:24 OTOH, it's in the #swhack logs now, and I'm used to salvaging various bits of junk from there 00:08:27 or crib on of dan's? 00:08:28 own N3 parser: yep 00:08:41 nope, it's 100% "me". i.e., not all that good 00:08:45 Hand rolled or did you use a generator/framework. 00:08:54 How are you storing triples? 00:09:01 hand rolled. Python has good RegExping stuff... 00:09:06 Bah. 00:09:10 storing triples: in a Python list 00:09:14 Ouch. 00:09:17 that will *kill* you. 00:09:24 it works remarkable smoothly 00:09:33 pff: remarkably 00:10:02 of course, I could just extend the built-in Python list type if I wanted too 00:10:51 *really* bad idea 00:10:52 because really, the store classes that I've seen in other Python APIs are just wrappers for lists. A store is really just a list, with some fancy "add" methods and whatnot 00:11:04 eek. 00:11:05 how would you do it? how do you store them in your clone? 00:11:16 Well, in the clone I'm using rdf_db. 00:11:27 WHich ultimately stores them in the prolog db. 00:12:13 Hmm... so how does *that* store them? 00:12:31 heh, I love J's "todo" list on http://kingprimate.com/ 00:12:38 Not sure. 00:12:45 [http://kingprimate.com/2002/02/21.html#a355 for anyone reading these logs] 00:12:57 Pretty much like an indexed rdbms. 00:13:25 I.e, something like a bunch of big hashtables. 00:13:40 Argh. Something else that I'll be going through once I learn a semi-respectible amount of Prolog 00:13:46 (well, probably a more complicated datastructures) 00:13:47 hmm? 00:14:08 the rdf_db source, that is 00:14:22 yes, it puts a fair bit of effort into qname expansion. 00:14:35 And builds a cache for lookups. 00:14:44 I suspect I screw it up hard, regularly. 00:14:45 ;) 00:15:25 have you run any performance tests on your clone yet? 00:15:41 But, for example, I would definitely look at the various rdbms represenations of rdf proposals. 00:15:43 Not really. 00:15:47 Do you have a good test? 00:15:52 Or even a bad test? 00:16:18 I have that cool N3 test... but no really good query tests 00:16:26 just a few transitive closure things, etc. 00:16:34 * sbp looks through his tests 00:17:19 I also point you (again) to kjbuckets 00:17:23 Hmm... there are a fair few built-in tests. Are you planning on adding built-ins to your clone? 00:17:32 And its SQL implementations. 00:17:45 Yes, I suppose. 00:17:51 Builtins seem necessary. 00:17:57 * sbp reads http://www.chordate.com/kjbuckets/kjbuckets.html 00:18:00 I'd like to work out more of the pure logic bits. 00:18:14 And get a backward chainer in. 00:18:23 Builtins are just predicates, yes? 00:18:27 Oh, and lists 00:18:29 And... 00:18:30 Bah! 00:18:53 Builtins are relatively uninterestings implementationally. 00:19:15 Well,t he interaction between builtins and query is tricky. 00:19:28 But aren't they basically call outs to python code? 00:19:47 well, I managed to do it after looking at that old conversation between you and Tim 00:19:53 Heh. 00:19:55 and going through the Llyn source code a bit 00:20:15 basically, it searches *before* the query for any built-in predicates 00:20:16 Yes, I remember finally figuring out builtins. 00:20:19 Yes. 00:20:22 And orders. 00:20:26 Do light ones first 00:20:29 heavy ones after? 00:20:41 then it whips out the triples that contain those predicates, does the query, and performs the tests afterwards, with the queueing, as you mention 00:20:51 actually, it doesn't have as many states as CWM 00:20:59 15 seemed a few too many :-) 00:21:01 What doesn't? 00:21:05 Ah, yours. 00:21:06 Eep 00:21:27 Right, Eep/ 00:21:39 evidencing evil python 00:21:45 heh, heh 00:22:39 Entertainingly (un)elucidating processor, perhaps 00:23:11 Eliding essential palmer. 00:23:59 * sbp is all-essential 00:25:42 * sbp goes to get food and drink 00:37:37 @ http://news.bbc.co.uk/hi/english/entertainment/new_media/newsid_1834000/1834510.stm 00:37:45 B: http://news.bbc.co.uk/hi/english/entertainment/new_media/newsid_1834000/1834510.stm from sbp 00:37:49 B:|Hundreds queue for Xbox in Japan 00:37:51 titled item B 00:38:57 B::But, according to the article, the sales trailed off later in the day. Experts are predicting that it's going to be a tough three-way fight between Sony, Nintendo, and MS 00:38:58 commented item B 00:41:00 B::Japan always get cool technological doohickies before we do. It's not fair 00:41:01 commented item B 00:42:01 argh: http://news.bbc.co.uk/hi/english/sci/tech/newsid_1831000/1831843.stm 00:42:12 they tell us about the map, but where's the link? 00:42:46 http://mars.jpl.nasa.gov/mgs/ might help... 00:44:28 ah, Malin: http://www.msss.com/ 00:45:05 got it: http://www.msss.com/mars_images/moc/moc_atlas/ 00:46:56 Off to eat. 00:47:10 If you get into using kjbuckets for your clone, I'll kibbitz ;) 00:47:11 bijan has quit ("Leaving") 00:48:08 that's one against, then :-) 00:49:24 @ http://www.msss.com/mars_images/moc/moc_atlas/ 00:49:34 C: Mars Global Surveyor MOC2-299 Release from sbp 00:49:46 C:|Malin: Mars Atlas Revisited 00:49:48 titled item C 00:50:56 Morbus (~Morbus@63.173.138.138) has joined #swhack 00:51:05 C::An atlas of the red planet, compiled by [http://www.msss.com/|Malin] from hundreds of photos from [http://mars.jpl.nasa.gov/mgs/|MGS], into one big composite. All available over the 'net 00:51:06 commented item C 00:51:23 C::via. an [http://news.bbc.co.uk/hi/english/sci/tech/newsid_1831000/1831843.stm|article from the BBC] 00:51:24 commented item C 00:51:27 Hi there Morby 00:51:33 sbp, i need your help. 00:51:42 you say this UKish term, and I forgot what it swas. 00:51:46 you need *my* help? me? 00:51:53 it's just like "Rubbish!" only different. 00:51:54 Bugger? 00:52:04 Is it Bugger? It's not bugger. 00:52:07 what is it. 00:52:13 Bugger, shit, fuck it, smeg, bollocks, nads, arse... 00:52:17 all i keep thinking of is bullcocky, and that's not it. 00:52:20 bollocks! 00:52:29 yes, that was it. thanks./ 00:52:31 heh, heh 00:52:35 np 00:52:38 [[[ 00:52:41

Rest assured, I'm not going to force you to do anything you don't want to. Some of you have heard of this compiling junk, and it turns your stomach. You're thinking "Wait, the Mac was easy! They added this old-fangled type-in-the-window thing, and now they want me to quack like a programmer?! Bollocks on you, I'm tellin' Mom!" 00:52:45 ]]] 00:52:54 :) 00:53:05 heh, heh 00:53:15 what's that going to be in? 00:53:22 part 5 00:53:46 y'know, bollocks is taken by some to be moderate-swearing over here 00:53:54 i know :) 00:53:55 [not me, though. I couldn't give a crap] 00:54:06 heh, heh. All the better, then! 00:54:09 hehehehe 00:54:17 i hope no one from ora reads swhack 00:54:19 ;) 00:54:23 Swhack exclusive! 00:55:10 * sbp can't wait for this edition 00:56:21 Your articles are becoming a beloved ORA institution, you know. People salivate upon hearing that there's going to be a new article coming from the scary Hemenway dude 00:56:28 i doubt it :) 00:56:33 maybe you, patti, and llllll. 00:56:34 well, I do 00:56:40 heh, yeah 00:56:45 and a few people who email me every so often. 00:57:25 and the millions of comments that you got? 00:57:40 eh 00:57:42 * Morbus waves hands around. 00:57:55 fly in your room? 00:58:21 no, i farted. 00:58:26 lol 00:58:28 heh, heh 00:58:29 sigh. 00:59:11 sbp has changed the topic to: Swhack: the original birthplace of toilet humour 00:59:40 and the lipogrammatic /x70 game, of course 00:59:46 yeaaaah. 01:00:19 that game was just so funny 01:00:29 it'd be banned in most countries 01:05:51 GabeW has quit ("Client Exiting") 01:10:18 heh: http://www.ananova.com/news/story/sm_527956.html?menu=news.quirkies 01:25:40 gotta love rousing discussions: 01:25:41 that's mine. since 98, babay. 01:25:41 what's the correct way to spell that elongated, inflected "bahbee!" phrasE? 01:25:41 BaaaaaaaaaaaaayBEEE! 01:25:41 well, that one reminds me of those old deep bass'd 60s, 70s songs. 01:25:41 i think you'd have to remove a few 'a''s to get the one i'm looking for. 01:28:03 heh, heh 02:25:36 MorbusIff (~Morbus@s86.terminal3.totalnetnh.net) has joined #swhack 02:31:17 tansaku1a (~sam@n144-001.tokyu-net.catv.ne.jp) has joined #swhack 02:40:26 tansaku (~sam@n146-214.tokyu-net.catv.ne.jp) has joined #swhack 02:48:35 Morbus has quit (No route to host) 02:57:49 tansaku1a has quit (Read error: 110 (Connection timed out)) 03:51:42 hello 03:51:50 jeremiah_ is now known as jeremiah 03:52:24 Hi 03:52:30 how're you? 03:52:51 I seem to be fine, thanks 03:52:53 and you? 03:59:44 MorbusIff has left #swhack 04:22:57 good 04:23:00 sigh... I'm tired 04:24:06 .time 04:24:07 2002/02/23 04:25:35.1185 Universal 05:00:25 Gotta run 05:31:26 sbp has quit (Read error: 104 (Connection reset by peer)) 05:31:32 sbp- (~sean@63.149.73.20) has joined #swhack 05:32:26 sbp- is now known as sbp 11:49:53 tansaku has quit (Read error: 110 (Connection timed out)) 13:15:03 tansaku (~sam@n146-214.tokyu-net.catv.ne.jp) has joined #swhack 15:05:20 tansaku1a (~sam@n146-214.tokyu-net.catv.ne.jp) has joined #swhack 15:12:27 tansaku has quit (Read error: 110 (Connection timed out)) 15:54:44 tansaku1a has quit (Read error: 110 (Connection timed out)) 17:13:08 tansaku1a (~sam@n146-214.tokyu-net.catv.ne.jp) has joined #swhack 19:00:57 bijan (bparsia@login1.isis.unc.edu) has joined #swhack 20:30:57 xena has quit (Connection timed out) 20:41:48 Glenn_the_Great-AG (~glenn@pool1-66.max2.ahn.dialup.athens.net) has joined #swhack 20:43:00 Glenn_the_Great-AG is now known as Glenn_the_Great-AGN 20:47:38 System Information 12··> 13<·Operating System/Build: Windows 98 (4.10 - 2222)13·> 13<·Uptime: 5days 7hrs 15mins 21secs13·> 13<·Resolution: 1024x76813·> 13<·CPU Info: 1-AMD K7 (0.18 µm) {4} @~654.63MHz13·> 13<·Memory Resources: Usage: 330/384MB (85.94%) 12[4||||||||14||12]13·> 20:48:18 Glenn_the_Great-AGN has quit ("Get it at http://chat.theliberation.com/ss <·SS4·>") 20:55:55 heh, heh. Thanks for that :-) 20:56:00 Hey sean. 20:56:09 Hi bijan 20:57:38 * bijan updates cwmclone 20:57:43 Got the consult eof bug done. 20:57:47 Fixed. 20:57:52 Much less embaressing now :) 20:58:16 what bug was that, then? 20:58:34 The consulter wouldn't terminate. 20:58:37 You had to cancel. 20:58:57 If you had a certain sort of whitespace at the end it would infinite loop :) 20:59:03 Tail recursively. 20:59:08 So no stack blow out. 20:59:09 And too fast. 20:59:13 So no interrupt :) 20:59:18 you mean "@stop." wouldn't work? 20:59:30 No, this is in the file reader. 20:59:32 I.e., consulting. 20:59:39 ah 21:00:08 Trying to do the document namespace and empty prefixes. 21:00:29 So I can read a larger number of regular n3 files. 21:02:47 Galahad (xena@mewtwo.espnow.com) has joined #swhack 21:03:23 If you do come up with a good "speed" test case, I'd love to see it. 21:03:28 Preferably without builtins. 21:03:37 I need to think about builtins, but they are on the list. 21:03:47 Well, rm's test case might be fairly valuable. Let me try to find it... 21:08:06 ah, in http://blogspace.com/swhack/chatlogs/2002-02-21.txt 21:08:13 at 05:41:33 21:11:48 BRB, got to get hot drink. 21:11:51 O.K. 21:12:02 I'll paste the N3 version into the channel in the meantime... 21:12:13 @prefix : <#> . 21:12:13 @prefix u: . 21:12:13 @prefix log: . 21:12:18 this log:forAll :trk , :trkStruct , :has , :prop , :partStruct , 21:12:18 :otherProp , :anonLine , :lineText . 21:12:23 { :trk 21:12:23 . 21:12:28 :trk :trkStruct . 21:12:29 :trkStruct :has :prop . 21:12:32 :prop :partStruct . 21:12:32 :partStruct :otherProp :anonLine . 21:12:36 :anonLine :lineText . 21:12:36 } log:implies { 21:12:43 [ u:trk :trk; u:trkStruct :trkStruct; u:has :has; u:prop :prop; 21:12:44 u:partStruct :partStruct; u:otherProp :otherProp; u:anonLine :anonLine; 21:12:44 u:lineText :lineText ] } . 21:13:07 * sbp had to toss-up between www-archive and #swhack :-) 21:22:49 monokrom (~chatzilla@208-58-246-147.s147.tnt3.atnnj.pa.dialup.rcn.com) has joined #swhack 21:22:57 * sbp waves to monokrom 21:23:19 * monokrom waves back 21:24:19 if you've not been in here before, I should note that this channel is publically logged to the Web, blah, blah, blah 21:24:58 * monokrom nods 21:25:01 gotcha 21:25:16 logs are at http://blogspace.com/swhack/chatlogs/ 21:25:34 but we don't mid since we're all a bit nutty about recording information persistently... 21:25:47 however, you can make comments off-log by prefixing them with "# " 21:41:31 I have to say that I don't find n3 very perspicuous as a logic notation. 21:42:37 many have noticed that N3 is a particularly quirky logic notation 21:59:03 Glenn_the_Great-AG (~glenn@pool1-66.max2.ahn.dialup.athens.net) has joined #swhack 21:59:56 Glenn_the_Great-AG has quit (Client Quit) 22:00:49 X = user6722592 22:00:49 Y = 'http://util#anonLine' 22:00:50 Z = 'http://test/#j45234' 22:23:35 AlexMax (~xircon@clt74-11-127.carolina.rr.com) has joined #swhack 22:23:55 * sbp waves to Alex 22:24:00 hey 22:24:06 I was just told about this place 22:24:10 Glenn_the_Great-AG (~glenn@pool1-66.max2.ahn.dialup.athens.net) has joined #swhack 22:24:15 We got haxored by one of you guys 22:24:17 BTW, this channel is publically logged to the Web etc. To do an off-log comment, use "# " 22:24:20 Heh 22:24:25 haxored? Mmmkay 22:24:26 Okie 22:24:39 Do any of you know a "Li0n7?" 22:24:51 I have reason to believe he has hung around here before 22:25:25 er... this is not a cracking channel. it's a hacking channel 22:25:36 We are talking about hacking 22:25:43 Our main page was hacked by a Lion7 22:25:43 ah, good 22:25:48 Yeah 22:25:55 he's never been here to my knowledge 22:26:00 heh. no, I really do think you mean "cracking" 22:26:09 I do recall a Lion7 coming in here briefly 22:26:10 or if so under a different nick 22:26:14 or something like that 22:26:32 ah, Lion7, yes 22:26:43 heh. Remind me to kick Aaron when he comes back for choosing a dorky channel name 22:26:49 When is the last time you saw Lion7 in here? 22:27:06 dunno. I can grep the logs if you really want me to 22:28:19 * sbp greps 22:28:19 I don't really have time to sort through them all 22:28:19 Dude 22:28:19 Grep is a unix command 22:28:19 Okay 22:28:19 That (I think) searches for a specific text string 22:28:19 in a file 22:28:19 indeed 22:28:19 2002-01-27 22:28:19 I thought "grep" was supposed to be a cute slang word for "grab" 22:28:19 Nah 22:28:19 it'll take a minute or two, since we have quite a few logs... 22:28:23 no, it's an abbreviation 22:28:27 Well, thanks anyway 22:28:28 2002-02-10 17:37:00 Lion7 has left #swhack 22:28:28 Glenn, when you want to hang around these people, you need SOME prerequisites 22:28:33 get regular expression 22:28:34 ^_^ 22:28:36 g/re/p 22:29:04 "for every line matching this regular expression, print" 22:30:17 I wouldn't know. I'm a Windows whore...... 22:31:15 Well, I don't actually run the webpage 22:31:20 I'm a forum administrator 22:31:26 ah, neat 22:32:52 Apparantly this is a routine that Lion7 likes to do to peoples' websites 22:33:15 If you want to see what he did, look at the top of www.armageddongames.com 22:33:22 At least he didn't do anything harmful 22:33:37 well... as I say, we don't know much (if anything) about the guy. You can check for yourself from the logs 22:34:08 Well, thanks for your help. I'm just trying to grab whatever little info I can 22:35:32 Glenn_the_Great-AG has left #swhack 22:36:16 [[[ 22:36:16 17:40:03 sbp has changed the topic to: Swhack: Where the lamers and sk do roam 22:36:16 17:40:12 s/lamers/lamerz/ please 22:36:16 17:40:14 oops 22:36:16 17:40:19 sbp has changed the topic to: Swhack: Where the lamerz and sk do roam 22:36:17 ]]] 22:39:08 * AlexMax is away: (Auto-Away after 10 mins) [BX-MsgLog On] 22:45:11 wouldn't it be easier just to turn off the logger? 22:46:05 why's that, deltab? :-) 22:46:09 [OLM] 22:46:40 sbp has changed the topic to: Swhack has now been banned in every country in the world except for Finland. We're not sure why 22:47:58 not sure why: I blame Aaron, of course. He'll blame me, so I'm just getting in my shot early 22:58:41 u:lineText="I sit at my table and wage war on myself"> 22:58:41 22:58:41 22:58:41 22:58:41 22:58:44 22:58:46 22:58:47 22:58:49 22:59:19 user6722785? sound of much barfing 22:59:41 Eh. 22:59:44 actually, we didn't really resolve how to hack bNode labels into XML RDF 22:59:44 works for now :) 22:59:54 27 bnodes 23:00:08 since "_" is void as a URI scheme, someone (probably TimBL) suggested using that 23:00:23 yep, that's what CWM got 23:00:28 Well, that's just what my gen_id does. 23:00:34 It's easy to change it to whatever. 23:00:39 But it doesn't matter. 23:00:45 re: inferencing. 23:00:49 is that really unique based upon the current bNodes, or just a random thing? 23:01:03 unique 23:01:13 user is the rdf_db it's unique to 23:01:23 It maintains an integer. 23:01:24 wow, that was speedy 23:01:50 .641 seconds 23:02:03 Er.. or something. 23:02:05 That doesn't seem right. 23:02:10 I'm not sure about timing in prolog. 23:02:20 * sbp wonders how to benchmark CWM 23:02:37 there must be a Python benchmarking framework somewhere... 23:02:43 profile is built in. 23:02:49 can't you do it fromthe command line? 23:02:54 How long does CWM take? 23:03:36 dunno, can't time it. Less than 5 seconds, certainly 23:03:53 How long did eep take? 23:04:01 That was the half hour -->crash? 23:04:15 erm... 23:04:18 *ahem* 23:04:26 yeah. About twenty minutes before I crashed it 23:04:38 taking up plenty of memory in the meantime 23:04:57 Well, I could have told you straight off that this would be trivial. 23:05:04 The prolog rule is *not* complex. 23:05:30 You probably have a bug somewhere. 23:06:07 This isn't a great test if CWM resolves it so quickly, actually, as I would expect. 23:06:09 yep - but it's something that I don't particularly want to debug... :-) 23:06:33 You were supposed to give me a performance tester. 23:06:36 no, it's not a great test - more of a sanity test. I'm sure that there are some decent files in SWAP, but most have builtins etc. - ugh 23:06:45 Of course, it's nice that mine works and yours doesn't :) 23:06:45 well, that's the best one that I have! 23:06:51 blargh! :-) 23:07:10 Really? Have you ever run *anything* that takes a long time on CWM. 23:07:19 --thinking, likely. 23:07:29 of course, plenty of stuff. Under --think, as you say... 23:07:30 That isn't obvious like a log:semantics 23:07:44 I've been debugging stuff that takes like five minutes per run. That's frustrating 23:07:50 So, what I need is something reasonably tortuous, that we can purge the builtins ;) 23:07:53 Ok, one of those. 23:08:04 well, I'll go find some decent N3 on my hards drive... 23:08:08 s/hards/hard/ 23:08:14 I was *wondering*! 23:08:43 * sbp searches for *.n3 23:08:57 1927 files found 23:09:01 Er.. 23:09:12 10.9 MB 23:09:14 Just whip out a python script that runs and times each one! :) 23:09:17 Yick, man. 23:09:20 heh: I should run the whole lot through CWM 23:09:24 You have to give up the n3 habit! 23:09:40 It'd probably give me a world peace formula or something 23:09:54 N3 habit: heh, heh. It's so difficult to stop! 23:10:22 can you parse = and ()? 23:10:27 No. 23:10:34 ugh 23:10:38 Sorry. 23:10:44 () is on the list. 23:10:56 axioms1.n3 would have been a good test 23:10:57 = should be easy if I knew what it expanded to :) 23:11:15 aha, I think I've found a good one 23:11:45 here: http://infomesh.net/2001/12/map/data.n3 23:11:53 it has default prefixes, but then so does most N3 23:12:03 s/ :/ x:/ 23:12:13 yes. 23:12:24 136KB of N3, there 23:12:28 x: is taken :) 23:12:34 How long does it take on CWM? 23:12:49 x: so it is! 23:12:57 long: to do what? we need a query... 23:13:22 I guess I could run { ?x a:icao ?y } => { ?x a:icao ?y } . 23:13:26 Well, think one up! :) 23:13:26 how's that? 23:13:31 I don't know. 23:14:00 * sbp gets to work on it 23:16:32 wow, it takes ages. I thought I'd borked it, so I actually stopped it 23:16:35 * sbp runs it again 23:18:09 It's huge! 23:18:48 given that Python can RegExp the necessary information out in about 0.01 seconds flat... 23:19:10 heh, it started at 23:17:47, and it still going... 23:19:26 running cwm data.n3 --filter=q.n3 > q-out.n3 23:20:14 now I think about it, I am running the new CWM, which is meant to be very slow. Perhaps I shouldn't have downloaded it 23:20:20 Hmm. I broke n3_repl. at some point. 23:20:24 * bijan sighs 23:21:31 N.B., the query is just:- 23:21:31 @prefix : <#> . 23:21:31 @prefix log: . 23:21:31 @prefix a: . 23:21:31 this log:forAll :x , :y . 23:21:31 { :x a:icao :y } log:implies { :x a:icao :y } . 23:21:37 Ah, damn, bad syntax. 23:21:39 Thanks 23:21:47 np 23:22:01 CWM is still plodding along... 23:22:09 done! 23:22:13 $ u timenow; cwm data.n3 --filter=q.n3 > q-out.n3; u timenow 23:22:14 20020223-231747 23:22:14 20020223-232155 23:22:25 4:08 23:22:53 that's quite terrible. Where'd my old .tar.gz go to... I'm gonna try the old version 23:23:33 * sbp slurps it via. FTP 23:23:58 Ok, reading it in. 23:24:09 Oh ohoh . 23:24:15 I'm going to have a *huge* advantage. 23:24:19 Since I wont' have to parse. 23:24:21 Hmm. 23:24:39 ugh 23:24:54 wow! 23:24:55 $ u timenow; python cwm/cwm.py data.n3 --filter=q.n3 > q-out.n3; u timenow 23:24:55 20020223-232416 23:24:55 20020223-232438 23:25:04 1.82 is sooooo much faster! 23:25:16 indeed.Ok, I did it 23:25:33 only 22 seconds under 1.82? I can't believe that 23:25:42 Did it get the right results? 23:25:49 X = 'http://www.test.com/#MOB' 23:25:49 Y = 'http://www.megginson.com/exp/ns/airports#icao' 23:25:49 Z = literal('KMOB') ; 23:25:49 X = 'http://www.test.com/#BFM' 23:25:49 Y = 'http://www.megginson.com/exp/ns/airports#icao' 23:25:50 Z = literal('KBFM') ; 23:25:51 Etc. 23:26:02 I'm under a minute, even with parsing. 23:26:08 yeah, that seems alright 23:26:17 well, you whip the new CWM, but the old CWM whips you 23:26:30 But is the old CWM correct? 23:26:53 * bijan notes that CWMclone is a wild prototype :) 23:27:53 heh, heh 23:28:21 the old CWM is a good stable version 23:29:22 Doesn't mean it's correct. 23:29:29 sample output:-0 23:29:34 I'm just pointing out htat I have *no* optimization. 23:29:49 s/0// 23:29:49 :01R a:icao "K01R" . 23:29:49 23:29:49 :01T a:icao "K01T" . 23:30:17 It generates a *lot* of output. 23:31:01 Ah, it's the identity. 23:31:08 Not an interesting test. 23:31:32 it is correct 23:32:34 How fast is your machine? 23:33:22 I put my results in sw/cwmclone/ 23:33:24 the data seems very consistent 23:33:24 Hmm... I suppose there's a way to test - I could pretty print them both and hash the outputs 23:33:24 but I'm not going to bother :-) 23:33:54 Well, you can dl mine and compare. 23:34:13 At http://www.unc.edu/~bparsia/sw/cwmclone/tc2_2_results.rdf 23:34:21 How fast is your machine? 23:35:05 Actually, I don't know how fast *mine* is. 23:35:15 Oh, mine is going to be *really* hurt by this one. 23:35:46 I essentially have to touch every inference twice. 23:36:03 I mean, I shouldn't *have* to, but I do. 23:36:24 So, one should expect to easily double the speed. 23:36:29 Without anything tricky. 23:37:47 sorry, my connection was lagging 23:38:03 it turns out that you were speaking, and the bits of text were only coming through after some delay 23:38:08 heheh. 23:38:26 Hmm. But no, it won't double. 23:38:30 The testing is *very* fast. 23:38:37 Looks like the time is in db updating. 23:38:45 I have more memory. 23:38:48 But I may be slower. 23:38:54 22.9 seconds for the filter. 23:38:57 No parsing. 23:39:11 not too bad - equals the old CWM 23:39:50 We should run it on your machine. 23:39:53 * sbp emails the speed tests to Tim/Dan/Norm 23:40:23 ta da: http://lists.w3.org/Archives/Public/www-archive/2002Feb/0038 23:40:35 run it on my machine: sure. just tell me what to do 23:41:53 ok, got to http://www.unc.edu/~bparsia/sw/cwmclone/ 23:42:00 Get cwmclone.P 23:42:07 And tc2.2.n3 23:42:32 the Website seems to be borked 23:42:35 Oo, you know what's prolly slowing down the parse...all the info I preint. 23:42:56 did I typo? http://www.unc.edu/~bparsia/sw/cwmclone/ 23:43:00 Is working for me. 23:43:09 working for me now too... 23:43:31 got 'em 23:44:08 Ok, fire up swi. 23:44:18 O.K. 23:44:32 ['path/to/cwmclone.P']. 23:45:00 Yep 23:45:48 Ok, get_time(T1),n3_consult('path to n3', user), get_time(T2), Time is T2 - T1. 23:46:45 (This should take a bit. My tokenizer/parser are 1) slow, 2) prolly non-deterministic, and 3) printing lots of info :( 23:47:11 after a lot of printing:- 23:47:11 S: x:P60 V: y:state O: literal(WY) C: user 23:47:11 alldone 23:47:11 No 23:47:18 Yes. 23:47:27 How long did it take, btw? 23:47:35 hm. Might not have answered. 23:47:35 no idea 23:47:38 Ok. 23:47:43 compile_rules(user). 23:47:59 done it "Yes" 23:48:15 get_time(T1), filter(user, test), get_time(T2), Time is T2 - T1. 23:48:47 T1 = 1.01451e+009 23:48:47 T2 = 1.01451e+009 23:48:47 Time = 15.38 23:48:54 Yep, faster than mine. 23:49:00 By about what I expected. 23:49:24 and quite a bit faster than CWM, but no parsing... 23:49:32 I still prolly come in behind CWM the younger. 23:49:37 No parsing, and no writing to disk. 23:49:52 Though rdf_save/2 can approximate. 23:50:07 In *much* less code though :) 23:50:13 true 23:50:20 * sbp wonders if he dare try Eep on it 23:50:30 And note, SWI is not, generall, a *fast* prolog. 23:52:24 what's a better alternative? XSB? 23:52:38 I don't know off hand. 23:52:42 I've note benchmarked. 23:52:51 Plus it very much depends on your appication. 23:52:56 XSB may be faster for some things. 23:53:56 But some speed gains possible: 23:54:12 In the "generate applicable rules' bit (espeically for a filter, there isnt' any need. 23:54:38 rdf_db may be slowing things down (or speeding them up!) 23:55:19 We need a more complex inference to compare, I think. 23:55:25 yeah... 23:55:30 THis is more of an I/O thing. 23:56:10 hmm. Satisfaction testing only takes .03 seconds. Negligible. 23:56:25 That suggestst that most of the time is in the assertion. 23:56:34 This may be due to rdf_db:rdf_assert 23:57:19 what is that doing? 23:57:21 Is there an interesting, more complex query to be done on this data? 23:57:33 Well, it does some qname expansion. 23:57:37 yes, but it involves builtins 23:57:56 We'll, I"m trying to think of something that doesn't involve builtins :) 23:58:07 the filter's at http://infomesh.net/2001/12/map/distance.n3 23:58:30 math, blagh 23:58:53 I could hand translate that... 23:59:15 Does that take a long time on CWM?