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

Return values of make_xxx_pulse functions #47

Closed
schuenke opened this issue Apr 13, 2021 · 11 comments
Closed

Return values of make_xxx_pulse functions #47

schuenke opened this issue Apr 13, 2021 · 11 comments
Assignees
Labels
bug Something isn't working

Comments

@schuenke
Copy link
Collaborator

schuenke commented Apr 13, 2021

Since 7542b39 the make-pulse-functions like make_sinc_pulse.py and make_gauss_pulse.py return a different number of variables as before when using return_gz = False.

For compatibility with previous versions I suggest to return Nones for gz and gzr as it was the case before the release of v1.3.1. However, I think using the _return_gz' flag instead of the try block is a good idea and I suggest to change the return lines only. For example the make_sinc_pulse.py could be modified to:

if return_gz:
    return rf, gz, gzr
else:
    return rf, None, None

This would also solve issue #46

Let me know if I should include this in the PRs for issue #46 and issue #48.

@sravan953 sravan953 self-assigned this Apr 13, 2021
@sravan953 sravan953 added the bug Something isn't working label Apr 13, 2021
@sravan953
Copy link
Collaborator

I guess the return function executes irrespective of the return_gz value, missed this! I will work on this fix, and incorporate your suggested changes, consequently fixing #46.

sravan953 added a commit that referenced this issue Apr 13, 2021
@sravan953
Copy link
Collaborator

Please let me know if pulling from the latest dev commit fixes this issue for you.

sravan953 added a commit that referenced this issue Apr 15, 2021
@sravan953
Copy link
Collaborator

Thanks @schuenke for bearing with me. The latest commits must have fixed this for good!

@schuenke
Copy link
Collaborator Author

Issue is fixed now. Thanks @sravan953 !

@schuenke
Copy link
Collaborator Author

Hey @sravan953,
will you merge this fix and the others from the dev branch into master and create a new release soon?

@sravan953
Copy link
Collaborator

Hi, yes! I commit to publishing a new release by Friday (04/30). Thanks for bearing with me!

@schuenke
Copy link
Collaborator Author

Will this be 1.3.1post1 than? We need to submit the proofs of our paper by tomorrow and I would lile to mention the release.

@sravan953
Copy link
Collaborator

Yes 1.3.1post1

@sravan953
Copy link
Collaborator

@schuenke Hi, published!

@schuenke
Copy link
Collaborator Author

schuenke commented May 3, 2021

Thanks @sravan953 . Will test it tomorrow 👍

@schuenke
Copy link
Collaborator Author

schuenke commented May 6, 2021

Seems to work fine. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants