This change helps avoid stale TriggerRecords between the TriggerRecordBuilder and the DataWriter. (It may also help other cases, but I haven't explicitly tested that.)
For the TRB-> DataWriter case, I used the following confgen command to test the code before and after the change:
daqconf_multiru_gen -t 5.0 --use-fake-data-producers -d $PWD/frames.bin -o <a slow disk location> -s 10 -n 5 -b 100000 -a 100000 mdapp_fdp
This change helps avoid stale TriggerRecords between the TriggerRecordBuilder and the DataWriter. (It may also help other cases, but I haven't explicitly tested that.)
For the TRB-> DataWriter case, I used the following confgen command to test the code before and after the change:
and the following nanorc command:
To check for errors, I used the dfmodules:kbiery/DataWriterInvalidRunCheck branch and the following command:
NB that I included the appfwk, ipm, and networkmanager repos in my software area, along with the iomanager repo.