Set the run
Examples, batch size, epochs, gradient accumulation give total steps; or type steps directly.
Fine-tuning
A schedule is easier to reason about as a picture. Set the total steps from epochs and batches, the peak learning rate, warmup and the schedule type, and see the curve, the rate at any step, and the values as CSV or a code snippet for the framework you use.
Loading the tool…
Examples, batch size, epochs, gradient accumulation give total steps; or type steps directly.
Constant, linear decay, cosine, cosine with restarts, step decay, one-cycle, with linear warmup steps or ratio and a minimum rate.
CSV of step and rate, or the equivalent transformers get_scheduler / torch.optim.lr_scheduler call.
3-10 percent of steps for transformers; more when the batch is small or the model is fresh. Warmup avoids the early divergence a high rate causes on uncentred gradients.
Both end near zero; cosine keeps the rate high longer, which tends to help when the dataset is small and the run short.
Ending at 10 percent of peak rather than zero keeps late steps useful for LoRA runs of a few epochs.
Steps = ceil(examples / (batch x accumulation)) x epochs; the tool shows the arithmetic.
Ultralytics uses linear by default with cos_lr as an option; both are plotted with its warmup_epochs convention.
Yes; add a second schedule to compare.