Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

create a serverless app to copy model_weights to destination directory #1962

Open
mwartell opened this issue Jul 18, 2023 · 1 comment
Open

Comments

@mwartell
Copy link
Contributor

The armory-uploader places its files in eval7/CODE/addr/model_weights on S3. However, Armory expects them to be in a flat directory.

The notification will be for a path like s3://armory-submission-data/eval6/JHUM/[email protected]/model-weights/JHUM_deformable_detr_AT.pth where the eval number, the CODE, and the address will be variable.

Using this example the function will want to copy that file JHUM_deformable_detr_AT.pth to a common model weights directory. We have assumed that the filenames will be unique in the common directory, because they always have been. The copy destination folder is s3://armory-submission-data/model-weights/

Find a way such that the lamba triggers when the upload is complete, and then initiate the copy action. These files can be on order of 1GB so copy will likely not be quick.

You should be able to test the lambda function by copying files to s3://armory-submission-data/eval7/GARD/[email protected]/model-weights/` using the AWS CLI

@swsuggs
Copy link
Contributor

swsuggs commented Oct 18, 2023

@mwartell This was completed, correct?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants