|
Size: 1336
Comment:
|
Size: 1858
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 24: | Line 24: |
| * 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? [xx day / 2 week data] * How long do we need to check validity? [xx day / 2 weeks data / 1 segment] |
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? [xx day / 2 week data]
- How long do we need to check validity? [xx day / 2 weeks data / 1 segment]
- Most of segments are provided with short-time enough (~1day) for data release.
DetChar tool list
- Omicron
- Omega Scan
- hveto
- Fscan
- Line database
- CAGMON
- Overflow monitor
- Nose Budgetter?
- Pastavi?
- (ligoDV web?)