= Data Release Planning for O4 =

== Deliverables ==

=== Before the Data release ===
 * State vector
 * Segment database

=== During the obs ===
 * SummaryPages service 

=== ??? ===
 * Omicron triggers, hveto
  * We need to discuss what format, what data to release with LIGO-VIRGO
 * Data quality information


== Task List during/after Observation ==
|| Task Name || Note.                                   || Necessary FTE (Expert) || Necessary FTE (Trainee) || Available FTE || Time || Site or Remote || Interfacing with other group? ||
|| Segments  || Analize state vector etc and make segments ||                        ||                         ||             ||      ||                ||                               ||
|| Triggers  || Trigger generation, How long does it take for O3GK? ||                                    ||                         ||             ||      ||                ||                     ||
|| DQ shift  || What are the tasks after obs           ||                                    ||                         ||             ||      ||                ||                     ||

 * Segments
   * Most of segments are provided with short-time enough (~1day) for data release.
     * Check validity: (one day) * (2,3 persons) for 2 weeks data (experience from O3GK (?))
   * How should we do offline segments?
     * Configuration should be decided before starting observing run (e.g. during Engineering run)
     * How long does it take to create a new segment file with the current script? [2 hours / one data => Science segments case]
     * How long do we need to check validity? [xx day / 2 weeks data / 1 segment]
 * Triggers
   * 1 day for 2 weeks data (O3GK C20 case)
   * Data transfer time should be ignored because we should construct omicron environment at Kashiwa.


== DetChar tool list ==
 * SummaryPages
 * Omicron
 * Omega Scan
 * hveto
 * Fscan
 * Line database
 * CAGMON
 * Overflow monitor
 * Nose Budgetter?
 * Pastavi?
 * (ligoDV web?)