You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the generated .simularium file is named based on a variety of parameters in the recipe and config files that are submitted for a cellpack packing. This means if we wanted to know what the output file name is going to be at the time of submitting a packing request, we would have to read the recipe and config files in advance, which is inconvenient if we're submitting a AWS packing with a recipe path that's in firebase.
It would be good to have an override for the existing functionality so we can provide a output file name to the pack script that will be used when the .simularium file is written.
The text was updated successfully, but these errors were encountered:
Use Case
Currently, the generated .simularium file is named based on a variety of parameters in the recipe and config files that are submitted for a cellpack packing. This means if we wanted to know what the output file name is going to be at the time of submitting a packing request, we would have to read the recipe and config files in advance, which is inconvenient if we're submitting a AWS packing with a recipe path that's in firebase.
It would be good to have an override for the existing functionality so we can provide a output file name to the pack script that will be used when the .simularium file is written.
The text was updated successfully, but these errors were encountered: