 |
 |
Hi, Sho, what do you think of this? I know you wrote most of the ECAL monitoring drivers. Some of them were not copied to ecal.plots and only exist in drivers.ecal. Is it okay to sandbox the "old" drivers.ecal package? Anything we need later could be moved back to trunk. --Jeremy -----Original Message----- From: andrea.celentano [mailto:[log in to unmask]] Sent: Thursday, June 05, 2014 11:21 AM To: McCormick, Jeremy I.; hps-software Subject: R: forked package Hi, The monitoring app drivers for ecal are in monitoring.ecal.plots I copied them from drivers.ecal at the beginning of the development. You can move drivers.ecal in the sandbox if you want, they are not needed any longer. Andrea -------- Messaggio originale -------- Da: "McCormick, Jeremy I." Data:05/06/2014 20:00 (GMT+01:00) A: hps-software Oggetto: forked package Hi, Looking over some code today... It seems to me that org.hps.monitoring.drivers.ecal was forked into org.hps.monitoring.ecal.plots, as most of the classes are the same. I guess the ones in drivers.ecal were from the test run, but they are probably not needed any longer. One of these should be removed or they should both be combined into one package. Any opinions on this? --Jeremy ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the HPS-SOFTWARE list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=HPS-SOFTWARE&A=1 ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the HPS-SOFTWARE list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=HPS-SOFTWARE&A=1