search for: mji

...er plot with marginal histograms. I tried par(mfrow= ) ahead of layout(). It does not work. Could I repeat layout() to reach my point? Following is the code I use. Any advice is greatly appreciated. ================================================================= x <- demog$age y1 <- demog$mji y2 <- demog$nles xhist <- hist(x, plot=FALSE) y1hist <- hist(y1, plot=FALSE) y2hist <- hist(y2, plot=FALSE) top1 <- max(c(xhist$counts, y1hist$counts)) top2 <- max(c(xhist$counts, y2hist$counts)) xrange <- range(x,na.rm=TRUE) y1range <- range(y1,na.rm=TRUE) y2range <...

The rules for conformability of objects required for various operators remain a mystery as do some related problems like the rules for recycling in creating arrays etc. Would someone be able to direct me to where such rules are stated? In a related vein, there are all manner of operations that are readily coded in Gauss or in MATA that fail, often mysteriously, in R. Are there some

Probably an uncaught malformed query - the following form of search queries causes a crash for me (core 1.2.3, Perl API, 64bit Debian Lenny, self-compiled): x-y NEAR test NEAR test The first term can be anything with a hyphen in it but word characters at the beginning and end ("3--3" will do). The other 2 terms can be anything. "test NEAR x-y NEAR test" will not cause a

...&l@#K?FQkFH_+nZ!*8W&;PZLP8_Su7UJ z=X2(ZDa%De?JQ+kVyl|U1<E=qhJ<#L`u}h5e0tkB&N%$c%+8LM6iG=;<v13kIBD#Q z>%ytq1_q2cEov0~4n at 8}kyHA$g1|QyHGFB}q=Dt6ap5|F11Od3%5)@A`+tX<!|X0s zag-E6TEHL&;DHA&0lu7>_uub%Q(F)xuG#5}2cI+A`8Nx`CeBipmzQ~A?IcN(Fc?0E zcwQ0}5u-a#SX4cJ|A#kt<MJi)Jg3|3Hm~E#QZu;|YYG;?S9=G1w0Xy|ZceV?c}}hC z>xCvSnq?Vr95X)L#~cJ4s6CP-V?lewUW~CBMi!)LNsc8iCn(=R?TsHW=ovQC7 at MXH z20d0*Rv2{pXstN+(#u at FaGB4xxA@QE7S@;i^1^uz$6q;M!(qtCQ*^uC1``$pLF4TF z=+d at l!U3u%Q9=uHTky%<e>&Zy30xXXYn0aL1w-H)q?8SWH?sw4ZZSoGMPQQ>)9IoL z4blV8Fo{F*GNH&)@+c?e0MGN-cy...

...zkM{4Ia_>;?C6o5|(%d0J3kA4vVYVr+#FZ{8q=csuI$w*$;R4@HX~yT9spq2Ls^ z(^Ob@cpZNd)>yk5_zvDtwzQ?wV5>Z$p;dGjczMuV)scqFcK+VkWu;obgO~pLz>6KJ zDiF6TJLS%>O3k`qN)W-7dhJPOUC5w`)Nr=LdwSTGND8_{Ek}bB*xj95W@cYh-rt#4 zi-omz$oVT!1A*gm++tZ{WW@g&GD3Oq!Qu6$f=zT3bQQU<kTER~b^eVE$RZfg?tQml zv=7ms#t3xuW$mJi>Lrk^y%XZ#mTt+{?vQrcs>PhX#pzd7jYbXRA`YHh-rn5Qb#ig} zJ~cHJ(bCegcXn3J#m&8YdMagNLf)efUQ<^aS6)t|sH$3|s;WxO&dy$5Y|+zEjxDAr z6On)L+HM8?>PBjJ0n+67i_cPrj35RI6>&^xr*SbbZgW0$&JJJNExNC(Ju|Gp>u(hI zoz^_QVl{Ep>s~Txnog$f$w#j?eKULFQT=HS@{Lxkm>B{RNX$bB*PEtaL-nNK#FZGK za%Ow&gt...

...p;QGn5aF at Ujvae(oF34n=!Nr1_K zDb)B%W4!w`%DYdeyl4jHj+vC-G8- at lFc-9Wl#>O3g at 8qX#gsdj0G3jt4db^ir~K9x zAfr13-6T^GM;8gYed|iZ(KUju+`0;JG)d3}g09 at U8X>w%Ff4*$-MR*842NJi1j8d3 z4ng+`hC(nTf?*I0gP at xPLm(IeLAP_(0oGG~+Xkdh3avr734rM)nBrddB7ZYr3*bJ= zdu;`5LmYW at JLP>I0Ix784<URQ03&ky4up?VemjiN?T;aZ;ko^B&~_pYLv;HtgfK*8 zH)wkhe*yqQbo*Y)OZI`bpK|vBga?s6MEL-Sa{$CS0OE8%O^rXmQG+cS_zdL(pG8-W zfE6}t;ByFJugJ?nt&n~mY1pWNM-jqq4LpVrHf`W>gs%&W4S?MuuvY}Oiom83*sVKH zQl4^3)CqV|l%f2uFHx?(jPMntUq$$ur~~0Sz#D)!0dE1`7UCuRukRrKF5o at D`+yHX z{}ACv2tNjVg7~KhKL>nC`Q2Y3{2Jjml;8O+HCm{A at DG#^{*...

This is my test case, what am I doing wrong? It seems that the API is used incorrectly, but I cannot find the problem... --- 8< --- #!/usr/bin/perl use Search::Xapian qw(:all); use strict; my $xa = new Search::Xapian::WritableDatabase ("/tmp/xapian", DB_CREATE_OR_OVERWRITE); my $indexer = Search::Xapian::TermGenerator->new();

Hi, we've been using Xapian in production for several months now and update our (chert) databases continuously. A freshly generated index occupies only around ~35% of the disk space compared to what it becomes after a few days. This is not a huge concern (we use SSDs), but I've been wondering whether there is a way to fine-tune this (other than recreating the index frequently), so

Hi, is anyone working on Xapian bindings for Go? SWIG supports Go since version 2.0 (http://www.swig.org/Doc2.0/Go.html), but there's some Go-specific code that needs to be written. Unfortunately, I have 0 experience both with SWIG and hacking on the Xapian bindings, so I probably cannot do this as a weekend project. It would come in very handy though. Regards, Marinos

I am using BM25 with k1=0 and min_normlen=1 to get weights unaffected by document length and term frequency in the document (min_normlen=1 isn't necessary I guess) and am expecting single-term weights to be identical for all matches. I have added a document value to steer such general search queries and it works fine, except that for some search terms, I get results like: