workflUX
workflUX copied to clipboard
An open-source, cloud-ready web application for simplified deployment of big data workflows.
Currently, an execution profile can overwrite the automatically set status by a custom status. The custom status is only displayed when the status indicates an unproblematic state. This should be...
Add instructions to the documentation.
Elixir gives you the option to select:  ... for sharing with CWLab. CWLab needs the first 3 elements. Therefore, either make them non-optional or show an error message to...
Workflow metadata is not correctly stored. In the `*.job_templ.xlsx`, the data remains at the packed intermediate: 
Currently: - prepare - exec - monitor - finish Whereby, finish is for cleaning up. Additionally add methods for: - terminate - reset (terminate and remove (intermediate) output) - delete...
Draft in the config yaml could be: ```{yaml} INPUT_SOURCES: LocalFileSystem: - name: scratch path: /scratch - name: ngs_share path: /mnt/ngs_share UploadToFileSystem: - name: scratch path: /scratch URL: True ````
Currently, run params are saved to file. It would be better if the file creation is avoided completely.
Currently, any user can request the run list for any job by providing the correct job id. This should be changed. But for the project-based organization, it might not be...
Currently, connections between database models are inferred via names (username, job_name, run_name, ...). To make querying more efficient names could be replaced by id (foreign keys). Things to consider: -...