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
@marcverhagen suggested the other day that he wants to store output MMIFs from CLAMS pipeline initiated by an evaluation "invoker", perhaps somewhere on github, for later access. This would require
a schema to store pipeline configuration with the results
naming convention for results files
large enough storage to store all the results
This issue to discuss the design of such storage system and track progress of implementation.
The text was updated successfully, but these errors were encountered:
Just for future reference, while finalizing M3P2 period with our first ever round of app evaluation, we did upload machine annotation files (MMIF) by hand, under relevant xxx_eval directory, using preds@ prefix.
@marcverhagen suggested the other day that he wants to store output MMIFs from CLAMS pipeline initiated by an evaluation "invoker", perhaps somewhere on github, for later access. This would require
This issue to discuss the design of such storage system and track progress of implementation.
The text was updated successfully, but these errors were encountered: