updates for CPP low level hits

[sdobbs]

• add handling of writing out all the appropriate fields for FMWPC hits to HDDM event format
• add ability to apply thresholds to both the digit hit amplitude and integral. we can implement the appropriate CCDB table after this

[gluex]

Test status for this pull request: SUCCESS

Summary: /work/halld/pull_request_test/halld_recon^sdobbs_fmwpc_fix_oct2024/tests/summary.txt
Logs: /work/halld/pull_request_test/halld_recon^sdobbs_fmwpc_fix_oct2024/tests/log

Build log: /work/halld/pull_request_test/halld_recon^sdobbs_fmwpc_fix_oct2024/make_sdobbs_fmwpc_fix_oct2024.log
Build report: /work/halld/pull_request_test/halld_recon^sdobbs_fmwpc_fix_oct2024/report_sdobbs_fmwpc_fix_oct2024.txt
Location of build: /work/halld/pull_request_test/halld_recon^sdobbs_fmwpc_fix_oct2024

[aaust]

I tried to write out events with randomtrigger_skim from a CPP evio file, and I get these entries:

      <fmwpcChamber layer="6" wire="77">
          <fmwpcHit dE="0" t="184">
            <fmwpcHitQ q="0" />
            <fmwpcHitQ q="1194" />
            <fmwpcDigiHit amp="0" ped="0" qf="0" />
          </fmwpcHit>
        </fmwpcChamber>
        <fmwpcChamber layer="6" wire="78">
          <fmwpcHit dE="0" t="340.8">
            <fmwpcHitQ q="0" />
            <fmwpcHitQ q="1663" />
            <fmwpcDigiHit amp="0" ped="0" qf="0" />
          </fmwpcHit>
        </fmwpcChamber>

For comparison, the master produces this:

        <fmwpcChamber layer="6" wire="77">
          <fmwpcHit dE="0" t="184">
          </fmwpcHit>
        </fmwpcChamber>
        <fmwpcChamber layer="6" wire="78">
          <fmwpcHit dE="0" t="340.8">
          </fmwpcHit>
        </fmwpcChamber>

Do you understand why HitQ is written out twice, once with 0 value? And why are all digihit entries 0?

[aaust]

@sdobbs Did you have any more insights on this?

[sdobbs]

Thanks for the reminder on this, I will take a look.