unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Mikael Djurfeldt <mikael@djurfeldt.com>
To: tomas@tuxteam.de
Cc: guile-devel@gnu.org
Subject: Re: GPT-4 knows Guile! :)
Date: Sat, 18 Mar 2023 10:03:15 +0100	[thread overview]
Message-ID: <CAA2Xvw+pTXC2RO-epuiV-+ChaNWzrdQ4n_ATwutkQ3n7sq5GBw@mail.gmail.com> (raw)
In-Reply-To: <CAA2XvwLOqBr1cxC+ZpVOXdw7Tto7hZCifUO7mFF6wM071T3Dqg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1415 bytes --]

On Sat, Mar 18, 2023 at 9:58 AM Mikael Djurfeldt <mikael@djurfeldt.com>
wrote:

> On Sat, Mar 18, 2023 at 9:46 AM <tomas@tuxteam.de> wrote:
>
>> On Sat, Mar 18, 2023 at 09:41:37AM +0100, Mikael Djurfeldt wrote:
>> > On Sat, Mar 18, 2023 at 9:36 AM <tomas@tuxteam.de> wrote:
>>
>> [...]
>>
>> > > Perhaps you didn't know, but you are training the model :-)
>> > >
>> >
>> > Unfortunately not. I'm prompting it within its 32000 token (GPT-4)
>> > attention span. Next conversation the model is back to exactly the same
>> > state again. Then, of course, it is possible that OpenAI chooses to
>> filter
>> > out something from the dialogs it has had.
>>
>> You don't think that those coversations end up as raw data for the
>> next model? I'd be surprised, but you know definitely more than me.
>>
>
> I know very little apart from knowing what deep learning is and having
> skimmed the "Attention is all you need"-paper. I only meant that you are
> not training the model during and between sessions. It is certainly
> possible that OpenAI filters out things from the dialogs to use as part of
> training for the next version. They warn you that they may take data from
> the dialogs. If and how they do that I don't know.
>

Or, as GPT-4 would phrase it: I apologize for the confusion in my previous
answer. You may be right that I'm training the next version of the model. :)

[-- Attachment #2: Type: text/html, Size: 2099 bytes --]

  reply	other threads:[~2023-03-18  9:03 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-17 16:01 GPT-4 knows Guile! :) Mikael Djurfeldt
2023-03-17 17:25 ` Mikael Djurfeldt
2023-03-17 19:09   ` Damien Mattei
2023-03-17 19:28     ` Damien Mattei
2023-03-18  7:03   ` tomas
2023-03-18  7:55     ` Mikael Djurfeldt
2023-03-18  8:11       ` Mikael Djurfeldt
2023-03-18  8:14       ` tomas
2023-03-18  8:22         ` Mikael Djurfeldt
2023-03-18  8:36           ` tomas
2023-03-18  8:41             ` Mikael Djurfeldt
2023-03-18  8:46               ` tomas
2023-03-18  8:58                 ` Mikael Djurfeldt
2023-03-18  9:03                   ` Mikael Djurfeldt [this message]
2023-03-18  9:23                     ` Damien Mattei
2023-03-18  9:47                     ` Mikael Djurfeldt
2023-03-18 10:01                     ` tomas
2023-03-18 10:49                       ` Stefan Israelsson Tampe
2023-03-18 11:43                         ` Mikael Djurfeldt
2023-03-19  8:46                         ` tomas
2023-03-18  8:34         ` Mikael Djurfeldt
2023-03-18  8:21     ` Dr. Arne Babenhauserheide
2023-03-19 21:22       ` tomas

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://www.gnu.org/software/guile/

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

  git send-email \
    --in-reply-to=CAA2Xvw+pTXC2RO-epuiV-+ChaNWzrdQ4n_ATwutkQ3n7sq5GBw@mail.gmail.com \
    --to=mikael@djurfeldt.com \
    --cc=guile-devel@gnu.org \
    --cc=tomas@tuxteam.de \
    /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.
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).