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

pyHAMS is now conda-installable! #31

Merged
merged 12 commits into from
Sep 8, 2023
Merged

Conversation

gbarter
Copy link
Contributor

@gbarter gbarter commented Aug 1, 2023

Good news! The pyHAMS extension of HAMS is now conda installable!

The only change to the source code required to make this possible was changing calls from atan2d() to atan2()*180/pi. This is because the windows gfortran compiler available in Anacoda is very old (~v5.3) and doesn't support some of the newer library functions. Credit to Yingyi that the simple atan2d change was the only one needed to support this old windows gfortran compiler.

@YingyiLiu
Copy link
Owner

YingyiLiu commented Sep 5, 2023

Dear Garrett,

Thank you for your great effort. Your decent work is very much appreciated.

By the way, I'm really sorry for my late response due to the summer vacation. Now I see three options to merge the pull request: 1. Create a merge commit; 2. Squash and merge; 3. Rebase and merge. But the third option seems not to work any more since the message says "This branch cannot be rebased due to conflicts". So which one of the other two do you recommend me to choose? Your suggestion will be helpful to me. Thanks.

Best wishes,
Yingyi

@gbarter
Copy link
Contributor Author

gbarter commented Sep 5, 2023

@YingyiLiu : I see no conflicts on this page and you should see a green merge button. Is this not the case?

@YingyiLiu
Copy link
Owner

YingyiLiu commented Sep 6, 2023

@gbarter I see that the button of "rebase and merge" is in grey and not enabled (see the screenshot here https://share.iii.kyushu-u.ac.jp/public/bEopwLII2ly0hCEXONBhAVe7o-1yaGi7XNhj4H7cbOFZ ). But "Create a merge commit" or "Squash and merge" is enabled. I would like to know which one is best suited to choose.

(Please copy the above link to the web browser since directly clicking seems not to work.)

@gbarter
Copy link
Contributor Author

gbarter commented Sep 6, 2023

I don't understand why my view says "This branch has no conflicts with the base branch" but yours says there are conflicts that need to be resolved. I think the "Create a merge commit" is the standard and recommended approach.

If it helps, here is some Github documentation.

@YingyiLiu
Copy link
Owner

OK, let me choose the "Create a merge commit" approach.

@YingyiLiu YingyiLiu merged commit 1443ae0 into YingyiLiu:master Sep 8, 2023
6 checks passed
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