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

task deployment configurations should be configured from config file #71

Open
wise-east opened this issue Sep 28, 2023 · 2 comments
Open
Assignees

Comments

@wise-east
Copy link
Collaborator

each customizable item for a task deployment should be configured inside a config file and the frontend should be loaded accordingly

e.g.

model: 
  type: dropdown
  items: 
    - gpt4
    - gpt3 
number_turns:
  type: slider 
  start: 1
  end: 4 
...
@wise-east
Copy link
Collaborator Author

the goal is to remove any hardcoded dependencies to darma. please open any other relevant issues that you deem suitable for this goal

@River-vocal
Copy link
Collaborator

River-vocal commented Oct 30, 2023

Refactoring steps to consider:

  1. Move the “limits” part of conf.yml into boteval repo.
  2. Create a new section in conf.yml to decide what options to display when creating a new task.
  3. The user of boteval can choose which entry of the “limits” will be displayed under the Actions column of topics.html (The entries not being displayed will always keep their default values)
  4. Create a new module under topics for the customized task deployment options
  5. We should have a new load_bot_agent() method under bots.py. Or we always initialize a new bot under the get_dialog_man() method of service.py.
  6. Following the previous bullet point, darma should have a new way to initialize a bot (with and only with a dict as argument)
  7. Each thread should store the customized dict setting

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

3 participants