Rarely-used plugins should be optional targets, outdated ones removed #843
Comments
|
Hi,
CDC_expert can be retired.
I think these can be made optional. Someone else (Sean, Mark?) might wish
to retain the skims in the default build set.
- cdcbcal_skim.so
- cdc_goodtrack_skim.so
- CDC_PerStrawReco.so
- CDC_roc_hits.so
- dedx_tree.so
Could we make all of the non-production plugins optional unless someone
speaks up for them?
Naomi.
…On Fri, Sep 27, 2024 at 11:13 AM Alexander Austregesilo < ***@***.***> wrote:
We currently compile 165 plugins by default. This takes time and the
compiled libraries take up disk space. Only about 50% of the plugins are
regularly used for in production, for monitoring, calibration or analysis.
Many others are outdated or only serve a very limited purpose.
Could we identify which plugins are important to be included in the
default build, which ones can be kept as optional targets and which ones
can be retired? Here is a list of all plugins that are currently compiled
by default. I marked the ones used in production:
- 1p1pi1pi0.so
- 1p2pi.so
- 2trackskim.so
- b1pi_hists.so
- B3pi_eff_missgamma.so
- B3pi_eff_misspim.so
- B3pi_eff_misspip.so
- B3pi_eff_missprot.so
- BCAL_attenlength_gainratio.so
- BCAL_Eff.so
- BCAL_gainmatrix.so
- BCAL_Hadronic_Eff.so
- BCAL_inv_mass.so
- BCAL_LEDonline.so
- BCAL_LED.so
- BCAL_LED_time.so
- BCAL_online.so
- BCAL_point_calib.so
- BCAL_point_time.so
- BCAL_saturation.so
- BCAL_SiPM_saturation.so
- BCAL_TDC_Timing.so
- BEAM_online.so
- bigevents_skim.so
- cal_high_energy_skim.so
- CCAL_online.so
- CDC_amp.so
- cdcbcal_skim.so
- CDC_dedx.so
- CDC_drift.so
- CDC_Efficiency.so
- CDC_expert_2.so
- CDC_expert.so
- cdc_goodtrack_skim.so
- CDC_online.so
- CDC_PerStrawReco.so
- CDC_roc_hits.so
- CDC_TimeToDistance.so
- coherent_peak_skim.so
- compton_neutral_skim.so
- compton.so
- cppFMWPC_ana.so
- cppFMWPC.so
- cpp_hists.so
- cpp_itrig.so
- cpp_skim.so
- danarest.so
- DAQ_online.so
- DAQTreeBCAL.so
- DAQTree.so
- dedx_tree.so
- dirc_hists.so
- DIRC_online.so
- dirc_reactions.so
- dirc_tree.so
- EPICS_dump.so
- es_test.so
- eta2g_primexd_skim.so
- eta6g_primexd_skim.so
- etapi0_primexd_skim.so
- EventTagPi0.so
- evio-hddm.so
- evio_writer.so
- exclusivepi0skim.so
- fa125_itrig.so
- fcal_charged.so
- FCAL_cpp.so
- FCAL_Hadronic_Eff.so
- FCAL_invmass.so
- FCAL_LED_shifts.so
- FCALLEDTree.so
- FCAL_online.so
- FCAL_Pi0HFA.so
- FCAL_Pi0TOF.so
- FCAL_TimingOffsets_Primex.so
- FDC_Efficiency.so
- FDC_InternalAlignment.so
- FDC_online.so
- FDCProjectionResiduals.so
- FMWPC_online.so
- FMWPC_Performance.so
- HELI_online.so
- highlevel_online.so
- HLDetectorTiming.so
- imaging.so
- L1_online.so
- lowlevel_online.so
- lumi_mon.so
- lut_dirc.so
- mcthrown_hists.so
- mcthrown_tree.so
- MilleFieldOff.so
- MilleFieldOn.so
- MilleKs.so
- monitoring_hists.so
- npp_hists.so
- npp_skim.so
- occupancy_online.so
- omega_skim.so
- p2gamma_hists.so
- p2k_hists.so
- p2pi0_hists.so
- p2pi_hists.so
- p3pi_hists.so
- p4pi_hists.so
- pedestal_online.so
- phi_skim.so
- pi0bcalskim.so
- pi0fcalskim.so
- pi0fcaltofskim.so
- Pi0Finder.so
- pid_dirc.so
- ppi0gamma_hists.so
- primex-online.so
- PSC_online.so
- PSC_TW.so
- PS_E_calib.so
- PS_flux.so
- PS_online.so
- PSPair_online.so
- ps_skim.so
- PS_timing.so
- randomtrigger_skim.so
- ReactionEfficiency.so
- ReactionFilter.so
- RF_online.so
- RSAI_KO.so
- run_summary.so
- scaler_primex.so
- SC_Eff.so
- single_neutral_skim.so
- ST_online_efficiency.so
- ST_online_lowlevel.so
- ST_online_multi.so
- ST_online_tracking.so
- ST_online_Tresolution.so
- ST_Propagation_Time.so
- ST_Tresolution.so
- st_tw_corr_auto.so
- syncskim.so
- TAGGER_online.so
- TAGH_online.so
- TAGH_timewalk.so
- TAGM_clusters.so
- TAGM_online.so
- TAGM_TW.so
- timing_online.so
- TOF_calib.so
- TOF_Eff.so
- TOF_online.so
- TOF_TDC_shift.so
- TPOL_online.so
- TPOL_tree.so
- trackeff_hists.so
- trackeff_missing.so
- TrackingPulls.so
- TrackingPulls_straight.so
- track_skimmer.so
- TRD_hists.so
- TRD_online.so
- trigger_skims.so
- TRIG_online.so
- truth_dirc.so
- TS_scaler.so
- twogamma_fcal_skim.so
—
Reply to this email directly, view it on GitHub
<#843>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADXOCVQDPLRL3SE46537LRTZYVY2DAVCNFSM6AAAAABO7LY43GVHI2DSMVQWIX3LMV43ASLTON2WKOZSGU2TGMJYGA2TCMI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
|
what does "retired" mean, here? removed from the repo? |
|
@sdobbs Correct. In scenarios where a plugin was superseded by another one or if a plugin would require significant changes to even compile, we could remove it. |
|
One thing we could consider is making some of the plugin subdirectories optional targets - like if you had to explicitly request the alignment or monitoring plugins to be built |
|
Here are my comments / opinions on these plugins:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We currently compile 165 plugins by default. This takes time and the compiled libraries take up disk space. Only about 50% of the plugins are regularly used for in production, for monitoring, calibration or analysis. Many others are outdated or only serve a very limited purpose.
Could we identify which plugins are important to be included in the default build, which ones can be kept as optional targets and which ones can be retired? Here is a list of all plugins that are currently compiled by default. I marked the ones used in production:
The text was updated successfully, but these errors were encountered: