Skip to content

modelplane requirements #145

@superdosh

Description

@superdosh
  • Configurable output column name
  • EvalContext metadata should be optional
  • Documentation for arbiter best practices
  • Cover the DAGAnnotator in documentation
  • Link back to mlflow artifacts
  • Allow prompt engineered stuff to take arbitrary substitutions (not just prompt/response)

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions