Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Warn if Source is outside Harminv frequency range #355

Merged
merged 2 commits into from
Jun 1, 2018
Merged

Warn if Source is outside Harminv frequency range #355

merged 2 commits into from
Jun 1, 2018

Conversation

ChristopherHogan
Copy link
Contributor

@stevengj
Copy link
Collaborator

Not sure why this should be a warning — it is okay (and not uncommon) to have a source over a wider bandwidth than the harminv frequency range.

Maybe there should be a warning if the source bandwidth does not include the harminv bandwidth .

@ChristopherHogan
Copy link
Contributor Author

Fixed.

@stevengj stevengj merged commit 4e0f366 into NanoComp:master Jun 1, 2018
@ChristopherHogan ChristopherHogan deleted the chogan/harminv_freqs branch June 4, 2018 13:08
bencbartlett pushed a commit to bencbartlett/meep that referenced this pull request Sep 9, 2021
* Warn if Source is outside Harminv frequency range

* Do opposite check with Harminv and sources
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants