Project

General

Profile

Bug #5097

Warning messages when runing LBNE and uBooNE simulation

Added by Erica Snider almost 7 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
High
Category:
Simulation
Target version:
Start date:
12/15/2013
Due date:
% Done:

50%

Estimated time:
Occurs In:
Experiment:
-
Co-Assignees:
Duration:

Description

Several messages observed. Need to determine if they matter.

#1:

%MSG-w LArProperties: LArG4:largeant@BeginJob 15-Dec-2013 03:39:07 CST ModuleConst
ruction
!!! Extracting values from LArProperties before they have been read in from the dat
abase.
You may not be using the correct values of electron lifetime, temperature and electric field! You should not be initializing Database originating values in BeginJob()s or constructors. You have been warned !!!

#2:
TimeReport> Report columns headings for modules: eventnum runnum modulelabel modulen
ame timetaken
%MSG-w DatabaseUtil: PostSourceRun 15-Dec-2013 03:39:20 CST run: 1
Connection to database failed, fe_sendauth: no password supplied

%MSG
%MSG-w DatabaseUtil: PostSourceRun 15-Dec-2013 03:39:20 CST run: 1
DB Connection error

#3
%MSG-w DetectorProperties: LArG4:largeant@BeginJob 13-Dec-2013 23:42:39 CST ModuleConstruction
!!! Extracting values from DetectorProperties before they have been read in from the database.
You may not be using the correct values of T0! You should not be initializing Database originating values in BeginJob()s or constructors. You have been warned !!!

%MSG

Associated revisions

Revision b0bcb9ea (diff)
Added by Gianluca Petrillo over 6 years ago

Do not try to connect to an unexisting DB (issue #5097).
When DB are available, it will be necessary to revert the changes.

Revision 624d2fb5 (diff)
Added by Gianluca Petrillo over 6 years ago

Do not try to connect to an unexisting DB (issue #5097).
When DB are available, it will be necessary to revert the changes.

Revision 624d2fb5 (diff)
Added by Gianluca Petrillo over 6 years ago

Do not try to connect to an unexisting DB (issue #5097).
When DB are available, it will be necessary to revert the changes.

Revision 624d2fb5 (diff)
Added by Gianluca Petrillo over 6 years ago

Do not try to connect to an unexisting DB (issue #5097).
When DB are available, it will be necessary to revert the changes.

Revision 624d2fb5 (diff)
Added by Gianluca Petrillo over 6 years ago

Do not try to connect to an unexisting DB (issue #5097).
When DB are available, it will be necessary to revert the changes.

Revision 624d2fb5 (diff)
Added by Gianluca Petrillo over 6 years ago

Do not try to connect to an unexisting DB (issue #5097).
When DB are available, it will be necessary to revert the changes.

Revision 624d2fb5 (diff)
Added by Gianluca Petrillo over 6 years ago

Do not try to connect to an unexisting DB (issue #5097).
When DB are available, it will be necessary to revert the changes.

Revision 624d2fb5 (diff)
Added by Gianluca Petrillo over 6 years ago

Do not try to connect to an unexisting DB (issue #5097).
When DB are available, it will be necessary to revert the changes.

Revision 624d2fb5 (diff)
Added by Gianluca Petrillo over 6 years ago

Do not try to connect to an unexisting DB (issue #5097).
When DB are available, it will be necessary to revert the changes.

Revision 624d2fb5 (diff)
Added by Gianluca Petrillo over 6 years ago

Do not try to connect to an unexisting DB (issue #5097).
When DB are available, it will be necessary to revert the changes.

Revision 624d2fb5 (diff)
Added by Gianluca Petrillo over 6 years ago

Do not try to connect to an unexisting DB (issue #5097).
When DB are available, it will be necessary to revert the changes.

History

#1 Updated by Brian Rebel almost 7 years ago

none of these are important as no experiment database has yet been setup. We may want to update the messages to reflect that.

#2 Updated by Erica Snider almost 7 years ago

  • Target version set to v0_02_02
  • % Done changed from 0 to 50

#3 Updated by Erica Snider over 6 years ago

  • Status changed from New to Assigned
  • Assignee set to Gianluca Petrillo

#4 Updated by Erica Snider over 6 years ago

  • Priority changed from Normal to High
  • Target version changed from v0_02_02 to v1_01_00

#5 Updated by Gianluca Petrillo over 6 years ago

  • Status changed from Assigned to Resolved
  • Target version changed from v1_01_00 to v1_00_04

The default configuration has been updated so that no access to the database is attempted.
Each time a connection would occur, now a "I don't want to connect"-type of message occurs.
I tried also to reduce the verbosity of this message, but I am probably lacking some understanding of how the message service works.
The same change has been pushed also in one of the configuration files in uboonecode.

Note: when the DB become available for a given experiment, this change must be reverted for the configuration of the DB of that experiment (and only that, of course).

#6 Updated by Gianluca Petrillo over 6 years ago

  • Status changed from Resolved to Assigned

Reopening, as at least when running prodgenie_lbnefd.fcl the issue appears again.

#7 Updated by Gianluca Petrillo over 6 years ago

  • Status changed from Assigned to Closed

Fixed.

Also available in: Atom PDF