call path validation when initiating the packing for remote recipes

[rugeli]

Problem

What is the problem this work solves, including
closes #245

Solution

What I/we did to solve this problem
Added the function call back for remote packings.
Expected behaviors in merged pr #230

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)

[github-actions]

Packing analysis report

Analysis for packing results located at cellpack/tests/outputs/test_spheres/spheresSST

Ingredient name	Encapsulating radius	Average number packed
ext_A	25	236.0

Packing image

Distance analysis

Expected minimum distance: 50.00
Actual minimum distance: 50.01

Ingredient key	Pairwise distance distribution
ext_A

[rugeli]

Quickest way to get the remote recipe path is to copy and paste the field recipe_path within recipes collection.

[mogres]

Thanks for the quick update!

I was able to run the one_sphere recipe after deleting and reuploading it. The previous version did not have the recipe_path field and I wasn't able to update it by reuploading since a recipe with the same name was already in the firestore. Maybe some validation to update the recipe if the format/saved fields have changed might be useful?

[rugeli]

Thanks for the quick update!

I was able to run the one_sphere recipe after deleting and reuploading it. The previous version did not have the recipe_path field and I wasn't able to update it by reuploading since a recipe with the same name was already in the firestore. Maybe some validation to update the recipe if the format/saved fields have changed might be useful?

The Firebase system is still in active development, and as we're refining it, we may need to delete old test recipes periodically until things stabilize. I agree that adding validation in the future to handle updates, especially when fields or formats are missing, will be useful! Thanks for testing the database!