From: Nicolas Graves via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org>
To: guix-devel@gnu.org
Subject: Where should we put machine learning model parameters ?
Date: Mon, 03 Apr 2023 18:48:12 +0200 [thread overview]
Message-ID: <87jzyshpyr.fsf@ngraves.fr> (raw)
Hi Guix!
I've recently contributed a few tools that make a few OSS machine
learning programs usable for Guix, namely nerd-dictation for dictation
and llama-cpp as a converstional bot.
In the first case, I would also like to contribute parameters of some
localized models so that they can be used more easily through Guix. I've
already discussed this subject when submitting these patches, without a
clear answer.
In the case of nerd-dictation, the model parameters that can be used
are listed here : https://alphacephei.com/vosk/models
One caveat is that using all these models can take a lot of space on the
servers, a burden which is not useful because no build step are really
needed (except an unzip step). In this case, we can use the
#:substitutable? #f flag. You can find an example of some of these
packages right here :
https://git.sr.ht/~ngraves/dotfiles/tree/main/item/packages.scm
So my question is: Should we add this type of models in packages for
Guix? If yes, where should we put them? In machine-learning.scm? In a
new file machine-learning-models.scm (such a file would never need new
modules, and it might avoid some confusion between the tools and the
parameters needed to use the tools)?
--
Best regards,
Nicolas Graves
next reply other threads:[~2023-04-03 17:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 16:48 Nicolas Graves via Development of GNU Guix and the GNU System distribution. [this message]
2023-04-03 19:12 ` Where should we put machine learning model parameters ? Kyle
2023-04-06 18:55 ` how to deal with large dataset? (was Re: Where should we put machine learning model parameters ?) Simon Tournier
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=87jzyshpyr.fsf@ngraves.fr \
--to=guix-devel@gnu.org \
--cc=ngraves@ngraves.fr \
/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).