if we don't overload it then everything is a DatumFiller according to this statement, causing trouble for APICaffe
[NORMAL] <TrainProcessDriver::configure> Instantiating Process ID=0 Type: ADCThreshold w/ Name: ADCThres
[NORMAL] <TrainProcessDriver::configure> Instantiating Process ID=1 Type: SegFiller w/ Name: SegFiller
(ADCThreshold)
Is it datumfiller? 1
Is it an aho? 1
(SegFiller)
Is it datumfiller? 1
Is it an aho? 0
ADCThreshold is is both aho and DatumFiller since we sent a non-empty string.
Fix is to define virtual is(...) for ADCThreshold class and call it something else.
ThreadDatumFiller
complains that there are two DatumFillers, when infact there is only one specified in apicaffe_cleanuphttps://github.com/LArbys/LArCV/tree/apicaffe_cleanup
branch.
On line 50 of ProcessBase.h
virtual bool is(const std::string& question) const { return !(question.empty()); }
if we don't overload it then everything is a
DatumFiller
according to this statement, causing trouble for APICaffeADCThreshold is is both
aho
andDatumFiller
since we sent a non-empty string.Fix is to define
virtual is(...)
for ADCThreshold class and call it something else.