Closed mwartell closed 11 months ago
Armory-upload currently routes submitted model weights into an evalX folder (with everything else). But armory only knows to look for them under model-weights . I think in eval6 I sometimes copied the weights into model-weights so armory could find them easily. Going forward, what do you prefer: updating armory to search deeper (might be tricky to tell it which eval folder to look in), just having people download the weights themselves, or something else?
Hey that was my question . . .
But what if we just have armory-upload put them in both spots, then we can delete model-weights when no longer needed?
We are making AWS Lambda copy from eval?/CODE/email/model-weights/foo.pt
to model-weights/foo.pt
upon upload under #1962
Eval 7 is completed.
eval7
s3 destination foldereval7
folder