simonsobs / simonsobs/sotodlib

Frequency Cutoff error in preprocessing?

Open
#1,735 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
19
Forks
23
Avg merge
1d 5h
Merged PRs (30d)
14

Description

I'm seeing a bunch of observations raising errors that look like this:

1788491409.0804863, obs_1763234806_satp1_1111111, ['ws6', 'f090'], init_pipeline_run_error
        <class 'ValueError'>: lower freq=1 >= upper freq=0.8388319434722693  File "/global/homes/k/kmharrin/.local/soconda/20260812_0.2.5/lib/python3.13/site-packages/sotodlib
/preprocess/preprocess_util.py", line 1449, in preproc_or_load_group
    proc_aman, success = pipe_init.run(aman)
                         ~~~~~~~~~~~~~^^^^^^
  File "/global/homes/k/kmharrin/.local/soconda/20260812_0.2.5/lib/python3.13/site-packages/sotodlib/preprocess/pcore.py", line 567, in run
    aman, proc_aman = process.calc_and_save(aman, proc_aman)
                      ~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^
  File "/global/homes/k/kmharrin/.local/soconda/20260812_0.2.5/lib/python3.13/site-packages/sotodlib/preprocess/processes.py", line 818, in calc_and_save
    wn_f_high = check_frequency_cutoff(wn_f_low, wn_f_high)
  File "/global/homes/k/kmharrin/.local/soconda/20260812_0.2.5/lib/python3.13/site-packages/sotodlib/preprocess/processes.py", line 792, in check_frequency_cutoff
    raise ValueError(f"lower freq={fmin} >= upper freq={fmax}")

What does this mean?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in sotodlib/preprocess/processes.py at check_frequency_cutoff and calc_and_save, then trace the call through pcore.py and the reported preprocessing run. Reproduce the failure with the relevant preprocessing configuration and determine why the frequency bounds are invalid. Done means the cause and expected handling are established, with a focused regression test or documented resolution.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
data-engineering
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.