|
|
*(AKA: Stuff that broke when I tried to use Bridges)*
|
|
|
|
|
|
- Trying to automagically generate the Pegasus `sites.xml` and `conf.rc` files probably isn't going to be feasible due to the variety of run-time environments people might be using. Probably better is to add command-line flags to the `chip-gen` script to specify paths to existing files which are then just copied to the workflow directory. We can provide examples in the docs for a few types of environments to help people create the files for their particular setup.
|
|
|
|
|
|
- DB files must exist locally or the code bails. This is fine when running directly, but when using BOSCO this means the DB will get staged again for every run via SSH. Would be better to allow specifying a location on the remote resource. This would require people to manually copy the files initially, but then Pegasus would just do symlinking for each run.
|
|
|
|
|
|
- Default resource requirements are way off.
|
... | ... | |