Differences between revisions 80 and 81

Log of Kamioka Activity during 2020/08/17 ~ 27

Participants

If you are unfamiliar with the simulation operations, there is a possibility that errors may occur in the script description and so on.
By creating a GUI, such errors can be prevented and the reliability of the simulation results can be increased.

1. Installation of eel

note that:

We installed several tools to run simulations using Finesse.
We initially considered using eel, but found it difficult to create gui using eel and finesse at the same time, so we decided to use pysimplegui instead of eel.
This eliminates the need to install eel (and chromium).
PySimpleGUI is a module for python that creates gui.
eel is a Python module used to create a GUI.
I didn't found any instructions on how to install eel without using pip.
Therefore, we use pip to install eel in conda's virtual environment.

Activate the conda virtual environment.

And type the following command

To use eel, you need to install a specific browser like "chromium".

You can install chromium by typing the following command.

2. Learning HTML and javascript

3. Learning Python

Python is used to run simulations using "finesse2
Creation of GUI In "finesse2", we use character strings which describe the simulation settings.
Create a selection box (GUI) and load the settings you entered into the box by "finesse2" and execute it.

4. Creating a simple GUI with python and HTML.

An error occurs when sending the input value to Finesse, so we are looking for an improvement.
We gave up to use eel.

how we installed package PySimpleGUI?
- We use conda. https://anaconda.org/conda-forge/pysimplegui
  - ```
  conda install -c conda-forge pysimplegui 
```
what is the name of virtual environment on control workstation?
- MIFsim37
- Now there are many kinds of environments on control workstation. Before leaving, we should delete unnecessary virtual environment.
- Yuzurihara likes the name of 'mifsim37'
you can choose which DoF to run.
You can now choose where to put the PD.
You can now choose the laser power.
overplot ga mondai.We can't split plots.
in jupyter-notebook, two plots are displayed separately. .py dato gamenn kuroi
- (Yuzurihara) one of the solution is to use 'matplotlib' and summarize all the result on one figure. If so, we don't need second plot.
- Koyama-san solved this by using matplotlib.
pd1 ga hituyoukadouka ("Transfer function" uses "pd2". need "pd1" for "diff"?)
- Based on lecture by Kokeyama-san, Koyama-san implemented.
Yuzurihara implemented the feature to output the plot data and the kat file.

resize the figure of the interferometer

convert Fabry_Perot_MI_eom_drawing.png -resize 800x600 hoge.png

Koyama added all nodes to GUI (on GUI, we use REFL/AS. But, in the source we use just n1 / n2 /....)
Koyama removed exit button from GUI (By pushing the button on top right, we exit from GUI)
Koyama changed the size of the outputted figure to be large
(Koyama) the xlabel and ylabel on figure are automatically added.
make the plot display large
- Figure size changed large. But, the label and number on axis are very small.
output kat file (be careful to overwride)
output the plot data (be careful to overwride)
if we use "put" multiple times, what will happen?
(Koyama) Fixed the bug
- when plotting PD2, the plotting of PD1 appear at the same time
(Koyama) change variable name (f1 → f1_SB, f2→ f2_SB)
(Yuzurihara) Prepared the virtual environment on all control workstation (virtual environment name : mifsim37)

(Hirose) prepare manual
- write README.md on git repository
- make a drawing of interferometers by using an "inkscape"
(Hirose) add the brief manual on GUI display (such as "1. select interferometer configuration 2. select mode (power/...)")
(Hirose) change the displayed name of PD place(GUI) to something suitable name (nxtrans→netx??) http://gwwiki.icrr.u-tokyo.ac.jp/JGWwiki/LCGT/subgroup/ifo/MIF/OptParam
(Hirose) change the check box of PDs larger→[font=(font_name,font_size)]
(Hirose) measure the computational time
(Koyama) make a select box about "pd1" plotting (Eg.I1/Q1/I1 and Q1 overplot)
(Koyama) Fixed the bug
- when sekected only one pd1 output option(I1/I2/Q2/Q2), it caused an error.
(Koyama) Add option tab to select not required settings(xplotsclae(log/linear)/yplotscale...)
- (Koyama) Check the plotting scale (log/linear) for PD0 and PD1
- (Koyama) Add options to select the yaxis plotting scale log/linear(pd2)
- (Koyama) Add options to select the plotting scale(log/linear), especialy y-scale of PD2

KAGRA/Subgroups/MIF/Simulation/KamikokaActivity20200817 (last edited 2020-10-18 17:32:36 by naoki.koyama)

-  ⇤ ← Revision 80 as of 2020-08-26 09:34:47 → 
  Size: 6633
  Editor: HirotakaYuzurihara
  Comment:
+   ← Revision 81 as of 2020-08-26 09:35:43 → ⇥
  Size: 6633
  Editor: HirotakaYuzurihara
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 120:
-  * (Koyama) ADD options to select the yaxis plotting scale log/linear(pd2)
+  * (Koyama) Add options to select the yaxis plotting scale log/linear(pd2)