WEBVTT

00:00:00.372 --> 00:00:02.513 align:center
I'm Byron Shetler, CEO of Hertzler

00:00:02.553 --> 00:00:03.014 align:center
Systems.

00:00:03.734 --> 00:00:04.795 align:center
And one of the exciting new

00:00:04.855 --> 00:00:06.416 align:center
features that we've added to our

00:00:06.516 --> 00:00:08.277 align:center
Game Seeker Suite is the ability

00:00:08.597 --> 00:00:12.940 align:center
to send the statistical information from

00:00:12.980 --> 00:00:15.442 align:center
a chart to an artificial intelligence

00:00:15.542 --> 00:00:18.264 align:center
bot using the right-click Send To

00:00:18.324 --> 00:00:18.684 align:center
menu.

00:00:20.125 --> 00:00:22.706 align:center
And as we send this information

00:00:22.766 --> 00:00:25.348 align:center
to our computer overlords, they'll give

00:00:25.388 --> 00:00:27.229 align:center
us some analysis and...

00:00:29.282 --> 00:00:32.284 align:center
possibly some recommendations about the data

00:00:32.324 --> 00:00:32.584 align:center
set.

00:00:33.124 --> 00:00:34.765 align:center
So you can see here, I've

00:00:34.785 --> 00:00:36.286 align:center
got a number of different AI

00:00:36.346 --> 00:00:39.367 align:center
set up and with different prompts,

00:00:39.928 --> 00:00:41.128 align:center
and you can always go in

00:00:41.368 --> 00:00:44.950 align:center
and edit the prompt or choose

00:00:45.030 --> 00:00:48.452 align:center
from the last five prompts that

00:00:48.492 --> 00:00:49.673 align:center
you've modified.

00:00:50.273 --> 00:00:51.674 align:center
So if I go ahead and

00:00:52.714 --> 00:00:54.835 align:center
send this statistical information to chat

00:00:55.076 --> 00:00:56.116 align:center
GPT-Four,

00:00:58.569 --> 00:01:00.770 align:center
What's going on is the statistical

00:01:00.810 --> 00:01:03.370 align:center
information gets packaged and sent, and

00:01:03.410 --> 00:01:04.911 align:center
then the results will come back

00:01:05.551 --> 00:01:06.491 align:center
in a few moments.

00:01:07.231 --> 00:01:09.572 align:center
Now, there's a caution note on

00:01:09.592 --> 00:01:10.532 align:center
that one screen.

00:01:11.392 --> 00:01:13.393 align:center
You don't want your AI to

00:01:13.513 --> 00:01:16.254 align:center
hallucinate when it sends the information

00:01:16.294 --> 00:01:16.574 align:center
back.

00:01:17.134 --> 00:01:19.415 align:center
So you always want to check

00:01:19.455 --> 00:01:20.055 align:center
the results.

00:01:20.135 --> 00:01:22.575 align:center
And here we get some information

00:01:22.635 --> 00:01:26.737 align:center
back, looking like it's broken down

00:01:26.797 --> 00:01:28.077 align:center
into different categories.

00:01:29.007 --> 00:01:31.168 align:center
and it's given us some recommendations

00:01:31.729 --> 00:01:32.669 align:center
on what to do.

00:01:32.869 --> 00:01:34.510 align:center
And since I have the checkbox

00:01:34.630 --> 00:01:38.093 align:center
to include the prompt and the

00:01:38.193 --> 00:01:39.753 align:center
statistics that were being sent, you

00:01:39.774 --> 00:01:41.775 align:center
can see here it also included

00:01:42.135 --> 00:01:44.556 align:center
in my results the statistics that

00:01:44.576 --> 00:01:45.197 align:center
were sent out.

00:01:45.797 --> 00:01:48.319 align:center
So I can save this information

00:01:48.379 --> 00:01:50.320 align:center
to an HTML file, send it

00:01:50.480 --> 00:01:54.362 align:center
via email, or close this results

00:01:54.402 --> 00:01:55.623 align:center
window and go on.

00:01:56.154 --> 00:01:57.314 align:center
to the next dataset.

00:01:57.394 --> 00:01:58.715 align:center
Now you're probably wondering, how did

00:01:58.775 --> 00:02:01.695 align:center
all this magic occur behind the

00:02:01.776 --> 00:02:02.176 align:center
scenes?

00:02:02.476 --> 00:02:03.676 align:center
And if we go into our

00:02:03.936 --> 00:02:07.037 align:center
administration module, you can see that

00:02:07.757 --> 00:02:09.818 align:center
there's an artificial intelligence link.

00:02:11.798 --> 00:02:14.059 align:center
And from here, I can go

00:02:14.119 --> 00:02:15.619 align:center
into any of these, let's edit

00:02:15.639 --> 00:02:17.320 align:center
the chat GPT-Four.

00:02:17.960 --> 00:02:19.400 align:center
You can choose what type of

00:02:19.600 --> 00:02:20.340 align:center
AI it is.

00:02:20.380 --> 00:02:22.201 align:center
This latest information button will

00:02:23.090 --> 00:02:25.592 align:center
display any updates like any new

00:02:25.652 --> 00:02:27.793 align:center
models that might work or any

00:02:27.873 --> 00:02:31.015 align:center
other AIs and how to interface

00:02:31.055 --> 00:02:32.236 align:center
to them even if they're not

00:02:32.276 --> 00:02:33.937 align:center
in the predefined list.

00:02:34.017 --> 00:02:35.918 align:center
My API key is really long

00:02:36.078 --> 00:02:37.919 align:center
so I don't mind showing you

00:02:37.939 --> 00:02:38.679 align:center
the first part of it.

00:02:38.739 --> 00:02:40.661 align:center
There's like three or four times

00:02:40.701 --> 00:02:41.741 align:center
as much you can't see.

00:02:41.761 --> 00:02:43.722 align:center
You get your API key from

00:02:44.523 --> 00:02:46.164 align:center
your provider and paste it in

00:02:46.204 --> 00:02:46.424 align:center
there.

00:02:47.004 --> 00:02:47.805 align:center
So you can go in

00:02:48.392 --> 00:02:51.333 align:center
and edit statistics like your measurement

00:02:51.393 --> 00:02:53.353 align:center
data, SPC statistics, or if you

00:02:53.373 --> 00:02:56.133 align:center
have attribute or defect data, you

00:02:56.173 --> 00:02:58.054 align:center
can edit those statistics as well

00:02:58.114 --> 00:03:00.074 align:center
in terms of what goes out.

00:03:00.234 --> 00:03:01.274 align:center
You can choose from a couple

00:03:01.314 --> 00:03:03.815 align:center
of hundred statistics to send out,

00:03:03.895 --> 00:03:05.035 align:center
and then obviously you can set

00:03:05.075 --> 00:03:06.995 align:center
up your prompt that goes with

00:03:07.075 --> 00:03:08.336 align:center
the statistics.

00:03:08.756 --> 00:03:10.696 align:center
Now, if you are a pretty

00:03:10.716 --> 00:03:12.636 align:center
hardcore programmer maybe and you want

00:03:12.656 --> 00:03:15.577 align:center
to try different models

00:03:16.553 --> 00:03:18.775 align:center
reduce your spend by reducing the

00:03:18.815 --> 00:03:20.976 align:center
number of tokens, that sort of

00:03:20.996 --> 00:03:21.117 align:center
thing.

00:03:21.157 --> 00:03:22.538 align:center
You can edit the default values.

00:03:23.939 --> 00:03:24.799 align:center
Feel free to go ahead and

00:03:24.839 --> 00:03:25.260 align:center
do that.

00:03:25.920 --> 00:03:27.922 align:center
And the test that we send

00:03:27.982 --> 00:03:29.463 align:center
out just to make sure everything's

00:03:29.563 --> 00:03:31.444 align:center
working, your API key URL and

00:03:31.464 --> 00:03:34.066 align:center
all that is correct, is a

00:03:34.287 --> 00:03:37.049 align:center
pretty simple one for an AI

00:03:37.089 --> 00:03:38.149 align:center
with a square root of four.

00:03:38.210 --> 00:03:39.851 align:center
Hopefully it knows that it's two.

00:03:40.832 --> 00:03:42.233 align:center
So I think that's about it

00:03:42.413 --> 00:03:43.433 align:center
for the demo.

00:03:45.234 --> 00:03:47.199 align:center
We're pretty excited about adding the

00:03:47.640 --> 00:03:51.070 align:center
AI interface to GainSeeker Suite.

00:03:51.370 --> 00:03:52.112 align:center
Thanks for listening.

00:03:52.313 --> 00:03:52.493 align:center
Bye.