SBND maintains two separate values for the pedestal: in database_sbnd.fcl and in detsimmodules_sbnd.fcl #9
Description
The pedestal info in detsim was updated within the last 1/2 year (collection ped==650) but that change did not propagate to the pedestal service (collection ped==400).
The SBND LArSoft event display, by default, reads pedestal information from the database which means you get a very angry raw event display with a baseline of 650-400==250 ADU.
Other areas of sbndcode, which require pedestal use, take their information directly from the raw::RawDigit whose pedestal info is calculated in the detsim stage which uses the firstly mentioned pedestal value. So, internally, a consistent pedestal value is subtracted in the places that really matter.
However, I think we should only maintain one set of pedestal values.
We can set the pedestal values in the pedestal service and point the detsim fcl param set to those values.