hi -

in recent devval releases, i've been seeing these messages running 
the d3pd maker tests in physicsanalysis/d3pdmaker/d3pdmakertest:

+verbatim+
toolsvc.muonpropertiestool                           info initialize() successful in toolsvc.muonpropertiestool
toolsvc.trk::tracksummarytool                       error could get neither indethelpertool nor muonhelpertool. must abort.
toolsvc                                             error error initializing tool 'toolsvc.trk::tracksummarytool'
toolsvc.indetdetailedtrackselectortool               info  unable to retrieve.
-verbatim-


this is coming from the following tool hierarchy, set up from aodfix:

+verbatim+
  metrefinedalgorithm/metrefalg
    metmuontool/metrefalg.muonboytrack
      rec::muonselectortoool/metmuonselectortool
        rec::combinedmuonselectortool/metmuonselectortool.combinedmuonselectortool
          indet::indetdetdetailedtrackselectortool/indetdetailedtrackselectortool
            trk::tracksummarytool/trk::tracksummarytool
-verbatim-

none of the tools in the list above are configured in the toolsvc
for these jobs, so the c++ defaults are being used.  and an unconfigured
trk::tracksummarytool will give the errors above.

there is code in indetrecloadtools.py to configure
indetdetailedtrackselectortool.  however, that's run only on the
following conditions:

+verbatim+
if indetflags.dovertexfinding() or indetflags.domonitoringprimaryvertexingenhanced() or indetflags.dovtxmonitoringd3pd() or indetflags.dovtxntuple():
-verbatim-

none of which are true for this job.


for the purpose of making d3pds, i can paper this over, so that we're
not getting the error messages.  however, the met people should check
that the muon track selection is ok in this case, and if not,
work with the id people to fix it,
