[ET Trac] [Einstein Toolkit] #1517: Make Simfactory tell you what it's doing

Einstein Toolkit trac-noreply at einsteintoolkit.org
Tue Jan 14 09:48:59 CST 2014

#1517: Make Simfactory tell you what it's doing
  Reporter:  sbrandt      |       Owner:  eschnett           
      Type:  enhancement  |      Status:  review             
  Priority:  optional     |   Milestone:  Cactus_4.3.0       
 Component:  SimFactory   |     Version:  development version
Resolution:               |    Keywords:                     

Comment (by rhaas):

 Hmm, outputting the same information twice certainly should be avoided.
 Having lookied at the dprint routine that the uberftp cude uses, I think
 we are not quite doing the right thing though. Most likely we should use
 info() or dprint() instead of just print to make sure that the information
 also appears in the simfactory log file. Currently both info() and
 dprint() always write to the log file, so to get the behaviour we just
 implemented (but also writing to the log) we'd need another dprint wrapper
 eg "verbose_info" (or replicate the verbosity level in the callers).

 Also seems to me as if libutil.py's dprint code contains a bug in that it
 does not check for flag == USE_VERBOSE and does not actually implement
 what the comment just above indicates.

Ticket URL: <https://trac.einsteintoolkit.org/ticket/1517#comment:9>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit

More information about the Trac mailing list