Electronic format about gzcandels_datapaper HOT 18 OPEN

Also this brings up another issue...

from gzcandels_datapaper.

I say data.galaxyzoo.org and VizieR/CDS at a minimum so that people can match to other tables via a cone search.

from gzcandels_datapaper.

Agreed.

On Thu, Apr 14, 2016, 20:32 Brooke Simmons [email protected] wrote:

I say data.galaxyzoo.org and VizieR/CDS at a minimum so that people can
match to other tables via a cone search.

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#30 (comment)

from gzcandels_datapaper.

I really want to close this because I want that milestone to be met but then again we won't have the final versions of tables until publication, right?

from gzcandels_datapaper.

Can split it into sub-issues for each type, if you want

On Mon, Apr 25, 2016, 11:16 Brooke Simmons [email protected] wrote:

I really want to close this because I want that milestone to be met but
then again we won't have the final versions of tables until publication,
right?

—
You are receiving this because you were assigned.

Reply to this email directly or view it on GitHub
#30 (comment)

from gzcandels_datapaper.

yesssss

from gzcandels_datapaper.

data.galaxyzoo.org is ready to be deployed (zooniverse/data.galaxyzoo.org@7ae72d6) whenever the paper is accepted.

from gzcandels_datapaper.

I updated the data.galaxyzoo.org repo (zooniverse/data.galaxyzoo.org@85d21e6 and a few commits before that) to account for the changes made in the resubmission, and also updated the files available on AWS.

I added the commits to the hubble branch as it seemed like that may have been more updated than the candels branch? Hope that was the right thing...

from gzcandels_datapaper.

Awesome - I'm really sorry I didn't tackle it myself last week.

Yeah - the hubble and candels branches are diverging somewhat, but I
think they have fairly parallel changes and should be eventually merged
without difficulty. Only the master branch is actually deployed live to the
site, which we said we were waiting on until the papers are accepted or
posted to arXiv. Just give me a shout when you're ready for that.

On Sun, Aug 14, 2016 at 11:03 PM Brooke Simmons [email protected]
wrote:

I updated the data.galaxyzoo.org repo (zooniverse/data.galaxyzoo.org@
85d21e6
zooniverse/data.galaxyzoo.org@85d21e6
and a few commits before that) to account for the changes made in the
resubmission, and also updated the files available on AWS.

I added the commits to the hubble branch as it seemed like that may have
been more updated than the candels branch? Hope that was the right thing...

—
You are receiving this because you were assigned.

Reply to this email directly, view it on GitHub
#30 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACLha-nDQAqbskyaKSqm6JtPKlMf4OHsks5qf9cOgaJpZM4G3wS0
.

from gzcandels_datapaper.

I'd be happy to make it public now (without advertising it yet), if @chrislintott and @karenlmasters approve...

from gzcandels_datapaper.

Update: actually it would be really great to publish this soon as there's a CANDELS meeting next week and they'd like an update on the catalog, so this seems like the easiest way.

from gzcandels_datapaper.

That's fine by me. I suspect few people will notice, as I don't know how
regularly the site is visited (I don't know that we have Google Analytics
or anything similar implemented for data.galaxyzoo.org, actually).

I'd rather hold off on adding the GZ Hubble data yet, though, as Mel and I
aren't 100% complete yet. I think it would have been more appropriate to
put these changes in the candels branch after all.

Do you know if there's a git way that we can peel off your last five
commits and attach them to candels instead of hubble? Undoing the
hubble branch is easy (just a revert), but I want to know if there's a
way we could reapply them to the candels branch and then merge that with
master.

Maybe the devs can help us out if neither of us know off the top of our
head.

On Mon, Aug 15, 2016 at 7:27 PM Brooke Simmons [email protected]
wrote:

Update: actually it would be really great to publish this soon as there's
a CANDELS meeting next week and they'd like an update on the catalog, so
this seems like the easiest way.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
#30 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACLha-LRpoWBxHaNOoODuhhxCHFw-6qhks5qgPXbgaJpZM4G3wS0
.

from gzcandels_datapaper.

Fine by me too.

On Tue, Aug 16, 2016 at 4:45 PM, Kyle Willett [email protected]
wrote:

That's fine by me. I suspect few people will notice, as I don't know how
regularly the site is visited (I don't know that we have Google Analytics
or anything similar implemented for data.galaxyzoo.org, actually).

I'd rather hold off on adding the GZ Hubble data yet, though, as Mel and I
aren't 100% complete yet. I think it would have been more appropriate to
put these changes in the candels branch after all.

Do you know if there's a git way that we can peel off your last five
commits and attach them to candels instead of hubble? Undoing the
hubble branch is easy (just a revert), but I want to know if there's a
way we could reapply them to the candels branch and then merge that with
master.

Maybe the devs can help us out if neither of us know off the top of our
head.

On Mon, Aug 15, 2016 at 7:27 PM Brooke Simmons [email protected]
wrote:

Update: actually it would be really great to publish this soon as there's
a CANDELS meeting next week and they'd like an update on the catalog, so
this seems like the easiest way.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#30
issuecomment-239959303>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACLha-
LRpoWBxHaNOoODuhhxCHFw-6qhks5qgPXbgaJpZM4G3wS0>

.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#30 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AD7wBdgy5q5vGDEdSt9UUnawteBIvUopks5qgdsFgaJpZM4G3wS0
.

from gzcandels_datapaper.

Okay, thanks to @srallen and git cherry-pick, I've moved the commits over to the candels branch and rewound the hubble branch.

from gzcandels_datapaper.

Awesome sauce. Thanks for the help, @srallen.

Looks like merge into master from this branch will be painless, so feel
free to do so whenever you're ready. Instructions on actually deploying are
in the README.md file; let me know if you have any issues with that
(versions of node or keys can be weird). I can try if it doesn't work for
you, @vrooje.

On Tue, Aug 16, 2016 at 3:52 PM Brooke Simmons [email protected]
wrote:

Okay, thanks to @srallen https://github.com/srallen and git cherry-pick,
I've moved the commits over to the candels branch and rewound the hubble
branch.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
#30 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACLhaxFucAN8PmATOsKaTiiaWnIO_v4Mks5qghT3gaJpZM4G3wS0
.

from gzcandels_datapaper.

Great, merged -- but I don't have node and also my key is now only stored in one program in encrypted form and I don't actually know what it is! If you wouldn't mind trying the deploy that would be fantastic... thanks.

from gzcandels_datapaper.

Tried, but my AWS keys no longer work - I suspect @astopy rightly discontinued them. :(

Looks like we'll have to ask a dev to help (@srallen?) or else get node installed on your machine.

from gzcandels_datapaper.

Okay turns out the secret key was also in my keychain and node + nvm aren't that hard to install.

Done.

from gzcandels_datapaper.