Adding the functionality to run the 4 process setup but with ND fronte…

[alexbooth92]

…nd type. There should be no affect on any of the existing functionality. I have run the two tests below, but I would ask for reviewers to look closely at the changes given it is my first time implementing such a thing.

• I have verified that running, for example, python -m minidaqapp.nanorc.mdapp_multiru_gen --host-ru localhost -d ./frames.bin -o . -s 10 mdapp_4proc behaves as before.
• I have verified that passing --frontend-type pacman produces a configuration that can be run using nanorc and successfully writes pacman frames generated by pacman-generator.py in lbrulibs to hdf5.

[bieryAtFnal]

Hi Alex, Sorry for not getting to this sooner.

As you did, I successfully ran some configurations that didn't include pacman readout.

When I ran with the pacman readout type, I noticed that the HDF5 detector-level Group names were "Invalid" instead of something like "NDLArTPC". I presume that you noticed the same thing. I can look into fixing that in the dfmodules repo.

• Ah, sorry, I see that you've already made those changes - thanks!

To test the pacman readout, I used steps like the following (mainly included for my reference):

• created a software area that had this branch of minidaqapp in it
• added the lbrulibs repo to the software area
  • cd sourcecode; git clone https://github.com/DUNE-DAQ/lbrulibs.git -b develop; cd ..
• cloned the larpix-control repo into the top directory of the software area and installed it into the python virtual environment
  • git clone https://github.com/larpix/larpix-control.git
  • cd larpix-control
  • git checkout v3.5.1
  • pip install larpix-control
• started the pacman-generator at the appropriate time (when a run had been started with nanorc in another shell window)
  • cd sourcecode/lbrulibs/test
  • python pacman-generator.py --input_file example-pacman-data.h5

[alexbooth92]

That's great thank you for taking a look!