W. David Dagenhart

@pfs I can reproduce the assert failure. I'll continue working on that. I've only been in this part of the code once to fix a bug 4 years ago, so...

I am still working to remember or figure out how this is supposed to work, but this avoids the assert if added to the PoolSource in the consuming configuration: ```labelRawDataLikeMC...

Kind of arcane. The ```labelRawDataLikeMC``` is a backward compatibility feature for reading data written with a release dating back to around 2013. If you read an input file made with...

Below are two relevant emails from 2011 and 2012 from the hyper news that explain the normal naming scheme for branches containing FEDRawDataCollection for real data. I'm not sure how...

The code fails the assert because the implementation of ```labelRawDataLikeMC``` uses a vector of ProcessConfiguration's read directly from the input file. This vector exists in the input file for pre...

@pfs The solution I recommend is that you follow the pattern in FedRawDataInputSource and use the DaqProvenanceHelper. I've have not done that myself yet. If you have problems, ask for...

I just submitted a PR to change the assert to an exception. See #45159

+1 Great! My PR was also just merged. I recommend closing this Issue also. I'm not sure my +1 does anything or who actually has authority to close it...

Just to make sure I understand how this works. The text string "?scitag.flow=" gets appended to the PFN. Once that is done with the correct value for the ID, then...

I'm thinking that maybe we should also allow a configuration parameter value that turns packet labeling off, maybe 0 means don't add the CGI parameter to the PFN. Or do...