unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Guix Devel <guix-devel@gnu.org>
Subject: "guix search" needs your help
Date: Mon, 11 May 2020 13:05:21 +0200	[thread overview]
Message-ID: <CAJ3okZ3jyRpEomJCneWqeL9UXR9id4gWSeyWi1AJxc9Hyb3A3w@mail.gmail.com> (raw)

Dear,

I am lacking imagination and I need your help for:
 - what should be the query you type,
 - then what is the package you expect with such query, in order.

Example:

  guix search source control management
  # expect: git, mercurial, svn, then other

  guix search r cytometry
  # expect: r-flowcore r-flowsom then other


Using your imagination, I can benchmark some ranking functions.


As reported, the experience with "guix search" is sometimes poor.
Aside the issue of pager or output format,  there is 2 explorations
for improvements discussed in this bug report [1]: faster and more
accurate.  The benchmark for "faster" is straightforward and the
exploration is on going. :-)

Currently, the packages are ranked accordingly to 'relevance'.  There
is good, bad and ugly about this strategy and the state-of-art Okapi
BM25 ranking function has to be evaluated to know if such information
retrieval strategy is worth or not for search of packages.  Well,
thanks to Arun guile-xapian bindings, the BM25 ranking is easy to
benchmark since all the tough work is relayed to Xapian.

[1] http://issues.guix.gnu.org/39258


From my point of view, such pair (query terms, expected packages)
would help to improve the tools:
 - maybe "guix search"
 - maybe "guix lint" by establishing some metrics indicating is the
synopsis and description are relevant -- compared to all the other
packages.


Thank you in advance for help me in the exploration of such ideas.

Best regards,
simon


                 reply	other threads:[~2020-05-11 11:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAJ3okZ3jyRpEomJCneWqeL9UXR9id4gWSeyWi1AJxc9Hyb3A3w@mail.gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).