This repository has been archived by the owner on May 13, 2020. It is now read-only.
0.7 release #306
Merged
0.7 release #306
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Plotting was not done on an axis, meaning that the plotting crashed
Merging master release 0.6 back into develop, these are commits we found while testing the develop branch
no need sudo inside the script
stable basemap vesion
Enhancement acf plot input check
Fixed the scatter part of fan
Exposed the resolution of the latitude
Xueling updated the python_install_mac_port.sh and plotMapGrd.py.
…ached Bugfix hdw.dat server not reached
Removed unnecessary plotCoords variable that caused bug.
The comma should be a decimal point.
Fix Typo in Geopack
|
I think we should merge in AACGM v2 ( #303 ) to this, lest we suffer the wrath of Simon at the workshop. |
|
What I said on #303. If Simon has some wrath, then point him to the develop branch which we should be the first merge off the bat after the new master is released. |
|
Hey all, are we set for a new davitpy release tomorrow? Looks like we've got a merge conflict with the mac port install script. Maybe @Shirling-VT, or @aburrell can point out whether the release or the master branch is right here? |
|
I never use the install script, it messes with my system :P
Also, did anyone test this at all?
…-----Original Message-----
From: "Kevin Sterne" <notifications@github.com>
Sent: 31/05/2017 22:03
To: "vtsuperdarn/davitpy" <davitpy@noreply.github.com>
Cc: "Angeline Burrell" <urania.shopper@gmail.com>; "Mention" <mention@noreply.github.com>
Subject: Re: [vtsuperdarn/davitpy] 0.7 release (#306)
Hey all, are we set for a new davitpy release tomorrow? Looks like we've got a merge conflict with the mac port install script. Maybe @Shirling-VT, or @aburrell can point out whether the release or the master branch is right here?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
Yes, I tested it early this year. The release branch is the right way of
installing basemap.
…On Wed, May 31, 2017 at 5:09 PM, Angeline Burrell ***@***.***> wrote:
I never use the install script, it messes with my system :P
Also, did anyone test this at all?
-----Original Message-----
From: "Kevin Sterne" ***@***.***>
Sent: 31/05/2017 22:03
To: "vtsuperdarn/davitpy" ***@***.***>
Cc: "Angeline Burrell" ***@***.***>; "Mention" <
***@***.***>
Subject: Re: [vtsuperdarn/davitpy] 0.7 release (#306)
Hey all, are we set for a new davitpy release tomorrow? Looks like we've
got a merge conflict with the mac port install script. Maybe @Shirling-VT,
or @aburrell can point out whether the release or the master branch is
right here?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#306 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AIEZK_amSLuVf9B2vgWuf_Z-0CDzZb5vks5r_db-gaJpZM4NK70Z>
.
--
Best wishes,
Xueling
|
|
Thank you @Shirling-VT! I'm fairly Mac illiterate, so I needed someone to give some guidance here. I'll work on resolving the merge conflict and then getting the new release out in the morning of eastern USA. I think the release notes here will be somewhat small/short. |
|
I think just replace those in the master branch:
cd basemap
python2.7 setup.py install
with those in the release branch:
cd basemap/geos-3.3.3
export GEOS_DIR=/usr/local/geos
./configure --prefix=$GEOS_DIR
make
make install
cd ..
python setup.py install
This is more a basemap installation issue when I first found it at #236. We
fixed it in the debian dependence installation script by #245 but didn't in
the mac script. This is why I included it here during this release. I'm
sorry I didn't explain it well earlier.
…On Wed, May 31, 2017 at 11:07 PM, Kevin Sterne ***@***.***> wrote:
Thank you @Shirling-VT <https://github.com/shirling-vt>! I'm fairly Mac
illiterate, so I needed someone to give some guidance here. I'll work on
resolving the merge conflict and then getting the new release out in the
morning of eastern USA. I think the release notes here will be somewhat
small/short.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#306 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AIEZK3OVO7hSM_PLpO_cMPkkQAa39mPMks5r_irtgaJpZM4NK70Z>
.
--
Best wishes,
Xueling
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've created the release branch as of a few minutes ago, so it includes the typo hotfix as the last part here. I don't think there's any big goals for this release, but test this out thoroughly (use this branch instead of develop). Looks like there's a few merge conflicts that we'll need to sort out. Otherwise I'll merge this branch on June 1st.