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

FEAT: Refactor PAIR to be a special instance of TAP #580

Merged
merged 6 commits into from
Dec 2, 2024

Conversation

rlundeen2
Copy link
Contributor

@rlundeen2 rlundeen2 commented Nov 28, 2024

This PR refactors PAIR to be a special instance of TAP. This simplifies a lot of logic. But the functionality should be identical as it was (the system prompts should be the same)

  • FEAT: refactoring PAIR to just be a specific case of TAP. The system prompts and turns should be identical, but maintenance is easier and we get certain features (like converters, better print_conversation that can display images)
  • FEAT: Adding desired_response_prefix as an option for TAP
  • FIX: generalizing multi-turn print_messages for different formats
  • MAINT: added tests for print_conversation_async

Note: Currently I am removing the single_turn option for PAIR, but will add it back soon for all multi-turn-orchestrators

Tests:

  • Ran TAP and PAIR notebooks

@rlundeen2 rlundeen2 merged commit c4fc7bc into Azure:main Dec 2, 2024
9 checks passed
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

Successfully merging this pull request may close these issues.

2 participants