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

Support Multi-choice Tasks (Manipulate the completion tokens) #520

Closed
MM-IR opened this issue Jul 19, 2023 · 3 comments
Closed

Support Multi-choice Tasks (Manipulate the completion tokens) #520

MM-IR opened this issue Jul 19, 2023 · 3 comments

Comments

@MM-IR
Copy link

MM-IR commented Jul 19, 2023

Hi, I have noticed my previous failures now.
#Previous Failures

That is, for some multi-choice tasks, e.g., multi-choice sentence completions, in most common-sense reasoning tasks, we do need to manipulate the completion tokens, instead of current Samplingparams which generate token-by-token on LLMs themselves.

That is, autoregressive LMs will adjust their logprobs each step with different inputs. For MC tasks, we do need to input the correct prefix to LMs.

How can we enable so?

@MM-IR
Copy link
Author

MM-IR commented Jul 19, 2023

Otherwise, I do need to query multiple prompts for the same LM in serving this task.

For instance,

  • Prompt: ABC.
  • Completion 1: DE.
  • Completion 2: FG.

Then, in current implementations, I can only prompt with ABC=>ABCD, and ABC=>ABCF for the cumulative probabilities results...

  • Is this one less efficient, or achieving on par efficiency?

@MM-IR
Copy link
Author

MM-IR commented Jul 19, 2023

A better solution is to prompt query + Option together, and obtain their logits/logprobs at the same time..

@hmellor
Copy link
Collaborator

hmellor commented Mar 8, 2024

Closing because this is now supported via guided decoding #2819

@hmellor hmellor closed this as completed Mar 8, 2024
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

2 participants