1 #ifndef RecoLocalCalo_HGCalRecProducers_KernelManagerHGCalRecHit_h
2 #define RecoLocalCalo_HGCalRecProducers_KernelManagerHGCalRecHit_h
5 #include "RecoLocalCalo/HGCalRecProducers/plugins/HGCalRecHitKernelImpl.cuh"
14 #include <cuda_runtime.h>
27 "The KernelConstantData class does not support this type.");
56 #endif //RecoLocalCalo_HGCalRecProducers_KernelManagerHGCalRecHit_h
The Signals That Services Can Subscribe To This is based on ActivityRegistry and is current per Services can connect to the signals distributed by the ActivityRegistry in order to monitor the activity of the application Each possible callback has some defined which we here list in angle e< void, edm::EventIDconst &, edm::Timestampconst & > We also list in braces which AR_WATCH_USING_METHOD_ is used for those or
HGCUncalibRecHitSoA h_uncalibSoA_
KernelManagerHGCalRecHit()
constexpr uint32_t calo_rechit_masks[]
~KernelManagerHGCalRecHit()
void run_kernels(const KernelConstantData< HGCeeUncalibRecHitConstantData > *, const cudaStream_t &)
KernelConstantData(T &data, HGCConstantVectorData &vdata)
ConstHGCRecHitSoA d_calibConstSoA_
char data[epos_bytes_allocation]
HGCConstantVectorData vdata_
void transfer_soa_to_device_(const cudaStream_t &)
void transfer_soa_to_host(const cudaStream_t &)
HGCUncalibRecHitSoA d_uncalibSoA_