OkayStudy
EN English 한국어 日本語 中文 हिन्दी বাংলা اردو Español Português Français Deutsch Русский العربية Bahasa Indonesia Tiếng Việt ไทย Türkçe

How to enable notifications

Notifications are unavailable in this browser or on this address. Try a supported browser on the secure BaeumNova site.

If notifications are blocked, allow them in your browser settings.

  1. Open the site controls beside the address bar, or your browser’s site settings. Set Notifications for this site to Allow.
  2. In your device settings, allow notifications for your browser and check Do Not Disturb or Focus.
  3. Return to BaeumNova and reload the page. Once notifications are on, the bell disappears.

On iPhone or iPad, add BaeumNova to your Home Screen, open it there, then allow notifications.

Guest

Sign in to see your lesson schedule.

Getting started

Start English lessons step by step

Tap a step to go there.

Free trial

  1. Pick a free trial teacher

    Tap a teacher with [Free trial] on the photo.

  2. Tap a time with a gift

    Tap a free time with a gift picture in the timetable.

  3. Sign in and book

    Sign in and it is booked right away. No payment.

  4. Camera & Mic Check

    Check your camera and mic before class.

  5. Check your booked lessons

    See the time and tutor of your booked lesson.

  6. Enter the lesson

    Join the video classroom when it’s time.

  7. Check your past lessons

    Look back at the lessons you finished.

  8. Rate your tutor

    Rate your tutor after the lesson.

About me

  1. Add your profile photo

    A photo helps your tutor recognize you.

  2. Introduce yourself

    Write a hello on the introductions board.

Take lessons

  1. Book a lesson

    Pick a time on a tutor’s timetable.

  2. Pay the lesson fee with PayPal

    Pay on PayPal — your lesson is booked as soon as PayPal confirms it.

  3. Check your booked lessons

    See the time and tutor of your booked lesson.

  4. Enter the lesson

    Join the video classroom when it’s time.

  5. Check your past lessons

    Look back at the lessons you finished.

  6. Rate your tutor

    Rate your tutor after the lesson.

The road your request travels

An office where a robot receptionist sends a question card to just three of many expert desks, and only those three lit-up experts work on it
The whole path at a glance

From the text an AI learned to the answer on your screen

First text is gathered and a is built from it (). Then the finished model answers by computing the next , one at a time (). On the upper path the change; on the lower path the weights stay fixed and the model only computes.

Real XSLM computation The numbers are real values from running XSLM, a small learning model, with its default settings. Only the bars marked "Illustrative example" use hand-picked scores.

Building the model — training Weights change

  1. Collect data
  2. Clean it up
  3. Into tokens and numbers
  4. Train again and again

Training loop: predict → compare with the answer → compute the loss → adjust the weights

Using the model — inference Weights fixed

  1. A person asks
  2. Input into numbers
  3. Model computes
  4. Pick the next token
  5. Turn back into text
  6. Show on screen

Answer loop: compute the next token → pick one → append it to the input → compute again (stops at an end mark or a length limit)

  • Data (text)
  • Token
  • Weight
  • Probability
  • Sentence
Many kinds of writing pass through a cleaning machine and become a tidy stack of data

① Prepare the data to learn from

Web pages, books, and conversations are gathered, and and people filter out duplicates and low-quality text. Part of it is kept aside as a test set (validation data).

XSLM XSLM: 15 lines → duplicates removed → 12 for training · 3 for validation

Learn more
A strip of text is cut into token pieces and each piece is linked to a row of numbers

② Turn text into numbers

The sentence is cut into token pieces, each piece gets a number, and that number fetches a bundle of numbers (an ).

  1. Q:␣29
  2. s22
  3. u24
  4. n18
  5. ↵1
  6. A:␣30
  7. t23
  8. h13
  9. e11
  10. ␣2
  11. s22
  12. u24
  13. n␣31
  14. is␣35
  15. w25
  16. a7
  17. r21
  18. m.39
  19. ↵1

XSLM Vocabulary of 40 · this sentence is 19 pieces

Learn more
A robot guesses a hidden piece, measures the difference and turns the adjustment knobs

③ Learn the weights by predicting

The next piece is hidden and the model guesses it. The difference from the answer (the ) is sent backwards to adjust the weights a little.

Prediction goes forward The correction goes backward

XSLM Computing the same window again: loss 3.7050 → 3.6684

Learn more
A blueprint, weights, a tokenizer and settings packed into one box and loaded into a server

④ Finish the model to use

After training, the model is measured on validation data it has never seen, and the design, learned weights, and settings are saved as one bundle. Large chat models get extra training and evaluation before this. A loads the bundle into .

XSLM XSLM: 9 matrices · 1,248 weights · validation loss 3.7568 → 3.7298

Learn more
Question pieces pass through the model, become probability bars, and the biggest piece is appended

⑤ Compute the next token

The question is turned into numbers and fed to the model. Every candidate gets a score, the scores become and one piece is picked. The picked piece is appended and the model computes again.

Illustrative example — word-level If the model had learned longer the sun is …
  • warm63.2%
  • hot23.2%
  • blue10.4%
  • run3.1%

Weights fixed The weights do not change here.

Learn more
Tokens turn into text and appear in a chat window on a laptop, with the whole path in the background

⑥ It becomes an answer a person can read

The picked numbers are turned back into characters, and the sends them to the , which shows them in the chat window.

the sun is warm.

The XSLM runner sends the answer once it is finished; most chatbots stream it while they write.

Learn more

Try it yourself

Follow the same sentence "⁨the sun is warm.⁩" and press the buttons to see how tokens, embeddings, weights and probabilities differ.

Token number and embedding

Press a piece: its number and its bundle of numbers (embedding) light up together.

Token number — just a number that points to the piece; it has no meaning
t 23

Embedding — 8 numbers decided by training

Before training
  1. 0.11
  2. -0.03
  3. 0.28
  4. -0.12
  5. 0.09
  6. -0.03
  7. 0.01
  8. 0.07
After 20 training steps
  1. 0.11
  2. -0.03
  3. 0.28
  4. -0.12
  5. 0.09
  6. -0.02
  7. 0.01
  8. 0.07

One training step Weights change

The fresh model predicts → measures the loss → adjusts the weights on this sentence window, one step at a time.

  1. Q:␣
  2. s
  3. u
  4. n
  5. ↵
  6. A:␣
  7. ?
Piece to guess
t
Probability of the right piece
3.2%
Loss
3.7050
  1. Before training · Loss 3.7050

One answer step Weights fixed

XSLM, trained for only 20 steps, picks one piece at a time after the question. The weights are fixed.

Answer so far Q:␣sun↵A:␣

  • Q:␣5.4%
  • .3.8%
  • A:␣i3.4%
  • A3.1%
  • t3.1%
  • All other candidates81.3%

Picked piece —

A probability is how likely a candidate is to come next, not how likely the answer is to be true. After only 20 steps the model still picks odd pieces — the answer in the is "⁨the sun is warm.⁩".

The big picture — five places

  • Your computer
  • The
  • Remote machines
1

The program on my computer

A , a , an app. It takes your request and decides what to send.

Zones 1 and 5 are the same computer: yours

Inside place three — the distant calculating machine

Once
  1. Large files on hold the learned numbers and information used to load the .
  2. A reads it and puts it on a chip built for calculating, then keeps it there.
Every time
  1. A doorkeeper checks the key and the request waits its turn.
  2. The calculating runs against the numbers that are already up there.

Step by step

Eight steps, in order. Step eight is where the road forks.

1

You send it

Keyboard and mouse go through the , which hands the signal to the you are looking at. The microphone is different: only if you allow it, the program takes the sound and turns it into letters with — or sends the sound to a that can listen directly.

Two roads, not one

Drawing these as a single road is where the frightening misunderstanding comes from. They are not the same.

8 Here the road forks

Talking only

  1. Text on screen
  2. Ends here
Read more

Letters flow onto the screen and that is the end of it. Nothing on your computer is touched. Lyen, the study helper on this site, works this way.

Borrowing hands

  1. Spotting a tool request
  2. Asking permission
  3. Actually doing it
  4. Packing the result

The result goes into the bag at step two and out again at step three

Read more

What comes back is still only text. When that text is a tool request — "edit this file" — the on your computer checks it and does it instead. Then it packs the result into the bag at step two and sends it off again at step three, and the conversation continues. That loop is what people call an .

A well-built program asks you before it deletes a file or runs a command — and it is people who decide to switch that question off. That question is the safety catch: the program enforces it, not a polite instruction to the model.

Practise checking destructive commands

If we must compare it to something

The model is a part that only calculates; the body is the program on your computer, or the service around it. A calculating part has no hands — it cannot create a file or open an app by itself. It can only ask, in text. Whatever actually moves is done by the program, within what it is allowed to do.

  • The is the body and the model is its calculating part — and the body can swap that part. The same editor can be wired to a model from a different company tomorrow.

  • One calculating part serves crowds of people who do not know each other, all at the same time. Nothing alive could do that.

Two more things

The machine is not always far away

This site’s study helper goes through our server

Three roads a request can take
1 · Your app 2 · The 3 · Remote machine 4 · The calculating 5 · Your screen
Inside my own Yes No No Yes Yes
By way of our Yes Yes Yes Yes Yes
On a distant company’s machine Yes Yes Yes Yes Yes

On the middle road (through our ), the real calculating still happens on the third road, on a company's machine far away. Our server only checks the request and carries it.

Read more

Small models can run inside your own computer. The voice on this site works that way: once the is downloaded, turning text into speech happens on your device. Chatting is different — those messages still go through BaeumNova to the service.

Open the study helper and ask it something. Your sends it to our server, and our server hands it to a distant calculating machine. The letters coming back in pieces is step six; the letters growing on your screen is step seven. The helper stays on the talking-only road: it never touches a file on your computer.

The study helper. Our server passes the request along; it does not run a model.

This is where the calculating happens. Which runtime they use in there is not published.

Notes for grown-ups

Slightly more exact wording, for anyone who wants it.

Token

A model does not read words. A cuts the text into — sometimes a whole word, sometimes a few letters, sometimes a single — and each one becomes a number. Different models cut the same sentence differently, so the same text can count as a different number of tokens.

Streaming

Partial output is pushed out as it is produced, usually over . How big each piece is differs by product; some send a sentence at a time rather than a token.

Kinds of model

(large language model), (small language model), (vision-language model), and for images and video. LLMs and SLMs differ mainly in size, VLMs also read pictures, and diffusion models mostly produce pictures and video (diffusion language models that write text exist too).

The pick

How the next token is chosen is a setting. Turn the down and the model takes the highest score more often, so the same input gives more similar answers; turn it up and they vary more. Even at zero, real services do not promise exactly the same answer every time, and a steadier answer is not a more correct one.

RAG, MCP, skills

Names for ways of putting more into the bag. searches documents and attaches what it finds; is an that connects AI apps to outside tools and ; skills are prepared sets of instructions. Which of them are available is decided by the app's settings and — never by the model alone.

Programs that run models

What this site actually uses is (for speech) and (for dictation). For large language models on a server, programs with the same job — , , and others — are used instead. Which company runs which is not published.

Weights, parameter count and file size

are numbers learned during . include weights and other learned values, such as biases. A has about 70 billion parameters; reduces the used to store them, not their count. Here, “weight size” means the size of all these stored model parameters.

Weight size in bytes ≈ parameter count × bits per parameter ÷ 8. Divide by 8 because 1 byte is 8 bits. For 70B at 4 bits: 70,000,000,000 × 4 ÷ 8 = 35,000,000,000 bytes, or 35 in decimal units. This excludes quantization and working .

Q4, Q6 and Q8: the same numbers in less space

, Q6 and Q8 usually mean roughly 4, 6 and 8 per . For the same , the theoretical sizes are 35 , 52.5 GB and 70 GB. Against a 16-bit baseline of 140 GB, these are 25%, 37.5% and 50%.

These are estimates, not exact download sizes. Formats such as mix precisions and add scales and . Quantization approximates values more coarsely and can reduce answer quality; it does not remove .

70B: theoretical weight size (decimal GB)
  • FP16 / BF16 140 GB · 100%
  • Q8 70 GB · 50%
  • Q6 52.5 GB · 37.5%
  • Q4 35 GB · 25%
Does an unquantized original always mean 16 bits?

No. Many released store their original in or BF16, both 16-bit formats. They use the same storage per value but differ in range and precision. This comparison uses a 16-bit original as an example.

“Original” is not a bit width: a checkpoint may instead use (32 ), mixed precision, or already weights. Check the and the actual . Calling every original “16-bit” would be incorrect.

Does a smaller file use less memory and GPU?

Saving usually makes the files smaller. If the keeps them packed in , weight memory also shrinks. Quantizing only while loading can leave the original files unchanged; expanding weights while loading can increase memory again.

memory ≈ weights + + temporary buffers + . Weight quantization does not automatically quantize the KV cache. Longer conversations and more simultaneous requests can need more . / utilization and speed do not scale directly with bit width: support, unpacking and transfer matter.

Is a model one file containing numbers and a program?

The largest part of a typical download is learned numbers arranged in . A model can occupy one file or many shards, with configuration and files alongside. Settings describe the architecture; the tokenizer maps text pieces to .

can bundle tensors, architecture and tokenizer information; stores tensors and metadata, with architecture settings often separate. can also describe a . Describing a structure is different from including the engine that executes it. such as or are separate that read this information and run calculations on /.

Think of a recipe, its measured ingredients and a cook: the model describes what to calculate and the learned values to use; the runner performs the steps. It is misleading to say that an ordinary model file contains the entire execution program.

Read next

Booking time has passed

Voice chat with Lyen Pick a language and a topic, then talk with Lyen by voice

Lyen speaks aloud in English · 한국어 · 日本語 · हिन्दी. In other languages she answers in text.

Voice chat with Lyen is for members. Sign up first, then start talking.