Running deepclean of MDC (pseudo) replay at LHO
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 10
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
We set up a pseudo replay of 1-second-long MDC frames at LHO and LLO.
The scripts to make the replay are here:
https://git.ligo.org/muhammed.saleem/deepclean/-/tree/master/pseudo_replay/codes
also at the LHO path:
/home/muhammed.saleem/deepClean/deepclean/pseudo_replay/codes
Path to MDC replay that was used for the validation studies.
The new replay is at LHO:
/home/deep.clean/O4-tests/MDC/pseudo-replay/
The cleaned frames (from deepclean) will be written to a directory:
/some/directory/
The offline-deepclean results from the same segments are here (if we want to compare the results)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the pseudo_replay/codes scripts in the linked repository or /home/muhammed.saleem/deepClean/deepclean/pseudo_replay/codes, then inspect the replay frames under /home/deep.clean/O4-tests/MDC/pseudo-replay/. The issue does not specify the command to run, the output directory, comparison procedure, or acceptance criteria, so the expected completed result needs clarification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100