Update README.md
Browse files
README.md
CHANGED
|
@@ -14,10 +14,11 @@ capacity that the two experts can enable simultaneously with the current build.
|
|
| 14 |
|
| 15 |
So in a sense, the experts will say what the settings are most likely going to be most optimized at, by making a quick soup.
|
| 16 |
|
| 17 |
-
This should provide the necessary yields that I require, assuming I pick experts with relationally similar math.
|
|
|
|
| 18 |
|
| 19 |
-
|
| 20 |
-
|
| 21 |
|
| 22 |
## Flows, Routes, Patterns, Trajectories, Magnitudes, Etc
|
| 23 |
Everything mathematically will have a represented flow attenuation mechanism specifically aligned to the curation of that math.
|
|
|
|
| 14 |
|
| 15 |
So in a sense, the experts will say what the settings are most likely going to be most optimized at, by making a quick soup.
|
| 16 |
|
| 17 |
+
This should provide the necessary yields that I require, assuming I pick experts with relationally similar math. So... parameter narrowing soup for now,
|
| 18 |
+
eventually the system should be able to directly self-attenuate the parameters for the best suggested parameters at the get-go.
|
| 19 |
|
| 20 |
+
The models themselves will never be trained by the experts, only the params selected by what is most likely. The models will never see an expert opinion directly,
|
| 21 |
+
nor will they be given gradients from anything expert-related. Everything in a vacuum.
|
| 22 |
|
| 23 |
## Flows, Routes, Patterns, Trajectories, Magnitudes, Etc
|
| 24 |
Everything mathematically will have a represented flow attenuation mechanism specifically aligned to the curation of that math.
|