Skip to content

Move kGriffinLayers into ConfigNoSSM, set kGemmaLayers directly#260

Merged
copybara-service[bot] merged 1 commit intodevfrom
test_644377361
Jun 18, 2024
Merged

Move kGriffinLayers into ConfigNoSSM, set kGemmaLayers directly#260
copybara-service[bot] merged 1 commit intodevfrom
test_644377361

Conversation

@copybara-service
Copy link

Move kGriffinLayers into ConfigNoSSM, set kGemmaLayers directly

For regular (non-SSM) Gemma models, kGriffinLayers is by definition always zero
and kGemmaLayers is just the number of layers.

@copybara-service copybara-service bot force-pushed the test_644377361 branch 2 times, most recently from 103f688 to f96c6f0 Compare June 18, 2024 14:45
For regular (non-SSM) Gemma models, kGriffinLayers is by definition always zero
and kGemmaLayers is just the number of layers.

PiperOrigin-RevId: 644384531
@copybara-service copybara-service bot merged commit d7d9d14 into dev Jun 18, 2024
@copybara-service copybara-service bot deleted the test_644377361 branch June 18, 2024 14:52
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.

1 participant