... | ... | @@ -10,6 +10,12 @@ One solution to this is to create a web interface which will allow communication |
|
|
This is a major project, and will require development of a new database for storing the asimov ledger, back-end interface work, and front-end interface work.
|
|
|
However, it has the potential to substantially improve the process of setting-up a run, and making it easier for non-pipeline experts to rapidly produce results.
|
|
|
|
|
|
### Improved error logging
|
|
|
|
|
|
A major problem we encountered in O3 was tracking down the sources of errors and runtime problems.
|
|
|
We need an easier way of accessing errors which arise within asimov, as well as collecting errors from the pipelines it is monitoring in a more efficient manner.
|
|
|
A major difficulty for this, at least naively, is a pipeline like RIFT which generates thousands of separate error files.
|
|
|
|
|
|
### Condor improvements
|
|
|
|
|
|
The process for tracking jobs progress in condor was hacky and unreliable in O3. This problem was partially solved when producing the post-processing pipeline, and the code from that should be merged back in to the main project.
|
... | ... | |