Add Mammo-FM risk Stage 1 and Stage 2 checkpoints
Browse files
risk_checkpoints/Mammo-FM_risk_stage1_distillation_fold1.pth-best.tar
ADDED
|
@@ -0,0 +1,3 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
version https://git-lfs.github.com/spec/v1
|
| 2 |
+
oid sha256:bd16aa6dba9f1812d52947a325df92cd8aace440ddec2fee21cbd8357fcdf41a
|
| 3 |
+
size 184831762
|
risk_checkpoints/Mammo-FM_risk_stage2_finetuning_fold1.pth-best.tar
ADDED
|
@@ -0,0 +1,3 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
version https://git-lfs.github.com/spec/v1
|
| 2 |
+
oid sha256:397098ff49c914dba52a56c9c3ec530fe4d1637170a0a536d5e84c0dc95bc6cf
|
| 3 |
+
size 184831762
|
risk_checkpoints/README.md
ADDED
|
@@ -0,0 +1,39 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
# Mammo-FM risk checkpoints
|
| 2 |
+
|
| 3 |
+
The historical risk artifacts are released at
|
| 4 |
+
[`batmanLab/Mammo-FM/risk_checkpoints`](https://huggingface.co/batmanLab/Mammo-FM/tree/main/risk_checkpoints).
|
| 5 |
+
|
| 6 |
+
| File | Original training stage | Payload epoch | Bytes | SHA-256 |
|
| 7 |
+
| --- | --- | ---: | ---: | --- |
|
| 8 |
+
| `Mammo-FM_risk_stage1_distillation_fold1.pth-best.tar` | MIRAI probability distillation | 17 | 184,831,762 | `bd16aa6dba9f1812d52947a325df92cd8aace440ddec2fee21cbd8357fcdf41a` |
|
| 9 |
+
| `Mammo-FM_risk_stage2_finetuning_fold1.pth-best.tar` | supervised five-year risk training | 8 | 184,831,762 | `397098ff49c914dba52a56c9c3ec530fe4d1637170a0a536d5e84c0dc95bc6cf` |
|
| 10 |
+
|
| 11 |
+
These files are uploaded byte-for-byte under descriptive release names. Their
|
| 12 |
+
payloads contain `model`, `optimizer`, `scheduler`, and `epoch`. They do not
|
| 13 |
+
contain explicit `stage`, `fold`, validation loss, class weights, teacher
|
| 14 |
+
provenance, or base-model configuration. “fold1” is retained from the original
|
| 15 |
+
filename rather than inferred from checkpoint metadata.
|
| 16 |
+
|
| 17 |
+
The historical model state contains 1,763 entries because its wrapper
|
| 18 |
+
registered the same EfficientNet image encoder at both `image_encoder.*` and
|
| 19 |
+
`aggregator.image_encoder.*`. The two namespaces are duplicates within each
|
| 20 |
+
file. `mayo_mammofm_risk.model.compatible_model_state` verifies tensor equality
|
| 21 |
+
and removes only the duplicate namespace, leaving 911 keys for strict loading.
|
| 22 |
+
|
| 23 |
+
The original Mayo launchers explicitly identify these exact filenames as the
|
| 24 |
+
Stage 1 and Stage 2 Mayo models. The payloads themselves do not contain enough
|
| 25 |
+
metadata to independently re-establish that lineage, so the original path,
|
| 26 |
+
filename, payload inventory, and hashes are retained as provenance. Between
|
| 27 |
+
the two checkpoints, all image-encoder parameter tensors remain identical;
|
| 28 |
+
only BatchNorm running means, variances, and counters differ. This matches the
|
| 29 |
+
historical wrapper leaving frozen BatchNorm modules in training mode. The
|
| 30 |
+
cleaned runner corrects that behavior and therefore may not reproduce the
|
| 31 |
+
historical numbers bit-for-bit.
|
| 32 |
+
|
| 33 |
+
The historical optimizer state is not resumed by the cleaned runner. Only
|
| 34 |
+
model weights are loaded. A compatible Mammo-FM base checkpoint is also
|
| 35 |
+
required to construct the image-encoder configuration before loading either
|
| 36 |
+
file.
|
| 37 |
+
|
| 38 |
+
The repository's model-weight license applies. The weights are for
|
| 39 |
+
non-commercial academic research and must not be used for clinical decisions.
|