Repository navigation
Add a section 'Astropy is used by' #117
Description
It would be nice to have somewhere maybe on the front page where we can show organizations that we know use Astropy (e.g. STScI/JWST, etc.)
Metadata
Metadata
Assignees
Labels
No labels
Activity
eteq commentedon Aug 30, 2016
Maybe we should start collecting a list of them? Some that I know of:
eteq commentedon Aug 30, 2016
Perhaps this should also go in a section with "supported by in some manner"? So that would probably be just STScI and CXC?
taldcroft commentedon Aug 31, 2016
I'm not aware of anyone else in the CXC who develops astropy, so the "supported by" statement might be a little thin (though I personally spend most of my science time on Astropy). What is definitely true is that the CXC uses astropy to support spacecraft operations, and Sherpa is now using astropy.
I'm sure there are more projects at CfA. Maybe I should send an email to our pythonusers list asking for funded projects that use astropy? BTW, are we talking core or the Astropy ecosystem?
taldcroft commentedon Aug 31, 2016
http://cxc.harvard.edu/symposium_2007/imgs/cxc-logo.gif
bsipocz commentedon Sep 1, 2016
@eteq - What about Subaru and Gemini?
astrofrog commentedon Sep 1, 2016
Maybe we could send an email to the list to ask people which pipelines/organizations they know astropy is being used in? (we don't want to know about person X at some institution is using it, but rather that it is being used for official software for the telescope/pipeline/organization, so we would need to make that clear). And we can ask at the same time for permission to include their logo on this page?
demitri commentedon Sep 26, 2016
I would recommend finer granularity. List the institutions together, sure, but also list individual projects/pipelines. SDSS definitely uses Astropy, but MaNGA, APOGEE, and eBOSS should be listed. JWST and Hubble, for example, should be individually listed in addition to "NASA".
bsipocz commentedon Sep 26, 2016
Ohh, this was the thread I remembered on twitter, it's great @demitri that you've found it.
astrofrog commentedon Oct 30, 2016
List from a brainstorming session at ADASS:
Not all of these need to be mentioned in the proposed page/section, but just wanted to give a more complete list.
eteq commentedon Nov 2, 2016
Whoa. That's a pretty impressive list.
granttremblay commentedon Dec 11, 2016
This is a really lovely idea!
Are we thinking something really simple, e.g. a small section at the bottom of the "About" page?
Prototype example:
granttremblay commentedon Dec 11, 2016
I should add, given most institutes' branding guidelines, that we'd probably need to ask permission to show their logos. I'm happy to start that process, if we decide to go ahead.
taldcroft commentedon Dec 12, 2016
Looks great! At the bottom of the About page seems like a fine location.
Not clear how big of a project it is to get permission for all the logo's, so I wonder in the short term if the simple bulleted list of institutions would be a good start. This could be preceded by some disclaimer that this does not imply institutional endorsement of the Astropy project, merely that the project is known to use astropy in their code.
For kicks I started looking at the Harvard regulations for branding and immediately got annoyed and bored at the legalese. But probably this is pretty much worst-case in that regard.
astrofrog commentedon Dec 12, 2016
What about adding a sentence that allows people to contact us to ask for addition/removal of logo?
2 remaining items
demitri commentedon Dec 12, 2016
Use the logos; don't ask for permission. It's not illegal to use a company's/institutions's logo. They are public entities. It is illegal to use it in a manner that suggests that they endorse or represent the service or product. The wording at the top of the page should make this clear.
The branding guidelines that you find are mostly written to dictate how the logo is used on the company's/institution's own materials, e.g. packaging, web site, letterhead, etc. Most of the time this is not available on a web page since it's not intended for external users.
If a particular institution objects to the use of their logo on the page, they will have their coterie of lawyers send an email requesting it be removed. In that event we remove it, and the matter ends there. Don't put any message about how to request to remove the logo - trust me, they will know who to contact. No disclaimer is needed as long as it's made clear that the institutions are not being presented as endorsing or having ownership of Astropy, and I doubt that one could construe that from the web page.
granttremblay commentedon Dec 13, 2016
Draft here. Let me know what you think!
When we reach consensus, I'll issue a PR.
demitri commentedon Dec 13, 2016
Great work Grant. May I make a few suggestions?
Don't bundle surveys or even instruments together in a bullet point. Hubble should be its own thing, JWST, etc. I would even go as far to list Hubble, JWST, and "other" STScI as three items. I don't think this is unreasonable or unfair padding - they are individually very large and well-funded missions. MaNGA, APOGEE, and eBOSS each have their own logos and can be considered different surveys. I'd even add SDSS on top of those since Astropy is used in SDSS infrastructure.
You can get the SDSS logo here.
What do you think of this list more akin to a table view? I was thinking two columns - the logo on the left, the name and description as you have it on the right. I imagine this list growing significantly, and the logos will start to span several lines just by themselves. The table view will associate the description and the logo more strongly.
granttremblay commentedon Dec 13, 2016
Thanks Demitri! Nice suggestions. I'll draft up the table idea - more in a bit...
eteq commentedon Jan 5, 2017
This looks great @granttremblay!
kjordahl commentedon Feb 23, 2017
We use astropy internally at Planet Labs. Not because we are doing astronomy (though we are imaging the Earth from space), but because the NaN treatment in astropy.convolution.convolve() is so good.
eteq commentedon May 19, 2017
@granttremblay - @taldcroft and I we were just thinking about this and realized we left this pretty much at "it's basically done". Any chance you can finish this up as a PR?
eteq commentedon May 19, 2017
(although it may be good to wait on #159 ?)
granttremblay commentedon May 19, 2017
@eteq @taldcroft Absolutely, will do. I'll wait on #159 and issue a PR incorporating Demitri's suggestions
granttremblay commentedon May 8, 2018
This was first proposed back in 2016, so its high time I actually implement this. ;)
My apologies for the endless delay - will put something together (like the above, with the requested changes) and issue a PR.
bsipocz commentedon May 8, 2018
@granttremblay - I have a WIP project that looks into usage stats, so let me know if there are concrete questions to look for (e.g. github username for orgs to look into, etc.)
astrofrog commentedon Oct 4, 2020
IBM: https://www.zdnet.com/article/ibm-to-open-source-space-junk-collision-avoidance/ (code: https://github.com/IBM/spacetech-ssa)
taldcroft commentedon Oct 5, 2020
And not to forget the EHT and first black hole image, which got a nice shout-out in the NumPy Nature paper!
hamogu commentedon Oct 5, 2020
I'm also a big fan of the "survey endangered animals with drones": https://www.ljmu.ac.uk/about-us/news/articles/2018/4/4/astro-ecology
pllim commentedon Oct 5, 2020
For sure, Nancy Grace Roman Space Telescope will use
astropytoo.Didn't @bsipocz also mention Netflix at one point? 😸