BUG all photos uploaded to ReefCloud with width=600 height=800

[gcoleman72]

The BUG was introduced to reefscan-desktop-data-manager while modifying for use with gen2 hardware.
The problem is at line 78 of sub_sample.py.

The width and height are written to file photos.json which is created during the subset operation and used by the reefcloud upload in reefscan_aws

My suggested fix is to remove height and width from the photos.json file created by reefscan-desktop-data-manager. Then modify reefscan_aws to ignore those columns if they exist. In this way there is no urgency to deploy the changes to reefscan-desktop-data-manager.

[lamontra]

What impact would this have for ReefClouds ingestion of the data?

[gcoleman72]

The step function sanity-check which is part of reefscan_aws will need to determine the height and width of each image programatically and pass that to the reefcloud upload via the established queue mechanism.

[lamontra]

@gcoleman72 Who pay's for that instance? Do we have a rough idea of added compute cost?

[gcoleman72]

I don't know do you want me to investigate this?

[gcoleman72]

Total cost for our ReefScan account is between $20 and $30 per month. Most of that is S3 (storage) costs. The green section labelled "other" includes lambda costs. Lambda is the serverless processing that we would use to do this job.

Gemini says:

[gcoleman72]

In aims_aws

Look at this lambda sanity_check/lambdas/check_photos_json.py

This reads the input file photos.json and breaks it into 500 metre long transects (line 92)

It creates a new photos.json for each transect.
Replace the width and height in the new file with the actual width and height of the photo.