cmsgemos merge requestshttps://gitlab.cern.ch/cmsgemonline/gem-daq/cmsgemos/-/merge_requests2024-03-06T18:42:31+01:00https://gitlab.cern.ch/cmsgemonline/gem-daq/cmsgemos/-/merge_requests/334Draft: Add an MGT eye scan diagram feature2024-03-06T18:42:31+01:00Laurent PetreDraft: Add an MGT eye scan diagram feature## Description
Heavily work in progress...
## Related Issue
## How Has This Been Tested?
## Types of changes
- [ ] Bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
-...## Description
Heavily work in progress...
## Related Issue
## How Has This Been Tested?
## Types of changes
- [ ] Bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
## Checklist:
- [ ] My code follows the code style of this project.
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [ ] I have read the **CONTRIBUTING** document.
- [ ] I have added tests to cover my changes.
- [ ] All new and existing tests passed.Laurent PetreLaurent Petrehttps://gitlab.cern.ch/cmsgemonline/gem-daq/cmsgemos/-/merge_requests/329Draft: Port an initial subset of views to Vue.js2024-01-17T12:30:38+01:00Laurent PetreDraft: Port an initial subset of views to Vue.js## Description
\[Based on top of !328.\]
This merge request is a revival of !251 (see MR for rationales).
Todo:
* [ ] Convert tables from Bootstrap to another, Vue.js compatible, UI framework (mainly for the popovers)
* [ ] Port all ...## Description
\[Based on top of !328.\]
This merge request is a revival of !251 (see MR for rationales).
Todo:
* [ ] Convert tables from Bootstrap to another, Vue.js compatible, UI framework (mainly for the popovers)
* [ ] Port all `fedMonitor.js` updates into the Vue.js app/component
* [ ] Avoid stalled values
* [ ] Implement dynamic layout
* [ ] Convert the `FEDMonitor` application to use the Vue.js components
* [ ] Optionally convert as many "views" as possible to Vue.js
## Related Issue
Relates to the initial experimentations on #128.
## How Has This Been Tested?
## Types of changes
* [ ] Bug fix (non-breaking change which fixes an issue)
* [ ] New feature (non-breaking change which adds functionality)
* [ ] Breaking change (fix or feature that would cause existing functionality to change)
## Checklist:
* [ ] My code follows the code style of this project.
* [ ] My change requires a change to the documentation.
* [ ] I have updated the documentation accordingly.
* [ ] I have read the **CONTRIBUTING** document.
* [ ] I have added tests to cover my changes.
* [ ] All new and existing tests passed.Laurent PetreLaurent Petrehttps://gitlab.cern.ch/cmsgemonline/gem-daq/cmsgemos/-/merge_requests/319Draft: AMC13Manager cleanup and refactoring2023-10-31T16:26:51+01:00Laurent PetreDraft: AMC13Manager cleanup and refactoring## Description
<!-- Describe your changes in detail -->
This is a real draft of a draft of a draft...
## Related Issue
<!-- This project only accepts pull requests related to open issues -->
<!-- If suggesting a new feature or change, ...## Description
<!-- Describe your changes in detail -->
This is a real draft of a draft of a draft...
## Related Issue
<!-- This project only accepts pull requests related to open issues -->
<!-- If suggesting a new feature or change, please discuss it in an issue first -->
<!-- If fixing a bug, there should be an issue describing it with steps to reproduce -->
<!-- If addressing multiple issues, comment on their relation if needed -->
<!-- Please link issues accordgin to the automation rules: -->
<!-- https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically -->
Should address #207, #91, and (part of) #154.
## How Has This Been Tested?
<!-- Please describe in detail how you tested your changes. -->
<!-- Include details of your testing environment, and the tests you ran to -->
<!-- see how your change affects other areas of the code, etc. -->
<!-- ## Screenshots (if appropriate): -->
## Types of changes
<!-- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
## Checklist:
<!-- Go over all the following points, and put an `x` in all the boxes that apply. -->
<!-- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
- [ ] My code follows the code style of this project.
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [ ] I have read the **CONTRIBUTING** document.
- [ ] I have added tests to cover my changes.
- [ ] All new and existing tests passed.https://gitlab.cern.ch/cmsgemonline/gem-daq/cmsgemos/-/merge_requests/317Draft: Add an S-bit phase scan routine2023-10-31T15:48:21+01:00Laurent PetreDraft: Add an S-bit phase scan routine## Description
<!-- Describe your changes in detail -->
This is even more than a draft... Although first text results are encouraging. :smiley:
## Related Issue
<!-- This project only accepts pull requests related to open issues -->
<...## Description
<!-- Describe your changes in detail -->
This is even more than a draft... Although first text results are encouraging. :smiley:
## Related Issue
<!-- This project only accepts pull requests related to open issues -->
<!-- If suggesting a new feature or change, please discuss it in an issue first -->
<!-- If fixing a bug, there should be an issue describing it with steps to reproduce -->
<!-- If addressing multiple issues, comment on their relation if needed -->
<!-- Please link issues accordgin to the automation rules: -->
<!-- https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically -->
Fixes #259.
## How Has This Been Tested?
<!-- Please describe in detail how you tested your changes. -->
<!-- Include details of your testing environment, and the tests you ran to -->
<!-- see how your change affects other areas of the code, etc. -->
<!-- ## Screenshots (if appropriate): -->
## Types of changes
<!-- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
## Checklist:
<!-- Go over all the following points, and put an `x` in all the boxes that apply. -->
<!-- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
- [ ] My code follows the code style of this project.
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [ ] I have read the **CONTRIBUTING** document.
- [ ] I have added tests to cover my changes.
- [ ] All new and existing tests passed.Laurent PetreLaurent Petrehttps://gitlab.cern.ch/cmsgemonline/gem-daq/cmsgemos/-/merge_requests/309Draft: Front-end links initialization enhancements2024-03-21T17:57:36+01:00Laurent PetreDraft: Front-end links initialization enhancements## Description
<!-- Describe your changes in detail -->
[Based on top of !310.]
**WIP**
## Related Issue
<!-- This project only accepts pull requests related to open issues -->
<!-- If suggesting a new feature or change, please discus...## Description
<!-- Describe your changes in detail -->
[Based on top of !310.]
**WIP**
## Related Issue
<!-- This project only accepts pull requests related to open issues -->
<!-- If suggesting a new feature or change, please discuss it in an issue first -->
<!-- If fixing a bug, there should be an issue describing it with steps to reproduce -->
<!-- If addressing multiple issues, comment on their relation if needed -->
<!-- Please link issues accordgin to the automation rules: -->
<!-- https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically -->
## How Has This Been Tested?
<!-- Please describe in detail how you tested your changes. -->
<!-- Include details of your testing environment, and the tests you ran to -->
<!-- see how your change affects other areas of the code, etc. -->
Deployed in production at P5.
## Types of changes
<!-- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
## Checklist:
<!-- Go over all the following points, and put an `x` in all the boxes that apply. -->
<!-- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
- [ ] My code follows the code style of this project.
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [ ] I have read the **CONTRIBUTING** document.
- [ ] I have added tests to cover my changes.
- [ ] All new and existing tests passed.Laurent PetreLaurent Petrehttps://gitlab.cern.ch/cmsgemonline/gem-daq/cmsgemos/-/merge_requests/286Draft: Create RPM packages containing the backend artifacts2022-09-08T13:37:08+02:00Laurent PetreDraft: Create RPM packages containing the backend artifacts## Description
<!-- Describe your changes in detail -->
**WIP**
## Related Issue
<!-- This project only accepts pull requests related to open issues -->
<!-- If suggesting a new feature or change, please discuss it in an issue first --...## Description
<!-- Describe your changes in detail -->
**WIP**
## Related Issue
<!-- This project only accepts pull requests related to open issues -->
<!-- If suggesting a new feature or change, please discuss it in an issue first -->
<!-- If fixing a bug, there should be an issue describing it with steps to reproduce -->
<!-- If addressing multiple issues, comment on their relation if needed -->
<!-- Please link issues accordgin to the automation rules: -->
<!-- https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically -->
## How Has This Been Tested?
<!-- Please describe in detail how you tested your changes. -->
<!-- Include details of your testing environment, and the tests you ran to -->
<!-- see how your change affects other areas of the code, etc. -->
<!-- ## Screenshots (if appropriate): -->
## Types of changes
<!-- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
## Checklist:
<!-- Go over all the following points, and put an `x` in all the boxes that apply. -->
<!-- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
- [ ] My code follows the code style of this project.
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [ ] I have read the **CONTRIBUTING** document.
- [ ] I have added tests to cover my changes.
- [ ] All new and existing tests passed.https://gitlab.cern.ch/cmsgemonline/gem-daq/cmsgemos/-/merge_requests/260Draft: Fix the GEM loader issue2022-04-29T19:28:22+02:00Laurent PetreDraft: Fix the GEM loader issue## Description
<!-- Describe your changes in detail -->
WIP
Made as a companion to https://gitlab.cern.ch/emu/0xbefe/-/merge_requests/111
## Related Issue
<!-- This project only accepts pull requests related to open issues -->
<!-- If...## Description
<!-- Describe your changes in detail -->
WIP
Made as a companion to https://gitlab.cern.ch/emu/0xbefe/-/merge_requests/111
## Related Issue
<!-- This project only accepts pull requests related to open issues -->
<!-- If suggesting a new feature or change, please discuss it in an issue first -->
<!-- If fixing a bug, there should be an issue describing it with steps to reproduce -->
<!-- If addressing multiple issues, comment on their relation if needed -->
<!-- Please link issues accordgin to the automation rules: -->
<!-- https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically -->
## How Has This Been Tested?
<!-- Please describe in detail how you tested your changes. -->
<!-- Include details of your testing environment, and the tests you ran to -->
<!-- see how your change affects other areas of the code, etc. -->
<!-- ## Screenshots (if appropriate): -->
## Types of changes
<!-- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
## Checklist:
<!-- Go over all the following points, and put an `x` in all the boxes that apply. -->
<!-- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
- [ ] My code follows the code style of this project.
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [ ] I have read the **CONTRIBUTING** document.
- [ ] I have added tests to cover my changes.
- [ ] All new and existing tests passed.https://gitlab.cern.ch/cmsgemonline/gem-daq/cmsgemos/-/merge_requests/241Generalize GBT phases using GBT and elink numbers2022-06-09T18:46:28+02:00Antonello PellecchiaGeneralize GBT phases using GBT and elink numbers## Description
Generalizes the `writeGBTPhase` function to use GBT and elink as parameters instead of VFAT number. The GBT phase scan function is adjusted accordingly and the output format of the GBT phase scan contains now the gbt and e...## Description
Generalizes the `writeGBTPhase` function to use GBT and elink as parameters instead of VFAT number. The GBT phase scan function is adjusted accordingly and the output format of the GBT phase scan contains now the gbt and elink columns instead of the vfat column.
To be implemented:
- [x] Improve log message when invalid phase is set
- [x] Move default phase map from gemhardware to gemcore
- [x] Update cmsgemos-analysis to analyze GBT phase scan result with new format (see [MR 24](https://gitlab.cern.ch/cmsgemonline/gem-daq/cmsgemos-analysis/-/merge_requests/24) in the analysis repository)
- [x] Use updated configuration file format in cmsgemos
## Related Issue
<!-- This project only accepts pull requests related to open issues -->
<!-- If suggesting a new feature or change, please discuss it in an issue first -->
<!-- If fixing a bug, there should be an issue describing it with steps to reproduce -->
<!-- If addressing multiple issues, comment on their relation if needed -->
<!-- Please link issues accordgin to the automation rules: -->
<!-- https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically -->
## How Has This Been Tested?
Tested on GE2/1 integration stand in B904.
<!-- Please describe in detail how you tested your changes. -->
<!-- Include details of your testing environment, and the tests you ran to -->
<!-- see how your change affects other areas of the code, etc. -->
<!-- ## Screenshots (if appropriate): -->
## Types of changes
<!-- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [x] Breaking change (fix or feature that would cause existing functionality to change)
## Checklist:
<!-- Go over all the following points, and put an `x` in all the boxes that apply. -->
<!-- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
- [ ] My code follows the code style of this project.
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [ ] I have read the **CONTRIBUTING** document.
- [ ] I have added tests to cover my changes.
- [ ] All new and existing tests passed.Antonello PellecchiaAntonello Pellecchiahttps://gitlab.cern.ch/cmsgemonline/gem-daq/cmsgemos/-/merge_requests/221Implement the SCA GBT phase scan2022-01-26T16:09:05+01:00Pieter EveraertsImplement the SCA GBT phase scan## Description
This MR adds a phase scan for the SCA e-link. For each phase from 0 to 15 the SCA is reset a number of times (default 100) and the ready state is checked.
It is a bit ugly that we have to read the config-file to apply t...## Description
This MR adds a phase scan for the SCA e-link. For each phase from 0 to 15 the SCA is reset a number of times (default 100) and the ready state is checked.
It is a bit ugly that we have to read the config-file to apply the phases, but otherwise we overwrite other values and the scan misbehaves. This can be modified once we have the possibility to read back GBT registers.
The raw results are saved in `/tmp/gemdata/scaPhaseScan/`. The phases and the corresponding number of failures are printed.
## Related Issue
This MR addresses issue #193. We could consider merging the solution with #192 and make it a single scan.
## How Has This Been Tested?
Tested on the GE2/1 integration setup in B904.
## Types of changes
<!-- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [X] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
## Checklist:
<!-- Go over all the following points, and put an `x` in all the boxes that apply. -->
<!-- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
- [X] My code follows the code style of this project.
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [X] I have read the **CONTRIBUTING** document.
- [ ] I have added tests to cover my changes.
- [ ] All new and existing tests passed.Pieter EveraertsAntonello PellecchiaPieter Everaertshttps://gitlab.cern.ch/cmsgemonline/gem-daq/cmsgemos/-/merge_requests/220Add OH FPGA slow-control phase scan2022-01-26T16:35:42+01:00Antonello PellecchiaAdd OH FPGA slow-control phase scan## Description
This MR adds a phase scan for the FPGA slow control e-link. For each phase from 0 to 15 the scan sends many times (by default 50 times) a signal through the e-link by writing the register `BEFE.GEM.OH.OH*.FPGA.CONTROL.LOOP...## Description
This MR adds a phase scan for the FPGA slow control e-link. For each phase from 0 to 15 the scan sends many times (by default 50 times) a signal through the e-link by writing the register `BEFE.GEM.OH.OH*.FPGA.CONTROL.LOOPBACK.DATA` and reads the loopback value from the same register. If the read value is different from the written one, the phase is marked as bad.
The raw and analysed results are saved in `/tmp/gemdata/fpgaSlowControlPhaseScan/`. The analysed result contains the optimal phase determined in the window of good phases.
## Related Issue
This MR addresses issue #192.
<!-- This project only accepts pull requests related to open issues -->
<!-- If suggesting a new feature or change, please discuss it in an issue first -->
<!-- If fixing a bug, there should be an issue describing it with steps to reproduce -->
<!-- If addressing multiple issues, comment on their relation if needed -->
<!-- Please link issues accordgin to the automation rules: -->
<!-- https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically -->
## How Has This Been Tested?
Tested on the GE2/1 integration setup in B904.
<!-- Please describe in detail how you tested your changes. -->
<!-- Include details of your testing environment, and the tests you ran to -->
<!-- see how your change affects other areas of the code, etc. -->
<!-- ## Screenshots (if appropriate): -->
## Types of changes
<!-- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
## Checklist:
<!-- Go over all the following points, and put an `x` in all the boxes that apply. -->
<!-- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
- [x] My code follows the code style of this project.
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [x] I have read the **CONTRIBUTING** document.
- [ ] I have added tests to cover my changes.
- [ ] All new and existing tests passed.Pieter EveraertsAntonello PellecchiaPieter Everaertshttps://gitlab.cern.ch/cmsgemonline/gem-daq/cmsgemos/-/merge_requests/193Draft:Scripts for sbit mapping test2021-10-07T12:06:15+02:00Yechan KangDraft:Scripts for sbit mapping test## Description
This merge request will add the scripts for sbit mapping test.
There are 2 scripts. And following lines for description for each script.
The `cluster_scan.py` is the script that should be running inside of CTP7.
```sh
pyt...## Description
This merge request will add the scripts for sbit mapping test.
There are 2 scripts. And following lines for description for each script.
The `cluster_scan.py` is the script that should be running inside of CTP7.
```sh
python cluster_scan.py --nOH NUMBER_OF_OH_TO_SCAN \
--nEvent NUMBER_OF_EVENT_FOR_DATA_TAKING \
--threshold THRESHOLD_VALUE_TO_USE_DURING_DATA_TAKING
```
The `run_cluster_scan.py` is the wrapper for the previous script.
```sh
python run_cluster_scan.py --nOH NUMBER_OF_OH_TO_SCAN \
--nEvent NUMBER_OF_EVENT_FOR_DATA_TAKING \
--threshold THRESHOLD_VALUE_TO_USE_DURING_DATA_TAKING \
--CTP7 CTP7_HOST_NAME \
--data_path OUTPUT_FILE_DIRECTORY \
```
The default `CTP7_HOST_NAME` is `gempro@gem-shelf01-amc02`.
## Related Issue
<!-- This project only accepts pull requests related to open issues -->
<!-- If suggesting a new feature or change, please discuss it in an issue first -->
<!-- If fixing a bug, there should be an issue describing it with steps to reproduce -->
<!-- If addressing multiple issues, comment on their relation if needed -->
<!-- Please link issues accordgin to the automation rules: -->
<!-- https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically -->
## How Has This Been Tested?
<!-- Please describe in detail how you tested your changes. -->
<!-- Include details of your testing environment, and the tests you ran to -->
<!-- see how your change affects other areas of the code, etc. -->
<!-- ## Screenshots (if appropriate): -->
## Types of changes
<!-- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
## Checklist:
<!-- Go over all the following points, and put an `x` in all the boxes that apply. -->
<!-- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
- [ ] My code follows the code style of this project.
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [ ] I have read the **CONTRIBUTING** document.
- [ ] I have added tests to cover my changes.
- [ ] All new and existing tests passed.Yechan KangJohny JaramilloCaterina ArutaYechan Kanghttps://gitlab.cern.ch/cmsgemonline/gem-daq/cmsgemos/-/merge_requests/167Documenting the steps to configure a CTP7 to run the DAQ code2024-03-26T16:35:08+01:00Antonello PellecchiaDocumenting the steps to configure a CTP7 to run the DAQ code## Description
A documentation file describing the steps to configure the CTP7 by creating a user to run the DAQ code, creating the required folder structure and copying the necessary libraries, executables and configuration files from:
...## Description
A documentation file describing the steps to configure the CTP7 by creating a user to run the DAQ code, creating the required folder structure and copying the necessary libraries, executables and configuration files from:
- the DAQ repository;
- the firmware repository;
- an external archive.
## Related Issue
<!--- This project only accepts pull requests related to open issues -->
<!--- If suggesting a new feature or change, please discuss it in an issue first -->
<!--- If fixing a bug, there should be an issue describing it with steps to reproduce -->
<!--- If addressing multiple issues, comment on their relation if needed -->
<!--- Please link issues accordgin to the automation rules: -->
<!--- https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically -->
## How Has This Been Tested?
Steps described here were performed on board `gem-shelf02-amc07`; the setup is yet to be tested.
<!--- ## Screenshots (if appropriate): -->
## Types of changes
<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
## Checklist:
<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
- [ ] My code follows the code style of this project.
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [x] I have read the **CONTRIBUTING** document.
- [ ] I have added tests to cover my changes.
- [x] All new and existing tests passed.Antonello PellecchiaAntonello Pellecchiahttps://gitlab.cern.ch/cmsgemonline/gem-daq/cmsgemos/-/merge_requests/101WIP: Document the cmsgemos packages2021-08-18T18:09:40+02:00Laurent PetreWIP: Document the cmsgemos packages## Description
<!--- Describe your changes in detail -->
This MR aims at writing a first documentation of the various `cmsgemos` packages in order for the developers to better understand the software architecture.
This is far from bein...## Description
<!--- Describe your changes in detail -->
This MR aims at writing a first documentation of the various `cmsgemos` packages in order for the developers to better understand the software architecture.
This is far from being a finalized documentation but is the first step of a WIP MR. Feel free to already comment on it or add new ideas.
## Related Issue
<!--- This project only accepts pull requests related to open issues -->
<!--- If suggesting a new feature or change, please discuss it in an issue first -->
<!--- If fixing a bug, there should be an issue describing it with steps to reproduce -->
<!--- If addressing multiple issues, comment on their relation if needed -->
<!--- Please link issues accordgin to the automation rules: -->
<!--- https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically -->
Closes #145
## Types of changes
<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
- [x] Bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
## Checklist:
<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
- [x] My code follows the code style of this project.
- [x] My change requires a change to the documentation.
- [x] I have updated the documentation accordingly.
- [x] I have read the **CONTRIBUTING** document.
- [ ] I have added tests to cover my changes.
- [ ] All new and existing tests passed.Laurent PetreLaurent Petre