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

Does fine tuning tasks re-initiate optimizer states? #1478

Open
garywei944 opened this issue Dec 26, 2023 · 0 comments
Open

Does fine tuning tasks re-initiate optimizer states? #1478

garywei944 opened this issue Dec 26, 2023 · 0 comments

Comments

@garywei944
Copy link

I'm trying to reproduce the T5.1.1 fine-tuning on GLUE result from this paper https://arxiv.org/pdf/2110.08529.pdf. I read through the configuration and source code implementation of Adafactor from this repo to ensure that I'm using consistent hyper-parameters while training using hugging face and pytorch.

However, I can't reproduce the performance. I have preprocessed the GLUE dataset as something like
<task_name> sentence1: <sentence1> sentence2: <sentence2> <EOS>
following the SeqIO GLUE preprocessor in the T5 repo.

Another reason I could think of that can cause this performance drop is that when fine-tuning from .gin config file, the optimizer state is also loaded from the checkpoint and then the fine-tuning happens. But this is infeasible to reproduce if one only has access to publicly accessible checkpoints.

I tried to run this repo and add breakpoints but didn't get it. Could someone help me confirm if the optimizer state is loaded if we run fine-tuning scripts from this repo?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant