<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi Alex,<div class=""><br class=""></div><div class="">I think I’m satisfied with the process you’ve outlined, so we’ll plan to work on the master branch for now. I don’t anticipate any issues with our plugins failing to build or interfering with anything else.</div><div class=""><br class=""></div><div class="">On a different topic, do you have the ability to create us a directory <font face="Menlo" class="">/cache/halld/SRC-CT</font> for us to use as a common space for the analysis, or else can you give us the permissions to do so ourselves?</div><div class=""><br class=""></div><div class="">Thanks,</div><div class="">Jackson<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Sep 21, 2021, at 2:17 PM, Alexander Austregesilo <<a href="mailto:aaustreg@jlab.org" class="">aaustreg@jlab.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hi Jackson,<br class=""><br class="">Our policy for pull request only requires the automatic build test (<30min) and one additional person to approve. This can be done very quickly, and since you are just submitting a plugin, there is no great danger of breaking the code.<br class=""><br class="">For an even quicker turn-around, changes to the online system can also be done in real time on the online machines, but one has to be careful.<br class=""><br class="">Apart from unnecessary forking, the problem of working with branches is that there is no guarantee that the code even compiles.<br class=""><br class="">Cheers,<br class=""><br class="">Alex<br class=""><br class="">On 9/21/2021 2:07 PM, Jackson Reeves Pybus wrote:<br class=""><blockquote type="cite" class="">Hi Alex,<br class=""><br class="">I like the option to test our plugins during the PrimeX run, but I also want to make sure we reserve the ability to make quick changes to them during our run time if necessary.<br class="">Is there a process in place for getting pull requests accepted quickly? Would working on a separate branch give us the benefits of direct access to change the code with less delay?<br class="">What I don’t want is for us to be in our run time and for any changes we decide we need to make to the plugins to take days to propagate, so it would be good to know how the different options could work in this regard.<br class=""><br class="">Jackson<br class=""><br class=""><blockquote type="cite" class="">On Sep 19, 2021, at 9:35 PM, Nathaly Santiesteban <<a href="mailto:ssanties@jlab.org" class="">ssanties@jlab.org</a>> wrote:<br class=""><br class="">Sounds good, we will share it this week.<br class=""><br class="">Talk you soon!<br class=""><br class="">Nathaly<br class=""><br class="">On 9/18/21 11:25 AM, Alexander Austregesilo wrote:<br class=""><blockquote type="cite" class="">Hi Nathaly,<br class=""><br class="">We are not running a special branch for the PrimEx data monitoring, I just have to change a few configuration lines for the reconstruction without magnetic field.<br class=""><br class="">Having your analysis plugins in the master branch would give us the advantage that we can test them right away.<br class=""><br class="">Best regards,<br class=""><br class="">Alex<br class=""><br class="">On 9/17/2021 1:43 PM, Nathaly Santiesteban wrote:<br class=""><blockquote type="cite" class="">Thank you for your prompt answer. That sounds great.<br class=""><br class="">Let's increase that number for our run to 20% please. I don't think we need to increase that number into the low level and standard plugins, so may be you can increase the number for our specific plugins, that will be other option.<br class=""><br class="">Also other question for our branch, I think we can use our branch and use that one for our experiment. Now, the question is if that branch is up-to-date with the master one, where master means the standard Gluex configuration of the past run with magnetic field before Primex. I am not sure if Primex has other requirements in the branches.<br class=""><br class="">Thank you again,<br class=""><br class="">Nathaly<br class=""><br class=""><br class=""><br class="">On 9/17/21 1:29 PM, Alexander Austregesilo wrote:<br class=""><blockquote type="cite" class="">Hi Nathaly,<br class=""><br class="">1.) The 'incoming monitoring' system is currently set up to run over 5 files automatically, but we can easily increase this number. The root files are merged and end up in:<br class=""><br class="">/work/halld/data_monitoring/RunPeriod-2021-08/mon_ver01/rootfiles/<br class=""><br class="">I would prefer if you could pull in the new plugins into the master branch, but I can also switch the system to use the SRC branch once your run starts.<br class=""><br class=""><br class="">2.) For permanent storage, I would suggest to use /cache/halld because the files will be automatically saved to tape. The work disk is not really backed up, so the files could be deleted accidentally.<br class=""><br class="">Cheers,<br class=""><br class="">Alex<br class=""><br class=""><br class="">On 9/17/2021 1:21 PM, Nathaly Santiesteban wrote:<br class=""><blockquote type="cite" class="">Dear Alex,<br class=""><br class="">Thank you for coming to our meeting last Tuesday.<br class="">We have a small group of people working in monitoring and we have some questions for you:<br class=""><br class="">1. In terms of using the halld_reco src branch to upload our scripts. We discussed that we could use the system to generate the rootfiles for later do our physics plots without using the online interface. Is that possible? If that is the case, what could be the location of those files? and can we setup to run it automatically with 20% of the data of each run?<br class=""><br class="">2. We want to generate some simulation files (hddm) for different channels and make that available to our students and group of people working in the experiment. They are not going to be very heavy, so I was thinking we could make a shared folder in /work/halld2/home or something similar. Can we do that or do you recommend other location that will be safe for us and our files won't disappear that would be the case of volatile.<br class=""><br class="">Thank you,<br class=""><br class="">Nathaly<br class=""><br class=""></blockquote></blockquote></blockquote></blockquote>_______________________________________________<br class="">Halld_srcct_analysis mailing list<br class=""><a href="mailto:Halld_srcct_analysis@jlab.org" class="">Halld_srcct_analysis@jlab.org</a><br class="">https://mailman.jlab.org/mailman/listinfo/halld_srcct_analysis<br class=""></blockquote></blockquote></div></div></blockquote></div><br class=""></div></body></html>