all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nathan Dehnel <ncdehnel@gmail.com>
To: Saku Laesvuori <saku@laesvuori.fi>
Cc: guix-devel@gnu.org
Subject: Re: Binary descriptors for OpenCV
Date: Tue, 1 Aug 2023 15:58:11 -0500	[thread overview]
Message-ID: <CAEEhgEvxWVyHp_FngyhXr62K71MpnbZfi4m_Z43ivG3YQgibrA@mail.gmail.com> (raw)
In-Reply-To: <20230801203700.67ef6l3ibg27wzpk@X-kone>

>If you know how to convert the blob to weights in the neural network
(something the program has to do to make any use of the blob) and know
the error function, you can continue the training with new data.

Yeah, I get that, but you don't necessarily know what the weights
mean. Let's charitably assume you know the blob works on image data
(instead of audio data or whatever). Do you know if it needs to be
trained on images of a particular size, or color depth, or encoding,
or color format, etc.? And what about models for more complex data
than images like genetic data? How do you know you're not going to end
up with a network that spews out invalid garbage if you re-train it
with things that are incompatible with the original training dataset?
And how do you know that, beyond trial and error, unless you have the
original dataset?

On Tue, Aug 1, 2023 at 3:37 PM Saku Laesvuori <saku@laesvuori.fi> wrote:
>
> > Is this even practically possible? How do you re-train a blob you know
> > nothing about? To me this sounds similar to saying a compiled binary
> > is free software if the license allows you to decompile it and
> > deobfuscate it.
>
> If you know how to convert the blob to weights in the neural network
> (something the program has to do to make any use of the blob) and know
> the error function, you can continue the training with new data.
>
> This is not any different from training the model from scratch. In both
> cases we begin with some set of initial weights for a huge polynomial,
> take a sample of our training data, compute the polynomial for it and
> tweak the weights a bit if the result was not what we wanted. The only
> difference is that when training from scratch we begin with very bad
> guesses for all the weights. When we are tuning the blob we begin with
> much better guesses that are closer to the values we would actually
> want.
>
> The difference to a compiled binary program is that you would want to
> edit it in the source code form. You really would not want to edit the
> neural network by editing the original training data and retraining the
> entire network from scratch. The data set probably contains thousands,
> tens of thousands or even more random pictures that you would have to go
> through and see if they represent the data and results you want. It
> would be much easier to test whether the network gives the correct
> results and train it with new data that you know describes your problem
> better.


  reply	other threads:[~2023-08-01 20:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-01 18:50 Binary descriptors for OpenCV Nathan Dehnel
2023-08-01 20:37 ` Saku Laesvuori
2023-08-01 20:58   ` Nathan Dehnel [this message]
2023-08-02  4:46     ` Saku Laesvuori
2023-08-02 20:25       ` Nathan Dehnel
2023-08-03  6:18         ` Saku Laesvuori
  -- strict thread matches above, loose matches on Subject: below --
2023-08-01  7:21 Nathan Dehnel
2023-08-01 12:14 ` Ricardo Wurmus
2023-08-16 16:55   ` Ludovic Courtès
2023-08-17 21:57     ` Nathan Dehnel
2023-08-17 23:18     ` Maxim Cournoyer
2023-08-24 15:08       ` Ludovic Courtès
2023-07-31 13:12 Ricardo Wurmus
2023-08-01 14:02 ` Maxim Cournoyer
2023-08-01 14:39   ` Saku Laesvuori
2023-08-19  9:37 ` Simon Tournier
2023-08-24 15:06   ` Ludovic Courtès

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

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

  git send-email \
    --in-reply-to=CAEEhgEvxWVyHp_FngyhXr62K71MpnbZfi4m_Z43ivG3YQgibrA@mail.gmail.com \
    --to=ncdehnel@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=saku@laesvuori.fi \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.