Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,8 @@ It is designed to be used with this repository [FlowCron-Globus_Flow-side](https

First, clone this repository to Baskerville in your project directory, then run the setup. The only requirement for other HPC systems is to have slurm and cron available. You're chosen config will be stored in **~/.config/flowcron**, which can be changed in the setup.sh if you have more than one FlowCron instance. In setup.sh, you'll be asked to name the cron job, how often the cron job should run, and whether to add a timestamp to uploaded Units of Work to prevent similarly named Units of Work merging.

**Important:** The timestamp feature is currently not compatible with [FlowCron-Globus_Flow-side](https://github.com/rosalindfranklininstitute/FlowCron-Globus_Flow-side). Select *no* timestamp during setup if you intend to use the Globus Flow.

On a HPC system where there are multiple login nodes the cron file will be installed to the login node the setup script is run from.

Each time this runs it will create, if necessary, five new directories alongside **CodeToRun** called;
Expand Down
2 changes: 1 addition & 1 deletion setup.sh
Original file line number Diff line number Diff line change
Expand Up @@ -120,7 +120,7 @@ then
fi

yes_no=("Yes" "No")
echo "Would you like to add a timestamp to each uploaded Unit of Work to prevent clobbering? If no, we recommend you do that manually."
echo "Would you like to add a timestamp to each uploaded Unit of Work to prevent clobbering? Select no for Flowcron-Globus compatibility or if you intend to do so manually."
select yn in "${yes_no[@]}"
do
case $yn in
Expand Down