Closed dan-homebrew closed 9 months ago
We should ideally capture most if not all of the Model and Inference Engine settings, that Oobabooga, and etc avail.
See LiteLLM's approach to prefix, suffix and roles and prompt templates
https://github.com/abetlen/llama-cpp-python/issues/717#issuecomment-1722093969
One question is also whether there should be a "Hardware Settings", e.g. for Apple Silicon users? Is this also present for other types of Hardware - e.g. Intel, etc.
@dan-jan for current release there will be no different in settings for different hardwares, mostly already automatically handled at build time
important asset reference for prompt template: https://github.com/mounta11n/plusplus-caMalL/blob/4fa32ad0e3b61a6e13cdb6261723b6fd608a0fad/examples/server/public/promptFormats.js#L15
Q:Where are these prompt template coming from? Most of community projects now using TheBloke metadata as referrence, example.
https://huggingface.co/TheBloke/LLaMA2-13B-Psyfighter2-AWQ#prompt-template-alpaca-tiefighter
We will have 2 main modes: LOCAL and REMOTE
LOCAL
REMOTE
Link to excalid draw: https://excalidraw.com/#json=kOBPg9OoLTCLAm3JO7FHn,qV29wMh7fLvGkFXf5HRYNA
Asks:
schema fields
id:
type:
required: boolean
data_validation: {
min:
max:
}
default:
information: // (i) that tells users what this field actually does
Discussion updates, mostly as a reminder/reference for @imtuyethan
Based on: https://app.excalidraw.com/s/kFY0dI05mm/3WHim5p2OLu
Assistant Section: Add back the model selector
inference parameters
, model params
engine params
content may change depending on the model chosen.Users can change Assistant Instructions
aka the system message
system message
may show up in MainPane differently, not as a regular message sent from the user, but as a little box/styled differently?We shouldn't auto save when users edit each field. We should make users click a global save
button, which saves all sections at once.
thread.json
Users must restart model after editting model_params
or engine_parameters
model_parameters
& engine_parameters
, then they have to save & restart model
, a two step process. @imtuyethan will play around with how the designs communicate this.Alan is working on parameter fields, like mins/max/etc.
Model Parameters
section UI
prompt template
as in a plain text box. Advanced users can directly edit the text. Do not highlight : “{prompt}” “{system_message}”, or do anything fancy like Daniel suggested XD.Actually play around with having a reset button for each sections, at the section level (not global)
@Rex make sure every model has a prompt template filled in
Alan TODO later: low fidelity mock on how “model.json settings is different than thread.model.json settings”
Remote model side panel - we didn't discuss this as much. Punt till later
@imtuyethan
A note on the menu items, I saw that we currently open up model.json
assistant.json
when users click "Reveal in Finder/JSON" in all the sections.
It should be
@imtuyethan , please help to verify this. cc @louis-jan
Tasks
model.json
Threads
,Assistants
,Models
,Engines
.model.json
params are well documented in Swaggerfileassistant.json
params are well documented in Swaggerfileengine.json
params are well documented in SwaggerfileSpec
Overview
assistant.json
assistant.model
'smodel.json
model.engine
'sengine.json
thread.json
thread.json
is usually empty, as it auto-inherits properties from the associated defaultsWireframes
Excalidraw: https://link.excalidraw.com/l/kFY0dI05mm/3WHim5p2OLu