Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Designed Excitation Biased Towards High Frequencies

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
python

Research direction

Start by obtaining the animation and the referenced dataset at /users/michael/sysID/data/srm_measurement_result_081226.npz, then reproduce the later excitation iterations for the 8th-order model. Compare the frequency coverage across iterations and identify why lower-frequency features are missed; done means the cause is documented and the excitation resolves the reported low-frequency behavior.

Written by the indexing model from the issue text.

Description

For a few realistic measurements I have conducted with a significant source of noise and a wide frequency range (about 2 decades) I have noticed that the designed excitation trends towards high frequency features during later iterations and misses or fails to resolve the lower frequency features. This is for a more complicated model to fit (8th order). I'll provide an animation to evaluate the evolution of the designed excitation over a few iterations as well as the data stored from this run.

I cannot upload my data here however it is stored on the controls computer at: /users/michael/sysID/data/srm_measurement_result_081226.npz

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

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 CaltechExperimentalGravity/system_ident

All issues in CaltechExperimentalGravity/system_ident

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.