Upload FAQ.md with huggingface_hub
Browse files
FAQ.md
CHANGED
|
@@ -61,6 +61,19 @@ Use the full methods if you want richer diagnostics.
|
|
| 61 |
The bundle will still run.
|
| 62 |
But prediction quality may be weaker because richer fields will use fallback defaults.
|
| 63 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 64 |
## Will I get the exact same answers as your internal environment?
|
| 65 |
Not necessarily.
|
| 66 |
|
|
|
|
| 61 |
The bundle will still run.
|
| 62 |
But prediction quality may be weaker because richer fields will use fallback defaults.
|
| 63 |
|
| 64 |
+
## Why does the model talk about 48 signals if the sample CSV has fewer raw columns?
|
| 65 |
+
Because the wrapper builds the final model input row before inference.
|
| 66 |
+
|
| 67 |
+
Some signals come from:
|
| 68 |
+
- raw columns already present in the history CSV
|
| 69 |
+
- rolling features derived from past match results
|
| 70 |
+
- fallback defaults when richer optional columns are missing
|
| 71 |
+
|
| 72 |
+
So:
|
| 73 |
+
- the model expects `48` numeric signals at prediction time
|
| 74 |
+
- your history CSV does not need to contain all `48` as raw columns
|
| 75 |
+
- but a richer CSV helps the wrapper build a stronger feature row
|
| 76 |
+
|
| 77 |
## Will I get the exact same answers as your internal environment?
|
| 78 |
Not necessarily.
|
| 79 |
|