Python in Astronomy 2015: Day 1 Tweets
20 Apr 2015Python in Astronomy 2015 is going on this week and I’m not there (boo, though that did give me time today to release a project of mine). But, lots of participants are kindly tweeting under the hashtag #pyastro15. I was watching the twitter stream when I could during the day and grabbed the tweets that I found most interesting. View the following as a glimpse into my OmniFocus Personal-Tech-Advancement list of things I want to look into and/or things I know now but may forget and want to be able to re-locate easily in the future. And, things I found interesting or important. And, maybe, a few tweets that made me laugh or that otherwise caught my eye. And, no, really, this is only a small sample of the tweets that came out from #pyastro15 today.
Thanks everyone at #pyastro15! Keep up the good tweeting tomorrow.
These flash intros at #pyastro15 are amazing!! Quite challenging to summarise everything in 1min, but really fun to do and listen to.
— Antonio M. Carrillo (@antmarcarr) April 20, 2015
1 min intros at #pyastro15 are great, very good to see names with all the faces right away and learn interesting random bits about them
— Erik Tollerud (@eteq) April 20, 2015
(The flash intros seem to have been quite a hit, though went so fast that not many people tweeted them.)
Since there seems to be strong interest in FITS alternatives I'm just going to leave this here http://t.co/BhYAIqgZfJ #pyastro15
— Erik (@Iguananaut) April 20, 2015
Wow! FORTRAN77 got more wuuw than IDL! #pyastro15
— DVD (@DVDGC13) April 20, 2015
(Hey, I still have a soft spot for F77. I did a lot of coding in F77 in the day. And, F90 was a major revelation when I started using it.)
#pyastro15 Google doc for collecting interest and ideas for fostering the community of #python users in Astro: https://t.co/GX9wuKHeD0
— Kelle Cruz (@kellecruz) April 20, 2015
“As astronomers we have the privilege of hanging out with astronomers. It could be worse, they could be physicists.” @kellecruz #pyastro15
— Edward Gomez (@zemogle) April 20, 2015
“My dream job was not an advertised position” @kellecruz on building your niche rather than finding it. #pyastro15
— Matt Mechtley (@biphenyl) April 20, 2015
. @kellecruz points out that being part of "the establishment" can be helpful for making change. Introduces @AstronomyAllies. #pyastro15
— Pauline Barmby (@PBarmby) April 20, 2015
shared vision from @kellecruz -- "programming and software dev skills & contributions are valued and rewarded" yes yes yes #pyastro15
— Alex Hagen (@astrophysicalex) April 20, 2015
An important aspect of the meeting @kellecruz highlights is the code of conduct #pyastro15 http://t.co/YgSN6Xqe6i
— Steven Crawford (@astrocrawford) April 20, 2015
"we want to make it a societal norm that people know how to comment code" wisdom from @kellecruz #pyastro15
— Alex Hagen (@astrophysicalex) April 20, 2015
.@kellecruz starts out with a list of what she thinks of as "shared values" - I think we mostly agree at #pyastro15 pic.twitter.com/k8DDtvqvmS
— Erik Tollerud (@eteq) April 20, 2015
Shared vision by @kellecruz 1. students given time and resources to learn fundamental coding skills #pyastro15
— Haley Gomez (@astrofairy) April 20, 2015
shared vision 2. critical mass astronomers implement coding practice and reproducibility (code sharing) @kellecruz #pyastro15
— Haley Gomez (@astrofairy) April 20, 2015
#pyastro15 @kellecruz advocating changing the astro community by stealth and guile
— Joe Zuntz (@joezuntz) April 20, 2015
. @kellecruz points out that jr people in room "won't be junior forever." I'll tell you, it's a surprise to realize you're not #pyastro15
— Pauline Barmby (@PBarmby) April 20, 2015
(um, yeah, um. Realizing that not only do I turn a big round number this summer, but this summer I’ll have been in my tenure-track/tenured job longer than I was a grad-student/post-doc combined. I’m middle-something’d by now.)
#pyastro15 nobody tweet the thing @kellecruz just said! Might make us all look a bit crazy!
— Joe Zuntz (@joezuntz) April 20, 2015
(I never figured out what this referred to and remain curious…)
don't ask what the #pyastro15 community can do for you, ask what you can do for the #pyastro15 community @kellecruz
— Alex Hagen (@astrophysicalex) April 20, 2015
@astrophysicalex a wise man (@jonathansick) said to me "you can do anything but you can't do everything." Good advice #pyastro15
— Pauline Barmby (@PBarmby) April 20, 2015
(A colleague of mine puts it less elegantly as “You may think you’re having your cake and eating it too, but you’re just getting crumbs all over yourself.” Focus and limiting projects is hard. There are so many exciting things out there to work on.)
(BTW: as a point of personal preference, I’m not on Facebook and not repeating any tweets that refer to it.)
“@DVDGC13 Do the people know some of us are in IRC at the #pyastro15 channel too??” Come join us on http://t.co/zz22rEa2iD.
— Stuart Mumford (@StuartMumford) April 20, 2015
(I’m watching the IRC with gitter; I’ve only been using it for a day so far, so no endorsements from me yet, but it seems good at first look.)
“Need a commitment from astronomy python community not to be jerks on StackOverflow” @kellecruz #pyastro15
— Edward Gomez (@zemogle) April 20, 2015
(Not just on stackoverflow, but everywhere, ok? Please? I’ve heard of some awful things recently. Let’s lead by example.)
http://t.co/iZX0tzJlvm is going to be the central location for people to find python resources #pyastro15
— Haley Gomez (@astrofairy) April 20, 2015
“Start calling ‘hack’ days, ‘maker’ day, to make them less intimidating” @kellecruz #pyastro15 . Hacking ≠ coding http://t.co/ahHeH6veTl
— Edward Gomez (@zemogle) April 20, 2015
@astrophysicalex something like this for astronomy? http://t.co/SPWcB06Y57 #pyastro15
— DVD (@DVDGC13) April 20, 2015
Re: @kellecruz's modular lesson idea: you could try @swcarpentry's lesson template repo on @github: https://t.co/nwRFsrhjXl #pyastro15
— Pauline Barmby (@PBarmby) April 20, 2015
@zemogle @kellecruz #pyastro15 I also like "sprint" days instead of "hack" days.
— Curtis McCully (@curtis_mccully) April 20, 2015
#pyastro15 already-Git users might find this amusing: http://t.co/IQHFHNH9fe
— Pauline Barmby (@PBarmby) April 20, 2015
This doc is now *editable*. “@kellecruz: #pyastro15 …for collecting interest & ideas for fostering the community: https://t.co/GX9wuKHeD0”
— Kelle Cruz (@kellecruz) April 20, 2015
The exercises that I've just mentioned at #pyastrolocal in #pyastro15 https://t.co/Ic2jXXvyMt
— DVD (@DVDGC13) April 20, 2015
Notes on #pyastro15 observation planning and scheduling: https://t.co/tX4QbeNlM7
— Christoph Deil (@ChristophDeil) April 20, 2015
Here are today's unconference sessions at #pyastro15. pic.twitter.com/iZzWZVWzUE
— Geert Barentsen (@GeertHub) April 20, 2015
LCOGT updates their schedule every 15 minutes with a completely new schedule #pyobservatory #pyastro15
— Steven Crawford (@astrocrawford) April 20, 2015
Messed up your git? Some suggestions for fixing it: http://t.co/Lx7oQ3K132 #pyastro15
— Ricarda Beckmann (@RicardaBeckmann) April 20, 2015
some #pyastro15 folks were talking about FITS. here's a paper on FITS' limitations -- http://t.co/ni2QwQIiuw
— Alex Hagen (@astrophysicalex) April 20, 2015
Today's tasks:
- obsessively follow #pyastro15
- resist urge to favorite every tweet
— Henry Roe (@_hroe) April 20, 2015
(how true, how true. Wait, that was me.)
we want user groups that transcendent python -- include best practices, general coding, etc. -- @kellecruz #pyastro15 #pyastrolocal
— Alex Hagen (@astrophysicalex) April 20, 2015
Little Dutch waffle cookies at #pyastro15 coffee break!!! pic.twitter.com/QXI3CEW6L8
— Alex Hagen (@astrophysicalex) April 20, 2015
(bad enough I’m jealous of everyone at #pyastro15 because of the content and colleagues in attendance. now food too!??!)
Notes on #pyastro15 #specutils session: http://t.co/iz4f64bHWC #pyastrospec
— Brigitta Sipocz (@AstroBrigi) April 20, 2015
Helpful Git commands cheat sheet: http://t.co/jFqqa5efp9 #pyastro15
— Pauline Barmby (@PBarmby) April 20, 2015
important note of importance from @biphenyl --> always always always explicitly state your priors. you are always using a prior #pyastro15
— Alex Hagen (@astrophysicalex) April 20, 2015
#pyastro15 Here are some very brief links from our MCMC session - participants please feel free to edit/add! https://t.co/DlP1IRJqVK
— Joe Zuntz (@joezuntz) April 20, 2015
Missed the #pyastro15 git intro or want to review? Notes here: http://t.co/8Rz4t4hETU
— Pauline Barmby (@PBarmby) April 20, 2015
. @zemogle explains how to get an academic @github account (5 private repos) @astrofrog notes that acad GH orgs can get 20 such. #pyastro15
— Pauline Barmby (@PBarmby) April 20, 2015
(my request is now submitted)
@RicardaBeckmann There *is* a sheep outside my window! Not sure how I missed it #pyastro15
— Joe Zuntz (@joezuntz) April 20, 2015
@joezuntz Once you see it, you can't unsee it ;) #thesheepisamazing #pyastro15
— Ricarda Beckmann (@RicardaBeckmann) April 20, 2015
Also, Pauline Barmby delayed getting a much needed beer to write up a blog post regarding Day 1:
New blog post: Python in Astornomy, day 1. #pyastro15
http://t.co/Jo6u78Cabt
(tomorrow I’ll fix the spelling)
— Pauline Barmby (@PBarmby) April 20, 2015
Looking forward to another good day tomorrow! Keep the tweets coming.