Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't find 'adapter_config.json' #3466

Closed
1 task done
may012345 opened this issue Apr 26, 2024 · 1 comment
Closed
1 task done

Can't find 'adapter_config.json' #3466

may012345 opened this issue Apr 26, 2024 · 1 comment
Labels
solved This problem has been already solved.

Comments

@may012345
Copy link

Reminder

  • I have read the README and searched the existing issues.

Reproduction

want to train dpo

#!/bin/bash

CUDA_VISIBLE_DEVICES=0 python ../../src/train_bash.py
--stage dpo
--do_train
--model_name_or_path BASE_MODEL
--adapter_name_or_path FINETUNED_MODEL
--create_new_adapter
--dataset orca_rlhf
--dataset_dir ../../data
--template default
--finetuning_type lora
--lora_target q_proj,v_proj
--output_dir ../../saves/LLaMA2-7B/lora/dpo
--overwrite_cache
--overwrite_output_dir
--cutoff_len 1024
--preprocessing_num_workers 16
--per_device_train_batch_size 1
--per_device_eval_batch_size 1
--gradient_accumulation_steps 8
--lr_scheduler_type cosine
--logging_steps 10
--warmup_steps 20
--save_steps 100
--eval_steps 100
--evaluation_strategy steps
--load_best_model_at_end
--learning_rate 1e-5
--num_train_epochs 1.0
--max_samples 1000
--val_size 0.1
--dpo_ftx 1.0
--plot_loss
--fp16

Expected behavior

error. cannot run dpo.
Should I just put FINETUNED_MODEL at "--model_name_or_path" and delete "--adapter_name_or_path"?

System Info

ValueError: Can't find 'adapter_config.json' at '/path/to/FINETUNED_MODEL'

Others

No response

@hiyouga
Copy link
Owner

hiyouga commented Apr 26, 2024

if you have merged lora adapters to the base model, just use --model_name_or_path only, otherwise, put your sft lora to --adapter_name_or_path

@hiyouga hiyouga added the solved This problem has been already solved. label Apr 26, 2024
@hiyouga hiyouga closed this as completed Apr 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
solved This problem has been already solved.
Projects
None yet
Development

No branches or pull requests

2 participants