-
Notifications
You must be signed in to change notification settings - Fork 51
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
Conversation
… interface library to avoid confusion with HAMS as a dynamic, shared library
… conda fortran compilers
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, |
@YingyiLiu : I see no conflicts on this page and you should see a green merge button. Is this not the case? |
@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.) |
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. |
OK, let me choose the "Create a merge commit" approach. |
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()
toatan2()*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 simpleatan2d
change was the only one needed to support this old windows gfortran compiler.