Commit ff0d5535 authored by Michal Maciejewski's avatar Michal Maciejewski
Browse files

Updated README.md

parent 24a291a0
......@@ -57,10 +57,22 @@
analysis_start_time = datetime.now().strftime("%Y.%m.%d_%H%M%S.%f")
```
%%%% Output: error
---------------------------------------------------------------------------
ModuleNotFoundError Traceback (most recent call last)
<ipython-input-1-5a477aa5a2c0> in <module>()
18 from lhcsmapi.gui.qh.DateTimeBaseModule import DateTimeBaseModule
19 from lhcsmapi.gui.pc.FgcPmSearchModuleMediator import FgcPmSearchModuleMediator
---> 20 from lhcsmapi.gui.pc._600AFgcPmSearchBaseModule import _600AFgcPmSearchBaseModule
21
22
ModuleNotFoundError: No module named 'lhcsmapi.gui.pc._600AFgcPmSearchBaseModule'
%% Cell type:markdown id: tags:
## 0.2. LHCSMAPI Version
%% Cell type:code id: tags:
......
......@@ -3,22 +3,22 @@
# Notebooks for Circuit Analysis of HWC Tests and Events during Operation
Although, as the project name indicates, our primary goal is the development of signal monitoring applications, we realized that the analysis modules developed so far can be pieced together into HWC test and operation analysis notebooks.
Even though, we develop the analyses system by system, they were developed in a general way to account for all circuits in which the system was present. Thus, by taking a perpendicular view of the analysis table, a circuit analysis for this stance was possible.
<img src="https://gitlab.cern.ch/LHCData/lhc-sm-hwc/raw/master/figures/monitoring-vs-hwc.png" width=50%>
<center><img src="https://gitlab.cern.ch/LHCData/lhc-sm-hwc/raw/master/figures/monitoring-vs-hwc.png" width=50%></center>
In particular, thotebooks are suited for HWC tests:
- can be adjusted on-the-fly for new requirements while performing a test;
- can immediately generate a report for storage and distribution among a team of domain experts;
- provide a sequential way of testing each system in a given order.
%% Cell type:markdown id: tags:
# Supported Circuits
## 1. RB - Main Dipole Circuit
<img src = "https://gitlab.cern.ch/LHCData/lhc-sm-hwc/raw/master/figures/rb/RB.png" width=75%>
<center><img src = "https://gitlab.cern.ch/LHCData/lhc-sm-hwc/raw/master/figures/rb/RB.png" width=75%></center>
<p>source: Powering Procedure and Acceptance Criteria for the 13 kA Dipole Circuits, MP3 Procedure, <a href="https://edms.cern.ch/document/874713/5.1">https://edms.cern.ch/document/874713/5.1</a></p>
|Type|Test|Current|Description|Notebook|Example report|
|----|----|-------|-----------|--------|--------------|
......@@ -35,11 +35,11 @@
|HWC|PNO.b2|I\_PNO+I\_DELTA|Energy Extraction from QPS|[AN\_RB\_PNO.b2](https://gitlab.cern.ch/LHCData/lhc-sm-hwc/-/blob/master/rb/AN_RB_PNO.b2.ipynb)|[AN\_RB\_PNO.b2](https://sigmon.web.cern.ch/node/58)|
|HWC|PNO.a6|I\_PNO|Energy Extraction from QPS|[AN\_RB\_PNO.a6](https://gitlab.cern.ch/LHCData/lhc-sm-hwc/-/blob/master/rb/AN_RB_PNO.a6.ipynb)|[AN\_RB\_PNO.a6](https://sigmon.web.cern.ch/node/57)|
|Operation|FPA|I\_PNO|FPA during operation with magnets quenching|[AN\_RB\_FPA](https://gitlab.cern.ch/LHCData/lhc-sm-hwc/-/blob/master/rb/AN_RB_FPA.ipynb)|[AN\_RB\_FPA](https://sigmon.web.cern.ch/node/59)|
## 2. RQ - Main Quadrupole Circuit
<img src="https://gitlab.cern.ch/LHCData/lhc-sm-hwc/raw/master/figures/rq/RQ.png" width=75%>
<center><img src="https://gitlab.cern.ch/LHCData/lhc-sm-hwc/raw/master/figures/rq/RQ.png" width=75%></center>
<p>source: Test Procedure and Acceptance Criteria for the 13 kA Quadrupole (RQD-RQF) Circuits, MP3 Procedure, <a href="https://edms.cern.ch/document/874714/5.1">https://edms.cern.ch/document/874714/5.1</a></p>
|Type|Test|Current|Description|Notebook|Example report|
|----|----|-------|-----------|--------|--------------|
......@@ -61,11 +61,11 @@
- circuits with
- and without EE.
Each variant may or may not be equipped with a DC contactor ensuring the effectiveness of the crowbar in case of a PC short circuit. Moreover, the magnets of several circuits are equipped with parallel resistors, in order to decouple the current decay in a quenching magnet from that in the rest of the circuit. Figure 1 shows a generic circuit diagram, equipped with EE and parallel resistor, as well as lead resistances and a quench resistance.
<img src="https://gitlab.cern.ch/LHCData/lhc-sm-hwc/-/raw/master/figures/600A/600A.png" width=75%>
<center><img src="https://gitlab.cern.ch/LHCData/lhc-sm-hwc/-/raw/master/figures/600A/600A.png" width=75%></center>
source: Test Procedure and Acceptance Criteria for the 600 A Circuits, MP3 Procedure, <a href="https://edms.cern.ch/document/874716/5.3">https://edms.cern.ch/document/874716/5.3</a>
Table below provides a list of circuits to be used with these analysis notebooks
......@@ -120,21 +120,21 @@
The following steps should be followed in order to log-in to SWAN
1. Go to http://swan.cern.ch
2. Login with your NICE account
- SWAN is tightly integrated with CERNBox service (in fact, files created in SWAN are accessible in CERNBox). In case you have not used CERNBox, the following error message will be displayed in- dicating that your CERNBox account has not been activated yet. In order to activate your CERNBox account, please login on the website: http://cernbox.cern.ch. Afterwards, please login to SWAN service again. In case the error persists, please contact the SWAN support (see Section Help and Feedback at the bottom).
<img src="https://gitlab.cern.ch/LHCData/lhc-sm-hwc/raw/master/figures/swan-inactive-cernbox-error.png" width=50%>
<cetner><img src="https://gitlab.cern.ch/LHCData/lhc-sm-hwc/raw/master/figures/swan-inactive-cernbox-error.png" width=50%></center>
## 3. Setting an Environment Script
In order to execute the HWC notebooks, one requires `lhc-sm-api` package and HWC notebooks. To this end, we created a dedicated environment script to prepare the SWAN project space.
The script sets a path to a virtual environment with the necessary packages (for more details, cf. https://lhc-sm-api.web.cern.ch/lhc-sm-api/user_install.html#preinstalled-packages) as well as makes a copy of HWC notebooks to `hwc` notebooks. **Note that in order to ensure compatibility between package and notebook versions, the `hwc` folder is deleted each time the script is executed'.**
Firstly, contact the Signal Monitoring team (mailto:lhc-signal-monitoring@cern.ch) in order to get read access to the EOS folder with pre-installed packages and HWC analysis notebooks.
Once the access is granted, at every log-in to SWAN, please provide the following environment script:
`/eos/project/l/lhcsm/public/packages_notebooks.sh`
<img src="https://gitlab.cern.ch/LHCData/lhc-sm-hwc/raw/master/figures/swan_environment_script.png" width=25%>
<center><img src="https://gitlab.cern.ch/LHCData/lhc-sm-hwc/raw/master/figures/swan_environment_script.png" width=25%></center>
Note the following settings while configuring environment:
- Software stack: `NXCals Python3`
- Platform: `CentOS 7 (gcc7)` - default
- Environment script: `/eos/project/l/lhcsm/public/packages_notebooks.sh`
......@@ -145,30 +145,30 @@
## 4. Running Notebook
### 4.1. Open notebook
To do so simply click its name and a new page will be opened. The top of the notebook is presented in Figure below.
![SWAN RB FPA analysis intro](figures/swan-rb-fpa-analysis-intro.png)
<center><img src="https://gitlab.cern.ch/LHCData/lhc-sm-hwc/raw/master/figures/swan-rb-fpa-analysis-intro.png" width=50%></center>
### 4.2. Connect to the NXCALS Spark Cluster
Once a notebook is opened, please click a star button as shown in Figure below in order to open the Spark cluster configuration in a panel on the right side of an active notebook.
![SWAN Open Spark Cluster Configuration](figures/swan-open-spark-cluster-configuration.png)
<center><img src="https://gitlab.cern.ch/LHCData/lhc-sm-hwc/raw/master/figures/swan-open-spark-cluster-configuration.png" width=50%></center>
Figure below shows a three-step procedure of Spark cluster connection. The first step involves providing the NICE account password. The second step allows setting additional settings for the connection. In order to connect with NXCALS please make sure to enable the following options:
- Include NXCALS options - to connect to the cluster
- Include SparkMetrics options - to enable statistics helpful for analysing NXCALS queries
The last step is a confirmation of a successful connection to the cluster.
![SWAN Spark Cluster Connection](figures/swan-spark-cluster-connection.png)
<center><img src="https://gitlab.cern.ch/LHCData/lhc-sm-hwc/raw/master/figures/swan-spark-cluster-connection.png" width=75%></center>
### 4.3. Analysis Notebook Execution
A notebook is composed by cells. A cell contains either a markdown text with description or python code toexecute. Cells with markdown text have white background and can contain text, tables, figures, and hyperlinks.Cells with code have gray background and are executed by clicking a run icon in the top bar highlighted in Figure below. Alternatively, one can put a cursor in a cell with code an press a keyboard shortcut Ctrl+Enter.
![SWAN Execute Cell](figures/swan-execute-cell.png)
<center><img src="https://gitlab.cern.ch/LHCData/lhc-sm-hwc/raw/master/figures/swan-execute-cell.png" width=50%></center>
A state of a cell is indicated by square brackets located on the left to a cell. Execution of a cell is indicatedby a star in the square brackets. Once cell execution is completed the star changes into a number representingthe order of cell execution. A cell can execute for too long due to connection problems, issues with a databasequery, kernel problems. In this case, two actions are recommended:
1. Select from the top menu: Kernel -> Interrupt and execute the problematic cell again (either a run button (cf. Figure above) or Ctrl+Enter).
2. In case the first option does not help, select from the top menu Kernel -> Restart & Clear Output. Thenall cells prior to the problematic one have to be executed again (multiple cell selection is possible byclicking on the left of a cell to select it and afterwards selecting others with pressed Shift button). After this operation one needs to reconnect to the NXCALS Spark cluster.
......@@ -182,18 +182,19 @@
# Analysis Workflow
An FPA analysis workflow consists of four steps: (i) finding of an FGC Post Mortem timestamp (ii) executing analysis cells on the cluster (iii); (iv) storing output files on EOS; see Figure below.
![FPA Analysis Workflow](figures/fpa-analysis-workflow.png)
<center><img src="https://gitlab.cern.ch/LHCData/lhc-sm-hwc/raw/master/figures/fpa-analysis-workflow.png" width=50%></center>
The RB FPA Analysis notebook is organized into 11 chapters:
0. Initialise the working environment
Loads external packages as well as lhcsmapi classes required to perform analysis and plot results.
1. Select FGC Post Mortem Entry
After executing this cell, a FGC Post Mortem GUI with default settings is displayed.
![SWAN RB FPA Analysis FGC PM Browser Empty](figures/swan-rb-fpa-analysis-fgc-pm-browser-empty.png)
<center><img src="https://gitlab.cern.ch/LHCData/lhc-sm-hwc/raw/master/figures/swan-rb-fpa-analysis-fgc-pm-browser-empty.png" width=50%></center>
The GUI consists of 8 widgets described in Table below.
|Widget|Description|
|------|-----------|
......@@ -207,21 +208,20 @@
**Please note that in order to execute any of the following cells, there should be at least one entry in the FGC PM Entries list. The list is populated after clicking [Find FGC PM entries button].**
Figure below shows the GUI after clicking button [Find FGC PM entries] with the default settings. Note that the list only contains FGC PM timestamps surrounded by QPS timestamps (1 minute before and 5 minutes after an FGC PM timestamp).
![SWAN RB FPA Analysis FGC PM Browser](figures/swan-rb-fpa-analysis-fgc-pm-browser.png)
<center><img src="https://gitlab.cern.ch/LHCData/lhc-sm-hwc/raw/master/figures/swan-rb-fpa-analysis-fgc-pm-browser.png" width=50%></center>
2. Query All Signals Prior to Analysis
In order to avoid delays between analyses, the necessary signals are queried prior to performing the analysis.
3. Timestamps
Table of timestamps main systems representing the sequence of events for a given analysis.
4. Schematic
Interactive schematic of the RB circuit composed of: power converter, two energy extraction systems, current leads, magnets, and nQPS crates. Hovering a mouse over a center of a box representing a system provides additional pieces of information. Location of quenched magnets is highlighted. Slider below the schematic enables its scrolling.
![RB Schematic](figures/rb-schematic.png)
<center><img src="https://gitlab.cern.ch/LHCData/lhc-sm-hwc/raw/master/figures/rb-schematic.png" width=50%></center>
5. PIC
Check of PIC timestamps
6. Power Converter
Analysis of the main power converter as well as earth currents.
......@@ -246,17 +246,17 @@
# Analysis Notebook for HWC
## Analysis Workflow
A HWC analysis workflow consists of four steps: (i) finding of start and end time of an HWC test (ii) executing analysis cells on the cluster (iii); (iv) storing output files on EOS; see Figure below.
![HWC Analysis Workflow](figures/hwc-analysis-workflow.png)
<center><img src="https://gitlab.cern.ch/LHCData/lhc-sm-hwc/raw/master/figures/hwc-analysis-workflow.png" width=50%></center>
## Notebook Structure
Each notebook is composed of initial part with a circuit schematic, test current profile, and table summarising test criteria. This part is followed by package import instructions, display and the browser of HWC tests; see Figure below.
![SWAN HWC Browser](figures/swan-hwc-browser.png)
<center><img src="https://gitlab.cern.ch/LHCData/lhc-sm-hwc/raw/master/figures/swan-hwc-browser.png" width=50%></center>
The remainder of each notebook depends on the particular test to be performed. At the end of an HWC notebook there are instructions for saving the output files.
## Notebook Output
......
......@@ -3,7 +3,7 @@ Although, as the project name indicates, our primary goal is the development of
Even though, we develop the analyses system by system, they were developed in a general way to account for all circuits in which the system was present. Thus, by taking a perpendicular view of the analysis table, a circuit analysis for this stance was possible.
<img src="https://gitlab.cern.ch/LHCData/lhc-sm-hwc/raw/master/figures/monitoring-vs-hwc.png" width=50%>
<center><img src="https://gitlab.cern.ch/LHCData/lhc-sm-hwc/raw/master/figures/monitoring-vs-hwc.png" width=50%></center>
In particular, thotebooks are suited for HWC tests:
- can be adjusted on-the-fly for new requirements while performing a test;
......@@ -12,7 +12,7 @@ In particular, thotebooks are suited for HWC tests:
# Supported Circuits
## 1. RB - Main Dipole Circuit
<img src = "https://gitlab.cern.ch/LHCData/lhc-sm-hwc/raw/master/figures/rb/RB.png" width=75%>
<center><img src = "https://gitlab.cern.ch/LHCData/lhc-sm-hwc/raw/master/figures/rb/RB.png" width=75%></center>
<p>source: Powering Procedure and Acceptance Criteria for the 13 kA Dipole Circuits, MP3 Procedure, <a href="https://edms.cern.ch/document/874713/5.1">https://edms.cern.ch/document/874713/5.1</a></p>
......@@ -33,7 +33,7 @@ In particular, thotebooks are suited for HWC tests:
|Operation|FPA|I\_PNO|FPA during operation with magnets quenching|[AN\_RB\_FPA](https://gitlab.cern.ch/LHCData/lhc-sm-hwc/-/blob/master/rb/AN_RB_FPA.ipynb)|[AN\_RB\_FPA](https://sigmon.web.cern.ch/node/59)|
## 2. RQ - Main Quadrupole Circuit
<img src="https://gitlab.cern.ch/LHCData/lhc-sm-hwc/raw/master/figures/rq/RQ.png" width=75%>
<center><img src="https://gitlab.cern.ch/LHCData/lhc-sm-hwc/raw/master/figures/rq/RQ.png" width=75%></center>
<p>source: Test Procedure and Acceptance Criteria for the 13 kA Quadrupole (RQD-RQF) Circuits, MP3 Procedure, <a href="https://edms.cern.ch/document/874714/5.1">https://edms.cern.ch/document/874714/5.1</a></p>
......@@ -59,7 +59,7 @@ The 600-A circuits come in one of two main variants:
Each variant may or may not be equipped with a DC contactor ensuring the effectiveness of the crowbar in case of a PC short circuit. Moreover, the magnets of several circuits are equipped with parallel resistors, in order to decouple the current decay in a quenching magnet from that in the rest of the circuit. Figure 1 shows a generic circuit diagram, equipped with EE and parallel resistor, as well as lead resistances and a quench resistance.
<img src="https://gitlab.cern.ch/LHCData/lhc-sm-hwc/-/raw/master/figures/600A/600A.png" width=75%>
<center><img src="https://gitlab.cern.ch/LHCData/lhc-sm-hwc/-/raw/master/figures/600A/600A.png" width=75%></center>
source: Test Procedure and Acceptance Criteria for the 600 A Circuits, MP3 Procedure, <a href="https://edms.cern.ch/document/874716/5.3">https://edms.cern.ch/document/874716/5.3</a>
......@@ -116,7 +116,7 @@ The following steps should be followed in order to log-in to SWAN
2. Login with your NICE account
- SWAN is tightly integrated with CERNBox service (in fact, files created in SWAN are accessible in CERNBox). In case you have not used CERNBox, the following error message will be displayed in- dicating that your CERNBox account has not been activated yet. In order to activate your CERNBox account, please login on the website: http://cernbox.cern.ch. Afterwards, please login to SWAN service again. In case the error persists, please contact the SWAN support (see Section Help and Feedback at the bottom).
<img src="https://gitlab.cern.ch/LHCData/lhc-sm-hwc/raw/master/figures/swan-inactive-cernbox-error.png" width=50%>
<cetner><img src="https://gitlab.cern.ch/LHCData/lhc-sm-hwc/raw/master/figures/swan-inactive-cernbox-error.png" width=50%></center>
## 3. Setting an Environment Script
In order to execute the HWC notebooks, one requires `lhc-sm-api` package and HWC notebooks. To this end, we created a dedicated environment script to prepare the SWAN project space.
......@@ -126,7 +126,7 @@ Firstly, contact the Signal Monitoring team (mailto:lhc-signal-monitoring@cern.c
Once the access is granted, at every log-in to SWAN, please provide the following environment script:
`/eos/project/l/lhcsm/public/packages_notebooks.sh`
<img src="https://gitlab.cern.ch/LHCData/lhc-sm-hwc/raw/master/figures/swan_environment_script.png" width=25%>
<center><img src="https://gitlab.cern.ch/LHCData/lhc-sm-hwc/raw/master/figures/swan_environment_script.png" width=25%></center>
Note the following settings while configuring environment:
- Software stack: `NXCals Python3`
......@@ -141,13 +141,13 @@ Note the following settings while configuring environment:
To do so simply click its name and a new page will be opened. The top of the notebook is presented in Figure below.
![SWAN RB FPA analysis intro](figures/swan-rb-fpa-analysis-intro.png)
<center><img src="https://gitlab.cern.ch/LHCData/lhc-sm-hwc/raw/master/figures/swan-rb-fpa-analysis-intro.png" width=50%></center>
### 4.2. Connect to the NXCALS Spark Cluster
Once a notebook is opened, please click a star button as shown in Figure below in order to open the Spark cluster configuration in a panel on the right side of an active notebook.
![SWAN Open Spark Cluster Configuration](figures/swan-open-spark-cluster-configuration.png)
<center><img src="https://gitlab.cern.ch/LHCData/lhc-sm-hwc/raw/master/figures/swan-open-spark-cluster-configuration.png" width=50%></center>
Figure below shows a three-step procedure of Spark cluster connection. The first step involves providing the NICE account password. The second step allows setting additional settings for the connection. In order to connect with NXCALS please make sure to enable the following options:
- Include NXCALS options - to connect to the cluster
......@@ -155,12 +155,12 @@ Figure below shows a three-step procedure of Spark cluster connection. The first
The last step is a confirmation of a successful connection to the cluster.
![SWAN Spark Cluster Connection](figures/swan-spark-cluster-connection.png)
<center><img src="https://gitlab.cern.ch/LHCData/lhc-sm-hwc/raw/master/figures/swan-spark-cluster-connection.png" width=75%></center>
### 4.3. Analysis Notebook Execution
A notebook is composed by cells. A cell contains either a markdown text with description or python code toexecute. Cells with markdown text have white background and can contain text, tables, figures, and hyperlinks.Cells with code have gray background and are executed by clicking a run icon in the top bar highlighted in Figure below. Alternatively, one can put a cursor in a cell with code an press a keyboard shortcut Ctrl+Enter.
![SWAN Execute Cell](figures/swan-execute-cell.png)
<center><img src="https://gitlab.cern.ch/LHCData/lhc-sm-hwc/raw/master/figures/swan-execute-cell.png" width=50%></center>
A state of a cell is indicated by square brackets located on the left to a cell. Execution of a cell is indicatedby a star in the square brackets. Once cell execution is completed the star changes into a number representingthe order of cell execution. A cell can execute for too long due to connection problems, issues with a databasequery, kernel problems. In this case, two actions are recommended:
1. Select from the top menu: Kernel -> Interrupt and execute the problematic cell again (either a run button (cf. Figure above) or Ctrl+Enter).
......@@ -176,14 +176,15 @@ Quench analysis assumptions:
An FPA analysis workflow consists of four steps: (i) finding of an FGC Post Mortem timestamp (ii) executing analysis cells on the cluster (iii); (iv) storing output files on EOS; see Figure below.
![FPA Analysis Workflow](figures/fpa-analysis-workflow.png)
<center><img src="https://gitlab.cern.ch/LHCData/lhc-sm-hwc/raw/master/figures/fpa-analysis-workflow.png" width=50%></center>
The RB FPA Analysis notebook is organized into 11 chapters:
0. Initialise the working environment
Loads external packages as well as lhcsmapi classes required to perform analysis and plot results.
1. Select FGC Post Mortem Entry
After executing this cell, a FGC Post Mortem GUI with default settings is displayed.
![SWAN RB FPA Analysis FGC PM Browser Empty](figures/swan-rb-fpa-analysis-fgc-pm-browser-empty.png)
<center><img src="https://gitlab.cern.ch/LHCData/lhc-sm-hwc/raw/master/figures/swan-rb-fpa-analysis-fgc-pm-browser-empty.png" width=50%></center>
The GUI consists of 8 widgets described in Table below.
......@@ -201,7 +202,7 @@ The GUI consists of 8 widgets described in Table below.
Figure below shows the GUI after clicking button [Find FGC PM entries] with the default settings. Note that the list only contains FGC PM timestamps surrounded by QPS timestamps (1 minute before and 5 minutes after an FGC PM timestamp).
![SWAN RB FPA Analysis FGC PM Browser](figures/swan-rb-fpa-analysis-fgc-pm-browser.png)
<center><img src="https://gitlab.cern.ch/LHCData/lhc-sm-hwc/raw/master/figures/swan-rb-fpa-analysis-fgc-pm-browser.png" width=50%></center>
2. Query All Signals Prior to Analysis
In order to avoid delays between analyses, the necessary signals are queried prior to performing the analysis.
......@@ -210,8 +211,7 @@ Table of timestamps main systems representing the sequence of events for a given
4. Schematic
Interactive schematic of the RB circuit composed of: power converter, two energy extraction systems, current leads, magnets, and nQPS crates. Hovering a mouse over a center of a box representing a system provides additional pieces of information. Location of quenched magnets is highlighted. Slider below the schematic enables its scrolling.
![RB Schematic](figures/rb-schematic.png)
<center><img src="https://gitlab.cern.ch/LHCData/lhc-sm-hwc/raw/master/figures/rb-schematic.png" width=50%></center>
5. PIC
Check of PIC timestamps
......@@ -232,18 +232,19 @@ The notebook creates three output files in the folder //cern.ch/eos/project/l/lh
- CSV file with MP3 results table with a subset analysis results - [fgc-timestamp]-[analysis-execution-date]-[notebook-name]\_mp3\_results\_table.csv};
- CSV file with full results table - [fgc-timestamp]-[analysis-execution-date]-[notebook-name]\_results_table.csv};
# Analysis Notebook for HWC
## Analysis Workflow
A HWC analysis workflow consists of four steps: (i) finding of start and end time of an HWC test (ii) executing analysis cells on the cluster (iii); (iv) storing output files on EOS; see Figure below.
![HWC Analysis Workflow](figures/hwc-analysis-workflow.png)
<center><img src="https://gitlab.cern.ch/LHCData/lhc-sm-hwc/raw/master/figures/hwc-analysis-workflow.png" width=50%></center>
## Notebook Structure
Each notebook is composed of initial part with a circuit schematic, test current profile, and table summarising test criteria. This part is followed by package import instructions, display and the browser of HWC tests; see Figure below.
![SWAN HWC Browser](figures/swan-hwc-browser.png)
<center><img src="https://gitlab.cern.ch/LHCData/lhc-sm-hwc/raw/master/figures/swan-hwc-browser.png" width=50%></center>
The remainder of each notebook depends on the particular test to be performed. At the end of an HWC notebook there are instructions for saving the output files.
......@@ -260,6 +261,7 @@ e.g.,
- HTML report file with the snapshot of the entire notebook - [test-start]-[test-end]\_report.html;
# Help and Feedback
Despite thorough testing, while using LHC-SM quench analysis notebooks two types of issues can occur, related to:
- analysis (e.g., wrong analysis results, corrupted plots, etc.);
......@@ -276,4 +278,4 @@ There are three ways to contact SWAN support for help related to the service:
All three links are also available in the footer of SWAN website as shown in Fig. 3.1.
![SWAN Help](figures/swan-help.png)
\ No newline at end of file
![SWAN Help](figures/swan-help.png)
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment