Open mogres opened 1 year ago
I updated the CORs rules on our bucket so the links work now. http://localhost:9001/viewer?trajUrl=https://cellpack-results.s3.us-west-2.amazonaws.com/jitter/seed_0_test_spheres_test_config_1.0.0_results.simularium
I updated the CORs rules on our bucket so the links work now. http://localhost:9001/viewer?trajUrl=https://cellpack-results.s3.us-west-2.amazonaws.com/jitter/seed_0_test_spheres_test_config_1.0.0_results.simularium
Confirmed this is working on simularium viewer. @meganrm are we good to close this issue or do we want to wait on reorganizing simularium files separately?
I think it would be good to have a workflow that looked like this:
cellpack-results
bucket but what we need to work out is how to keep the folder from ballooning. do we clear out older results? do we move things we want to keep to the simularium aws bucket?
ideally we'd also keep track of the meta data of these files in firebase. Ie, a json that has the recipe run, the person who ran it, creation date and link to the aws file. with the idea that in the long run we'd then be able to delete files through the database + a gui
I like the idea of adding the metadata, perhaps we could embed it within the Simularium file description as a first pass?
One idea we could implement to save space is clearing out old packing files periodically (every 30 days?) via github actions.
In Simularium helper:
[x] add upload_to_s3
which uploads the results to cellpack-results
using the s3 python sdk and then saves metadata to the firebase under results
collection. the metadata should have:
[x] add open_in_simularium
which takes in the was url and makes a Simularium url and opens it. ex: https://simularium.allencell.org/viewer?trajUrl=https://cellpack-results.s3.us-west-2.amazonaws.com/jitter/seed_0_test_spheres_test_config_1.0.0_results.simularium
.env
?open_in_simularium
? concerns:
pack
command will be performing multiple tasks.simularium
is added after the output path more than one place
Use Case
It would be useful to have simularium packing results available online (on S3 etc.) in order to share URLs for visualization.
Solution
Create a new public sub-bucket on AWS S3 to store simularium results and use the URL to load visualizations.
Alternatives
Dropbox, Drive, Firebase, etc. are alternative hosting services that could be used.