HiroseKoichi
commited on
Commit
•
a3ea066
1
Parent(s):
658c387
Update README.md
Browse files
README.md
CHANGED
@@ -19,7 +19,7 @@ One of the main reasons I started model merging was to create a model that's goo
|
|
19 |
|
20 |
Now that I think about it, is this really emergent behavior? It seems pretty obvious in hindsight that a model that's not trying to shove positivity up your ass at every turn would be more willing to generate "offensive" and realistic content.
|
21 |
|
22 |
-
Note: 2.0 seems to have more repitition than the
|
23 |
|
24 |
# Merging Tips
|
25 |
If I were to write a paper on model merging, it would be called "Model Stock Is All You Need" because it's seriously amazing. I've tried many different merge methods, and I could only get barely passable results after tweaking parameters all day, but Model Stock has consistently produced good models for me. I recently made a discovery, though in hindsight it's very obvious, but model order matters a lot when using Model Stock, and it can make or break a merge. I have found that models at the top of the list integrate more deeply into the model, and models at the bottom of the list keep more of their style in the final result. What this means is that you should put chaotic models and ones that add new capabilities at the top of the list and the more balanced and coherent ones at the bottom.
|
|
|
19 |
|
20 |
Now that I think about it, is this really emergent behavior? It seems pretty obvious in hindsight that a model that's not trying to shove positivity up your ass at every turn would be more willing to generate "offensive" and realistic content.
|
21 |
|
22 |
+
Note: 2.0 seems to have more repitition than the first. I'll try to fix that in future versions.
|
23 |
|
24 |
# Merging Tips
|
25 |
If I were to write a paper on model merging, it would be called "Model Stock Is All You Need" because it's seriously amazing. I've tried many different merge methods, and I could only get barely passable results after tweaking parameters all day, but Model Stock has consistently produced good models for me. I recently made a discovery, though in hindsight it's very obvious, but model order matters a lot when using Model Stock, and it can make or break a merge. I have found that models at the top of the list integrate more deeply into the model, and models at the bottom of the list keep more of their style in the final result. What this means is that you should put chaotic models and ones that add new capabilities at the top of the list and the more balanced and coherent ones at the bottom.
|