...
As text is typed into the search bar, the results of the search are updated almost immediately (but see Large file mode, below).
Caching
Once a remote file has been transferred and viewed, it will be cached locally to speed up future access. To get the latest version of a job's output, see Reload, below.
Job output
The job output tab has some additional functionality over the others, described in the following sub-sections.
...
Beneath the output file is a list of files available for that node; select a file to view its contents. The one file defined by ECF_JOBOUT is considered to be the the current one, and will be selected by default . It and is highlighted in the file list. Select a file to view its contentsIf ECF_TRYNO is 0 then the task is not currently running and hence there is no current output file; in this case the viewer will be empty until you select one of the files from the list.
Detailed file information
Since there can be several steps to retrieving an output file, this information is made available by clicking on the Information button in the toolbar.
Local output files
Output files may be read in one of three ways, attempted in the following order:
- from a log server (if defined)
- directly from disk (optional)
- from an ecFlow server
ecFlowUI will always attempt to obtain a file from the log server if it is defined for this task. Then, optionally, it attempts to read the file directly from disk if it is accessible. Finally, if the file has not yet been read, ecFlowUI will request the file from the ecFlow server.
This behaviour tries to avoid the situation where the wrong file is read because the same path exists on the machine where the task is running and on the machine where ecFlowUI is running, but they are not the same file. As an example, consider that the machine that ran the job wrote its output into a file called /tmp/myjob.1, where /tmp is a file system local to that machine. If a different file of the same name exists on the machine where ecFlowUI is running, this could be read instead of the 'real' output file.
If you know that this could be the case, you should go to the Server Settings and deactivate the option Read files from disk when appropriate.
| Anchor | ||||
|---|---|---|---|---|
|
Click the Reload button to obtain the latest version of the job output file. Note that these files can become very large, and can take some time to transfer across a network if they are hundreds of megabytes or more. If you are viewing an old output file and you click the Reload button, the file viewer will switch to the current version of the file (it assumes there is no need to reload an old version of the file). This button also causes the file listing to be updated.
Saving a local copy of the job output
The job output toolbar has a 'disk' icon which allows you to save a local copy of the currently-displayed file. This will invoke a standard 'file save' dialogue from where you can choose the location to save the file to.
Automatic search
...