ASCL News
-
Judy Schmidt, our designer/developer, and I have a new paper, "Looking before Leaping: Creating a Software Registry," in the Journal of Open Research Software. The article is open access and can be found here: http://doi.org/10.5334/jors.bv
When I started work on the ASCL in 2010, I wanted to understand why the original ASCL -- started in 1999 -- and other previous similar resources had not reached critical mass. I looked at these resources, what they offered, and how they were structured, and for some of them, talked with the people who had started them, to see what I could learn from their experiences. In addition, Robert Nemiroff and I have had many conversations about the early days of the ASCL, and I also talked with researchers who used some of these services. The lessons from this look back has informed our work on the ASCL. My background in change management has also been helpful in determining the ASCL's path forward. In the paper, we share not only some of what was learned, but also specific steps we've taken, why we've taken them, how the ASCL has changed over time, and some of our future plans.
The first version of this paper was accepted for the 2nd Workshop on Sustainable Software for Science: Practice and Experiences (WSSSPE2), which took place in New Orleans in November 2014, and was later revised for publication.
WSSSPE2 blog post
3rd Workshop on Sustainable Software for Science: Practice and Experiences -
On Tuesday, October 27, the ASCL held a Birds of a Feather session at ADASS on Improving Software Citation and Credit. The session was opened with a brief presentation by Bruce Berriman, who reported on a Software Publishing Special Interest Group meeting held at the January 2015 AAS meeting and the ongoing work that has come out of that. I followed with a quick overview of other efforts to improve software credit and citation, not just in astronomy but across disciplines, after which Keith Shortridge moderated a lively discussion among the forty people present. The slides Bruce and I presented are now available online.
Previously, we shared resources for the session and the Google doc created during the session to capture some of the main points from the discussion.
-
The ASCL has organized a Birds of a Feather session (BoF) at ADASS to discuss improving software citation and credit to be held on Tuesday, October 27; the following links may be helpful for the discussion.
Astronomy-specific
Astronomy software citation examples and ideas (working [Google] document arising from AAS SPSIG discussion)Astronomy software indexing workshop
Cross-disciplinary
Workshop on Sustainable Software for Science: Practice and Experiences (WSSSPE)
Force11 Software Citation Working Group (Mission statement, member list, timeline, communications plan, etc. on GitHub)Center for Open Science's Transparency and Openness Promotion (TOP) Guidelines
Google doc created during the BoF session; anyone with the link can comment.
-
The ASCL is at .Astronomy ("dot astronomy"), which officially starts tomorrow morning. Three days of unconference, discussion, sessions, hacking, ideas, collaborating, fun, cool buttons, and, rumor has it, Belgian chocolate, in the magnificent city of Chicago. Follow along on Twitter, hashtag #dotastro!
-
I'm delighted to offer the following guest post by Jonathan Petters, Data Management Consultant, Johns Hopkins Data Management Services, and thank him very much for it!
In a recent discussion on preservation and sharing of research data, a few participants expressed their concern (paraphrased here) that “My research community doesn't know how to create a quality data management plan” and “We don't know how to evaluate data management plans.” The astronomy community explicitly requested a little guidance. We in Johns Hopkins University Data Management Services have developed a few resources, described below, of use in both developing and evaluating data management plans within all research disciplines, including astronomy.Funding agencies have long encouraged and expected that data and code used in the course of funded research be made available to those in the research discipline. NSF is an important funder of astronomical research that has such expectations (and the agency I will focus on here). A few years ago NSF began requiring data management plans as part of research proposal, in part to aid in the dissemination and sharing of research data and code. Following a February 2013 Office of Science and Technology Policy memo other US funding agencies are expected to follow suit with similar data management plan requirements, including the Department of Energy's Office of Science.
What does NSF say about writing and evaluating quality data management plans? A good overview of NSF data policies relevant for the AST community can be found in these slides from Daniel Katz, NSF). In general the National Science Foundation (NSF) states that data management will be defined by “the communities of interest.” The NSF AST-specific policy further states “MPS Divisions will rely heavily on the merit review process in this initial phase to determine those types of plan that best serve each community and update the information accordingly.” Neither statement is especially prescriptive and can leave researchers unclear as to what they should do.
Creating a plan
While effective research data management certainly has community- and discipline-specific attributes, there ARE aspects of effective data management that are generalizable across research disciplines. It is around these general aspects that we in Johns Hopkins University Data Management Services (JHUDMS) devised our Data Management Planning Questionnaire. We work through this questionnaire with researchers at Johns Hopkins to help them create effective data management plans.The Questionnaire is designed to comprehensively hit upon the important aspects of effective research data management (e.g. data inputs/outputs in the research, ethical/legal compliance, standards and formats used, intended sharing and preservation, PI restrictions on the use of the data). By answering the applicable questions in the document, removing the questions/front matter and connecting the answers in each section into paragraphs, a researcher would be well on their way to a quality, well thought-out data management plan.
Two relevant side-notes:
1.) For the Questionnaire we consider code and software tools as one 'kind' of research data; thus analysis or simulation codes used in the course of your proposed research should be included as a Data Product. While research code and research data generated or processed by code are clearly NOT the same, there are many similarities in managing the two. In both cases effective management should include consideration of documentation, licensing, formats, associated metadata, and upon what platform(s) the data or code could be shared.2.) Astronomy, as in other disciplines, conducts a substantial amount of research through large collaborations (e.g. surrounding HST or SDSS data). In these cases it is typical for investments in research data infrastructure to be made, and data policies/practices to be defined for those working with the data. Citing those policies and practices in a data management plan would be appropriate.
Evaluating a plan
To help researchers evaluate data management plans for their quality, my colleagues developed the Reviewer Guide and Worksheet for Data Management Plans (dotx). This Guide and Worksheet is a complement to our Questionnaire; it is a handy checklist by which a grant reviewer can determine whether a researcher thoroughly considered the important aspects of research data management.For those who researchers saying to themselves, “The Questionnaire and Reviewer Guide are nice, but PLEASE just tell me what to do!!!”, I found two tweets from the code sharing session at the latest (223rd) AAS meeting in January to be quite relevant (h/t August Muench and Lucianne Walkowicz):
I wholeheartedly agree with both tweets. It is up to the research community members to police and enforce the data management and sharing practices they would like to see in their community. That’s how peer review works! So the next time you review astronomical research proposals, look over the data management plans carefully and bring up relevant thoughts and concerns to the review panel.
Summing up
I hope the Data Management Planning Questionnaire and Reviewer Guide and Worksheet for Data Management Plans help you and other researchers in the astronomy community more fully develop expectations for data management and sharing practices. It’s likely your institution also has research data management personnel (like the JHUDMS at Hopkins) who are more than happy to help! -
Mozilla Science Lab, GitHub and Figshare team up to fix the citation of code in academia
The Mozilla Science Lab, GitHub and Figshare – a repository where academics can upload, share and cite their research materials – is starting to tackle the problem. The trio have developed a system so researchers can easily sync their GitHub releases with a Figshare account. It creates a Digital Object Identifier (DOI) automatically, which can then be referenced and checked by other people.Discussion of the above article on YCombinator
...it always make me cringe when privately held companies want to define an "open standard" for scientific citations that (surprise!) relies completely on their proprietary infrastructure. I still remember the case of Mendeley, which promised to build an open repository for research documents, and which is now a subsidiary of Elsevier, an organization that does not really embrace "open science", to put it mildly.Tool developed at CERN makes software citation easier
Researchers working at CERN have developed a tool that allows source code from the popular software development site GitHub to be preserved and cited through the CERN-hosted online repository Zenodo....
Now, people working on software in GitHub will be able to ensure that their code is not only preserved through Zenodo, but is also provided with a unique digital object identifier (DOI), just like an academic paper.Webcite
WebCite is an on-demand archiving system for webreferences (cited webpages and websites, or other kinds of Internet-accessible digital objects), which can be used by authors, editors, and publishers of scholarly papers and books, to ensure that cited webmaterial will remain available to readers in the future.DOIs unambiguously and persistently identify published, trustworthy, citable online scholarly literature. Right?
So DOIs unambiguously and persistently identify published, trustworthy, citable online scholarly literature. Right? Wrong.
The examples above are useful because they help elucidate some misconceptions about the DOI itself, the nature of the DOI registration agencies and, in particular issues being raised by new RAs and new DOI allocation models. -
The ASCL has 779 codes in it now, some of which date back to the 1990s. With the speed at which both the web and code authors (often grad students or post docs) move, links to some code sites are bound to go bad over time. We use a checker regularly to test links to ensure we're not pointing to dead links; when we do find a broken link (defined as one we haven't been able to reach for at least 2 weeks), we look for a new one and, if that doesn't work, email the code author(s) to ask where the code has moved.
We can't always find a good link, and code authors sometimes don't reply to our emails. Currently, eight codes -- 1% of our entries -- have bad links. Of these, for half of them we either cannot find the code author or the code author has not replied to numerous emails.
What else can we do?
I assume that some code authors forget their codes. Having moved on perhaps to another institution and other work, they do not have time nor incentive to create a new web home for a code they wrote some years ago. That's understandable, but then the code, a unique solution to a problem, an artifact of astrophysics research, a method used in research, is lost.
We'd like to save the codes (Save the Codes! I may have to put that on glow-in-the-dark pencils); here are a few ideas for authors who no longer want to maintain a site for their codes:
- Send an archive file of the code to the ASCL. We can house it, as we do for CHIWEI.
- Post the code in an online repostitory such as GitHub, SourceForge,
Code.Google, or Bitbucket if you would like the code to be open source and are open to others continuing its development, or on a site such as Figshare or Zenodo to simply make it available. - Create a Research Compendium for your paper, data, and code on Research Compendia, or a companion website for your research on RunMyCode and load the code and data for your research there.
- Ask your institutional library to house it; many institutions have repositories for storing the digital artifacts of academia and research.
I don't know about option 4, but options 1-3 should take 15 minutes or less. Surely a code is worth that little bit of extra time to make it available to others even if you don't want to be bothered with it anymore.
Please save your code; don't let it go bad!
-
"...some of the greatest artifacts of the [astronomy] community’s creative problem-solving are at risk of being lost."
I believe this; a good thing, since this is what Peter Teuben and I wrote in We didn’t see this coming: Our unexpected roles as software archivists and what we learned at Preserving.exe, one of three participant reports in "Preserving.exe: Toward a National Strategy for Software Preservation."
This report arose from a summit held at the Library of Congress on May 20-21, 2013 by the National Digital Information Infrastructure and Preservation Program. Our piece discusses the summit itself, some of what we learned there, and its impact on the way we think about the ASCL and our work. Among the ideas raised at the summit was that of software as a cultural artifact. We wrote:
The Summit broadened our view and appreciation for software as a cultural artifact and as a method of capturing creativity in problem-solving.
Now we see the loss of computational methods that result in research as a loss of part of astronomy’s cultural heritage. This isn’t happening just for astronomy, of course; the Summit made clear that it is happening for everything. With so much rendered digitally, whether born that way or migrated to a digital medium, without preserving the digital artifacts and the software (and sometimes hardware) to lift these artifacts from their digital storage, we risk losing our art, our music, our games, our prose, our data, and our histories, of daily life and activities, of solutions to scientific problems, of popular pastimes and play experiences, and even knowledge of our computer worries and angst.
More on what we learned at the summit is available in the full report, which includes excellent pieces by participants Henry Lowood, Stanford University (The Lures of Software Preservation) and Matthew Kirschenbaum, University of Maryland (An Executable Past: The Case for a National Software Registry), an introduction by Trevor Owens, Library of Congress, and interviews of Doug White of the National Institute of Standards and Technology's National Software Reference Library and Michael Mansfield from the Smithsonian American Art Museum.
PreservingEXE: Toward a National Strategy for Software Preservation
-
It's not just astrophysics; other sciences are also grappling with issues surrounding software release, transparency of research, and collaboratively sharing codes.
The challenge of software licensing came up in the AAS 223 Special Session on code sharing; ASCL advisor Bruce Berriman followed up on this issue with a post on Astronomy Computing Today, and I've recently run across A Quick Guide to Software Licensing for the Scientist-Programmer, which also offers some guidance on this important issue.
-
The code sharing crowd took over the AAS Twitter feed, it seems, during the Special Session on code sharing at AAS 223. Bottom up is the best way to read these, as the most recent tweet is on the top, and please note they aren't strictly in order of occurrence and I likely missed some (there were so many!). I'm happy to add those I missed if someone tells me about them. Thanks to all those who tweeted throughout the session!
-
ASCL @asclnet 10 Jan
@#astroCodeShare folks here: http://asterisk.apod.com/viewtopic.php?f=35&t=21544 ….#aas223 -
Lucianne Walkowicz @shaka_lulu 10 Jan
For those who were interested in the#astroCodeShare session: "Best Practices for Scientific Computing": http://www.plosbiology.org/article/info%3Adoi%2F10.1371%2Fjournal.pbio.1001745 …#aas223 -
August Muench @augustmuench 7 Jan
Relevant to#astroCodeShare#aas223 RT@swcarpentry: Our 'Best Practices' Paper Has Been Published: http://software-carpentry.org/blog/2014/01/best-practices-has-been-published.html … -
Nuria Lorente @NoTruerAlien 7 Jan
@@bruceberriman Absolutely, but NOT releasing code also comes at a price, which is often forgotten.#aas223#astroCodeShare -
Zach Pace @zpacefromspace 7 Jan
Just got finished with an awesome breakout session at#aas223 on code sharing. The moral: your code may be crap, but release it anyway! -
Nuria Lorente
@NoTruerAlien 7 Jan
Morin et al: Informative paper on Sw licensing for Scientist-Programmer. MT@augustmuench: http://bit.ly/QlZKDP#astroCodeShare#aas223 -
Chrissy Madison @cmmadiso 7 Jan
See. It happens! RT@bathompso: Pulling a@cmmadiso: my phone has 1% battery after the#astroCodeShare session.#AAS223 -
Ben Thompson @bathompso 7 Jan
Pulling a@cmmadiso: my phone has 1% battery after the#astroCodeShare session.#AAS223 -
Lucianne Walkowicz
@shaka_lulu 7 Jan
Astronomical source code library: http://ascl.net#aas223#astroCodeShare -
Adrian Price-Whelan @a_p_w 7 Jan
RE: writing quick/dirty code to get papers out. "Weeks of programming can save you hours of planning."#aas223
-
Lucianne Walkowicz
@shaka_lulu 7 Jan
Working group on astronomical software: http://aas.org/comms/working-group-astronomical-software-wgas …#aas223#astroCodeShare -
Lucianne Walkowicz
@shaka_lulu 7 Jan
Hanisch: there should also be a prize for software, esp since Webber prize is for hardware only#aas223#astroCodeShare -
August Muench
@augustmuench 7 Jan
.@AlexaVillaume note: that paper is for software. licensing of *data/papers* is distinct but VERY important thing.#aas223#astroCodeShare -
August Muench
@augustmuench 7 Jan
.@AlexaVillaume try this paper: http://bit.ly/QlZKDP#astroCodeShare#aas223 -
Lucianne Walkowicz
@shaka_lulu 7 Jan
Licensing: BSD or MIT and forget about it- but we should discuss it more as community -@davidwhogg#astroCodeShare#aas223 cc@jonmccann -
Lucianne Walkowicz
@shaka_lulu 7 Jan
@#astroCodeShare tag if someone else got it -
Christopher Hanley @chanley 7 Jan
@#astroCodeShare -
August Muench
@augustmuench 7 Jan
so@aaccomazzi brings us back to licensing: unlicenced code is the WORST.@davidwhogg echos this point#aas223#astroCodeShare -
Lia Corrales @eblur27 7 Jan
Hey#astroCodeShare, I still want to know how I should cite software I get through github. Could help with fluid contributor lists#aas223 -
Lucianne Walkowicz
@shaka_lulu 7 Jan
Something to be gleaned from size of room v attendance v perceived necessary size of room & how code is valued.#aas223#astroCodeShare -
Ben Cook @bacook17 7 Jan
Reference in#aas223 code sharing session. http://wssspe.researchcomputing.org.uk 
Kelle Cruz @kellecruz 7 Jan
#- Lucianne Walkowicz
@shaka_lulu 7 Jan
Comment in back: u make good science by making good investments- invest in quality code by encouraging code sharing#aas223#astroCodeShare - Kelle Cruz
@kellecruz 7 Jan
# 
Alexa Villaume @AlexaVillaume 7 Jan
A mortifying story of a misplaced 2 in a program causing 8 years of research going down the drain. Share your code. It'll be ok.#aas223-
Meredith Rawls @merrdiff 7 Jan
.@kellecruz If it's easy to share code & get credit, we'll do it. Reminds me of this: http://theoatmeal.com/comics/game_of_thrones …#aas223#astroCodeShare -
Lucianne Walkowicz
@shaka_lulu 7 Jan
There are more ppl in this room than were in the Kepler session I attended yesterday.#aas223#astroCodeShare -
August Muench
@augustmuench 7 Jan
@#astroCodeShare -
August Muench
@augustmuench 7 Jan
So@eteq is gonna drop the mic: papers have fixed author lists. software authorship if fluid and grows. Et tu, ADS?#astroCodeShare#aas223 -
Lucianne Walkowicz
@shaka_lulu 7 Jan
Reply: if it goes on arXiv you can never update contributor list, so subsequent contributors don't get credit#aas223#astroCodeShare -
Lucianne Walkowicz
@shaka_lulu 7 Jan
Prsa: would be great if announcement of code went up on arXiv (I think they often do as release papers, e.g. emcee)#aas223#astroCodeShare -
August Muench
@augustmuench 7 Jan
interesting point: Montage built under contract to NASA; astropy built by cats, hosted on a cat based website#astroCodeShare#aas223 -
Meredith Rawls
@merrdiff 7 Jan
Andrej Prsa implores everyone in#astroCodeShare session to post code on astro-ph every time you submit a paper.#aas223 -
Meredith Rawls
@merrdiff 7 Jan
My advisor has said not to "waste time" writing generalized code; contradicting this is troubling. Mixed messages.#aas223
#astroCodeShare -
Lucianne Walkowicz
@shaka_lulu 7 Jan
Cost to sharing: making code useable by anyone req more time than just making it work for you then publishing w it#aas223#astroCodeShare -
Meredith Rawls
@merrdiff 7 Jan
Recurring theme of how do I maximize research productivity and make my code useable for others? Not an easy Q.#AAS223#astroCodeShare -
Lucianne Walkowicz
@shaka_lulu 7 Jan
That is, proprietary data sometimes equates to leverage- there is prob some analogy in code community-@davidwhogg#aas223#astroCodeShare -
Lucianne Walkowicz
@shaka_lulu 7 Jan
panelists doubt ppl are being hired for a specific code as opposed to skill, but must be analogy w proprietary data#aas223#astroCodeShare -
Lucianne Walkowicz
@shaka_lulu 7 Jan
Q: how do we reward ppl in ways that don't req keeping code proprietary? As in, ppl get hired bc they have the code#aas223#astroCodeShare -
Lia Corrales
@eblur27 7 Jan
Sad I'm missing#astroCodeShare, but reports of a packed room and massive twitter coverage are letting me stay comfy in COS session#aas223 -
Lucianne Walkowicz
@shaka_lulu 7 Jan
Besides, every little thing you think no one else needs- *someone* will prob find it useful#aas223#astroCodeShare -
Lucianne Walkowicz
@shaka_lulu 7 Jan
A: do what you need, if no one else needs it then that's fine, you haven't made anyone's life worse -@davidwhogg#aas223#astroCodeShare -
Lucianne Walkowicz
@shaka_lulu 7 Jan
Q: what's the balance bt needing to make code work for yourself vs making it useful for everyone always?#aas223#astroCodeShare -
Lucianne Walkowicz
@shaka_lulu 7 Jan
Comment in back: u make good science by making good investments- invest in quality code by encouraging code sharing#aas223#astroCodeShare -
Lucianne Walkowicz
@shaka_lulu 7 Jan
Katz: not really, unlikely beyond a few years' horizon at a time#aas223#astroCodeShare -
Lucianne Walkowicz
@shaka_lulu 7 Jan
No long term stewardship of code like there is for results (i.e. pubs)- does NSF have plans for that? -@davidwhogg#aas223#astroCodeShare -
Ben Thompson
@bathompso 7 Jan
.@kellecruz starting off the#astroCodeShare question session strong. Why no AAS reps here?#AAS223 -
Lucianne Walkowicz
@shaka_lulu 7 Jan
Do you use other people's codes? Do you modify them or use them as is?#astroCodeShare#aas223 - Lucianne Walkowicz
@shaka_lulu 7 JanDo you share code? If not, why not?#astroCodeShare#aas223 -
Lucianne Walkowicz
@shaka_lulu 7 Jan
Benefits: perceived priority on work, visibility & good will, citations, bug-catching, and moral high ground - DWH#astroCodeShare#aas223 - Alexa Villaume
@AlexaVillaume 7 Jan
Releasing code establishes priority and good will. Benefit from bug catching. Also, you get to be smug.#aas223 
Laura Watkins @laurawatkins_ 7 Jan
@#aas223
Ian Paul Freeley @ianpaulfreeley 7 Jan
If your not embarrassed by your code/website, you launched too late--Hogg#aas223-
Ben Thompson
@bathompso 7 Jan
If you’re not embarrassed by your code, you’re releasing it too late#AAS223#astroCodeShare - Meredith Rawls
@merrdiff 7 Jan
.@davidwhogg debunks cons to code sharing. Only real cost is email & support requests. He knows of NO example of being scooped.#aas223 -
August Muench
@augustmuench 7 Jan
hogg: "if you're not embarrassed by the code/website you put out there then you put it out there too late." so good.#astroCodeShare#aas223 -
Lucianne Walkowicz
@shaka_lulu 7 Jan
Cost: embarrassment! You know your code is crap, but if yr not embarrassed you released too late. -@davidwhogg#aas223#astroCodeShare -
Lucianne Walkowicz
@shaka_lulu 7 Jan
Costs: getting scooped?@davidwhogg knows of no cases of scooping caused by *release of code*#astroCodeShare#aas223 -
Lucianne Walkowicz
@shaka_lulu 7 Jan
All papers, grant writing, etc - not just code - are developed out in the open since 2005. -@davidwhogg#astroCodeShare#aas223 -
Matthew Turk @powersoffour 7 Jan
@#astroCodeShare -
Lucianne Walkowicz
@shaka_lulu 7 Jan
And boom,@davidwhogg right on time. Also, who mic'd him?#astroCodeShare#aas223 -
Laura Watkins
@laurawatkins_ 7 Jan
+1 MT@augustmuench "and this fact terrifies me because we have no idea collectively what sharing should look like.#astroCodeShare#aas223” -
August Muench
@augustmuench 7 Jan
and this fact terrifies me because education -- we have no idea collectively what sharing should look like.#astroCodeShare#aas223 -
August Muench
@augustmuench 7 Jan
Who enforces software/data sharing in astronomy? YOU DO! WE DO! PEER REVIEW DOES! not nsf/nasa.#aas223#astroCodeShare -
Lucianne Walkowicz
@shaka_lulu 7 Jan
Its UP TO YOU to include good data management plan as part of panel reviews. The community must enforce importance.#aas223#astroCodeShare -
Lucianne Walkowicz
@shaka_lulu 7 Jan
Data management plans in NSF proposals are required to detail how results/data/software will be shared. - Katz#astroCodeShare#aas223 -
Lucianne Walkowicz
@shaka_lulu 7 Jan
NSF policy for sharing research results: supposed to share not only the data and the results but the software#astroCodeShare#aas223 -
Lucianne Walkowicz
@shaka_lulu 7 Jan
NSF does include "products" in addtn to pubs in bio sketches, but could be better abt following up on code release#AAS223#astroCodeShare -
Lucianne Walkowicz
@shaka_lulu 7 Jan
Do we have policies that mandate code release in conjunction w publication or receipt of fed funds?#aas223#astroCodeShare
-
August Muench
@augustmuench 7 Jan
Software that enables all this new software: Github, Travis, Sphinx, Jenkins.#aas223#astroCodeShare - August Muench
@augustmuench 7 Jan
Agreed. RT@kellecruz: .@augustmuench we need to make data/code sharing requirements part of AAS journal policy. those two things.#aas223 -
Ben Thompson
@bathompso 7 Jan
Testing code is an important part of code sharing.#aas224 session?#AAS223 - Kelle Cruz
@kellecruz 7 Jan
.@augustmuench we need to make data/code sharing requirements part of AAS journal policy. those two things.#aas223 -
Lucianne Walkowicz
@shaka_lulu 7 Jan
If you build it, they will code - Tollerud#aas223#astroCodeShare -
Lucianne Walkowicz
@shaka_lulu 7 Jan
Need infrastructure, a few software ppl to do housekeeping, let scientists do whatev & set expectations - Tollerud#astroCodeShare#aas223 -
Lucianne Walkowicz
@shaka_lulu 7 Jan
Most ppl who have contributed code to AstroPY have never met each other - all via@github - Tollerud#astroCodeShare#aas223 -
Ben Thompson
@bathompso 7 Jan
Almost 60 people (who have not met) have all worked together to build@astropy#astroCodeShare#AAS223 -
Lucianne Walkowicz
@shaka_lulu 7 Jan
AstroPY: a python library for and by astronomers, developed by self-herding astronomers since 2011 - Tollerud#astroCodeShare#aas223 -
August Muench
@augustmuench 7 Jan
I hoping that we see some cool diffs between the@astropy and montage *support* networks in the open discussion in#astroCodeShare#aas223 -
August Muench
@augustmuench 7 Jan
.@merrdiff "research objects" is I think the new age terminology.#aas223#astroCodeShare -
David Morrison @drmorr0 7 Jan
@#astroCodeShare -
-
Lucianne Walkowicz
@shaka_lulu 7 Jan
I have used this exact cat herding graphic in Erik Tollerud's talk in an LSST talk hehe#aas223#astroCodeShare -
August Muench
@augustmuench 7 Jan
the@astropy project -- cat herding software development from@eteq at#astroCodeShare#aas223 -
Ian Paul Freeley
@ianpaulfreeley 7 Jan
Damn it--tweets from code sharing session sounded cool, but I got here late and now crowd out the door.#aas223 -
Alex Parker @Alex_Parker 7 Jan
I'm nodding so vigorously at the#astroCodeShare tweets that I might need to ice my neck later. -
Dr Chris Tibbs @chris_tibbs 7 Jan
Love the fact that my timeline is currently full of great tweets about code sharing and EPO#aas223- Kelle Cruz
@kellecruz 7 Jan
##interesting -
Alexa Villaume
@AlexaVillaume 7 Jan
"I wrote my first fortran code when Apollo 12 was on the moon."#aas223 -
August Muench
@augustmuench 7 Jan
Decision to code Cloudy in C++ was partly motivated to use industry grade lang & give students real world job ops!#astroCodeShare#aas223 -
Meredith Rawls
@merrdiff 7 Jan
Learning about the CLOUDY code, but speaker has no visuals :( Jokes that the code can be opaque; "C++: write once, read never."#aas223 -
Lucianne Walkowicz
@shaka_lulu 7 Jan
Complaining astros aren't comp scientists is like saying they shldn't learn math bc they aren't mathematicians#astroCodeShare#aas223 -
Timothy Pickering @te_pickering 7 Jan
#@shaka_lulu: I'll paraphrase@mjuric here: code is to modern astronomy what calculus once was.#aas223#astroCodeShare -
Lucianne Walkowicz
@shaka_lulu 7 Jan
I'll paraphrase@mjuric here: code is to modern astronomy what calculus once was.#aas223#astroCodeShare -
Kelle Cruz
@kellecruz 7 Jan
# - Kelle Cruz
@kellecruz 7 Jan
# -
-
Lucianne Walkowicz
@shaka_lulu 7 Jan
Q: how much do you think we fail to educate our young researchers to write good code?#astroCodeShare#aas223 - Ben Thompson
@bathompso 7 Jan
Q on why students are not educated on how to write good code (or code at all!)#AAS223
We have all failed here. -
August Muench
@augustmuench 7 Jan
The code base under question is Montage http://bit.ly/1aELvEz , dev'd & now volunteerly supported by IPAC scientists#aas223#astroCodeShare -
August Muench
@augustmuench 7 Jan
"Releasing your code comes with a price" --@bruceberriman Hmm, let's see if this pivots to the positive+solutions!#aas223#astroCodeShare -
Lucianne Walkowicz
@shaka_lulu 7 Jan
Lastly, resist the pundit-technician divide. - Weiner#aas223#astroCodeShare -
August Muench
@augustmuench 7 Jan
I completely agree with@cloud149: a lot of our concerns about sharing code are "pseudo" or hypothetical problems.#aas223#astroCodeShare -
Michelle Collins @michelle_lmc 7 Jan
We are failing to teach students how to write GOOD code in astronomy. Need to do better. Some programs in place, but not standard#aas223 -
Laura Watkins
@laurawatkins_ 7 Jan
"Do we do enough to teach our researchers how to write good code?" No. Fundamental skills but so many are left to learn alone.#aas223 - Kelle Cruz
@kellecruz 7 Jan
##exaggerating - Laura Watkins
@laurawatkins_ 7 Jan
Standing room only at the code sharing session. Apparently this is more popular than anticipated (this can only be a good thing)!#aas223 - Meredith Rawls
@merrdiff 7 Jan
Astrophysics code sharing session 225 at#aas223. Let's stop re-inventing the wheel. Our hardware is built to last; why not software? - Michelle Collins
@michelle_lmc 7 Jan
Oh, there are no women on the code sharing panel. Are we not sharing code? I'm currently not, but i'm here to learn how to#aas223 -
Ben Thompson
@bathompso 7 Jan
Excited for the Astronomy Code Sharing session. Wondering what to do with all my research programs.#AAS223 
Erik Tollerud @eteq 7 Jan
#@astropy on how code can be shared, along side@owlice@davidwhogg@bruceberriman@cloud149
Benjamin Weiner @cloud149 7 Jan
My talk "Occupy Hard Drives" for code session Tues 2 pm#aas223 is here: http://bit.ly/1acClmg@davidwhogg@bruceberriman@owlice@eteq-
ADASS @astroADASS 7 Jan
Follow discussion on astronomy code sharing at the#aas223 meeting using#astroCodeShare hashtag. - Benjamin Weiner
@cloud149 7 Jan
Tues 2pm#aas223 I aim to provoke on astro code sharing and why we don't respect software with@davidwhogg@bruceberriman@owlice@eteq -
Astropy @astropy 6 Jan
At the#aas223? Don't miss Tuesday's 14:00-15:30 session on code sharing - including a talk by@eteq about@astropy! 
David W. Hogg @davidwhogg 6 Jan
Tues at 2 see@owlice Hanisch Teuben@cloud149@bruceberriman Ferland Katz@eteq and me get all crazy about#code sharing at#aas223 in NH5
-
Jessica Lu