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

Allow to Specify Additional, Task and/or dataset Specific Resources #479

Open
mam10eks opened this issue Aug 10, 2023 · 3 comments
Open
Labels
enhancement New feature or request stale Inactive issues

Comments

@mam10eks
Copy link
Member

When we now want to make LLMs available in TIRA (such as Alpaca or other instruction-based models), we should pay attention that a software can be executed against different (especially future, simulated, or commercial) LLMs without adoption.

Therefore, Johannes had the idea that one can select a second type of resources that might be dependent on the task/dataset. I.e., that I can select in the first select box the resources on which my software runs on (e.g., "4CPU's + 40GB RAM") and in a second select box I can select which ChatNoir Chat Access token and endpoint configuration I want to have injected into my software execution. For security reasons, the ChatNoir Chat version accessible from within TIRA should only be available within TIRA, no one else (besides admins) should be able to access it.

@potthast I think a previous version of TIRA already allowed the injection of API keys if I remember correctly for the plagiarism source retrieval task?

@mam10eks mam10eks added the enhancement New feature or request label Aug 10, 2023
@mam10eks
Copy link
Member Author

This might be a good motivation that the public version of ChatNoir chat is not even running in our own infrastructure but within OWS?

@mam10eks
Copy link
Member Author

cc @MattiWe, @kaaage

Copy link

github-actions bot commented May 2, 2024

This issue has been marked stale because it has been open 60 days with no activity.

@github-actions github-actions bot added the stale Inactive issues label May 2, 2024
@github-project-automation github-project-automation bot moved this to Discussion Candidates in Agenda Aug 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request stale Inactive issues
Projects
Status: Discussion Candidates
Development

No branches or pull requests

1 participant