From 933f9fb4793e0f9760505f96e2885b04c919df4b Mon Sep 17 00:00:00 2001
From: ibelyaev <Ivan.Belyaev@cern.ch>
Date: Mon, 5 Mar 2018 18:01:45 +0100
Subject: [PATCH]  more

---
 advanced-bender/tools.md |  2 +-
 simulation/README.md     | 15 ++++++++++-----
 2 files changed, 11 insertions(+), 6 deletions(-)

diff --git a/advanced-bender/tools.md b/advanced-bender/tools.md
index 96ee899..ef793ea 100644
--- a/advanced-bender/tools.md
+++ b/advanced-bender/tools.md
@@ -67,4 +67,4 @@ BeamY              b__ENDVERTEX_NDOF  b__ENDVERTEX_YERR  b__FD_OWNPV        b__O
 b__DIRA_OWNPV      b__ENDVERTEX_X     b__ENDVERTEX_Z     b__IPCHI2_OWNPV    b__OWNPV_NDOF      b__OWNPV_YERR    
 b__ENDVERTEX_CHI2  b__ENDVERTEX_XERR  b__ENDVERTEX_ZERR  b__IP_OWNPV        b__OWNPV_X         b__OWNPV_Z       
 ```
-{% endchallenge %}
+{% endchallenge %}
\ No newline at end of file
diff --git a/simulation/README.md b/simulation/README.md
index e24de4e..8026035 100644
--- a/simulation/README.md
+++ b/simulation/README.md
@@ -28,11 +28,13 @@ dv = DaVinci ( Simulation      = True                      , ##
 Correct `DDDB/SIMCOND`-tags can be retrived in several  ways: 
   1. from `bookkeeping-DB` for the given production type
 {% challenge "Challenge (only for those who knows how to do it)" %}
-Do you know how to do it? If so make a try to use  this way. Please use the timer for comparison. 
+Do you know how to do it? If so make a try to use  this way. 
+  * Please use the timer for comparison. 
 {% endchallenge %}
   2. using the helper Bender scripts `get-dbtags` or `get-metainfo` for the given file 
 {% challenge "Challenge" %}
-Try to use these  scripts form the command line. Start with `get-dbtags -h` and `get-metainfo -h` and follow the instructions.
+Try to use these  scripts form the command line. 
+  * Start with `get-dbtags -h` and `get-metainfo -h` and follow the instructions.
 {% solution "Solution" %}
 <script src="https://gist.github.com/VanyaBelyaev/8e316f81caaccda69cb3b7ced2abd5d5.js"/></script>
 {% endchallenge %}
@@ -41,8 +43,9 @@ Try to use these  scripts form the command line. Start with `get-dbtags -h` and
 lb-run -c x86_64-slc6-gcc49-opt LHCbDirac/prod dirac-bookkeeping-decays-path 13104231
 ``` 
 {% challenge "Challenge" %}
-Make a try with this command. (Do not forget to obtain valid Grid proxy)
- * Is the output clear enough? 
+Make a try with this command. 
+  * (Do not forget to obtain valid Grid proxy)
+  * Is the output clear enough? 
 {% solution "Solution" %}
 The output is a list tuples. For each tuple one gets (in order)
    - The path in `bookkeeping-DB`
@@ -96,6 +99,8 @@ setData  ( inputdata , catalogs , castor , useDBtags = True ) ## <--- HERE!
 This is, probably, the most robust, safe and simultaneously the most convinient way 
 to treat `DDDB/SIMCOND`-tags for your application :-) 
 
-  
+The price to pay: since internally it relies on the functionality provided by `get-dbtags`-script, 
+for processing it could take addtional O(1-2) minutes to open the first input file 
+and to read `DDDB/SIMCOND`-tags from it.