Skip to content

Conversation

dan-garvey
Copy link
Member

Clarified the state of LlamaHParams and added some light design suggestion for future extension.

Clarified the state of LlamaHParams and added some light design guidance for future extension.
Copy link
Contributor

github-actions bot commented Oct 1, 2025

Coverage report

Click to see where and how coverage changed

FileStatementsMissingCoverageCoverage
(new stmts)
Lines missing
  sharktank/sharktank/layers/configs
  llm_configs.py
Project Total  

This report was generated by python-coverage-comment-action

Comment on lines 62 to 64
See the optional_configs under the get_custom_configs function
for an example of how to add support for custom Params without
basing conditionals on a name prefix.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am a bit confused as get_custom_configs
would conditionally populate fields based on the model name prefix.

I think the main point is to have fields in the structure that have general/abstract names such that they survive and can be reused for new models.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah what I was trying to get at is that the optional_keys under that function are agnostic to the name prefix provided. I'll make that clearer

@dan-garvey dan-garvey requested a review from sogartar October 2, 2025 20:46
@dan-garvey dan-garvey enabled auto-merge (squash) October 6, 2025 01:22
@dan-garvey dan-garvey merged commit 26bf73d into main Oct 6, 2025
39 checks passed
@dan-garvey dan-garvey deleted the llm_config_comments branch October 6, 2025 01:32
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