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
Due to the way the API is designed, a file must first be uploaded, then attached to a model output in 2 discrete calls.
We implement this with the methods/CLI:
upload_files (or some variant thereof)
attach_files_to_model_output
This will become tedious once scripted in conjunction with benchcab.
I suggest we add optional arguments to the upload routines to specify a model output that does little more than issue the attach command immediately after the upload.
I'm in discussions with UNSW as to the ramifications of this approach.
The text was updated successfully, but these errors were encountered:
Due to the way the API is designed, a file must first be uploaded, then attached to a model output in 2 discrete calls.
We implement this with the methods/CLI:
upload_files
(or some variant thereof)attach_files_to_model_output
This will become tedious once scripted in conjunction with benchcab.
I suggest we add optional arguments to the upload routines to specify a model output that does little more than issue the attach command immediately after the upload.
I'm in discussions with UNSW as to the ramifications of this approach.
The text was updated successfully, but these errors were encountered: