From 0c646bbf70f9be25d8d2fb25292a68928a3f1265 Mon Sep 17 00:00:00 2001
From: Leo Gordon <lg4@ebi.ac.uk>
Date: Mon, 19 May 2014 15:53:57 +0100
Subject: [PATCH] cosmetic/bugfix: refer to load_resource_usage.pl in usage
legend instead of lsf_report.pl that is no longer around
---
modules/Bio/EnsEMBL/Hive/PipeConfig/HiveGeneric_conf.pm | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/modules/Bio/EnsEMBL/Hive/PipeConfig/HiveGeneric_conf.pm b/modules/Bio/EnsEMBL/Hive/PipeConfig/HiveGeneric_conf.pm
index ee3c9f8c6..a25566317 100644
--- a/modules/Bio/EnsEMBL/Hive/PipeConfig/HiveGeneric_conf.pm
+++ b/modules/Bio/EnsEMBL/Hive/PipeConfig/HiveGeneric_conf.pm
@@ -718,10 +718,10 @@ sub useful_commands_legend {
" # At any moment during or after execution you can request a pipeline diagram in an image file (desired format is set via extension) :",
"\tgenerate_graph.pl -url $pipeline_url -out $pipeline_name.png",
'',
- " # If you are running the pipeline on LSF, you can collect actual resource usage statistics :",
- "\tlsf_report.pl -url $pipeline_url",
+ " # Depending on the Meadow the pipeline is running on, you may be able to collect actual resource usage statistics :",
+ "\tload_resource_usage.pl -url $pipeline_url",
'',
- " # After having run lsf_report.pl, you can request a resource usage timeline in an image file (desired format is set via extension) :",
+ " # After having run load_resource_usage.pl, you can request a resource usage timeline in an image file (desired format is set via extension) :",
"\tgenerate_timeline.pl -url $pipeline_url -out timeline_$pipeline_name.png",
'',
" # Peek into your pipeline database with a database client (useful to have open while the pipeline is running) :",
--
GitLab