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

introduce new wfs 2.5D point source time domain driving function #168

Merged
merged 1 commit into from
Jan 20, 2021

Conversation

fs446
Copy link
Member

@fs446 fs446 commented Jan 16, 2021

As we introduced a new 2.5D WFS point source driving function in frequency domain with version 0.5.0 we should do this in time frequency as well for consistency, I'd propose.
Thus, for time domain same idea as for frequency domain: putting the new version into point_25D() (this is the 3D->2.5D Delft approach) and creating point_25d_legacy() that holds the function which was used up to <=0.6.0 (this is the 2D -> 2.5D approach by Rabenstein/Spors).

Furthermore, some minor corrections in the math docstrings for the other time domain WFS functions and some pep8 issues fixed.

I would suggest to create a 0.6.1 minor release to introduce the new feature.

@hagenw
Copy link
Member

hagenw commented Jan 18, 2021

You have to merge #169 first in order to fix the CI error.

@fs446
Copy link
Member Author

fs446 commented Jan 19, 2021

Thanks for fixing things beforehand in #169! This PR is now updated by rebase.

Copy link
Member

@hagenw hagenw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great, thanks for the effort.

@fs446 fs446 merged commit efdda38 into master Jan 20, 2021
@fs446 fs446 deleted the wfs_td_point25d branch January 20, 2021 09:48
@fs446 fs446 restored the wfs_td_point25d branch January 21, 2021 10:46
fs446 pushed a commit that referenced this pull request Jan 21, 2021
@fs446
Copy link
Member Author

fs446 commented Jan 21, 2021

I re-opened this PR to improve and correct some docstring passages and to allow further double check / review. Thanks!

@hagenw
Copy link
Member

hagenw commented Jan 23, 2021

I thik you have to create a bew pull request as you cannot merge here.

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