Add a section 'Astropy is used by' #117

astrofrog · 2016-08-26T12:46:34Z

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.)

eteq · 2016-08-30T19:38:48Z

Maybe we should start collecting a list of them? Some that I know of:

NASA
STScI (strictly speaking not the same as NASA)
CXC/Harvard CfA (@taldcroft might know better what the best name/logo is for this)
LSST
the Norway Mapping Authority
NOAO (I think although I'm not 100% sure)

eteq · 2016-08-30T19:41:46Z

Perhaps this should also go in a section with "supported by in some manner"? So that would probably be just STScI and CXC?

taldcroft · 2016-08-31T01:07:51Z

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 · 2016-08-31T01:10:59Z

http://cxc.harvard.edu/symposium_2007/imgs/cxc-logo.gif

bsipocz · 2016-09-01T16:33:02Z

@eteq - What about Subaru and Gemini?

astrofrog · 2016-09-01T17:00:03Z

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 · 2016-09-26T16:55:47Z

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 · 2016-09-26T21:00:39Z

Ohh, this was the thread I remembered on twitter, it's great @demitri that you've found it.

astrofrog · 2016-10-30T14:10:37Z

List from a brainstorming session at ADASS:

James Webb Space Telescope (JWST) pipeline : https://github.com/STScI-JWST/jwst
Gran Telescopio Canarias (GTC) pipeline for EMIR (Infrared MOS) https://github.com/guaix-ucm/pyemir and MEGARA (Optical MOS and IFU) https://github.com/guaix-ucm/megaradrp
Hubble Space Telescope (HST) Pipelines (STScI)
JWST and HST instrumentation support and data analysis efforts
LSST Science Pipelines (currently for tables and units in tables but see http://dx.doi.org/10.1117/12.2231313 for a future plan)
JWST-MIRI Simulator : http://www.miricle.org (using io.fits, io.ascii, coordinates, units, modeling, gwcs)
INAF - DISCOS project in some of the external packages ( https://github.com/discos/basie https://github.com/discos/discos-backend )
CTA - The Cherenkov Telescope Array - Pipeline framework: https://github.com/cta-observatory/ctapipe
SimCADO - the MICADO+E-ELT instrument simulator
Code Investigating GALaxy Emission (CIGALE - http://cigale.lam.fr/)
We should scrape github for astropy imports, can do a huge list of organizations
The Herschel Extragalactic Legacy Project (https://herschellegacyproject.wordpress.com/)
Tuna - project at LAM, pipeline for reduction of Fabry-Perot interferograms. It uses Astropy for fitting. Also, Tuna was built using Astropy’s guidelines for affiliated packages - it helped me a lot in getting a “best practices” project up and running!
Gemini data reduction software. Science and Data quality pipeline.
PyVO - An Interface to the Virtual Observatory using DAL Standards https://github.com/pyvirtobs/pyvo
MUSE - MPDAF (MUSE Python Data Analysis Framework) http://mpdaf.readthedocs.io/en/latest/
AAO - SAMI Galaxy Survey - http://sami-survey.org
Hubble Frontier Fields
Hubble RELICS Project
UTFSM - Universidad Técnica Federico Santa María

Not all of these need to be mentioned in the proposed page/section, but just wanted to give a more complete list.

eteq · 2016-11-02T19:36:49Z

Whoa. That's a pretty impressive list.

granttremblay · 2016-12-11T19:13:31Z

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 · 2016-12-11T22:40:11Z

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 · 2016-12-12T15:34:59Z

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 · 2016-12-12T15:58:58Z

What about adding a sentence that allows people to contact us to ask for addition/removal of logo?

granttremblay · 2016-12-12T20:21:51Z

That would be way easier, @astrofrog. Better to beg for forgiveness than ask for permission. Anyone actively against a simple disclaimer that combines the suggestions by @astrofrog and @taldcroft ?

While we await consensus re: logo permissions, I'll draft up the new section with a (temporary?) disclaimer and issue a PR for review.

kelle · 2016-12-12T20:43:35Z

+1 for forgiveness > permission and a small, simple disclaimer.

…

On Mon, Dec 12, 2016 at 3:21 PM, Grant Tremblay ***@***.***> wrote: That would be way easier, @astrofrog <https://github.com/astrofrog>. In this case it might be far better to beg forgiveness than ask for permission. Anyone actively against a simple disclaimer that combines the suggestions by @astrofrog <https://github.com/astrofrog> and @taldcroft <https://github.com/taldcroft> ? If not, I'll draft up the new section and issue a PR for review. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#117 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABYJmZYQVDRRwGSEHEyZMvjtQuK7IS6Bks5rHazfgaJpZM4JuCto> .

-- Kelle Cruz, PhD — http://kellecruz.com/ 917.725.1334 — Hunter: x16486 — AMNH: x3404

demitri · 2016-12-12T21:59:19Z

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 · 2016-12-13T04:55:44Z

Draft here. Let me know what you think!

When we reach consensus, I'll issue a PR.

demitri · 2016-12-13T16:25:11Z

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 · 2016-12-13T20:58:46Z

Thanks Demitri! Nice suggestions. I'll draft up the table idea - more in a bit...

eteq · 2017-01-05T23:01:08Z

This looks great @granttremblay!

kjordahl · 2017-02-23T03:54:06Z

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 · 2017-05-19T20:35:25Z

@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 · 2017-05-19T20:36:01Z

(although it may be good to wait on #159 ?)

granttremblay · 2017-05-19T20:37:55Z

@eteq @taldcroft Absolutely, will do. I'll wait on #159 and issue a PR incorporating Demitri's suggestions

granttremblay · 2018-05-08T16:40:43Z

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 · 2018-05-08T17:41:00Z

@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 · 2020-10-04T13:04:39Z

IBM: https://www.zdnet.com/article/ibm-to-open-source-space-junk-collision-avoidance/ (code: https://github.com/IBM/spacetech-ssa)

taldcroft · 2020-10-05T09:55:23Z

And not to forget the EHT and first black hole image, which got a nice shout-out in the NumPy Nature paper!

hamogu · 2020-10-05T11:06:10Z

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 · 2020-10-05T13:56:59Z

For sure, Nancy Grace Roman Space Telescope will use astropy too.

Didn't @bsipocz also mention Netflix at one point? 😸

kelle assigned granttremblay Dec 6, 2016

astrofrog mentioned this issue Feb 23, 2017

Convolution consistency astropy/astropy#5782

Merged

4 tasks

granttremblay mentioned this issue Jun 28, 2017

Add a list of organizations that have supported astropy #166

Closed

granttremblay mentioned this issue Jul 24, 2017

add inclusivity statement to website #145

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Add a section 'Astropy is used by' #117

Add a section 'Astropy is used by' #117

astrofrog commented Aug 26, 2016

eteq commented Aug 30, 2016 •

edited

Loading

eteq commented Aug 30, 2016 •

edited

Loading

taldcroft commented Aug 31, 2016

taldcroft commented Aug 31, 2016

bsipocz commented Sep 1, 2016

astrofrog commented Sep 1, 2016

demitri commented Sep 26, 2016

bsipocz commented Sep 26, 2016

astrofrog commented Oct 30, 2016

eteq commented Nov 2, 2016

granttremblay commented Dec 11, 2016 •

edited

Loading

granttremblay commented Dec 11, 2016 •

edited

Loading

taldcroft commented Dec 12, 2016

astrofrog commented Dec 12, 2016

granttremblay commented Dec 12, 2016 •

edited

Loading

kelle commented Dec 12, 2016 via email

demitri commented Dec 12, 2016

granttremblay commented Dec 13, 2016

demitri commented Dec 13, 2016 •

edited

Loading

granttremblay commented Dec 13, 2016

eteq commented Jan 5, 2017

kjordahl commented Feb 23, 2017

eteq commented May 19, 2017

eteq commented May 19, 2017

granttremblay commented May 19, 2017

granttremblay commented May 8, 2018

bsipocz commented May 8, 2018

astrofrog commented Oct 4, 2020

taldcroft commented Oct 5, 2020 •

edited

Loading

hamogu commented Oct 5, 2020

pllim commented Oct 5, 2020

Add a section 'Astropy is used by' #117

Add a section 'Astropy is used by' #117

Comments

astrofrog commented Aug 26, 2016

eteq commented Aug 30, 2016 • edited Loading

eteq commented Aug 30, 2016 • edited Loading

taldcroft commented Aug 31, 2016

taldcroft commented Aug 31, 2016

bsipocz commented Sep 1, 2016

astrofrog commented Sep 1, 2016

demitri commented Sep 26, 2016

bsipocz commented Sep 26, 2016

astrofrog commented Oct 30, 2016

eteq commented Nov 2, 2016

granttremblay commented Dec 11, 2016 • edited Loading

granttremblay commented Dec 11, 2016 • edited Loading

taldcroft commented Dec 12, 2016

astrofrog commented Dec 12, 2016

granttremblay commented Dec 12, 2016 • edited Loading

kelle commented Dec 12, 2016 via email

demitri commented Dec 12, 2016

granttremblay commented Dec 13, 2016

demitri commented Dec 13, 2016 • edited Loading

granttremblay commented Dec 13, 2016

eteq commented Jan 5, 2017

kjordahl commented Feb 23, 2017

eteq commented May 19, 2017

eteq commented May 19, 2017

granttremblay commented May 19, 2017

granttremblay commented May 8, 2018

bsipocz commented May 8, 2018

astrofrog commented Oct 4, 2020

taldcroft commented Oct 5, 2020 • edited Loading

hamogu commented Oct 5, 2020

pllim commented Oct 5, 2020

eteq commented Aug 30, 2016 •

edited

Loading

eteq commented Aug 30, 2016 •

edited

Loading

granttremblay commented Dec 11, 2016 •

edited

Loading

granttremblay commented Dec 11, 2016 •

edited

Loading

granttremblay commented Dec 12, 2016 •

edited

Loading

demitri commented Dec 13, 2016 •

edited

Loading

taldcroft commented Oct 5, 2020 •

edited

Loading