Differences between revisions 144 and 145
Revision 144 as of 2020-11-26 12:51:49
Size: 20337
Comment:
Revision 145 as of 2020-12-03 11:05:51
Size: 20965
Comment:
Deletions are marked like this. Additions are marked like this.
Line 9: Line 9:
=== 20201203 (Thu.) ===
  * Agenda
    * Recovery of SummaryPage
    * Progress of O3GK analysis (incl. GEO data)
    * LV(K) O3 data replay
    * BNS range of O3GK with C20 h(t)
Line 20: Line 27:
      * waiting cWB triggers now.
      * Test with past CBC triggers will be performed.
Line 21: Line 30:
      * The 1st step is to see the bandbassed h(t) around Omicron triggers.
      * Cutoff frequencies of bandpass filter can be decided by Omicron frequency info.
Line 22: Line 33:
    * New computers in Kashiwa
    * f2f/KIW7
      * NFS trouble occurs and it is not available.
      * Only Kamioka local network, k1sum0 is available instead of gwdet.icrr....
    * f2f
      * Maybe one talk in O3GK session.
    * KIW7
      * No talk
Line 25: Line 40:
      * No talk

Meetings


Agenda & Minutes

20201203 (Thu.)

  • Agenda
    • Recovery of SummaryPage

    • Progress of O3GK analysis (incl. GEO data)
    • LV(K) O3 data replay
    • BNS range of O3GK with C20 h(t)

20201126 (Thu.)

  • Agenda
    • O3GK analysis
      • hveto progress (cWB situation)
      • Glitch catalogue
    • O4 preparation
    • Meetings
  • Minutes
    • hveto progress (cWB situation)
      • waiting cWB triggers now.
      • Test with past CBC triggers will be performed.
    • Glitch catalogue
      • The 1st step is to see the bandbassed h(t) around Omicron triggers.
      • Cutoff frequencies of bandpass filter can be decided by Omicron frequency info.
    • SummaryPage problem

      • NFS trouble occurs and it is not available.
      • Only Kamioka local network, k1sum0 is available instead of gwdet.icrr....
    • f2f
      • Maybe one talk in O3GK session.
    • KIW7
      • No talk
    • JPS
      • No talk

20201119 (Thu.)

  • Agenda
    • C20 offline h(t)
    • O4 preparation
    • f2f/KIW7/JPS
  • Minutes
    • C20 offline h(t)
      • hveto analysis is performed with Omicron triggers of h(t) and aux. channels.
        • cWB search is not finished yet.
      • Data transfer to KISTI is performed with DMG software.
    • O4 preparation
      • SummaryPage is now stopped for the maintenance and updates.

      • New DetChar computers are preparing in Kashiwa

        • Procuring itself is finished until end of year.
      • Additional disk storage is needed in KISTI as Tier-1 site.
        • 600-800TB/yr is required to store the full data of O4 (in 1-year obs. case.)
        • Actual past results and data-access frequency are required to submit a proposal.
    • f2f
      • O3GK session: 1 slot(?) [progress report of O3GK analysis]
      • parallel session: No talk(?)
      • poster session: No talk(?)
    • KIW7
      • No talk(?)
    • JPS
      • No talk(?)
    • Monthly telecon with LV
      • held on last Monday in every month.
      • start from Nov. 30th or Jan. 25th
      • Dec 28th will be cancelled due to the end-of-year holidays.

20201111 (Thu.)

  • Agenda
    • C20 offline h(t)
    • O4 data release schedule
    • f2f/KIW7
  • Minutes
    • C20 offline h(t)
      • Comment from DAC meeting:
        • Burst group can be provide GW event trigger list (schedule is not decided yet.)
        • Detail DQ info. around GRB events is very useful.
      • Data transfer on DET server
        • Done.
      • Omicron trigger generation for C20 h(t)
        • Generation itself was finished
        • There is no error on Omicron process.
      • Data transfer on KISTI cluster
        • Sangwook will do.
        • After the data transfer, Kihyun can resume his analysis with C20.
    • O4 data release schedule

20201103 (Thu.)

  • Agenda
    • C20 offline h(t)
    • O4 data release schedule
  • Minutes
    • C20 offline h(t)
      • Data should be copied to Kamioka server.
      • Glitch trigger search by Omicron
        • After data copy, it will be resumed.
      • hveto needs GW trigger search
        • We can demonstrate with omicron trigger of h(t).
        • After GW search triggers are available it will be resumed.
      • Data transfer to KISTI
        • discuss with DAS people on the next KGWG meeting
    • O4 data release schedule

20201022 (Thu.)

  • Agenda
    • Segment of O3GK
    • Documentation about O3GK info.
    • SummaryPage for O4 installation

  • Minutes

20201008 (Thu.)

  • Agenda
    • Planned power outage
    • hveto bug
  • Minutes
    • Planned power outage
      • All jobs on k1det must be stopped until 10/13 morning.
    • hveto bug
      • Code reading is in progress by Chihiro.
        • There is no response from LIGO people.
      • Analysis of Apr 8th - 21st data is on going.
    • Segment update
      • Discussion with Robert is resumed.
      • Upload method is 'pull' from LIGO side.
      • They already know the path to the segment files and types of segment file.
      • Remains tasks are schedule and segment name on DQSEGDB.
    • Announcement
      • 22:00 (JST/KST) tonight, LVK operation workshop will be held.

20201001 (Thu.)

  • Agenda
    • Planned power outage (10/14)
  • Minutes
    • Planned power outage (10/14)
      • k1det will be stopped until 10/13 morning.
      • They will come back online after 10/15.

20200924 (Thu.)

  • Agenda
    • Segment update
    • hveto problem
  • Minutes
    • Segment update
      • All 9 segment info. were fixed.
      • They had already copied to Kashiwa and Kamioka.
      • They should be copied also KISTI.
      • TY will contact to Robert again.
      • After then, segments will be uploaded to DQSEGDB.
    • hveto problem
      • Problem is cased by hveto
      • Some trigger files are sent to LDAS.
      • Investigation on LDAS is ongoing.
      • Conf. file on Kamioka should be share to KISTI.

20200911 (Thu.)

  • Agenda
    • Progress of O3GK analysis
    • Duty cycle evaluation during O3GK
    • Lock loss study
    • O3GK DetChar talk in LVK meeting

  • Minuets
    • Progress of O3GK analysis
      • Investigating strange behavior of hveto
      • On KISTI cluster, it works well.
        • Cross check of Chihiro's result and Kihyun's one is ongoing.
        • Round winner channel changes day by day. (Is it consistent with past results?)
        • K1:ASC-AS*** is not maintained well.
        • Both Safe and Unsafe channel list should be used as same ones.
    • Duty cycle evaluation during O3GK
      • 54% duty factor (2 weeks average)
      • BNS range, 500kpc (2 weeks average, cal mistakes is already revised.)
      • Only last a few days, BPC lines are enabled.
    • Lock loss study
      • BLRMS has some time delay.
      • LOCKED segments should be used ins
    • O3GK DetChar talk in LVK meeting

      • topics
        • Achievement of KAGRA readiness
        • Progress of concrete analysis
        • BNS ranges, duty factor as the overview.
      • => Yamamoto, Kozakai

20200903 (Thu.)

  • Agenda
    • trigger generation
    • hveto analysis
  • Minutes
    • trigger generation
      • Analysis is finished.
      • Two channels have some problem.
      • The version problem of gwpy occurs on KISTI.
      • Latest channel list should be shared on GitHub.

    • hveto analysis
      • Omicron triggers should be shared with LIGO people. (Kamioka -> LIGO) => Kozakai-san will contact to Alex.

      • hveto works well on KISTI. => Kihyun will continue to analysis.

20200827 (Thu.)

  • Agenda
    • Segment Update
    • KAGRA data analysis
    • GEO data analysis
  • Minutes
    • Segment Update
      • Broken frames period are removed from new science segments (K1-GRD_SCIENCE_MODE_AND_DAQ_STATUS_OK)
      • Broken frames period as provided a new segments definition (K1-DAQ_STATUS_BAD)
      • They are store in detchar@m31:Segments/
      • Obsolete segments are still generated (???).
    • KAGRA data analysis
      • Some PEM sensors are added to the channel list for omicron analysis. => (until next week.)

      • When is the location of each sensor fixed? => At least around Feb. (also for PORTABLE)

      • Disk full problem and script errors are occur KISTI
      • hveto problem occurs (Apr 15. UTC)
    • GEO data analysis

20200806 (Thu.)

  • Agenda
    • f2f meeting
    • progress of O3GK
  • Minutes
    • f2f meeting
      • We have parallel session. (need to prepare two talks for Experiment and Data analysis.)
      • Experiment -> Yamamoto, Data Analysis -> Kozakai? Kihyun also considers an oral or a poster session.

    • progress of O3GK
      • Reconsidering Safe/Unsafe channels is on going.
      • We need to re-analyze for some channels and some segments by Omicron.
      • Cross check of KAGRA data analysis can be done by Kihyun.
      • GEO data transfer to KISTI cluster is almost done.
      • Kihyun can continue to analyze the GEO data.
      • We need to do cross check of the results of GEO data analysis.

20200730 (Thu.)

  • Agenda
    • Safe/Unsafe channel (slide)

20200723 (Thu.)

  • Cancelled

20200702 (Thu.)

  • Agenda
    • Safe/Unsafe channel
    • Omicron troubles
    • GEO data analysis

20200625 (Thu.)

  • Agenda
    • Broken frames
    • O3GK
      • trigger generation
      • hveto
      • CAGMon
  • Minutes
    • Broken frames
      • Totally 26 broken frames. (Science: 4, Locked: 4, Unlocked: 18)
      • TY will remove 32-second long data which is in broken frames from science mode segments by manually.
      • After then, the segment script will be updated for taking into account broken frames.
    • O3GK
      • trigger generation
        • Some runtime error occurs on the Kamioka server.
        • Trigger generation test is started with KAGRA data on the KISTI server.
        • GEO data transfer to the KISTI server is not finished yet.
      • hveto
        • Test with short time data is ongoing
      • CAGMon
        • Analysis with Apr. observation data is already started.
        • Used Channel list is same as YuzuSummary's one.

        • Safe/Unsefe channel list is also required --> will be discussed next week.

20200618 (Thu.)

  • Agenda
    • LVK operations white paper
      • task list
      • introduction of ICA
      • Current progress of CAGMON

20200610 (Thu.)

  • Agenda
    • DAQ error during O3GK (JGW-G2011751)

    • KAGRA data analysis (Omicron/hveto)
    • GEO data analysis (Omicron/CAGMon)
  • Minutes
    • DAQ error during O3GK
      • Ueno-san found file reading error with following frames.
        • K-K1_C-1270444416-32.gwf 2020-04-09 14:13:18 (JST)
          K-K1_C-1270570496-32.gwf 2020-04-11 01:14:38 (JST)
          K-K1_C-1270577376-32.gwf 2020-04-11 03:09:18 (JST)
          K-K1_C-1270680672-32.gwf 2020-04-12 07:50:54 (JST)
          K-K1_C-1271033536-32.gwf 2020-04-16 09:51:58 (JST)
          K-K1_C-1271174912-32.gwf 2020-04-18 01:08:14 (JST)
          K-K1_C-1271226144-32.gwf 2020-04-18 15:22:06 (JST)
          K-K1_C-1271440736-32.gwf 2020-04-21 02:58:38 (JST)
    • KAGRA data analysis
      • Omicron search around GRB was finished.
      • Whole 2-weeks analysis is now being performed.
      • It's better to remove some channels from unsafe channel list.
      • We should test hveto with some channel lists.

20200604 (Thu.)

  • Agenda
    • LVK white paper
    • O3GK analysis
  • Minutes
    • LVK white paper
      • Operations white paper
        • 2. Observatory Operations
          3. Detector Commissioning
          4. Calibration
          5. Detector Characterization
          6. Computing and software
      • Observational Science white paper
        • 1.1 Burst
          1.2 CBC
          1.3 CW
          1.4 Stochastic
          2 Burst
          3 CBC
          4 CW
          5 Stochastic
          6 Burst+CBC+DetChar Joint Activity Plans
          7 Burst+CBC Joint Activity Plans
          8 Burst+Stochastic Joint Activity Plans
          9 Stochastic+CBC
          10 Stochastic+Detchar

20200521 (Thu.)

  • Agenda
    • Talk plans for JPS meeting
    • PTEP paper
    • O3GK analysis
  • Minutes
    • Talk plans for JPS meeting
      • TY will give a DET summary talk.
      • Deadline 4th June.
    • PTEP paper
      • Writing draft was finished.
      • After checking the whole, draft will be submitted to CPC.
    • O3GK analysis
      • Segment information is being reprovided as Science, Locked , Unlock, and OMC Overflow.
      • Omicron triggers will be regenerated with new segment information.
      • hveto will be applied after generating Omicron triggers with new segment and configurations.
      • O3GK data is available on the KISTI cluster.
      • Bug fix is required for using CAGMon.

LVK 20200518/19 (Mon./Tue.)

20200514 (Thu.)

  • Agenda
    • PTEP paper
    • Regenerate segment information
    • Regenerate omicron triggers
    • SummaryPage stability

    • Activities on KISTI
  • Minutes

20200507 (Thu.)

  • O3GK DetChar analysis

    • KAGRA DQ flags/segments
    • Glitch searches
    • Burst trigger veto
    • GEO DQ flags/segments
  • Minutes
    • KAGRA DQ flags/segments
      • Reproducing OMC overflow segments
      • Overflow segments are provided as separately from Science mode
      • 'SegmentList_locked_UTC_***.txt' is expired.

      • Reproduced segments information should be uploaded to DQSEGDB
    • Glitch searches
      • Omicron configuration should be reoconsidered
      • Triggers will be regenerated with new configurations
      • Discussion of configuration (chunk-size, intervals...) is ongoing.
    • Burst trigger veto
      • All cWB triggers are not vetoed by hveto
      • cWB has some problems(?)
      • Omicron parameter should be considered again.
    • GEO DQ flags/segments
      • GEO people are now providing new frames including both the strain signal and important auxiliary channels.
      • GEO frames will be transferred form CIT to Kashiwa (and Kashiwa to KISTI?)
      • Omicron can be used on KISTI cluster
      • We need the information about the amount of data.
      • CAGMon results will be also available in near future.

20200423 (Thu.)

Minutes

  • How to manage a DQ check for event alerts
    • Shall we make a proper data quality report for each event? => after collecting information we will make a report and put on JGW doc

    • Does ligo have the template to be sent to segdb? => to be checked

    • For now, we make a dedicated wiki page
      • list a specific check list: For GRB200415A, check resG condition, check if OMC PD A was overflow or not
    • Share Detchar info with CAL, BURST, DMG
  • How to organize RRT for the next obs

20200416 (Thu.)

  • Agenda:
    • Run status
    • DQ Shift
    • KISTI activities

20200402 (Thu.)

  • Agenda:
    • File server status
      • SummaryPage

      • Omicron trigger generation
      • Segment Information
      • KISTI results capability
    • Observing run
    • Update for O4 plan

20200326 (Thu.)

  • Agenda:
    • Commissioning situation
      • Commissioning test will be continued until Mar. 31st
      • During Apr. 1st to 7th, engineering run will be performed.
      • After Apr. 7th, we have a two weeks observing run (only KAGRA)
      • If LIGO, and Virgo will come back to observing run, we will aim to join O3.
    • SummaryPage (RAID trouble)

      • File server has a disk problem.
      • RAID system is now being rebuilt. (It will be finished today's evening.)
    • GlitchPlot for Burst evnet triggers

    • DetChar pipelines on KISTI

      • Code update of CAGMon

20200312 (Thu.)

  • Agenda:
    • Current status of site (commissioning) activities
      • Commissioning break was started from 10th Mar. It continues until 24th Mar.
      • Joinning O3 should be discussed on JRPC meeting on 26th Mar.(?).
    • Update of DQ state vector
      • Science mode during 25th Feb. - 10th Mar. didn't include SDF flags.
      • I updated to contain the SDF flags as the one of the condition of the Science mode.
    • Automation plan of GlitchPlot for GW event alert

      • We plan to move GlitchPlot from ICRR cluster to Kamioka computers.

      • Requirement:
        • Disk: 100MB/event
        • CPU: ???
    • Data transfer to KISTI
      • ER on Dec. data was transferred.
      • Many tools is already available on KISTI cluster.
    • Announce about LVK session
      • We plan to have DetChar telecons instead of LVK meeting.

      • TY circulate concrete date and time on ML after deciding.

20200305 (Thu.)

  • Agenda:
    • Observing run status
      • Binary range is ~400kpc (Best is 500kpc.)
      • Trigger rate check
        • Quite difference Trigger rate between the strain signal and the error signal.
      • Glitch plot with Burst triggers.
    • SummaryPage troubles

      • Some process (LSC.ini) was frequently stopped.
    • RRT tools
      • Shinkai-san suggested us it's better to prepare the dedicated workstation and mail address.
      • RRT tools from medm interface is available at Kamioka site
      • LValert can be receive alert from GraceDB.
        • Event information is not enough (no mass parameter).
        • Tagoshi-san tested on Kashiwa server.

20200227 (Thu.)

  • Agenda:
    • SummaryPage trouble

      • Configuration file errors -> fixed and checking now (Oshino-san)

      • Past two day's pages will be regenerated.
    • RRT
      • Short-time SummaryPage generator tool on MEDM.

      • lvalert may be already available for KAGRA.
      • We can receive RRT call by setting 'GCN PRELIM SENT'.
    • DQ shift
      • This taks should be assigned for collaborator shift.
      • TY will discuss this issue with Miyoki-san.

20200130 (Thu.)

  • Agenda:
    • KAGRA Readiness
    • RRT shift
    • PEM DQ flags

20200116 (Thu.)

  • Agenda:
    • Minimum goal of KAGRA readiness issue
      • State Vector definition
        • goal: send K1:DET-DQ_STATE_VECTOR

        • status: Done.
      • DQSEGDB capability
        • goal: send OBSERVATION segment
        • status: 95%
          • Automation should be done. (will be done by Robert)
      • Web page preparation
      • DQ event validation
        • under discussion
          • Probably we cannot provide so many veto segments.
            So at least one (hopefully a few) simple segments will be provided and uploaded.
            (e.g. Omicron triggered segments, Earthquake segments, etc.)

      • GraceDB issue
        • under discussion
          • Full(?) access to GraceDB is opened for KAGRA people.
            Developing/importing GraceDB API tools is better to be done with DET and DAWG.

20200109 (Thu.)

  • Agenda:
    • KAGRA readiness issue
      • State Vector definition
        • SV is provided on the real-time IFO control model.
        • SV is contained in both raw frames and low-latency frames.
        • SV definition is summarized on Wiki and kept as latest information.

        • Finally it should be summarized as a tech-report.
      • DQSEGDB capability
        • Segment files are provided on the Kamioka and Kashiwa servers.
        • Files will be shared with LV by rsync+ssh method.
        • Accessing gwdet.icrr.u-tokyo.ac.jp from LIGO's DQSEGDB was already successfully.
      • Web page preparation
        • SummaryPage is opened also for remote site people.

        • Contents are being closed to LIGO's SummaryPage contents.

        • TY and Alex are now updating some softwares on k1sum0. So SummaryPage may become unstable next couple of days.

      • DetChar/DQ event validataion
        • We are now planning to provide DQ flags indicating earthquake, loud seismotion, etc. (See Kozakai-san's slide)
        • These information are shared with LV via DQSEGDB.
      • Low-Latency tools and GraceDB issues
        • Some tools used as low-latency ones in LIGO (Omicron, hveto etc.) are available.
        • We are waiting for the update of GraceDB authentication by LIGO.
    • Offline DQ Slides

    • E-run analysis (washimi) Slide

Past meeting

KAGRA/Subgroups/DET/Meeting (last edited 2024-11-01 12:16:19 by HirotakaYuzurihara)