CLICdp issueshttps://gitlab.cern.ch/groups/CLICdp/-/issues2023-08-28T15:49:19+02:00https://gitlab.cern.ch/CLICdp/DAQs/h2m_lab/-/issues/6Use cli methods2023-08-28T15:49:19+02:00Simon SpannagelUse cli methodshttps://gitlab.cern.ch/CLICdp/DAQs/h2m_lab/-/blob/main/dac_scan/dac_ibias.txt#L8-21
is there a reason that not the ready-made `scanDAC` cli method is used? There is one hardcoded parameter `DAC_OUT` which could just become another param...https://gitlab.cern.ch/CLICdp/DAQs/h2m_lab/-/blob/main/dac_scan/dac_ibias.txt#L8-21
is there a reason that not the ready-made `scanDAC` cli method is used? There is one hardcoded parameter `DAC_OUT` which could just become another parameter of the method. Alternatively, add a single line to the periphery mappings and name the ADC input by the same name.https://gitlab.cern.ch/CLICdp/HGCAL/HGCAL_sensor_web/-/issues/6Access is denied for some pages2021-02-01T12:31:04+01:00Erica BrondolinAccess is denied for some pagesCurrently it is not possible to access to some png and pdf on some of the pages website in the [Sensor List](https://hexweb.web.cern.ch/HexWeb/sensorslist/).
One example of accessible page is [hpk_8in_198ch_2019_2006](https://hexweb.we...Currently it is not possible to access to some png and pdf on some of the pages website in the [Sensor List](https://hexweb.web.cern.ch/HexWeb/sensorslist/).
One example of accessible page is [hpk_8in_198ch_2019_2006](https://hexweb.web.cern.ch/HexWeb/sensorslist/hpk_8in_198ch_2019_2006/), while one that is not accessible is [hpk_8in_198ch_2019_2106](https://hexweb.web.cern.ch/HexWeb/sensorslist/hpk_8in_198ch_2019_2106/).
Debugging steps already performed:
- since there's only one `.htaccess` file in the root of the site, the two paths should have the same access rules.
- the correspondent folders in `/eos/user/h/hgsensor/HGCAL_test_results/Results` have the same access rights:
```
drwx------. 2 99078 1399 4096 Oct 7 12:06 HPK_8in_198ch_2019_2006
drwx------. 2 99078 1399 4096 Oct 30 16:07 HPK_8in_198ch_2019_2106
```
- the same accessibility problem happen also to other users, not only my personal account (ebrondol)https://gitlab.cern.ch/CLICdp/HGCAL/rpi-daq/-/issues/2Improve data file i/o2020-08-10T13:09:02+02:00Thorben QuastImprove data file i/oImprove the handling (I/O) in case a data file already exists.Improve the handling (I/O) in case a data file already exists.https://gitlab.cern.ch/CLICdp/HGCAL/rpi-daq/-/issues/1Total current and bias voltage reading2020-08-10T13:08:24+02:00Thorben QuastTotal current and bias voltage readingRead the total current and bias voltage from the power supply during the measurement and write it to file.Read the total current and bias voltage from the power supply during the measurement and write it to file.https://gitlab.cern.ch/CLICdp/HGCAL/HGCAL_sensor_analysis/-/issues/58Segmentation violation when using --useLogVal2019-02-27T10:18:25+01:00Eva SickingSegmentation violation when using --useLogValIn case negative values are inside the cell current list (which normally should not happen), the plotting with --useLogVal crashes with a segmentation violation.
An example with the latest develop branch that crashes is this one:
./bin/...In case negative values are inside the cell current list (which normally should not happen), the plotting with --useLogVal crashes with a segmentation violation.
An example with the latest develop branch that crashes is this one:
./bin/HexPlot --colorpalette 57 -g ./geo/hex_positions_HPK_256ch_8inch.txt -o CERN_3007_IV.pdf -i HGCAL_test_results/Results/HPK_8in_271ch_3007/HPK_8in_271ch_3007_IV.txt --select -600 -z -0.01:10000 --invertVal --useLogVal
At -600V, the cell list has at least one positive value, which is converted to negative values when using --invertVal.https://gitlab.cern.ch/CLICdp/HGCAL/HGCAL_sensor_web/-/issues/4List disapprearing in the header2018-08-15T16:25:23+02:00Erica BrondolinList disapprearing in the headerIn this moment all "children" appear in the header when you click on the folder (for example "Sensor analysis").
It would be nice to have the entire list of folders in a category appearing **only** when the sub-folder is select.In this moment all "children" appear in the header when you click on the folder (for example "Sensor analysis").
It would be nice to have the entire list of folders in a category appearing **only** when the sub-folder is select.https://gitlab.cern.ch/CLICdp/HGCAL/HGCAL_sensor_web/-/issues/3RSS Feed2018-08-15T16:33:18+02:00Erica BrondolinRSS FeedThe ELOG uses RSS Feeds.
It would be nice to integrate them in the website in form of posts.The ELOG uses RSS Feeds.
It would be nice to integrate them in the website in form of posts.https://gitlab.cern.ch/CLICdp/HGCAL/HGCAL_sensor_analysis/-/issues/56Repair functionality "findvalue"2018-08-09T14:09:25+02:00Manfred ValentanRepair functionality "findvalue"The findvalue functionality could use some overhaul. I tried to use it to plot the voltage at which the sensor cells reach a certain current. I ran into several problems:
1) The finding algorithm operates on 1/value², and not on the z v...The findvalue functionality could use some overhaul. I tried to use it to plot the voltage at which the sensor cells reach a certain current. I ran into several problems:
1) The finding algorithm operates on 1/value², and not on the z values themselves. So it propably was intended to work on CV data. Not a big problem, one can use the flag --notrafo to work on the z values themselves. However, this behaviour should be documented.
2) When I use a threshold which is larger than all z values, the algorithm returns NaN. Not sure if this makes sense. For IV curves, I'd rather put the maximum voltage there, because it would mean that the cell is stable at least up to that voltage.
3) The algorithm uses a spline for interpolation. This spline is very sensitive to outliers. In my test data I have several IV curves, where the very first point is ridiculously large. Is there a possibility to have the spline ignore points which would lead to a high local curvature?
4) The algorithm doesn't adhere to limits of the fit range, unlike the other fit functions. Such a functionality would be a viable workaround for point 3).https://gitlab.cern.ch/CLICdp/HGCAL/HGCAL_sensor_analysis/-/issues/54Use docker container for deployment on Windows2018-06-28T12:49:00+02:00Andreas Alexander MaierUse docker container for deployment on Windowshttps://gitlab.cern.ch/CLICdp/HGCAL/HGCAL_sensor_analysis/-/issues/52Ctest does not accept multiple regex2018-06-08T12:36:16+02:00Erica BrondolinCtest does not accept multiple regexCtest result complete successfully when AT LEAST one of the regular expressions are matched. It should be matched with ALL OF THEM.
Adapt `CMakeLists.txt` to check for each line in the HexPlot output. Maybe by introducing a separate te...Ctest result complete successfully when AT LEAST one of the regular expressions are matched. It should be matched with ALL OF THEM.
Adapt `CMakeLists.txt` to check for each line in the HexPlot output. Maybe by introducing a separate test for each line.https://gitlab.cern.ch/CLICdp/HGCAL/HGCAL_sensor_analysis/-/issues/49Set default geometry file directory to avoid absolute paths2018-02-06T16:59:57+01:00Andreas Alexander MaierSet default geometry file directory to avoid absolute pathsSet default geometry file directory to avoid absolute paths when executing HexPlot in arbitrary directories.Set default geometry file directory to avoid absolute paths when executing HexPlot in arbitrary directories.https://gitlab.cern.ch/CLICdp/HGCAL/HGCAL_sensor_analysis/-/issues/46x-axis of --detailed overlay plot doesn't show full range2018-05-23T07:50:44+02:00Manfred Valentanx-axis of --detailed overlay plot doesn't show full rangeIt seems like the range of the x-axis is derived from the data range of the first IV curve (or whatever) HexPlot reads. If other curves have a larger range, they are cropped in the overlay plot, which is created by the --detailed option....It seems like the range of the x-axis is derived from the data range of the first IV curve (or whatever) HexPlot reads. If other curves have a larger range, they are cropped in the overlay plot, which is created by the --detailed option.
Is there a way to plot the full range of all curves?
Alternatively: Is there a way to manually set the x range, similar to the -z option?https://gitlab.cern.ch/CLICdp/HGCAL/HGCAL_sensor_web/-/issues/2Make sure standard plots available for every sensor2018-07-26T16:04:05+02:00Andreas Alexander MaierMake sure standard plots available for every sensorUse png for quicker display.Use png for quicker display.Andreas Alexander MaierErica BrondolinAndreas Alexander Maierhttps://gitlab.cern.ch/CLICdp/HGCAL/HGCAL_sensor_analysis/-/issues/40Use std library functions wherever possible2017-09-20T14:27:49+02:00Andreas Alexander MaierUse std library functions wherever possibleAndreas Alexander MaierAndreas Alexander Maierhttps://gitlab.cern.ch/CLICdp/HGCAL/HGCAL_sensor_analysis/-/issues/19Rotation of entire figure2017-10-25T14:25:04+02:00Andreas Alexander MaierRotation of entire figureAdd a flag to rotate the entire HexPlot.
Hints: the new flag has to be defined in hex_plotter.cxx (e.g. --rotate 45) and passed over to the gep_plot class. Then it has to turn the x/y coordinates of every pad around the center 0/0. Che...Add a flag to rotate the entire HexPlot.
Hints: the new flag has to be defined in hex_plotter.cxx (e.g. --rotate 45) and passed over to the gep_plot class. Then it has to turn the x/y coordinates of every pad around the center 0/0. Check root_utils.cxx for the rotate_polygon function, which has a rotation implemented. Note however, that simply changing the position won't be enough, the pads have to be rotated themselves as well. So a rotation has to be appended to each transformation string.Manfred ValentanManfred Valentanhttps://gitlab.cern.ch/CLICdp/HGCAL/HGCAL_sensor_analysis/-/issues/17Pad area file for relative cell capacitances2018-06-28T12:59:54+02:00Andreas Alexander MaierPad area file for relative cell capacitancesThe processing of area info is already implemented in geo_plot::get_pad_surface. This could be read from an external optional file. The plot option "-p FLAT" (the former "CHAN") does the area normalization automatically. Check e.g. examp...The processing of area info is already implemented in geo_plot::get_pad_surface. This could be read from an external optional file. The plot option "-p FLAT" (the former "CHAN") does the area normalization automatically. Check e.g. example 8 and the file ../examples/example_relcat.pdf it gives out.
Edit: it should be integrated as optional lines int the geometry filehttps://gitlab.cern.ch/CLICdp/HGCAL/HGCAL_sensor_analysis/-/issues/14Add wildcard option for input files2017-09-20T14:37:56+02:00Andreas Alexander MaierAdd wildcard option for input filesWould simplify the concatenation of several input filesWould simplify the concatenation of several input fileshttps://gitlab.cern.ch/CLICdp/HGCAL/HGCAL_sensor_analysis/-/issues/13Make inter-cell values work for averages2017-09-20T14:37:41+02:00Andreas Alexander MaierMake inter-cell values work for averageshttps://gitlab.cern.ch/CLICdp/HGCAL/HGCAL_sensor_analysis/-/issues/3Extreme zoom values do not work as expected2017-09-20T14:28:42+02:00Andreas Alexander MaierExtreme zoom values do not work as expectedThe upper limit of the zoom parameter is not accepted as it is, but incremented by about 0.5 by Root:
./HexPlot -i ../examples/test_data.txt -g ../geo/hex_positions_HPK_128ch_6inch.txt -o ../examples/example.pdf -IV -p HEX -pn 1 -select...The upper limit of the zoom parameter is not accepted as it is, but incremented by about 0.5 by Root:
./HexPlot -i ../examples/test_data.txt -g ../geo/hex_positions_HPK_128ch_6inch.txt -o ../examples/example.pdf -IV -p HEX -pn 1 -select 10 -ys 1e-1 -ap 0 -z 52:53
The plot has a z-axis from 52 to 53.5