[ 
https://issues.apache.org/jira/browse/AIRAVATA-3557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17487269#comment-17487269
 ] 

Marcus Christie edited comment on AIRAVATA-3557 at 2/15/22, 2:18 PM:
---------------------------------------------------------------------

I've got this mostly done, generally as described in the task description. 
There are still a few things to do:

- [ ] only display text files if they are less than some threshold in file size
- [ ] for now, just don't show output view providers menu when executing
- [ ] Fix entry function so that it works with Vuex as well
- [ ] either support downloading URI_COLLECTION as zip or remove it when 
URI_COLLECTION
- [ ] profile and tune full experiment endpoint, running a little slowly and 
this affects how quickly the UI can refresh for an executing experiment
- [x] need helix to update the process output with data product URI for 
wildcards to work
- [ ] view-experiment store: only one full experiment fetch at a time
- [ ] idea: add a checkbox for outputs to supply text/plain metadata in 
application interface editor (inline text output file view only works when file 
is known to be a text file)
- [ ] what to display when there is no output once experiment completes? Just 
don't show experiment output card?
- [ ] refresh the experiment data storage directory view as experiment executes 
and when completed
- [ ] fix blocking the UI while intermediate output fetch is running
- [ ] require WRITE access to use intermediate output fetching


was (Author: marcuschristie):
I've got this mostly done, generally as described in the task description. 
There are still a few things to do:

- [ ] only display text files if they are less than some threshold in file size
- [ ] for now, just don't show output view providers menu when executing
- [ ] Fix entry function so that it works with Vuex as well
- [ ] either support downloading URI_COLLECTION as zip or remove it when 
URI_COLLECTION
- [ ] profile and tune full experiment endpoint, running a little slowly and 
this affects how quickly the UI can refresh for an executing experiment
- [ ] need helix to update the process output with data product URI for 
wildcards to work
- [ ] view-experiment store: only one full experiment fetch at a time
- [ ] idea: add a checkbox for outputs to supply text/plain metadata in 
application interface editor (inline text output file view only works when file 
is known to be a text file)
- [ ] what to display when there is no output once experiment completes? Just 
don't show experiment output card?
- [ ] refresh the experiment data storage directory view as experiment executes 
and when completed
- [ ] fix blocking the UI while intermediate output fetch is running
- [ ] require WRITE access to use intermediate output fetching

> Update Experiment Summary to display intermediate output files
> --------------------------------------------------------------
>
>                 Key: AIRAVATA-3557
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-3557
>             Project: Airavata
>          Issue Type: Sub-task
>          Components: Django Portal
>            Reporter: Marcus Christie
>            Assignee: Marcus Christie
>            Priority: Major
>
> From mailing list discussion:
> {quote}As for UI, you're right. Currently the output file UI only displays 
> when an experiment is COMPLETED. I'm thinking of having a panel for each 
> output file that will display once the experiment is EXECUTING. Each panel 
> will have a button to fetch the current file. When the fetch is executing the 
> button is disabled and a spinner displays with a message that the file is 
> being fetched. Once the file is fetched, if it is a text file (and maybe 
> within some max file size limit) then it will display in the panel and the 
> user can scroll through the file. This is the main use case, retrieving the 
> current value of a log file or STDOUT or something similar. If the file is 
> too large or binary then instead of displaying the file directly there will 
> be a download button.  That's the general idea.{quote}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to