Differences between revisions 8 and 9
Revision 8 as of 2019-07-19 11:36:04
Size: 3047
Editor: AyakaShoda
Comment:
Revision 9 as of 2019-07-19 13:03:45
Size: 3120
Editor: AyakaShoda
Comment:
Deletions are marked like this. Additions are marked like this.
Line 60: Line 60:
   * They want to check the current situation (such as TFs) by one-click. -> Shoda proposes to make the 'latest' directory to store the latest results, where the data is automatically updated with the copies of the measurements when we run the auto-measurement script. Also add the summary plot there. ([[|sample]])    * They want to check the current situation (such as TFs) by one-click. -> Shoda proposes to make the 'latest' directory to store the latest results, where the data is automatically updated with the copies of the measurements when we run the auto-measurement script. Also add the summary plot there. ([[https://www.dropbox.com/s/yqn4vtsn7pyqkf9/PR3_IM_20190719_120643.png?dl=0|sample]])

Agenda/Minutes of the VIS Meeting on 2019/7/19

2019/7/19 13:30 -

Zoom Meeting

Participants:

Progress report

Type-A

Past week report

  • Modified the HPCD for the ETMY TM to increase the current limit from 40 mA to 120 mA, limited by the hardware watchdog.
  • The commissioning team was working on the damping filter for ETMY, the guardian for ETMX, and the DC control path.

Plan for coming weeks

Type B

Past week report

Plan for coming weeks

Type-Bp

Past week report

  • BFH output: klog

  • Working on updating noise-budgeting tool.

Plan for coming weeks

OMMT & OSTM (Takahashi)

Past week report

  • Checked the stock of OSEMs. 9 of 17 OSEMs are available, but evaluation is necessary.
  • Confirmed some dimensions on the present OSTM. The height of the breadboards was consistent with the design one. 10mm spacer is necessary.
  • Ordered the modification parts for the mirror gluing jig and the standoffs.

Plan for coming weeks

VIS electronics

Past week report

Plan for coming weeks

Other site works

Safety

  • Incidents:

Discussion

  • Data management
    • The directory structure of the auto-measurement is different between each types of suspensions.
      • Script files
        • TypeAtower: /users/VISsvn/TypeAtower/scripts
          TypeApayload: /users/VISsvn/TypeApayload/scripts
          TypeB: /kagra/Dropbox/Subsystems/VIS/TypeBData/scripts
          TypeBp: /users/VISsvn/TypeBp/scripts

      • Measured files
        • TypeAtower: /users/VISsvn/TypeAtower/(OPTIC)/Measurements/TF/Measurements/
          TypeApayload: /users/VISsvn/TypeApayload/(OPTIC)/TF/Measurements/
          TypeB: /kagra/Dropbox/Subsystems/VIS/TypeBData/(OPTIC)/TF/Measurements/
          TypeBp: /users/VISsvn/TypeBp/(OPTIC)/TF/Measurements/

      • And there are many junk files and directories that makes confusion.
    • Request from Commissioner
      • Unify the data structure so that they can easily look up the data. -> We will use /users/VISsvn or Dropbox.

      • They want to check the current situation (such as TFs) by one-click. -> Shoda proposes to make the 'latest' directory to store the latest results, where the data is automatically updated with the copies of the measurements when we run the auto-measurement script. Also add the summary plot there. (sample)

      • They also requested to make the templates for spectra of each guardian states (SAFE, DAMPED, ALIGNED, MISALIGNED).
    • template update campaign at some point?

Travel Plans

  • Travel (Week of 7/22):
    • Takahashi:
    • Sato:
    • Hirata:
    • Shoda:
    • Fujii:
    • Tanaka:
    • Terrence:
  • Travel (Week of 7/29):
    • Takahashi:
    • Sato:
    • Hirata:
    • Shoda:
    • Fujii:
    • Tanaka:

Next meeting

On 2019/7/26(Fri)

KAGRA/Subgroups/VIS/VISMinutes20190719 (last edited 2019-07-19 15:52:36 by YoichiAso)