Fermilab Redmine: Issues 2020-01-17T13:44:02Z Fermilab Redmine Redmine artdaq - Support #23918 (New): Investigate CPU usage of DataLogger process at SBN 2020-01-17T13:44:02Z Eric Flumerfelt eflumerf@fnal.gov <p.</p> <p>I did find a few minor performance improvements, but the bulk of the art process time (>90%) was spent in ROOT libraries involved in writing data (i.e. WriteFastArray).</p> <p>I still intend to collect perf recordings of processes <em>in situ</em> at ICARUS, just to make sure there isn't anything specific to their environment.</p> LArSoft - Feature #23916 (New): Publish Doxygen tag files 2020-01-17T00:14:53Z Gianluca Petrillo petrillo@slac.stanford.edu <p>Doxygen allows to import the documentation from external projects.<br />It is as easy as adding <code>acsys-fe:source:dev-app|fanoutgain.erl</a> as an improvement to <a class="issue tracker-11 status-4 priority-4 priority-default parent" title="Task: Request for Device Driver that Fans Out a Setting (Feedback)" href="">#23907<> Front-end Group - Task #23907 (Feedback): Request for Device Driver that Fans Out a Setting 2020-01-15T23:15:26Z Dennis Nicklaus nicklaus@fnal.gov <p>Nathan Eddy request:<br />Implement software to provide a single device to switch the attenuation and gains for the IOTA bpm system. This involves changing attenuation in the analog modules and setting gains in the digitizers all through a variety of other ACNET devices. The new device would provide attenuation selections of 0db, 6db, 12db, 18db, 24db, and 30db then set all other other devices accordingly. Below are the devices and details.</p> <p>New device N:IBPATN should allow a picklist of settings</p> <ul> <li> 0 db</li> <li> 6 db</li> <li> 12 db</li> <li> 18 db</li> <li> 24 db</li> <li> 30 db</li> </ul> <p>When a setting is made from this device...</p> 1. Set the attenuators in all transition modules <ul> <li> in 2 front-end crates. Each crate has a different acnet interface a method to set the attenuation value (att = 0,6,12,18,24,30) as selected </li> <li> 1st crate (canbus from 5500) <ul> <li> set N:A1CATN to <ul> <li>0 for 0db</li> <li>12 for 6db</li> <li>24 for 12db</li> <li>36 for 18db</li> <li>48 for 24db</li> <li>60 for 30db</li> </ul> </li> </ul> </li> <li> 2nd crate (rasp pi on e-net) <ul> <li> Z:RP2BDN select board address 1</li> <li> Z:RP2CHN set to channel 15 for all</li> <li> Z:RP2ATN set to <ul> <li>0 for 0db</li> <li>12 for 6db</li> <li>24 for 12db</li> <li>36 for 18db</li> <li>48 for 24db</li> <li>60 for 30db</li> </ul></li> </ul></li> </ul> <p>2. Set N:IBPMGAINMODE to corresponding db setting – it has a picklist of settings from 0-30db.</p> GlideinWMS - Feature #23906 (New): Create a script to prune and purge the web-area 2020-01-15T22:40:01Z Marco Mambelli marcom@fnal.gov <p>The web-area is the staging area for the files downloaded by the glideins.<br />Its size can grow considerably, especially if there are many entries and if there are many reconfig/update operations.<br />Deleting files from it at random may cause inconsistencies that cause errors when the Factory is restarted.<br />This happens especially because of signature files and download lists, that may end up referencing files that have been deleted.</p> <p>A script for cleanup operations would be a useful tool. It should allow:<br />- purging of old files no more used by glideins or referenced by newer download files<br />- pruning files for entries that are no more in use<br />All of the above without removing files that are still referenced by files that are kept</p> <p>This would have been useful in a recent cleanup of the HEPCloud Factory</p> PIP-II IT HWR - Task #23896 (New): Argonne Resonance Controller Troubleshooting & Modifications 2020-01-15T17:44:10Z Daniel Klepec klepec@fnal.gov MECAR - Feature #23894 (Resolved): MI Beam Intensity Compensation problems 2020-01-15T16:25:50Z Kevin Martin ksmartin@fnal.gov <p.</p> ArtDaq RunControl GUI - Bug #23886 (New): Infinite loop when Run button is pressed 2020-01-14T18:26:59Z Esteban Cristaldo <p>In some cases, the gui enters in a infinite loop when the Run buttons is pressed. e.g. when the gui is in the booted state and tries to configure with an invalid configuration, the gui will fall back to the booted state and will issue the configure signal again entering an infinite loop.<br />This is the only reported case of this bug but it can happen when DAQInterface falls back to a previous state, that is for example when the run signal is issued and DAQInterface falls back to the Ready state or booted state.</p> art - Bug #23881 (New): segv reading art files with overlapping event ranges 2020-01-14T16:07:39Z David Brown Dave_Brown@lbl.gov <p>Due to a procedural error, Mu2e inadvertently produced data files with overlapping event ranges. This problem was difficult to diagnose because the (profile build) art job reading these files failed with segmentation violation, instead of throwing an exception. In a debug build, the error manifests differently:</p> <p.<br />Aborted</p> <p>The problem can be reproduced running any art configuration on the file<br />/pnfs/mu2e/persistent/users/mu2epro/valjob/2020/01/11/reco/art/reco_00.art</p> artdaq Utilities - Feature #23880 (Resolved): SystemMetricCollector should report more detail CPU... 2020-01-14T14:27:02Z Eric Flumerfelt eflumerf@fnal.gov <p>Right now, SystemMetricCollector only reports the total CPU usage in the system. It may be desirable to also have the broken out components such as IOWait, User, System, IRQ.</p> ArtDaq RunControl GUI - Feature #23878 (Resolved): Select single options by default. 2020-01-13T18:07:54Z Iker de Icaza Astiz icaza@fnal.gov <p>If there's a single option for boot and config, select it by default.</p> PIP II IT SSR1 - Feature #23877 (New): LabVIEW creation for SSR1 2020-01-13T14:31:24Z Shrividhyaa Sankar Raman <p>A LabVIEW executable was created to support SSR1 properties and functions.<br />The executable can be found both attached here and on the Y drive at the following location:<br />Y:\Projects\LLRF\Applications\LabVIEW\PIP2IT_SSR1\SSR1 Builds\PIP2IT_SSR1_Build_1_6_2020\PIP2IT_SSR1</p> cetbuildtools - Feature #23864 (Assigned): Provide CMake namespace targets for FindUPSRoot 2020-01-10T14:11:39Z Kyle Knoepfel knoepfel@fnal.gov <p>Recent versions of ROOT include a <code>ROOTConfig-targets.cmake</code> file, which allows for the use of namespace-qualified targets (e.g. <code>ROOT::Core</code> instead of the CMake variable <code>${ROOT_CORE}</code>, which is provided by the FindUPSRoot CMake module). Could FindUPSRoot be enhanced to provide the namespace-qualified ROOT targets for downstream CMake code? I am happy to work on this.</p>