coś nie tak z przeglądaniem idx które nie mają sensu

Open
#32 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
tooling

Research direction

Start by running bpsk_v0.1.12-rx.py with debug enabled and inspect the reported sample indices, especially the index near the end of the samples. Determine the intended handling for entries with no sync sequence or frame; the issue does not define the expected result, so completion requires confirming that behavior before changing code.

Written by the indexing model from the issue text.

Description

bug

sprawdzić przy włączonym debug

Samples at index 26261 is too close to the end of samples to contain a full frame. Skipping.
idx= np.uint32(26261) sync sequence real frame_name= ' frame real' has_sync_sequence= True, has_frame= True
bpsk_v0.1.12-rx.py rx_pluto.samples.has_amp_greater_than_ths=np.True_
Otwieranie w istniejącej sesji przeglądarki.
Otwieranie w istniejącej sesji przeglądarki.
Otwieranie w istniejącej sesji przeglądarki.
Before CFO: 0.13 ms.
Before CFO: 0.05 ms.
idx= np.uint32(22) has_sync_sequence= True, has_frame= True
Before CFO: 0.05 ms.
Before CFO: 0.05 ms.
idx= np.uint32(23) has_sync_sequence= True, has_frame= True
idx= np.uint32(191) has_sync_sequence= False, has_frame= False
idx= np.uint32(329) has_sync_sequence= False, has_frame= False
idx= np.uint32(345) has_sync_sequence= False, has_frame= False
idx= np.uint32(361) has_sync_sequence= False, has_frame= False
idx= np.uint32(633) has_sync_sequence= False, has_frame= False
idx= np.uint32(649) has_sync_sequence= False, has_frame= False
idx= np.uint32(953) has_sync_sequence= False, has_frame= False
idx= np.uint32(969) has_sync_sequence= False, has_frame= False

Dominant language
Python
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

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.

More from yabool2001/temp

All issues in yabool2001/temp

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.