From 6d9354683d896b18720b068d901a1d5bd983abda Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:35:52 +0000
Subject: [PATCH 001/909] New translations community.md (Spanish)
---
content/es/community.md | 65 +++++++++++++++++++++++++++++++++++++++++
1 file changed, 65 insertions(+)
create mode 100644 content/es/community.md
diff --git a/content/es/community.md b/content/es/community.md
new file mode 100644
index 0000000000..4e24a83784
--- /dev/null
+++ b/content/es/community.md
@@ -0,0 +1,65 @@
+---
+title: Community
+sidebar: false
+---
+
+NumPy is a community-driven open source project developed by a very diverse group of [contributors](/gallery/team.html). The NumPy leadership has made a strong commitment to creating an open, inclusive, and positive community. Please read the [NumPy Code of Conduct](/code-of-conduct) for guidance on how to interact with others in a way that makes the community thrive.
+
+We offer several communication channels to learn, share your knowledge and connect with others within the NumPy community.
+
+
+## Participate online
+
+The following are ways to engage directly with the NumPy project and community. _Please note that we encourage users and community members to support each other for usage questions - see [Get Help](/gethelp)._
+
+
+### [NumPy mailing list](https://mail.python.org/mailman/listinfo/numpy-discussion)
+
+This list is the main forum for longer-form discussions, like adding new features to NumPy, making changes to the NumPy Roadmap, and all kinds of project-wide decision making. Announcements about NumPy, such as for releases, developer meetings, sprints or conference talks are also made on this list.
+
+On this list please use bottom posting, reply to the list (rather than to another sender), and don't reply to digests. A searchable archive of this list is available [here](http://numpy-discussion.10968.n7.nabble.com/).
+
+***
+
+### [GitHub issue tracker](https://github.com/numpy/numpy/issues)
+
+- For bug reports (e.g. "`np.arange(3).shape` returns `(5,)`, when it should return `(3,)`");
+- documentation issues (e.g. "I found this section unclear");
+- and feature requests (e.g. "I would like to have a new interpolation method in `np.percentile`").
+
+_Please note that GitHub is not the right place to report a security vulnerability. If you think you have found a security vulnerability in NumPy, please report it [here](https://tidelift.com/docs/security)._
+
+***
+
+### [Slack](https://numpy-team.slack.com)
+
+A real-time chat room to ask questions about _contributing_ to NumPy. This is a private space, specifically meant for people who are hesitant to bring up their questions or ideas on a large public mailing list or GitHub. Please see [here](https://numpy.org/devdocs/dev/index.html#contributing-to-numpy) for more details and how to get an invite.
+
+
+## Study Groups and Meetups
+
+If you would like to find a local meetup or study group to learn more about NumPy and the wider ecosystem of Python packages for data science and scientific computing, we recommend exploring the [PyData meetups](https://www.meetup.com/pro/pydata/) (150+ meetups, 100,000+ members).
+
+NumPy also organizes in-person sprints for its team and interested contributors occasionally. These are typically planned several months in advance and will be announced on the [mailing list](https://mail.python.org/mailman/listinfo/numpy-discussion) and [Twitter](https://twitter.com/numpy_team).
+
+
+## Conferences
+
+The NumPy project doesn't organize its own conferences. The conferences that have traditionally been most popular with NumPy maintainers, contributors and users are the SciPy and PyData conference series:
+
+- [SciPy US](https://conference.scipy.org)
+- [EuroSciPy](https://www.euroscipy.org)
+- [SciPy Latin America](https://www.scipyla.org)
+- [SciPy India](https://scipy.in)
+- [SciPy Japan](https://conference.scipy.org)
+- [PyData conferences](https://pydata.org/event-schedule/) (15-20 events a year spread over many countries)
+
+Many of these conferences include tutorial days that cover NumPy and/or sprints where you can learn how to contribute to NumPy or related open source projects.
+
+
+## Join the NumPy community
+
+To thrive, the NumPy project needs your expertise and enthusiasm. Not a coder? Not a problem! There are many ways to contribute to NumPy.
+
+If you are interested in becoming a NumPy contributor (yay!) we recommend checking out our [Contribute](/contribute) page.
+
From 000d81ac0fde76270d9b525192914b56331fbc72 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:35:53 +0000
Subject: [PATCH 002/909] New translations diversity_sep2020.md (Chinese
Simplified)
---
content/zh/diversity_sep2020.md | 48 +++++++++++++++++++++++++++++++++
1 file changed, 48 insertions(+)
create mode 100644 content/zh/diversity_sep2020.md
diff --git a/content/zh/diversity_sep2020.md b/content/zh/diversity_sep2020.md
new file mode 100644
index 0000000000..ef3030d5f7
--- /dev/null
+++ b/content/zh/diversity_sep2020.md
@@ -0,0 +1,48 @@
+---
+title: NumPy Diversity and Inclusion Statement
+sidebar: false
+---
+
+
+_In light of the foregoing discussion on social media after publication of the NumPy paper in Nature and the concerns raised about the state of diversity and inclusion on the NumPy team, we would like to issue the following statement:_
+
+
+It is our strong belief that we are at our best, as a team and community, when we are inclusive and equitable. Being an international team from the onset, we recognize the value of collaborating with individuals from diverse backgrounds and expertise. A culture where everyone is welcomed, supported, and valued is at the core of the NumPy project.
+
+## The Past
+
+Contributing to open source has always been a pastime in which most historically marginalized groups, especially women, faced more obstacles to participate due to a number of societal constraints and expectations. Open source has a severe diversity gap that is well documented (see, e.g., the [2017 GitHub Open Source Survey](https://opensourcesurvey.org/2017/) and [this blog post](https://medium.com/tech-diversity-files/if-you-think-women-in-tech-is-just-a-pipeline-problem-you-haven-t-been-paying-attention-cb7a2073b996)).
+
+Since its inception and until 2018, NumPy was maintained by a handful of volunteers often working nights and weekends outside of their day jobs. At any one time, the number of active core developers, the ones doing most of the heavy lifting as well as code review and integration of contributions from the community, was in the range of 4 to 8. The project didn't have a roadmap or mechanism for directing resources, being driven by individual efforts to work on what seemed needed. The authors on the NumPy paper are the individuals who made the most significant and sustained contributions to the project over a period of 15 years (2005 - 2019). The lack of diversity on this author list is a reflection of the formative years of the Python and SciPy ecosystems.
+
+2018 has marked an important milestone in the history of the NumPy project. Receiving funding from The Gordon and Betty Moore Foundation and Alfred P. Sloan Foundation allowed us to provide full-time employment for two software engineers with years of experience contributing to the Python ecosystem. Those efforts brought NumPy to a much healthier technical state.
+
+This funding also created space for NumPy maintainers to focus on project governance, community development, and outreach to underrepresented groups. [The diversity statement](https://figshare.com/articles/online_resource/Diversity_and_Inclusion_Statement_NumPy_for_Chan_Zuckerberg_Initiative_EOSS_2019_round_1/12980852) written in mid 2019 for the CZI EOSS program grant application details some of the challenges as well as the advances in our efforts to bring in more diverse talent to the NumPy team.
+
+## The Present
+
+Offering employment opportunities is an effective way to attract and retain diverse talent in OSS. Therefore, we used two-thirds of our second grant that became available in Dec 2019 to employ Melissa Weber Mendonça and Mars Lee.
+
+As a result of several initiatives aimed at community development and engagement led by Inessa Pawson and Ralf Gommers, the NumPy project has received a number of valuable contributions from women and other underrepresented groups in open source in 2020:
+
+- Melissa Weber Mendonça gained commit rights, is maintaining numpy.f2py and is leading the documentation team,
+- Shaloo Shalini created all case studies on numpy.org,
+- Mars Lee contributed web design and led our accessibility improvements work,
+- Isabela Presedo-Floyd designed our new logo,
+- Stephanie Mendoza, Xiayoi Deng, Deji Suolang, and Mame Fatou Thiam designed and fielded the first NumPy user survey,
+- Yuki Dunn, Dayane Machado, Mahfuza Humayra Mohona, Sumera Priyadarsini, Shaloo Shalini, and Kriti Singh (former Outreachy intern) helped the survey team to reach out to non-English speaking NumPy users and developers by translating the questionnaire into their native languages,
+- Sayed Adel, Raghuveer Devulapalli, and Chunlin Fang are driving the work on SIMD optimizations in the core of NumPy.
+
+While we still have much more work to do, the NumPy team is starting to look much more representative of our user base. And we can assure you that the next NumPy paper will certainly have a more diverse group of authors.
+
+## The Future
+
+We are fully committed to fostering inclusion and diversity on our team and in our community, and to do our part in building a more just and equitable future.
+
+We are open to dialogue and welcome every opportunity to connect with organizations representing and supporting women and minorities in tech and science. We are ready to listen, learn, and support.
+
+Please get in touch with us on [our mailing list](https://scipy.org/scipylib/mailing-lists.html#mailing-lists), [GitHub](https://github.com/numpy/numpy/issues), [Slack](https://numpy.org/contribute/), in private at numpy-team@googlegroups.com, or join our [bi-weekly community meeting](https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg).
+
+
+_Sayed Adel, Sebastian Berg, Raghuveer Devulapalli, Chunlin Fang, Ralf Gommers, Allan Haldane, Stephan Hoyer, Mars Lee, Melissa Weber Mendonça, Jarrod Millman, Inessa Pawson, Matti Picus, Nathaniel Smith, Julian Taylor, Pauli Virtanen, Stéfan van der Walt, Eric Wieser, on behalf of the NumPy team_
+
From ec7cec44c1a0e753956c3b9b9ee5c3a59ac2423a Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:35:55 +0000
Subject: [PATCH 003/909] New translations gethelp.md (Portuguese, Brazilian)
---
content/pt/gethelp.md | 34 ++++++++++++++++++++++++++++++++++
1 file changed, 34 insertions(+)
create mode 100644 content/pt/gethelp.md
diff --git a/content/pt/gethelp.md b/content/pt/gethelp.md
new file mode 100644
index 0000000000..bba586e7f2
--- /dev/null
+++ b/content/pt/gethelp.md
@@ -0,0 +1,34 @@
+---
+title: Obter ajuda
+sidebar: false
+---
+
+**Perguntas de usuários:** A melhor maneira de obter ajuda é postar sua pergunta em um site como [StackOverflow](http://stackoverflow.com/questions/tagged/numpy), com milhares de usuários disponíveis para responder. Outras alternativas incluem [IRC](https://webchat.freenode.net/?channels=%23numpy), [Gitter](https://gitter.im/numpy/numpy)e [Reddit](https://www.reddit.com/r/Numpy/). Gostaríamos de poder ficar de olho nestes sites, ou responder perguntas diretamente, mas o volume é imenso!
+
+**Issues sobre desenvolvimento:** Para assuntos relacionados ao desenvolvimento do NumPy (por exemplo, relatórios de bugs), veja a [Comunidade](/community).
+
+
+
+### [StackOverflow](http://stackoverflow.com/questions/tagged/numpy)
+
+Um fórum para fazer perguntas sobre a utilização da biblioteca, por exemplo: "Como faço X no NumPy?". Por favor [use a tag `#numpy`](https://stackoverflow.com/help/tagging)
+
+***
+
+### [Reddit](https://www.reddit.com/r/Numpy/)
+
+Outro fórum para perguntas de utilização.
+
+***
+
+### [Gitter](https://gitter.im/numpy/numpy)
+
+Uma sala de bate-papo em tempo real onde usuários e membros da comunidade se ajudam uns aos outros.
+
+***
+
+### [IRC](https://webchat.freenode.net/?channels=%23numpy)
+
+Outra sala de bate-papo em tempo real onde usuários e membros da comunidade se ajudam uns aos outros.
+
+***
From 7d05e8cdcdd4c77b675243b3d03a4e038402756e Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:35:57 +0000
Subject: [PATCH 004/909] New translations report-handling-manual.md
(Portuguese, Brazilian)
---
content/pt/report-handling-manual.md | 95 ++++++++++++++++++++++++++++
1 file changed, 95 insertions(+)
create mode 100644 content/pt/report-handling-manual.md
diff --git a/content/pt/report-handling-manual.md b/content/pt/report-handling-manual.md
new file mode 100644
index 0000000000..14418d0e11
--- /dev/null
+++ b/content/pt/report-handling-manual.md
@@ -0,0 +1,95 @@
+---
+title: Código de Conduta NumPy - Como dar seguimento a um relatório
+sidebar: false
+---
+
+Este é o manual seguido pelo Comitê do Código de Conduta do NumPy. É usado quando respondemos a um incidente para nos certificarmos de que somos pessoas consistentes e justas.
+
+Garantir que o [Código de Conduta](/code-of-conduct) seja respeitado afeta nossa comunidade hoje e no futuro. É uma ação que levamos muito a sério. Ao analisar medidas de aplicação do Código de Conduta, o Comitê terá em mente os seguintes valores e orientações:
+
+* Agir de forma pessoal e não impessoal. O Comitê pode levar as partes a compreender a situação, respeitando simultaneamente a privacidade e a necessária confidencialidade das pessoas relatantes. No entanto, por vezes, é necessário comunicar diretamente com um ou mais indivíduos: o objetivo do Comitê é melhorar a saúde da nossa comunidade, em vez de produzir apenas uma decisão formal.
+* Enfatizar empatia pelos indivíduos ao invés de julgar o comportamento, evitando rótulos binários de "bom" e "mau". Existem atos de agressão e assédio claros e visíveis, e vamos abordá-los com firmeza. Mas muitos cenários que podem ser desafiadores são aqueles em que as discordâncias normais se transformam em comportamento desnecessário ou prejudicial de várias partes. Compreender o contexto completo e encontrar um caminho que traga um entendimento entre as partes é difícil, mas, em última análise, é o resultado mais produtivo para a nossa comunidade.
+* Compreendemos que o e-mail é um meio difícil e que pode causar uma sensação de isolamento. Receber críticas por e-mail, sem contato pessoal, pode ser particularmente doloroso. Isto faz com que seja especialmente importante manter um clima de respeito aberto pelas opiniões dos outros. Significa também que temos de ser transparentes nas nossas ações, e que faremos tudo o que estiver ao nosso alcance para garantir que todos os nossos membros sejam tratados de forma justa e com simpatia.
+* A discriminação pode ser sutil e pode ser inconsciente. Pode revelar-se em tratamentos injustos e hostis em interações que normalmente seriam ordinárias. Sabemos que isso acontece, e teremos o cuidado de ter isso em mente. Gostaríamos muito de ouvir se você acha que foi tratado injustamente, e usaremos esses procedimentos para garantir que a sua reclamação seja ouvida e abordada.
+* Ajudar a aumentar o envolvimento em uma boa prática de discussão: tentar identificar onde a discussão pode ter falhado, e fornecer informações úteis, indicadores e recursos que podem levar a mudanças positivas nestes pontos.
+* Estar ciente das necessidades de novos membros: fornecer-lhes apoio e consideração explícitos, com o objetivo de aumentar a participação de grupos sub-representados, em particular.
+* As pessoas vêm de meios culturais e linguísticos diferentes. Tentar identificar quaisquer mal-entendidos honestos causados por falantes não-nativos e ajudá-los a entender a questão e o que pode ser modificado para evitar causar ofensa. Uma discussão complexa numa língua estrangeira pode ser muito intimidante, e queremos aumentar a nossa diversidade também entre nacionalidades e culturas.
+
+
+## Mediação
+
+A mediação informal voluntária é um instrumento à nossa disposição. Em contextos em que duas ou mais partes escalaram ao ponto de demonstrarem comportamento inapropriado (algo tristemente comum no conflito humano), poderá ser útil facilitar um processo de mediação. Isto é apenas um exemplo: em todo caso, o Comitê pode considerar a mediação, tendo em conta que o processo se destina a ser estritamente voluntário e que nenhuma das partes pode ser pressionada a participar. Se o Comitê sugerir mediação, deve:
+
+* Encontrar uma pessoa candidata que possa servir de mediadora.
+* Obter o acordo da(s) pessoa(s) relatante(s). A(s) pessoa(s) relatante(s) têm total liberdade para recusar a ideia de mediação ou propor um mediador alternativo.
+* Obter o acordo da(s) pessoa(s) relatada(s).
+* Estabelecer uma pessoa mediadora: enquanto as partes podem propor um mediador diferente da pessoa sugerida, o processo só poderá avançar se for alcançado um acordo comum em todos os termos.
+* Estabelecer um cronograma para a mediação ser concluida, idealmente dentro de duas semanas.
+
+A pessoa mediadora entrará em contato com todas as partes e procurará uma resolução satisfatória para todos. Após a sua conclusão, a pessoa mediadora apresentará ao Comitê um relatório (examinado por todas as partes envolvidas no processo) com recomendações sobre outras medidas. O Comitê avaliará então esses resultados (em caso de resolução satisfatória ou não) e decidirá sobre quaisquer medidas adicionais consideradas necessárias.
+
+
+## Como o Comitê responderá aos relatórios
+
+Quando o Comitê (ou um membro do Comitê) recebe um relatório, será inicialmente determinado se o relatório é sobre uma violação clara e severa (como definido abaixo). Em caso afirmativo, medidas imediatas serão tomadas para além do processo regular de tratamento dos relatórios.
+
+
+## Ações claras e severas de violação
+
+Sabemos que é mais comum do que o desejado que a comunicação na Internet comece ou se transforme em abusos óbvios e flagrantes. Trataremos rapidamente de violações claras e severas como ameaças pessoais, linguagem violenta, sexista ou racista.
+
+Quando um membro do Comitê do Código de Conduta tomar conhecimento de uma violação clara e grave, fará o seguinte:
+
+* Desligará imediatamente a pessoa originadora de todos os canais de comunicação do NumPy.
+* Responderá à pessoa relatante para informá-la que seu relatório foi recebido e que a pessoa originadora foi desligada.
+* Em todos os casos, a pessoa moderadora deve fazer um esforço razoável para entrar em contato com a pessoa originadora, e dizer-lhes especificamente como sua linguagem ou ações se qualificam como uma "violação clara e severa". A pessoa moderadora deve também dizer que, se a pessoa originadora considerar que isso é injusto ou quiser ser reconectada ao NumPy, tem o direito de solicitar uma revisão, de acordo com as disposições do Comitê do Código de Conduta. A pessoa moderadora deve copiar esta explicação para o Comitê do Código de Conduta.
+* O Comitê do Código de Conduta procederá formalmente à análise e decisão em todos os casos em que este mecanismo tenha sido aplicado para garantir que não seja utilizado para controlar desentendimentos acalorados comuns.
+
+
+## Tratamento de relatórios
+
+Quando um relatório é enviado ao Comitê, ele responderá imediatamente à pessoa relatante para confirmar a sua recepção. Esta resposta deve ser enviada no prazo de 72 horas, e o grupo deve esforçar-se por responder muito mais rapidamente.
+
+Se um relatório não contiver informações suficientes, o Comitê obterá todos os dados relevantes antes de agir. O Comitê tem poderes para agir em nome do Conselho Diretor ao contactar quaisquer pessoas envolvidas para obter um relato mais completo dos acontecimentos.
+
+O Comitê analisará então o incidente e determinará, do melhor jeito possível:
+
+* O que aconteceu.
+* Se este evento constitui ou não uma violação do Código de Conduta.
+* Quem são as pessoas responsáveis.
+* Se se trata de uma situação contínua, e existe uma ameaça para a segurança física de alguém.
+
+Estas informações serão recolhidas por escrito e, sempre que possível, as deliberações do grupo serão gravadas e armazenadas (por exemplo, transcrições de conversas, discussões por e-mail, chamadas gravadas de videoconferência, resumos de conversas por voz, etc).
+
+É importante manter um arquivo de todas as atividades deste Comitê para garantir a consistência no comportamento e fornecer memória institucional ao projeto. Para ajudar com isto, o canal de discussão padrão para este Comitê será uma lista de e-mail privada, acessível a atuais e futuros membros do Comitê, bem como aos membros do Conselho Diretor a pedido justificado. Se o Comitê sentir a necessidade de usar comunicações fora da lista (por exemplo, chamadas por telefone para resposta precoce/rápida), deve em todos os casos resumi-las de volta para a lista, para que haja um bom registro do processo.
+
+O Comitê do Código de Conduta deve ter por objetivo chegar a um acordo sobre uma resolução no prazo de duas semanas. Caso uma resolução não possa ser determinada nesse período, o Comitê responderá à(s) pessoa(s) relatante(s) com uma atualização e cronograma previsto para a resolução.
+
+
+## Resoluções
+
+O Comitê tem de chegar a um acordo sobre uma resolução por consenso. Se o grupo não conseguir chegar a um consenso e permanece bloqueado durante mais de uma semana, o grupo encaminhará o assunto para o Conselho Diretor para resolução.
+
+Possíveis respostas podem incluir:
+
+* Não tomar nenhuma outra ação:
+ - se determinarmos que não ocorreram violações;
+ - se a questão tiver sido resolvida publicamente enquanto o Comitê estava considerando uma resposta.
+* Coordenação de mediação voluntária: se todas as partes envolvidas concordarem, o Comitê poderá facilitar um processo de mediação, conforme detalhado acima.
+* Salientar publicamente que alguns comportamentos, ações ou linguagem foram julgados inapropriados ou podem ser considerados danosos para algumas pessoas, explicando por que no contexto atual e solicitando que a comunidade se auto-ajuste.
+* Uma advertência privada do Comitê para a(s) pessoa(s) envolvida(s). Neste caso, a pessoa presidente do Comitê irá entregar essa advertência à(s) pessoa(s) por e-mail, em cópia (CC) ao grupo.
+* Uma advertência pública. Neste caso, a pessoa presidente do Comitê vai apresentar essa advertência no mesmo fórum em que ocorreu a violação, dentro dos limites da viabilidade. Exemplo: a lista original para uma violação de e-mail, mas para uma discussão em sala de bate-papo onde a pessoa/contexto pode sumir, isto pode ser feito por outros meios. O grupo pode optar por publicar esta mensagem em outro local para fins de documentação.
+* Um pedido de desculpas públicas ou privadas, supondo que a(s) pessoa(s) relatante(s) concorde(m) com esta ideia: a(s) pessoa(s) pode(m), a seu critério, recusar contatos adicionais com a pessoa relatada. A Presidência dará seguimento a este pedido. O Comitê, se escolher, pode anexar condições adicionais a este pedido inicial: por exemplo, o grupo pode pedir à pessoa relatada que se desculpe para que tenha o direito de manter a sua adesão a uma lista de e-mails.
+* Um “acordo mútuo de trégua” onde o Comitê solicita à pessoa que se abstenha temporariamente da participação na comunidade. Se a pessoa optar por não fazer uma pausa temporária voluntariamente, o Comitê pode aplicar um “período de afastamento obrigatório”.
+* Um banimento permanente ou temporário de alguns ou todos os espaços do NumPy (listas de e-mails, gitter.im, etc.). O grupo manterá registro de todas essas proibições, para que elas possam ser revistas no futuro ou mantidas.
+
+Uma vez aprovada uma resolução, mas antes de ser efetivamente aplicada, o Comitê entrará em contato com a pessoa relatante original e quaisquer outras partes afetadas e explicará a resolução proposta. O Comitê perguntará se esta resolução é aceitável e terá de tomar nota da sua resposta para registro futuro.
+
+Finalmente, o Comitê apresentará um relatório ao Conselho Diretor do NumPy (bem como ao time *core* do NumPy no caso de uma resolução em curso, como um banimento).
+
+O Comitê nunca discutirá publicamente a questão; todas as declarações públicas serão feitas pela pessoa presidente do Comitê do Código de Conduta ou pelo Conselho Diretor do NumPy.
+
+
+## Conflitos de Interesse
+
+Em caso de conflito de interesses, um membro do Comitê deve notificar imediatamente os outros membros e abdicar de sua participação no processo caso seja necessário.
From 7adb5ed0e8b245dffff7d1c0ecf5c23068fe1a57 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:35:58 +0000
Subject: [PATCH 005/909] New translations terms.md (Portuguese, Brazilian)
---
content/pt/terms.md | 178 ++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 178 insertions(+)
create mode 100644 content/pt/terms.md
diff --git a/content/pt/terms.md b/content/pt/terms.md
new file mode 100644
index 0000000000..a294b49483
--- /dev/null
+++ b/content/pt/terms.md
@@ -0,0 +1,178 @@
+---
+title: Termos de Uso
+sidebar: false
+---
+
+*Última atualização em 4 de janeiro de 2020*
+
+
+## AGREEMENT TO TERMS
+
+These Terms of Use constitute a legally binding agreement made between you, whether personally or on behalf of an entity (“you”) and NumPy ("**Project**", “**we**”, “**us**”, or “**our**”), concerning your access to and use of the numpy.org website as well as any other media form, media channel, mobile website or mobile application related, linked, or otherwise connected thereto (collectively, the “Site”). You agree that by accessing the Site, you have read, understood, and agreed to be bound by all of these Terms of Use. IF YOU DO NOT AGREE WITH ALL OF THESE TERMS OF USE, THEN YOU ARE EXPRESSLY PROHIBITED FROM USING THE SITE AND YOU MUST DISCONTINUE USE IMMEDIATELY.
+
+
+
+Supplemental terms and conditions or documents that may be posted on the Site from time to time are hereby expressly incorporated herein by reference. We reserve the right, in our sole discretion, to make changes or modifications to these Terms of Use at any time and for any reason. We will alert you about any changes by updating the “Last updated” date of these Terms of Use, and you waive any right to receive specific notice of each such change. It is your responsibility to periodically review these Terms of Use to stay informed of updates. You will be subject to, and will be deemed to have been made aware of and to have accepted, the changes in any revised Terms of Use by your continued use of the Site after the date such revised Terms of Use are posted.
+
+
+
+The information provided on the Site is not intended for distribution to or use by any person or entity in any jurisdiction or country where such distribution or use would be contrary to law or regulation or which would subject us to any registration requirement within such jurisdiction or country. Accordingly, those persons who choose to access the Site from other locations do so on their own initiative and are solely responsible for compliance with local laws, if and to the extent local laws are applicable.
+
+
+## USER REPRESENTATIONS
+
+By using the Site, you represent and warrant that: (1) you have the legal capacity and you agree to comply with these Terms of Use; (2) you will not use the Site for any illegal or unauthorized purpose; and (3) your use of the Site will not violate any applicable law or regulation.
+
+
+If you provide any information that is untrue, inaccurate, not current, or incomplete, we have the right to refuse any and all current or future use of the Site (or any portion thereof).
+
+
+## PROHIBITED ACTIVITIES
+
+You may not access or use the Site for any purpose other than that for which we make the Site available.
+
+As a user of the Site, you agree not to:
+
+1. Systematically retrieve data or other content from the Site to create or compile, directly or indirectly, a collection, compilation, database, or directory without written permission from us.
+
+2. Make any unauthorized use of the Site, including collecting usernames and/or email addresses of users by electronic or other means for the purpose of sending unsolicited email, or creating user accounts by automated means or under false pretenses.
+
+3. Use the Site to advertise or offer to sell goods and services.
+
+4. Circumvent, disable, or otherwise interfere with security-related features of the Site.
+
+5. Engage in unauthorized framing of or linking to the Site.
+
+6. Trick, defraud, or mislead us and other users, especially in any attempt to learn sensitive account information such as user passwords.
+
+7. Make improper use of our support services or submit false reports of abuse or misconduct.
+
+8. Engage in any automated use of the system, such as using scripts to send comments or messages, or using any data mining, robots, or similar data gathering and extraction tools.
+
+9. Interfere with, disrupt, or create an undue burden on the Site or the networks or services connected to the Site.
+
+10. Attempt to impersonate another user or person or use the username of another user.
+
+11. Use any information obtained from the Site in order to harass, abuse, or harm another person.
+
+12. Disparage, tarnish, or otherwise harm, in our opinion, us and/or the Site.
+
+13. Except as may be the result of standard search engine or Internet browser usage, use, launch, develop, or distribute any automated system, including without limitation, any spider, robot, cheat utility, scraper, or offline reader that accesses the Site, or using or launching any unauthorized script or other software.
+
+14. Upload or transmit (or attempt to upload or to transmit) any material that acts as a passive or active information collection or transmission mechanism, including without limitation, clear graphics interchange formats (“gifs”), 1×1 pixels, web bugs, cookies, or other similar devices (sometimes referred to as “spyware” or “passive collection mechanisms” or “pcms”).
+
+15. Upload or transmit (or attempt to upload or to transmit) viruses, Trojan horses, or other material, including excessive use of capital letters and spamming (continuous posting of repetitive text), that interferes with any party’s uninterrupted use and enjoyment of the Site or modifies, impairs, disrupts, alters, or interferes with the use, features, functions, operation, or maintenance of the Site.
+
+16. Harass, annoy, intimidate, or threaten any of our employees or agents engaged in providing any portion of the Site to you.
+
+17. Attempt to bypass any measures of the Site designed to prevent or restrict access to the Site, or any portion of the Site.
+
+
+## SUBMISSIONS
+
+You acknowledge and agree that any questions, comments, suggestions, ideas, feedback, or other information regarding the Site ("Submissions") provided by you to us are non-confidential and shall become our sole property. We shall own exclusive rights, including all intellectual property rights, and shall be entitled to the unrestricted use and dissemination of these Submissions for any lawful purpose, commercial or otherwise, without acknowledgment or compensation to you. You hereby waive all moral rights to any such Submissions, and you hereby warrant that any such Submissions are original with you or that you have the right to submit such Submissions. You agree there shall be no recourse against us for any alleged or actual infringement or misappropriation of any proprietary right in your Submissions.
+
+## THIRD-PARTY WEBSITES AND CONTENT
+
+The Site may contain (or you may be sent via the Site) links to other websites ("Third-Party Websites") as well as articles, photographs, text, graphics, pictures, designs, music, sound, video, information, applications, software, and other content or items belonging to or originating from third parties ("Third-Party Content"). Such Third-Party Websites and Third-Party Content are not investigated, monitored, or checked for accuracy, appropriateness, or completeness by us, and we are not responsible for any Third-Party Websites accessed through the Site or any Third-Party Content posted on, available through, or installed from the Site, including the content, accuracy, offensiveness, opinions, reliability, privacy practices, or other policies of or contained in the Third-Party Websites or the Third-Party Content. Inclusion of, linking to, or permitting the use or installation of any Third-Party Websites or any Third-Party Content does not imply approval or endorsement thereof by us. If you decide to leave the Site and access the Third-Party Websites or to use or install any Third-Party Content, you do so at your own risk, and you should be aware these Terms of Use no longer govern. You should review the applicable terms and policies, including privacy and data gathering practices, of any website to which you navigate from the Site or relating to any applications you use or install from the Site. Any purchases you make through Third-Party Websites will be through other websites and from other companies, and we take no responsibility whatsoever in relation to such purchases which are exclusively between you and the applicable third party. You agree and acknowledge that we do not endorse the products or services offered on Third-Party Websites and you shall hold us harmless from any harm caused by your purchase of such products or services. Additionally, you shall hold us harmless from any losses sustained by you or harm caused to you relating to or resulting in any way from any Third-Party Content or any contact with Third-Party Websites.
+
+
+## SITE MANAGEMENT
+
+We reserve the right, but not the obligation, to: (1) monitor the Site for violations of these Terms of Use; (2) take appropriate legal action against anyone who, in our sole discretion, violates the law or these Terms of Use, including without limitation, reporting such user to law enforcement authorities; (3) in our sole discretion and without limitation, refuse, restrict access to, limit the availability of, or disable (to the extent technologically feasible) any of your Contributions or any portion thereof; (4) in our sole discretion and without limitation, notice, or liability, to remove from the Site or otherwise disable all files and content that are excessive in size or are in any way burdensome to our systems; and (5) otherwise manage the Site in a manner designed to protect our rights and property and to facilitate the proper functioning of the Site.
+
+
+## PRIVACY POLICY
+
+We care about data privacy and security. Please review our [Privacy Policy](/privacy). By using the Site, you agree to be bound by our Privacy Policy, which is incorporated into these Terms of Use. Please be advised the Site is hosted in the United States. If you access the Site from the European Union, Asia, or any other region of the world with laws or other requirements governing personal data collection, use, or disclosure that differ from applicable laws in the United States, then through your continued use of the Site, you are transferring your data to the United States, and you expressly consent to have your data transferred to and processed in the United States. Further, we do not knowingly accept, request, or solicit information from children or knowingly market to children. Therefore, in accordance with the U.S. Children’s Online Privacy Protection Act, if we receive actual knowledge that anyone under the age of 13 has provided personal information to us without the requisite and verifiable parental consent, we will delete that information from the Site as quickly as is reasonably practical.
+
+## TERM AND TERMINATION
+
+These Terms of Use shall remain in full force and effect while you use the Site. WITHOUT LIMITING ANY OTHER PROVISION OF THESE TERMS OF USE, WE RESERVE THE RIGHT TO, IN OUR SOLE DISCRETION AND WITHOUT NOTICE OR LIABILITY, DENY ACCESS TO AND USE OF THE SITE (INCLUDING BLOCKING CERTAIN IP ADDRESSES), TO ANY PERSON FOR ANY REASON OR FOR NO REASON, INCLUDING WITHOUT LIMITATION FOR BREACH OF ANY REPRESENTATION, WARRANTY, OR COVENANT CONTAINED IN THESE TERMS OF USE OR OF ANY APPLICABLE LAW OR REGULATION. WE MAY TERMINATE YOUR USE OR PARTICIPATION IN THE SITE OR DELETE ANY CONTENT OR INFORMATION THAT YOU POSTED AT ANY TIME, WITHOUT WARNING, IN OUR SOLE DISCRETION.
+
+
+## MODIFICATIONS AND INTERRUPTIONS
+
+We reserve the right to change, modify, or remove the contents of the Site at any time or for any reason at our sole discretion without notice. However, we have no obligation to update any information on our Site. We also reserve the right to modify or discontinue all or part of the Site without notice at any time. We will not be liable to you or any third party for any modification, suspension, or discontinuance of the Site.
+
+We cannot guarantee the Site will be available at all times. We may experience hardware, software, or other problems or need to perform maintenance related to the Site, resulting in interruptions, delays, or errors. We reserve the right to change, revise, update, suspend, discontinue, or otherwise modify the Site at any time or for any reason without notice to you. You agree that we have no liability whatsoever for any loss, damage, or inconvenience caused by your inability to access or use the Site during any downtime or discontinuance of the Site. Nothing in these Terms of Use will be construed to obligate us to maintain and support the Site or to supply any corrections, updates, or releases in connection therewith.
+
+
+## GOVERNING LAW
+
+These Terms of Use and your use of the Site are governed by and construed in accordance with the laws of the State of Texas applicable to agreements made and to be entirely performed within the State of Texas, without regard to its conflict of law principles.
+
+
+## DISPUTE RESOLUTION
+
+### Informal Negotiations
+
+To expedite resolution and control the cost of any dispute, controversy, or claim related to these Terms of Use (each a "Dispute" and collectively, the “Disputes”) brought by either you or us (individually, a “Party” and collectively, the “Parties”), the Parties agree to first attempt to negotiate any Dispute (except those Disputes expressly provided below) informally for at least thirty (30) days before initiating arbitration. Such informal negotiations commence upon written notice from one Party to the other Party.
+
+
+### Binding Arbitration
+
+If the Parties are unable to resolve a Dispute through informal negotiations, the Dispute (except those Disputes expressly excluded below) will be finally and exclusively resolved by binding arbitration. YOU UNDERSTAND THAT WITHOUT THIS PROVISION, YOU WOULD HAVE THE RIGHT TO SUE IN COURT AND HAVE A JURY TRIAL. The arbitration shall be commenced and conducted under the Commercial Arbitration Rules of the American Arbitration Association ("AAA") and, where appropriate, the AAA’s Supplementary Procedures for Consumer Related Disputes ("AAA Consumer Rules"), both of which are available at the AAA website www.adr.org. Your arbitration fees and your share of arbitrator compensation shall be governed by the AAA Consumer Rules and, where appropriate, limited by the AAA Consumer Rules. If such costs are determined to by the arbitrator to be excessive, we will pay all arbitration fees and expenses. The arbitration may be conducted in person, through the submission of documents, by phone, or online. The arbitrator will make a decision in writing, but need not provide a statement of reasons unless requested by either Party. The arbitrator must follow applicable law, and any award may be challenged if the arbitrator fails to do so. Except where otherwise required by the applicable AAA rules or applicable law, the arbitration will take place in Travis County, Texas. Except as otherwise provided herein, the Parties may litigate in court to compel arbitration, stay proceedings pending arbitration, or to confirm, modify, vacate, or enter judgment on the award entered by the arbitrator.
+
+If for any reason, a Dispute proceeds in court rather than arbitration, the Dispute shall be commenced or prosecuted in the state and federal courts located in Travis County, Texas, and the Parties hereby consent to, and waive all defenses of lack of personal jurisdiction, and forum non conveniens with respect to venue and jurisdiction in such state and federal courts. Application of the United Nations Convention on Contracts for the International Sale of Goods and the the Uniform Computer Information Transaction Act (UCITA) are excluded from these Terms of Use.
+
+In no event shall any Dispute brought by either Party related in any way to the Site be commenced more than one (1) years after the cause of action arose. If this provision is found to be illegal or unenforceable, then neither Party will elect to arbitrate any Dispute falling within that portion of this provision found to be illegal or unenforceable and such Dispute shall be decided by a court of competent jurisdiction within the courts listed for jurisdiction above, and the Parties agree to submit to the personal jurisdiction of that court.
+
+
+### Restrictions
+
+The Parties agree that any arbitration shall be limited to the Dispute between the Parties individually. To the full extent permitted by law, (a) no arbitration shall be joined with any other proceeding; (b) there is no right or authority for any Dispute to be arbitrated on a class-action basis or to utilize class action procedures; and (c) there is no right or authority for any Dispute to be brought in a purported representative capacity on behalf of the general public or any other persons.
+
+
+### Exceptions to Informal Negotiations and Arbitration
+
+The Parties agree that the following Disputes are not subject to the above provisions concerning informal negotiations and binding arbitration: (a) any Disputes seeking to enforce or protect, or concerning the validity of, any of the intellectual property rights of a Party; (b) any Dispute related to, or arising from, allegations of theft, piracy, invasion of privacy, or unauthorized use; and (c) any claim for injunctive relief. If this provision is found to be illegal or unenforceable, then neither Party will elect to arbitrate any Dispute falling within that portion of this provision found to be illegal or unenforceable and such Dispute shall be decided by a court of competent jurisdiction within the courts listed for jurisdiction above, and the Parties agree to submit to the personal jurisdiction of that court.
+
+
+## CORRECTIONS
+
+There may be information on the Site that contains typographical errors, inaccuracies, or omissions. We reserve the right to correct any errors, inaccuracies, or omissions and to change or update the information on the Site at any time, without prior notice.
+
+
+## DISCLAIMER
+
+THE SITE IS PROVIDED ON AN AS-IS AND AS-AVAILABLE BASIS. YOU AGREE THAT YOUR USE OF THE SITE AND OUR SERVICES WILL BE AT YOUR SOLE RISK. TO THE FULLEST EXTENT PERMITTED BY LAW, WE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, IN CONNECTION WITH THE SITE AND YOUR USE THEREOF, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. WE MAKE NO WARRANTIES OR REPRESENTATIONS ABOUT THE ACCURACY OR COMPLETENESS OF THE SITE’S CONTENT OR THE CONTENT OF ANY WEBSITES LINKED TO THE SITE AND WE WILL ASSUME NO LIABILITY OR RESPONSIBILITY FOR ANY (1) ERRORS, MISTAKES, OR INACCURACIES OF CONTENT AND MATERIALS, (2) PERSONAL INJURY OR PROPERTY DAMAGE, OF ANY NATURE WHATSOEVER, RESULTING FROM YOUR ACCESS TO AND USE OF THE SITE, (3) ANY UNAUTHORIZED ACCESS TO OR USE OF OUR SECURE SERVERS AND/OR ANY AND ALL PERSONAL INFORMATION AND/OR FINANCIAL INFORMATION STORED THEREIN, (4) ANY INTERRUPTION OR CESSATION OF TRANSMISSION TO OR FROM THE SITE, (5) ANY BUGS, VIRUSES, TROJAN HORSES, OR THE LIKE WHICH MAY BE TRANSMITTED TO OR THROUGH THE SITE BY ANY THIRD PARTY, AND/OR (6) ANY ERRORS OR OMISSIONS IN ANY CONTENT AND MATERIALS OR FOR ANY LOSS OR DAMAGE OF ANY KIND INCURRED AS A RESULT OF THE USE OF ANY CONTENT POSTED, TRANSMITTED, OR OTHERWISE MADE AVAILABLE VIA THE SITE. WE DO NOT WARRANT, ENDORSE, GUARANTEE, OR ASSUME RESPONSIBILITY FOR ANY PRODUCT OR SERVICE ADVERTISED OR OFFERED BY A THIRD PARTY THROUGH THE SITE, ANY HYPERLINKED WEBSITE, OR ANY WEBSITE OR MOBILE APPLICATION FEATURED IN ANY BANNER OR OTHER ADVERTISING, AND WE WILL NOT BE A PARTY TO OR IN ANY WAY BE RESPONSIBLE FOR MONITORING ANY TRANSACTION BETWEEN YOU AND ANY THIRD-PARTY PROVIDERS OF PRODUCTS OR SERVICES. AS WITH THE PURCHASE OF A PRODUCT OR SERVICE THROUGH ANY MEDIUM OR IN ANY ENVIRONMENT, YOU SHOULD USE YOUR BEST JUDGMENT AND EXERCISE CAUTION WHERE APPROPRIATE.
+
+
+## LIMITATIONS OF LIABILITY
+
+IN NO EVENT WILL WE OR OUR DIRECTORS, EMPLOYEES, OR AGENTS BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, EXEMPLARY, INCIDENTAL, SPECIAL, OR PUNITIVE DAMAGES, INCLUDING LOST PROFIT, LOST REVENUE, LOSS OF DATA, OR OTHER DAMAGES ARISING FROM YOUR USE OF THE SITE, EVEN IF WE HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. NOTWITHSTANDING ANYTHING TO THE CONTRARY CONTAINED HEREIN, OUR LIABILITY TO YOU FOR ANY CAUSE WHATSOEVER AND REGARDLESS OF THE FORM OF THE ACTION, WILL AT ALL TIMES BE LIMITED TO THE AMOUNT PAID, IF ANY, BY YOU TO US DURING THE SIX (6) MONTH PERIOD PRIOR TO ANY CAUSE OF ACTION ARISING. CERTAIN STATE LAWS DO NOT ALLOW LIMITATIONS ON IMPLIED WARRANTIES OR THE EXCLUSION OR LIMITATION OF CERTAIN DAMAGES. IF THESE LAWS APPLY TO YOU, SOME OR ALL OF THE ABOVE DISCLAIMERS OR LIMITATIONS MAY NOT APPLY TO YOU, AND YOU MAY HAVE ADDITIONAL RIGHTS.
+
+
+## INDEMNIFICATION
+
+You agree to defend, indemnify, and hold us harmless, including our subsidiaries, affiliates, and all of our respective officers, agents, partners, and employees, from and against any loss, damage, liability, claim, or demand, including reasonable attorneys’ fees and expenses, made by any third party due to or arising out of: (1) use of the Site; (2) breach of these Terms of Use; (3) any breach of your representations and warranties set forth in these Terms of Use; (4) your violation of the rights of a third party, including but not limited to intellectual property rights; or (5) any overt harmful act toward any other user of the Site with whom you connected via the Site. Notwithstanding the foregoing, we reserve the right, at your expense, to assume the exclusive defense and control of any matter for which you are required to indemnify us, and you agree to cooperate, at your expense, with our defense of such claims. We will use reasonable efforts to notify you of any such claim, action, or proceeding which is subject to this indemnification upon becoming aware of it.
+
+
+## USER DATA
+
+We will maintain certain data that you transmit to the Site for the purpose of managing the performance of the Site, as well as data relating to your use of the Site. Although we perform regular routine backups of data, you are solely responsible for all data that you transmit or that relates to any activity you have undertaken using the Site. You agree that we shall have no liability to you for any loss or corruption of any such data, and you hereby waive any right of action against us arising from any such loss or corruption of such data.
+
+
+## ELECTRONIC COMMUNICATIONS, TRANSACTIONS, AND SIGNATURES
+
+Visiting the Site, sending us emails, and completing online forms constitute electronic communications. You consent to receive electronic communications, and you agree that all agreements, notices, disclosures, and other communications we provide to you electronically, via email and on the Site, satisfy any legal requirement that such communication be in writing. YOU HEREBY AGREE TO THE USE OF ELECTRONIC SIGNATURES, CONTRACTS, ORDERS, AND OTHER RECORDS, AND TO ELECTRONIC DELIVERY OF NOTICES, POLICIES, AND RECORDS OF TRANSACTIONS INITIATED OR COMPLETED BY US OR VIA THE SITE. You hereby waive any rights or requirements under any statutes, regulations, rules, ordinances, or other laws in any jurisdiction which require an original signature or delivery or retention of non-electronic records, or to payments or the granting of credits by any means other than electronic means.
+
+
+## CALIFORNIA USERS AND RESIDENTS
+
+If any complaint with us is not satisfactorily resolved, you can contact the Complaint Assistance Unit of the Division of Consumer Services of the California Department of Consumer Affairs in writing at 1625 North Market Blvd., Suite N 112, Sacramento, California 95834 or by telephone at (800) 952-5210 or (916) 445-1254.
+
+
+## MISCELLANEOUS
+
+These Terms of Use and any policies or operating rules posted by us on the Site or in respect to the Site constitute the entire agreement and understanding between you and us. Our failure to exercise or enforce any right or provision of these Terms of Use shall not operate as a waiver of such right or provision. These Terms of Use operate to the fullest extent permissible by law. We may assign any or all of our rights and obligations to others at any time. We shall not be responsible or liable for any loss, damage, delay, or failure to act caused by any cause beyond our reasonable control. If any provision or part of a provision of these Terms of Use is determined to be unlawful, void, or unenforceable, that provision or part of the provision is deemed severable from these Terms of Use and does not affect the validity and enforceability of any remaining provisions. There is no joint venture, partnership, employment or agency relationship created between you and us as a result of these Terms of Use or use of the Site. You agree that these Terms of Use will not be construed against us by virtue of having drafted them. You hereby waive any and all defenses you may have based on the electronic form of these Terms of Use and the lack of signing by the parties hereto to execute these Terms of Use.
+
+## CONTACT US
+
+In order to resolve a complaint regarding the Site or to receive further information regarding use of the Site, please contact us at:
+
+NumFOCUS, Inc. P.O. Box 90596 Austin, TX, USA 78709 info@numfocus.org +1 (512) 222-5449
+
+
+
From af7b860c9dcefc8959dfeb4428d57200706db942 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:36:00 +0000
Subject: [PATCH 006/909] New translations privacy.md (Portuguese, Brazilian)
---
content/pt/privacy.md | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
create mode 100644 content/pt/privacy.md
diff --git a/content/pt/privacy.md b/content/pt/privacy.md
new file mode 100644
index 0000000000..be4b6613da
--- /dev/null
+++ b/content/pt/privacy.md
@@ -0,0 +1,18 @@
+---
+title: Política de privacidade
+sidebar: false
+---
+
+**numpy.org** é operado por [NumFOCUS, Inc.](https://numfocus.org), o patrocinador fiscal do projeto NumPy. Para a Política de Privacidade deste site, consulte https://numfocus.org/privacy-policy.
+
+Se você tiver alguma dúvida sobre a política ou as práticas de coleta de dados do NumFOCUS, uso e divulgação, entre em contato com a equipe do NumFOCUS em privacy@numfocus.org.
+
+
+
+
+
+
+
+
+
+
From 1a856ca1971c75484e1c3b1abe6a328b5dd13cae Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:36:02 +0000
Subject: [PATCH 007/909] New translations press-kit.md (Portuguese, Brazilian)
---
content/pt/press-kit.md | 8 ++++++++
1 file changed, 8 insertions(+)
create mode 100644 content/pt/press-kit.md
diff --git a/content/pt/press-kit.md b/content/pt/press-kit.md
new file mode 100644
index 0000000000..a59064dca5
--- /dev/null
+++ b/content/pt/press-kit.md
@@ -0,0 +1,8 @@
+---
+title: Kit de imprensa
+sidebar: false
+---
+
+Gostaríamos de facilitar a inclusão da identidade do projeto NumPy em seu próximo documento acadêmico, materiais educacionais ou apresentação.
+
+Você encontrará várias versões de alta resolução do logo do NumPy [aqui](https://github.com/numpy/numpy/tree/master/branding/logo). Note que usando os recursos numpy.org, você aceita o [Código de Conduta do NumPy](/code-of-conduct).
From 17718730255bf276179ae5e794f1240b027946cc Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:36:04 +0000
Subject: [PATCH 008/909] New translations learn.md (Portuguese, Brazilian)
---
content/pt/learn.md | 84 +++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 84 insertions(+)
create mode 100644 content/pt/learn.md
diff --git a/content/pt/learn.md b/content/pt/learn.md
new file mode 100644
index 0000000000..66ef85cc38
--- /dev/null
+++ b/content/pt/learn.md
@@ -0,0 +1,84 @@
+---
+title: Aprenda
+sidebar: false
+---
+
+**A documentação oficial do NumPy mora [aqui](https://numpy.org/doc/stable).**
+
+Abaixo está uma coleção de recursos externos selecionados. Para contribuir, veja o [fim desta página](#add-to-this-list).
+***
+
+## Iniciantes
+
+Há uma tonelada de informações sobre o NumPy lá fora. Se você está começando, recomendamos fortemente estes:
+
+ **Tutoriais**
+
+* [NumPy Quickstart Tutorial (Tutorial de Início Rápido)](https://numpy.org/devdocs/user/quickstart.html)
+* [SciPy Lectures](https://scipy-lectures.org/) Além de incluir conteúdo sobre a NumPy, estas aulas oferecem uma introdução mais ampla ao ecossistema científico do Python.
+* [NumPy: the absolute basics for beginners ("o básico absoluto para inciantes")](https://numpy.org/devdocs/user/absolute_beginners.html)
+* [Machine Learning Plus - Introduction to ndarray](https://www.machinelearningplus.com/python/numpy-tutorial-part1-array-python-examples/)
+* [Edureka - Learn NumPy Arrays with Examples ](https://www.edureka.co/blog/python-numpy-tutorial/)
+* [Dataquest - NumPy Tutorial: Data Analysis with Python](https://www.dataquest.io/blog/numpy-tutorial-python/)
+* [NumPy tutorial *por Nicolas Rougier*](https://github.com/rougier/numpy-tutorial)
+* [Stanford CS231 *by Justin Johnson*](http://cs231n.github.io/python-numpy-tutorial/)
+* [NumPy User Guide (Guia de Usuário NumPy)](https://numpy.org/devdocs)
+
+ **Livros**
+
+* [Guide to NumPy *de Travis E. Oliphant*](http://web.mit.edu/dvp/Public/numpybook.pdf) Essa é uma versão free de 2006. Para a última versão (2015) veja [aqui](https://www.barnesandnoble.com/w/guide-to-numpy-travis-e-oliphant-phd/1122853007).
+* [From Python to NumPy *por Nicolas P. Rougier*](https://www.labri.fr/perso/nrougier/from-python-to-numpy/)
+* [Elegant SciPy](https://www.amazon.com/Elegant-SciPy-Art-Scientific-Python/dp/1491922877) *por Juan Nunez-Iglesias, Stefan van der Walt, e Harriet Dashnow*
+
+Você também pode querer conferir a [lista Goodreads](https://www.goodreads.com/shelf/show/python-scipy) sobre o tema "Python+SciPy. A maioria dos livros lá serão sobre o "ecossistema SciPy", que tem o NumPy em sua essência.
+
+ **Vídeos**
+
+* [Introduction to Numerical Computing with NumPy](http://youtu.be/ZB7BZMhfPgk) *por Alex Chabot-Leclerc*
+
+***
+
+## Avançado
+
+Experimente esses recursos avançados para uma melhor compreensão dos conceitos da NumPy, como indexação avançada, splitting, stacking, álgebra linear e muito mais.
+
+ **Tutoriais**
+
+* [100 NumPy Exercises](http://www.labri.fr/perso/nrougier/teaching/numpy.100/index.html) *por Nicolas P. Rougier*
+* [An Introduction to NumPy and Scipy](https://engineering.ucsb.edu/~shell/che210d/numpy.pdf) *por M. Scott Shell*
+* [Numpy Medkits](http://mentat.za.net/numpy/numpy_advanced_slides/) *por Stéfan van der Walt*
+* [NumPy in Python (Advanced)](https://www.geeksforgeeks.org/numpy-python-set-2-advanced/)
+* [Advanced Indexing](https://www.tutorialspoint.com/numpy/numpy_advanced_indexing.htm)
+* [Machine Learning and Data Analytics with NumPy](https://www.machinelearningplus.com/python/numpy-tutorial-python-part2/)
+
+ **Livros**
+
+* [Python Data Science Handbook](https://www.amazon.com/Python-Data-Science-Handbook-Essential/dp/1491912057) *por Jake Vanderplas*
+* [Python for Data Analysis](https://www.amazon.com/Python-Data-Analysis-Wrangling-IPython/dp/1491957662) *por Wes McKinney*
+* [Numerical Python: Scientific Computing and Data Science Applications with Numpy, SciPy, and Matplotlib](https://www.amazon.com/Numerical-Python-Scientific-Applications-Matplotlib/dp/1484242459) *por Robert Johansson*
+
+ **Vídeos**
+
+* [Advanced NumPy - broadcasting rules, strides, and advanced indexing](https://www.youtube.com/watch?v=cYugp9IN1-Q) *por Juan Nunuz-Iglesias*
+* [Advanced Indexing Operations in NumPy Arrays](https://www.youtube.com/watch?v=2WTDrSkQBng) *por Amuls Academy*
+
+***
+
+## Palestras sobre NumPy
+
+* [The Future of NumPy Indexing](https://www.youtube.com/watch?v=o0EacbIbf58) *por Jaime Fernández* (2016)
+* [Evolution of Array Computing in Python](https://www.youtube.com/watch?v=HVLPJnvInzM&t=10s) *por Ralf Gommers* (2019)
+* [NumPy: what has changed and what is going to change?](https://www.youtube.com/watch?v=YFLVQFjRmPY) *por Matti Picus* (2019)
+* [Inside NumPy](https://www.youtube.com/watch?v=dBTJD_FDVjU) *por Ralf Gommers, Sebastian Berg, Matti Picus, Tyler Reddy, Stefan van der Walt, Charles Harris* (2019)
+* [Brief Review of Array Computing in Python](https://www.youtube.com/watch?v=f176j2g2eNc) *por Travis Oliphant* (2019)
+
+***
+
+## Citando a NumPy
+
+Se a NumPy é importante na sua pesquisa, e você gostaria de dar reconhecimento ao projeto na sua publicação acadêmica, por favor veja [estas informações sobre citações](/citing-numpy).
+
+## Contribua para esta lista
+
+
+Para adicionar a essa coleção, envie uma recomendação [através de um pull request](https://github.com/numpy/numpy.org/blob/master/content/en/learn.md). Diga por que sua recomendação merece ser mencionada nesta página e também qual o público que mais se beneficiaria.
From 782e6aca86eb4e133c8cedfde930667019bf7859 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:36:05 +0000
Subject: [PATCH 009/909] New translations install.md (Portuguese, Brazilian)
---
content/pt/install.md | 142 ++++++++++++++++++++++++++++++++++++++++++
1 file changed, 142 insertions(+)
create mode 100644 content/pt/install.md
diff --git a/content/pt/install.md b/content/pt/install.md
new file mode 100644
index 0000000000..319caaf9e2
--- /dev/null
+++ b/content/pt/install.md
@@ -0,0 +1,142 @@
+---
+title: Instalando o NumPy
+sidebar: false
+---
+
+The only prerequisite for installing NumPy is Python itself. If you don't have Python yet and want the simplest way to get started, we recommend you use the [Anaconda Distribution](https://www.anaconda.com/distribution) - it includes Python, NumPy, and many other commonly used packages for scientific computing and data science.
+
+NumPy can be installed with `conda`, with `pip`, with a package manager on macOS and Linux, or [from source](https://numpy.org/devdocs/user/building.html). For more detailed instructions, consult our [Python and NumPy installation guide](#python-numpy-install-guide) below.
+
+**CONDA**
+
+If you use `conda`, you can install NumPy from the `defaults` or `conda-forge` channels:
+
+```bash
+# Best practice, use an environment rather than install in the base env
+conda create -n my-env
+conda activate my-env
+# If you want to install from conda-forge
+conda config --env --add channels conda-forge
+# The actual install command
+conda install numpy
+```
+
+**PIP**
+
+If you use `pip`, you can install NumPy with:
+
+```bash
+pip install numpy
+```
+Also when using pip, it's good practice to use a virtual environment - see [Reproducible Installs](#reproducible-installs) below for why, and [this guide](https://dev.to/bowmanjd/python-tools-for-managing-virtual-environments-3bko#howto) for details on using virtual environments.
+
+
+
+# Guia de instalação do Python e do NumPy
+
+Installing and managing packages in Python is complicated, there are a number of alternative solutions for most tasks. This guide tries to give the reader a sense of the best (or most popular) solutions, and give clear recommendations. It focuses on users of Python, NumPy, and the PyData (or numerical computing) stack on common operating systems and hardware.
+
+## Recommendations
+
+We'll start with recommendations based on the user's experience level and operating system of interest. If you're in between "beginning" and "advanced", please go with "beginning" if you want to keep things simple, and with "advanced" if you want to work according to best practices that go a longer way in the future.
+
+### Usuários iniciantes
+
+On all of Windows, macOS, and Linux:
+
+- Instale o [Anaconda](https://www.anaconda.com/distribution/) (instala todos os pacotes que você precisa e todas as outras ferramentas mencionadas abaixo).
+- Para escrever e executar código, use notebooks no [JupyterLab](https://jupyterlab.readthedocs.io/en/stable/index.html) para a computação exploratória e interativa, e o [Spyder](https://www.spyder-ide.org/) ou [Visual Studio Code](https://code.visualstudio.com/) para escrever scripts e pacotes.
+- Use o [Anaconda Navigator](https://docs.anaconda.com/anaconda/navigator/) para gerenciar seus pacotes e iniciar o JupyterLab, Spyder ou o Visual Studio Code.
+
+
+### Usuários avançados
+
+#### Windows ou macOS
+
+- Instale o [Miniconda](https://docs.conda.io/en/latest/miniconda.html).
+- Mantenha o ambiente conda `base` mínimo, e use um ou mais [ambientes conda](https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#) para instalar o pacote que você precisa para a tarefa ou projeto em que você está trabalhando.
+- A menos que você esteja satisfeito com apenas os pacotes no canal `defaults`, faça do `conda-forge` seu canal padrão [definindo a prioridade do canal](https://conda-forge.org/docs/user/introduction.html#how-can-i-install-packages-from-conda-forge).
+
+
+#### Linux
+
+If you're fine with slightly outdated packages and prefer stability over being able to use the latest versions of libraries:
+- Use seu gerenciador de pacotes do SO o máximo possível (para o Python, NumPy e outras bibliotecas).
+- Instale pacotes não fornecidos pelo seu gerenciador de pacotes com `pip install algumpacote --user`.
+
+If you use a GPU:
+- Instale o [Miniconda](https://docs.conda.io/en/latest/miniconda.html).
+- Mantenha o ambiente conda `base` mínimo, e use um ou mais [ambientes conda](https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#) para instalar o pacote que você precisa para a tarefa ou projeto em que você está trabalhando.
+- Use o canal conda`defaults` (`conda-forge` não tem bom suporte para pacotes de GPU).
+
+Otherwise:
+- Instale o [Miniforge](https://github.com/conda-forge/miniforge).
+- Mantenha o ambiente conda `base` mínimo, e use um ou mais [ambientes conda](https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#) para instalar o pacote que você precisa para a tarefa ou projeto em que você está trabalhando.
+
+
+#### Alternativa se você preferir pip/PyPI
+
+For users who know, from personal preference or reading about the main differences between conda and pip below, they prefer a pip/PyPI-based solution, we recommend:
+- Instale o Python a partir de, por exemplo, [python.org](https://www.python.org/downloads/), [Homebrew](https://brew.sh/), ou seu gerenciador de pacotes Linux.
+- Use [Poetry](https://python-poetry.org/) como a ferramenta mais bem mantida que fornece um resolvedor de dependências e recursos de gerenciamento de ambiente de forma semelhante ao que o conda faz.
+
+
+## Python package management
+
+Managing packages is a challenging problem, and, as a result, there are lots of tools. For web and general purpose Python development there's a whole [host of tools](https://packaging.python.org/guides/tool-recommendations/) complementary with pip. For high-performance computing (HPC), [Spack](https://github.com/spack/spack) is worth considering. For most NumPy users though, [conda](https://conda.io/en/latest/) and [pip](https://pip.pypa.io/en/stable/) are the two most popular tools.
+
+
+### Pip & conda
+
+The two main tools that install Python packages are `pip` and `conda`. Their functionality partially overlaps (e.g. both can install `numpy`), however, they can also work together. We'll discuss the major differences between pip and conda here - this is important to understand if you want to manage packages effectively.
+
+The first difference is that conda is cross-language and it can install Python, while pip is installed for a particular Python on your system and installs other packages to that same Python install only. This also means conda can install non-Python libraries and tools you may need (e.g. compilers, CUDA, HDF5), while pip can't.
+
+The second difference is that pip installs from the Python Packaging Index (PyPI), while conda installs from its own channels (typically "defaults" or "conda-forge"). PyPI is the largest collection of packages by far, however, all popular packages are available for conda as well.
+
+The third difference is that conda is an integrated solution for managing packages, dependencies and environments, while with pip you may need another tool (there are many!) for dealing with environments or complex dependencies.
+
+
+### Instalações reprodutíveis
+
+As libraries get updated, results from running your code can change, or your code can break completely. It's important to be able to reconstruct the set of packages and versions you're using. Best practice is to:
+
+1. use a different environment per project you're working on,
+2. record package names and versions using your package installer; each has its own metadata format for this:
+ - Conda: [ambientes conda e arquivos environment.yml](https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#)
+ - Pip: [ambientes virtuais](https://docs.python.org/3/tutorial/venv.html) e [requirements.txt](https://pip.readthedocs.io/en/latest/user_guide/#requirements-files)
+ - Poetry: [ambientes virtuais e pyproject.toml](https://python-poetry.org/docs/basic-usage/)
+
+
+
+## NumPy packages & accelerated linear algebra libraries
+
+NumPy doesn't depend on any other Python packages, however, it does depend on an accelerated linear algebra library - typically [Intel MKL](https://software.intel.com/en-us/mkl) or [OpenBLAS](https://www.openblas.net/). Users don't have to worry about installing those (they're automatically included in all NumPy install methods). Power users may still want to know the details, because the used BLAS can affect performance, behavior and size on disk:
+
+- The NumPy wheels on PyPI, which is what pip installs, are built with OpenBLAS. The OpenBLAS libraries are included in the wheel. This makes the wheel larger, and if a user installs (for example) SciPy as well, they will now have two copies of OpenBLAS on disk.
+
+- In the conda defaults channel, NumPy is built against Intel MKL. MKL is a separate package that will be installed in the users' environment when they install NumPy.
+
+- In the conda-forge channel, NumPy is built against a dummy "BLAS" package. When a user installs NumPy from conda-forge, that BLAS package then gets installed together with the actual library - this defaults to OpenBLAS, but it can also be MKL (from the defaults channel), or even [BLIS](https://github.com/flame/blis) or reference BLAS.
+
+- The MKL package is a lot larger than OpenBLAS, it's about 700 MB on disk while OpenBLAS is about 30 MB.
+
+- MKL is typically a little faster and more robust than OpenBLAS.
+
+Besides install sizes, performance and robustness, there are two more things to consider:
+
+- Intel MKL is not open source. For normal use this is not a problem, but if a user needs to redistribute an application built with NumPy, this could be an issue.
+- Both MKL and OpenBLAS will use multi-threading for function calls like `np.dot`, with the number of threads being determined by both a build-time option and an environment variable. Often all CPU cores will be used. This is sometimes unexpected for users; NumPy itself doesn't auto-parallelize any function calls. It typically yields better performance, but can also be harmful - for example when using another level of parallelization with Dask, scikit-learn or multiprocessing.
+
+
+## Troubleshooting
+
+If your installation fails with the message below, see [Troubleshooting ImportError](https://numpy.org/doc/stable/user/troubleshooting-importerror.html).
+
+```
+IMPORTANT: PLEASE READ THIS FOR ADVICE ON HOW TO SOLVE THIS ISSUE!
+
+Importing the numpy c-extensions failed. This error can happen for
+different reasons, often due to issues with your setup.
+```
+
From 7dc5893758ceaa9b3d9a2ebce00b0929c43aa00f Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:36:07 +0000
Subject: [PATCH 010/909] New translations code-of-conduct.md (Portuguese,
Brazilian)
---
content/pt/code-of-conduct.md | 83 +++++++++++++++++++++++++++++++++++
1 file changed, 83 insertions(+)
create mode 100644 content/pt/code-of-conduct.md
diff --git a/content/pt/code-of-conduct.md b/content/pt/code-of-conduct.md
new file mode 100644
index 0000000000..d0088908a0
--- /dev/null
+++ b/content/pt/code-of-conduct.md
@@ -0,0 +1,83 @@
+---
+title: Código de Conduta NumPy
+sidebar: false
+aliases:
+ - /conduct.html
+---
+
+### Introdução
+
+Este código de conduta aplica-se a todos os espaços gerenciados pelo projeto NumPy, incluindo todas as listas de discussão públicas e privadas, *issue tracker*, wikis, blogs, Twitter e qualquer outro canal de comunicação usado pela nossa comunidade. O projeto NumPy não organiza eventos presenciais. No entanto, os eventos relacionados à nossa comunidade devem ter um código de conduta semelhante ao atual.
+
+Este Código de Conduta deve ser honrado por todas as pessoas que participam da comunidade NumPy formal ou informalmente, ou que reivindicam qualquer afiliação com o projeto, em qualquer atividade relacionada ao projeto, especialmente ao representar o projeto, em qualquer função.
+
+Este código não é exaustivo ou completo. Serve para disseminar a nossa compreensão comum de um ambiente colaborativo e de objetivos compartilhados entre nós. Por favor, tente seguir este código tanto na essência quanto ao pé da letra, para criar um ambiente amigável e produtivo que enriqueça a comunidade em geral.
+
+### Diretrizes específicas
+
+Nós nos esforçamos para:
+
+1. Sermos abertos. Convidamos qualquer pessoa a participar da nossa comunidade. Preferimos usar métodos públicos de comunicação para mensagens relacionadas aos projetos, a menos que estejamos discutindo algo sensível. Isso se aplica a mensagens em busca de ajuda ou suporte relacionado ao projeto também; não só é muito mais provável que um pedido de ajuda público resulte em uma resposta, mas isso também garante que qualquer erro involuntário na resposta seja mais facilmente detectado e corrigido.
+2. Sermos empáticos, acolhedores, amigáveis e pacientes. Trabalhamos juntos para resolver conflitos e acreditamos em boas intenções. Todos nós podemos sentir alguma frustração de vez em quando, mas não permitimos que a frustração se transforme num ataque pessoal. Uma comunidade onde as pessoas se sentem desconfortáveis ou ameaçadas não é uma comunidade produtiva.
+3. Sermos colaborativos. O nosso trabalho será utilizado por outras pessoas e, por sua vez, dependeremos do trabalho dos outros. Quando fazemos algo em benefício do projeto, estamos dispostos a explicar aos outros como esse algo funciona, para que outros possam desenvolver o trabalho e torná-lo ainda melhor. Qualquer decisão que tomemos afetará nossos usuários e os colegas, e levamos essas consequências a sério quando tomamos decisões.
+4. Sermos inquisitivos. Ninguém sabe tudo! Fazer perguntas antecipadamente evita muitos problemas mais tarde, por isso encorajamos as perguntas, embora possamos encaminhá-las para um fórum adequado. Vamos nos esforçar para sermos sensíveis e úteis.
+5. Termos cuidado com as palavras que escolhemos. Somos cuidadosos e respeitosos na nossa comunicação e assumimos a responsabilidade pelo nosso próprio discurso. Seja gentil com os outros. Não insulte ou deprecie outros participantes. Nós não aceitaremos assédio ou outros comportamentos exclusivos, como:
+ * Ameaças ou linguagem violenta direcionadas contra outra pessoa.
+ * Piadas e linguagem sexista, racista ou discriminatória.
+ * Postagem de material sexualmente explícito ou violento.
+ * Postar (ou ameaçar postar) informações pessoais de outras pessoas (“doxing”).
+ * Compartilhar conteúdo privado, como e-mails enviados de maneira privada ou não-pública, ou fóruns não registrados, como histórico de canais IRC, sem o consentimento do remetente.
+ * Insultos pessoais, especialmente aqueles que utilizam termos racistas ou sexistas.
+ * Atenção sexual não consentida.
+ * Profanidade excessiva. Por favor, evite palavrões; as pessoas diferem muito na sua sensibilidade à linguagem.
+ * Assédio reiterado. Em geral, se alguém pedir que você pare, então pare.
+ * Advogar em favor ou encorajar qualquer um dos comportamentos acima.
+
+### Declaração de diversidade
+
+O projeto NumPy convida e incentiva a participação de todas as pessoas. Estamos empenhados em ser uma comunidade da qual todas as pessoas gostem de fazer parte. Embora nem sempre sejamos capazes de acomodar as preferências de cada indivíduo, nós tentamos o nosso melhor para tratar todos gentilmente.
+
+Não importa como você se identifica ou como os outros percebem você: nós lhe damos as boas-vindas. Embora nenhuma lista possa esperar ser totalmente abrangente, honramos explicitamente a diversidade em: idade, cultura, etnia, genótipo, identidade ou expressão de gênero, língua, origem, neurotipo, fenotipo, crenças políticas, profissão, raça, religião, orientação sexual, estado socioeconômico, subcultura e capacidade técnica, na medida em que não entrem em conflito com este código de conduta.
+
+Embora sejamos receptivos às pessoas fluentes em todas as línguas, o desenvolvimento do NumPy é conduzido em inglês.
+
+Padrões de comportamento na comunidade NumPy estão detalhados no Código de Conduta acima. Os participantes da nossa comunidade devem se comportar de acordo com esses padrões em todas as suas interações e ajudar os outros a fazê-lo também (veja a próxima seção).
+
+### Diretrizes de Resposta a Incidentes
+
+Sabemos que é mais comum do que o desejado que a comunicação na Internet comece ou se transforme em abusos óbvios e flagrantes. Reconhecemos também que, por vezes, as pessoas podem ter um dia ruim, ou não conhecer algumas das orientações deste Código de Conduta. Tenha isto em mente ao decidir como responder a uma violação deste Código.
+
+Em caso de violações claramente intencionais, o Comitê do Código de Conduta (veja abaixo) deve ser informado. Para violações possivelmente não intencionais, você pode responder à pessoa e apontar este código de conduta (seja em público ou em privado, o que for mais apropriado). Se preferir não o fazer, sinta-se à vontade para informar diretamente o Comitê do Código de Conduta, ou peça ao Comitê um conselho, sigilosamente.
+
+Você pode relatar problemas ao Comitê do Código de Conduta NumPy em numpy-conduct@googlegroups.com.
+
+Atualmente, o comitê é formato por:
+
+* Stefan van der Walt
+* Melissa Weber Mendonça
+* Anirudh Subramanian
+
+Se o seu relatório envolve algum membro da comissão, ou se você sentir que existe um conflito de interesses em tratá-lo, então os membros abster-se-ão de considerar o seu relatório. Como alternativa, se por qualquer razão você se sentir desconfortável em fazer um relatório à comissão, então você também pode entrar em contato com a equipe sênior da NumFOCUS em [conduct@numfocus.org](https://numfocus.org/code-of-conduct#persons-responsible).
+
+### Resolução de Incidentes & Execução do Código de Conduta
+
+_Esta seção resume os pontos mais importantes, mais detalhes podem ser encontrados em_ [Código de Conduta do NumPy - Como dar seguimento a um relatório](/report-handling-manual).
+
+Vamos investigar e responder a todas as queixas. O Comitê do Código de Conduta do NumPy e o Comitê Diretor do NumPy (se envolvido) protegerão a identidade do relatante, e tratarão o conteúdo das reclamações como confidencial (a menos que o relatante aceite o contrário).
+
+Em caso de violações graves e óbvias, por exemplo, ameaça pessoal ou linguagem violenta, sexista ou racista, vamos imediatamente desconectar a pessoa relatada dos canais de comunicação do NumPy; por favor, consulte o manual para mais detalhes.
+
+Em casos que não envolvam claras violações graves e óbvias deste Código de Conduta, o processo de ação referente a qualquer relato de violação do Código de Conduta recebido será:
+
+1. acusar o recebimento do relato,
+2. discussão/feedback razoável,
+3. mediação (se o feedback não ajudar e somente se ambos o relatante e relatado concordarem com isso),
+4. aplicação de solução via decisão transparente (veja as [Resoluções](/report-handling-manual#resolutions)) do Comitê do Código de Conduta.
+
+O comitê responderá a qualquer relatório o mais rapidamente possível e, no máximo, no prazo de 72 horas.
+
+### Notas
+
+Somos gratos aos grupos responsáveis pelos documentos abaixo, dos quais retiramos conteúdo e inspiração:
+
+- [The SciPy Code of Conduct](https://docs.scipy.org/doc/scipy/reference/dev/conduct/code_of_conduct.html)
From dec7b7f739ac24dd60551dd1e07eb8e151eca238 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:36:09 +0000
Subject: [PATCH 011/909] New translations citing-numpy.md (Portuguese,
Brazilian)
---
content/pt/citing-numpy.md | 35 +++++++++++++++++++++++++++++++++++
1 file changed, 35 insertions(+)
create mode 100644 content/pt/citing-numpy.md
diff --git a/content/pt/citing-numpy.md b/content/pt/citing-numpy.md
new file mode 100644
index 0000000000..d390e925e9
--- /dev/null
+++ b/content/pt/citing-numpy.md
@@ -0,0 +1,35 @@
+---
+title: Citando a NumPy
+sidebar: false
+---
+
+Se a NumPy é importante na sua pesquisa, e você gostaria de dar reconhecimento ao projeto na sua publicação acadêmica, sugerimos citar os seguintes documentos:
+
+* Harris, C.R., Millman, K.J., van der Walt, S.J. et al. _Array programming with NumPy_. Nature 585, 357–362 (2020). DOI: [0.1038/s41586-020-2649-2](https://doi.org/10.1038/s41586-020-2649-2). ([Link da editora](https://www.nature.com/articles/s41586-020-2649-2)).
+
+_Em formato BibTeX:_
+
+ ```
+@Article{ harris2020array,
+ title = {Array programming with {NumPy}},
+ author = {Charles R. Harris and K. Jarrod Millman and St{'{e}}fan J.
+ van der Walt and Ralf Gommers and Pauli Virtanen and David
+ Cournapeau and Eric Wieser and Julian Taylor and Sebastian
+ Berg and Nathaniel J. Smith and Robert Kern and Matti Picus
+ and Stephan Hoyer and Marten H. van Kerkwijk and Matthew
+ Brett and Allan Haldane and Jaime Fern{'{a}}ndez del
+ R{'{\i}}o and Mark Wiebe and Pearu Peterson and Pierre
+ G{'{e}}rard-Marchant and Kevin Sheppard and Tyler Reddy and
+ Warren Weckesser and Hameer Abbasi and Christoph Gohlke and
+ Travis E. Oliphant},
+ year = {2020},
+ month = sep,
+ journal = {Nature},
+ volume = {585},
+ number = {7825},
+ pages = {357--362},
+ doi = {10.1038/s41586-020-2649-2},
+ publisher = {Springer Science and Business Media {LLC}},
+ url = {https://doi.org/10.1038/s41586-020-2649-2}
+}
+```
From 9286414c656328f594b414ed8c059e22d58a4768 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:36:11 +0000
Subject: [PATCH 012/909] New translations arraycomputing.md (Portuguese,
Brazilian)
---
content/pt/arraycomputing.md | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
create mode 100644 content/pt/arraycomputing.md
diff --git a/content/pt/arraycomputing.md b/content/pt/arraycomputing.md
new file mode 100644
index 0000000000..941f69fe42
--- /dev/null
+++ b/content/pt/arraycomputing.md
@@ -0,0 +1,21 @@
+---
+title: Computação com Arrays
+sidebar: false
+---
+
+*A computação com arrays é a base para estatística e matemática computacionais, computação científica e suas várias aplicações em ciência e análise de dados, tais como visualização de dados, processamento de sinais digitais, processamento de imagens, bioinformática, aprendizagem de máquina, IA e muitas outras.*
+
+A manipulação e a transformação de dados de grande escala dependem de computação eficiente de alta performance com arrays. A linguagem mais escolhida para análise de dados, aprendizagem de máquina e computação numérica produtiva é **Python.**
+
+**Num**erical **Py**thon (Python Numérico) ou NumPy é a biblioteca em Python padrão para o suporte à utilização de matrizes e arrays multidimensionais de grande porte, e vem com uma vasta coleção de funções matemáticas de alto nível para operar nestas arrays.
+
+Desde o lançamento do NumPy em 2006, o Pandas apareceu em 2008, e nos últimos anos vimos uma sucessão de bibliotecas de computação com arrays aparecerem, ocupando e preenchendo o campo da computação com arrays. Muitas dessas bibliotecas mais recentes imitam recursos e capacidades parecidas com o NumPy e entregam algoritmos e recursos mais recentes voltados para aplicações de aprendizagem de máquina e inteligência artificial.
+
+
+
+A **computação com arrays** é baseada em estruturas de dados chamadas **arrays**. *Arrays* são usadas para organizar grandes quantidades de dados de forma que um conjunto de valores relacionados possa ser facilmente ordenado, obtido, matematicamente manipulado e transformado fácil e rapidamente.
+
+A computação com arrays é *única* pois envolve operar nos valores de um array de dados *de uma vez*. Isso significa que qualquer operação de array se aplica a todo um conjunto de valores de uma só vez. Esta abordagem vetorizada fornece velocidade e simplicidade por permitir que os programadores organizem o código e operem em agregados de dados, sem ter que usar laços com operações escalares individuais.
From ed85c51459992c399e42d3d7dad3e8b00114f81b Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:36:12 +0000
Subject: [PATCH 013/909] New translations about.md (Portuguese, Brazilian)
---
content/pt/about.md | 69 +++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 69 insertions(+)
create mode 100644 content/pt/about.md
diff --git a/content/pt/about.md b/content/pt/about.md
new file mode 100644
index 0000000000..bb240c155e
--- /dev/null
+++ b/content/pt/about.md
@@ -0,0 +1,69 @@
+---
+title: Quem Somos
+sidebar: false
+---
+
+_Algumas informações sobre o projeto NumPy e a comunidade_
+
+NumPy é um projeto de código aberto visando habilitar a computação numérica com Python. Foi criado em 2005, com base no trabalho inicial das bibliotecas Numerical e Numarray. O NumPy sempre será um software 100% de código aberto, livre para que todos usem e disponibilizados sob os termos liberais da [licença BSD modificada](https://github.com/numpy/numpy/blob/master/LICENSE.txt).
+
+O NumPy é desenvolvido no GitHub, através do consenso da comunidade NumPy e de uma comunidade científica em Python mais ampla. Para obter mais informações sobre nossa abordagem de governança, por favor, consulte nosso [Documento de Governança](https://www.numpy.org/devdocs/dev/governance/index.html).
+
+
+## Conselho Diretor (Steering Council)
+
+O papel do Conselho Diretor do NumPy consiste em assegurar o bem-estar a longo prazo do projeto, tanto nos aspectos técnicos quanto na comunidade. Isso é feito através do trabalho com e para a comunidade NumPy em geral. O Conselho Diretor do NumPy atualmente consiste dos seguintes membros (em ordem alfabética):
+
+- Sebastian Berg
+- Jaime Fernández del Río
+- Ralf Gommers
+- Allan Haldane
+- Charles Harris
+- Stephan Hoyer
+- Matti Picus
+- Nathaniel Smith
+- Julian Taylor
+- Pauli Virtanen
+- Stéfan van der Walt
+- Eric Wieser
+
+Membros Eméritos:
+
+- Travis Oliphant (fundador do projeto, 2005-2012)
+- Alex Griffing (2015-2017)
+- Marten van Kerkwijk (2017-2019)
+
+## Times
+
+O projeto NumPy está crescendo; temos equipes para
+
+- código
+- documentação
+- website
+- triagem
+- financiamento e bolsas
+
+Veja a página de [Times](/gallery/team.html) para membros individuais de cada time.
+
+## Patrocinadores
+
+O NumPy recebe financiamento direto das seguintes fontes:
+{{< sponsors >}}
+
+
+## Parceiros Institucionais
+
+Os Parceiros Institucionais são organizações que apoiam o projeto, empregando pessoas que contribuem para a NumPy como parte de seu trabalho. Os parceiros institucionais atuais incluem:
+{{< partners >}}
+
+
+## Doações
+
+Se você achou o NumPy útil no seu trabalho, pesquisa ou empresa, por favor considere fazer uma doação para o projeto que seja compatível com seus recursos. Qualquer quantidade ajuda! Todas as doações serão utilizadas estritamente para financiar o desenvolvimento do software de código aberto da NumPy, documentação e comunidade.
+
+NumPy é um Projeto Patrocinado da NumFOCUS, uma instituição de caridade sem fins lucrativos nos Estados Unidos. A NumFOCUS fornece ao NumPy apoio fiscal, legal e administrativo para ajudar a garantir a saúde e a sustentabilidade do projeto. Visite [numfocus.org](https://numfocus.org) para obter mais informações.
+
+Doações para o NumPy são gerenciadas pela [NumFOCUS](https://numfocus.org). Para doadores nos Estados Unidos, sua doação é dedutível para fins fiscais na medida oferecida pela lei. Como em qualquer doação, você deve consultar seu conselheiro fiscal sobre sua situação fiscal em particular.
+
+O Conselho Diretor da NumPy tomará as decisões sobre a melhor forma de utilizar os fundos recebidos. Prioridades técnicas e de infraestrutura estão documentadas no [NumPy Roadmap](https://www.numpy.org/neps/index.html#roadmap).
+{{< numfocus >}}
From 3bbb473c712bf8c768c64a3828cc4bb96922d1af Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:36:14 +0000
Subject: [PATCH 014/909] New translations 404.md (Portuguese, Brazilian)
---
content/pt/404.md | 8 ++++++++
1 file changed, 8 insertions(+)
create mode 100644 content/pt/404.md
diff --git a/content/pt/404.md b/content/pt/404.md
new file mode 100644
index 0000000000..627cde96d0
--- /dev/null
+++ b/content/pt/404.md
@@ -0,0 +1,8 @@
+---
+title: 404
+sidebar: false
+---
+
+Oops! Você atingiu um beco sem saída.
+
+Se você acha que algo deveria estar aqui, você pode [abrir uma issue](https://github.com/numpy/numpy.org/issues) no GitHub.
From 6bb38b8965e9c54ece4f37d76354e3fdcfff1620 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:36:15 +0000
Subject: [PATCH 015/909] New translations gw-discov.md (Chinese Simplified)
---
content/zh/case-studies/gw-discov.md | 69 ++++++++++++++++++++++++++++
1 file changed, 69 insertions(+)
create mode 100644 content/zh/case-studies/gw-discov.md
diff --git a/content/zh/case-studies/gw-discov.md b/content/zh/case-studies/gw-discov.md
new file mode 100644
index 0000000000..3d25090e13
--- /dev/null
+++ b/content/zh/case-studies/gw-discov.md
@@ -0,0 +1,69 @@
+---
+title: "Case Study: Discovery of Gravitational Waves"
+sidebar: false
+---
+
+{{< figure src="/images/content_images/cs/gw_sxs_image.png" class="fig-center" caption="**Gravitational Waves**" alt="binary coalesce black hole generating gravitational waves" attr="*(Image Credits: The Simulating eXtreme Spacetimes (SXS) Project at LIGO)*" attrlink="https://youtu.be/Zt8Z_uzG71o" >}}
+
+
+
The scientific Python ecosystem is critical infrastructure for the research done at LIGO.
+
+
+
+## About [Gravitational Waves](https://www.nationalgeographic.com/news/2017/10/what-are-gravitational-waves-ligo-astronomy-science/) and [LIGO](https://www.ligo.caltech.edu)
+
+Gravitational waves are ripples in the fabric of space and time, generated by cataclysmic events in the universe such as collision and merging of two black holes or coalescing binary stars or supernovae. Observing GW can not only help in studying gravity but also in understanding some of the obscure phenomena in the distant universe and its impact.
+
+The [Laser Interferometer Gravitational-Wave Observatory (LIGO)](https://www.ligo.caltech.edu) was designed to open the field of gravitational-wave astrophysics through the direct detection of gravitational waves predicted by Einstein’s General Theory of Relativity. It comprises two widely-separated interferometers within the United States — one in Hanford, Washington and the other in Livingston, Louisiana — operated in unison to detect gravitational waves. Each of them has multi-kilometer-scale gravitational wave detectors that use laser interferometry. The LIGO Scientific Collaboration (LSC), is a group of more than 1000 scientists from universities around the United States and in 14 other countries supported by more than 90 universities and research institutes; approximately 250 students actively contributing to the collaboration. The new LIGO discovery is the first observation of gravitational waves themselves, made by measuring the tiny disturbances the waves make to space and time as they pass through the earth. It has opened up new astrophysical frontiers that explore the warped side of the universe—objects and phenomena that are made from warped spacetime.
+
+
+### Key Objectives
+
+* Though its [mission](https://www.ligo.caltech.edu/page/what-is-ligo) is to detect gravitational waves from some of the most violent and energetic processes in the Universe, the data LIGO collects may have far-reaching effects on many areas of physics including gravitation, relativity, astrophysics, cosmology, particle physics, and nuclear physics.
+* Crunch observed data via numerical relativity computations that involves complex maths in order to discern signal from noise, filter out relevant signal and statistically estimate significance of observed data
+* Data visualization so that the binary / numerical results can be comprehended.
+
+
+
+### The Challenges
+
+* **Computation**
+
+ Gravitational Waves are hard to detect as they produce a very small effect and have tiny interaction with matter. Processing and analyzing all of LIGO's data requires a vast computing infrastructure.After taking care of noise, which is billions of times of the signal, there is still very complex relativity equations and huge amounts of data which present a computational challenge: [O(10^7) CPU hrs needed for binary merger analyses](https://youtu.be/7mcHknWWzNI) spread on 6 dedicated LIGO clusters
+
+* **Data Deluge**
+
+ As observational devices become more sensitive and reliable, the challenges posed by data deluge and finding a needle in a haystack rise multi-fold. LIGO generates terabytes of data every day! Making sense of this data requires an enormous effort for each and every detection. For example, the signals being collected by LIGO must be matched by supercomputers against hundreds of thousands of templates of possible gravitational-wave signatures.
+
+* **Visualization**
+
+ Once the obstacles related to understanding Einstein’s equations well enough to solve them using supercomputers are taken care of, the next big challenge was making data comprehensible to the human brain. Simulation modeling as well as signal detection requires effective visualization techniques. Visualization also plays a role in lending more credibility to numerical relativity in the eyes of pure science aficionados, who did not give enough importance to numerical relativity until imaging and simulations made it easier to comprehend results for a larger audience. Speed of complex computations and rendering, re-rendering images and simulations using latest experimental inputs and insights can be a time consuming activity that challenges researchers in this domain.
+
+{{< figure src="/images/content_images/cs/gw_strain_amplitude.png" class="fig-center" alt="gravitational waves strain amplitude" caption="**Estimated gravitational-wave strain amplitude from GW150914**" attr="(**Graph Credits:** Observation of Gravitational Waves from a Binary Black Hole Merger, ResearchGate Publication)" attrlink="https://www.researchgate.net/publication/293886905_Observation_of_Gravitational_Waves_from_a_Binary_Black_Hole_Merger" >}}
+
+## NumPy’s Role in the Detection of Gravitational Waves
+
+Gravitational waves emitted from the merger cannot be computed using any technique except brute force numerical relativity using supercomputers. The amount of data LIGO collects is as incomprehensibly large as gravitational wave signals are small.
+
+NumPy, the standard numerical analysis package for Python, was utilized by the software used for various tasks performed during the GW detection project at LIGO. NumPy helped in solving complex maths and data manipulation at high speed. Here are some examples:
+
+* [Signal Processing](https://www.uv.es/virgogroup/Denoising_ROF.html): Glitch detection, [Noise identification and Data Characterization](https://ep2016.europython.eu/media/conference/slides/pyhton-in-gravitational-waves-research-communities.pdf) (NumPy, scikit-learn, scipy, matplotlib, pandas, pyCharm)
+* Data retrieval: Deciding which data can be analyzed, figuring out whether it contains a signal - needle in a haystack
+* Statistical analysis: estimate the statistical significance of observational data, estimating the signal parameters (e.g. masses of stars, spin velocity, and distance) by comparison with a model.
+* Visualization of data
+ - Time series
+ - Spectrograms
+* Compute Correlations
+* Key [Software](https://github.com/lscsoft) developed in GW data analysis such as [GwPy](https://gwpy.github.io/docs/stable/overview.html) and [PyCBC](https://pycbc.org) uses NumPy and AstroPy under the hood for providing object based interfaces to utilities, tools, and methods for studying data from gravitational-wave detectors.
+
+{{< figure src="/images/content_images/cs/gwpy-numpy-dep-graph.png" class="fig-center" alt="gwpy-numpy depgraph" caption="**Dependency graph showing how GwPy package depends on NumPy**" >}}
+
+----
+
+{{< figure src="/images/content_images/cs/PyCBC-numpy-dep-graph.png" class="fig-center" alt="PyCBC-numpy depgraph" caption="**Dependency graph showing how PyCBC package depends on NumPy**" >}}
+
+## Summary
+
+GW detection has enabled researchers to discover entirely unexpected phenomena while providing new insight into many of the most profound astrophysical phenomena known. Number crunching and data visualization is a crucial step that helps scientists gain insights into data gathered from the scientific observations and understand the results. The computations are complex and cannot be comprehended by humans unless it is visualized using computer simulations that are fed with the real observed data and analysis. NumPy along with other Python packages such as matplotlib, pandas, and scikit-learn is [enabling researchers](https://www.gw-openscience.org/events/GW150914/) to answer complex questions and discover new horizons in our understanding of the universe.
+
+{{< figure src="/images/content_images/cs/numpy_gw_benefits.png" class="fig-center" alt="numpy benefits" caption="**Key NumPy Capabilities utilized**" >}}
From 0c53bbdb7bdbb253cfe54a0fb40108ae9aebd977 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:36:17 +0000
Subject: [PATCH 016/909] New translations news.md (Portuguese, Brazilian)
---
content/pt/news.md | 83 ++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 83 insertions(+)
create mode 100644 content/pt/news.md
diff --git a/content/pt/news.md b/content/pt/news.md
new file mode 100644
index 0000000000..d922c2e0e2
--- /dev/null
+++ b/content/pt/news.md
@@ -0,0 +1,83 @@
+---
+title: Notícias
+sidebar: false
+---
+
+### Diversity in the NumPy project
+
+_Sep 20, 2020_ -- We wrote a [statement on the state of, and discussion on social media around, diversity and inclusion in the NumPy project](/diversity_sep2020).
+
+
+### First official NumPy paper published in Nature!
+
+_Sep 16, 2020_ -- We are pleased to announce the publication of [the first official paper on NumPy](https://www.nature.com/articles/s41586-020-2649-2) as a review article in Nature. This comes 14 years after the release of NumPy 1.0. The paper covers applications and fundamental concepts of array programming, the rich scientific Python ecosystem built on top of NumPy, and the recently added array protocols to facilitate interoperability with external array and tensor libraries like CuPy, Dask, and JAX.
+
+
+### Python 3.9 is coming, when will NumPy release binary wheels?
+
+_Sept 14, 2020_ -- Python 3.9 will be released in a few weeks. If you are an early adopter of Python versions, you may be dissapointed to find that NumPy (and other binary packages like SciPy) will not have binary wheels ready on the day of the release. It is a major effort to adapt the build infrastructure to a new Python version and it typically takes a few weeks for the packages to appear on PyPI and conda-forge. In preparation for this event, please make sure to
+- update your `pip` to version 20.1 at least to support `manylinux2010` and `manylinux2014`
+- use [`--only-binary=numpy`](https://pip.pypa.io/en/stable/reference/pip_install/#cmdoption-only-binary) or `--only-binary=:all:` to prevent `pip` from trying to build from source.
+
+
+### Numpy 1.19.2 release
+
+_Sept 10, 2020_ -- [NumPy 1.19.2](https://numpy.org/devdocs/release/1.19.2-notes.html) is now available. This latest release in the 1.19 series fixes several bugs, prepares for the [upcoming Cython 3.x release](http://docs.cython.org/en/latest/src/changes.html) and pins setuptools to keep distutils working while upstream modifications are ongoing. The aarch64 wheels are built with the latest manylinux2014 release that fixes the problem of differing page sizes used by different linux distros.
+
+### The inaugural NumPy survey is live!
+
+_Jul 2, 2020_ -- This survey is meant to guide and set priorities for decision-making about the development of NumPy as software and as a community. The survey is available in 8 additional languages besides English: Bangla, Hindi, Japanese, Mandarin, Portuguese, Russian, Spanish and French.
+
+Please help us make NumPy better and take the survey [here](https://umdsurvey.umd.edu/jfe/form/SV_8bJrXjbhXf7saAl).
+
+
+### NumPy has a new logo!
+
+_Jun 24, 2020_ -- NumPy now has a new logo:
+
+
+
+The logo is a modern take on the old one, with a cleaner design. Thanks to Isabela Presedo-Floyd for designing the new logo, as well as to Travis Vaught for the old logo that served us well for 15+ years.
+
+
+### NumPy 1.19.0 release
+
+_Jun 20, 2020_ -- NumPy 1.19.0 is now available. This is the first release without Python 2 support, hence it was a "clean-up release". The minimum supported Python version is now Python 3.6. An important new feature is that the random number generation infrastructure that was introduced in NumPy 1.17.0 is now accessible from Cython.
+
+
+### Season of Docs acceptance
+
+_May 11, 2020_ -- NumPy has been accepted as one of the mentor organizations for the Google Season of Docs program. We are excited about the opportunity to work with a technical writer to improve NumPy's documentation once again! For more details, please see [the official Season of Docs site](https://developers.google.com/season-of-docs/) and our [ideas page](https://github.com/numpy/numpy/wiki/Google-Season-of-Docs-2020-Project-Ideas).
+
+
+### NumPy 1.18.0 release
+
+_Dec 22, 2019_ -- NumPy 1.18.0 is now available. After the major changes in 1.17.0, this is a consolidation release. It is the last minor release that will support Python 3.5. Highlights of the release includes the addition of basic infrastructure for linking with 64-bit BLAS and LAPACK libraries, and a new C-API for `numpy.random`.
+
+Please see the [release notes](https://github.com/numpy/numpy/releases/tag/v1.18.0) for more details.
+
+
+### NumPy receives a grant from the Chan Zuckerberg Initiative
+
+_Nov 15, 2019_ -- We are pleased to announce that NumPy and OpenBLAS, one of NumPy's key dependencies, have received a joint grant for $195,000 from the Chan Zuckerberg Initiative through their [Essential Open Source Software for Science program](https://chanzuckerberg.com/eoss/) that supports software maintenance, growth, development, and community engagement for open source tools critical to science.
+
+This grant will be used to ramp up the efforts in improving NumPy documentation, website redesign, and community development to better serve our large and rapidly growing user base, and ensure the long-term sustainability of the project. While the OpenBLAS team will focus on addressing sets of key technical issues, in particular thread-safety, AVX-512, and thread-local storage (TLS) issues, as well as algorithmic improvements in ReLAPACK (Recursive LAPACK) on which OpenBLAS depends.
+
+More details on our proposed initiatives and deliverables can be found in the [full grant proposal](https://figshare.com/articles/Proposal_NumPy_OpenBLAS_for_Chan_Zuckerberg_Initiative_EOSS_2019_round_1/10302167). The work is scheduled to start on Dec 1st, 2019 and continue for the next 12 months.
+
+
+## Lançamentos
+
+Here is a list of NumPy releases, with links to release notes. All bugfix releases (only the `z` changes in the `x.y.z` version number) have no new features; minor releases (the `y` increases) do.
+
+- NumPy 1.18.4 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.18.4)) -- _3 May 2020_.
+- NumPy 1.18.3 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.18.3)) -- _19 Apr 2020_.
+- NumPy 1.18.2 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.18.2)) -- _17 Mar 2020_.
+- NumPy 1.18.1 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.18.1)) -- _6 Jan 2020_.
+- NumPy 1.17.5 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.17.5)) -- _1 Jan 2020_.
+- NumPy 1.18.0 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.18.0)) -- _22 Dec 2019_.
+- NumPy 1.17.4 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.17.4)) -- _11 Nov 2019_.
+- NumPy 1.17.0 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.17.0)) -- _26 Jul 2019_.
+- NumPy 1.16.0 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.16.0)) -- _14 Jan 2019_.
+- NumPy 1.15.0 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.15.0)) -- _23 Jul 2018_.
+- NumPy 1.14.0 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.14.0)) -- _7 Jan 2018_.
From 7b30ca681e69c9912292521564b45dd8bc36662b Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:36:19 +0000
Subject: [PATCH 017/909] New translations deeplabcut-dnn.md (Chinese
Simplified)
---
content/zh/case-studies/deeplabcut-dnn.md | 90 +++++++++++++++++++++++
1 file changed, 90 insertions(+)
create mode 100644 content/zh/case-studies/deeplabcut-dnn.md
diff --git a/content/zh/case-studies/deeplabcut-dnn.md b/content/zh/case-studies/deeplabcut-dnn.md
new file mode 100644
index 0000000000..b40ed2af50
--- /dev/null
+++ b/content/zh/case-studies/deeplabcut-dnn.md
@@ -0,0 +1,90 @@
+---
+title: "Case Study: DeepLabCut 3D Pose Estimation"
+sidebar: false
+---
+
+{{< figure src="/images/content_images/cs/mice-hand.gif" class="fig-center" caption="**Analyzing mice hand-movement using DeepLapCut**" alt="micehandanim" attr="*(Source: www.deeplabcut.org )*" attrlink="http://www.mousemotorlab.org/deeplabcut">}}
+
+
+
Open Source Software is accelerating Biomedicine. DeepLabCut enables automated video analysis of animal behavior using Deep Learning.
+
+
+
+## About DeepLabCut
+
+[DeepLabCut](https://github.com/DeepLabCut/DeepLabCut) is an open source toolbox that empowers researchers at hundreds of institutions worldwide to track behaviour of laboratory animals, with very little training data, at human-level accuracy. With DeepLabCut technology, scientists can delve deeper into the scientific understanding of motor control and behavior across animal species and timescales.
+
+Several areas of research, including neuroscience, medicine, and biomechanics, use data from tracking animal movement. DeepLabCut helps in understanding what humans and other animals are doing by parsing actions that have been recorded on film. Using automation for laborious tasks of tagging and monitoring, along with deep neural network based data analysis, DeepLabCut makes scientific studies involving observing animals, such as primates, mice, fish, flies etc., much faster and more accurate.
+
+{{< figure src="/images/content_images/cs/race-horse.gif" class="fig-center" caption="**Colored dots track the positions of a racehorse’s body part**" alt="horserideranim" attr="*(Source: Mackenzie Mathis)*">}}
+
+DeepLabCut's non-invasive behavioral tracking of animals by extracting the poses of animals is crucial for scientific pursuits in domains such as biomechanics, genetics, ethology & neuroscience. Measuring animal poses non-invasively from video - without markers - in dynamically changing backgrounds is computationally challenging, both technically as well as in terms of resource needs and training data required.
+
+DeepLabCut allows researchers to estimate the pose of the subject, efficiently enabling them to quantify the behavior through a Python based software toolkit. With DeepLabCut, researchers can identify distinct frames from videos, digitally label specific body parts in a few dozen frames with a tailored GUI, and then the deep learning based pose estimation architectures in DeepLabCut learn how to pick out those same features in the rest of the video and in other similar videos of animals. It works across species of animals, from common laboratory animals such as flies and mice to more unusual animals like [cheetahs][cheetah-movement].
+
+DeepLabCut uses a principle called [transfer learning](https://arxiv.org/pdf/1909.11229), which greatly reduces the amount of training data required and speeds up the convergence of the training period. Depending on the needs, users can pick different network architectures that provide faster inference (e.g. MobileNetV2), which can also be combined with real-time experimental feedback. DeepLabCut originally used the feature detectors from a top-performing human pose estimation architecture, called [DeeperCut](https://arxiv.org/abs/1605.03170), which inspired the name. The package now has been significantly changed to include additional architectures, augmentation methods, and a full front-end user experience. Furthermore, to support large-scale biological experiments DeepLabCut provides active learning capabilities so that users can increase the training set over time to cover edge cases and make their pose estimation algorithm robust within the specific context.
+
+Recently, the [DeepLabCut model zoo](http://www.mousemotorlab.org/dlc-modelzoo) was introduced, which provides pre-trained models for various species and experimental conditions from facial analysis in primates to dog posture. This can be run for instance in the cloud without any labeling of new data, or neural network training, and no programming experience is necessary.
+
+### Key Goals and Results
+
+* **Automation of animal pose analysis for scientific studies:**
+
+ The primary objective of DeepLabCut technology is to measure and track posture of animals in a diverse settings. This data can be used, for example, in neuroscience studies to understand how the brain controls movement, or to elucidate how animals socially interact. Researchers have observed a [tenfold performance boost](https://www.biorxiv.org/content/10.1101/457242v1) with DeepLabCut. Poses can be inferred offline at up to 1200 frames per second (FPS).
+
+* **Creation of an easy-to-use Python toolkit for pose estimation:**
+
+ DeepLabCut wanted to share their animal pose-estimation technology in the form of an easy to use tool that can be adopted by researchers easily. So they have created a complete, easy-to-use Python toolbox with project management features as well. These enable not only automation of pose-estimation but also managing the project end-to-end by helping the DeepLabCut Toolkit user right from the dataset collection stage to creating shareable and reusable analysis pipelines.
+
+ Their [toolkit][DLCToolkit] is now available as open source.
+
+ A typical DeepLabCut Workflow includes:
+
+ - creation and refining of training sets via active learning
+ - creation of tailored neural networks for specific animals and scenarios
+ - code for large-scale inference on videos
+ - draw inferences using integrated visualization tools
+
+{{< figure src="/images/content_images/cs/deeplabcut-toolkit-steps.png" class="csfigcaption" caption="**Pose estimation steps with DeepLabCut**" alt="dlcsteps" align="middle" attr="(Source: DeepLabCut)" attrlink="https://twitter.com/DeepLabCut/status/1198046918284210176/photo/1" >}}
+
+### The Challenges
+
+* **Speed**
+
+ Fast processing of animal behavior videos in order to measure their behavior and at the same time make scientific experiments more efficient, accurate. Extracting detailed animal poses for laboratory experiments, without markers, in dynamically changing backgrounds, can be challenging, both technically as well as in terms of resource needs and training data required. Coming up with a tool that is easy to use without the need for skills such as computer vision expertise that enables scientists to do research in more real-world contexts, is a non-trivial problem to solve.
+
+* **Combinatorics**
+
+ Combinatorics involves assembly and integration of movement of multiple limbs into individual animal behavior. Assembling keypoints and their connections into individual animal movements and linking them across time is a complex process that requires heavy-duty numerical analysis, especially in case of multi-animal movement tracking in experiment videos.
+
+* **Data Processing**
+
+ Last but not the least, array manipulation - processing large stacks of arrays corresponding to various images, target tensors and keypoints is fairly challenging.
+
+{{< figure src="/images/content_images/cs/pose-estimation.png" class="csfigcaption" caption="**Pose estimation variety and complexity**" alt="challengesfig" align="middle" attr="(Source: Mackenzie Mathis)" attrlink="https://www.biorxiv.org/content/10.1101/476531v1.full.pdf" >}}
+
+## NumPy's Role in meeting Pose Estimation Challenges
+
+NumPy addresses DeepLabCut technology's core need of numerical computations at high speed for behavioural analytics. Besides NumPy, DeepLabCut employs various Python software that utilize NumPy at their core, such as [SciPy](https://www.scipy.org), [Pandas](https://pandas.pydata.org), [matplotlib](https://matplotlib.org), [Tensorpack](https://github.com/tensorpack/tensorpack), [imgaug](https://github.com/aleju/imgaug), [scikit-learn](https://scikit-learn.org/stable/), [scikit-image](https://scikit-image.org) and [Tensorflow](https://www.tensorflow.org).
+
+The following features of NumPy played a key role in addressing the image processing, combinatorics requirements and need for fast computation in DeepLabCut pose estimation algorithms:
+
+* Vectorization
+* Masked Array Operations
+* Linear Algebra
+* Random Sampling
+* Reshaping of large arrays
+
+DeepLabCut utilizes NumPy’s array capabilities throughout the workflow offered by the toolkit. In particular, NumPy is used for sampling distinct frames for human annotation labeling, and for writing, editing and processing annotation data. Within TensorFlow the neural network is trained by DeepLabCut technology over thousands of iterations to predict the ground truth annotations from frames. For this purpose, target densities (scoremaps) are created to cast pose estimation as a image-to-image translation problem. To make the neural networks robust, data augmentation is employed, which requires the calculation of target scoremaps subject to various geometric and image processing steps. To make training fast, NumPy’s vectorization capabilities are leveraged. For inference, the most likely predictions from target scoremaps need to extracted and one needs to efficiently “link predictions to assemble individual animals”.
+
+{{< figure src="/images/content_images/cs/deeplabcut-workflow.png" class="fig-center" caption="**DeepLabCut Workflow**" alt="workflow" attr="*(Source: Mackenzie Mathis)*" attrlink="https://www.researchgate.net/figure/DeepLabCut-work-flow-The-diagram-delineates-the-work-flow-as-well-as-the-directory-and_fig1_329185962">}}
+
+## Summary
+
+Observing and efficiently describing behavior is a core tenant of modern ethology, neuroscience, medicine, and technology. [DeepLabCut](http://orga.cvss.cc/wp-content/uploads/2019/05/NathMathis2019.pdf) allows researchers to estimate the pose of the subject, efficiently enabling them to quantify the behavior. With only a small set of training images, the DeepLabCut Python toolbox allows training a neural network to within human level labeling accuracy, thus expanding its application to not only behavior analysis in the laboratory, but to potentially also in sports, gait analysis, medicine and rehabilitation studies. Complex combinatorics, data processing challenges faced by DeepLabCut algorithms are addressed through the use of NumPy's array manipulation capabilities.
+
+{{< figure src="/images/content_images/cs/numpy_dlc_benefits.png" class="fig-center" alt="numpy benefits" caption="**Key NumPy Capabilities utilized**" >}}
+
+[cheetah-movement]: https://www.technologynetworks.com/neuroscience/articles/interview-a-deeper-cut-into-behavior-with-mackenzie-mathis-327618
+
+[DLCToolkit]: https://github.com/DeepLabCut/DeepLabCut
From ec9dc56667fd5c3109cd2d3c67b841a47979deaf Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:36:21 +0000
Subject: [PATCH 018/909] New translations cricket-analytics.md (Chinese
Simplified)
---
content/zh/case-studies/cricket-analytics.md | 64 ++++++++++++++++++++
1 file changed, 64 insertions(+)
create mode 100644 content/zh/case-studies/cricket-analytics.md
diff --git a/content/zh/case-studies/cricket-analytics.md b/content/zh/case-studies/cricket-analytics.md
new file mode 100644
index 0000000000..987b38fb68
--- /dev/null
+++ b/content/zh/case-studies/cricket-analytics.md
@@ -0,0 +1,64 @@
+---
+title: "Case Study: Cricket Analytics, the game changer!"
+sidebar: false
+---
+
+{{< figure src="/images/content_images/cs/ipl-stadium.png" caption="**IPLT20, the biggest Cricket Festival in India**" alt="Indian Premier League Cricket cup and stadium" attr="*(Image credits: IPLT20 (cup and logo) & Akash Yadav (stadium))*" attrlink="https://unsplash.com/@aksh1802" >}}
+
+
+
You don't play for the crowd, you play for the country.
+
+
+
+## About Cricket
+
+It would be an understatement to state that Indians love cricket. The game is played in just about every nook and cranny of India, rural or urban, popular with the young and the old alike, connecting billions in India unlike any other sport. Cricket enjoys lots of media attention. There is a significant amount of [money](https://www.statista.com/topics/4543/indian-premier-league-ipl/) and fame at stake. Over the last several years, technology has literally been a game changer. Audiences are spoilt for choice with streaming media, tournaments, affordable access to mobile based live cricket watching, and more.
+
+The Indian Premier League (IPL) is a professional Twenty20 cricket league, founded in 2008. It is one of the most attended cricketing events in the world, valued at [$6.7 billion](https://en.wikipedia.org/wiki/Indian_Premier_League) in 2019.
+
+Cricket is a game of numbers - the runs scored by a batsman, the wickets taken by a bowler, the matches won by a cricket team, the number of times a batsman responds in a certain way to a kind of bowling attack, etc. The capability to dig into cricketing numbers for both improving performance and studying the business opportunities, overall market, and economics of cricket via powerful analytics tools, powered by numerical computing software such as NumPy, is a big deal. Cricket analytics provides interesting insights into the game and predictive intelligence regarding game outcomes.
+
+Today, there are rich and almost infinite troves of cricket game records and statistics available, e.g., [ESPN cricinfo](https://stats.espncricinfo.com/ci/engine/stats/index.html) and [cricsheet](https://cricsheet.org). These and several such cricket databases have been used for [cricket analysis](https://www.researchgate.net/publication/336886516_Data_visualization_and_toss_related_analysis_of_IPL_teams_and_batsmen_performances) using the latest machine learning and predictive modelling algorithms. Media and entertainment platforms along with professional sports bodies associated with the game use technology and analytics for determining key metrics for improving match winning chances:
+
+* batting performance moving average,
+* score forecasting,
+* gaining insights into fitness and performance of a player against different opposition,
+* player contribution to wins and losses for making strategic decisions on team composition
+
+{{< figure src="/images/content_images/cs/cricket-pitch.png" class="csfigcaption" caption="**Cricket Pitch, the focal point in the field**" alt="A cricket pitch with bowler and batsmen" align="middle" attr="*(Image credit: Debarghya Das)*" attrlink="http://debarghyadas.com/files/IPLpaper.pdf" >}}
+
+### Key Data Analytics Objectives
+
+* Sports data analytics are used not only in cricket but many [other sports](https://adtmag.com/blogs/dev-watch/2017/07/sports-analytics.aspx) for improving the overall team performance and maximizing winning chances.
+* Real-time data analytics can help in gaining insights even during the game for changing tactics by the team and by associated businesses for economic benefits and growth.
+* Besides historical analysis, predictive models are harnessed to determine the possible match outcomes that require significant number crunching and data science know-how, visualization tools and capability to include newer observations in the analysis.
+
+{{< figure src="/images/content_images/cs/player-pose-estimator.png" class="fig-center" alt="pose estimator" caption="**Cricket Pose Estimator**" attr="*(Image credit: connect.vin)*" attrlink="https://connect.vin/2019/05/ai-for-cricket-batsman-pose-analysis/" >}}
+
+### The Challenges
+
+* **Data Cleaning and preprocessing**
+
+ IPL has expanded cricket beyond the classic test match format to a much larger scale. The number of matches played every season across various formats has increased and so has the data, the algorithms, newer sports data analysis technologies and simulation models. Cricket data analysis requires field mapping, player tracking, ball tracking, player shot analysis, and several other aspects involved in how the ball is delivered, its angle, spin, velocity, and trajectory. All these factors together have increased the complexity of data cleaning and preprocessing.
+
+* **Dynamic Modeling**
+
+ In cricket, just like any other sport, there can be a large number of variables related to tracking various numbers of players on the field, their attributes, the ball, and several possibilities of potential actions. The complexity of data analytics and modeling is directly proportional to the kind of predictive questions that are put forth during analysis and are highly dependent on data representation and the model. Things get even more challenging in terms of computation, data comparisons when dynamic cricket play predictions are sought such as what would have happened if the batsman had hit the ball at a different angle or velocity.
+
+* **Predictive Analytics Complexity**
+
+ Much of the decision making in cricket is based on questions such as "how often does a batsman play a certain kind of shot if the ball delivery is of a particular type", or "how does a bowler change his line and length if the batsman responds to his delivery in a certain way". This kind of predictive analytics query requires highly granular dataset availability and the capability to synthesize data and create generative models that are highly accurate.
+
+## NumPy’s Role in Cricket Analytics
+
+Sports Analytics is a thriving field. Many researchers and companies [use NumPy](https://adtmag.com/blogs/dev-watch/2017/07/sports-analytics.aspx) and other PyData packages like Scikit-learn, SciPy, Matplotlib, and Jupyter, besides using the latest machine learning and AI techniques. NumPy has been used for various kinds of cricket related sporting analytics such as:
+
+* **Statistical Analysis:** NumPy's numerical capabilities help estimate the statistical significance of observational data or match events in the context of various player and game tactics, estimating the game outcome by comparison with a generative or static model. [Causal analysis](https://amplitude.com/blog/2017/01/19/causation-correlation) and [big data approaches](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4996805/) are used for tactical analysis.
+
+* **Data Visualization:** Data graphing and [visualization](https://towardsdatascience.com/advanced-sports-visualization-with-pandas-matplotlib-and-seaborn-9c16df80a81b) provides useful insights into relationship between various datasets.
+
+## Summary
+
+Sports Analytics is a game changer when it comes to how professional games are played, especially how strategic decision making happens, which until recently was primarily done based on “gut feeling" or adherence to past traditions. NumPy forms a solid foundation for a large set of Python packages which provide higher level functions related to data analytics, machine learning, and AI algorithms. These packages are widely deployed to gain real-time insights that help in decision making for game-changing outcomes, both on field as well as to draw inferences and drive business around the game of cricket. Finding out the hidden parameters, patterns, and attributes that lead to the outcome of a cricket match helps the stakeholders to take notice of game insights that are otherwise hidden in numbers and statistics.
+
+{{< figure src="/images/content_images/cs/numpy_ca_benefits.png" class="fig-center" alt="Diagram showing benefits of using NumPy for cricket analytics" caption="**Key NumPy Capabilities utilized**" >}}
From 66b7e6279d5fa3e59f5f22b68fac5c322d3768ed Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:36:22 +0000
Subject: [PATCH 019/909] New translations blackhole-image.md (Chinese
Simplified)
---
content/zh/case-studies/blackhole-image.md | 70 ++++++++++++++++++++++
1 file changed, 70 insertions(+)
create mode 100644 content/zh/case-studies/blackhole-image.md
diff --git a/content/zh/case-studies/blackhole-image.md b/content/zh/case-studies/blackhole-image.md
new file mode 100644
index 0000000000..f2460d3d5b
--- /dev/null
+++ b/content/zh/case-studies/blackhole-image.md
@@ -0,0 +1,70 @@
+---
+title: "Case Study: First Image of a Black Hole"
+sidebar: false
+---
+
+{{< figure src="/images/content_images/cs/blackhole.jpg" caption="**Black Hole M87**" alt="black hole image" attr="*(Image Credits: Event Horizon Telescope Collaboration)*" attrlink="https://www.jpl.nasa.gov/images/universe/20190410/blackhole20190410.jpg" >}}
+
+
+
Imaging the M87 Black Hole is like trying to see something that is by definition impossible to see.
+
+
+
+## A telescope the size of the earth
+
+The [Event Horizon telescope (EHT)](https://eventhorizontelescope.org) is an array of eight ground-based radio telescopes forming a computational telescope the size of the earth, studing the universe with unprecedented sensitivity and resolution. The huge virtual telescope, which uses a technique called very-long-baseline interferometry (VLBI), has an angular resolution of [20 micro-arcseconds][resolution] — enough to read a newspaper in New York from a sidewalk café in Paris!
+
+### Key Goals and Results
+
+* **A New View of the Universe:** The groundwork for the EHT's groundbreaking image had been laid 100 years earlier when [Sir Arthur Eddington][eddington] yielded the first observational support of Einstein's theory of general relativity.
+
+* **The Black Hole:** EHT was trained on a supermassive black hole approximately 55 million light-years from Earth, lying at the center of the galaxy Messier 87 (M87) in the Virgo galaxy cluster. Its mass is 6.5 billion times the Sun's. It had been studied for [over 100 years](https://www.jpl.nasa.gov/news/news.php?feature=7385), but never before had a black hole been visually observed.
+
+* **Comparing Observations to Theory:** From Einstein’s general theory of relativity, scientists expected to find a shadow-like region caused by gravitational bending and capture of light. Scientists could use it to measure the black hole's enormous mass.
+
+### The Challenges
+
+* **Computational scale**
+
+ EHT poses massive data-processing challenges, including rapid atmospheric phase fluctuations, large recording bandwidth, and telescopes that are widely dissimilar and geographically dispersed.
+
+* **Too much information**
+
+ Each day EHT generates over 350 terabytes of observations, stored on helium-filled hard drives. Reducing the volume and complexity of this much data is enormously difficult.
+
+* **Into the unknown**
+
+ When the goal is to see something never before seen, how can scientists be confident the image is correct?
+
+{{< figure src="/images/content_images/cs/dataprocessbh.png" class="csfigcaption" caption="**EHT Data Processing Pipeline**" alt="data pipeline" align="middle" attr="(Diagram Credits: The Astrophysical Journal, Event Horizon Telescope Collaboration)" attrlink="https://iopscience.iop.org/article/10.3847/2041-8213/ab0c57" >}}
+
+## NumPy’s Role
+
+What if there's a problem with the data? Or perhaps an algorithm relies too heavily on a particular assumption. Will the image change drastically if a single parameter is changed?
+
+The EHT collaboration met these challenges by having independent teams evaluate the data, using both established and cutting-edge image reconstruction techniques. When results proved consistent, they were combined to yield the first-of-a-kind image of the black hole.
+
+Their work illustrates the role the scientific Python ecosystem plays in advancing science through collaborative data analysis.
+
+{{< figure src="/images/content_images/cs/bh_numpy_role.png" class="fig-center" alt="role of numpy" caption="**The role of NumPy in Black Hole imaging**" >}}
+
+For example, the [`eht-imaging`][ehtim] Python package provides tools for simulating and performing image reconstruction on VLBI data. NumPy is at the core of array data processing used in this package, as illustrated by the partial software dependency chart below.
+
+{{< figure src="/images/content_images/cs/ehtim_numpy.png" class="fig-center" alt="ehtim dependency map highlighting numpy" caption="**Software dependency chart of ehtim package highlighting NumPy**" >}}
+
+Besides NumPy, many other packages, such as [SciPy](https://www.scipy.org) and [Pandas](https://pandas.io), are part of the data processing pipeline for imaging the black hole. The standard astronomical file formats and time/coordinate transformations were handled by [Astropy][astropy], while [Matplotlib][mpl] was used in visualizing data throughout the analysis pipeline, including the generation of the final image of the black hole.
+
+## Summary
+
+The efficient and adaptable n-dimensional array that is NumPy's central feature enabled researchers to manipulate large numerical datasets, providing a foundation for the first-ever image of a black hole. A landmark moment in science, it gives stunning visual evidence of Einstein’s theory. The achievement encompasses not only technological breakthroughs but also international collaboration among over 200 scientists and some of the world's best radio observatories. Innovative algorithms and data processing techniques, improving upon existing astronomical models, helped unfold a mystery of the universe.
+
+{{< figure src="/images/content_images/cs/numpy_bh_benefits.png" class="fig-center" alt="numpy benefits" caption="**Key NumPy Capabilities utilized**" >}}
+
+[resolution]: https://eventhorizontelescope.org/press-release-april-10-2019-astronomers-capture-first-image-black-hole
+
+[eddington]: https://en.wikipedia.org/wiki/Eddington_experiment
+
+[ehtim]: https://github.com/achael/eht-imaging
+
+[astropy]: https://www.astropy.org/
+[mpl]: https://matplotlib.org/
From e5987804012542482011ceda7c955caf91bf8f31 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:36:24 +0000
Subject: [PATCH 020/909] New translations news.md (Chinese Simplified)
---
content/zh/news.md | 83 ++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 83 insertions(+)
create mode 100644 content/zh/news.md
diff --git a/content/zh/news.md b/content/zh/news.md
new file mode 100644
index 0000000000..5dcb849596
--- /dev/null
+++ b/content/zh/news.md
@@ -0,0 +1,83 @@
+---
+title: News
+sidebar: false
+---
+
+### Diversity in the NumPy project
+
+_Sep 20, 2020_ -- We wrote a [statement on the state of, and discussion on social media around, diversity and inclusion in the NumPy project](/diversity_sep2020).
+
+
+### First official NumPy paper published in Nature!
+
+_Sep 16, 2020_ -- We are pleased to announce the publication of [the first official paper on NumPy](https://www.nature.com/articles/s41586-020-2649-2) as a review article in Nature. This comes 14 years after the release of NumPy 1.0. The paper covers applications and fundamental concepts of array programming, the rich scientific Python ecosystem built on top of NumPy, and the recently added array protocols to facilitate interoperability with external array and tensor libraries like CuPy, Dask, and JAX.
+
+
+### Python 3.9 is coming, when will NumPy release binary wheels?
+
+_Sept 14, 2020_ -- Python 3.9 will be released in a few weeks. If you are an early adopter of Python versions, you may be dissapointed to find that NumPy (and other binary packages like SciPy) will not have binary wheels ready on the day of the release. It is a major effort to adapt the build infrastructure to a new Python version and it typically takes a few weeks for the packages to appear on PyPI and conda-forge. In preparation for this event, please make sure to
+- update your `pip` to version 20.1 at least to support `manylinux2010` and `manylinux2014`
+- use [`--only-binary=numpy`](https://pip.pypa.io/en/stable/reference/pip_install/#cmdoption-only-binary) or `--only-binary=:all:` to prevent `pip` from trying to build from source.
+
+
+### Numpy 1.19.2 release
+
+_Sept 10, 2020_ -- [NumPy 1.19.2](https://numpy.org/devdocs/release/1.19.2-notes.html) is now available. This latest release in the 1.19 series fixes several bugs, prepares for the [upcoming Cython 3.x release](http://docs.cython.org/en/latest/src/changes.html) and pins setuptools to keep distutils working while upstream modifications are ongoing. The aarch64 wheels are built with the latest manylinux2014 release that fixes the problem of differing page sizes used by different linux distros.
+
+### The inaugural NumPy survey is live!
+
+_Jul 2, 2020_ -- This survey is meant to guide and set priorities for decision-making about the development of NumPy as software and as a community. The survey is available in 8 additional languages besides English: Bangla, Hindi, Japanese, Mandarin, Portuguese, Russian, Spanish and French.
+
+Please help us make NumPy better and take the survey [here](https://umdsurvey.umd.edu/jfe/form/SV_8bJrXjbhXf7saAl).
+
+
+### NumPy has a new logo!
+
+_Jun 24, 2020_ -- NumPy now has a new logo:
+
+
+
+The logo is a modern take on the old one, with a cleaner design. Thanks to Isabela Presedo-Floyd for designing the new logo, as well as to Travis Vaught for the old logo that served us well for 15+ years.
+
+
+### NumPy 1.19.0 release
+
+_Jun 20, 2020_ -- NumPy 1.19.0 is now available. This is the first release without Python 2 support, hence it was a "clean-up release". The minimum supported Python version is now Python 3.6. An important new feature is that the random number generation infrastructure that was introduced in NumPy 1.17.0 is now accessible from Cython.
+
+
+### Season of Docs acceptance
+
+_May 11, 2020_ -- NumPy has been accepted as one of the mentor organizations for the Google Season of Docs program. We are excited about the opportunity to work with a technical writer to improve NumPy's documentation once again! For more details, please see [the official Season of Docs site](https://developers.google.com/season-of-docs/) and our [ideas page](https://github.com/numpy/numpy/wiki/Google-Season-of-Docs-2020-Project-Ideas).
+
+
+### NumPy 1.18.0 release
+
+_Dec 22, 2019_ -- NumPy 1.18.0 is now available. After the major changes in 1.17.0, this is a consolidation release. It is the last minor release that will support Python 3.5. Highlights of the release includes the addition of basic infrastructure for linking with 64-bit BLAS and LAPACK libraries, and a new C-API for `numpy.random`.
+
+Please see the [release notes](https://github.com/numpy/numpy/releases/tag/v1.18.0) for more details.
+
+
+### NumPy receives a grant from the Chan Zuckerberg Initiative
+
+_Nov 15, 2019_ -- We are pleased to announce that NumPy and OpenBLAS, one of NumPy's key dependencies, have received a joint grant for $195,000 from the Chan Zuckerberg Initiative through their [Essential Open Source Software for Science program](https://chanzuckerberg.com/eoss/) that supports software maintenance, growth, development, and community engagement for open source tools critical to science.
+
+This grant will be used to ramp up the efforts in improving NumPy documentation, website redesign, and community development to better serve our large and rapidly growing user base, and ensure the long-term sustainability of the project. While the OpenBLAS team will focus on addressing sets of key technical issues, in particular thread-safety, AVX-512, and thread-local storage (TLS) issues, as well as algorithmic improvements in ReLAPACK (Recursive LAPACK) on which OpenBLAS depends.
+
+More details on our proposed initiatives and deliverables can be found in the [full grant proposal](https://figshare.com/articles/Proposal_NumPy_OpenBLAS_for_Chan_Zuckerberg_Initiative_EOSS_2019_round_1/10302167). The work is scheduled to start on Dec 1st, 2019 and continue for the next 12 months.
+
+
+## Releases
+
+Here is a list of NumPy releases, with links to release notes. All bugfix releases (only the `z` changes in the `x.y.z` version number) have no new features; minor releases (the `y` increases) do.
+
+- NumPy 1.18.4 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.18.4)) -- _3 May 2020_.
+- NumPy 1.18.3 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.18.3)) -- _19 Apr 2020_.
+- NumPy 1.18.2 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.18.2)) -- _17 Mar 2020_.
+- NumPy 1.18.1 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.18.1)) -- _6 Jan 2020_.
+- NumPy 1.17.5 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.17.5)) -- _1 Jan 2020_.
+- NumPy 1.18.0 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.18.0)) -- _22 Dec 2019_.
+- NumPy 1.17.4 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.17.4)) -- _11 Nov 2019_.
+- NumPy 1.17.0 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.17.0)) -- _26 Jul 2019_.
+- NumPy 1.16.0 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.16.0)) -- _14 Jan 2019_.
+- NumPy 1.15.0 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.15.0)) -- _23 Jul 2018_.
+- NumPy 1.14.0 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.14.0)) -- _7 Jan 2018_.
From f01a90b86cc5f8288bbfbdc0179a70a083af3ceb Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:36:26 +0000
Subject: [PATCH 021/909] New translations history.md (Chinese Simplified)
---
content/zh/history.md | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
create mode 100644 content/zh/history.md
diff --git a/content/zh/history.md b/content/zh/history.md
new file mode 100644
index 0000000000..fc79a621af
--- /dev/null
+++ b/content/zh/history.md
@@ -0,0 +1,21 @@
+---
+title: History of NumPy
+sidebar: false
+---
+
+NumPy is a foundational Python library that provides array data structures and related fast numerical routines. When started, the library had little funding, and was written mainly by graduate students—many of them without computer science education, and often without a blessing of their advisors. To even imagine that a small group of “rogue” student programmers could upend the already well-established ecosystem of research software—backed by millions in funding and many hundreds of highly qualified engineers — was preposterous. Yet, the philosophical motivations behind a fully open tool stack, in combination with the excited, friendly community with a singular focus, have proven auspicious in the long run. Nowadays, NumPy is relied upon by scientists, engineers, and many other professionals around the world. For example, the published scripts used in the analysis of gravitational waves import NumPy, and the M87 black hole imaging project directly cites NumPy.
+
+For the in-depth account on milestones in the development of NumPy and related libraries please see [arxiv.org](arxiv.org/abs/1907.10121).
+
+If you’d like to obtain a copy of the original Numeric and Numarray libraries, follow the links below:
+
+[Download Page for *Numeric*](https://sourceforge.net/projects/numpy/files/Old%20Numeric/)*
+
+[Download Page for *Numarray*](https://sourceforge.net/projects/numpy/files/Old%20Numarray/)*
+
+*Please note that these older array packages are no longer maintained, and users are strongly advised to use NumPy for any array-related purposes or refactor any pre-existing code to utilize the NumPy library.
+
+### Historic Documentation
+
+[Download *`Numeric'* Manual](static/numeric-manual.pdf)
+
From 3b095c1b88d94db4919474c010c6b804d61198f2 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:36:27 +0000
Subject: [PATCH 022/909] New translations gethelp.md (Chinese Simplified)
---
content/zh/gethelp.md | 34 ++++++++++++++++++++++++++++++++++
1 file changed, 34 insertions(+)
create mode 100644 content/zh/gethelp.md
diff --git a/content/zh/gethelp.md b/content/zh/gethelp.md
new file mode 100644
index 0000000000..a427b5b1f5
--- /dev/null
+++ b/content/zh/gethelp.md
@@ -0,0 +1,34 @@
+---
+title: Get Help
+sidebar: false
+---
+
+**User questions:** The best way to get help is to post your question to a site like [StackOverflow](http://stackoverflow.com/questions/tagged/numpy), with thousands of users available to answer. Smaller alternatives include [IRC](https://webchat.freenode.net/?channels=%23numpy), [Gitter](https://gitter.im/numpy/numpy), and [Reddit](https://www.reddit.com/r/Numpy/). We wish we could keep an eye on these sites, or answer questions directly, but the volume is just a little overwhelming!
+
+**Development issues:** For NumPy development-related matters (e.g. bug reports), please see [Community](/community).
+
+
+
+### [StackOverflow](http://stackoverflow.com/questions/tagged/numpy)
+
+A forum for asking usage questions, e.g. "How do I do X in NumPy?”. Please [use the `#numpy` tag](https://stackoverflow.com/help/tagging)
+
+***
+
+### [Reddit](https://www.reddit.com/r/Numpy/)
+
+Another forum for usage questions.
+
+***
+
+### [Gitter](https://gitter.im/numpy/numpy)
+
+A real-time chat room where users and community members help each other.
+
+***
+
+### [IRC](https://webchat.freenode.net/?channels=%23numpy)
+
+Another real-time chat room where users and community members help each other.
+
+***
From dd28bf3fa86be7467f9f5aa5ac4857b1e8c50925 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:36:29 +0000
Subject: [PATCH 023/909] New translations report-handling-manual.md (Chinese
Simplified)
---
content/zh/report-handling-manual.md | 95 ++++++++++++++++++++++++++++
1 file changed, 95 insertions(+)
create mode 100644 content/zh/report-handling-manual.md
diff --git a/content/zh/report-handling-manual.md b/content/zh/report-handling-manual.md
new file mode 100644
index 0000000000..5586668cba
--- /dev/null
+++ b/content/zh/report-handling-manual.md
@@ -0,0 +1,95 @@
+---
+title: NumPy Code of Conduct - How to follow up on a report
+sidebar: false
+---
+
+This is the manual followed by NumPy’s Code of Conduct Committee. It’s used when we respond to an issue to make sure we’re consistent and fair.
+
+Enforcing the [Code of Conduct](/code-of-conduct) impacts our community today and for the future. It’s an action that we do not take lightly. When reviewing enforcement measures, the Code of Conduct Committee will keep the following values and guidelines in mind:
+
+* Act in a personal manner rather than impersonal. The Committee can engage the parties to understand the situation while respecting the privacy and any necessary confidentiality of reporters. However, sometimes it is necessary to communicate with one or more individuals directly: the Committee’s goal is to improve the health of our community rather than only produce a formal decision.
+* Emphasize empathy for individuals rather than judging behavior, avoiding binary labels of “good” and “bad/evil”. Overt, clear-cut aggression and harassment exist, and we will address them firmly. But many scenarios that can prove challenging to resolve are those where normal disagreements devolve into unhelpful or harmful behavior from multiple parties. Understanding the full context and finding a path that re-engages all is hard, but ultimately the most productive for our community.
+* We understand that email is a difficult medium and can be isolating. Receiving criticism over email, without personal contact, can be particularly painful. This makes it especially important to keep an atmosphere of open-minded respect for the views of others. It also means that we must be transparent in our actions, and that we will do everything in our power to make sure that all our members are treated fairly and with sympathy.
+* Discrimination can be subtle and it can be unconscious. It can show itself as unfairness and hostility in otherwise ordinary interactions. We know that this does occur, and we will take care to look out for it. We would very much like to hear from you if you feel you have been treated unfairly, and we will use these procedures to make sure that your complaint is heard and addressed.
+* Help increase engagement in good discussion practice: try to identify where discussion may have broken down, and provide actionable information, pointers, and resources that can lead to positive change on these points.
+* Be mindful of the needs of new members: provide them with explicit support and consideration, with the aim of increasing participation from underrepresented groups in particular.
+* Individuals come from different cultural backgrounds and native languages. Try to identify any honest misunderstandings caused by a non-native speaker and help them understand the issue and what they can change to avoid causing offence. Complex discussion in a foreign language can be very intimidating, and we want to grow our diversity also across nationalities and cultures.
+
+
+## Mediation
+
+Voluntary informal mediation is a tool at our disposal. In contexts such as when two or more parties have all escalated to the point of inappropriate behavior (something sadly common in human conflict), it may be useful to facilitate a mediation process. This is only an example: the Committee can consider mediation in any case, mindful that the process is meant to be strictly voluntary and no party can be pressured to participate. If the Committee suggests mediation, it should:
+
+* Find a candidate who can serve as a mediator.
+* Obtain the agreement of the reporter(s). The reporter(s) have complete freedom to decline the mediation idea or to propose an alternate mediator.
+* Obtain the agreement of the reported person(s).
+* Settle on the mediator: while parties can propose a different mediator than the suggested candidate, only if a common agreement is reached on all terms can the process move forward.
+* Establish a timeline for mediation to complete, ideally within two weeks.
+
+The mediator will engage with all the parties and seek a resolution that is satisfactory to all. Upon completion, the mediator will provide a report (vetted by all parties to the process) to the Committee, with recommendations on further steps. The Committee will then evaluate these results (whether a satisfactory resolution was achieved or not) and decide on any additional action deemed necessary.
+
+
+## How the Committee will respond to reports
+
+When the Committee (or a Committee member) receives a report, they will first determine whether the report is about a clear and severe breach (as defined below). If so, immediate action needs to be taken in addition to the regular report handling process.
+
+
+## Clear and severe breach actions
+
+We know that it is painfully common for internet communication to start at or devolve into obvious and flagrant abuse. We will deal quickly with clear and severe breaches like personal threats, violent, sexist or racist language.
+
+When a member of the Code of Conduct Committee becomes aware of a clear and severe breach, they will do the following:
+
+* Immediately disconnect the originator from all NumPy communication channels.
+* Reply to the reporter that their report has been received and that the originator has been disconnected.
+* In every case, the moderator should make a reasonable effort to contact the originator, and tell them specifically how their language or actions qualify as a “clear and severe breach”. The moderator should also say that, if the originator believes this is unfair or they want to be reconnected to NumPy, they have the right to ask for a review, as below, by the Code of Conduct Committee. The moderator should copy this explanation to the Code of Conduct Committee.
+* The Code of Conduct Committee will formally review and sign off on all cases where this mechanism has been applied to make sure it is not being used to control ordinary heated disagreement.
+
+
+## Report handling
+
+When a report is sent to the Committee they will immediately reply to the reporter to confirm receipt. This reply must be sent within 72 hours, and the group should strive to respond much quicker than that.
+
+If a report doesn’t contain enough information, the Committee will obtain all relevant data before acting. The Committee is empowered to act on the Steering Council’s behalf in contacting any individuals involved to get a more complete account of events.
+
+The Committee will then review the incident and determine, to the best of their ability:
+
+* What happened.
+* Whether this event constitutes a Code of Conduct violation.
+* Who are the responsible party(ies).
+* Whether this is an ongoing situation, and there is a threat to anyone’s physical safety.
+
+This information will be collected in writing, and whenever possible the group’s deliberations will be recorded and retained (i.e. chat transcripts, email discussions, recorded conference calls, summaries of voice conversations, etc).
+
+It is important to retain an archive of all activities of this Committee to ensure consistency in behavior and provide institutional memory for the project. To assist in this, the default channel of discussion for this Committee will be a private mailing list accessible to current and future members of the Committee as well as members of the Steering Council upon justified request. If the Committee finds the need to use off-list communications (e.g. phone calls for early/rapid response), it should in all cases summarize these back to the list so there’s a good record of the process.
+
+The Code of Conduct Committee should aim to have a resolution agreed upon within two weeks. In the event that a resolution can’t be determined in that time, the Committee will respond to the reporter(s) with an update and projected timeline for resolution.
+
+
+## Resolutions
+
+The Committee must agree on a resolution by consensus. If the group cannot reach consensus and deadlocks for over a week, the group will turn the matter over to the Steering Council for resolution.
+
+Possible responses may include:
+
+* Taking no further action:
+ - if we determine no violations have occurred;
+ - if the matter has been resolved publicly while the Committee was considering responses.
+* Coordinating voluntary mediation: if all involved parties agree, the Committee may facilitate a mediation process as detailed above.
+* Remind publicly, and point out that some behavior/actions/language have been judged inappropriate and why in the current context, or can but hurtful to some people, requesting the community to self-adjust.
+* A private reprimand from the Committee to the individual(s) involved. In this case, the group chair will deliver that reprimand to the individual(s) over email, cc’ing the group.
+* A public reprimand. In this case, the Committee chair will deliver that reprimand in the same venue that the violation occurred, within the limits of practicality. E.g., the original mailing list for an email violation, but for a chat room discussion where the person/context may be gone, they can be reached by other means. The group may choose to publish this message elsewhere for documentation purposes.
+* A request for a public or private apology, assuming the reporter agrees to this idea: they may at their discretion refuse further contact with the violator. The chair will deliver this request. The Committee may, if it chooses, attach “strings” to this request: for example, the group may ask a violator to apologize in order to retain one’s membership on a mailing list.
+* A “mutually agreed upon hiatus” where the Committee asks the individual to temporarily refrain from community participation. If the individual chooses not to take a temporary break voluntarily, the Committee may issue a “mandatory cooling off period”.
+* A permanent or temporary ban from some or all NumPy spaces (mailing lists, gitter.im, etc.). The group will maintain records of all such bans so that they may be reviewed in the future or otherwise maintained.
+
+Once a resolution is agreed upon, but before it is enacted, the Committee will contact the original reporter and any other affected parties and explain the proposed resolution. The Committee will ask if this resolution is acceptable, and must note feedback for the record.
+
+Finally, the Committee will make a report to the NumPy Steering Council (as well as the NumPy core team in the event of an ongoing resolution, such as a ban).
+
+The Committee will never publicly discuss the issue; all public statements will be made by the chair of the Code of Conduct Committee or the NumPy Steering Council.
+
+
+## Conflicts of Interest
+
+In the event of any conflict of interest, a Committee member must immediately notify the other members, and recuse themselves if necessary.
From 0c5111ac8c1164ac778e0d66ab70edc52ae734d7 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:36:31 +0000
Subject: [PATCH 024/909] New translations terms.md (Chinese Simplified)
---
content/zh/terms.md | 178 ++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 178 insertions(+)
create mode 100644 content/zh/terms.md
diff --git a/content/zh/terms.md b/content/zh/terms.md
new file mode 100644
index 0000000000..9a66045505
--- /dev/null
+++ b/content/zh/terms.md
@@ -0,0 +1,178 @@
+---
+title: Terms of Use
+sidebar: false
+---
+
+*Last updated January 4, 2020*
+
+
+## AGREEMENT TO TERMS
+
+These Terms of Use constitute a legally binding agreement made between you, whether personally or on behalf of an entity (“you”) and NumPy ("**Project**", “**we**”, “**us**”, or “**our**”), concerning your access to and use of the numpy.org website as well as any other media form, media channel, mobile website or mobile application related, linked, or otherwise connected thereto (collectively, the “Site”). You agree that by accessing the Site, you have read, understood, and agreed to be bound by all of these Terms of Use. IF YOU DO NOT AGREE WITH ALL OF THESE TERMS OF USE, THEN YOU ARE EXPRESSLY PROHIBITED FROM USING THE SITE AND YOU MUST DISCONTINUE USE IMMEDIATELY.
+
+
+
+Supplemental terms and conditions or documents that may be posted on the Site from time to time are hereby expressly incorporated herein by reference. We reserve the right, in our sole discretion, to make changes or modifications to these Terms of Use at any time and for any reason. We will alert you about any changes by updating the “Last updated” date of these Terms of Use, and you waive any right to receive specific notice of each such change. It is your responsibility to periodically review these Terms of Use to stay informed of updates. You will be subject to, and will be deemed to have been made aware of and to have accepted, the changes in any revised Terms of Use by your continued use of the Site after the date such revised Terms of Use are posted.
+
+
+
+The information provided on the Site is not intended for distribution to or use by any person or entity in any jurisdiction or country where such distribution or use would be contrary to law or regulation or which would subject us to any registration requirement within such jurisdiction or country. Accordingly, those persons who choose to access the Site from other locations do so on their own initiative and are solely responsible for compliance with local laws, if and to the extent local laws are applicable.
+
+
+## USER REPRESENTATIONS
+
+By using the Site, you represent and warrant that: (1) you have the legal capacity and you agree to comply with these Terms of Use; (2) you will not use the Site for any illegal or unauthorized purpose; and (3) your use of the Site will not violate any applicable law or regulation.
+
+
+If you provide any information that is untrue, inaccurate, not current, or incomplete, we have the right to refuse any and all current or future use of the Site (or any portion thereof).
+
+
+## PROHIBITED ACTIVITIES
+
+You may not access or use the Site for any purpose other than that for which we make the Site available.
+
+As a user of the Site, you agree not to:
+
+1. Systematically retrieve data or other content from the Site to create or compile, directly or indirectly, a collection, compilation, database, or directory without written permission from us.
+
+2. Make any unauthorized use of the Site, including collecting usernames and/or email addresses of users by electronic or other means for the purpose of sending unsolicited email, or creating user accounts by automated means or under false pretenses.
+
+3. Use the Site to advertise or offer to sell goods and services.
+
+4. Circumvent, disable, or otherwise interfere with security-related features of the Site.
+
+5. Engage in unauthorized framing of or linking to the Site.
+
+6. Trick, defraud, or mislead us and other users, especially in any attempt to learn sensitive account information such as user passwords.
+
+7. Make improper use of our support services or submit false reports of abuse or misconduct.
+
+8. Engage in any automated use of the system, such as using scripts to send comments or messages, or using any data mining, robots, or similar data gathering and extraction tools.
+
+9. Interfere with, disrupt, or create an undue burden on the Site or the networks or services connected to the Site.
+
+10. Attempt to impersonate another user or person or use the username of another user.
+
+11. Use any information obtained from the Site in order to harass, abuse, or harm another person.
+
+12. Disparage, tarnish, or otherwise harm, in our opinion, us and/or the Site.
+
+13. Except as may be the result of standard search engine or Internet browser usage, use, launch, develop, or distribute any automated system, including without limitation, any spider, robot, cheat utility, scraper, or offline reader that accesses the Site, or using or launching any unauthorized script or other software.
+
+14. Upload or transmit (or attempt to upload or to transmit) any material that acts as a passive or active information collection or transmission mechanism, including without limitation, clear graphics interchange formats (“gifs”), 1×1 pixels, web bugs, cookies, or other similar devices (sometimes referred to as “spyware” or “passive collection mechanisms” or “pcms”).
+
+15. Upload or transmit (or attempt to upload or to transmit) viruses, Trojan horses, or other material, including excessive use of capital letters and spamming (continuous posting of repetitive text), that interferes with any party’s uninterrupted use and enjoyment of the Site or modifies, impairs, disrupts, alters, or interferes with the use, features, functions, operation, or maintenance of the Site.
+
+16. Harass, annoy, intimidate, or threaten any of our employees or agents engaged in providing any portion of the Site to you.
+
+17. Attempt to bypass any measures of the Site designed to prevent or restrict access to the Site, or any portion of the Site.
+
+
+## SUBMISSIONS
+
+You acknowledge and agree that any questions, comments, suggestions, ideas, feedback, or other information regarding the Site ("Submissions") provided by you to us are non-confidential and shall become our sole property. We shall own exclusive rights, including all intellectual property rights, and shall be entitled to the unrestricted use and dissemination of these Submissions for any lawful purpose, commercial or otherwise, without acknowledgment or compensation to you. You hereby waive all moral rights to any such Submissions, and you hereby warrant that any such Submissions are original with you or that you have the right to submit such Submissions. You agree there shall be no recourse against us for any alleged or actual infringement or misappropriation of any proprietary right in your Submissions.
+
+## THIRD-PARTY WEBSITES AND CONTENT
+
+The Site may contain (or you may be sent via the Site) links to other websites ("Third-Party Websites") as well as articles, photographs, text, graphics, pictures, designs, music, sound, video, information, applications, software, and other content or items belonging to or originating from third parties ("Third-Party Content"). Such Third-Party Websites and Third-Party Content are not investigated, monitored, or checked for accuracy, appropriateness, or completeness by us, and we are not responsible for any Third-Party Websites accessed through the Site or any Third-Party Content posted on, available through, or installed from the Site, including the content, accuracy, offensiveness, opinions, reliability, privacy practices, or other policies of or contained in the Third-Party Websites or the Third-Party Content. Inclusion of, linking to, or permitting the use or installation of any Third-Party Websites or any Third-Party Content does not imply approval or endorsement thereof by us. If you decide to leave the Site and access the Third-Party Websites or to use or install any Third-Party Content, you do so at your own risk, and you should be aware these Terms of Use no longer govern. You should review the applicable terms and policies, including privacy and data gathering practices, of any website to which you navigate from the Site or relating to any applications you use or install from the Site. Any purchases you make through Third-Party Websites will be through other websites and from other companies, and we take no responsibility whatsoever in relation to such purchases which are exclusively between you and the applicable third party. You agree and acknowledge that we do not endorse the products or services offered on Third-Party Websites and you shall hold us harmless from any harm caused by your purchase of such products or services. Additionally, you shall hold us harmless from any losses sustained by you or harm caused to you relating to or resulting in any way from any Third-Party Content or any contact with Third-Party Websites.
+
+
+## SITE MANAGEMENT
+
+We reserve the right, but not the obligation, to: (1) monitor the Site for violations of these Terms of Use; (2) take appropriate legal action against anyone who, in our sole discretion, violates the law or these Terms of Use, including without limitation, reporting such user to law enforcement authorities; (3) in our sole discretion and without limitation, refuse, restrict access to, limit the availability of, or disable (to the extent technologically feasible) any of your Contributions or any portion thereof; (4) in our sole discretion and without limitation, notice, or liability, to remove from the Site or otherwise disable all files and content that are excessive in size or are in any way burdensome to our systems; and (5) otherwise manage the Site in a manner designed to protect our rights and property and to facilitate the proper functioning of the Site.
+
+
+## PRIVACY POLICY
+
+We care about data privacy and security. Please review our [Privacy Policy](/privacy). By using the Site, you agree to be bound by our Privacy Policy, which is incorporated into these Terms of Use. Please be advised the Site is hosted in the United States. If you access the Site from the European Union, Asia, or any other region of the world with laws or other requirements governing personal data collection, use, or disclosure that differ from applicable laws in the United States, then through your continued use of the Site, you are transferring your data to the United States, and you expressly consent to have your data transferred to and processed in the United States. Further, we do not knowingly accept, request, or solicit information from children or knowingly market to children. Therefore, in accordance with the U.S. Children’s Online Privacy Protection Act, if we receive actual knowledge that anyone under the age of 13 has provided personal information to us without the requisite and verifiable parental consent, we will delete that information from the Site as quickly as is reasonably practical.
+
+## TERM AND TERMINATION
+
+These Terms of Use shall remain in full force and effect while you use the Site. WITHOUT LIMITING ANY OTHER PROVISION OF THESE TERMS OF USE, WE RESERVE THE RIGHT TO, IN OUR SOLE DISCRETION AND WITHOUT NOTICE OR LIABILITY, DENY ACCESS TO AND USE OF THE SITE (INCLUDING BLOCKING CERTAIN IP ADDRESSES), TO ANY PERSON FOR ANY REASON OR FOR NO REASON, INCLUDING WITHOUT LIMITATION FOR BREACH OF ANY REPRESENTATION, WARRANTY, OR COVENANT CONTAINED IN THESE TERMS OF USE OR OF ANY APPLICABLE LAW OR REGULATION. WE MAY TERMINATE YOUR USE OR PARTICIPATION IN THE SITE OR DELETE ANY CONTENT OR INFORMATION THAT YOU POSTED AT ANY TIME, WITHOUT WARNING, IN OUR SOLE DISCRETION.
+
+
+## MODIFICATIONS AND INTERRUPTIONS
+
+We reserve the right to change, modify, or remove the contents of the Site at any time or for any reason at our sole discretion without notice. However, we have no obligation to update any information on our Site. We also reserve the right to modify or discontinue all or part of the Site without notice at any time. We will not be liable to you or any third party for any modification, suspension, or discontinuance of the Site.
+
+We cannot guarantee the Site will be available at all times. We may experience hardware, software, or other problems or need to perform maintenance related to the Site, resulting in interruptions, delays, or errors. We reserve the right to change, revise, update, suspend, discontinue, or otherwise modify the Site at any time or for any reason without notice to you. You agree that we have no liability whatsoever for any loss, damage, or inconvenience caused by your inability to access or use the Site during any downtime or discontinuance of the Site. Nothing in these Terms of Use will be construed to obligate us to maintain and support the Site or to supply any corrections, updates, or releases in connection therewith.
+
+
+## GOVERNING LAW
+
+These Terms of Use and your use of the Site are governed by and construed in accordance with the laws of the State of Texas applicable to agreements made and to be entirely performed within the State of Texas, without regard to its conflict of law principles.
+
+
+## DISPUTE RESOLUTION
+
+### Informal Negotiations
+
+To expedite resolution and control the cost of any dispute, controversy, or claim related to these Terms of Use (each a "Dispute" and collectively, the “Disputes”) brought by either you or us (individually, a “Party” and collectively, the “Parties”), the Parties agree to first attempt to negotiate any Dispute (except those Disputes expressly provided below) informally for at least thirty (30) days before initiating arbitration. Such informal negotiations commence upon written notice from one Party to the other Party.
+
+
+### Binding Arbitration
+
+If the Parties are unable to resolve a Dispute through informal negotiations, the Dispute (except those Disputes expressly excluded below) will be finally and exclusively resolved by binding arbitration. YOU UNDERSTAND THAT WITHOUT THIS PROVISION, YOU WOULD HAVE THE RIGHT TO SUE IN COURT AND HAVE A JURY TRIAL. The arbitration shall be commenced and conducted under the Commercial Arbitration Rules of the American Arbitration Association ("AAA") and, where appropriate, the AAA’s Supplementary Procedures for Consumer Related Disputes ("AAA Consumer Rules"), both of which are available at the AAA website www.adr.org. Your arbitration fees and your share of arbitrator compensation shall be governed by the AAA Consumer Rules and, where appropriate, limited by the AAA Consumer Rules. If such costs are determined to by the arbitrator to be excessive, we will pay all arbitration fees and expenses. The arbitration may be conducted in person, through the submission of documents, by phone, or online. The arbitrator will make a decision in writing, but need not provide a statement of reasons unless requested by either Party. The arbitrator must follow applicable law, and any award may be challenged if the arbitrator fails to do so. Except where otherwise required by the applicable AAA rules or applicable law, the arbitration will take place in Travis County, Texas. Except as otherwise provided herein, the Parties may litigate in court to compel arbitration, stay proceedings pending arbitration, or to confirm, modify, vacate, or enter judgment on the award entered by the arbitrator.
+
+If for any reason, a Dispute proceeds in court rather than arbitration, the Dispute shall be commenced or prosecuted in the state and federal courts located in Travis County, Texas, and the Parties hereby consent to, and waive all defenses of lack of personal jurisdiction, and forum non conveniens with respect to venue and jurisdiction in such state and federal courts. Application of the United Nations Convention on Contracts for the International Sale of Goods and the the Uniform Computer Information Transaction Act (UCITA) are excluded from these Terms of Use.
+
+In no event shall any Dispute brought by either Party related in any way to the Site be commenced more than one (1) years after the cause of action arose. If this provision is found to be illegal or unenforceable, then neither Party will elect to arbitrate any Dispute falling within that portion of this provision found to be illegal or unenforceable and such Dispute shall be decided by a court of competent jurisdiction within the courts listed for jurisdiction above, and the Parties agree to submit to the personal jurisdiction of that court.
+
+
+### Restrictions
+
+The Parties agree that any arbitration shall be limited to the Dispute between the Parties individually. To the full extent permitted by law, (a) no arbitration shall be joined with any other proceeding; (b) there is no right or authority for any Dispute to be arbitrated on a class-action basis or to utilize class action procedures; and (c) there is no right or authority for any Dispute to be brought in a purported representative capacity on behalf of the general public or any other persons.
+
+
+### Exceptions to Informal Negotiations and Arbitration
+
+The Parties agree that the following Disputes are not subject to the above provisions concerning informal negotiations and binding arbitration: (a) any Disputes seeking to enforce or protect, or concerning the validity of, any of the intellectual property rights of a Party; (b) any Dispute related to, or arising from, allegations of theft, piracy, invasion of privacy, or unauthorized use; and (c) any claim for injunctive relief. If this provision is found to be illegal or unenforceable, then neither Party will elect to arbitrate any Dispute falling within that portion of this provision found to be illegal or unenforceable and such Dispute shall be decided by a court of competent jurisdiction within the courts listed for jurisdiction above, and the Parties agree to submit to the personal jurisdiction of that court.
+
+
+## CORRECTIONS
+
+There may be information on the Site that contains typographical errors, inaccuracies, or omissions. We reserve the right to correct any errors, inaccuracies, or omissions and to change or update the information on the Site at any time, without prior notice.
+
+
+## DISCLAIMER
+
+THE SITE IS PROVIDED ON AN AS-IS AND AS-AVAILABLE BASIS. YOU AGREE THAT YOUR USE OF THE SITE AND OUR SERVICES WILL BE AT YOUR SOLE RISK. TO THE FULLEST EXTENT PERMITTED BY LAW, WE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, IN CONNECTION WITH THE SITE AND YOUR USE THEREOF, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. WE MAKE NO WARRANTIES OR REPRESENTATIONS ABOUT THE ACCURACY OR COMPLETENESS OF THE SITE’S CONTENT OR THE CONTENT OF ANY WEBSITES LINKED TO THE SITE AND WE WILL ASSUME NO LIABILITY OR RESPONSIBILITY FOR ANY (1) ERRORS, MISTAKES, OR INACCURACIES OF CONTENT AND MATERIALS, (2) PERSONAL INJURY OR PROPERTY DAMAGE, OF ANY NATURE WHATSOEVER, RESULTING FROM YOUR ACCESS TO AND USE OF THE SITE, (3) ANY UNAUTHORIZED ACCESS TO OR USE OF OUR SECURE SERVERS AND/OR ANY AND ALL PERSONAL INFORMATION AND/OR FINANCIAL INFORMATION STORED THEREIN, (4) ANY INTERRUPTION OR CESSATION OF TRANSMISSION TO OR FROM THE SITE, (5) ANY BUGS, VIRUSES, TROJAN HORSES, OR THE LIKE WHICH MAY BE TRANSMITTED TO OR THROUGH THE SITE BY ANY THIRD PARTY, AND/OR (6) ANY ERRORS OR OMISSIONS IN ANY CONTENT AND MATERIALS OR FOR ANY LOSS OR DAMAGE OF ANY KIND INCURRED AS A RESULT OF THE USE OF ANY CONTENT POSTED, TRANSMITTED, OR OTHERWISE MADE AVAILABLE VIA THE SITE. WE DO NOT WARRANT, ENDORSE, GUARANTEE, OR ASSUME RESPONSIBILITY FOR ANY PRODUCT OR SERVICE ADVERTISED OR OFFERED BY A THIRD PARTY THROUGH THE SITE, ANY HYPERLINKED WEBSITE, OR ANY WEBSITE OR MOBILE APPLICATION FEATURED IN ANY BANNER OR OTHER ADVERTISING, AND WE WILL NOT BE A PARTY TO OR IN ANY WAY BE RESPONSIBLE FOR MONITORING ANY TRANSACTION BETWEEN YOU AND ANY THIRD-PARTY PROVIDERS OF PRODUCTS OR SERVICES. AS WITH THE PURCHASE OF A PRODUCT OR SERVICE THROUGH ANY MEDIUM OR IN ANY ENVIRONMENT, YOU SHOULD USE YOUR BEST JUDGMENT AND EXERCISE CAUTION WHERE APPROPRIATE.
+
+
+## LIMITATIONS OF LIABILITY
+
+IN NO EVENT WILL WE OR OUR DIRECTORS, EMPLOYEES, OR AGENTS BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, EXEMPLARY, INCIDENTAL, SPECIAL, OR PUNITIVE DAMAGES, INCLUDING LOST PROFIT, LOST REVENUE, LOSS OF DATA, OR OTHER DAMAGES ARISING FROM YOUR USE OF THE SITE, EVEN IF WE HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. NOTWITHSTANDING ANYTHING TO THE CONTRARY CONTAINED HEREIN, OUR LIABILITY TO YOU FOR ANY CAUSE WHATSOEVER AND REGARDLESS OF THE FORM OF THE ACTION, WILL AT ALL TIMES BE LIMITED TO THE AMOUNT PAID, IF ANY, BY YOU TO US DURING THE SIX (6) MONTH PERIOD PRIOR TO ANY CAUSE OF ACTION ARISING. CERTAIN STATE LAWS DO NOT ALLOW LIMITATIONS ON IMPLIED WARRANTIES OR THE EXCLUSION OR LIMITATION OF CERTAIN DAMAGES. IF THESE LAWS APPLY TO YOU, SOME OR ALL OF THE ABOVE DISCLAIMERS OR LIMITATIONS MAY NOT APPLY TO YOU, AND YOU MAY HAVE ADDITIONAL RIGHTS.
+
+
+## INDEMNIFICATION
+
+You agree to defend, indemnify, and hold us harmless, including our subsidiaries, affiliates, and all of our respective officers, agents, partners, and employees, from and against any loss, damage, liability, claim, or demand, including reasonable attorneys’ fees and expenses, made by any third party due to or arising out of: (1) use of the Site; (2) breach of these Terms of Use; (3) any breach of your representations and warranties set forth in these Terms of Use; (4) your violation of the rights of a third party, including but not limited to intellectual property rights; or (5) any overt harmful act toward any other user of the Site with whom you connected via the Site. Notwithstanding the foregoing, we reserve the right, at your expense, to assume the exclusive defense and control of any matter for which you are required to indemnify us, and you agree to cooperate, at your expense, with our defense of such claims. We will use reasonable efforts to notify you of any such claim, action, or proceeding which is subject to this indemnification upon becoming aware of it.
+
+
+## USER DATA
+
+We will maintain certain data that you transmit to the Site for the purpose of managing the performance of the Site, as well as data relating to your use of the Site. Although we perform regular routine backups of data, you are solely responsible for all data that you transmit or that relates to any activity you have undertaken using the Site. You agree that we shall have no liability to you for any loss or corruption of any such data, and you hereby waive any right of action against us arising from any such loss or corruption of such data.
+
+
+## ELECTRONIC COMMUNICATIONS, TRANSACTIONS, AND SIGNATURES
+
+Visiting the Site, sending us emails, and completing online forms constitute electronic communications. You consent to receive electronic communications, and you agree that all agreements, notices, disclosures, and other communications we provide to you electronically, via email and on the Site, satisfy any legal requirement that such communication be in writing. YOU HEREBY AGREE TO THE USE OF ELECTRONIC SIGNATURES, CONTRACTS, ORDERS, AND OTHER RECORDS, AND TO ELECTRONIC DELIVERY OF NOTICES, POLICIES, AND RECORDS OF TRANSACTIONS INITIATED OR COMPLETED BY US OR VIA THE SITE. You hereby waive any rights or requirements under any statutes, regulations, rules, ordinances, or other laws in any jurisdiction which require an original signature or delivery or retention of non-electronic records, or to payments or the granting of credits by any means other than electronic means.
+
+
+## CALIFORNIA USERS AND RESIDENTS
+
+If any complaint with us is not satisfactorily resolved, you can contact the Complaint Assistance Unit of the Division of Consumer Services of the California Department of Consumer Affairs in writing at 1625 North Market Blvd., Suite N 112, Sacramento, California 95834 or by telephone at (800) 952-5210 or (916) 445-1254.
+
+
+## MISCELLANEOUS
+
+These Terms of Use and any policies or operating rules posted by us on the Site or in respect to the Site constitute the entire agreement and understanding between you and us. Our failure to exercise or enforce any right or provision of these Terms of Use shall not operate as a waiver of such right or provision. These Terms of Use operate to the fullest extent permissible by law. We may assign any or all of our rights and obligations to others at any time. We shall not be responsible or liable for any loss, damage, delay, or failure to act caused by any cause beyond our reasonable control. If any provision or part of a provision of these Terms of Use is determined to be unlawful, void, or unenforceable, that provision or part of the provision is deemed severable from these Terms of Use and does not affect the validity and enforceability of any remaining provisions. There is no joint venture, partnership, employment or agency relationship created between you and us as a result of these Terms of Use or use of the Site. You agree that these Terms of Use will not be construed against us by virtue of having drafted them. You hereby waive any and all defenses you may have based on the electronic form of these Terms of Use and the lack of signing by the parties hereto to execute these Terms of Use.
+
+## CONTACT US
+
+In order to resolve a complaint regarding the Site or to receive further information regarding use of the Site, please contact us at:
+
+NumFOCUS, Inc. P.O. Box 90596 Austin, TX, USA 78709 info@numfocus.org +1 (512) 222-5449
+
+
+
From a13e723ab76df7536e52aff91203ff36cf8d0b95 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:36:32 +0000
Subject: [PATCH 025/909] New translations privacy.md (Chinese Simplified)
---
content/zh/privacy.md | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
create mode 100644 content/zh/privacy.md
diff --git a/content/zh/privacy.md b/content/zh/privacy.md
new file mode 100644
index 0000000000..a3674dd48a
--- /dev/null
+++ b/content/zh/privacy.md
@@ -0,0 +1,18 @@
+---
+title: Privacy Policy
+sidebar: false
+---
+
+**numpy.org** is operated by [NumFOCUS, Inc.](https://numfocus.org), the fiscal sponsor of the NumPy project. For the Privacy Policy of this website please refer to https://numfocus.org/privacy-policy.
+
+If you have any questions about the policy or NumFOCUS’s data collection, use, and disclosure practices, please contact the NumFOCUS staff at privacy@numfocus.org.
+
+
+
+
+
+
+
+
+
+
From dc5f33309281b60905cd1a766ebce19f7de57a64 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:36:34 +0000
Subject: [PATCH 026/909] New translations press-kit.md (Chinese Simplified)
---
content/zh/press-kit.md | 8 ++++++++
1 file changed, 8 insertions(+)
create mode 100644 content/zh/press-kit.md
diff --git a/content/zh/press-kit.md b/content/zh/press-kit.md
new file mode 100644
index 0000000000..2309040ad2
--- /dev/null
+++ b/content/zh/press-kit.md
@@ -0,0 +1,8 @@
+---
+title: Press kit
+sidebar: false
+---
+
+We would like to make it easy for you to include the NumPy project identity in your next academic paper, course materials, or presentation.
+
+You will find several high-resolution versions of the NumPy logo [here](https://github.com/numpy/numpy/tree/master/branding/logo). Note that by using the numpy.org resources, you accept the [NumPy Code of Conduct](/code-of-conduct).
From b9dad28fefb80d078e3717c35973a2e054951a92 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:36:36 +0000
Subject: [PATCH 027/909] New translations learn.md (Chinese Simplified)
---
content/zh/learn.md | 84 +++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 84 insertions(+)
create mode 100644 content/zh/learn.md
diff --git a/content/zh/learn.md b/content/zh/learn.md
new file mode 100644
index 0000000000..264677ac48
--- /dev/null
+++ b/content/zh/learn.md
@@ -0,0 +1,84 @@
+---
+title: Learn
+sidebar: false
+---
+
+**The official NumPy documentation lives [here](https://numpy.org/doc/stable).**
+
+Below is a curated collection of external resources. To contribute, see the [end of this page](#add-to-this-list).
+***
+
+## Beginners
+
+There's a ton of information about NumPy out there. If you are new, we'd strongly recommend these:
+
+ **Tutorials**
+
+* [NumPy Quickstart Tutorial](https://numpy.org/devdocs/user/quickstart.html)
+* [SciPy Lectures](https://scipy-lectures.org/) Besides covering NumPy, these lectures offer a broader introduction to the scientific Python ecosystem.
+* [NumPy: the absolute basics for beginners](https://numpy.org/devdocs/user/absolute_beginners.html)
+* [Machine Learning Plus - Introduction to ndarray](https://www.machinelearningplus.com/python/numpy-tutorial-part1-array-python-examples/)
+* [Edureka - Learn NumPy Arrays with Examples ](https://www.edureka.co/blog/python-numpy-tutorial/)
+* [Dataquest - NumPy Tutorial: Data Analysis with Python](https://www.dataquest.io/blog/numpy-tutorial-python/)
+* [NumPy tutorial *by Nicolas Rougier*](https://github.com/rougier/numpy-tutorial)
+* [Stanford CS231 *by Justin Johnson*](http://cs231n.github.io/python-numpy-tutorial/)
+* [NumPy User Guide](https://numpy.org/devdocs)
+
+ **Books**
+
+* [Guide to NumPy *by Travis E. Oliphant*](http://web.mit.edu/dvp/Public/numpybook.pdf) This is a free version 1 from 2006. For the latest copy (2015) see [here](https://www.barnesandnoble.com/w/guide-to-numpy-travis-e-oliphant-phd/1122853007).
+* [From Python to NumPy *by Nicolas P. Rougier*](https://www.labri.fr/perso/nrougier/from-python-to-numpy/)
+* [Elegant SciPy](https://www.amazon.com/Elegant-SciPy-Art-Scientific-Python/dp/1491922877) *by Juan Nunez-Iglesias, Stefan van der Walt, and Harriet Dashnow*
+
+You may also want to check out the [Goodreads list](https://www.goodreads.com/shelf/show/python-scipy) on the subject of "Python+SciPy." Most books there are about the "SciPy ecosystem," which has NumPy at its core.
+
+ **Videos**
+
+* [Introduction to Numerical Computing with NumPy](http://youtu.be/ZB7BZMhfPgk) *by Alex Chabot-Leclerc*
+
+***
+
+## Advanced
+
+Try these advanced resources for a better understanding of NumPy concepts like advanced indexing, splitting, stacking, linear algebra, and more.
+
+ **Tutorials**
+
+* [100 NumPy Exercises](http://www.labri.fr/perso/nrougier/teaching/numpy.100/index.html) *by Nicolas P. Rougier*
+* [An Introduction to NumPy and Scipy](https://engineering.ucsb.edu/~shell/che210d/numpy.pdf) *by M. Scott Shell*
+* [Numpy Medkits](http://mentat.za.net/numpy/numpy_advanced_slides/) *by Stéfan van der Walt*
+* [NumPy in Python (Advanced)](https://www.geeksforgeeks.org/numpy-python-set-2-advanced/)
+* [Advanced Indexing](https://www.tutorialspoint.com/numpy/numpy_advanced_indexing.htm)
+* [Machine Learning and Data Analytics with NumPy](https://www.machinelearningplus.com/python/numpy-tutorial-python-part2/)
+
+ **Books**
+
+* [Python Data Science Handbook](https://www.amazon.com/Python-Data-Science-Handbook-Essential/dp/1491912057) *by Jake Vanderplas*
+* [Python for Data Analysis](https://www.amazon.com/Python-Data-Analysis-Wrangling-IPython/dp/1491957662) *by Wes McKinney*
+* [Numerical Python: Scientific Computing and Data Science Applications with Numpy, SciPy, and Matplotlib](https://www.amazon.com/Numerical-Python-Scientific-Applications-Matplotlib/dp/1484242459) *by Robert Johansson*
+
+ **Videos**
+
+* [Advanced NumPy - broadcasting rules, strides, and advanced indexing](https://www.youtube.com/watch?v=cYugp9IN1-Q) *by Juan Nunuz-Iglesias*
+* [Advanced Indexing Operations in NumPy Arrays](https://www.youtube.com/watch?v=2WTDrSkQBng) *by Amuls Academy*
+
+***
+
+## NumPy Talks
+
+* [The Future of NumPy Indexing](https://www.youtube.com/watch?v=o0EacbIbf58) *by Jaime Fernández* (2016)
+* [Evolution of Array Computing in Python](https://www.youtube.com/watch?v=HVLPJnvInzM&t=10s) *by Ralf Gommers* (2019)
+* [NumPy: what has changed and what is going to change?](https://www.youtube.com/watch?v=YFLVQFjRmPY) *by Matti Picus* (2019)
+* [Inside NumPy](https://www.youtube.com/watch?v=dBTJD_FDVjU) *by Ralf Gommers, Sebastian Berg, Matti Picus, Tyler Reddy, Stefan van der Walt, Charles Harris* (2019)
+* [Brief Review of Array Computing in Python](https://www.youtube.com/watch?v=f176j2g2eNc) *by Travis Oliphant* (2019)
+
+***
+
+## Citing NumPy
+
+If NumPy has been significant in your research, and you would like to acknowledge the project in your academic publication, please see [this citation information](/citing-numpy).
+
+## Contribute to this list
+
+
+To add to this collection, submit a recommendation [via a pull request](https://github.com/numpy/numpy.org/blob/master/content/en/learn.md). Say why your recommendation deserves mention on this page and also which audience would benefit most.
From e8197bc414c6aadd61d3de3fdf4fdfccb719971a Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:36:38 +0000
Subject: [PATCH 028/909] New translations install.md (Chinese Simplified)
---
content/zh/install.md | 142 ++++++++++++++++++++++++++++++++++++++++++
1 file changed, 142 insertions(+)
create mode 100644 content/zh/install.md
diff --git a/content/zh/install.md b/content/zh/install.md
new file mode 100644
index 0000000000..43dd44cb12
--- /dev/null
+++ b/content/zh/install.md
@@ -0,0 +1,142 @@
+---
+title: Installing NumPy
+sidebar: false
+---
+
+The only prerequisite for installing NumPy is Python itself. If you don't have Python yet and want the simplest way to get started, we recommend you use the [Anaconda Distribution](https://www.anaconda.com/distribution) - it includes Python, NumPy, and many other commonly used packages for scientific computing and data science.
+
+NumPy can be installed with `conda`, with `pip`, with a package manager on macOS and Linux, or [from source](https://numpy.org/devdocs/user/building.html). For more detailed instructions, consult our [Python and NumPy installation guide](#python-numpy-install-guide) below.
+
+**CONDA**
+
+If you use `conda`, you can install NumPy from the `defaults` or `conda-forge` channels:
+
+```bash
+# Best practice, use an environment rather than install in the base env
+conda create -n my-env
+conda activate my-env
+# If you want to install from conda-forge
+conda config --env --add channels conda-forge
+# The actual install command
+conda install numpy
+```
+
+**PIP**
+
+If you use `pip`, you can install NumPy with:
+
+```bash
+pip install numpy
+```
+Also when using pip, it's good practice to use a virtual environment - see [Reproducible Installs](#reproducible-installs) below for why, and [this guide](https://dev.to/bowmanjd/python-tools-for-managing-virtual-environments-3bko#howto) for details on using virtual environments.
+
+
+
+# Python and NumPy installation guide
+
+Installing and managing packages in Python is complicated, there are a number of alternative solutions for most tasks. This guide tries to give the reader a sense of the best (or most popular) solutions, and give clear recommendations. It focuses on users of Python, NumPy, and the PyData (or numerical computing) stack on common operating systems and hardware.
+
+## Recommendations
+
+We'll start with recommendations based on the user's experience level and operating system of interest. If you're in between "beginning" and "advanced", please go with "beginning" if you want to keep things simple, and with "advanced" if you want to work according to best practices that go a longer way in the future.
+
+### Beginning users
+
+On all of Windows, macOS, and Linux:
+
+- Install [Anaconda](https://www.anaconda.com/distribution/) (it installs all packages you need and all other tools mentioned below).
+- For writing and executing code, use notebooks in [JupyterLab](https://jupyterlab.readthedocs.io/en/stable/index.html) for exploratory and interactive computing, and [Spyder](https://www.spyder-ide.org/) or [Visual Studio Code](https://code.visualstudio.com/) for writing scripts and packages.
+- Use [Anaconda Navigator](https://docs.anaconda.com/anaconda/navigator/) to manage your packages and start JupyterLab, Spyder, or Visual Studio Code.
+
+
+### Advanced users
+
+#### Windows or macOS
+
+- Install [Miniconda](https://docs.conda.io/en/latest/miniconda.html).
+- Keep the `base` conda environment minimal, and use one or more [conda environments](https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#) to install the package you need for the task or project you're working on.
+- Unless you're fine with only the packages in the `defaults` channel, make `conda-forge` your default channel via [setting the channel priority](https://conda-forge.org/docs/user/introduction.html#how-can-i-install-packages-from-conda-forge).
+
+
+#### Linux
+
+If you're fine with slightly outdated packages and prefer stability over being able to use the latest versions of libraries:
+- Use your OS package manager for as much as possible (Python itself, NumPy, and other libraries).
+- Install packages not provided by your package manager with `pip install somepackage --user`.
+
+If you use a GPU:
+- Install [Miniconda](https://docs.conda.io/en/latest/miniconda.html).
+- Keep the `base` conda environment minimal, and use one or more [conda environments](https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#) to install the package you need for the task or project you're working on.
+- Use the `defaults` conda channel (`conda-forge` doesn't have good support for GPU packages yet).
+
+Otherwise:
+- Install [Miniforge](https://github.com/conda-forge/miniforge).
+- Keep the `base` conda environment minimal, and use one or more [conda environments](https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#) to install the package you need for the task or project you're working on.
+
+
+#### Alternative if you prefer pip/PyPI
+
+For users who know, from personal preference or reading about the main differences between conda and pip below, they prefer a pip/PyPI-based solution, we recommend:
+- Install Python from, for example, [python.org](https://www.python.org/downloads/), [Homebrew](https://brew.sh/), or your Linux package manager.
+- Use [Poetry](https://python-poetry.org/) as the most well-maintained tool that provides a dependency resolver and environment management capabilities in a similar fashion as conda does.
+
+
+## Python package management
+
+Managing packages is a challenging problem, and, as a result, there are lots of tools. For web and general purpose Python development there's a whole [host of tools](https://packaging.python.org/guides/tool-recommendations/) complementary with pip. For high-performance computing (HPC), [Spack](https://github.com/spack/spack) is worth considering. For most NumPy users though, [conda](https://conda.io/en/latest/) and [pip](https://pip.pypa.io/en/stable/) are the two most popular tools.
+
+
+### Pip & conda
+
+The two main tools that install Python packages are `pip` and `conda`. Their functionality partially overlaps (e.g. both can install `numpy`), however, they can also work together. We'll discuss the major differences between pip and conda here - this is important to understand if you want to manage packages effectively.
+
+The first difference is that conda is cross-language and it can install Python, while pip is installed for a particular Python on your system and installs other packages to that same Python install only. This also means conda can install non-Python libraries and tools you may need (e.g. compilers, CUDA, HDF5), while pip can't.
+
+The second difference is that pip installs from the Python Packaging Index (PyPI), while conda installs from its own channels (typically "defaults" or "conda-forge"). PyPI is the largest collection of packages by far, however, all popular packages are available for conda as well.
+
+The third difference is that conda is an integrated solution for managing packages, dependencies and environments, while with pip you may need another tool (there are many!) for dealing with environments or complex dependencies.
+
+
+### Reproducible installs
+
+As libraries get updated, results from running your code can change, or your code can break completely. It's important to be able to reconstruct the set of packages and versions you're using. Best practice is to:
+
+1. use a different environment per project you're working on,
+2. record package names and versions using your package installer; each has its own metadata format for this:
+ - Conda: [conda environments and environment.yml](https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#)
+ - Pip: [virtual environments](https://docs.python.org/3/tutorial/venv.html) and [requirements.txt](https://pip.readthedocs.io/en/latest/user_guide/#requirements-files)
+ - Poetry: [virtual environments and pyproject.toml](https://python-poetry.org/docs/basic-usage/)
+
+
+
+## NumPy packages & accelerated linear algebra libraries
+
+NumPy doesn't depend on any other Python packages, however, it does depend on an accelerated linear algebra library - typically [Intel MKL](https://software.intel.com/en-us/mkl) or [OpenBLAS](https://www.openblas.net/). Users don't have to worry about installing those (they're automatically included in all NumPy install methods). Power users may still want to know the details, because the used BLAS can affect performance, behavior and size on disk:
+
+- The NumPy wheels on PyPI, which is what pip installs, are built with OpenBLAS. The OpenBLAS libraries are included in the wheel. This makes the wheel larger, and if a user installs (for example) SciPy as well, they will now have two copies of OpenBLAS on disk.
+
+- In the conda defaults channel, NumPy is built against Intel MKL. MKL is a separate package that will be installed in the users' environment when they install NumPy.
+
+- In the conda-forge channel, NumPy is built against a dummy "BLAS" package. When a user installs NumPy from conda-forge, that BLAS package then gets installed together with the actual library - this defaults to OpenBLAS, but it can also be MKL (from the defaults channel), or even [BLIS](https://github.com/flame/blis) or reference BLAS.
+
+- The MKL package is a lot larger than OpenBLAS, it's about 700 MB on disk while OpenBLAS is about 30 MB.
+
+- MKL is typically a little faster and more robust than OpenBLAS.
+
+Besides install sizes, performance and robustness, there are two more things to consider:
+
+- Intel MKL is not open source. For normal use this is not a problem, but if a user needs to redistribute an application built with NumPy, this could be an issue.
+- Both MKL and OpenBLAS will use multi-threading for function calls like `np.dot`, with the number of threads being determined by both a build-time option and an environment variable. Often all CPU cores will be used. This is sometimes unexpected for users; NumPy itself doesn't auto-parallelize any function calls. It typically yields better performance, but can also be harmful - for example when using another level of parallelization with Dask, scikit-learn or multiprocessing.
+
+
+## Troubleshooting
+
+If your installation fails with the message below, see [Troubleshooting ImportError](https://numpy.org/doc/stable/user/troubleshooting-importerror.html).
+
+```
+IMPORTANT: PLEASE READ THIS FOR ADVICE ON HOW TO SOLVE THIS ISSUE!
+
+Importing the numpy c-extensions failed. This error can happen for
+different reasons, often due to issues with your setup.
+```
+
From d418b2a8f6fb0b43d291d6b71f993f13225dc57c Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:36:39 +0000
Subject: [PATCH 029/909] New translations code-of-conduct.md (Chinese
Simplified)
---
content/zh/code-of-conduct.md | 83 +++++++++++++++++++++++++++++++++++
1 file changed, 83 insertions(+)
create mode 100644 content/zh/code-of-conduct.md
diff --git a/content/zh/code-of-conduct.md b/content/zh/code-of-conduct.md
new file mode 100644
index 0000000000..efcde754ae
--- /dev/null
+++ b/content/zh/code-of-conduct.md
@@ -0,0 +1,83 @@
+---
+title: NumPy Code of Conduct
+sidebar: false
+aliases:
+ - /conduct.html
+---
+
+### Introduction
+
+This Code of Conduct applies to all spaces managed by the NumPy project, including all public and private mailing lists, issue trackers, wikis, blogs, Twitter, and any other communication channel used by our community. The NumPy project does not organise in-person events, however events related to our community should have a code of conduct similar in spirit to this one.
+
+This Code of Conduct should be honored by everyone who participates in the NumPy community formally or informally, or claims any affiliation with the project, in any project-related activities and especially when representing the project, in any role.
+
+This code is not exhaustive or complete. It serves to distill our common understanding of a collaborative, shared environment and goals. Please try to follow this code in spirit as much as in letter, to create a friendly and productive environment that enriches the surrounding community.
+
+### Specific Guidelines
+
+We strive to:
+
+1. Be open. We invite anyone to participate in our community. We prefer to use public methods of communication for project-related messages, unless discussing something sensitive. This applies to messages for help or project-related support, too; not only is a public support request much more likely to result in an answer to a question, it also ensures that any inadvertent mistakes in answering are more easily detected and corrected.
+2. Be empathetic, welcoming, friendly, and patient. We work together to resolve conflict, and assume good intentions. We may all experience some frustration from time to time, but we do not allow frustration to turn into a personal attack. A community where people feel uncomfortable or threatened is not a productive one.
+3. Be collaborative. Our work will be used by other people, and in turn we will depend on the work of others. When we make something for the benefit of the project, we are willing to explain to others how it works, so that they can build on the work to make it even better. Any decision we make will affect users and colleagues, and we take those consequences seriously when making decisions.
+4. Be inquisitive. Nobody knows everything! Asking questions early avoids many problems later, so we encourage questions, although we may direct them to the appropriate forum. We will try hard to be responsive and helpful.
+5. Be careful in the words that we choose. We are careful and respectful in our communication, and we take responsibility for our own speech. Be kind to others. Do not insult or put down other participants. We will not accept harassment or other exclusionary behaviour, such as:
+ * Violent threats or language directed against another person.
+ * Sexist, racist, or otherwise discriminatory jokes and language.
+ * Posting sexually explicit or violent material.
+ * Posting (or threatening to post) other people’s personally identifying information (“doxing”).
+ * Sharing private content, such as emails sent privately or non-publicly, or unlogged forums such as IRC channel history, without the sender’s consent.
+ * Personal insults, especially those using racist or sexist terms.
+ * Unwelcome sexual attention.
+ * Excessive profanity. Please avoid swearwords; people differ greatly in their sensitivity to swearing.
+ * Repeated harassment of others. In general, if someone asks you to stop, then stop.
+ * Advocating for, or encouraging, any of the above behaviour.
+
+### Diversity Statement
+
+The NumPy project welcomes and encourages participation by everyone. We are committed to being a community that everyone enjoys being part of. Although we may not always be able to accommodate each individual’s preferences, we try our best to treat everyone kindly.
+
+No matter how you identify yourself or how others perceive you: we welcome you. Though no list can hope to be comprehensive, we explicitly honour diversity in: age, culture, ethnicity, genotype, gender identity or expression, language, national origin, neurotype, phenotype, political beliefs, profession, race, religion, sexual orientation, socioeconomic status, subculture and technical ability, to the extent that these do not conflict with this code of conduct.
+
+Though we welcome people fluent in all languages, NumPy development is conducted in English.
+
+Standards for behaviour in the NumPy community are detailed in the Code of Conduct above. Participants in our community should uphold these standards in all their interactions and help others to do so as well (see next section).
+
+### Reporting Guidelines
+
+We know that it is painfully common for internet communication to start at or devolve into obvious and flagrant abuse. We also recognize that sometimes people may have a bad day, or be unaware of some of the guidelines in this Code of Conduct. Please keep this in mind when deciding on how to respond to a breach of this Code.
+
+For clearly intentional breaches, report those to the Code of Conduct Committee (see below). For possibly unintentional breaches, you may reply to the person and point out this code of conduct (either in public or in private, whatever is most appropriate). If you would prefer not to do that, please feel free to report to the Code of Conduct Committee directly, or ask the Committee for advice, in confidence.
+
+You can report issues to the NumPy Code of Conduct Committee at numpy-conduct@googlegroups.com.
+
+Currently, the Committee consists of:
+
+* Stefan van der Walt
+* Melissa Weber Mendonça
+* Anirudh Subramanian
+
+If your report involves any members of the Committee, or if they feel they have a conflict of interest in handling it, then they will recuse themselves from considering your report. Alternatively, if for any reason you feel uncomfortable making a report to the Committee, then you can also contact senior NumFOCUS staff at [conduct@numfocus.org](https://numfocus.org/code-of-conduct#persons-responsible).
+
+### Incident reporting resolution & Code of Conduct enforcement
+
+_This section summarizes the most important points, more details can be found in_ [NumPy Code of Conduct - How to follow up on a report](/report-handling-manual).
+
+We will investigate and respond to all complaints. The NumPy Code of Conduct Committee and the NumPy Steering Committee (if involved) will protect the identity of the reporter, and treat the content of complaints as confidential (unless the reporter agrees otherwise).
+
+In case of severe and obvious breaches, e.g. personal threat or violent, sexist or racist language, we will immediately disconnect the originator from NumPy communication channels; please see the manual for details.
+
+In cases not involving clear severe and obvious breaches of this Code of Conduct the process for acting on any received Code of Conduct violation report will be:
+
+1. acknowledge report is received,
+2. reasonable discussion/feedback,
+3. mediation (if feedback didn’t help, and only if both reporter and reportee agree to this),
+4. enforcement via transparent decision (see [Resolutions](/report-handling-manual#resolutions)) by the Code of Conduct Committee.
+
+The Committee will respond to any report as soon as possible, and at most within 72 hours.
+
+### Endnotes
+
+We are thankful to the groups behind the following documents, from which we drew content and inspiration:
+
+- [The SciPy Code of Conduct](https://docs.scipy.org/doc/scipy/reference/dev/conduct/code_of_conduct.html)
From 490d0cfb94e8c2eca49670f6f34656726dc4c106 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:36:41 +0000
Subject: [PATCH 030/909] New translations history.md (Portuguese, Brazilian)
---
content/pt/history.md | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
create mode 100644 content/pt/history.md
diff --git a/content/pt/history.md b/content/pt/history.md
new file mode 100644
index 0000000000..2ddc33eb57
--- /dev/null
+++ b/content/pt/history.md
@@ -0,0 +1,21 @@
+---
+title: Histórico do NumPy
+sidebar: false
+---
+
+NumPy é uma biblioteca Python fundamental que fornece estruturas de *arrays* de dados e rotinas numéricas rápidas relacionadas a estas arrays. Quando começou, a biblioteca tinha pouco financiamento e foi escrita principalmente por estudantes de pós-graduação—muitos deles sem educação em ciência da computação e, muitas vezes, sem autorização dos seus orientadores. Imaginar que um pequeno grupo de programadores estudantis "desobedientes" poderiam subverter o já bem estabelecido ecossistema de software de pesquisa - apoiado por milhões em financiamento e muitas centenas de engenheiros altamente qualificados - era absurdo. No entanto, as motivações filosóficas por trás de uma ferramenta totalmente aberta, em combinação com a vibrante, amigável comunidade com foco singular, provaram ser auspiciosas a longo prazo. Hoje em dia, cientistas, engenheiros e muitos outros profissionais ao redor do mundo confiam no NumPy. Por exemplo, os scripts usados e publicados na análise de ondas gravitacionais importam o NumPy, e o projeto de imagem para buraco negro M87 cita diretamente o NumPy.
+
+Para um histórico aprofundado dos marcos no desenvolvimento do NumPy e bibliotecas relacionadas, por favor veja [arxiv.org](arxiv.org/abs/1907.10121).
+
+Se você quiser obter uma cópia das bibliotecas Numeric e Numarray, siga os links abaixo:
+
+[Página de download para *Numeric*](https://sourceforge.net/projects/numpy/files/Old%20Numeric/)*
+
+[Página de download para *Numarray*](https://sourceforge.net/projects/numpy/files/Old%20Numarray/)*
+
+*Por favor, note que esses pacotes antigos não são mais mantidos, e os usuários são fortemente aconselhados a usar o NumPy para quaisquer propósitos relacionados a arrays e matrizes ou refatorar qualquer código pré-existente para utilizar a biblioteca do NumPy.
+
+### Documentação Histórica
+
+[Baixe o manual do *`Numeric'*](static/numeric-manual.pdf)
+
From 4d6a5dc39196ccea7b472b88019d15bef91cffd1 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:36:43 +0000
Subject: [PATCH 031/909] New translations blackhole-image.md (Portuguese,
Brazilian)
---
content/pt/case-studies/blackhole-image.md | 70 ++++++++++++++++++++++
1 file changed, 70 insertions(+)
create mode 100644 content/pt/case-studies/blackhole-image.md
diff --git a/content/pt/case-studies/blackhole-image.md b/content/pt/case-studies/blackhole-image.md
new file mode 100644
index 0000000000..e59861dfa2
--- /dev/null
+++ b/content/pt/case-studies/blackhole-image.md
@@ -0,0 +1,70 @@
+---
+title: "Case Study: First Image of a Black Hole"
+sidebar: false
+---
+
+{{< figure src="/images/content_images/cs/blackhole.jpg" caption="**Black Hole M87**" alt="black hole image" attr="*(Créditos: Event Horizon Telescope Collaboration)*" attrlink="https://www.jpl.nasa.gov/images/universe/20190410/blackhole20190410.jpg" >}}
+
+
+
Criar uma imagem do Buraco Negro M87 é como tentar ver algo que, por definição, é impossível de se ver.
+
+
+
+## A telescope the size of the earth
+
+The [Event Horizon telescope (EHT)](https://eventhorizontelescope.org) is an array of eight ground-based radio telescopes forming a computational telescope the size of the earth, studing the universe with unprecedented sensitivity and resolution. The huge virtual telescope, which uses a technique called very-long-baseline interferometry (VLBI), has an angular resolution of [20 micro-arcseconds][resolution] — enough to read a newspaper in New York from a sidewalk café in Paris!
+
+### Principais Objetivos e Resultados
+
+* **A New View of the Universe:** The groundwork for the EHT's groundbreaking image had been laid 100 years earlier when [Sir Arthur Eddington][eddington] yielded the first observational support of Einstein's theory of general relativity.
+
+* **The Black Hole:** EHT was trained on a supermassive black hole approximately 55 million light-years from Earth, lying at the center of the galaxy Messier 87 (M87) in the Virgo galaxy cluster. Its mass is 6.5 billion times the Sun's. It had been studied for [over 100 years](https://www.jpl.nasa.gov/news/news.php?feature=7385), but never before had a black hole been visually observed.
+
+* **Comparing Observations to Theory:** From Einstein’s general theory of relativity, scientists expected to find a shadow-like region caused by gravitational bending and capture of light. Scientists could use it to measure the black hole's enormous mass.
+
+### Desafios
+
+* **Computational scale**
+
+ EHT poses massive data-processing challenges, including rapid atmospheric phase fluctuations, large recording bandwidth, and telescopes that are widely dissimilar and geographically dispersed.
+
+* **Too much information**
+
+ Each day EHT generates over 350 terabytes of observations, stored on helium-filled hard drives. Reducing the volume and complexity of this much data is enormously difficult.
+
+* **Into the unknown**
+
+ When the goal is to see something never before seen, how can scientists be confident the image is correct?
+
+{{< figure src="/images/content_images/cs/dataprocessbh.png" class="csfigcaption" caption="**Etapas de Processamento de Dados do EHT**" alt="data pipeline" align="middle" attr="(Créditos do diagrama: The Astrophysical Journal, Event Horizon Telescope Collaboration)" attrlink="https://iopscience.iop.org/article/10.3847/2041-8213/ab0c57" >}}
+
+## NumPy’s Role
+
+What if there's a problem with the data? Or perhaps an algorithm relies too heavily on a particular assumption. Will the image change drastically if a single parameter is changed?
+
+The EHT collaboration met these challenges by having independent teams evaluate the data, using both established and cutting-edge image reconstruction techniques. When results proved consistent, they were combined to yield the first-of-a-kind image of the black hole.
+
+Their work illustrates the role the scientific Python ecosystem plays in advancing science through collaborative data analysis.
+
+{{< figure src="/images/content_images/cs/bh_numpy_role.png" class="fig-center" alt="role of numpy" caption="**The role of NumPy in Black Hole imaging**" >}}
+
+For example, the [`eht-imaging`][ehtim] Python package provides tools for simulating and performing image reconstruction on VLBI data. NumPy is at the core of array data processing used in this package, as illustrated by the partial software dependency chart below.
+
+{{< figure src="/images/content_images/cs/ehtim_numpy.png" class="fig-center" alt="ehtim dependency map highlighting numpy" caption="**Software dependency chart of ehtim package highlighting NumPy**" >}}
+
+Besides NumPy, many other packages, such as [SciPy](https://www.scipy.org) and [Pandas](https://pandas.io), are part of the data processing pipeline for imaging the black hole. The standard astronomical file formats and time/coordinate transformations were handled by [Astropy][astropy], while [Matplotlib][mpl] was used in visualizing data throughout the analysis pipeline, including the generation of the final image of the black hole.
+
+## Resumo
+
+The efficient and adaptable n-dimensional array that is NumPy's central feature enabled researchers to manipulate large numerical datasets, providing a foundation for the first-ever image of a black hole. A landmark moment in science, it gives stunning visual evidence of Einstein’s theory. The achievement encompasses not only technological breakthroughs but also international collaboration among over 200 scientists and some of the world's best radio observatories. Innovative algorithms and data processing techniques, improving upon existing astronomical models, helped unfold a mystery of the universe.
+
+{{< figure src="/images/content_images/cs/numpy_bh_benefits.png" class="fig-center" alt="numpy benefits" caption="**Key NumPy Capabilities utilized**" >}}
+
+[resolution]: https://eventhorizontelescope.org/press-release-april-10-2019-astronomers-capture-first-image-black-hole
+
+[eddington]: https://en.wikipedia.org/wiki/Eddington_experiment
+
+[ehtim]: https://github.com/achael/eht-imaging
+
+[astropy]: https://www.astropy.org/
+[mpl]: https://matplotlib.org/
From 53051e96f90c370cd0789410fe40d9e33da087fc Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:36:44 +0000
Subject: [PATCH 032/909] New translations arraycomputing.md (Chinese
Simplified)
---
content/zh/arraycomputing.md | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
create mode 100644 content/zh/arraycomputing.md
diff --git a/content/zh/arraycomputing.md b/content/zh/arraycomputing.md
new file mode 100644
index 0000000000..abd29d11c1
--- /dev/null
+++ b/content/zh/arraycomputing.md
@@ -0,0 +1,21 @@
+---
+title: Array Computing
+sidebar: false
+---
+
+*Array computing is the foundation of statistical, mathematical, scientific computing in various contemporary data science and analytics applications such as data visualization, digital signal processing, image processing, bioinformatics, machine learning, AI, and several others.*
+
+Large scale data manipulation and transformation depends on efficient, high-performance array computing. The language of choice for data analytics, machine learning, and productive numerical computing is **Python.**
+
+**Num**erical **Py**thon or NumPy is its de-facto standard Python programming language library that supports large, multi-dimensional arrays and matrices, and comes with a vast collection of high-level mathematical functions to operate on these arrays.
+
+Since the launch of NumPy in 2006, Pandas appeared on the landscape in 2008, and it was not until a couple of years ago that several array computing libraries showed up in succession, crowding the array computing landscape. Many of these newer libraries mimic NumPy-like features and capabilities, and pack newer algorithms and features geared towards machine learning and artificial intelligence applications.
+
+
+
+**Array computing** is based on **arrays** data structures. *Arrays* are used to organize vast amounts of data such that a related set of values can be easily sorted, searched, mathematically manipulated, and transformed easily and quickly.
+
+Array computing is *unique* as it involves operating on the data array *at once*. What this means is that any array operation applies to an entire set of values in one shot. This vectorized approach provides speed and simplicity by enabling programmers to code and operate on aggregates of data, without having to use loops of individual scalar operations.
From ba297b9a4a3e7db9fd3611d732159e9680ab1188 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:36:46 +0000
Subject: [PATCH 033/909] New translations terms.md (Arabic)
---
content/ar/terms.md | 178 ++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 178 insertions(+)
create mode 100644 content/ar/terms.md
diff --git a/content/ar/terms.md b/content/ar/terms.md
new file mode 100644
index 0000000000..9a66045505
--- /dev/null
+++ b/content/ar/terms.md
@@ -0,0 +1,178 @@
+---
+title: Terms of Use
+sidebar: false
+---
+
+*Last updated January 4, 2020*
+
+
+## AGREEMENT TO TERMS
+
+These Terms of Use constitute a legally binding agreement made between you, whether personally or on behalf of an entity (“you”) and NumPy ("**Project**", “**we**”, “**us**”, or “**our**”), concerning your access to and use of the numpy.org website as well as any other media form, media channel, mobile website or mobile application related, linked, or otherwise connected thereto (collectively, the “Site”). You agree that by accessing the Site, you have read, understood, and agreed to be bound by all of these Terms of Use. IF YOU DO NOT AGREE WITH ALL OF THESE TERMS OF USE, THEN YOU ARE EXPRESSLY PROHIBITED FROM USING THE SITE AND YOU MUST DISCONTINUE USE IMMEDIATELY.
+
+
+
+Supplemental terms and conditions or documents that may be posted on the Site from time to time are hereby expressly incorporated herein by reference. We reserve the right, in our sole discretion, to make changes or modifications to these Terms of Use at any time and for any reason. We will alert you about any changes by updating the “Last updated” date of these Terms of Use, and you waive any right to receive specific notice of each such change. It is your responsibility to periodically review these Terms of Use to stay informed of updates. You will be subject to, and will be deemed to have been made aware of and to have accepted, the changes in any revised Terms of Use by your continued use of the Site after the date such revised Terms of Use are posted.
+
+
+
+The information provided on the Site is not intended for distribution to or use by any person or entity in any jurisdiction or country where such distribution or use would be contrary to law or regulation or which would subject us to any registration requirement within such jurisdiction or country. Accordingly, those persons who choose to access the Site from other locations do so on their own initiative and are solely responsible for compliance with local laws, if and to the extent local laws are applicable.
+
+
+## USER REPRESENTATIONS
+
+By using the Site, you represent and warrant that: (1) you have the legal capacity and you agree to comply with these Terms of Use; (2) you will not use the Site for any illegal or unauthorized purpose; and (3) your use of the Site will not violate any applicable law or regulation.
+
+
+If you provide any information that is untrue, inaccurate, not current, or incomplete, we have the right to refuse any and all current or future use of the Site (or any portion thereof).
+
+
+## PROHIBITED ACTIVITIES
+
+You may not access or use the Site for any purpose other than that for which we make the Site available.
+
+As a user of the Site, you agree not to:
+
+1. Systematically retrieve data or other content from the Site to create or compile, directly or indirectly, a collection, compilation, database, or directory without written permission from us.
+
+2. Make any unauthorized use of the Site, including collecting usernames and/or email addresses of users by electronic or other means for the purpose of sending unsolicited email, or creating user accounts by automated means or under false pretenses.
+
+3. Use the Site to advertise or offer to sell goods and services.
+
+4. Circumvent, disable, or otherwise interfere with security-related features of the Site.
+
+5. Engage in unauthorized framing of or linking to the Site.
+
+6. Trick, defraud, or mislead us and other users, especially in any attempt to learn sensitive account information such as user passwords.
+
+7. Make improper use of our support services or submit false reports of abuse or misconduct.
+
+8. Engage in any automated use of the system, such as using scripts to send comments or messages, or using any data mining, robots, or similar data gathering and extraction tools.
+
+9. Interfere with, disrupt, or create an undue burden on the Site or the networks or services connected to the Site.
+
+10. Attempt to impersonate another user or person or use the username of another user.
+
+11. Use any information obtained from the Site in order to harass, abuse, or harm another person.
+
+12. Disparage, tarnish, or otherwise harm, in our opinion, us and/or the Site.
+
+13. Except as may be the result of standard search engine or Internet browser usage, use, launch, develop, or distribute any automated system, including without limitation, any spider, robot, cheat utility, scraper, or offline reader that accesses the Site, or using or launching any unauthorized script or other software.
+
+14. Upload or transmit (or attempt to upload or to transmit) any material that acts as a passive or active information collection or transmission mechanism, including without limitation, clear graphics interchange formats (“gifs”), 1×1 pixels, web bugs, cookies, or other similar devices (sometimes referred to as “spyware” or “passive collection mechanisms” or “pcms”).
+
+15. Upload or transmit (or attempt to upload or to transmit) viruses, Trojan horses, or other material, including excessive use of capital letters and spamming (continuous posting of repetitive text), that interferes with any party’s uninterrupted use and enjoyment of the Site or modifies, impairs, disrupts, alters, or interferes with the use, features, functions, operation, or maintenance of the Site.
+
+16. Harass, annoy, intimidate, or threaten any of our employees or agents engaged in providing any portion of the Site to you.
+
+17. Attempt to bypass any measures of the Site designed to prevent or restrict access to the Site, or any portion of the Site.
+
+
+## SUBMISSIONS
+
+You acknowledge and agree that any questions, comments, suggestions, ideas, feedback, or other information regarding the Site ("Submissions") provided by you to us are non-confidential and shall become our sole property. We shall own exclusive rights, including all intellectual property rights, and shall be entitled to the unrestricted use and dissemination of these Submissions for any lawful purpose, commercial or otherwise, without acknowledgment or compensation to you. You hereby waive all moral rights to any such Submissions, and you hereby warrant that any such Submissions are original with you or that you have the right to submit such Submissions. You agree there shall be no recourse against us for any alleged or actual infringement or misappropriation of any proprietary right in your Submissions.
+
+## THIRD-PARTY WEBSITES AND CONTENT
+
+The Site may contain (or you may be sent via the Site) links to other websites ("Third-Party Websites") as well as articles, photographs, text, graphics, pictures, designs, music, sound, video, information, applications, software, and other content or items belonging to or originating from third parties ("Third-Party Content"). Such Third-Party Websites and Third-Party Content are not investigated, monitored, or checked for accuracy, appropriateness, or completeness by us, and we are not responsible for any Third-Party Websites accessed through the Site or any Third-Party Content posted on, available through, or installed from the Site, including the content, accuracy, offensiveness, opinions, reliability, privacy practices, or other policies of or contained in the Third-Party Websites or the Third-Party Content. Inclusion of, linking to, or permitting the use or installation of any Third-Party Websites or any Third-Party Content does not imply approval or endorsement thereof by us. If you decide to leave the Site and access the Third-Party Websites or to use or install any Third-Party Content, you do so at your own risk, and you should be aware these Terms of Use no longer govern. You should review the applicable terms and policies, including privacy and data gathering practices, of any website to which you navigate from the Site or relating to any applications you use or install from the Site. Any purchases you make through Third-Party Websites will be through other websites and from other companies, and we take no responsibility whatsoever in relation to such purchases which are exclusively between you and the applicable third party. You agree and acknowledge that we do not endorse the products or services offered on Third-Party Websites and you shall hold us harmless from any harm caused by your purchase of such products or services. Additionally, you shall hold us harmless from any losses sustained by you or harm caused to you relating to or resulting in any way from any Third-Party Content or any contact with Third-Party Websites.
+
+
+## SITE MANAGEMENT
+
+We reserve the right, but not the obligation, to: (1) monitor the Site for violations of these Terms of Use; (2) take appropriate legal action against anyone who, in our sole discretion, violates the law or these Terms of Use, including without limitation, reporting such user to law enforcement authorities; (3) in our sole discretion and without limitation, refuse, restrict access to, limit the availability of, or disable (to the extent technologically feasible) any of your Contributions or any portion thereof; (4) in our sole discretion and without limitation, notice, or liability, to remove from the Site or otherwise disable all files and content that are excessive in size or are in any way burdensome to our systems; and (5) otherwise manage the Site in a manner designed to protect our rights and property and to facilitate the proper functioning of the Site.
+
+
+## PRIVACY POLICY
+
+We care about data privacy and security. Please review our [Privacy Policy](/privacy). By using the Site, you agree to be bound by our Privacy Policy, which is incorporated into these Terms of Use. Please be advised the Site is hosted in the United States. If you access the Site from the European Union, Asia, or any other region of the world with laws or other requirements governing personal data collection, use, or disclosure that differ from applicable laws in the United States, then through your continued use of the Site, you are transferring your data to the United States, and you expressly consent to have your data transferred to and processed in the United States. Further, we do not knowingly accept, request, or solicit information from children or knowingly market to children. Therefore, in accordance with the U.S. Children’s Online Privacy Protection Act, if we receive actual knowledge that anyone under the age of 13 has provided personal information to us without the requisite and verifiable parental consent, we will delete that information from the Site as quickly as is reasonably practical.
+
+## TERM AND TERMINATION
+
+These Terms of Use shall remain in full force and effect while you use the Site. WITHOUT LIMITING ANY OTHER PROVISION OF THESE TERMS OF USE, WE RESERVE THE RIGHT TO, IN OUR SOLE DISCRETION AND WITHOUT NOTICE OR LIABILITY, DENY ACCESS TO AND USE OF THE SITE (INCLUDING BLOCKING CERTAIN IP ADDRESSES), TO ANY PERSON FOR ANY REASON OR FOR NO REASON, INCLUDING WITHOUT LIMITATION FOR BREACH OF ANY REPRESENTATION, WARRANTY, OR COVENANT CONTAINED IN THESE TERMS OF USE OR OF ANY APPLICABLE LAW OR REGULATION. WE MAY TERMINATE YOUR USE OR PARTICIPATION IN THE SITE OR DELETE ANY CONTENT OR INFORMATION THAT YOU POSTED AT ANY TIME, WITHOUT WARNING, IN OUR SOLE DISCRETION.
+
+
+## MODIFICATIONS AND INTERRUPTIONS
+
+We reserve the right to change, modify, or remove the contents of the Site at any time or for any reason at our sole discretion without notice. However, we have no obligation to update any information on our Site. We also reserve the right to modify or discontinue all or part of the Site without notice at any time. We will not be liable to you or any third party for any modification, suspension, or discontinuance of the Site.
+
+We cannot guarantee the Site will be available at all times. We may experience hardware, software, or other problems or need to perform maintenance related to the Site, resulting in interruptions, delays, or errors. We reserve the right to change, revise, update, suspend, discontinue, or otherwise modify the Site at any time or for any reason without notice to you. You agree that we have no liability whatsoever for any loss, damage, or inconvenience caused by your inability to access or use the Site during any downtime or discontinuance of the Site. Nothing in these Terms of Use will be construed to obligate us to maintain and support the Site or to supply any corrections, updates, or releases in connection therewith.
+
+
+## GOVERNING LAW
+
+These Terms of Use and your use of the Site are governed by and construed in accordance with the laws of the State of Texas applicable to agreements made and to be entirely performed within the State of Texas, without regard to its conflict of law principles.
+
+
+## DISPUTE RESOLUTION
+
+### Informal Negotiations
+
+To expedite resolution and control the cost of any dispute, controversy, or claim related to these Terms of Use (each a "Dispute" and collectively, the “Disputes”) brought by either you or us (individually, a “Party” and collectively, the “Parties”), the Parties agree to first attempt to negotiate any Dispute (except those Disputes expressly provided below) informally for at least thirty (30) days before initiating arbitration. Such informal negotiations commence upon written notice from one Party to the other Party.
+
+
+### Binding Arbitration
+
+If the Parties are unable to resolve a Dispute through informal negotiations, the Dispute (except those Disputes expressly excluded below) will be finally and exclusively resolved by binding arbitration. YOU UNDERSTAND THAT WITHOUT THIS PROVISION, YOU WOULD HAVE THE RIGHT TO SUE IN COURT AND HAVE A JURY TRIAL. The arbitration shall be commenced and conducted under the Commercial Arbitration Rules of the American Arbitration Association ("AAA") and, where appropriate, the AAA’s Supplementary Procedures for Consumer Related Disputes ("AAA Consumer Rules"), both of which are available at the AAA website www.adr.org. Your arbitration fees and your share of arbitrator compensation shall be governed by the AAA Consumer Rules and, where appropriate, limited by the AAA Consumer Rules. If such costs are determined to by the arbitrator to be excessive, we will pay all arbitration fees and expenses. The arbitration may be conducted in person, through the submission of documents, by phone, or online. The arbitrator will make a decision in writing, but need not provide a statement of reasons unless requested by either Party. The arbitrator must follow applicable law, and any award may be challenged if the arbitrator fails to do so. Except where otherwise required by the applicable AAA rules or applicable law, the arbitration will take place in Travis County, Texas. Except as otherwise provided herein, the Parties may litigate in court to compel arbitration, stay proceedings pending arbitration, or to confirm, modify, vacate, or enter judgment on the award entered by the arbitrator.
+
+If for any reason, a Dispute proceeds in court rather than arbitration, the Dispute shall be commenced or prosecuted in the state and federal courts located in Travis County, Texas, and the Parties hereby consent to, and waive all defenses of lack of personal jurisdiction, and forum non conveniens with respect to venue and jurisdiction in such state and federal courts. Application of the United Nations Convention on Contracts for the International Sale of Goods and the the Uniform Computer Information Transaction Act (UCITA) are excluded from these Terms of Use.
+
+In no event shall any Dispute brought by either Party related in any way to the Site be commenced more than one (1) years after the cause of action arose. If this provision is found to be illegal or unenforceable, then neither Party will elect to arbitrate any Dispute falling within that portion of this provision found to be illegal or unenforceable and such Dispute shall be decided by a court of competent jurisdiction within the courts listed for jurisdiction above, and the Parties agree to submit to the personal jurisdiction of that court.
+
+
+### Restrictions
+
+The Parties agree that any arbitration shall be limited to the Dispute between the Parties individually. To the full extent permitted by law, (a) no arbitration shall be joined with any other proceeding; (b) there is no right or authority for any Dispute to be arbitrated on a class-action basis or to utilize class action procedures; and (c) there is no right or authority for any Dispute to be brought in a purported representative capacity on behalf of the general public or any other persons.
+
+
+### Exceptions to Informal Negotiations and Arbitration
+
+The Parties agree that the following Disputes are not subject to the above provisions concerning informal negotiations and binding arbitration: (a) any Disputes seeking to enforce or protect, or concerning the validity of, any of the intellectual property rights of a Party; (b) any Dispute related to, or arising from, allegations of theft, piracy, invasion of privacy, or unauthorized use; and (c) any claim for injunctive relief. If this provision is found to be illegal or unenforceable, then neither Party will elect to arbitrate any Dispute falling within that portion of this provision found to be illegal or unenforceable and such Dispute shall be decided by a court of competent jurisdiction within the courts listed for jurisdiction above, and the Parties agree to submit to the personal jurisdiction of that court.
+
+
+## CORRECTIONS
+
+There may be information on the Site that contains typographical errors, inaccuracies, or omissions. We reserve the right to correct any errors, inaccuracies, or omissions and to change or update the information on the Site at any time, without prior notice.
+
+
+## DISCLAIMER
+
+THE SITE IS PROVIDED ON AN AS-IS AND AS-AVAILABLE BASIS. YOU AGREE THAT YOUR USE OF THE SITE AND OUR SERVICES WILL BE AT YOUR SOLE RISK. TO THE FULLEST EXTENT PERMITTED BY LAW, WE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, IN CONNECTION WITH THE SITE AND YOUR USE THEREOF, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. WE MAKE NO WARRANTIES OR REPRESENTATIONS ABOUT THE ACCURACY OR COMPLETENESS OF THE SITE’S CONTENT OR THE CONTENT OF ANY WEBSITES LINKED TO THE SITE AND WE WILL ASSUME NO LIABILITY OR RESPONSIBILITY FOR ANY (1) ERRORS, MISTAKES, OR INACCURACIES OF CONTENT AND MATERIALS, (2) PERSONAL INJURY OR PROPERTY DAMAGE, OF ANY NATURE WHATSOEVER, RESULTING FROM YOUR ACCESS TO AND USE OF THE SITE, (3) ANY UNAUTHORIZED ACCESS TO OR USE OF OUR SECURE SERVERS AND/OR ANY AND ALL PERSONAL INFORMATION AND/OR FINANCIAL INFORMATION STORED THEREIN, (4) ANY INTERRUPTION OR CESSATION OF TRANSMISSION TO OR FROM THE SITE, (5) ANY BUGS, VIRUSES, TROJAN HORSES, OR THE LIKE WHICH MAY BE TRANSMITTED TO OR THROUGH THE SITE BY ANY THIRD PARTY, AND/OR (6) ANY ERRORS OR OMISSIONS IN ANY CONTENT AND MATERIALS OR FOR ANY LOSS OR DAMAGE OF ANY KIND INCURRED AS A RESULT OF THE USE OF ANY CONTENT POSTED, TRANSMITTED, OR OTHERWISE MADE AVAILABLE VIA THE SITE. WE DO NOT WARRANT, ENDORSE, GUARANTEE, OR ASSUME RESPONSIBILITY FOR ANY PRODUCT OR SERVICE ADVERTISED OR OFFERED BY A THIRD PARTY THROUGH THE SITE, ANY HYPERLINKED WEBSITE, OR ANY WEBSITE OR MOBILE APPLICATION FEATURED IN ANY BANNER OR OTHER ADVERTISING, AND WE WILL NOT BE A PARTY TO OR IN ANY WAY BE RESPONSIBLE FOR MONITORING ANY TRANSACTION BETWEEN YOU AND ANY THIRD-PARTY PROVIDERS OF PRODUCTS OR SERVICES. AS WITH THE PURCHASE OF A PRODUCT OR SERVICE THROUGH ANY MEDIUM OR IN ANY ENVIRONMENT, YOU SHOULD USE YOUR BEST JUDGMENT AND EXERCISE CAUTION WHERE APPROPRIATE.
+
+
+## LIMITATIONS OF LIABILITY
+
+IN NO EVENT WILL WE OR OUR DIRECTORS, EMPLOYEES, OR AGENTS BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, EXEMPLARY, INCIDENTAL, SPECIAL, OR PUNITIVE DAMAGES, INCLUDING LOST PROFIT, LOST REVENUE, LOSS OF DATA, OR OTHER DAMAGES ARISING FROM YOUR USE OF THE SITE, EVEN IF WE HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. NOTWITHSTANDING ANYTHING TO THE CONTRARY CONTAINED HEREIN, OUR LIABILITY TO YOU FOR ANY CAUSE WHATSOEVER AND REGARDLESS OF THE FORM OF THE ACTION, WILL AT ALL TIMES BE LIMITED TO THE AMOUNT PAID, IF ANY, BY YOU TO US DURING THE SIX (6) MONTH PERIOD PRIOR TO ANY CAUSE OF ACTION ARISING. CERTAIN STATE LAWS DO NOT ALLOW LIMITATIONS ON IMPLIED WARRANTIES OR THE EXCLUSION OR LIMITATION OF CERTAIN DAMAGES. IF THESE LAWS APPLY TO YOU, SOME OR ALL OF THE ABOVE DISCLAIMERS OR LIMITATIONS MAY NOT APPLY TO YOU, AND YOU MAY HAVE ADDITIONAL RIGHTS.
+
+
+## INDEMNIFICATION
+
+You agree to defend, indemnify, and hold us harmless, including our subsidiaries, affiliates, and all of our respective officers, agents, partners, and employees, from and against any loss, damage, liability, claim, or demand, including reasonable attorneys’ fees and expenses, made by any third party due to or arising out of: (1) use of the Site; (2) breach of these Terms of Use; (3) any breach of your representations and warranties set forth in these Terms of Use; (4) your violation of the rights of a third party, including but not limited to intellectual property rights; or (5) any overt harmful act toward any other user of the Site with whom you connected via the Site. Notwithstanding the foregoing, we reserve the right, at your expense, to assume the exclusive defense and control of any matter for which you are required to indemnify us, and you agree to cooperate, at your expense, with our defense of such claims. We will use reasonable efforts to notify you of any such claim, action, or proceeding which is subject to this indemnification upon becoming aware of it.
+
+
+## USER DATA
+
+We will maintain certain data that you transmit to the Site for the purpose of managing the performance of the Site, as well as data relating to your use of the Site. Although we perform regular routine backups of data, you are solely responsible for all data that you transmit or that relates to any activity you have undertaken using the Site. You agree that we shall have no liability to you for any loss or corruption of any such data, and you hereby waive any right of action against us arising from any such loss or corruption of such data.
+
+
+## ELECTRONIC COMMUNICATIONS, TRANSACTIONS, AND SIGNATURES
+
+Visiting the Site, sending us emails, and completing online forms constitute electronic communications. You consent to receive electronic communications, and you agree that all agreements, notices, disclosures, and other communications we provide to you electronically, via email and on the Site, satisfy any legal requirement that such communication be in writing. YOU HEREBY AGREE TO THE USE OF ELECTRONIC SIGNATURES, CONTRACTS, ORDERS, AND OTHER RECORDS, AND TO ELECTRONIC DELIVERY OF NOTICES, POLICIES, AND RECORDS OF TRANSACTIONS INITIATED OR COMPLETED BY US OR VIA THE SITE. You hereby waive any rights or requirements under any statutes, regulations, rules, ordinances, or other laws in any jurisdiction which require an original signature or delivery or retention of non-electronic records, or to payments or the granting of credits by any means other than electronic means.
+
+
+## CALIFORNIA USERS AND RESIDENTS
+
+If any complaint with us is not satisfactorily resolved, you can contact the Complaint Assistance Unit of the Division of Consumer Services of the California Department of Consumer Affairs in writing at 1625 North Market Blvd., Suite N 112, Sacramento, California 95834 or by telephone at (800) 952-5210 or (916) 445-1254.
+
+
+## MISCELLANEOUS
+
+These Terms of Use and any policies or operating rules posted by us on the Site or in respect to the Site constitute the entire agreement and understanding between you and us. Our failure to exercise or enforce any right or provision of these Terms of Use shall not operate as a waiver of such right or provision. These Terms of Use operate to the fullest extent permissible by law. We may assign any or all of our rights and obligations to others at any time. We shall not be responsible or liable for any loss, damage, delay, or failure to act caused by any cause beyond our reasonable control. If any provision or part of a provision of these Terms of Use is determined to be unlawful, void, or unenforceable, that provision or part of the provision is deemed severable from these Terms of Use and does not affect the validity and enforceability of any remaining provisions. There is no joint venture, partnership, employment or agency relationship created between you and us as a result of these Terms of Use or use of the Site. You agree that these Terms of Use will not be construed against us by virtue of having drafted them. You hereby waive any and all defenses you may have based on the electronic form of these Terms of Use and the lack of signing by the parties hereto to execute these Terms of Use.
+
+## CONTACT US
+
+In order to resolve a complaint regarding the Site or to receive further information regarding use of the Site, please contact us at:
+
+NumFOCUS, Inc. P.O. Box 90596 Austin, TX, USA 78709 info@numfocus.org +1 (512) 222-5449
+
+
+
From 4d83fab9cc0c280e170dade45a65041fb9be4074 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:36:47 +0000
Subject: [PATCH 034/909] New translations contribute.md (Chinese Simplified)
---
content/zh/contribute.md | 78 ++++++++++++++++++++++++++++++++++++++++
1 file changed, 78 insertions(+)
create mode 100644 content/zh/contribute.md
diff --git a/content/zh/contribute.md b/content/zh/contribute.md
new file mode 100644
index 0000000000..2533761d12
--- /dev/null
+++ b/content/zh/contribute.md
@@ -0,0 +1,78 @@
+- - -
+title: Contribute to NumPy sidebar: false
+- - -
+
+The NumPy project welcomes your expertise and enthusiasm! Your choices aren't limited to programming -- in addition to
+
+- [Writing code](#writing-code)
+
+you can
+
+- [Review pull requests](#reviewing-pull-requests)
+- [Develop tutorials, presentations, and other educational material](#developing-educational-materials)
+- [Triage issues](#issue-triaging)
+- [Work on our website](#website-development)
+- [Contribute graphic design](#graphic-design)
+- [Translate website content](#translating-website-content)
+- [Serve as a community coordinator](#community-coordination-and-outreach)
+- [Write grant proposals and help with other fundraising](#fundraising)
+
+If you're unsure where to start or how your skills fit in, _reach out!_ You can ask on the [mailing list](https://mail.python.org/mailman/listinfo/numpy-discussion) or [GitHub](http://github.com/numpy/numpy) (open an [issue](https://github.com/numpy/numpy/issues) or comment on a relevant issue).
+
+Those are our preferred channels (open source is open by nature), but if you prefer to talk privately, contact our community coordinators at or on [Slack](https://numpy-team.slack.com) (write for an invite).
+
+We also have a biweekly _community call_, details of which are announced on the [mailing list](https://mail.python.org/mailman/listinfo/numpy-discussion). You are very welcome to join. If you are new to contributing to open source, we also highly recommend reading [this guide](https://opensource.guide/how-to-contribute/).
+
+Our community aspires to treat everyone equally and to value all contributions. We have a [Code of Conduct](/code-of-conduct) to foster an open and welcoming environment.
+
+### Writing code
+
+Programmers, this [guide](https://numpy.org/devdocs/dev/index.html#development-process-summary) explains how to contribute to the codebase.
+
+### Reviewing pull requests
+The project has more than 250 open pull requests -- meaning many potential improvements and many open-source contributors waiting for feedback. If you're a developer who knows NumPy, you can help even if you're not familiar with the codebase. You can:
+* summarize a long-running discussion
+* triage documentation PRs
+* test proposed changes
+
+
+### Developing educational materials
+
+NumPy's [User Guide](https://numpy.org/devdocs) is undergoing rehabilitation. We're in need of new tutorials, how-to's, and deep-dive explanations, and the site needs restructuring. Opportunities aren't limited to writers. We'd also welcome worked examples, notebooks, and videos. [NEP 44 — Restructuring the NumPyDocumentation](https://numpy.org/neps/nep-0044-restructuring-numpy-docs.html) lays out our ideas -- and you may have others.
+
+
+### Issue triaging
+
+The [NumPy issue tracker](https://github.com/numpy/numpy/issues) has a _lot_ of open issues. Some are no longer valid, some should be prioritized, and some would make good issues for new contributors. You can:
+
+* check if older bugs are still present
+* find duplicate issues and link related ones
+* add good self-contained reproducers to issues
+* label issues correctly (this requires triage rights -- just ask)
+
+Please just dive in.
+
+
+### Website development
+
+We've just revamped our website, but we're far from done. If you love web development, these [issues](https://github.com/numpy/numpy.org/issues?q=is%3Aissue+is%3Aopen+label%3Adesign) list some of our unmet needs -- and feel free to share your own ideas.
+
+
+### Graphic design
+
+We can barely begin to list the contributions a graphic designer can make here. Our docs are parched for illustration; our growing website craves images -- opportunities abound.
+
+
+### Translating website content
+
+We plan multiple translations of [numpy.org](https://numpy.org) to make NumPy accessible to users in their native language. Volunteer translators are at the heart of this effort. See [here](https://numpy.org/neps/nep-0028-website-redesign.html#translation-multilingual-i18n) for background; comment on [this GitHub issue](https://github.com/numpy/numpy.org/issues/55) to sign up.
+
+
+### Community coordination and outreach
+
+Through community contact we share our work more widely and learn where we're falling short. We're eager to get more people involved in efforts like our [Twitter](https://twitter.com/numpy_team) account, organizing NumPy [code sprints](https://scisprints.github.io/), a newsletter, and perhaps a blog.
+
+### Fundraising
+
+NumPy was all-volunteer for many years, but as its importance grew it became clear that to ensure stability and growth we'd need financial support. [This SciPy'19 talk](https://www.youtube.com/watch?v=dBTJD_FDVjU) explains how much difference that support has made. Like all the nonprofit world, we're constantly searching for grants, sponsorships, and other kinds of support. We have a number of ideas and of course we welcome more. Fundraising is a scarce skill here -- we'd appreciate your help.
+
From ed8cd9e2a6856af44c17d30056f393ab0ab00020 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:36:49 +0000
Subject: [PATCH 035/909] New translations contribute.md (Korean)
---
content/ko/contribute.md | 78 ++++++++++++++++++++++++++++++++++++++++
1 file changed, 78 insertions(+)
create mode 100644 content/ko/contribute.md
diff --git a/content/ko/contribute.md b/content/ko/contribute.md
new file mode 100644
index 0000000000..2533761d12
--- /dev/null
+++ b/content/ko/contribute.md
@@ -0,0 +1,78 @@
+- - -
+title: Contribute to NumPy sidebar: false
+- - -
+
+The NumPy project welcomes your expertise and enthusiasm! Your choices aren't limited to programming -- in addition to
+
+- [Writing code](#writing-code)
+
+you can
+
+- [Review pull requests](#reviewing-pull-requests)
+- [Develop tutorials, presentations, and other educational material](#developing-educational-materials)
+- [Triage issues](#issue-triaging)
+- [Work on our website](#website-development)
+- [Contribute graphic design](#graphic-design)
+- [Translate website content](#translating-website-content)
+- [Serve as a community coordinator](#community-coordination-and-outreach)
+- [Write grant proposals and help with other fundraising](#fundraising)
+
+If you're unsure where to start or how your skills fit in, _reach out!_ You can ask on the [mailing list](https://mail.python.org/mailman/listinfo/numpy-discussion) or [GitHub](http://github.com/numpy/numpy) (open an [issue](https://github.com/numpy/numpy/issues) or comment on a relevant issue).
+
+Those are our preferred channels (open source is open by nature), but if you prefer to talk privately, contact our community coordinators at or on [Slack](https://numpy-team.slack.com) (write for an invite).
+
+We also have a biweekly _community call_, details of which are announced on the [mailing list](https://mail.python.org/mailman/listinfo/numpy-discussion). You are very welcome to join. If you are new to contributing to open source, we also highly recommend reading [this guide](https://opensource.guide/how-to-contribute/).
+
+Our community aspires to treat everyone equally and to value all contributions. We have a [Code of Conduct](/code-of-conduct) to foster an open and welcoming environment.
+
+### Writing code
+
+Programmers, this [guide](https://numpy.org/devdocs/dev/index.html#development-process-summary) explains how to contribute to the codebase.
+
+### Reviewing pull requests
+The project has more than 250 open pull requests -- meaning many potential improvements and many open-source contributors waiting for feedback. If you're a developer who knows NumPy, you can help even if you're not familiar with the codebase. You can:
+* summarize a long-running discussion
+* triage documentation PRs
+* test proposed changes
+
+
+### Developing educational materials
+
+NumPy's [User Guide](https://numpy.org/devdocs) is undergoing rehabilitation. We're in need of new tutorials, how-to's, and deep-dive explanations, and the site needs restructuring. Opportunities aren't limited to writers. We'd also welcome worked examples, notebooks, and videos. [NEP 44 — Restructuring the NumPyDocumentation](https://numpy.org/neps/nep-0044-restructuring-numpy-docs.html) lays out our ideas -- and you may have others.
+
+
+### Issue triaging
+
+The [NumPy issue tracker](https://github.com/numpy/numpy/issues) has a _lot_ of open issues. Some are no longer valid, some should be prioritized, and some would make good issues for new contributors. You can:
+
+* check if older bugs are still present
+* find duplicate issues and link related ones
+* add good self-contained reproducers to issues
+* label issues correctly (this requires triage rights -- just ask)
+
+Please just dive in.
+
+
+### Website development
+
+We've just revamped our website, but we're far from done. If you love web development, these [issues](https://github.com/numpy/numpy.org/issues?q=is%3Aissue+is%3Aopen+label%3Adesign) list some of our unmet needs -- and feel free to share your own ideas.
+
+
+### Graphic design
+
+We can barely begin to list the contributions a graphic designer can make here. Our docs are parched for illustration; our growing website craves images -- opportunities abound.
+
+
+### Translating website content
+
+We plan multiple translations of [numpy.org](https://numpy.org) to make NumPy accessible to users in their native language. Volunteer translators are at the heart of this effort. See [here](https://numpy.org/neps/nep-0028-website-redesign.html#translation-multilingual-i18n) for background; comment on [this GitHub issue](https://github.com/numpy/numpy.org/issues/55) to sign up.
+
+
+### Community coordination and outreach
+
+Through community contact we share our work more widely and learn where we're falling short. We're eager to get more people involved in efforts like our [Twitter](https://twitter.com/numpy_team) account, organizing NumPy [code sprints](https://scisprints.github.io/), a newsletter, and perhaps a blog.
+
+### Fundraising
+
+NumPy was all-volunteer for many years, but as its importance grew it became clear that to ensure stability and growth we'd need financial support. [This SciPy'19 talk](https://www.youtube.com/watch?v=dBTJD_FDVjU) explains how much difference that support has made. Like all the nonprofit world, we're constantly searching for grants, sponsorships, and other kinds of support. We have a number of ideas and of course we welcome more. Fundraising is a scarce skill here -- we'd appreciate your help.
+
From 19baea4d79de2615ee63a049ba4ada9a5bf21bb4 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:36:51 +0000
Subject: [PATCH 036/909] New translations contribute.md (Japanese)
---
content/ja/contribute.md | 78 ++++++++++++++++++++++++++++++++++++++++
1 file changed, 78 insertions(+)
create mode 100644 content/ja/contribute.md
diff --git a/content/ja/contribute.md b/content/ja/contribute.md
new file mode 100644
index 0000000000..040b29464d
--- /dev/null
+++ b/content/ja/contribute.md
@@ -0,0 +1,78 @@
+- - -
+title: Numpy に貢献する サイドバー: false
+- - -
+
+Numpyプロジェクトを成功させるには、あなたの専門知識とプロジェクトに関する熱意が必要です。 Numpyに貢献する方法はコーディングだけではありません。
+
+- [コードを書く。](#writing-code)
+
+他にも下記の貢献の方法があります:
+
+- [プラリクエストのレビュー](#reviewing-pull-requests)
+- [チュートリアル、プレゼン資料、その他の教育資料の作成](#developing-educational-materials)
+- [イシューのトリアージ。](#issue-triaging)
+- [ウェブサイトのメンテナンス](#website-development)
+- [グラフィックデザインへの貢献](#graphic-design)
+- [ウェブサイトの翻訳](#translating-website-content)
+- [コミュニティのコーディネーターとしての貢献](#community-coordination-and-outreach)
+- [助成金のプロポーザルの作成や他の人の資金調達のサポート](#fundraising)
+
+もしどの分野で, 自分が貢献出来るか、わからない場合は、 _是非ご連絡下さい。_ 連絡の方法としては、 [メーリングリスト](https://mail.python.org/mailman/listinfo/numpy-discussion) 、 [GitHub](http://github.com/numpy/numpy)、 [イシューの作成](https://github.com/numpy/numpy/issues) 、関連するイシューへのコメントがあります。
+
+これらが私達にとって好ましい連絡手段ですが(元来、オープンソースプロジェクトはオープンな方法を好みます)、もしどうしても非公開の方法で連絡を取りたい場合は、コミュニティコーディネーターに連絡して下さい。連絡先としては、 または、[Slack](https://numpy-team.slack.com) (グループに招待するためにこちらに連絡お願いします: )があります。
+
+また、隔週の _コミュニティミーティング_もあり、詳細は [メーリングリスト](https://mail.python.org/mailman/listinfo/numpy-discussion) で発表されています。 是非、参加してみて下さい! オープンソースプロジェクトに貢献するのが初めての方は、是非、 [このガイド](https://opensource.guide/how-to-contribute/) を読んでみて下さい。
+
+私たちのコミュニティは、誰もが平等に扱われ、すべての貢献が平等に扱われることを目指しています。 私達はオープンで居心地の良いコミュニティを作るために [行動基準](/code-of-conduct) を制定しています。
+
+### コードを書く
+
+プログラマーの方々に向けて、こちらの [ガイド](https://numpy.org/devdocs/dev/index.html#development-process-summary)でNumpyのコードに貢献する方法か説明されています。
+
+### プルリクエストのレビュー
+Numpyプロジェクトには現時点で250以上のオープンなプルリクエストがあり、多くの 改善要求と多くのレビュワーからのフィードバックを待っています。 もしあなたがNumPy を使ったことがある場合、 たとえNumpyコードベースに慣れていない場合でも貢献する方法はあります。 例えば、
+* 長期にわたる議論をまとめる
+* ドキュメントのPRをトリアージする
+* 提案された変更をテストする
+
+
+### 教育用の資料を作成する
+
+NumPy の [ユーザガイド](https://numpy.org/devdocs) は現在、大規模な再設計中です。 新しいNumpyのWebページは、新しいチュートリアルや、Numpyの使い方、Numpy内部の深い説明など必要としており、サイト全体にも再設計と再構築が必要です。 このウェブサイトの再構築の作業は、ドキュメントを書くだけではありません。 コード例や、ノートブック、ビデオなどの作成も歓迎しています。 [NEP 44 — Restructuring the NumPyDocumentation](https://numpy.org/neps/nep-0044-restructuring-numpy-docs.html)に、ウェブサイトの再構築についての詳細が説明されています。
+
+
+### イシューのトリアージ
+
+[NumPyのイシュートラッカー](https://github.com/numpy/numpy/issues) には、 _沢山の_Open状態のイシューがあります。 いくつかのイシューはすでに解決されており、いくつかは優先順位付けされるべきであり、 いくつかは初心者が取り組むのに良いイシューになるでしょう。 例えば、できる貢献としては、
+
+* 古いバグがまだ残っているかを確認する
+* 重複したイシューを見つけ、お互いに関連づける。
+* 問題を再現するコードを作成すること
+* イシューに正しいラベル付けをすること(トリアージ権が必要なので、必要で有れば連絡下さい)
+
+是非参加してみてください。
+
+
+### ウェブサイトの開発
+
+私たちはちょうどウェブサイトの再設計を始めました。しかし、それらはまだ完了していません。 もしWeb開発が好きなら、この[イシュー](https://github.com/numpy/numpy.org/issues?q=is%3Aissue+is%3Aopen+label%3Adesign) ではまだ実装されていない要求が列挙されているので、是非あなたのアイデアを共有してください。
+
+
+### グラフィックデザイン
+
+残念ながら、グラフィックデザイナーの方々が可能な貢献をリストアップすることは難しいです。 しかし、私たちのドキュメントは説明のために可視化が重要であり、私たちの拡大しているウェブサイトは良い画像を求めていることから、 貢献する機会が沢山あると言えます。
+
+
+### ウェブサイトの翻訳
+
+私達は、[numpy.org](https://numpy.org) を複数言語に翻訳し、Numpyを母国語でアクセスできるようにしたいと思っています。 これを実現するには、ボランティアの翻訳者が必要です。 詳しくは[このイシュー](https://numpy.org/neps/nep-0028-website-redesign.html#translation-multilingual-i18n)を参照してください。 [この GitHubイシュー](https://github.com/numpy/numpy.org/issues/55) にコメントしてサインアップしてください。
+
+
+### コミュニティの調整とアウトリーチ
+
+コミュニティとのコミュニケーションを通じて、私たちは、Numpyより広く知ってもらうようにし、どこに問題があるのかを知りたいと思っています。 私達は、[Twitter](https://twitter.com/numpy_team) アカウントや、NumPy [code sprints](https://scisprints.github.io/)の開催, ニュースレターの発行、そしておそらくブログなどを通じて、より沢山の人にコミュニティに参加して欲しいと思っています。
+
+### 資金調達
+
+NumPyは何年にも渡ってボランティアベースで活動していましたが、Bumpy の重要性が高まるにつれ、安定性と成長のためには資金面での支援が必要であることがわかってきました。 こちらの[SciPy'19のプレゼン](https://www.youtube.com/watch?v=dBTJD_FDVjU) では、資金的なサポートを受けたことで、どれだけ違いが出たかを説明しています。 他の非営利団体のように、私たちは助成金や、スポンサーシップ、その他の資金支援を常に探しています。 私たちはすでにいくつかの資金調達のアイデアを持っていますが、他にもより多くを資金調達を受けたいと思っています。 資金調達に関する知識は、我々には不足しているスキルです。是非、あなたのサポートをお待ちしています。
+
From b1a605510b0b7851de3317f0b034409a8e5d577b Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:36:52 +0000
Subject: [PATCH 037/909] New translations contribute.md (Spanish)
---
content/es/contribute.md | 78 ++++++++++++++++++++++++++++++++++++++++
1 file changed, 78 insertions(+)
create mode 100644 content/es/contribute.md
diff --git a/content/es/contribute.md b/content/es/contribute.md
new file mode 100644
index 0000000000..2533761d12
--- /dev/null
+++ b/content/es/contribute.md
@@ -0,0 +1,78 @@
+- - -
+title: Contribute to NumPy sidebar: false
+- - -
+
+The NumPy project welcomes your expertise and enthusiasm! Your choices aren't limited to programming -- in addition to
+
+- [Writing code](#writing-code)
+
+you can
+
+- [Review pull requests](#reviewing-pull-requests)
+- [Develop tutorials, presentations, and other educational material](#developing-educational-materials)
+- [Triage issues](#issue-triaging)
+- [Work on our website](#website-development)
+- [Contribute graphic design](#graphic-design)
+- [Translate website content](#translating-website-content)
+- [Serve as a community coordinator](#community-coordination-and-outreach)
+- [Write grant proposals and help with other fundraising](#fundraising)
+
+If you're unsure where to start or how your skills fit in, _reach out!_ You can ask on the [mailing list](https://mail.python.org/mailman/listinfo/numpy-discussion) or [GitHub](http://github.com/numpy/numpy) (open an [issue](https://github.com/numpy/numpy/issues) or comment on a relevant issue).
+
+Those are our preferred channels (open source is open by nature), but if you prefer to talk privately, contact our community coordinators at or on [Slack](https://numpy-team.slack.com) (write for an invite).
+
+We also have a biweekly _community call_, details of which are announced on the [mailing list](https://mail.python.org/mailman/listinfo/numpy-discussion). You are very welcome to join. If you are new to contributing to open source, we also highly recommend reading [this guide](https://opensource.guide/how-to-contribute/).
+
+Our community aspires to treat everyone equally and to value all contributions. We have a [Code of Conduct](/code-of-conduct) to foster an open and welcoming environment.
+
+### Writing code
+
+Programmers, this [guide](https://numpy.org/devdocs/dev/index.html#development-process-summary) explains how to contribute to the codebase.
+
+### Reviewing pull requests
+The project has more than 250 open pull requests -- meaning many potential improvements and many open-source contributors waiting for feedback. If you're a developer who knows NumPy, you can help even if you're not familiar with the codebase. You can:
+* summarize a long-running discussion
+* triage documentation PRs
+* test proposed changes
+
+
+### Developing educational materials
+
+NumPy's [User Guide](https://numpy.org/devdocs) is undergoing rehabilitation. We're in need of new tutorials, how-to's, and deep-dive explanations, and the site needs restructuring. Opportunities aren't limited to writers. We'd also welcome worked examples, notebooks, and videos. [NEP 44 — Restructuring the NumPyDocumentation](https://numpy.org/neps/nep-0044-restructuring-numpy-docs.html) lays out our ideas -- and you may have others.
+
+
+### Issue triaging
+
+The [NumPy issue tracker](https://github.com/numpy/numpy/issues) has a _lot_ of open issues. Some are no longer valid, some should be prioritized, and some would make good issues for new contributors. You can:
+
+* check if older bugs are still present
+* find duplicate issues and link related ones
+* add good self-contained reproducers to issues
+* label issues correctly (this requires triage rights -- just ask)
+
+Please just dive in.
+
+
+### Website development
+
+We've just revamped our website, but we're far from done. If you love web development, these [issues](https://github.com/numpy/numpy.org/issues?q=is%3Aissue+is%3Aopen+label%3Adesign) list some of our unmet needs -- and feel free to share your own ideas.
+
+
+### Graphic design
+
+We can barely begin to list the contributions a graphic designer can make here. Our docs are parched for illustration; our growing website craves images -- opportunities abound.
+
+
+### Translating website content
+
+We plan multiple translations of [numpy.org](https://numpy.org) to make NumPy accessible to users in their native language. Volunteer translators are at the heart of this effort. See [here](https://numpy.org/neps/nep-0028-website-redesign.html#translation-multilingual-i18n) for background; comment on [this GitHub issue](https://github.com/numpy/numpy.org/issues/55) to sign up.
+
+
+### Community coordination and outreach
+
+Through community contact we share our work more widely and learn where we're falling short. We're eager to get more people involved in efforts like our [Twitter](https://twitter.com/numpy_team) account, organizing NumPy [code sprints](https://scisprints.github.io/), a newsletter, and perhaps a blog.
+
+### Fundraising
+
+NumPy was all-volunteer for many years, but as its importance grew it became clear that to ensure stability and growth we'd need financial support. [This SciPy'19 talk](https://www.youtube.com/watch?v=dBTJD_FDVjU) explains how much difference that support has made. Like all the nonprofit world, we're constantly searching for grants, sponsorships, and other kinds of support. We have a number of ideas and of course we welcome more. Fundraising is a scarce skill here -- we'd appreciate your help.
+
From 5d0872e8d442dd123a1651969a506b59ddecc2a8 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:36:53 +0000
Subject: [PATCH 038/909] New translations diversity_sep2020.md (Arabic)
---
content/ar/diversity_sep2020.md | 48 +++++++++++++++++++++++++++++++++
1 file changed, 48 insertions(+)
create mode 100644 content/ar/diversity_sep2020.md
diff --git a/content/ar/diversity_sep2020.md b/content/ar/diversity_sep2020.md
new file mode 100644
index 0000000000..ef3030d5f7
--- /dev/null
+++ b/content/ar/diversity_sep2020.md
@@ -0,0 +1,48 @@
+---
+title: NumPy Diversity and Inclusion Statement
+sidebar: false
+---
+
+
+_In light of the foregoing discussion on social media after publication of the NumPy paper in Nature and the concerns raised about the state of diversity and inclusion on the NumPy team, we would like to issue the following statement:_
+
+
+It is our strong belief that we are at our best, as a team and community, when we are inclusive and equitable. Being an international team from the onset, we recognize the value of collaborating with individuals from diverse backgrounds and expertise. A culture where everyone is welcomed, supported, and valued is at the core of the NumPy project.
+
+## The Past
+
+Contributing to open source has always been a pastime in which most historically marginalized groups, especially women, faced more obstacles to participate due to a number of societal constraints and expectations. Open source has a severe diversity gap that is well documented (see, e.g., the [2017 GitHub Open Source Survey](https://opensourcesurvey.org/2017/) and [this blog post](https://medium.com/tech-diversity-files/if-you-think-women-in-tech-is-just-a-pipeline-problem-you-haven-t-been-paying-attention-cb7a2073b996)).
+
+Since its inception and until 2018, NumPy was maintained by a handful of volunteers often working nights and weekends outside of their day jobs. At any one time, the number of active core developers, the ones doing most of the heavy lifting as well as code review and integration of contributions from the community, was in the range of 4 to 8. The project didn't have a roadmap or mechanism for directing resources, being driven by individual efforts to work on what seemed needed. The authors on the NumPy paper are the individuals who made the most significant and sustained contributions to the project over a period of 15 years (2005 - 2019). The lack of diversity on this author list is a reflection of the formative years of the Python and SciPy ecosystems.
+
+2018 has marked an important milestone in the history of the NumPy project. Receiving funding from The Gordon and Betty Moore Foundation and Alfred P. Sloan Foundation allowed us to provide full-time employment for two software engineers with years of experience contributing to the Python ecosystem. Those efforts brought NumPy to a much healthier technical state.
+
+This funding also created space for NumPy maintainers to focus on project governance, community development, and outreach to underrepresented groups. [The diversity statement](https://figshare.com/articles/online_resource/Diversity_and_Inclusion_Statement_NumPy_for_Chan_Zuckerberg_Initiative_EOSS_2019_round_1/12980852) written in mid 2019 for the CZI EOSS program grant application details some of the challenges as well as the advances in our efforts to bring in more diverse talent to the NumPy team.
+
+## The Present
+
+Offering employment opportunities is an effective way to attract and retain diverse talent in OSS. Therefore, we used two-thirds of our second grant that became available in Dec 2019 to employ Melissa Weber Mendonça and Mars Lee.
+
+As a result of several initiatives aimed at community development and engagement led by Inessa Pawson and Ralf Gommers, the NumPy project has received a number of valuable contributions from women and other underrepresented groups in open source in 2020:
+
+- Melissa Weber Mendonça gained commit rights, is maintaining numpy.f2py and is leading the documentation team,
+- Shaloo Shalini created all case studies on numpy.org,
+- Mars Lee contributed web design and led our accessibility improvements work,
+- Isabela Presedo-Floyd designed our new logo,
+- Stephanie Mendoza, Xiayoi Deng, Deji Suolang, and Mame Fatou Thiam designed and fielded the first NumPy user survey,
+- Yuki Dunn, Dayane Machado, Mahfuza Humayra Mohona, Sumera Priyadarsini, Shaloo Shalini, and Kriti Singh (former Outreachy intern) helped the survey team to reach out to non-English speaking NumPy users and developers by translating the questionnaire into their native languages,
+- Sayed Adel, Raghuveer Devulapalli, and Chunlin Fang are driving the work on SIMD optimizations in the core of NumPy.
+
+While we still have much more work to do, the NumPy team is starting to look much more representative of our user base. And we can assure you that the next NumPy paper will certainly have a more diverse group of authors.
+
+## The Future
+
+We are fully committed to fostering inclusion and diversity on our team and in our community, and to do our part in building a more just and equitable future.
+
+We are open to dialogue and welcome every opportunity to connect with organizations representing and supporting women and minorities in tech and science. We are ready to listen, learn, and support.
+
+Please get in touch with us on [our mailing list](https://scipy.org/scipylib/mailing-lists.html#mailing-lists), [GitHub](https://github.com/numpy/numpy/issues), [Slack](https://numpy.org/contribute/), in private at numpy-team@googlegroups.com, or join our [bi-weekly community meeting](https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg).
+
+
+_Sayed Adel, Sebastian Berg, Raghuveer Devulapalli, Chunlin Fang, Ralf Gommers, Allan Haldane, Stephan Hoyer, Mars Lee, Melissa Weber Mendonça, Jarrod Millman, Inessa Pawson, Matti Picus, Nathaniel Smith, Julian Taylor, Pauli Virtanen, Stéfan van der Walt, Eric Wieser, on behalf of the NumPy team_
+
From e83c4e3fcd51abe438c60c6a61e20cd6335e60ff Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:36:55 +0000
Subject: [PATCH 039/909] New translations gw-discov.md (Arabic)
---
content/ar/case-studies/gw-discov.md | 69 ++++++++++++++++++++++++++++
1 file changed, 69 insertions(+)
create mode 100644 content/ar/case-studies/gw-discov.md
diff --git a/content/ar/case-studies/gw-discov.md b/content/ar/case-studies/gw-discov.md
new file mode 100644
index 0000000000..3d25090e13
--- /dev/null
+++ b/content/ar/case-studies/gw-discov.md
@@ -0,0 +1,69 @@
+---
+title: "Case Study: Discovery of Gravitational Waves"
+sidebar: false
+---
+
+{{< figure src="/images/content_images/cs/gw_sxs_image.png" class="fig-center" caption="**Gravitational Waves**" alt="binary coalesce black hole generating gravitational waves" attr="*(Image Credits: The Simulating eXtreme Spacetimes (SXS) Project at LIGO)*" attrlink="https://youtu.be/Zt8Z_uzG71o" >}}
+
+
+
The scientific Python ecosystem is critical infrastructure for the research done at LIGO.
+
+
+
+## About [Gravitational Waves](https://www.nationalgeographic.com/news/2017/10/what-are-gravitational-waves-ligo-astronomy-science/) and [LIGO](https://www.ligo.caltech.edu)
+
+Gravitational waves are ripples in the fabric of space and time, generated by cataclysmic events in the universe such as collision and merging of two black holes or coalescing binary stars or supernovae. Observing GW can not only help in studying gravity but also in understanding some of the obscure phenomena in the distant universe and its impact.
+
+The [Laser Interferometer Gravitational-Wave Observatory (LIGO)](https://www.ligo.caltech.edu) was designed to open the field of gravitational-wave astrophysics through the direct detection of gravitational waves predicted by Einstein’s General Theory of Relativity. It comprises two widely-separated interferometers within the United States — one in Hanford, Washington and the other in Livingston, Louisiana — operated in unison to detect gravitational waves. Each of them has multi-kilometer-scale gravitational wave detectors that use laser interferometry. The LIGO Scientific Collaboration (LSC), is a group of more than 1000 scientists from universities around the United States and in 14 other countries supported by more than 90 universities and research institutes; approximately 250 students actively contributing to the collaboration. The new LIGO discovery is the first observation of gravitational waves themselves, made by measuring the tiny disturbances the waves make to space and time as they pass through the earth. It has opened up new astrophysical frontiers that explore the warped side of the universe—objects and phenomena that are made from warped spacetime.
+
+
+### Key Objectives
+
+* Though its [mission](https://www.ligo.caltech.edu/page/what-is-ligo) is to detect gravitational waves from some of the most violent and energetic processes in the Universe, the data LIGO collects may have far-reaching effects on many areas of physics including gravitation, relativity, astrophysics, cosmology, particle physics, and nuclear physics.
+* Crunch observed data via numerical relativity computations that involves complex maths in order to discern signal from noise, filter out relevant signal and statistically estimate significance of observed data
+* Data visualization so that the binary / numerical results can be comprehended.
+
+
+
+### The Challenges
+
+* **Computation**
+
+ Gravitational Waves are hard to detect as they produce a very small effect and have tiny interaction with matter. Processing and analyzing all of LIGO's data requires a vast computing infrastructure.After taking care of noise, which is billions of times of the signal, there is still very complex relativity equations and huge amounts of data which present a computational challenge: [O(10^7) CPU hrs needed for binary merger analyses](https://youtu.be/7mcHknWWzNI) spread on 6 dedicated LIGO clusters
+
+* **Data Deluge**
+
+ As observational devices become more sensitive and reliable, the challenges posed by data deluge and finding a needle in a haystack rise multi-fold. LIGO generates terabytes of data every day! Making sense of this data requires an enormous effort for each and every detection. For example, the signals being collected by LIGO must be matched by supercomputers against hundreds of thousands of templates of possible gravitational-wave signatures.
+
+* **Visualization**
+
+ Once the obstacles related to understanding Einstein’s equations well enough to solve them using supercomputers are taken care of, the next big challenge was making data comprehensible to the human brain. Simulation modeling as well as signal detection requires effective visualization techniques. Visualization also plays a role in lending more credibility to numerical relativity in the eyes of pure science aficionados, who did not give enough importance to numerical relativity until imaging and simulations made it easier to comprehend results for a larger audience. Speed of complex computations and rendering, re-rendering images and simulations using latest experimental inputs and insights can be a time consuming activity that challenges researchers in this domain.
+
+{{< figure src="/images/content_images/cs/gw_strain_amplitude.png" class="fig-center" alt="gravitational waves strain amplitude" caption="**Estimated gravitational-wave strain amplitude from GW150914**" attr="(**Graph Credits:** Observation of Gravitational Waves from a Binary Black Hole Merger, ResearchGate Publication)" attrlink="https://www.researchgate.net/publication/293886905_Observation_of_Gravitational_Waves_from_a_Binary_Black_Hole_Merger" >}}
+
+## NumPy’s Role in the Detection of Gravitational Waves
+
+Gravitational waves emitted from the merger cannot be computed using any technique except brute force numerical relativity using supercomputers. The amount of data LIGO collects is as incomprehensibly large as gravitational wave signals are small.
+
+NumPy, the standard numerical analysis package for Python, was utilized by the software used for various tasks performed during the GW detection project at LIGO. NumPy helped in solving complex maths and data manipulation at high speed. Here are some examples:
+
+* [Signal Processing](https://www.uv.es/virgogroup/Denoising_ROF.html): Glitch detection, [Noise identification and Data Characterization](https://ep2016.europython.eu/media/conference/slides/pyhton-in-gravitational-waves-research-communities.pdf) (NumPy, scikit-learn, scipy, matplotlib, pandas, pyCharm)
+* Data retrieval: Deciding which data can be analyzed, figuring out whether it contains a signal - needle in a haystack
+* Statistical analysis: estimate the statistical significance of observational data, estimating the signal parameters (e.g. masses of stars, spin velocity, and distance) by comparison with a model.
+* Visualization of data
+ - Time series
+ - Spectrograms
+* Compute Correlations
+* Key [Software](https://github.com/lscsoft) developed in GW data analysis such as [GwPy](https://gwpy.github.io/docs/stable/overview.html) and [PyCBC](https://pycbc.org) uses NumPy and AstroPy under the hood for providing object based interfaces to utilities, tools, and methods for studying data from gravitational-wave detectors.
+
+{{< figure src="/images/content_images/cs/gwpy-numpy-dep-graph.png" class="fig-center" alt="gwpy-numpy depgraph" caption="**Dependency graph showing how GwPy package depends on NumPy**" >}}
+
+----
+
+{{< figure src="/images/content_images/cs/PyCBC-numpy-dep-graph.png" class="fig-center" alt="PyCBC-numpy depgraph" caption="**Dependency graph showing how PyCBC package depends on NumPy**" >}}
+
+## Summary
+
+GW detection has enabled researchers to discover entirely unexpected phenomena while providing new insight into many of the most profound astrophysical phenomena known. Number crunching and data visualization is a crucial step that helps scientists gain insights into data gathered from the scientific observations and understand the results. The computations are complex and cannot be comprehended by humans unless it is visualized using computer simulations that are fed with the real observed data and analysis. NumPy along with other Python packages such as matplotlib, pandas, and scikit-learn is [enabling researchers](https://www.gw-openscience.org/events/GW150914/) to answer complex questions and discover new horizons in our understanding of the universe.
+
+{{< figure src="/images/content_images/cs/numpy_gw_benefits.png" class="fig-center" alt="numpy benefits" caption="**Key NumPy Capabilities utilized**" >}}
From 766a8786bb30db3293e7fac4bdb1404941767d4c Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:36:56 +0000
Subject: [PATCH 040/909] New translations deeplabcut-dnn.md (Arabic)
---
content/ar/case-studies/deeplabcut-dnn.md | 90 +++++++++++++++++++++++
1 file changed, 90 insertions(+)
create mode 100644 content/ar/case-studies/deeplabcut-dnn.md
diff --git a/content/ar/case-studies/deeplabcut-dnn.md b/content/ar/case-studies/deeplabcut-dnn.md
new file mode 100644
index 0000000000..b40ed2af50
--- /dev/null
+++ b/content/ar/case-studies/deeplabcut-dnn.md
@@ -0,0 +1,90 @@
+---
+title: "Case Study: DeepLabCut 3D Pose Estimation"
+sidebar: false
+---
+
+{{< figure src="/images/content_images/cs/mice-hand.gif" class="fig-center" caption="**Analyzing mice hand-movement using DeepLapCut**" alt="micehandanim" attr="*(Source: www.deeplabcut.org )*" attrlink="http://www.mousemotorlab.org/deeplabcut">}}
+
+
+
Open Source Software is accelerating Biomedicine. DeepLabCut enables automated video analysis of animal behavior using Deep Learning.
+
+
+
+## About DeepLabCut
+
+[DeepLabCut](https://github.com/DeepLabCut/DeepLabCut) is an open source toolbox that empowers researchers at hundreds of institutions worldwide to track behaviour of laboratory animals, with very little training data, at human-level accuracy. With DeepLabCut technology, scientists can delve deeper into the scientific understanding of motor control and behavior across animal species and timescales.
+
+Several areas of research, including neuroscience, medicine, and biomechanics, use data from tracking animal movement. DeepLabCut helps in understanding what humans and other animals are doing by parsing actions that have been recorded on film. Using automation for laborious tasks of tagging and monitoring, along with deep neural network based data analysis, DeepLabCut makes scientific studies involving observing animals, such as primates, mice, fish, flies etc., much faster and more accurate.
+
+{{< figure src="/images/content_images/cs/race-horse.gif" class="fig-center" caption="**Colored dots track the positions of a racehorse’s body part**" alt="horserideranim" attr="*(Source: Mackenzie Mathis)*">}}
+
+DeepLabCut's non-invasive behavioral tracking of animals by extracting the poses of animals is crucial for scientific pursuits in domains such as biomechanics, genetics, ethology & neuroscience. Measuring animal poses non-invasively from video - without markers - in dynamically changing backgrounds is computationally challenging, both technically as well as in terms of resource needs and training data required.
+
+DeepLabCut allows researchers to estimate the pose of the subject, efficiently enabling them to quantify the behavior through a Python based software toolkit. With DeepLabCut, researchers can identify distinct frames from videos, digitally label specific body parts in a few dozen frames with a tailored GUI, and then the deep learning based pose estimation architectures in DeepLabCut learn how to pick out those same features in the rest of the video and in other similar videos of animals. It works across species of animals, from common laboratory animals such as flies and mice to more unusual animals like [cheetahs][cheetah-movement].
+
+DeepLabCut uses a principle called [transfer learning](https://arxiv.org/pdf/1909.11229), which greatly reduces the amount of training data required and speeds up the convergence of the training period. Depending on the needs, users can pick different network architectures that provide faster inference (e.g. MobileNetV2), which can also be combined with real-time experimental feedback. DeepLabCut originally used the feature detectors from a top-performing human pose estimation architecture, called [DeeperCut](https://arxiv.org/abs/1605.03170), which inspired the name. The package now has been significantly changed to include additional architectures, augmentation methods, and a full front-end user experience. Furthermore, to support large-scale biological experiments DeepLabCut provides active learning capabilities so that users can increase the training set over time to cover edge cases and make their pose estimation algorithm robust within the specific context.
+
+Recently, the [DeepLabCut model zoo](http://www.mousemotorlab.org/dlc-modelzoo) was introduced, which provides pre-trained models for various species and experimental conditions from facial analysis in primates to dog posture. This can be run for instance in the cloud without any labeling of new data, or neural network training, and no programming experience is necessary.
+
+### Key Goals and Results
+
+* **Automation of animal pose analysis for scientific studies:**
+
+ The primary objective of DeepLabCut technology is to measure and track posture of animals in a diverse settings. This data can be used, for example, in neuroscience studies to understand how the brain controls movement, or to elucidate how animals socially interact. Researchers have observed a [tenfold performance boost](https://www.biorxiv.org/content/10.1101/457242v1) with DeepLabCut. Poses can be inferred offline at up to 1200 frames per second (FPS).
+
+* **Creation of an easy-to-use Python toolkit for pose estimation:**
+
+ DeepLabCut wanted to share their animal pose-estimation technology in the form of an easy to use tool that can be adopted by researchers easily. So they have created a complete, easy-to-use Python toolbox with project management features as well. These enable not only automation of pose-estimation but also managing the project end-to-end by helping the DeepLabCut Toolkit user right from the dataset collection stage to creating shareable and reusable analysis pipelines.
+
+ Their [toolkit][DLCToolkit] is now available as open source.
+
+ A typical DeepLabCut Workflow includes:
+
+ - creation and refining of training sets via active learning
+ - creation of tailored neural networks for specific animals and scenarios
+ - code for large-scale inference on videos
+ - draw inferences using integrated visualization tools
+
+{{< figure src="/images/content_images/cs/deeplabcut-toolkit-steps.png" class="csfigcaption" caption="**Pose estimation steps with DeepLabCut**" alt="dlcsteps" align="middle" attr="(Source: DeepLabCut)" attrlink="https://twitter.com/DeepLabCut/status/1198046918284210176/photo/1" >}}
+
+### The Challenges
+
+* **Speed**
+
+ Fast processing of animal behavior videos in order to measure their behavior and at the same time make scientific experiments more efficient, accurate. Extracting detailed animal poses for laboratory experiments, without markers, in dynamically changing backgrounds, can be challenging, both technically as well as in terms of resource needs and training data required. Coming up with a tool that is easy to use without the need for skills such as computer vision expertise that enables scientists to do research in more real-world contexts, is a non-trivial problem to solve.
+
+* **Combinatorics**
+
+ Combinatorics involves assembly and integration of movement of multiple limbs into individual animal behavior. Assembling keypoints and their connections into individual animal movements and linking them across time is a complex process that requires heavy-duty numerical analysis, especially in case of multi-animal movement tracking in experiment videos.
+
+* **Data Processing**
+
+ Last but not the least, array manipulation - processing large stacks of arrays corresponding to various images, target tensors and keypoints is fairly challenging.
+
+{{< figure src="/images/content_images/cs/pose-estimation.png" class="csfigcaption" caption="**Pose estimation variety and complexity**" alt="challengesfig" align="middle" attr="(Source: Mackenzie Mathis)" attrlink="https://www.biorxiv.org/content/10.1101/476531v1.full.pdf" >}}
+
+## NumPy's Role in meeting Pose Estimation Challenges
+
+NumPy addresses DeepLabCut technology's core need of numerical computations at high speed for behavioural analytics. Besides NumPy, DeepLabCut employs various Python software that utilize NumPy at their core, such as [SciPy](https://www.scipy.org), [Pandas](https://pandas.pydata.org), [matplotlib](https://matplotlib.org), [Tensorpack](https://github.com/tensorpack/tensorpack), [imgaug](https://github.com/aleju/imgaug), [scikit-learn](https://scikit-learn.org/stable/), [scikit-image](https://scikit-image.org) and [Tensorflow](https://www.tensorflow.org).
+
+The following features of NumPy played a key role in addressing the image processing, combinatorics requirements and need for fast computation in DeepLabCut pose estimation algorithms:
+
+* Vectorization
+* Masked Array Operations
+* Linear Algebra
+* Random Sampling
+* Reshaping of large arrays
+
+DeepLabCut utilizes NumPy’s array capabilities throughout the workflow offered by the toolkit. In particular, NumPy is used for sampling distinct frames for human annotation labeling, and for writing, editing and processing annotation data. Within TensorFlow the neural network is trained by DeepLabCut technology over thousands of iterations to predict the ground truth annotations from frames. For this purpose, target densities (scoremaps) are created to cast pose estimation as a image-to-image translation problem. To make the neural networks robust, data augmentation is employed, which requires the calculation of target scoremaps subject to various geometric and image processing steps. To make training fast, NumPy’s vectorization capabilities are leveraged. For inference, the most likely predictions from target scoremaps need to extracted and one needs to efficiently “link predictions to assemble individual animals”.
+
+{{< figure src="/images/content_images/cs/deeplabcut-workflow.png" class="fig-center" caption="**DeepLabCut Workflow**" alt="workflow" attr="*(Source: Mackenzie Mathis)*" attrlink="https://www.researchgate.net/figure/DeepLabCut-work-flow-The-diagram-delineates-the-work-flow-as-well-as-the-directory-and_fig1_329185962">}}
+
+## Summary
+
+Observing and efficiently describing behavior is a core tenant of modern ethology, neuroscience, medicine, and technology. [DeepLabCut](http://orga.cvss.cc/wp-content/uploads/2019/05/NathMathis2019.pdf) allows researchers to estimate the pose of the subject, efficiently enabling them to quantify the behavior. With only a small set of training images, the DeepLabCut Python toolbox allows training a neural network to within human level labeling accuracy, thus expanding its application to not only behavior analysis in the laboratory, but to potentially also in sports, gait analysis, medicine and rehabilitation studies. Complex combinatorics, data processing challenges faced by DeepLabCut algorithms are addressed through the use of NumPy's array manipulation capabilities.
+
+{{< figure src="/images/content_images/cs/numpy_dlc_benefits.png" class="fig-center" alt="numpy benefits" caption="**Key NumPy Capabilities utilized**" >}}
+
+[cheetah-movement]: https://www.technologynetworks.com/neuroscience/articles/interview-a-deeper-cut-into-behavior-with-mackenzie-mathis-327618
+
+[DLCToolkit]: https://github.com/DeepLabCut/DeepLabCut
From d0f051f734d3e83aa9853e8515c4603d862b6c24 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:36:57 +0000
Subject: [PATCH 041/909] New translations cricket-analytics.md (Arabic)
---
content/ar/case-studies/cricket-analytics.md | 64 ++++++++++++++++++++
1 file changed, 64 insertions(+)
create mode 100644 content/ar/case-studies/cricket-analytics.md
diff --git a/content/ar/case-studies/cricket-analytics.md b/content/ar/case-studies/cricket-analytics.md
new file mode 100644
index 0000000000..987b38fb68
--- /dev/null
+++ b/content/ar/case-studies/cricket-analytics.md
@@ -0,0 +1,64 @@
+---
+title: "Case Study: Cricket Analytics, the game changer!"
+sidebar: false
+---
+
+{{< figure src="/images/content_images/cs/ipl-stadium.png" caption="**IPLT20, the biggest Cricket Festival in India**" alt="Indian Premier League Cricket cup and stadium" attr="*(Image credits: IPLT20 (cup and logo) & Akash Yadav (stadium))*" attrlink="https://unsplash.com/@aksh1802" >}}
+
+
+
You don't play for the crowd, you play for the country.
+
+
+
+## About Cricket
+
+It would be an understatement to state that Indians love cricket. The game is played in just about every nook and cranny of India, rural or urban, popular with the young and the old alike, connecting billions in India unlike any other sport. Cricket enjoys lots of media attention. There is a significant amount of [money](https://www.statista.com/topics/4543/indian-premier-league-ipl/) and fame at stake. Over the last several years, technology has literally been a game changer. Audiences are spoilt for choice with streaming media, tournaments, affordable access to mobile based live cricket watching, and more.
+
+The Indian Premier League (IPL) is a professional Twenty20 cricket league, founded in 2008. It is one of the most attended cricketing events in the world, valued at [$6.7 billion](https://en.wikipedia.org/wiki/Indian_Premier_League) in 2019.
+
+Cricket is a game of numbers - the runs scored by a batsman, the wickets taken by a bowler, the matches won by a cricket team, the number of times a batsman responds in a certain way to a kind of bowling attack, etc. The capability to dig into cricketing numbers for both improving performance and studying the business opportunities, overall market, and economics of cricket via powerful analytics tools, powered by numerical computing software such as NumPy, is a big deal. Cricket analytics provides interesting insights into the game and predictive intelligence regarding game outcomes.
+
+Today, there are rich and almost infinite troves of cricket game records and statistics available, e.g., [ESPN cricinfo](https://stats.espncricinfo.com/ci/engine/stats/index.html) and [cricsheet](https://cricsheet.org). These and several such cricket databases have been used for [cricket analysis](https://www.researchgate.net/publication/336886516_Data_visualization_and_toss_related_analysis_of_IPL_teams_and_batsmen_performances) using the latest machine learning and predictive modelling algorithms. Media and entertainment platforms along with professional sports bodies associated with the game use technology and analytics for determining key metrics for improving match winning chances:
+
+* batting performance moving average,
+* score forecasting,
+* gaining insights into fitness and performance of a player against different opposition,
+* player contribution to wins and losses for making strategic decisions on team composition
+
+{{< figure src="/images/content_images/cs/cricket-pitch.png" class="csfigcaption" caption="**Cricket Pitch, the focal point in the field**" alt="A cricket pitch with bowler and batsmen" align="middle" attr="*(Image credit: Debarghya Das)*" attrlink="http://debarghyadas.com/files/IPLpaper.pdf" >}}
+
+### Key Data Analytics Objectives
+
+* Sports data analytics are used not only in cricket but many [other sports](https://adtmag.com/blogs/dev-watch/2017/07/sports-analytics.aspx) for improving the overall team performance and maximizing winning chances.
+* Real-time data analytics can help in gaining insights even during the game for changing tactics by the team and by associated businesses for economic benefits and growth.
+* Besides historical analysis, predictive models are harnessed to determine the possible match outcomes that require significant number crunching and data science know-how, visualization tools and capability to include newer observations in the analysis.
+
+{{< figure src="/images/content_images/cs/player-pose-estimator.png" class="fig-center" alt="pose estimator" caption="**Cricket Pose Estimator**" attr="*(Image credit: connect.vin)*" attrlink="https://connect.vin/2019/05/ai-for-cricket-batsman-pose-analysis/" >}}
+
+### The Challenges
+
+* **Data Cleaning and preprocessing**
+
+ IPL has expanded cricket beyond the classic test match format to a much larger scale. The number of matches played every season across various formats has increased and so has the data, the algorithms, newer sports data analysis technologies and simulation models. Cricket data analysis requires field mapping, player tracking, ball tracking, player shot analysis, and several other aspects involved in how the ball is delivered, its angle, spin, velocity, and trajectory. All these factors together have increased the complexity of data cleaning and preprocessing.
+
+* **Dynamic Modeling**
+
+ In cricket, just like any other sport, there can be a large number of variables related to tracking various numbers of players on the field, their attributes, the ball, and several possibilities of potential actions. The complexity of data analytics and modeling is directly proportional to the kind of predictive questions that are put forth during analysis and are highly dependent on data representation and the model. Things get even more challenging in terms of computation, data comparisons when dynamic cricket play predictions are sought such as what would have happened if the batsman had hit the ball at a different angle or velocity.
+
+* **Predictive Analytics Complexity**
+
+ Much of the decision making in cricket is based on questions such as "how often does a batsman play a certain kind of shot if the ball delivery is of a particular type", or "how does a bowler change his line and length if the batsman responds to his delivery in a certain way". This kind of predictive analytics query requires highly granular dataset availability and the capability to synthesize data and create generative models that are highly accurate.
+
+## NumPy’s Role in Cricket Analytics
+
+Sports Analytics is a thriving field. Many researchers and companies [use NumPy](https://adtmag.com/blogs/dev-watch/2017/07/sports-analytics.aspx) and other PyData packages like Scikit-learn, SciPy, Matplotlib, and Jupyter, besides using the latest machine learning and AI techniques. NumPy has been used for various kinds of cricket related sporting analytics such as:
+
+* **Statistical Analysis:** NumPy's numerical capabilities help estimate the statistical significance of observational data or match events in the context of various player and game tactics, estimating the game outcome by comparison with a generative or static model. [Causal analysis](https://amplitude.com/blog/2017/01/19/causation-correlation) and [big data approaches](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4996805/) are used for tactical analysis.
+
+* **Data Visualization:** Data graphing and [visualization](https://towardsdatascience.com/advanced-sports-visualization-with-pandas-matplotlib-and-seaborn-9c16df80a81b) provides useful insights into relationship between various datasets.
+
+## Summary
+
+Sports Analytics is a game changer when it comes to how professional games are played, especially how strategic decision making happens, which until recently was primarily done based on “gut feeling" or adherence to past traditions. NumPy forms a solid foundation for a large set of Python packages which provide higher level functions related to data analytics, machine learning, and AI algorithms. These packages are widely deployed to gain real-time insights that help in decision making for game-changing outcomes, both on field as well as to draw inferences and drive business around the game of cricket. Finding out the hidden parameters, patterns, and attributes that lead to the outcome of a cricket match helps the stakeholders to take notice of game insights that are otherwise hidden in numbers and statistics.
+
+{{< figure src="/images/content_images/cs/numpy_ca_benefits.png" class="fig-center" alt="Diagram showing benefits of using NumPy for cricket analytics" caption="**Key NumPy Capabilities utilized**" >}}
From 64acbc42d52907c5b952a79f0582d6f8ece531c4 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:36:59 +0000
Subject: [PATCH 042/909] New translations blackhole-image.md (Arabic)
---
content/ar/case-studies/blackhole-image.md | 70 ++++++++++++++++++++++
1 file changed, 70 insertions(+)
create mode 100644 content/ar/case-studies/blackhole-image.md
diff --git a/content/ar/case-studies/blackhole-image.md b/content/ar/case-studies/blackhole-image.md
new file mode 100644
index 0000000000..f2460d3d5b
--- /dev/null
+++ b/content/ar/case-studies/blackhole-image.md
@@ -0,0 +1,70 @@
+---
+title: "Case Study: First Image of a Black Hole"
+sidebar: false
+---
+
+{{< figure src="/images/content_images/cs/blackhole.jpg" caption="**Black Hole M87**" alt="black hole image" attr="*(Image Credits: Event Horizon Telescope Collaboration)*" attrlink="https://www.jpl.nasa.gov/images/universe/20190410/blackhole20190410.jpg" >}}
+
+
+
Imaging the M87 Black Hole is like trying to see something that is by definition impossible to see.
+
+
+
+## A telescope the size of the earth
+
+The [Event Horizon telescope (EHT)](https://eventhorizontelescope.org) is an array of eight ground-based radio telescopes forming a computational telescope the size of the earth, studing the universe with unprecedented sensitivity and resolution. The huge virtual telescope, which uses a technique called very-long-baseline interferometry (VLBI), has an angular resolution of [20 micro-arcseconds][resolution] — enough to read a newspaper in New York from a sidewalk café in Paris!
+
+### Key Goals and Results
+
+* **A New View of the Universe:** The groundwork for the EHT's groundbreaking image had been laid 100 years earlier when [Sir Arthur Eddington][eddington] yielded the first observational support of Einstein's theory of general relativity.
+
+* **The Black Hole:** EHT was trained on a supermassive black hole approximately 55 million light-years from Earth, lying at the center of the galaxy Messier 87 (M87) in the Virgo galaxy cluster. Its mass is 6.5 billion times the Sun's. It had been studied for [over 100 years](https://www.jpl.nasa.gov/news/news.php?feature=7385), but never before had a black hole been visually observed.
+
+* **Comparing Observations to Theory:** From Einstein’s general theory of relativity, scientists expected to find a shadow-like region caused by gravitational bending and capture of light. Scientists could use it to measure the black hole's enormous mass.
+
+### The Challenges
+
+* **Computational scale**
+
+ EHT poses massive data-processing challenges, including rapid atmospheric phase fluctuations, large recording bandwidth, and telescopes that are widely dissimilar and geographically dispersed.
+
+* **Too much information**
+
+ Each day EHT generates over 350 terabytes of observations, stored on helium-filled hard drives. Reducing the volume and complexity of this much data is enormously difficult.
+
+* **Into the unknown**
+
+ When the goal is to see something never before seen, how can scientists be confident the image is correct?
+
+{{< figure src="/images/content_images/cs/dataprocessbh.png" class="csfigcaption" caption="**EHT Data Processing Pipeline**" alt="data pipeline" align="middle" attr="(Diagram Credits: The Astrophysical Journal, Event Horizon Telescope Collaboration)" attrlink="https://iopscience.iop.org/article/10.3847/2041-8213/ab0c57" >}}
+
+## NumPy’s Role
+
+What if there's a problem with the data? Or perhaps an algorithm relies too heavily on a particular assumption. Will the image change drastically if a single parameter is changed?
+
+The EHT collaboration met these challenges by having independent teams evaluate the data, using both established and cutting-edge image reconstruction techniques. When results proved consistent, they were combined to yield the first-of-a-kind image of the black hole.
+
+Their work illustrates the role the scientific Python ecosystem plays in advancing science through collaborative data analysis.
+
+{{< figure src="/images/content_images/cs/bh_numpy_role.png" class="fig-center" alt="role of numpy" caption="**The role of NumPy in Black Hole imaging**" >}}
+
+For example, the [`eht-imaging`][ehtim] Python package provides tools for simulating and performing image reconstruction on VLBI data. NumPy is at the core of array data processing used in this package, as illustrated by the partial software dependency chart below.
+
+{{< figure src="/images/content_images/cs/ehtim_numpy.png" class="fig-center" alt="ehtim dependency map highlighting numpy" caption="**Software dependency chart of ehtim package highlighting NumPy**" >}}
+
+Besides NumPy, many other packages, such as [SciPy](https://www.scipy.org) and [Pandas](https://pandas.io), are part of the data processing pipeline for imaging the black hole. The standard astronomical file formats and time/coordinate transformations were handled by [Astropy][astropy], while [Matplotlib][mpl] was used in visualizing data throughout the analysis pipeline, including the generation of the final image of the black hole.
+
+## Summary
+
+The efficient and adaptable n-dimensional array that is NumPy's central feature enabled researchers to manipulate large numerical datasets, providing a foundation for the first-ever image of a black hole. A landmark moment in science, it gives stunning visual evidence of Einstein’s theory. The achievement encompasses not only technological breakthroughs but also international collaboration among over 200 scientists and some of the world's best radio observatories. Innovative algorithms and data processing techniques, improving upon existing astronomical models, helped unfold a mystery of the universe.
+
+{{< figure src="/images/content_images/cs/numpy_bh_benefits.png" class="fig-center" alt="numpy benefits" caption="**Key NumPy Capabilities utilized**" >}}
+
+[resolution]: https://eventhorizontelescope.org/press-release-april-10-2019-astronomers-capture-first-image-black-hole
+
+[eddington]: https://en.wikipedia.org/wiki/Eddington_experiment
+
+[ehtim]: https://github.com/achael/eht-imaging
+
+[astropy]: https://www.astropy.org/
+[mpl]: https://matplotlib.org/
From 8f7467485f41d258d864bab2b0bf5054c39249da Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:37:00 +0000
Subject: [PATCH 043/909] New translations news.md (Arabic)
---
content/ar/news.md | 83 ++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 83 insertions(+)
create mode 100644 content/ar/news.md
diff --git a/content/ar/news.md b/content/ar/news.md
new file mode 100644
index 0000000000..5dcb849596
--- /dev/null
+++ b/content/ar/news.md
@@ -0,0 +1,83 @@
+---
+title: News
+sidebar: false
+---
+
+### Diversity in the NumPy project
+
+_Sep 20, 2020_ -- We wrote a [statement on the state of, and discussion on social media around, diversity and inclusion in the NumPy project](/diversity_sep2020).
+
+
+### First official NumPy paper published in Nature!
+
+_Sep 16, 2020_ -- We are pleased to announce the publication of [the first official paper on NumPy](https://www.nature.com/articles/s41586-020-2649-2) as a review article in Nature. This comes 14 years after the release of NumPy 1.0. The paper covers applications and fundamental concepts of array programming, the rich scientific Python ecosystem built on top of NumPy, and the recently added array protocols to facilitate interoperability with external array and tensor libraries like CuPy, Dask, and JAX.
+
+
+### Python 3.9 is coming, when will NumPy release binary wheels?
+
+_Sept 14, 2020_ -- Python 3.9 will be released in a few weeks. If you are an early adopter of Python versions, you may be dissapointed to find that NumPy (and other binary packages like SciPy) will not have binary wheels ready on the day of the release. It is a major effort to adapt the build infrastructure to a new Python version and it typically takes a few weeks for the packages to appear on PyPI and conda-forge. In preparation for this event, please make sure to
+- update your `pip` to version 20.1 at least to support `manylinux2010` and `manylinux2014`
+- use [`--only-binary=numpy`](https://pip.pypa.io/en/stable/reference/pip_install/#cmdoption-only-binary) or `--only-binary=:all:` to prevent `pip` from trying to build from source.
+
+
+### Numpy 1.19.2 release
+
+_Sept 10, 2020_ -- [NumPy 1.19.2](https://numpy.org/devdocs/release/1.19.2-notes.html) is now available. This latest release in the 1.19 series fixes several bugs, prepares for the [upcoming Cython 3.x release](http://docs.cython.org/en/latest/src/changes.html) and pins setuptools to keep distutils working while upstream modifications are ongoing. The aarch64 wheels are built with the latest manylinux2014 release that fixes the problem of differing page sizes used by different linux distros.
+
+### The inaugural NumPy survey is live!
+
+_Jul 2, 2020_ -- This survey is meant to guide and set priorities for decision-making about the development of NumPy as software and as a community. The survey is available in 8 additional languages besides English: Bangla, Hindi, Japanese, Mandarin, Portuguese, Russian, Spanish and French.
+
+Please help us make NumPy better and take the survey [here](https://umdsurvey.umd.edu/jfe/form/SV_8bJrXjbhXf7saAl).
+
+
+### NumPy has a new logo!
+
+_Jun 24, 2020_ -- NumPy now has a new logo:
+
+
+
+The logo is a modern take on the old one, with a cleaner design. Thanks to Isabela Presedo-Floyd for designing the new logo, as well as to Travis Vaught for the old logo that served us well for 15+ years.
+
+
+### NumPy 1.19.0 release
+
+_Jun 20, 2020_ -- NumPy 1.19.0 is now available. This is the first release without Python 2 support, hence it was a "clean-up release". The minimum supported Python version is now Python 3.6. An important new feature is that the random number generation infrastructure that was introduced in NumPy 1.17.0 is now accessible from Cython.
+
+
+### Season of Docs acceptance
+
+_May 11, 2020_ -- NumPy has been accepted as one of the mentor organizations for the Google Season of Docs program. We are excited about the opportunity to work with a technical writer to improve NumPy's documentation once again! For more details, please see [the official Season of Docs site](https://developers.google.com/season-of-docs/) and our [ideas page](https://github.com/numpy/numpy/wiki/Google-Season-of-Docs-2020-Project-Ideas).
+
+
+### NumPy 1.18.0 release
+
+_Dec 22, 2019_ -- NumPy 1.18.0 is now available. After the major changes in 1.17.0, this is a consolidation release. It is the last minor release that will support Python 3.5. Highlights of the release includes the addition of basic infrastructure for linking with 64-bit BLAS and LAPACK libraries, and a new C-API for `numpy.random`.
+
+Please see the [release notes](https://github.com/numpy/numpy/releases/tag/v1.18.0) for more details.
+
+
+### NumPy receives a grant from the Chan Zuckerberg Initiative
+
+_Nov 15, 2019_ -- We are pleased to announce that NumPy and OpenBLAS, one of NumPy's key dependencies, have received a joint grant for $195,000 from the Chan Zuckerberg Initiative through their [Essential Open Source Software for Science program](https://chanzuckerberg.com/eoss/) that supports software maintenance, growth, development, and community engagement for open source tools critical to science.
+
+This grant will be used to ramp up the efforts in improving NumPy documentation, website redesign, and community development to better serve our large and rapidly growing user base, and ensure the long-term sustainability of the project. While the OpenBLAS team will focus on addressing sets of key technical issues, in particular thread-safety, AVX-512, and thread-local storage (TLS) issues, as well as algorithmic improvements in ReLAPACK (Recursive LAPACK) on which OpenBLAS depends.
+
+More details on our proposed initiatives and deliverables can be found in the [full grant proposal](https://figshare.com/articles/Proposal_NumPy_OpenBLAS_for_Chan_Zuckerberg_Initiative_EOSS_2019_round_1/10302167). The work is scheduled to start on Dec 1st, 2019 and continue for the next 12 months.
+
+
+## Releases
+
+Here is a list of NumPy releases, with links to release notes. All bugfix releases (only the `z` changes in the `x.y.z` version number) have no new features; minor releases (the `y` increases) do.
+
+- NumPy 1.18.4 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.18.4)) -- _3 May 2020_.
+- NumPy 1.18.3 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.18.3)) -- _19 Apr 2020_.
+- NumPy 1.18.2 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.18.2)) -- _17 Mar 2020_.
+- NumPy 1.18.1 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.18.1)) -- _6 Jan 2020_.
+- NumPy 1.17.5 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.17.5)) -- _1 Jan 2020_.
+- NumPy 1.18.0 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.18.0)) -- _22 Dec 2019_.
+- NumPy 1.17.4 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.17.4)) -- _11 Nov 2019_.
+- NumPy 1.17.0 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.17.0)) -- _26 Jul 2019_.
+- NumPy 1.16.0 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.16.0)) -- _14 Jan 2019_.
+- NumPy 1.15.0 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.15.0)) -- _23 Jul 2018_.
+- NumPy 1.14.0 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.14.0)) -- _7 Jan 2018_.
From 9740d697b34422efc5184f64adf6be93bf3f01c7 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:37:01 +0000
Subject: [PATCH 044/909] New translations history.md (Arabic)
---
content/ar/history.md | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
create mode 100644 content/ar/history.md
diff --git a/content/ar/history.md b/content/ar/history.md
new file mode 100644
index 0000000000..fc79a621af
--- /dev/null
+++ b/content/ar/history.md
@@ -0,0 +1,21 @@
+---
+title: History of NumPy
+sidebar: false
+---
+
+NumPy is a foundational Python library that provides array data structures and related fast numerical routines. When started, the library had little funding, and was written mainly by graduate students—many of them without computer science education, and often without a blessing of their advisors. To even imagine that a small group of “rogue” student programmers could upend the already well-established ecosystem of research software—backed by millions in funding and many hundreds of highly qualified engineers — was preposterous. Yet, the philosophical motivations behind a fully open tool stack, in combination with the excited, friendly community with a singular focus, have proven auspicious in the long run. Nowadays, NumPy is relied upon by scientists, engineers, and many other professionals around the world. For example, the published scripts used in the analysis of gravitational waves import NumPy, and the M87 black hole imaging project directly cites NumPy.
+
+For the in-depth account on milestones in the development of NumPy and related libraries please see [arxiv.org](arxiv.org/abs/1907.10121).
+
+If you’d like to obtain a copy of the original Numeric and Numarray libraries, follow the links below:
+
+[Download Page for *Numeric*](https://sourceforge.net/projects/numpy/files/Old%20Numeric/)*
+
+[Download Page for *Numarray*](https://sourceforge.net/projects/numpy/files/Old%20Numarray/)*
+
+*Please note that these older array packages are no longer maintained, and users are strongly advised to use NumPy for any array-related purposes or refactor any pre-existing code to utilize the NumPy library.
+
+### Historic Documentation
+
+[Download *`Numeric'* Manual](static/numeric-manual.pdf)
+
From b9f3677684d8eb182aae7667886eeb47bea6f098 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:37:03 +0000
Subject: [PATCH 045/909] New translations gethelp.md (Arabic)
---
content/ar/gethelp.md | 34 ++++++++++++++++++++++++++++++++++
1 file changed, 34 insertions(+)
create mode 100644 content/ar/gethelp.md
diff --git a/content/ar/gethelp.md b/content/ar/gethelp.md
new file mode 100644
index 0000000000..a427b5b1f5
--- /dev/null
+++ b/content/ar/gethelp.md
@@ -0,0 +1,34 @@
+---
+title: Get Help
+sidebar: false
+---
+
+**User questions:** The best way to get help is to post your question to a site like [StackOverflow](http://stackoverflow.com/questions/tagged/numpy), with thousands of users available to answer. Smaller alternatives include [IRC](https://webchat.freenode.net/?channels=%23numpy), [Gitter](https://gitter.im/numpy/numpy), and [Reddit](https://www.reddit.com/r/Numpy/). We wish we could keep an eye on these sites, or answer questions directly, but the volume is just a little overwhelming!
+
+**Development issues:** For NumPy development-related matters (e.g. bug reports), please see [Community](/community).
+
+
+
+### [StackOverflow](http://stackoverflow.com/questions/tagged/numpy)
+
+A forum for asking usage questions, e.g. "How do I do X in NumPy?”. Please [use the `#numpy` tag](https://stackoverflow.com/help/tagging)
+
+***
+
+### [Reddit](https://www.reddit.com/r/Numpy/)
+
+Another forum for usage questions.
+
+***
+
+### [Gitter](https://gitter.im/numpy/numpy)
+
+A real-time chat room where users and community members help each other.
+
+***
+
+### [IRC](https://webchat.freenode.net/?channels=%23numpy)
+
+Another real-time chat room where users and community members help each other.
+
+***
From f87cec10f5a56cd4c6316b508d8b8d1e292d2da5 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:37:04 +0000
Subject: [PATCH 046/909] New translations report-handling-manual.md (Arabic)
---
content/ar/report-handling-manual.md | 95 ++++++++++++++++++++++++++++
1 file changed, 95 insertions(+)
create mode 100644 content/ar/report-handling-manual.md
diff --git a/content/ar/report-handling-manual.md b/content/ar/report-handling-manual.md
new file mode 100644
index 0000000000..5586668cba
--- /dev/null
+++ b/content/ar/report-handling-manual.md
@@ -0,0 +1,95 @@
+---
+title: NumPy Code of Conduct - How to follow up on a report
+sidebar: false
+---
+
+This is the manual followed by NumPy’s Code of Conduct Committee. It’s used when we respond to an issue to make sure we’re consistent and fair.
+
+Enforcing the [Code of Conduct](/code-of-conduct) impacts our community today and for the future. It’s an action that we do not take lightly. When reviewing enforcement measures, the Code of Conduct Committee will keep the following values and guidelines in mind:
+
+* Act in a personal manner rather than impersonal. The Committee can engage the parties to understand the situation while respecting the privacy and any necessary confidentiality of reporters. However, sometimes it is necessary to communicate with one or more individuals directly: the Committee’s goal is to improve the health of our community rather than only produce a formal decision.
+* Emphasize empathy for individuals rather than judging behavior, avoiding binary labels of “good” and “bad/evil”. Overt, clear-cut aggression and harassment exist, and we will address them firmly. But many scenarios that can prove challenging to resolve are those where normal disagreements devolve into unhelpful or harmful behavior from multiple parties. Understanding the full context and finding a path that re-engages all is hard, but ultimately the most productive for our community.
+* We understand that email is a difficult medium and can be isolating. Receiving criticism over email, without personal contact, can be particularly painful. This makes it especially important to keep an atmosphere of open-minded respect for the views of others. It also means that we must be transparent in our actions, and that we will do everything in our power to make sure that all our members are treated fairly and with sympathy.
+* Discrimination can be subtle and it can be unconscious. It can show itself as unfairness and hostility in otherwise ordinary interactions. We know that this does occur, and we will take care to look out for it. We would very much like to hear from you if you feel you have been treated unfairly, and we will use these procedures to make sure that your complaint is heard and addressed.
+* Help increase engagement in good discussion practice: try to identify where discussion may have broken down, and provide actionable information, pointers, and resources that can lead to positive change on these points.
+* Be mindful of the needs of new members: provide them with explicit support and consideration, with the aim of increasing participation from underrepresented groups in particular.
+* Individuals come from different cultural backgrounds and native languages. Try to identify any honest misunderstandings caused by a non-native speaker and help them understand the issue and what they can change to avoid causing offence. Complex discussion in a foreign language can be very intimidating, and we want to grow our diversity also across nationalities and cultures.
+
+
+## Mediation
+
+Voluntary informal mediation is a tool at our disposal. In contexts such as when two or more parties have all escalated to the point of inappropriate behavior (something sadly common in human conflict), it may be useful to facilitate a mediation process. This is only an example: the Committee can consider mediation in any case, mindful that the process is meant to be strictly voluntary and no party can be pressured to participate. If the Committee suggests mediation, it should:
+
+* Find a candidate who can serve as a mediator.
+* Obtain the agreement of the reporter(s). The reporter(s) have complete freedom to decline the mediation idea or to propose an alternate mediator.
+* Obtain the agreement of the reported person(s).
+* Settle on the mediator: while parties can propose a different mediator than the suggested candidate, only if a common agreement is reached on all terms can the process move forward.
+* Establish a timeline for mediation to complete, ideally within two weeks.
+
+The mediator will engage with all the parties and seek a resolution that is satisfactory to all. Upon completion, the mediator will provide a report (vetted by all parties to the process) to the Committee, with recommendations on further steps. The Committee will then evaluate these results (whether a satisfactory resolution was achieved or not) and decide on any additional action deemed necessary.
+
+
+## How the Committee will respond to reports
+
+When the Committee (or a Committee member) receives a report, they will first determine whether the report is about a clear and severe breach (as defined below). If so, immediate action needs to be taken in addition to the regular report handling process.
+
+
+## Clear and severe breach actions
+
+We know that it is painfully common for internet communication to start at or devolve into obvious and flagrant abuse. We will deal quickly with clear and severe breaches like personal threats, violent, sexist or racist language.
+
+When a member of the Code of Conduct Committee becomes aware of a clear and severe breach, they will do the following:
+
+* Immediately disconnect the originator from all NumPy communication channels.
+* Reply to the reporter that their report has been received and that the originator has been disconnected.
+* In every case, the moderator should make a reasonable effort to contact the originator, and tell them specifically how their language or actions qualify as a “clear and severe breach”. The moderator should also say that, if the originator believes this is unfair or they want to be reconnected to NumPy, they have the right to ask for a review, as below, by the Code of Conduct Committee. The moderator should copy this explanation to the Code of Conduct Committee.
+* The Code of Conduct Committee will formally review and sign off on all cases where this mechanism has been applied to make sure it is not being used to control ordinary heated disagreement.
+
+
+## Report handling
+
+When a report is sent to the Committee they will immediately reply to the reporter to confirm receipt. This reply must be sent within 72 hours, and the group should strive to respond much quicker than that.
+
+If a report doesn’t contain enough information, the Committee will obtain all relevant data before acting. The Committee is empowered to act on the Steering Council’s behalf in contacting any individuals involved to get a more complete account of events.
+
+The Committee will then review the incident and determine, to the best of their ability:
+
+* What happened.
+* Whether this event constitutes a Code of Conduct violation.
+* Who are the responsible party(ies).
+* Whether this is an ongoing situation, and there is a threat to anyone’s physical safety.
+
+This information will be collected in writing, and whenever possible the group’s deliberations will be recorded and retained (i.e. chat transcripts, email discussions, recorded conference calls, summaries of voice conversations, etc).
+
+It is important to retain an archive of all activities of this Committee to ensure consistency in behavior and provide institutional memory for the project. To assist in this, the default channel of discussion for this Committee will be a private mailing list accessible to current and future members of the Committee as well as members of the Steering Council upon justified request. If the Committee finds the need to use off-list communications (e.g. phone calls for early/rapid response), it should in all cases summarize these back to the list so there’s a good record of the process.
+
+The Code of Conduct Committee should aim to have a resolution agreed upon within two weeks. In the event that a resolution can’t be determined in that time, the Committee will respond to the reporter(s) with an update and projected timeline for resolution.
+
+
+## Resolutions
+
+The Committee must agree on a resolution by consensus. If the group cannot reach consensus and deadlocks for over a week, the group will turn the matter over to the Steering Council for resolution.
+
+Possible responses may include:
+
+* Taking no further action:
+ - if we determine no violations have occurred;
+ - if the matter has been resolved publicly while the Committee was considering responses.
+* Coordinating voluntary mediation: if all involved parties agree, the Committee may facilitate a mediation process as detailed above.
+* Remind publicly, and point out that some behavior/actions/language have been judged inappropriate and why in the current context, or can but hurtful to some people, requesting the community to self-adjust.
+* A private reprimand from the Committee to the individual(s) involved. In this case, the group chair will deliver that reprimand to the individual(s) over email, cc’ing the group.
+* A public reprimand. In this case, the Committee chair will deliver that reprimand in the same venue that the violation occurred, within the limits of practicality. E.g., the original mailing list for an email violation, but for a chat room discussion where the person/context may be gone, they can be reached by other means. The group may choose to publish this message elsewhere for documentation purposes.
+* A request for a public or private apology, assuming the reporter agrees to this idea: they may at their discretion refuse further contact with the violator. The chair will deliver this request. The Committee may, if it chooses, attach “strings” to this request: for example, the group may ask a violator to apologize in order to retain one’s membership on a mailing list.
+* A “mutually agreed upon hiatus” where the Committee asks the individual to temporarily refrain from community participation. If the individual chooses not to take a temporary break voluntarily, the Committee may issue a “mandatory cooling off period”.
+* A permanent or temporary ban from some or all NumPy spaces (mailing lists, gitter.im, etc.). The group will maintain records of all such bans so that they may be reviewed in the future or otherwise maintained.
+
+Once a resolution is agreed upon, but before it is enacted, the Committee will contact the original reporter and any other affected parties and explain the proposed resolution. The Committee will ask if this resolution is acceptable, and must note feedback for the record.
+
+Finally, the Committee will make a report to the NumPy Steering Council (as well as the NumPy core team in the event of an ongoing resolution, such as a ban).
+
+The Committee will never publicly discuss the issue; all public statements will be made by the chair of the Code of Conduct Committee or the NumPy Steering Council.
+
+
+## Conflicts of Interest
+
+In the event of any conflict of interest, a Committee member must immediately notify the other members, and recuse themselves if necessary.
From a5d263623c991b5bf592d1a79b6efacfdf993bfd Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:37:05 +0000
Subject: [PATCH 047/909] New translations privacy.md (Arabic)
---
content/ar/privacy.md | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
create mode 100644 content/ar/privacy.md
diff --git a/content/ar/privacy.md b/content/ar/privacy.md
new file mode 100644
index 0000000000..a3674dd48a
--- /dev/null
+++ b/content/ar/privacy.md
@@ -0,0 +1,18 @@
+---
+title: Privacy Policy
+sidebar: false
+---
+
+**numpy.org** is operated by [NumFOCUS, Inc.](https://numfocus.org), the fiscal sponsor of the NumPy project. For the Privacy Policy of this website please refer to https://numfocus.org/privacy-policy.
+
+If you have any questions about the policy or NumFOCUS’s data collection, use, and disclosure practices, please contact the NumFOCUS staff at privacy@numfocus.org.
+
+
+
+
+
+
+
+
+
+
From d1ce2e38ad301da1c64b2e598f9af69ab0fe13f6 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:37:09 +0000
Subject: [PATCH 048/909] New translations cricket-analytics.md (Portuguese,
Brazilian)
---
content/pt/case-studies/cricket-analytics.md | 64 ++++++++++++++++++++
1 file changed, 64 insertions(+)
create mode 100644 content/pt/case-studies/cricket-analytics.md
diff --git a/content/pt/case-studies/cricket-analytics.md b/content/pt/case-studies/cricket-analytics.md
new file mode 100644
index 0000000000..2a6ecda3bd
--- /dev/null
+++ b/content/pt/case-studies/cricket-analytics.md
@@ -0,0 +1,64 @@
+---
+title: "Estudo de Caso: Análise de Críquete, a revolução!"
+sidebar: false
+---
+
+{{< figure src="/images/content_images/cs/ipl-stadium.png" caption="**IPLT20, o maior festival de Críquete da Índia**" alt="Copa e estádio da Indian Premier League Cricket" attr="*(Image credits: IPLT20 (cup and logo) & Akash Yadav (stadium))*" attrlink="https://unsplash.com/@aksh1802" >}}
+
+
+
Você não joga para a torcida, joga para o país.
+
+
+
+## Sobre Críquete
+
+Dizer que os indianos adoram o críquete seria subestimar este sentimento. O jogo é jogado praticamente em todas as localidades da Índia, rurais ou urbanas, e é popular com os jovens e os anciões, conectando bilhões de pessoas na Índia como nenhum outro esporte. O cricket também recebe muita atenção da mídia. Há uma quantidade significativa de [dinheiro](https://www.statista.com/topics/4543/indian-premier-league-ipl/) e fama em jogo. Ao longo dos últimos anos, a tecnologia foi literalmente uma revolução. As audiências tem uma ampla possibilidade de escolha, com mídias de streaming, torneios, acesso barato a jogos de críquete ao vivo em dispositivos móveis, e mais.
+
+A Primeira Liga Indiana (*Indian Premier League* - IPL) é uma liga profissional de críquete [Twenty20](https://pt.wikipedia.org/wiki/Twenty20), fundada em 2008. É um dos eventos de críquete mais assistidos no mundo avaliado em [$6,7 bilhões de dólares](https://en.wikipedia.org/wiki/Indian_Premier_League) em 2019.
+
+Críquete é um jogo dominado pelos números - as corridas executadas por um batsman, os wickets perdidos por um boleador, as partidas ganhas por uma equipe de críquete, o número de vezes que um batsman responde de certa maneira a um tipo de arremesso do boleador, etc. A capacidade de investigar números de críquete para melhorar o desempenho e estudar as oportunidades de negócio, mercado e economia de críquete através de poderosas ferramentas de análise, alimentadas por softwares numéricos de computação, como o NumPy, é um grande negócio. As análises de críquete fornecem informações interessantes sobre o jogo e informações preditivas sobre os resultados do jogo.
+
+Hoje, existem conjuntos ricos e quase infinitos de estatísticas e informações sobre jogos de críquete, por exemplo, [ESPN cricinfo](https://stats.espncricinfo.com/ci/engine/stats/index.html) e [cricsheet](https://cricsheet.org). Estes e muitos outros bancos de dados de críquete foram usados para [análise de críquete](https://www.researchgate.net/publication/336886516_Data_visualization_and_toss_related_analysis_of_IPL_teams_and_batsmen_performances) usando os mais modernos algoritmos de aprendizagem de máquina e modelagem preditiva. Plataformas de mídia e entretenimento, juntamente com entidades de esporte profissionais associadas ao jogo usam tecnologia e análise para determinar métricas chave para melhorar as chances de vitória:
+
+* média móvel do desempenho em rebatidas,
+* previsão de pontuação,
+* ganho de informações sobre desempenho e condição física de um determinado jogador contra determinado adversário,
+* contribuições dos jogadores para vitórias e derrotas para a tomada de decisões estratégicas na composição do time
+
+{{< figure src="/images/content_images/cs/cricket-pitch.png" class="csfigcaption" caption="**Pitch de críquete, o ponto focal do campo**" alt="Um pitch de críquete com um boleador e batsmen" align="middle" attr="*(Créditos de imagem: Debarghya Das)*" attrlink="http://debarghyadas.com/files/IPLpaper.pdf" >}}
+
+### Objetivos Principais da Análise de Dados
+
+* A análise de dados esportivos é usada não somente em críquete mas em muitos [outros esportes](https://adtmag.com/blogs/dev-watch/2017/07/sports-analytics.aspx) para melhorar o desempenho geral da equipe e maximizar as chances de vitória.
+* A análise de dados em tempo real pode ajudar a obtenção de informações mesmo durante o jogo para orientar mudanças nas táticas da equipe e dos negócios associados para benefícios e crescimento econômicos.
+* Além da análise histórica, os modelos preditivos explorados para determinar os possíveis resultados das partidas requerem um conhecimento significativo sobre processamento numérico e ciência de dados, ferramentas de visualização e a possibilidade de incluir observações mais recentes na análise.
+
+{{< figure src="/images/content_images/cs/player-pose-estimator.png" class="fig-center" alt="estimador de postura" caption="**Estimador de Postura de Críquete**" attr="*(Créditos de imagem: connect.vin)*" attrlink="https://connect.vin/2019/05/ai-for-cricket-batsman-pose-analysis/" >}}
+
+### Desafios
+
+* **Limpeza e pré-processamento de dados**
+
+ A IPL expandiu o cricket para além do formato de jogo clássico para uma escala muito maior. O número de partidas jogadas a cada temporada em vários formatos tem aumentado, assim como os dados, os algoritmos, tecnologias de análise de dados mais recentes e modelos de simulação. A análise de dados de críquete requer mapeamento de campo, rastreamento do jogador, rastreamento de bola e análise de tiros do jogador, análise de lances do jogador e vários outros aspectos envolvidos em como a bola é lançada, seu ângulo, giro, velocidade e trajetória. Todos esses fatores em conjunto aumentaram a complexidade da limpeza e pré-processamento de dados.
+
+* **Modelagem Dinâmica**
+
+ No críquete, como em qualquer outro esporte, pode haver um grande número de variáveis relacionadas ao rastreamento de vários jogadores no campo, seus atributos, a bola e várias possibilidades de ações em potencial. A complexidade da análise e modelagem de dados é diretamente proporcional ao tipo de questões preditivas que são consideradas durante a análise e são altamente dependentes da representação de dados e do modelo. As coisas são ainda mais desafiadoras em termos de computação e comparações de dados quando previsões dinâmicas de jogo de críquete são desejadas, como o que teria acontecido se o batsman tivesse atingido a bola com um ângulo ou velocidade diferentes.
+
+* **Complexidade da análise preditiva**
+
+ Muito da tomada de decisões em críquete se baseia em questões como "com que frequência um batsman joga um certo tipo de lance se a recepção da bola for de um determinado tipo", ou "como um boleador muda a direção e alcance da sua jogada se o batsman responder de uma certa maneira". Esse tipo de consulta de análise preditiva requer a disponibilidade de conjuntos de dados altamente granulares e a capacidade de sintetizar dados e criar modelos generativos que sejam altamente precisos.
+
+## Papel da NumPy na Análise de Críquete
+
+A análise de dados esportivos é um campo próspero. Muitos pesquisadores e empresas [usam NumPy](https://adtmag.com/blogs/dev-watch/2017/07/sports-analytics.aspx) e outros pacotes PyData como Scikit-learn, SciPy, Matplotlib, e Jupyter, além de usar as últimas técnicas de aprendizagem de máquina e IA. A NumPy foi usada para vários tipos de análise esportiva relacionada a críquete, como:
+
+* **Análise Estatística:** Os recursos numéricos da NumPy ajudam a estimar o significado estatístico de dados observados ou de eventos ocorridos em partidas no contexto de vários jogadores e táticas de jogo, bem como estimar o resultado do jogo em comparação com um modelo generativo ou estático. [Análise Causal](https://amplitude.com/blog/2017/01/19/causation-correlation) e [abordagens em *big data*](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4996805/) são usados para análise tática.
+
+* **Visualização de dados:** Gráficos e [visualizações](https://towardsdatascience.com/advanced-sports-visualization-with-pandas-matplotlib-and-seaborn-9c16df80a81b) fornecem informações úteis sobre as relações entre vários conjuntos de dados.
+
+## Resumo
+
+A análise de dados esportivos é revolucionária quando se trata de como os jogos profissionais são jogados, especialmente se consideramos como acontece a tomada de decisões estratégicas, que até pouco tempo atrás era principalmente feito com base na "intuição" ou adesão a tradições passadas. A NumPy forma uma fundação sólida para um grande conjunto de pacotes Python que fornecem funções de alto nível relacionadas à análise de dados, aprendizagem de máquina e algoritmos de IA. Estes pacotes são amplamente implantados para se obter informações em tempo real que ajudam na tomada de decisão para resultados decisivos, tanto em campo como para se derivar inferências e orientar negócios em torno do jogo de críquete. Encontrar os parâmetros ocultos, padrões, e atributos que levam ao resultado de uma partida de críquete ajuda os envolvidos a tomar nota das percepções do jogo que estariam de outra forma ocultas nos números e estatísticas.
+
+{{< figure src="/images/content_images/cs/numpy_ca_benefits.png" class="fig-center" alt="Diagrama mostrando os benefícios de usar a NumPy para análise de críquete" caption="**Recursos principais da NumPy utilizados**" >}}
From bdeeca5156f6f3f2a96e5d7b24f14df232b6ca40 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:37:10 +0000
Subject: [PATCH 049/909] New translations press-kit.md (Arabic)
---
content/ar/press-kit.md | 8 ++++++++
1 file changed, 8 insertions(+)
create mode 100644 content/ar/press-kit.md
diff --git a/content/ar/press-kit.md b/content/ar/press-kit.md
new file mode 100644
index 0000000000..2309040ad2
--- /dev/null
+++ b/content/ar/press-kit.md
@@ -0,0 +1,8 @@
+---
+title: Press kit
+sidebar: false
+---
+
+We would like to make it easy for you to include the NumPy project identity in your next academic paper, course materials, or presentation.
+
+You will find several high-resolution versions of the NumPy logo [here](https://github.com/numpy/numpy/tree/master/branding/logo). Note that by using the numpy.org resources, you accept the [NumPy Code of Conduct](/code-of-conduct).
From 746b163d9efb609b5fbaa9bc05375148d7daf8e1 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:37:11 +0000
Subject: [PATCH 050/909] New translations learn.md (Arabic)
---
content/ar/learn.md | 84 +++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 84 insertions(+)
create mode 100644 content/ar/learn.md
diff --git a/content/ar/learn.md b/content/ar/learn.md
new file mode 100644
index 0000000000..264677ac48
--- /dev/null
+++ b/content/ar/learn.md
@@ -0,0 +1,84 @@
+---
+title: Learn
+sidebar: false
+---
+
+**The official NumPy documentation lives [here](https://numpy.org/doc/stable).**
+
+Below is a curated collection of external resources. To contribute, see the [end of this page](#add-to-this-list).
+***
+
+## Beginners
+
+There's a ton of information about NumPy out there. If you are new, we'd strongly recommend these:
+
+ **Tutorials**
+
+* [NumPy Quickstart Tutorial](https://numpy.org/devdocs/user/quickstart.html)
+* [SciPy Lectures](https://scipy-lectures.org/) Besides covering NumPy, these lectures offer a broader introduction to the scientific Python ecosystem.
+* [NumPy: the absolute basics for beginners](https://numpy.org/devdocs/user/absolute_beginners.html)
+* [Machine Learning Plus - Introduction to ndarray](https://www.machinelearningplus.com/python/numpy-tutorial-part1-array-python-examples/)
+* [Edureka - Learn NumPy Arrays with Examples ](https://www.edureka.co/blog/python-numpy-tutorial/)
+* [Dataquest - NumPy Tutorial: Data Analysis with Python](https://www.dataquest.io/blog/numpy-tutorial-python/)
+* [NumPy tutorial *by Nicolas Rougier*](https://github.com/rougier/numpy-tutorial)
+* [Stanford CS231 *by Justin Johnson*](http://cs231n.github.io/python-numpy-tutorial/)
+* [NumPy User Guide](https://numpy.org/devdocs)
+
+ **Books**
+
+* [Guide to NumPy *by Travis E. Oliphant*](http://web.mit.edu/dvp/Public/numpybook.pdf) This is a free version 1 from 2006. For the latest copy (2015) see [here](https://www.barnesandnoble.com/w/guide-to-numpy-travis-e-oliphant-phd/1122853007).
+* [From Python to NumPy *by Nicolas P. Rougier*](https://www.labri.fr/perso/nrougier/from-python-to-numpy/)
+* [Elegant SciPy](https://www.amazon.com/Elegant-SciPy-Art-Scientific-Python/dp/1491922877) *by Juan Nunez-Iglesias, Stefan van der Walt, and Harriet Dashnow*
+
+You may also want to check out the [Goodreads list](https://www.goodreads.com/shelf/show/python-scipy) on the subject of "Python+SciPy." Most books there are about the "SciPy ecosystem," which has NumPy at its core.
+
+ **Videos**
+
+* [Introduction to Numerical Computing with NumPy](http://youtu.be/ZB7BZMhfPgk) *by Alex Chabot-Leclerc*
+
+***
+
+## Advanced
+
+Try these advanced resources for a better understanding of NumPy concepts like advanced indexing, splitting, stacking, linear algebra, and more.
+
+ **Tutorials**
+
+* [100 NumPy Exercises](http://www.labri.fr/perso/nrougier/teaching/numpy.100/index.html) *by Nicolas P. Rougier*
+* [An Introduction to NumPy and Scipy](https://engineering.ucsb.edu/~shell/che210d/numpy.pdf) *by M. Scott Shell*
+* [Numpy Medkits](http://mentat.za.net/numpy/numpy_advanced_slides/) *by Stéfan van der Walt*
+* [NumPy in Python (Advanced)](https://www.geeksforgeeks.org/numpy-python-set-2-advanced/)
+* [Advanced Indexing](https://www.tutorialspoint.com/numpy/numpy_advanced_indexing.htm)
+* [Machine Learning and Data Analytics with NumPy](https://www.machinelearningplus.com/python/numpy-tutorial-python-part2/)
+
+ **Books**
+
+* [Python Data Science Handbook](https://www.amazon.com/Python-Data-Science-Handbook-Essential/dp/1491912057) *by Jake Vanderplas*
+* [Python for Data Analysis](https://www.amazon.com/Python-Data-Analysis-Wrangling-IPython/dp/1491957662) *by Wes McKinney*
+* [Numerical Python: Scientific Computing and Data Science Applications with Numpy, SciPy, and Matplotlib](https://www.amazon.com/Numerical-Python-Scientific-Applications-Matplotlib/dp/1484242459) *by Robert Johansson*
+
+ **Videos**
+
+* [Advanced NumPy - broadcasting rules, strides, and advanced indexing](https://www.youtube.com/watch?v=cYugp9IN1-Q) *by Juan Nunuz-Iglesias*
+* [Advanced Indexing Operations in NumPy Arrays](https://www.youtube.com/watch?v=2WTDrSkQBng) *by Amuls Academy*
+
+***
+
+## NumPy Talks
+
+* [The Future of NumPy Indexing](https://www.youtube.com/watch?v=o0EacbIbf58) *by Jaime Fernández* (2016)
+* [Evolution of Array Computing in Python](https://www.youtube.com/watch?v=HVLPJnvInzM&t=10s) *by Ralf Gommers* (2019)
+* [NumPy: what has changed and what is going to change?](https://www.youtube.com/watch?v=YFLVQFjRmPY) *by Matti Picus* (2019)
+* [Inside NumPy](https://www.youtube.com/watch?v=dBTJD_FDVjU) *by Ralf Gommers, Sebastian Berg, Matti Picus, Tyler Reddy, Stefan van der Walt, Charles Harris* (2019)
+* [Brief Review of Array Computing in Python](https://www.youtube.com/watch?v=f176j2g2eNc) *by Travis Oliphant* (2019)
+
+***
+
+## Citing NumPy
+
+If NumPy has been significant in your research, and you would like to acknowledge the project in your academic publication, please see [this citation information](/citing-numpy).
+
+## Contribute to this list
+
+
+To add to this collection, submit a recommendation [via a pull request](https://github.com/numpy/numpy.org/blob/master/content/en/learn.md). Say why your recommendation deserves mention on this page and also which audience would benefit most.
From 0203d36e20318bc49ea3e9b31ceb0b8d26d0f77b Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:37:12 +0000
Subject: [PATCH 051/909] New translations install.md (Arabic)
---
content/ar/install.md | 142 ++++++++++++++++++++++++++++++++++++++++++
1 file changed, 142 insertions(+)
create mode 100644 content/ar/install.md
diff --git a/content/ar/install.md b/content/ar/install.md
new file mode 100644
index 0000000000..43dd44cb12
--- /dev/null
+++ b/content/ar/install.md
@@ -0,0 +1,142 @@
+---
+title: Installing NumPy
+sidebar: false
+---
+
+The only prerequisite for installing NumPy is Python itself. If you don't have Python yet and want the simplest way to get started, we recommend you use the [Anaconda Distribution](https://www.anaconda.com/distribution) - it includes Python, NumPy, and many other commonly used packages for scientific computing and data science.
+
+NumPy can be installed with `conda`, with `pip`, with a package manager on macOS and Linux, or [from source](https://numpy.org/devdocs/user/building.html). For more detailed instructions, consult our [Python and NumPy installation guide](#python-numpy-install-guide) below.
+
+**CONDA**
+
+If you use `conda`, you can install NumPy from the `defaults` or `conda-forge` channels:
+
+```bash
+# Best practice, use an environment rather than install in the base env
+conda create -n my-env
+conda activate my-env
+# If you want to install from conda-forge
+conda config --env --add channels conda-forge
+# The actual install command
+conda install numpy
+```
+
+**PIP**
+
+If you use `pip`, you can install NumPy with:
+
+```bash
+pip install numpy
+```
+Also when using pip, it's good practice to use a virtual environment - see [Reproducible Installs](#reproducible-installs) below for why, and [this guide](https://dev.to/bowmanjd/python-tools-for-managing-virtual-environments-3bko#howto) for details on using virtual environments.
+
+
+
+# Python and NumPy installation guide
+
+Installing and managing packages in Python is complicated, there are a number of alternative solutions for most tasks. This guide tries to give the reader a sense of the best (or most popular) solutions, and give clear recommendations. It focuses on users of Python, NumPy, and the PyData (or numerical computing) stack on common operating systems and hardware.
+
+## Recommendations
+
+We'll start with recommendations based on the user's experience level and operating system of interest. If you're in between "beginning" and "advanced", please go with "beginning" if you want to keep things simple, and with "advanced" if you want to work according to best practices that go a longer way in the future.
+
+### Beginning users
+
+On all of Windows, macOS, and Linux:
+
+- Install [Anaconda](https://www.anaconda.com/distribution/) (it installs all packages you need and all other tools mentioned below).
+- For writing and executing code, use notebooks in [JupyterLab](https://jupyterlab.readthedocs.io/en/stable/index.html) for exploratory and interactive computing, and [Spyder](https://www.spyder-ide.org/) or [Visual Studio Code](https://code.visualstudio.com/) for writing scripts and packages.
+- Use [Anaconda Navigator](https://docs.anaconda.com/anaconda/navigator/) to manage your packages and start JupyterLab, Spyder, or Visual Studio Code.
+
+
+### Advanced users
+
+#### Windows or macOS
+
+- Install [Miniconda](https://docs.conda.io/en/latest/miniconda.html).
+- Keep the `base` conda environment minimal, and use one or more [conda environments](https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#) to install the package you need for the task or project you're working on.
+- Unless you're fine with only the packages in the `defaults` channel, make `conda-forge` your default channel via [setting the channel priority](https://conda-forge.org/docs/user/introduction.html#how-can-i-install-packages-from-conda-forge).
+
+
+#### Linux
+
+If you're fine with slightly outdated packages and prefer stability over being able to use the latest versions of libraries:
+- Use your OS package manager for as much as possible (Python itself, NumPy, and other libraries).
+- Install packages not provided by your package manager with `pip install somepackage --user`.
+
+If you use a GPU:
+- Install [Miniconda](https://docs.conda.io/en/latest/miniconda.html).
+- Keep the `base` conda environment minimal, and use one or more [conda environments](https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#) to install the package you need for the task or project you're working on.
+- Use the `defaults` conda channel (`conda-forge` doesn't have good support for GPU packages yet).
+
+Otherwise:
+- Install [Miniforge](https://github.com/conda-forge/miniforge).
+- Keep the `base` conda environment minimal, and use one or more [conda environments](https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#) to install the package you need for the task or project you're working on.
+
+
+#### Alternative if you prefer pip/PyPI
+
+For users who know, from personal preference or reading about the main differences between conda and pip below, they prefer a pip/PyPI-based solution, we recommend:
+- Install Python from, for example, [python.org](https://www.python.org/downloads/), [Homebrew](https://brew.sh/), or your Linux package manager.
+- Use [Poetry](https://python-poetry.org/) as the most well-maintained tool that provides a dependency resolver and environment management capabilities in a similar fashion as conda does.
+
+
+## Python package management
+
+Managing packages is a challenging problem, and, as a result, there are lots of tools. For web and general purpose Python development there's a whole [host of tools](https://packaging.python.org/guides/tool-recommendations/) complementary with pip. For high-performance computing (HPC), [Spack](https://github.com/spack/spack) is worth considering. For most NumPy users though, [conda](https://conda.io/en/latest/) and [pip](https://pip.pypa.io/en/stable/) are the two most popular tools.
+
+
+### Pip & conda
+
+The two main tools that install Python packages are `pip` and `conda`. Their functionality partially overlaps (e.g. both can install `numpy`), however, they can also work together. We'll discuss the major differences between pip and conda here - this is important to understand if you want to manage packages effectively.
+
+The first difference is that conda is cross-language and it can install Python, while pip is installed for a particular Python on your system and installs other packages to that same Python install only. This also means conda can install non-Python libraries and tools you may need (e.g. compilers, CUDA, HDF5), while pip can't.
+
+The second difference is that pip installs from the Python Packaging Index (PyPI), while conda installs from its own channels (typically "defaults" or "conda-forge"). PyPI is the largest collection of packages by far, however, all popular packages are available for conda as well.
+
+The third difference is that conda is an integrated solution for managing packages, dependencies and environments, while with pip you may need another tool (there are many!) for dealing with environments or complex dependencies.
+
+
+### Reproducible installs
+
+As libraries get updated, results from running your code can change, or your code can break completely. It's important to be able to reconstruct the set of packages and versions you're using. Best practice is to:
+
+1. use a different environment per project you're working on,
+2. record package names and versions using your package installer; each has its own metadata format for this:
+ - Conda: [conda environments and environment.yml](https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#)
+ - Pip: [virtual environments](https://docs.python.org/3/tutorial/venv.html) and [requirements.txt](https://pip.readthedocs.io/en/latest/user_guide/#requirements-files)
+ - Poetry: [virtual environments and pyproject.toml](https://python-poetry.org/docs/basic-usage/)
+
+
+
+## NumPy packages & accelerated linear algebra libraries
+
+NumPy doesn't depend on any other Python packages, however, it does depend on an accelerated linear algebra library - typically [Intel MKL](https://software.intel.com/en-us/mkl) or [OpenBLAS](https://www.openblas.net/). Users don't have to worry about installing those (they're automatically included in all NumPy install methods). Power users may still want to know the details, because the used BLAS can affect performance, behavior and size on disk:
+
+- The NumPy wheels on PyPI, which is what pip installs, are built with OpenBLAS. The OpenBLAS libraries are included in the wheel. This makes the wheel larger, and if a user installs (for example) SciPy as well, they will now have two copies of OpenBLAS on disk.
+
+- In the conda defaults channel, NumPy is built against Intel MKL. MKL is a separate package that will be installed in the users' environment when they install NumPy.
+
+- In the conda-forge channel, NumPy is built against a dummy "BLAS" package. When a user installs NumPy from conda-forge, that BLAS package then gets installed together with the actual library - this defaults to OpenBLAS, but it can also be MKL (from the defaults channel), or even [BLIS](https://github.com/flame/blis) or reference BLAS.
+
+- The MKL package is a lot larger than OpenBLAS, it's about 700 MB on disk while OpenBLAS is about 30 MB.
+
+- MKL is typically a little faster and more robust than OpenBLAS.
+
+Besides install sizes, performance and robustness, there are two more things to consider:
+
+- Intel MKL is not open source. For normal use this is not a problem, but if a user needs to redistribute an application built with NumPy, this could be an issue.
+- Both MKL and OpenBLAS will use multi-threading for function calls like `np.dot`, with the number of threads being determined by both a build-time option and an environment variable. Often all CPU cores will be used. This is sometimes unexpected for users; NumPy itself doesn't auto-parallelize any function calls. It typically yields better performance, but can also be harmful - for example when using another level of parallelization with Dask, scikit-learn or multiprocessing.
+
+
+## Troubleshooting
+
+If your installation fails with the message below, see [Troubleshooting ImportError](https://numpy.org/doc/stable/user/troubleshooting-importerror.html).
+
+```
+IMPORTANT: PLEASE READ THIS FOR ADVICE ON HOW TO SOLVE THIS ISSUE!
+
+Importing the numpy c-extensions failed. This error can happen for
+different reasons, often due to issues with your setup.
+```
+
From 4134f336b03c1e10daca62bfaa7ba19f3cc38283 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:37:14 +0000
Subject: [PATCH 052/909] New translations contribute.md (Arabic)
---
content/ar/contribute.md | 78 ++++++++++++++++++++++++++++++++++++++++
1 file changed, 78 insertions(+)
create mode 100644 content/ar/contribute.md
diff --git a/content/ar/contribute.md b/content/ar/contribute.md
new file mode 100644
index 0000000000..2533761d12
--- /dev/null
+++ b/content/ar/contribute.md
@@ -0,0 +1,78 @@
+- - -
+title: Contribute to NumPy sidebar: false
+- - -
+
+The NumPy project welcomes your expertise and enthusiasm! Your choices aren't limited to programming -- in addition to
+
+- [Writing code](#writing-code)
+
+you can
+
+- [Review pull requests](#reviewing-pull-requests)
+- [Develop tutorials, presentations, and other educational material](#developing-educational-materials)
+- [Triage issues](#issue-triaging)
+- [Work on our website](#website-development)
+- [Contribute graphic design](#graphic-design)
+- [Translate website content](#translating-website-content)
+- [Serve as a community coordinator](#community-coordination-and-outreach)
+- [Write grant proposals and help with other fundraising](#fundraising)
+
+If you're unsure where to start or how your skills fit in, _reach out!_ You can ask on the [mailing list](https://mail.python.org/mailman/listinfo/numpy-discussion) or [GitHub](http://github.com/numpy/numpy) (open an [issue](https://github.com/numpy/numpy/issues) or comment on a relevant issue).
+
+Those are our preferred channels (open source is open by nature), but if you prefer to talk privately, contact our community coordinators at or on [Slack](https://numpy-team.slack.com) (write for an invite).
+
+We also have a biweekly _community call_, details of which are announced on the [mailing list](https://mail.python.org/mailman/listinfo/numpy-discussion). You are very welcome to join. If you are new to contributing to open source, we also highly recommend reading [this guide](https://opensource.guide/how-to-contribute/).
+
+Our community aspires to treat everyone equally and to value all contributions. We have a [Code of Conduct](/code-of-conduct) to foster an open and welcoming environment.
+
+### Writing code
+
+Programmers, this [guide](https://numpy.org/devdocs/dev/index.html#development-process-summary) explains how to contribute to the codebase.
+
+### Reviewing pull requests
+The project has more than 250 open pull requests -- meaning many potential improvements and many open-source contributors waiting for feedback. If you're a developer who knows NumPy, you can help even if you're not familiar with the codebase. You can:
+* summarize a long-running discussion
+* triage documentation PRs
+* test proposed changes
+
+
+### Developing educational materials
+
+NumPy's [User Guide](https://numpy.org/devdocs) is undergoing rehabilitation. We're in need of new tutorials, how-to's, and deep-dive explanations, and the site needs restructuring. Opportunities aren't limited to writers. We'd also welcome worked examples, notebooks, and videos. [NEP 44 — Restructuring the NumPyDocumentation](https://numpy.org/neps/nep-0044-restructuring-numpy-docs.html) lays out our ideas -- and you may have others.
+
+
+### Issue triaging
+
+The [NumPy issue tracker](https://github.com/numpy/numpy/issues) has a _lot_ of open issues. Some are no longer valid, some should be prioritized, and some would make good issues for new contributors. You can:
+
+* check if older bugs are still present
+* find duplicate issues and link related ones
+* add good self-contained reproducers to issues
+* label issues correctly (this requires triage rights -- just ask)
+
+Please just dive in.
+
+
+### Website development
+
+We've just revamped our website, but we're far from done. If you love web development, these [issues](https://github.com/numpy/numpy.org/issues?q=is%3Aissue+is%3Aopen+label%3Adesign) list some of our unmet needs -- and feel free to share your own ideas.
+
+
+### Graphic design
+
+We can barely begin to list the contributions a graphic designer can make here. Our docs are parched for illustration; our growing website craves images -- opportunities abound.
+
+
+### Translating website content
+
+We plan multiple translations of [numpy.org](https://numpy.org) to make NumPy accessible to users in their native language. Volunteer translators are at the heart of this effort. See [here](https://numpy.org/neps/nep-0028-website-redesign.html#translation-multilingual-i18n) for background; comment on [this GitHub issue](https://github.com/numpy/numpy.org/issues/55) to sign up.
+
+
+### Community coordination and outreach
+
+Through community contact we share our work more widely and learn where we're falling short. We're eager to get more people involved in efforts like our [Twitter](https://twitter.com/numpy_team) account, organizing NumPy [code sprints](https://scisprints.github.io/), a newsletter, and perhaps a blog.
+
+### Fundraising
+
+NumPy was all-volunteer for many years, but as its importance grew it became clear that to ensure stability and growth we'd need financial support. [This SciPy'19 talk](https://www.youtube.com/watch?v=dBTJD_FDVjU) explains how much difference that support has made. Like all the nonprofit world, we're constantly searching for grants, sponsorships, and other kinds of support. We have a number of ideas and of course we welcome more. Fundraising is a scarce skill here -- we'd appreciate your help.
+
From 14e0a0daf03144a7f9fa723f5eaabcd3ecf94131 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:37:15 +0000
Subject: [PATCH 053/909] New translations community.md (Arabic)
---
content/ar/community.md | 65 +++++++++++++++++++++++++++++++++++++++++
1 file changed, 65 insertions(+)
create mode 100644 content/ar/community.md
diff --git a/content/ar/community.md b/content/ar/community.md
new file mode 100644
index 0000000000..4e24a83784
--- /dev/null
+++ b/content/ar/community.md
@@ -0,0 +1,65 @@
+---
+title: Community
+sidebar: false
+---
+
+NumPy is a community-driven open source project developed by a very diverse group of [contributors](/gallery/team.html). The NumPy leadership has made a strong commitment to creating an open, inclusive, and positive community. Please read the [NumPy Code of Conduct](/code-of-conduct) for guidance on how to interact with others in a way that makes the community thrive.
+
+We offer several communication channels to learn, share your knowledge and connect with others within the NumPy community.
+
+
+## Participate online
+
+The following are ways to engage directly with the NumPy project and community. _Please note that we encourage users and community members to support each other for usage questions - see [Get Help](/gethelp)._
+
+
+### [NumPy mailing list](https://mail.python.org/mailman/listinfo/numpy-discussion)
+
+This list is the main forum for longer-form discussions, like adding new features to NumPy, making changes to the NumPy Roadmap, and all kinds of project-wide decision making. Announcements about NumPy, such as for releases, developer meetings, sprints or conference talks are also made on this list.
+
+On this list please use bottom posting, reply to the list (rather than to another sender), and don't reply to digests. A searchable archive of this list is available [here](http://numpy-discussion.10968.n7.nabble.com/).
+
+***
+
+### [GitHub issue tracker](https://github.com/numpy/numpy/issues)
+
+- For bug reports (e.g. "`np.arange(3).shape` returns `(5,)`, when it should return `(3,)`");
+- documentation issues (e.g. "I found this section unclear");
+- and feature requests (e.g. "I would like to have a new interpolation method in `np.percentile`").
+
+_Please note that GitHub is not the right place to report a security vulnerability. If you think you have found a security vulnerability in NumPy, please report it [here](https://tidelift.com/docs/security)._
+
+***
+
+### [Slack](https://numpy-team.slack.com)
+
+A real-time chat room to ask questions about _contributing_ to NumPy. This is a private space, specifically meant for people who are hesitant to bring up their questions or ideas on a large public mailing list or GitHub. Please see [here](https://numpy.org/devdocs/dev/index.html#contributing-to-numpy) for more details and how to get an invite.
+
+
+## Study Groups and Meetups
+
+If you would like to find a local meetup or study group to learn more about NumPy and the wider ecosystem of Python packages for data science and scientific computing, we recommend exploring the [PyData meetups](https://www.meetup.com/pro/pydata/) (150+ meetups, 100,000+ members).
+
+NumPy also organizes in-person sprints for its team and interested contributors occasionally. These are typically planned several months in advance and will be announced on the [mailing list](https://mail.python.org/mailman/listinfo/numpy-discussion) and [Twitter](https://twitter.com/numpy_team).
+
+
+## Conferences
+
+The NumPy project doesn't organize its own conferences. The conferences that have traditionally been most popular with NumPy maintainers, contributors and users are the SciPy and PyData conference series:
+
+- [SciPy US](https://conference.scipy.org)
+- [EuroSciPy](https://www.euroscipy.org)
+- [SciPy Latin America](https://www.scipyla.org)
+- [SciPy India](https://scipy.in)
+- [SciPy Japan](https://conference.scipy.org)
+- [PyData conferences](https://pydata.org/event-schedule/) (15-20 events a year spread over many countries)
+
+Many of these conferences include tutorial days that cover NumPy and/or sprints where you can learn how to contribute to NumPy or related open source projects.
+
+
+## Join the NumPy community
+
+To thrive, the NumPy project needs your expertise and enthusiasm. Not a coder? Not a problem! There are many ways to contribute to NumPy.
+
+If you are interested in becoming a NumPy contributor (yay!) we recommend checking out our [Contribute](/contribute) page.
+
From 74afed6c204c8f517138e883269fc858e0f6da3c Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:37:16 +0000
Subject: [PATCH 054/909] New translations code-of-conduct.md (Arabic)
---
content/ar/code-of-conduct.md | 83 +++++++++++++++++++++++++++++++++++
1 file changed, 83 insertions(+)
create mode 100644 content/ar/code-of-conduct.md
diff --git a/content/ar/code-of-conduct.md b/content/ar/code-of-conduct.md
new file mode 100644
index 0000000000..efcde754ae
--- /dev/null
+++ b/content/ar/code-of-conduct.md
@@ -0,0 +1,83 @@
+---
+title: NumPy Code of Conduct
+sidebar: false
+aliases:
+ - /conduct.html
+---
+
+### Introduction
+
+This Code of Conduct applies to all spaces managed by the NumPy project, including all public and private mailing lists, issue trackers, wikis, blogs, Twitter, and any other communication channel used by our community. The NumPy project does not organise in-person events, however events related to our community should have a code of conduct similar in spirit to this one.
+
+This Code of Conduct should be honored by everyone who participates in the NumPy community formally or informally, or claims any affiliation with the project, in any project-related activities and especially when representing the project, in any role.
+
+This code is not exhaustive or complete. It serves to distill our common understanding of a collaborative, shared environment and goals. Please try to follow this code in spirit as much as in letter, to create a friendly and productive environment that enriches the surrounding community.
+
+### Specific Guidelines
+
+We strive to:
+
+1. Be open. We invite anyone to participate in our community. We prefer to use public methods of communication for project-related messages, unless discussing something sensitive. This applies to messages for help or project-related support, too; not only is a public support request much more likely to result in an answer to a question, it also ensures that any inadvertent mistakes in answering are more easily detected and corrected.
+2. Be empathetic, welcoming, friendly, and patient. We work together to resolve conflict, and assume good intentions. We may all experience some frustration from time to time, but we do not allow frustration to turn into a personal attack. A community where people feel uncomfortable or threatened is not a productive one.
+3. Be collaborative. Our work will be used by other people, and in turn we will depend on the work of others. When we make something for the benefit of the project, we are willing to explain to others how it works, so that they can build on the work to make it even better. Any decision we make will affect users and colleagues, and we take those consequences seriously when making decisions.
+4. Be inquisitive. Nobody knows everything! Asking questions early avoids many problems later, so we encourage questions, although we may direct them to the appropriate forum. We will try hard to be responsive and helpful.
+5. Be careful in the words that we choose. We are careful and respectful in our communication, and we take responsibility for our own speech. Be kind to others. Do not insult or put down other participants. We will not accept harassment or other exclusionary behaviour, such as:
+ * Violent threats or language directed against another person.
+ * Sexist, racist, or otherwise discriminatory jokes and language.
+ * Posting sexually explicit or violent material.
+ * Posting (or threatening to post) other people’s personally identifying information (“doxing”).
+ * Sharing private content, such as emails sent privately or non-publicly, or unlogged forums such as IRC channel history, without the sender’s consent.
+ * Personal insults, especially those using racist or sexist terms.
+ * Unwelcome sexual attention.
+ * Excessive profanity. Please avoid swearwords; people differ greatly in their sensitivity to swearing.
+ * Repeated harassment of others. In general, if someone asks you to stop, then stop.
+ * Advocating for, or encouraging, any of the above behaviour.
+
+### Diversity Statement
+
+The NumPy project welcomes and encourages participation by everyone. We are committed to being a community that everyone enjoys being part of. Although we may not always be able to accommodate each individual’s preferences, we try our best to treat everyone kindly.
+
+No matter how you identify yourself or how others perceive you: we welcome you. Though no list can hope to be comprehensive, we explicitly honour diversity in: age, culture, ethnicity, genotype, gender identity or expression, language, national origin, neurotype, phenotype, political beliefs, profession, race, religion, sexual orientation, socioeconomic status, subculture and technical ability, to the extent that these do not conflict with this code of conduct.
+
+Though we welcome people fluent in all languages, NumPy development is conducted in English.
+
+Standards for behaviour in the NumPy community are detailed in the Code of Conduct above. Participants in our community should uphold these standards in all their interactions and help others to do so as well (see next section).
+
+### Reporting Guidelines
+
+We know that it is painfully common for internet communication to start at or devolve into obvious and flagrant abuse. We also recognize that sometimes people may have a bad day, or be unaware of some of the guidelines in this Code of Conduct. Please keep this in mind when deciding on how to respond to a breach of this Code.
+
+For clearly intentional breaches, report those to the Code of Conduct Committee (see below). For possibly unintentional breaches, you may reply to the person and point out this code of conduct (either in public or in private, whatever is most appropriate). If you would prefer not to do that, please feel free to report to the Code of Conduct Committee directly, or ask the Committee for advice, in confidence.
+
+You can report issues to the NumPy Code of Conduct Committee at numpy-conduct@googlegroups.com.
+
+Currently, the Committee consists of:
+
+* Stefan van der Walt
+* Melissa Weber Mendonça
+* Anirudh Subramanian
+
+If your report involves any members of the Committee, or if they feel they have a conflict of interest in handling it, then they will recuse themselves from considering your report. Alternatively, if for any reason you feel uncomfortable making a report to the Committee, then you can also contact senior NumFOCUS staff at [conduct@numfocus.org](https://numfocus.org/code-of-conduct#persons-responsible).
+
+### Incident reporting resolution & Code of Conduct enforcement
+
+_This section summarizes the most important points, more details can be found in_ [NumPy Code of Conduct - How to follow up on a report](/report-handling-manual).
+
+We will investigate and respond to all complaints. The NumPy Code of Conduct Committee and the NumPy Steering Committee (if involved) will protect the identity of the reporter, and treat the content of complaints as confidential (unless the reporter agrees otherwise).
+
+In case of severe and obvious breaches, e.g. personal threat or violent, sexist or racist language, we will immediately disconnect the originator from NumPy communication channels; please see the manual for details.
+
+In cases not involving clear severe and obvious breaches of this Code of Conduct the process for acting on any received Code of Conduct violation report will be:
+
+1. acknowledge report is received,
+2. reasonable discussion/feedback,
+3. mediation (if feedback didn’t help, and only if both reporter and reportee agree to this),
+4. enforcement via transparent decision (see [Resolutions](/report-handling-manual#resolutions)) by the Code of Conduct Committee.
+
+The Committee will respond to any report as soon as possible, and at most within 72 hours.
+
+### Endnotes
+
+We are thankful to the groups behind the following documents, from which we drew content and inspiration:
+
+- [The SciPy Code of Conduct](https://docs.scipy.org/doc/scipy/reference/dev/conduct/code_of_conduct.html)
From 96e8c288774d75773bb000069a1356ca28e43869 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:37:17 +0000
Subject: [PATCH 055/909] New translations citing-numpy.md (Arabic)
---
content/ar/citing-numpy.md | 35 +++++++++++++++++++++++++++++++++++
1 file changed, 35 insertions(+)
create mode 100644 content/ar/citing-numpy.md
diff --git a/content/ar/citing-numpy.md b/content/ar/citing-numpy.md
new file mode 100644
index 0000000000..cf20ae59cf
--- /dev/null
+++ b/content/ar/citing-numpy.md
@@ -0,0 +1,35 @@
+---
+title: Citing NumPy
+sidebar: false
+---
+
+If NumPy has been significant in your research, and you would like to acknowledge the project in your academic publication, we suggest citing the following paper:
+
+* Harris, C.R., Millman, K.J., van der Walt, S.J. et al. _Array programming with NumPy_. Nature 585, 357–362 (2020). DOI: [0.1038/s41586-020-2649-2](https://doi.org/10.1038/s41586-020-2649-2). ([Publisher link](https://www.nature.com/articles/s41586-020-2649-2)).
+
+_In BibTeX format:_
+
+ ```
+@Article{ harris2020array,
+ title = {Array programming with {NumPy}},
+ author = {Charles R. Harris and K. Jarrod Millman and St{'{e}}fan J.
+ van der Walt and Ralf Gommers and Pauli Virtanen and David
+ Cournapeau and Eric Wieser and Julian Taylor and Sebastian
+ Berg and Nathaniel J. Smith and Robert Kern and Matti Picus
+ and Stephan Hoyer and Marten H. van Kerkwijk and Matthew
+ Brett and Allan Haldane and Jaime Fern{'{a}}ndez del
+ R{'{\i}}o and Mark Wiebe and Pearu Peterson and Pierre
+ G{'{e}}rard-Marchant and Kevin Sheppard and Tyler Reddy and
+ Warren Weckesser and Hameer Abbasi and Christoph Gohlke and
+ Travis E. Oliphant},
+ year = {2020},
+ month = sep,
+ journal = {Nature},
+ volume = {585},
+ number = {7825},
+ pages = {357--362},
+ doi = {10.1038/s41586-020-2649-2},
+ publisher = {Springer Science and Business Media {LLC}},
+ url = {https://doi.org/10.1038/s41586-020-2649-2}
+}
+```
From 10c7aabb45d2640ff12c2276700c91facc5c30b2 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:37:19 +0000
Subject: [PATCH 056/909] New translations arraycomputing.md (Arabic)
---
content/ar/arraycomputing.md | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
create mode 100644 content/ar/arraycomputing.md
diff --git a/content/ar/arraycomputing.md b/content/ar/arraycomputing.md
new file mode 100644
index 0000000000..abd29d11c1
--- /dev/null
+++ b/content/ar/arraycomputing.md
@@ -0,0 +1,21 @@
+---
+title: Array Computing
+sidebar: false
+---
+
+*Array computing is the foundation of statistical, mathematical, scientific computing in various contemporary data science and analytics applications such as data visualization, digital signal processing, image processing, bioinformatics, machine learning, AI, and several others.*
+
+Large scale data manipulation and transformation depends on efficient, high-performance array computing. The language of choice for data analytics, machine learning, and productive numerical computing is **Python.**
+
+**Num**erical **Py**thon or NumPy is its de-facto standard Python programming language library that supports large, multi-dimensional arrays and matrices, and comes with a vast collection of high-level mathematical functions to operate on these arrays.
+
+Since the launch of NumPy in 2006, Pandas appeared on the landscape in 2008, and it was not until a couple of years ago that several array computing libraries showed up in succession, crowding the array computing landscape. Many of these newer libraries mimic NumPy-like features and capabilities, and pack newer algorithms and features geared towards machine learning and artificial intelligence applications.
+
+
+
+**Array computing** is based on **arrays** data structures. *Arrays* are used to organize vast amounts of data such that a related set of values can be easily sorted, searched, mathematically manipulated, and transformed easily and quickly.
+
+Array computing is *unique* as it involves operating on the data array *at once*. What this means is that any array operation applies to an entire set of values in one shot. This vectorized approach provides speed and simplicity by enabling programmers to code and operate on aggregates of data, without having to use loops of individual scalar operations.
From ceb0d8c276b36b7701f60e672126a6ab374e9fe3 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:37:20 +0000
Subject: [PATCH 057/909] New translations about.md (Arabic)
---
content/ar/about.md | 69 +++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 69 insertions(+)
create mode 100644 content/ar/about.md
diff --git a/content/ar/about.md b/content/ar/about.md
new file mode 100644
index 0000000000..df89bff1f5
--- /dev/null
+++ b/content/ar/about.md
@@ -0,0 +1,69 @@
+---
+title: About Us
+sidebar: false
+---
+
+_Some information about the NumPy project and community_
+
+NumPy is an open source project aiming to enable numerical computing with Python. It was created in 2005, building on the early work of the Numerical and Numarray libraries. NumPy will always be 100% open source software, free for all to use and released under the liberal terms of the [modified BSD license](https://github.com/numpy/numpy/blob/master/LICENSE.txt).
+
+NumPy is developed in the open on GitHub, through the consensus of the NumPy and wider scientific Python community. For more information on our governance approach, please see our [Governance Document](https://www.numpy.org/devdocs/dev/governance/index.html).
+
+
+## Steering Council
+
+The role of the NumPy Steering Council is to ensure, through working with and serving the broader NumPy community, the long-term well-being of the project, both technically and as a community. The NumPy Steering Council currently consists of the following members (in alphabetical order):
+
+- Sebastian Berg
+- Jaime Fernández del Río
+- Ralf Gommers
+- Allan Haldane
+- Charles Harris
+- Stephan Hoyer
+- Matti Picus
+- Nathaniel Smith
+- Julian Taylor
+- Pauli Virtanen
+- Stéfan van der Walt
+- Eric Wieser
+
+Emeritus:
+
+- Travis Oliphant (project founder, 2005-2012)
+- Alex Griffing (2015-2017)
+- Marten van Kerkwijk (2017-2019)
+
+## Teams
+
+The NumPy project is growing; we have teams for
+
+- code
+- documentation
+- website
+- triage
+- funding and grants
+
+See the [Team](/gallery/team.html) page for individual team members.
+
+## Sponsors
+
+NumPy receives direct funding from the following sources:
+{{< sponsors >}}
+
+
+## Institutional Partners
+
+Institutional Partners are organizations that support the project by employing people that contribute to NumPy as part of their job. Current Institutional Partners include:
+{{< partners >}}
+
+
+## Donate
+
+If you have found NumPy useful in your work, research, or company, please consider a donation to the project commensurate with your resources. Any amount helps! All donations will be used strictly to fund the development of NumPy’s open source software, documentation, and community.
+
+NumPy is a Sponsored Project of NumFOCUS, a 501(c)(3) nonprofit charity in the United States. NumFOCUS provides NumPy with fiscal, legal, and administrative support to help ensure the health and sustainability of the project. Visit [numfocus.org](https://numfocus.org) for more information.
+
+Donations to NumPy are managed by [NumFOCUS](https://numfocus.org). For donors in the United States, your gift is tax-deductible to the extent provided by law. As with any donation, you should consult with your tax advisor about your particular tax situation.
+
+NumPy's Steering Council will make the decisions on how to best use any funds received. Technical and infrastructure priorities are documented on the [NumPy Roadmap](https://www.numpy.org/neps/index.html#roadmap).
+{{< numfocus >}}
From 85dfbea6cba1f26372ee4f2fc35a6dfc8b32eda5 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:37:21 +0000
Subject: [PATCH 058/909] New translations 404.md (Arabic)
---
content/ar/404.md | 8 ++++++++
1 file changed, 8 insertions(+)
create mode 100644 content/ar/404.md
diff --git a/content/ar/404.md b/content/ar/404.md
new file mode 100644
index 0000000000..da192c53c0
--- /dev/null
+++ b/content/ar/404.md
@@ -0,0 +1,8 @@
+---
+title: 404
+sidebar: false
+---
+
+Oops! You've reached a dead end.
+
+If you think something should be here, you can [open an issue](https://github.com/numpy/numpy.org/issues) on GitHub.
From 050a7866744ba80a900e77c1d843fa6a11e5bff4 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:37:23 +0000
Subject: [PATCH 059/909] New translations diversity_sep2020.md (Portuguese,
Brazilian)
---
content/pt/diversity_sep2020.md | 48 +++++++++++++++++++++++++++++++++
1 file changed, 48 insertions(+)
create mode 100644 content/pt/diversity_sep2020.md
diff --git a/content/pt/diversity_sep2020.md b/content/pt/diversity_sep2020.md
new file mode 100644
index 0000000000..ef3030d5f7
--- /dev/null
+++ b/content/pt/diversity_sep2020.md
@@ -0,0 +1,48 @@
+---
+title: NumPy Diversity and Inclusion Statement
+sidebar: false
+---
+
+
+_In light of the foregoing discussion on social media after publication of the NumPy paper in Nature and the concerns raised about the state of diversity and inclusion on the NumPy team, we would like to issue the following statement:_
+
+
+It is our strong belief that we are at our best, as a team and community, when we are inclusive and equitable. Being an international team from the onset, we recognize the value of collaborating with individuals from diverse backgrounds and expertise. A culture where everyone is welcomed, supported, and valued is at the core of the NumPy project.
+
+## The Past
+
+Contributing to open source has always been a pastime in which most historically marginalized groups, especially women, faced more obstacles to participate due to a number of societal constraints and expectations. Open source has a severe diversity gap that is well documented (see, e.g., the [2017 GitHub Open Source Survey](https://opensourcesurvey.org/2017/) and [this blog post](https://medium.com/tech-diversity-files/if-you-think-women-in-tech-is-just-a-pipeline-problem-you-haven-t-been-paying-attention-cb7a2073b996)).
+
+Since its inception and until 2018, NumPy was maintained by a handful of volunteers often working nights and weekends outside of their day jobs. At any one time, the number of active core developers, the ones doing most of the heavy lifting as well as code review and integration of contributions from the community, was in the range of 4 to 8. The project didn't have a roadmap or mechanism for directing resources, being driven by individual efforts to work on what seemed needed. The authors on the NumPy paper are the individuals who made the most significant and sustained contributions to the project over a period of 15 years (2005 - 2019). The lack of diversity on this author list is a reflection of the formative years of the Python and SciPy ecosystems.
+
+2018 has marked an important milestone in the history of the NumPy project. Receiving funding from The Gordon and Betty Moore Foundation and Alfred P. Sloan Foundation allowed us to provide full-time employment for two software engineers with years of experience contributing to the Python ecosystem. Those efforts brought NumPy to a much healthier technical state.
+
+This funding also created space for NumPy maintainers to focus on project governance, community development, and outreach to underrepresented groups. [The diversity statement](https://figshare.com/articles/online_resource/Diversity_and_Inclusion_Statement_NumPy_for_Chan_Zuckerberg_Initiative_EOSS_2019_round_1/12980852) written in mid 2019 for the CZI EOSS program grant application details some of the challenges as well as the advances in our efforts to bring in more diverse talent to the NumPy team.
+
+## The Present
+
+Offering employment opportunities is an effective way to attract and retain diverse talent in OSS. Therefore, we used two-thirds of our second grant that became available in Dec 2019 to employ Melissa Weber Mendonça and Mars Lee.
+
+As a result of several initiatives aimed at community development and engagement led by Inessa Pawson and Ralf Gommers, the NumPy project has received a number of valuable contributions from women and other underrepresented groups in open source in 2020:
+
+- Melissa Weber Mendonça gained commit rights, is maintaining numpy.f2py and is leading the documentation team,
+- Shaloo Shalini created all case studies on numpy.org,
+- Mars Lee contributed web design and led our accessibility improvements work,
+- Isabela Presedo-Floyd designed our new logo,
+- Stephanie Mendoza, Xiayoi Deng, Deji Suolang, and Mame Fatou Thiam designed and fielded the first NumPy user survey,
+- Yuki Dunn, Dayane Machado, Mahfuza Humayra Mohona, Sumera Priyadarsini, Shaloo Shalini, and Kriti Singh (former Outreachy intern) helped the survey team to reach out to non-English speaking NumPy users and developers by translating the questionnaire into their native languages,
+- Sayed Adel, Raghuveer Devulapalli, and Chunlin Fang are driving the work on SIMD optimizations in the core of NumPy.
+
+While we still have much more work to do, the NumPy team is starting to look much more representative of our user base. And we can assure you that the next NumPy paper will certainly have a more diverse group of authors.
+
+## The Future
+
+We are fully committed to fostering inclusion and diversity on our team and in our community, and to do our part in building a more just and equitable future.
+
+We are open to dialogue and welcome every opportunity to connect with organizations representing and supporting women and minorities in tech and science. We are ready to listen, learn, and support.
+
+Please get in touch with us on [our mailing list](https://scipy.org/scipylib/mailing-lists.html#mailing-lists), [GitHub](https://github.com/numpy/numpy/issues), [Slack](https://numpy.org/contribute/), in private at numpy-team@googlegroups.com, or join our [bi-weekly community meeting](https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg).
+
+
+_Sayed Adel, Sebastian Berg, Raghuveer Devulapalli, Chunlin Fang, Ralf Gommers, Allan Haldane, Stephan Hoyer, Mars Lee, Melissa Weber Mendonça, Jarrod Millman, Inessa Pawson, Matti Picus, Nathaniel Smith, Julian Taylor, Pauli Virtanen, Stéfan van der Walt, Eric Wieser, on behalf of the NumPy team_
+
From 949c999d4d009cd72ca2fbe8808c7b1c6e809335 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:37:25 +0000
Subject: [PATCH 060/909] New translations gw-discov.md (Portuguese, Brazilian)
---
content/pt/case-studies/gw-discov.md | 69 ++++++++++++++++++++++++++++
1 file changed, 69 insertions(+)
create mode 100644 content/pt/case-studies/gw-discov.md
diff --git a/content/pt/case-studies/gw-discov.md b/content/pt/case-studies/gw-discov.md
new file mode 100644
index 0000000000..d189210057
--- /dev/null
+++ b/content/pt/case-studies/gw-discov.md
@@ -0,0 +1,69 @@
+---
+title: "Estudo de Caso: Descoberta de Ondas Gravitacionais"
+sidebar: false
+---
+
+{{< figure src="/images/content_images/cs/gw_sxs_image.png" class="fig-center" caption="**Ondas gravitacionais**" alt="binary coalesce black hole generating gravitational waves" attr="*(Créditos de imagem: O projeto Simulating eXtreme Spacetimes (SXS) no LIGO)*" attrlink="https://youtu.be/Zt8Z_uzG71o" >}}
+
+
+
O ecossistema científico Python é uma infraestrutura crítica para a pesquisa feita no LIGO.
+
+
+
+## Sobre [Ondas Gravitacionais](https://www.nationalgeographic.com/news/2017/10/what-are-gravitational-waves-ligo-astronomy-science/) e o [LIGO](https://www.ligo.caltech.edu)
+
+Ondas gravitacionais são ondulações no tecido espaço-tempo, gerado por eventos cataclísmicos no universo, como colisão e fusão de dois buracos negros ou a coalescência de estrelas binárias ou supernovas. A observação de ondas gravitacionais pode ajudar não só no estudo da gravidade, mas também no entendimento de alguns dos fenômenos obscuros existentes no universo distante e seu impacto.
+
+O [Observatório Interferômetro Laser de Ondas Gravitacionais (LIGO)](https://www.ligo.caltech.edu) foi projetado para abrir o campo da astrofísica das ondas gravitacionais através da detecção direta de ondas gravitacionais previstas pela Teoria Geral da Relatividade de Einstein. O observatório consiste de dois interferômetros amplamente separados dentro dos Estados Unidos - um em Hanford, Washington e o outro em Livingston, Louisiana — operando em uníssono para detectar ondas gravitacionais. Cada um deles tem detectores em escala quilométrica de ondas gravitacionais que usam interferometria laser. A Colaboração Científica LIGO (LSC), é um grupo de mais de 1000 cientistas de universidades dos Estados Unidos e em 14 outros países apoiados por mais de 90 universidades e institutos de pesquisa; aproximadamente 250 estudantes contribuem ativamente com a colaboração. A nova descoberta do LIGO é a primeira observação de ondas gravitacionais em si, feita medindo os pequenos distúrbios que as ondas fazem ao espaço-tempo enquanto atravessam a terra. A descoberta abriu novas fronteiras astrofísicas que exploram o lado "curvado" do universo - objetos e fenômenos que são feitos a partir da curvatura do espaço-tempo.
+
+
+### Objetivos
+
+* Embora sua [missão](https://www.ligo.caltech.edu/page/what-is-ligo) seja detectar ondas gravitacionais de alguns dos processos mais violentos e enérgicos no Universo, os dados que o LIGO coleta podem ter efeitos de grande alcance em muitas áreas da física, incluindo gravitação, relatividade, astrofísica, cosmologia, física de partículas e física nuclear.
+* Processar dados observados através de cálculos numéricos de relatividade que envolvem matemática complexa para identificar o sinal e o ruído, filtrar o sinal relevante e estimar estatisticamente o significado dos dados observados.
+* Visualização de dados para que os resultados binários/numéricos possam ser compreendidos.
+
+
+
+### Desafios
+
+* **Computação**
+
+ As ondas gravitacionais são difíceis de detectar pois produzem um efeito muito pequeno e têm uma pequena interação com a matéria. Processar e analisar todos os dados do LIGO requer uma vasta infraestrutura de computação. Depois de cuidar do ruído, que é bilhões de vezes maior que o sinal, ainda há equações de relatividade complexas e enormes quantidades de dados que apresentam um desafio computacional: [O(10^7) horas de CPU necessárias para análises de fusão binária](https://youtu.be/7mcHknWWzNI) espalhado em 6 clusters LIGO dedicados.
+
+* **Sobrecarga de dados**
+
+ À medida que os dispositivos observacionais se tornam mais sensíveis e confiáveis, os desafios criados pela sobrecarga de dados e a procura por uma agulha em um palheiro se tornam muito maiores. O LIGO gera terabytes de dados todos os dias! Entender esses dados requer um enorme esforço para cada detecção. Por exemplo, os sinais sendo coletados pelo LIGO devem ser combinados por supercomputadores e comparados a centenas de milhares de modelos de possíveis assinaturas de ondas gravitacionais.
+
+* **Visualização**
+
+ Uma vez que os obstáculos relacionados a compreender as equações de Einstein bem o suficiente para resolvê-las usando supercomputadores foram ultrapassados, o próximo grande desafio era tornar os dados compreensíveis para o cérebro humano. A modelagem de simulações, assim como a detecção de sinais, exigem técnicas de visualização efetiva. A visualização também desempenha um papel de fornecer mais credibilidade à relatividade numérica aos olhos dos aficionados pela ciência pura, que não dão importância suficiente à relatividade numérica até que a imagem e as simulações tornem mais fácil a compreensão dos resultados para um público maior. A velocidade da computação complexa, e da renderização, re-renderização de imagens e simulações usando as últimas entradas e informações experimentais pode ser uma atividade demorada que desafia pesquisadores neste domínio.
+
+{{< figure src="/images/content_images/cs/gw_strain_amplitude.png" class="fig-center" alt="gravitational waves strain amplitude" caption="**Amplitude estimada da deformação das ondas gravitacionais do evento GW150914**" attr="(**Créditos do gráfico:** Observation of Gravitational Waves from a Binary Black Hole Merger, ResearchGate Publication)" attrlink="https://www.researchgate.net/publication/293886905_Observation_of_Gravitational_Waves_from_a_Binary_Black_Hole_Merger" >}}
+
+## O papel da NumPy na detecção de ondas gravitacionais
+
+Ondas gravitacionais emitidas da fusão não podem ser calculadas usando nenhuma técnica a não ser relatividade numérica por força bruta usando supercomputadores. A quantidade de dados que o LIGO coleta é imensa tanto quanto os sinais de ondas gravitacionais são pequenos.
+
+NumPy, o pacote padrão de análise numérica para Python, foi parte do software utilizado para várias tarefas executadas durante o projeto de detecção de ondas gravitacionais no LIGO. A NumPy ajudou a resolver problemas matemáticos e de manipulação de dados complexos em alta velocidade. Aqui estão alguns exemplos:
+
+* [Processamento de sinais](https://www.uv.es/virgogroup/Denoising_ROF.html): Detecção de falhas, [Identificação de ruídos e caracterização de dados](https://ep2016.europython.eu/media/conference/slides/pyhton-in-gravitational-waves-research-communities.pdf) (NumPy, scikit-learn, scipy, matplotlib, pandas, PyCharm)
+* Recuperação de dados: Decidir quais dados podem ser analisados, compreender se os dados contém um sinal - como uma agulha em um palheiro
+* Análise estatística: estimar o significado estatístico dos dados observados, estimando os parâmetros do sinal (por exemplo, massa de estrelas, velocidade de giro e distância) em comparação com um modelo.
+* Visualização de dados
+ - Séries temporais
+ - Espectrogramas
+* Cálculo de correlações
+* [Software](https://github.com/lscsoft) fundamental desenvolvido na análise de ondas gravitacionais, como [GwPy](https://gwpy.github.io/docs/stable/overview.html) e [PyCBC](https://pycbc.org) usam NumPy e AstroPy internamente para fornecer interfaces baseadas em objetos para utilidades, ferramentas e métodos para o estudo de dados de detectores de ondas gravitacionais.
+
+{{< figure src="/images/content_images/cs/gwpy-numpy-dep-graph.png" class="fig-center" alt="gwpy-numpy depgraph" caption="**Grafo de dependências mostrando como o pacote GwPy depended da NumPy**" >}}
+
+----
+
+{{< figure src="/images/content_images/cs/PyCBC-numpy-dep-graph.png" class="fig-center" alt="PyCBC-numpy depgraph" caption="**Grafo de dependências mostrando como o pacote PyCBC depended da NumPy**" >}}
+
+## Resumo
+
+A detecção de ondas gravitacionais permitiu que pesquisadores descobrissem fenômenos totalmente inesperados ao mesmo tempo em que proporcionaram novas idéias sobre muitos dos fenômenos mais profundos conhecidos na astrofísica. O processamento e a visualização de dados é um passo crucial que ajuda cientistas a obter informações coletadas de observações científicas e a entender os resultados. Os cálculos são complexos e não podem ser compreendidos por humanos a não ser que sejam visualizados usando simulações de computador que são alimentadas com dados e análises reais observados. A NumPy, junto com outros pacotes Python, como matplotlib, pandas, e scikit-learn [permitem que pesquisadores](https://www.gw-openscience.org/events/GW150914/) respondam perguntas complexas e descubram novos horizontes em nossa compreensão do universo.
+
+{{< figure src="/images/content_images/cs/numpy_gw_benefits.png" class="fig-center" alt="numpy benefits" caption="**Recursos chave da NumPy utilizados**" >}}
From fcae610fb35130e69a23d764b88856deca753d32 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:37:26 +0000
Subject: [PATCH 061/909] New translations deeplabcut-dnn.md (Portuguese,
Brazilian)
---
content/pt/case-studies/deeplabcut-dnn.md | 90 +++++++++++++++++++++++
1 file changed, 90 insertions(+)
create mode 100644 content/pt/case-studies/deeplabcut-dnn.md
diff --git a/content/pt/case-studies/deeplabcut-dnn.md b/content/pt/case-studies/deeplabcut-dnn.md
new file mode 100644
index 0000000000..3d54a281e0
--- /dev/null
+++ b/content/pt/case-studies/deeplabcut-dnn.md
@@ -0,0 +1,90 @@
+---
+title: "Estudo de Caso: Estimativa de Pose 3D com DeepLabCut"
+sidebar: false
+---
+
+{{< figure src="/images/content_images/cs/mice-hand.gif" class="fig-center" caption="**Análise de movimentos de mãos de camundongos usando DeepLapCut**" alt="micehandanim" attr="*(Fonte: www.deeplabcut.org )*" attrlink="http://www.mousemotorlab.org/deeplabcut">}}
+
+
+
Software de código aberto está acelerando a Biomedicina. DeepLabCut permite a análise automática de vídeos de comportamento animal usando Deep Learning.
+
+
+
+## Sobre o DeepLabCut
+
+[DeepLabCut](https://github.com/DeepLabCut/DeepLabCut) é uma toolbox de código aberto que permite que pesquisadores de centenas de instituições em todo o mundo rastreiem o comportamento de animais de laboratório, com muito poucos dados de treinamento, mas com precisão no nível humano. Com a tecnologia DeepLabCut, cientistas podem aprofundar a compreensão científica do controle motor e do comportamento em diversas espécies animais e escalas temporais.
+
+Várias áreas de pesquisa, incluindo a neurociência, a medicina e a biomecânica, utilizam dados de rastreamento da movimentação de animais. A DeepLabCut ajuda a compreender o que os seres humanos e outros animais estão fazendo, analisando ações que foram registradas em vídeo. Ao usar automação para tarefas penosas de monitoramento e marcação, junto com análise de dados baseada em redes neurais profundas, a DeepLabCut garante que estudos científicos envolvendo a observação de animais como primatas, camundongos, peixes, moscas etc. sejam mais rápidos e mais precisos.
+
+{{< figure src="/images/content_images/cs/race-horse.gif" class="fig-center" caption="**Pontos coloridos rastreiam as posições das partes do corpo de um cavalo de corrida**" alt="horserideranim" attr="*(Fonte: Mackenzie Mathis)*">}}
+
+O rastreamento não invasivo dos animais pela DeepLabCut através da extração de poses é crucial para pesquisas científicas em domínios como a biomecânica, genética, etologia e neurociência. Medir as poses dos animais de maneira não invasiva através de vídeo - sem marcadores - com fundos dinamicamente variáveis é computacionalmente desafiador, tanto tecnicamente quanto em termos de recursos necessários e dados de treinamento exigidos.
+
+A DeepLabCut permite que pesquisadores façam estimativas de poses para os sujeitos, permitindo que se possa quantificar de maneira eficiente seus comportamentos através de um conjunto de ferramentas de software baseado em Python. Com a DeepLabCut, pesquisadores podem identificar quadros (*frames*) distintos em vídeos, rotular digitalmente partes específicas do corpo em alguns quadros com uma GUI específica, e a partir disso a arquitetura de estimação de poses baseada em deep learning na DeepLabCut aprende a selecionar essas mesmas características no resto do vídeo e em outros vídeos similares. A ferramenta funciona para várias espécies de animais, desde animais comuns em laboratórios como moscas e camundongos até os mais incomuns como [guepardos][cheetah-movement].
+
+A DeepLabCut usa um princípio chamado [aprendizado por transferência (*transfer learning*)](https://arxiv.org/pdf/1909.11229), o que reduz enormemente a quantidade de dados de treinamento necessários e acelera a convergência do período de treinamento. Dependendo das suas necessidades, usuários podem escolher diferentes arquiteturas de rede que forneçam inferência mais rápida (por exemplo, MobileNetV2), que também podem ser combinadas com feedback experimental em tempo real. A DeepLabCut usou originalmente os detectores de features de uma arquitetura de estimativa de poses humanas de alto desempenho, chamada [DeeperCut](https://arxiv.org/abs/1605.03170), que inspirou seu nome. O pacote agora foi significativamente alterado para incluir mais arquiteturas, métodos de ampliação e uma experiência de usuário completa no front-end. Além de possibilitar experiências biológicas em grande escala, DeepLabCut fornece capacidades ativas de aprendizado para que os usuários possam aumentar o conjunto de treinamento ao longo do tempo para incluir casos particulares e tornar seu algoritmo de estimativa de poses robusto no seu contexto específico.
+
+Recentemente, foi introduzido o [modelo DeepLabCut zoo](http://www.mousemotorlab.org/dlc-modelzoo), que proporciona modelos pré-treinados para várias espécies e condições experimentais, desde a análise facial em primatas até à posição de cães. Isso pode ser executado na nuvem, por exemplo, sem qualquer rotulagem de novos dados ou treinamento em rede neural, e não é necessária nenhuma experiência em programação.
+
+### Principais Objetivos e Resultados
+
+* **Automação da análise de poses animais para estudos científicos:**
+
+ O objetivo principal da tecnologia DeepLabCut é medir e rastrear a postura dos animais em várias configurações. Esses dados podem ser usados, por exemplo, em estudos de neurociência para entender como o cérebro controla o movimento, ou para elucidar como os animais interagem socialmente. Pesquisadores observaram que [desempenho é 10 vezes melhor](https://www.biorxiv.org/content/10.1101/457242v1) com o DeepLabCut. Poses podem ser inferidas off-line em até 1200 quadros por segundo (FPS).
+
+* **Criação de um kit de ferramentas Python fácil de usar para estimativa de poses:**
+
+ DeepLabCut queria compartilhar sua tecnologia de estimativa de poses animal na forma de uma ferramenta simples de usar que pudesse ser adotada pelos pesquisadores facilmente. Assim, criaram um conjunto de ferramentas em Python completo e fácil de usar, também com recursos de gerenciamento de projeto. Isso permite não apenas a automação de estimação de poses, mas também o gerenciamento do projeto de ponta a ponta, ajudando o usuário do DeepLabCut Toolkit desde a fase de coleta para criar fluxos de dados compartilháveis e reutilizáveis.
+
+ Seu [conjunto de ferramentas][DLCToolkit] agora está disponível como software de código aberto.
+
+ Um fluxo de trabalho típico na DeepLabCut inclui:
+
+ - criação e refinamento de conjuntos de treinamento por meio de aprendizagem ativa
+ - criação de redes neurais personalizadas para animais e cenários específicos
+ - código para inferência em larga escala em vídeos
+ - inferências de desenho usando ferramentas integradas de visualização
+
+{{< figure src="/images/content_images/cs/deeplabcut-toolkit-steps.png" class="csfigcaption" caption="**Passos na estimação de poses com DeepLabCut**" alt="dlcsteps" align="middle" attr="(Fonte: DeepLabCut)" attrlink="https://twitter.com/DeepLabCut/status/1198046918284210176/photo/1" >}}
+
+### Desafios
+
+* **Velocidade**
+
+ Processamento rápido de vídeos de animais para medir seu comportamento e, ao mesmo tempo, tornar os experimentos científicos mais eficientes e precisos. Extrair poses animais detalhadas para experimentos em laboratório, sem marcadores, sobre fundos dinâmicos, pode ser desafiador tanto tecnicamente quanto em termos de recursos e dados de treinamento necessários. Criar uma ferramenta que seja fácil de usar sem necessidade de habilidades como expertise em visão computacional que permita aos cientistas fazerem pesquisa em contextos mais próximos do mundo real é um problema não-trivial a ser solucionado.
+
+* **Combinatória**
+
+ Combinatória envolve a junção e integração de movimentos de múltiplos membros em um comportamento animal único. Reunir pontos-chave e suas conexões em movimentos animais individuais e encadeá-los em função do tempo é um processo complexo que exige análise numérica intensa, especialmente nos casos de rastreio de múltiplos animais em vídeos experimentais.
+
+* **Processamento de dados**
+
+ Por último, mas não menos importante, manipulação de matrizes - processar grandes conjuntos de matrizes correspondentes a várias imagens, tensores alvo e pontos-chave é bastante desafiador.
+
+{{< figure src="/images/content_images/cs/pose-estimation.png" class="csfigcaption" caption="**Estimação de poses e complexidade**" alt="challengesfig" align="middle" attr="(Fonte: Mackenzie Mathis)" attrlink="https://www.biorxiv.org/content/10.1101/476531v1.full.pdf" >}}
+
+## O papel da NumPy nos desafios da estimação de poses
+
+NumPy supre a principal necessidade da tecnologia DeepLabCut de cálculos numéricos de alta velocidade para análises comportamentais. Além da NumPy, DeepLabCut emprega várias bibliotecas Python que usam a NumPy como sua base, tais como [SciPy](https://www.scipy.org), [Pandas](https://pandas.pydata.org), [matplotlib](https://matplotlib.org), [Tensorpack](https://github.com/tensorpack/tensorpack), [imgaug](https://github.com/aleju/imgaug), [scikit-learn](https://scikit-learn.org/stable/), [scikit-image](https://scikit-image.org) e [Tensorflow](https://www.tensorflow.org).
+
+As seguintes características da NumPy desempenharam um papel fundamental para atender às necessidades de processamento de imagens, combinatória e cálculos rápidos nos algoritmos de estimação de pose na DeepLabCut:
+
+* Vetorização
+* Operações em arrays com máscaras
+* Álgebra linear
+* Amostragem aleatória
+* Reordenamento de matrizes grandes
+
+A DeepLabCut utiliza as capacidades de manipulação de arrays da NumPy em todo o fluxo de trabalho oferecido pelo seu conjunto de ferramentas. Em particular, a NumPy é usada para amostragem de quadros distintos para serem rotulados com anotações humanas e para escrita, edição e processamento de dados de anotação. Dentro da TensorFlow, a rede neural é treinada pela tecnologia DeepLabCut em milhares de iterações para prever as anotações verdadeiras dos quadros. Para este propósito, densidades de alvo (*scoremaps*) são criadas para colocar a estimativa como um problema de tradução de imagem a imagem. Para tornar as redes neurais robustas, o aumento de dados é empregado, o que requer o cálculo de scoremaps alvo sujeitos a várias etapas geométricas e de processamento de imagem. Para tornar o treinamento rápido, os recursos de vectorização da NumPy são utilizados. Para inferência, as previsões mais prováveis de scoremaps alvo precisam ser extraídas e é necessário "vincular previsões para montar animais individuais" de maneira eficiente.
+
+{{< figure src="/images/content_images/cs/deeplabcut-workflow.png" class="fig-center" caption="**Fluxo de dados DeepLabCut**" alt="workflow" attr="*(Fonte: Mackenzie Mathis)*" attrlink="https://www.researchgate.net/figure/DeepLabCut-work-flow-The-diagram-delineates-the-work-flow-as-well-as-the-directory-and_fig1_329185962">}}
+
+## Resumo
+
+Observação e descrição eficiente do comportamento é uma peça fundamental da etologia, neurociência, medicina e tecnologia modernas. [DeepLabCut](http://orga.cvss.cc/wp-content/uploads/2019/05/NathMathis2019.pdf) permite que os pesquisadores estimem a pose do sujeito, permitindo efetivamente que o seu comportamento seja quantificado. Com apenas um pequeno conjunto de imagens de treinamento, o conjunto de ferramentas em Python da DeepLabCut permite treinar uma rede neural tão precisa quanto a rotulagem humana, expandindo assim sua aplicação para não só análise de comportamento dentro do laboratório, mas também potencialmente em esportes, análise de locomoção, medicina e estudos sobre reabilitação. Desafios complexos em combinatória e processamento de dados enfrentados pelos algoritmos da DeepLabCut são tratados através do uso de recursos de manipulação de matriz do NumPy.
+
+{{< figure src="/images/content_images/cs/numpy_dlc_benefits.png" class="fig-center" alt="numpy benefits" caption="**Recursos chave do NumPy utilizados**" >}}
+
+[cheetah-movement]: https://www.technologynetworks.com/neuroscience/articles/interview-a-deeper-cut-into-behavior-with-mackenzie-mathis-327618
+
+[DLCToolkit]: https://github.com/DeepLabCut/DeepLabCut
From 29548871ccb40d93d09fb60466f05630e5b96b5b Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:37:28 +0000
Subject: [PATCH 062/909] New translations citing-numpy.md (Chinese Simplified)
---
content/zh/citing-numpy.md | 35 +++++++++++++++++++++++++++++++++++
1 file changed, 35 insertions(+)
create mode 100644 content/zh/citing-numpy.md
diff --git a/content/zh/citing-numpy.md b/content/zh/citing-numpy.md
new file mode 100644
index 0000000000..cf20ae59cf
--- /dev/null
+++ b/content/zh/citing-numpy.md
@@ -0,0 +1,35 @@
+---
+title: Citing NumPy
+sidebar: false
+---
+
+If NumPy has been significant in your research, and you would like to acknowledge the project in your academic publication, we suggest citing the following paper:
+
+* Harris, C.R., Millman, K.J., van der Walt, S.J. et al. _Array programming with NumPy_. Nature 585, 357–362 (2020). DOI: [0.1038/s41586-020-2649-2](https://doi.org/10.1038/s41586-020-2649-2). ([Publisher link](https://www.nature.com/articles/s41586-020-2649-2)).
+
+_In BibTeX format:_
+
+ ```
+@Article{ harris2020array,
+ title = {Array programming with {NumPy}},
+ author = {Charles R. Harris and K. Jarrod Millman and St{'{e}}fan J.
+ van der Walt and Ralf Gommers and Pauli Virtanen and David
+ Cournapeau and Eric Wieser and Julian Taylor and Sebastian
+ Berg and Nathaniel J. Smith and Robert Kern and Matti Picus
+ and Stephan Hoyer and Marten H. van Kerkwijk and Matthew
+ Brett and Allan Haldane and Jaime Fern{'{a}}ndez del
+ R{'{\i}}o and Mark Wiebe and Pearu Peterson and Pierre
+ G{'{e}}rard-Marchant and Kevin Sheppard and Tyler Reddy and
+ Warren Weckesser and Hameer Abbasi and Christoph Gohlke and
+ Travis E. Oliphant},
+ year = {2020},
+ month = sep,
+ journal = {Nature},
+ volume = {585},
+ number = {7825},
+ pages = {357--362},
+ doi = {10.1038/s41586-020-2649-2},
+ publisher = {Springer Science and Business Media {LLC}},
+ url = {https://doi.org/10.1038/s41586-020-2649-2}
+}
+```
From f8ed582920f8d5ccd83984d99911fcd91653c9cc Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:37:30 +0000
Subject: [PATCH 063/909] New translations about.md (Chinese Simplified)
---
content/zh/about.md | 69 +++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 69 insertions(+)
create mode 100644 content/zh/about.md
diff --git a/content/zh/about.md b/content/zh/about.md
new file mode 100644
index 0000000000..cccadd7da0
--- /dev/null
+++ b/content/zh/about.md
@@ -0,0 +1,69 @@
+---
+title: 关于我们
+sidebar: false
+---
+
+_下面是 NumPy 项目和社区的一些信息:_
+
+NumPy 是一个使 Python 支持数值计算的开源项目, 它诞生于 2005 年,早期由 Numerical 和 Numarray 库发展而来。 NumPy 将始终保证项目完整开源,所有人都可以根据 [修改后的 BSD 条款](https://github.com/numpy/numpy/blob/master/LICENSE.txt) 免费对其进行使用和分发。
+
+经过 Numpy 和 Python 科学计算社区协商讨论,最终决定将 Numpy 在 GitHub 上开源。 想要了解更多与社区治理有关的信息,请参阅我们的[治理文件](https://www.numpy.org/devdocs/dev/governance/index.html)。
+
+
+## 指导委员会
+
+指导委员会的成员们通过与 Numpy 社区合作并提供服务的形式来确保项目的长期发展,包括技术层面和社区层面。 Numpy 指导委员会目前由下列成员组成(按字母顺序排列):
+
+- Sebastian Berg
+- Jaime Fernández del Río
+- Ralf Gommers
+- Allan Haldane
+- Charles Harris
+- Stephan Hoyer
+- Matti Picus
+- Nathaniel Smith
+- Julian Taylor
+- Pauli Virtanen
+- Stéfan van der Walt
+- Eric Wieser
+
+荣誉会员:
+
+- Travis Oliphant(项目创始人,2005-2012年)
+- Alex Griffing(2015-2017年)
+- Marten van Kerkwijk (2017-2019年)
+
+## 团队
+
+NumPy 项目正在不断发展中,我们的团队成员负责:
+
+- 编码
+- 文档
+- 网站
+- 试用
+- 资金和赠款
+
+查看[团队](/gallery/team.html)页面以了解每个独立团队的成员信息。
+
+## 赞助商
+
+NumPy 直接从下列来源获得资金:
+{{< sponsors >}}
+
+
+## 机构合作伙伴
+
+机构合作伙伴指那些通过雇用为 NumPy 做贡献的人来支持该项目的组织。 目前的机构伙伴包括:
+{{< partners >}}
+
+
+## 捐赠
+
+如果您发现 NumPy 对您的工作、研究或公司有用,请考虑向该项目发起捐款。 任何金额都有帮助! 所有捐款将严格用于 NumPy 开源软件、文档和社区的开发。
+
+NumPy 是美国 501(c)(3) 非营利慈善机构 NumFOCUS 的一个赞助项目。 NumFOCUS 向 NumPy 提供财政、法律和行政支助,帮助确保该项目的健康和可持续性。 访问 [numfocus.org](https://numfocus.org) 获取更多信息。
+
+对 NumPy 的捐赠将由 [NumFOCUS](https://numfocus.org) 进行管理。 对于在美国的捐赠者,在法律规定的范围内,你的赠品可以免税。 如同任何捐赠一样,您应该与您的税务顾问商讨您的特定税务状况。
+
+NumPy 指导委员会将就如何最佳利用收到的任何资金作出决定。 技术和基础设施相关的优先事项已记录在 [NumPy 路线图](https://www.numpy.org/neps/index.html#roadmap) 上。
+{{< numfocus >}}
From 27758fa32a297384cd68eef750a8e7169fc65571 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:37:31 +0000
Subject: [PATCH 064/909] New translations community.md (Japanese)
---
content/ja/community.md | 65 +++++++++++++++++++++++++++++++++++++++++
1 file changed, 65 insertions(+)
create mode 100644 content/ja/community.md
diff --git a/content/ja/community.md b/content/ja/community.md
new file mode 100644
index 0000000000..5794d5626f
--- /dev/null
+++ b/content/ja/community.md
@@ -0,0 +1,65 @@
+---
+title: コミュニティ
+sidebar: false
+---
+
+Numpy は 常に多様な[コントリビュータ](/gallery/team.html) のグループによって開発されている、コミュニティ主導のオープンソースプロジェクトです。 Numpy を主導するグループは、オープンで協力的でポジティブなコミュニティを作ることを、約束しました。 コミュニティを繁栄させるために、コミュニティの人達と交流する方法については、 [NumPy 行動規範](/code-of-conduct) をご覧ください。
+
+私たちは、NumPyコミュニティ内で学んだり、知識を共有したり、他の人と交流するためのいくつかのコミュニケーション方法を提供しています。
+
+
+## オンラインで参加する方法
+
+Numpy プロジェクトやコミュニティと直接交流する方法は次の通りです。 _重要: 私達はユーザとコミュニティメンバーに互いにNumpyの使い方の質問に関して助言し合って欲しいと思っています。 - 参照[サポート](/gethelp)._
+
+
+### [NumPyメーリングリスト:](https://mail.python.org/mailman/listinfo/numpy-discussion)
+
+このメーリングリストは、Numpy に新しい機能を追加するなど、より長い期間の議論のための主なコミュニケーションの場です。 NumpyのRoadmapに変更を加えたり、プロジェクト全体での意思決定を行います。 このメーリングリストでは、リリース、開発者会議、スプリント、カンファレンストークなど、Numpy についてのアナウンスなどにも利用されます。
+
+このメーリングリストでは、一番下のメールを使用し、メーリングリストに返信して下さい( 他の送信者ではなく)。 また、自動送信のメールには返信しないでください。 このメーリングリストの検索可能なアーカイブは [こちら](http://numpy-discussion.10968.n7.nabble.com/) にあります。
+
+***
+
+### [GitHub イシュートラッカー](https://github.com/numpy/numpy/issues)
+
+- バグレポート(例:”`np.arange(3).shape` returns `(5,)`, when it should return `(3,)`");
+- ドキュメントの問題 (例: "I find this section unclear");
+- 機能追加リクエスト (例: "I would like to have a new interpolation method in `np.percentile`").
+
+_ちなみに、セキュリティの脆弱性を報告するには、GitHubのイシュートラッカーは適切な場所ではないことに注意してください。 NumPy でセキュリティ上の脆弱性を発見したと思われる場合は、 [こちら](https://tidelift.com/docs/security) から報告してください。_
+
+***
+
+### [Slack](https://numpy-team.slack.com)
+
+SlackはNumpyに_ 貢献するための質問をする_、リアルタイムのチャットルームです。 Slackはプライベートな空間です。具体的には、 公開のメーリングリストやGitHubで質問やアイデアを持ち出すことを躊躇している人々のためのものです。 Slackに招待してもらいたい場合は[こちら](https://numpy.org/devdocs/dev/index.html#contributing-to-numpy)を確認下さい。
+
+
+## 勉強会とミートアップ
+
+NumPyや、データサイエンス、科学技術計算などのより広いエコシステムのためのPythonパッケージついて、もっと学ぶためのローカルミートアップや勉強会を見つけたい場合、 [PyData ミートアップ](https://www.meetup.com/pro/pydata/) (150人以上のミートアップ、10万人以上のメンバーをまとめたもの) を調べてみることをお勧めします。
+
+加えて、NumPy では開発チームと参加に興味があるコントリビュータのために、対面でのスプリントを時折開催しています。 この開発スプリントは通常数ヶ月に一度に開催されており、 [ メーリングリスト ](https://mail. python. org/mailman/listinfo/numpy-discussion) と [ Twitter ](https://twitter. com/numpy_team) で開催連絡されます。
+
+
+## カンファレンス
+
+Numpy プロジェクトは独自のカンファレンスは開催していません。 NumPy の管理者や、コントリビュータ、ユーザーに最も人気があったカンファレンスは、SciPy および PyDataのカンファレンスです。
+
+- [SciPy US](https://conference.scipy.org)
+- [EuroSciPy](https://www.euroscipy.org)
+- [SciPy Latin America](https://www.scipyla.org)
+- [SciPy India](https://scipy.in)
+- [SciPy Japan](https://conference.scipy.org)
+- [PyData conference](https://pydata.org/event-schedule/) (年に15~20のイベントが様々な国で開催されています。)
+
+これらのカンファレンスの多くは、Numpyの使い方や関連するオープンソースプロジェクトに貢献する方法を学ぶことができるチュートリアルを開催しています。
+
+
+## NumPy コミュニティに参加する
+
+Numpyプロジェクトを成功させるには、あなたの専門知識とプロジェクトに関する熱意が必要です。 プログラマーじゃないから参加できない? そんなことはありません! Numpy に貢献する様々な方法があります。
+
+もし、Numpyに貢献したい場合は、 [コントリビュート](/contribute) ページをご覧いただくことをお勧めします。
+
From 91310e36dcdbd83a6eeec36c3630df90f354a759 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:37:33 +0000
Subject: [PATCH 065/909] New translations gethelp.md (Spanish)
---
content/es/gethelp.md | 34 ++++++++++++++++++++++++++++++++++
1 file changed, 34 insertions(+)
create mode 100644 content/es/gethelp.md
diff --git a/content/es/gethelp.md b/content/es/gethelp.md
new file mode 100644
index 0000000000..a427b5b1f5
--- /dev/null
+++ b/content/es/gethelp.md
@@ -0,0 +1,34 @@
+---
+title: Get Help
+sidebar: false
+---
+
+**User questions:** The best way to get help is to post your question to a site like [StackOverflow](http://stackoverflow.com/questions/tagged/numpy), with thousands of users available to answer. Smaller alternatives include [IRC](https://webchat.freenode.net/?channels=%23numpy), [Gitter](https://gitter.im/numpy/numpy), and [Reddit](https://www.reddit.com/r/Numpy/). We wish we could keep an eye on these sites, or answer questions directly, but the volume is just a little overwhelming!
+
+**Development issues:** For NumPy development-related matters (e.g. bug reports), please see [Community](/community).
+
+
+
+### [StackOverflow](http://stackoverflow.com/questions/tagged/numpy)
+
+A forum for asking usage questions, e.g. "How do I do X in NumPy?”. Please [use the `#numpy` tag](https://stackoverflow.com/help/tagging)
+
+***
+
+### [Reddit](https://www.reddit.com/r/Numpy/)
+
+Another forum for usage questions.
+
+***
+
+### [Gitter](https://gitter.im/numpy/numpy)
+
+A real-time chat room where users and community members help each other.
+
+***
+
+### [IRC](https://webchat.freenode.net/?channels=%23numpy)
+
+Another real-time chat room where users and community members help each other.
+
+***
From ca92e9d6a74bf63381548f6c1929812336722ec7 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:37:35 +0000
Subject: [PATCH 066/909] New translations install.md (Japanese)
---
content/ja/install.md | 166 ++++++++++++++++++++++++++++++++++++++++++
1 file changed, 166 insertions(+)
create mode 100644 content/ja/install.md
diff --git a/content/ja/install.md b/content/ja/install.md
new file mode 100644
index 0000000000..61f58002df
--- /dev/null
+++ b/content/ja/install.md
@@ -0,0 +1,166 @@
+---
+title: Numpyのインストール
+sidebar: false
+---
+
+Numpy をインストールするための必ず必要なものはPython本体です。 もしまだPythonをインストールしていないのであれば、最もシルプルな始め方として、こちらがあります: [Anaconda Distribution](https://www.anaconda.com/distribution)。このanacondaはPythonだけでなく、NumPyや、その他科学技術計算やデータサイエンスのために一般的に使用される沢山のパッケージが含まれています。
+
+NumPyは`conda`や`pip` 、Mac OSやLinuxのパッケージマネージャー、または [ソースコード](https://numpy.org/devdocs/user/building.html)からインストールすることが出来ます。 詳細な手順については、以下の [Python と Numpyの インストールガイド](#python-numpy-install-guide) を参照してください。
+
+**CONDA**
+
+`conda`を使用する場合、 `defaults` または `conda-forge` のチャンネルから NumPy をインストールできます。
+
+```bash
+# Best practice, use an environment rather than install in the base env
+conda create -n my-env
+conda activate my-env
+# If you want to install from conda-forge
+conda config --env --add channels conda-forge
+# The actual install command
+conda install numpy
+```
+
+**PIP**
+
+`pip`を使用している場合は、 NumPy を以下のようにインストールできます:
+
+```bash
+pip install numpy
+```
+またpipを使う場合、仮想環境を使うことをおすすめします - 参考 [再現可能なインストール](#reproducible-installs) 。 [こちらの記事](https://dev.to/bowmanjd/python-tools-for-managing-virtual-environments-3bko#howto)では仮想環境を使う詳細について説明されています。
+
+
+
+# Python と Numpy インストールガイド
+
+Pythonパッケージのインストールと管理は複雑なで、ほとんどのタスクには数多くの代替ツールがあります。 このガイドでは、読者に最適な(または最も人気のある) 方法と明確な指針を提供したいと思います。 このガイドでは、一般的なオペレーティングシステムとハードウェア上での、 Python、NumPy、PyData (または数値計算) スタックのユーザに焦点を当てています。
+
+## 推奨方法
+
+まずはユーザの経験のレベルと、関心のあるOSに基づいた推奨方法から説明していきたいと思います。 PythonやNumpyの経験が「初級」と「上級」の間の方や、シンプルにインストールしたい方は「初級」を、より長い視点にたったベストプラクティスに沿ってインストールしたい方は「上級」を参照下さい。
+
+### 初級ユーザ
+
+Windows、macOS、Linuxのすべてのユーザー向けには:
+
+- [Anaconda](https://www.anaconda.com/distribution/) をインストールします(必要な パッケージと以下に挙げるすべてのツールがインストールされます)。
+- コードを書いたり、実行するために[JupyterLab](https://jupyterlab.readthedocs.io/en/stable/index.html) でnotebookを利用することができます。また探索的、対話的コンピューティングも可能です。[Spyder](https://www.spyder-ide.org/) 、[Visual Studio Code](https://code.visualstudio.com/)はスクリプトを作成したり、パッケージを作成することができます。
+- 是非、[Anaconda Navigator](https://docs.anaconda.com/anaconda/navigator/) を使用して パッケージを管理し、JupyterLab、Spyder、Visual Studio Code を利用してみて下さい。
+
+
+### 上級ユーザー
+
+#### WindowsまたはmacOS
+
+- [Miniconda](https://docs.conda.io/en/latest/miniconda.html) をインストールします。
+- `ベース` のconda環境を出来るだけ小さく保ちます。 そして、作業中のタスクやプロジェクトに必要なパッケージは個別の` ` [conda 環境](https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#) を使用して、インストールするようにします。
+- もし、あなたの必要なパッケージが`defaults` チャンネルだけで足りない場合は、`conda-forge` こちらの [チャンネルプライオリティの設定](https://conda-forge.org/docs/user/introduction.html#how-can-i-install-packages-from-conda-forge)でデフォルトチャンネルを設定することができます。
+
+
+#### Linux
+
+もしあなたが最新バージョンのライブラリを使用するよりも、少し古いパッケージで安定性を求める場合は:
+- 可能な限りOS付帯のパッケージマネージャーを使用してください (Python本体やNumPy、 その他のライブラリのインストールに)。
+- `pip install somepackage --user` でパッケージマネージャによって提供されていないパッケージをインストールすることができます。
+
+GPUを使用する場合:
+- [Miniconda](https://docs.conda.io/en/latest/miniconda.html) をインストールして下さい。
+- `ベース` のconda環境を出来るだけ小さく保ちます。 そして、作業中のタスクやプロジェクトに必要なパッケージは個別の` ` [conda 環境](https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#) を使用して、インストールするようにします。
+- また、`デフォルトの` conda channel (`conda-forge` は GPU パッケージをまだサポートしていません) を使用してください。
+
+上記以外の場合
+- [Miniforge](https://github.com/conda-forge/miniforge) をインストールします。
+- `ベース` のconda環境を出来るだけ小さく保ちます。 そして、作業中のタスクやプロジェクトに必要なパッケージは個別の` ` [conda 環境](https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#) を使用して、インストールするようにします。
+
+
+#### pip/PyPI を利用したい場合
+
+個人的な好みや、下記のcondaとpipの違いを理解した上で、pip/PyPIベースの方法を使いたいユーザーには、下記をお勧めします:
+- Pythonをインストールします。例えば、 [python.org](https://www.python.org/downloads/), [Homebrew](https://brew.sh/), または Linux パッケージマネージャを使うことができます。
+- 依存関係の解決と環境の管理を提供する最もよくメンテナンスされているツールとして、[Poetry](https://python-poetry. org/) をconda と同様な方法で使用することができます。
+
+
+## Python パッケージ管理
+
+パッケージの管理は難しいので、その結果、たくさんのツールが存在しています。 ウェブ開発と汎用的なPython開発には、こちらのようなpipを補完する [ツール](https://packaging.python.org/guides/tool-recommendations/) があります。 ハイパフォーマンスコンピューティング(HPC)では、 [Spack](https://github.com/spack/spack) を使うことを検討して下さい。 NumPyのほとんどのユーザーにとっては、 [conda](https://conda.io/en/latest/) と [pip](https://pip.pypa.io/en/stable/) が最も広く利用されているツールです。
+
+
+### Pip & conda
+
+Python パッケージをインストールするための2 つの主要なツールは `pip` と `conda` です。 これらの二つのツールの機能は部分的に重複しますが(例えば、両方とも `numpy`をインストールできます)、これらは一緒に動作することもできます。 ここでは、pip とconda の主要な違いについて説明します。パッケージをどのように効果的に管理するかを理解することが重要です。
+
+最初の違いは、condaは複数言語に対応可能であり、condaからPythonをインストールできることです。pip はシステム上の特定の Python にインストールされ、パッケージはそのPythonにのみインストールします。 また、condaはPython 以外のライブラリや必要なツール (コンパイラ、CUDA、HDF5など) をインストールできますが、pip はできません。
+
+2つ目の違いは、pipはPython Packaging Index(PyPI) からパッケージをインストールするのに対し、condaは独自のチャンネル(一般的には "defaults "や "conda-forge "など) からインストールすることです。 PyPIは、最大のパッケージ管理システムですが、すべての代表的なパッケージは、condaにも利用可能です。
+
+3つ目の違いは、condaはパッケージ、依存関係、環境を管理するための統合されたソリューションであるのに対し、pipでは環境や複雑な依存関係を扱うために別のツール(たくさん存在しています!) が必要になるかもしれないということです。
+
+
+### 再現可能なインストール
+
+ライブラリが更新されると、コードの実行結果が変わったり、コードが壊れたりする可能性があります。 なので重要なことは、使用しているパッケージの組み合わせと各バージョンのセットを再構築できるようにしておくことです。 ベストプラクティスは次の通りです:
+
+1. プロジェクトごとに異なる仮想環境を使用してください。
+2. パッケージインストーラを使用してパッケージ名とバージョンを記録するようにします( それぞれに独自のメタデータフォーマットがあります)。
+ - Condaの場合: [conda environments, environment.yml](https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#)
+ - pipの場合: [仮想環境](https://docs.python.org/3/tutorial/venv.html) と [requirements.txt](https://pip.readthedocs.io/en/latest/user_guide/#requirements-files)
+ - Poetryの場合: [仮想環境と pyproject.toml](https://python-poetry.org/docs/basic-usage/)
+
+
+
+## Numpyパッケージ & 高速線形代数ライブラリ
+
+Numpy は他の Python パッケージに依存していませんが、高速な線形代数ライブラリ - 一般的には、 [インテル® MKL](https://software.intel.com/en-us/mkl) または [OpenBLAS](https://www.openblas.net/) に依存しています。 ユーザーはこれらの線形代数ライブラリのインストールを心配する必要はありません (Numpy install メソッドが自動的に実施します)。 パワーユーザーの中には、使用されているBLASがパフォーマンスや、動作、ディスク上のサイズに影響を与えるため、より詳細を知りたいと思っているかもしれません。
+
+- pipでインストールされる、PyPI 上の Numpy wheelは、OpenBLASを使ってビルドされます。 つまりwheelにはOpenBLASライブラリが含まれています。 これにより、ユーザが(例えば)SciPyをインストールした場合、ディスク上にOpenBLASのコピーをNumpyのものと、2つ持つことになります
+
+- Condaのデフォルトチャンネルでは、Numpy はインテル® MKLを使ってビルドされます。 MKL はNumpy をインストールしたときにユーザーの環境にインストールされるのとは、別のパッケージです。
+
+- conda-forgeのチャンネルでは、Numpyはダミーの「BLAS」パッケージを使ってビルドされています。 ユーザーがconda-forgeからNumPyをインストールすると、BLASパッケージが実際のライブラリと一緒にインストールされます - デフォルトはOpenBLASですが、MKL(default チャンネルの場合)やBLIS、またはBLASを利用することもできます。
IMPORTANT: PLEASE READ THIS FOR ADVICE ON HOW TO SOLVE THIS ISSUE!
+
+Importing the numpy c-extensions failed. This error can happen for different reasons, often due to issues with your setup.
+
+
From 7738066fe05d20790260442b0fb66919ee380976 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:37:37 +0000
Subject: [PATCH 067/909] New translations code-of-conduct.md (Japanese)
---
content/ja/code-of-conduct.md | 83 +++++++++++++++++++++++++++++++++++
1 file changed, 83 insertions(+)
create mode 100644 content/ja/code-of-conduct.md
diff --git a/content/ja/code-of-conduct.md b/content/ja/code-of-conduct.md
new file mode 100644
index 0000000000..10853e5152
--- /dev/null
+++ b/content/ja/code-of-conduct.md
@@ -0,0 +1,83 @@
+---
+title: Numpy行動規範
+sidebar: false
+aliases:
+ - /conduct.html
+---
+
+### はじめに
+
+この行動規範は、NumPy プロジェクトによって管理されるすべての場所で適用されます。この場所とは、すべてのパブリックおよびプライベートのメーリングリスト、イシュートラッカー、Wiki、ブログ、Twitter、コミュニティで使用されているその他の通信チャンネルなどを含みます。 Numpy プロジェクトでは対面でのイベントは開催していません。しかし、我々のコミュニティでは、対面でもイベント同様の行動規範を持つ必要があります。
+
+この行動規範は、NumPy コミュニティに正式または非公式に参加するすべての人が順守する必要があります。その他にも、Numpyとの提携、関連するプロジェクト活動、特にそれらのプロジェクトを運営する場合、同様の行動規範に従う必要があります。
+
+この行動規範は完全ではありません。 しかし、行動規範は我々が理解すべき、互いの協力の仕方や、共通の場所のあるべき姿、我々のゴールなどをまとめるのに重要な役目を果たします。 是非、我々のコミュニティをより豊かにし、フレンドリーで生産的な環境を作るために、この行動規範に従ってください。
+
+### ガイドラインの概要
+
+私たちは下記の内容に真摯に取り組みます。
+
+1. 開けたコミュニティにしましょう。 私たちは、誰でもコミュニティに参加できるようにします。 私たちは、何かあまり公にすべきではない内容を議論しない限り、プロジェクト関連のメッセージにはパブリックな通信方法を使用するように努めます。 この行動規範はNumpyのヘルプやプロジェクト関連のサポートのメッセージにも適用されます。パブリックなサポートだけでなく、Numpyに関する質問に答える場合もこの行動規範に従うことがひです。 これにより、質問に答えた時の、無意識な間違いを、より簡単に検出し、訂正できるようになります。
+2. 共感し、歓迎し、友好的で、そして我慢強くありましょう。 私たちはお互いの意見の尊重しあい、互いの善意を信じ合います。 私達はたまに様々な種類の不満を感じるかもしれません。しかしそんな時でも、私達はそのような不満を個人的な攻撃に変えるのを許しません。 なぜなら人々が不快や脅威を感じるコミュニティは、生産的な場所ではないからです。
+3. 互いに協力し合おう。 私たちが開発したものは、他の人々によって使用され、一方で、私たちは他の人が開発しているものに依存しているのです。 私たちがプロジェクトために何かを作るとき、私たちはそれがどのように動作するかを他の人に説明する必要があります。しかし、この作業により、より良いものを作り上げることができるのです。 私達が実施する全ての決断は、全てのユーザと開発コミュニティに影響を与え、その決断による結果を私達は真摯に受け止めます。
+4. 好奇心を大事にしよう。 全てのことを理解している人は存在しません。 早め早めに質問を行うことは、後で多くの問題を回避することができます。なので私達は、それぞれの質問に対して、適切なフォーラムに案内することで、質問を奨励していきます。 私たちは、出来るだけ質問に対する対応を良くし、手助けできるように努力します。
+5. 使う言葉に注意しましょう。 私たちは、コミュニティにおけるコミュニケーションに注意と敬意を払います。そして、私たちは自分の言葉に責任を持つようにします。 他人に優しくしましょう。 他のコミュニティの参加者を侮辱しないでください。 私たちは、以下のようなハラスメントやその他の排斥行為を許しません。:
+ * 他の人に向けられた暴力的な行為や言葉。
+ * 性差別や人種差別、その他の差別的なジョークや言動。
+ * 性的または暴力的な内容の投稿。
+ * 他のユーザーの個人情報を投稿すること。(または投稿すると脅すこと)。
+ * 公開目的のない電子メールや、非公開フォーラム上でものIRCチャネル履歴などのプライベートコンテンツを、送信者の同意なしに共有すること。
+ * 個人的な侮辱, 特に人種差別や性差別的な用語を使用して侮辱すること。
+ * 不快な思いをさせる性的な言動。
+ * 過度に粗暴に振る舞うこと。 ひどいな言葉を使うのを避けてください。 人々は怒りを覚える感度が、それぞれ大きく異なります。
+ * 他人に対するハラスメントの繰り返し。 一般的に、誰かがあなたにある言動を止めるように要求した場合、その言動をやめて下さい。
+ * 上記のいずれかの行動を擁護すること、または奨励すること。
+
+### 多様性に関する声明
+
+NumPyプロジェクトは、全ての人の参加を歓迎しています。 私たちは、誰もがコミュニティの一員であることを楽しめるように力を注いでいます。 全ての人が満足できるように対応できるとは限りませんが、全員を出来るだけ親切に扱えるように最善を尽くしていきます。
+
+あなたがどのようにあなた自身を認識し、他の人があなたをどのように認識していても、私達 はあなたのプロジェクトへの参加を歓迎します。 下記のリストが全てを含んでいるとは言えませんが、私達は行動規範に反しない限り、下記の多様性を尊重することを明言します。: 年齢、文化。 民族、遺伝、性同一性あるいは関連する表現、言語、国籍、神経学的な差異、生物学的な差異、 政治的信条、職業、人種、宗教、性的指向、社会経済的地位、文化的な差異、技術的な能力。
+
+私たちはすべての種類の言語言語話者の参加を歓迎しますが、Numpy 開発は英語で実施します。
+
+NumPy コミュニティの標準的なルールは、上記の行動規範で説明されています。 我々のコミュニティの参加者は、これらの行動基準をすべてのコミュニケーションにおいて順守し、他の人々にも同様な行動をすることを推奨すべきです。(次のセクションを参照)。
+
+### 報告ガイドライン
+
+私たちは、インターネットでの会話が簡単にひどい誹謗中傷になってしまうことを、痛いほど知っています. また、この行動規範のガイドラインにそのような行為が禁止されていることに気づいていない人もいることを認識しています。 行動規範の違反に対応する方法を決定する際には、この事実を覚心に留めておく必要があります。
+
+意図的な行動規範違反については、行動規範委員会に報告してください(下記参照)。 もし、ある行動規範違反が意図的ではない可能性がある場合、あなたはその人にこの行動規範が存在していることを指摘することができます(方法としてはパブリックな方法でもプライベートな方法に、適切な方法であればはどの様な方法でも可能です。)。 もし、直接指摘するのが躊躇われる場合は、是非、行動規範委員会に連絡下さい。 委員会に助言を求めることもできます。
+
+Numpy行動規範委員会に問題を報告する場合はこちらにご連絡下さい: numpy-conduct@googlegroups.com
+
+現在、行動規範委員会は以下のメンバーで構成されています:
+
+* Stefan van der Walt
+* Melissa Weber Mendonça
+* Anirudh Subramanian
+
+もしあなたの違反報告に委員会のメンバーが含まれている場合, または彼らがそれを処理する上で利益相反をしていると感じる場合、そのメンバーはあなたの報告を評価する立場からは辞退してもらいます。 または、もしあなたが行動規範委員会に報告するのが躊躇われるばあい、こちらのNumFOCUSのスタッフに連絡することも可能です。:[conduct@numfocus.org](https://numfocus.org/code-of-conduct#persons-responsible).
+
+### インシデント報告の解決 & 行動規範の実施
+
+本節では、_最も重要な点のみをまとめます。_詳細については、[Numpy Code of Conduct - How to follow up on a report](/report-handling-manual) をご覧ください。
+
+私たちはすべての訴えを調査し、対応するようにします。 NumPy行動規範委員会およびNumPy運営委員会(もし関係する場合) は、報告者の身元を保護します。 また(報告者が同意しない限り) 苦情の内容を機密として扱うこととします。
+
+もし深刻で明らかな違反の場合、例えば、 個人的な脅し、または暴力的、性差別的または人種差別的な発言などの場合、我々は直ちにNumPyのコミュニケーションの場から発言者を退場させます。詳細についてはマニュアルを参照してください。
+
+もし、行動規範に対して明白な違反がみられない場合、受領された行動規範違反報告に対するプロセスは以下の通りです。
+
+1. 報告書の受領を確認
+2. 建設的な議論/フィードバック
+3. 調停(報告者と報告を受けたものの両方がフィードバックが役に立たなかったと同意した場合に限る)
+4. 行動規範委員会による透明性のある決定と執行( [決議](/report-handling-manual#resolutions)を参照)
+
+行動規範委員会は、可能な限り速やかに対応し、最大で72時間以内に対応する様にします。
+
+### 文末脚注:
+
+私たちは下記のドキュメントの作成したグループに感謝しています。このドキュメントから私たちは我々の行動規範の内容と発想を得ることが出来ました。
+
+- [SciPy行動規範](https://docs.scipy.org/doc/scipy/reference/dev/conduct/code_of_conduct.html)
From 60934d1d3a1d261004749495d434c7fe82de8dac Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:37:38 +0000
Subject: [PATCH 068/909] New translations citing-numpy.md (Japanese)
---
content/ja/citing-numpy.md | 35 +++++++++++++++++++++++++++++++++++
1 file changed, 35 insertions(+)
create mode 100644 content/ja/citing-numpy.md
diff --git a/content/ja/citing-numpy.md b/content/ja/citing-numpy.md
new file mode 100644
index 0000000000..1aa50fa270
--- /dev/null
+++ b/content/ja/citing-numpy.md
@@ -0,0 +1,35 @@
+---
+title: NumPy を引用する場合
+sidebar: false
+---
+
+もしあなたの研究においてNumpyが重要な役割を果たし、論文でこのプロジェクトについて言及したい場合は、こちらの論文を引用して下さい。
+
+* Harris, C.R., Millman, K.J., van der Walt, S.J. et al. _Array programming with NumPy_. Nature 585, 357–362 (2020). DOI: [0.1038/s41586-020-2649-2](https://doi. org/10.1038/s41586-020-2649-2). ([リンク](https://www.nature.com/articles/s41586-020-2649-2)).
+
+_BibTeX形式:_
+
+ ```
+@Article{ harris2020array,
+ title = {Array programming with {NumPy}},
+ author = {Charles R. Harris and K. Jarrod Millman and St{'{e}}fan J.
+ van der Walt and Ralf Gommers and Pauli Virtanen and David
+ Cournapeau and Eric Wieser and Julian Taylor and Sebastian
+ Berg and Nathaniel J. Smith and Robert Kern and Matti Picus
+ and Stephan Hoyer and Marten H. van Kerkwijk and Matthew
+ Brett and Allan Haldane and Jaime Fern{'{a}}ndez del
+ R{'{\i}}o and Mark Wiebe and Pearu Peterson and Pierre
+ G{'{e}}rard-Marchant and Kevin Sheppard and Tyler Reddy and
+ Warren Weckesser and Hameer Abbasi and Christoph Gohlke and
+ Travis E. Oliphant},
+ year = {2020},
+ month = sep,
+ journal = {Nature},
+ volume = {585},
+ number = {7825},
+ pages = {357--362},
+ doi = {10.1038/s41586-020-2649-2},
+ publisher = {Springer Science and Business Media {LLC}},
+ url = {https://doi.org/10.1038/s41586-020-2649-2}
+}
+```
From 826e8287b340139473b107366d15147f85e012bb Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:37:40 +0000
Subject: [PATCH 069/909] New translations arraycomputing.md (Japanese)
---
content/ja/arraycomputing.md | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
create mode 100644 content/ja/arraycomputing.md
diff --git a/content/ja/arraycomputing.md b/content/ja/arraycomputing.md
new file mode 100644
index 0000000000..214d01e34e
--- /dev/null
+++ b/content/ja/arraycomputing.md
@@ -0,0 +1,21 @@
+---
+title: 配列演算
+sidebar: false
+---
+
+*配列演算は統計、数学、科学計算の基礎です。可視化、信号処理、画像処理、生命情報学、機械学習、人工知能など、現代のデータサイエンスやデータ分析の様々な分野でも配列演算は中核を担っています。*
+
+大規模なデータ処理やデータ変換には、効率的な配列演算が重要です。 データ分析や、機械学習、効率的な数値計算に最適な言語のひとつは **Python** です。
+
+**Num**erical **Py**thon: NumPyは、大規模な多次元配列や行列、そして、それらの配列を処理する様々な分野の数学ルーチンをサポートする、Pythonにおけるデファクトスタンダードなライブラリです。
+
+2006年にNumpyが発表されてから、2008年にPandasが登場し、その後、数年間にいくつかの配列演算関連のライブラリが次々と現れるようになりました。そこから配列演算界隈は盛り上がり始めました。 これらの新しい配列演算ライブラリの多くは、Numpy 似た機能を模倣しており、機械学習や人工知能に適した、新しいアルゴリズムや機能を有しています。
+
+
+
+**配列演算** は **配列** のデータ構造に基づいています。 *配列* は、関連する膨大なデータ群を簡単にかつ高速に、ソート、検索、変換、数学処理できるように構成されています。
+
+配列演算は *一度に* 配列のデータの複数の要素を操作するため、 * ユニーク* な処理と言えます。 これは、配列操作が一回の処理で、配列内の 値の全体に適用されることを意味しています。 このベクトル演算は、高速で、シンプルな処理を実現し、ループによる配列の個々の要素のスカラー演算無しに、データを処理することを可能にします。
From 5fea0fa4e99507694fe8c95a0c41b5e5d66c495f Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:37:41 +0000
Subject: [PATCH 070/909] New translations about.md (Japanese)
---
content/ja/about.md | 69 +++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 69 insertions(+)
create mode 100644 content/ja/about.md
diff --git a/content/ja/about.md b/content/ja/about.md
new file mode 100644
index 0000000000..e13172f599
--- /dev/null
+++ b/content/ja/about.md
@@ -0,0 +1,69 @@
+---
+title: Numpyプロジェクトについて
+sidebar: false
+---
+
+_このページでは、NumPyのプロジェクトとそれを支えるコミュニティについて説明します。_
+
+Numpy は Python を使った数値計算のためのオープンソースプロジェクトです。 Numpyは、Numerical and Numarrayライブラリの初期のコードを基に、2005年から開発がスタートしました。 NumPyは開発当初から100%オープンソースソフトウェアとして開発されてきました。[修正BSD ライセンス](https://github.com/numpy/numpy/blob/master/LICENSE.txt) の条項の下で、すべての人が利用可能です。
+
+Numpy は 、様々な科学Python コミュニティとのコンセンサスを得ながら、GitHub 上でオープンに開発されています。 Numpyのガバナンス方法の詳細については、 [Governance Document](https://www.numpy.org/devdocs/dev/governance/index.html) をご覧ください。
+
+
+## 運営委員会
+
+Numpy運営委員会の役割は、Numpyのコミュニティと協力しサポートすることを通じて、技術的にもコミュニティ的にも長期的にNumpyプロジェクトを良い状態に保つことです。 Numpy運営委員会は現在以下のメンバーで構成されています (アルファベット順):
+
+- Sebastian Berg
+- Jaime Fernández del Río
+- Ralf Gommers
+- Allan Haldane
+- Charles Harris
+- Stephan Hoyer
+- Matti Picus
+- Nathaniel Smith
+- Julian Taylor
+- Pauli Virtanen
+- Stéfan van der Walt
+- Eric Wieser
+
+終身名誉委員
+
+- Travis Oliphant (プロジェクト創設者, 2005-2012)
+- Alex Griffing (2015-2017)
+- Marten van Kerkwijk (2017-2019)
+
+## チーム
+
+Numpy プロジェクトは拡大しているため、いくつかのチームが設置されています。
+
+- コード
+- ドキュメント
+- ウェブサイト
+- トリアージ
+- 資金と助成金
+
+個々のチームメンバーについては、 [チーム](/gallery/team.html) のページを参照してください。
+
+## スポンサー情報
+
+Numpyは以下の団体から直接資金援助を受けています。
+{{< sponsors >}}
+
+
+## パートナー団体
+
+パートナー団体は、Numpyへの開発を仕事の一つとして、社員を雇っている団体です。 現在のパートナー団体としては、下記の通りです。
+{{< partner >}}
+
+
+## 寄付
+
+NumPy があなたの仕事や研究、ビジネスで役に立った場合、できる範囲で良いので、是非、Numpyプロジェクトへの寄付を検討して頂けると助かります。 少額の寄付でも大きな助けになります。 すべての寄付は、NumPyのオープンソースソフトウェア、ドキュメント、コミュニティの開発のために使用されることが約束されています。
+
+Numpy は NumFOCUS にスポンサーされたプロジェクトであり、米国の 501(c)(3) 非営利の慈善団体でもあります。 NumFOCUSは、Numpyプロジェクトに財政、法務、管理面でのサポートを提供し、プロジェクトの安定と持続可能性を保つ手助けをしています。 詳細については、 [numfocus.org](https://numfocus.org) をご覧ください。
+
+Numpy への寄付は [NumFOCUS](https://numfocus.org) によって管理されています。 米国の寄付提供者の場合、その人の寄付は法律によって定められる範囲で免税されます。 但し、他の寄付と同様に、あなたはあなたの税務状況について、あなたの税務担当と相談する必要があることを忘れないで下さい。
+
+Numpyの運営委員会は、受け取った資金をどのように使えば良いかを検討し、使用する方法について決定します. Numpyに関する技術とインフラの投資の優先順位に関しては、[Numpy Roadmap](https://www.numpy.org/neps/index.html#roadmap) に記載されています。
+{{< numfocus >}}
From 13c060f0b0648a129ae1403a12069ab3383a3013 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:37:43 +0000
Subject: [PATCH 071/909] New translations 404.md (Japanese)
---
content/ja/404.md | 8 ++++++++
1 file changed, 8 insertions(+)
create mode 100644 content/ja/404.md
diff --git a/content/ja/404.md b/content/ja/404.md
new file mode 100644
index 0000000000..8e4db85255
--- /dev/null
+++ b/content/ja/404.md
@@ -0,0 +1,8 @@
+---
+title: 404
+sidebar: false
+---
+
+おっとっと! 間違った所にアクセスしているようです。
+
+何かがここにページがあるべきだと思ったら、GitHub で [issue](https://github.com/numpy/numpy.org/issues) を作成してください。
From a9e4e11af7544c03fdebfaa171cf588e7962d94f Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:37:44 +0000
Subject: [PATCH 072/909] New translations diversity_sep2020.md (Spanish)
---
content/es/diversity_sep2020.md | 48 +++++++++++++++++++++++++++++++++
1 file changed, 48 insertions(+)
create mode 100644 content/es/diversity_sep2020.md
diff --git a/content/es/diversity_sep2020.md b/content/es/diversity_sep2020.md
new file mode 100644
index 0000000000..ef3030d5f7
--- /dev/null
+++ b/content/es/diversity_sep2020.md
@@ -0,0 +1,48 @@
+---
+title: NumPy Diversity and Inclusion Statement
+sidebar: false
+---
+
+
+_In light of the foregoing discussion on social media after publication of the NumPy paper in Nature and the concerns raised about the state of diversity and inclusion on the NumPy team, we would like to issue the following statement:_
+
+
+It is our strong belief that we are at our best, as a team and community, when we are inclusive and equitable. Being an international team from the onset, we recognize the value of collaborating with individuals from diverse backgrounds and expertise. A culture where everyone is welcomed, supported, and valued is at the core of the NumPy project.
+
+## The Past
+
+Contributing to open source has always been a pastime in which most historically marginalized groups, especially women, faced more obstacles to participate due to a number of societal constraints and expectations. Open source has a severe diversity gap that is well documented (see, e.g., the [2017 GitHub Open Source Survey](https://opensourcesurvey.org/2017/) and [this blog post](https://medium.com/tech-diversity-files/if-you-think-women-in-tech-is-just-a-pipeline-problem-you-haven-t-been-paying-attention-cb7a2073b996)).
+
+Since its inception and until 2018, NumPy was maintained by a handful of volunteers often working nights and weekends outside of their day jobs. At any one time, the number of active core developers, the ones doing most of the heavy lifting as well as code review and integration of contributions from the community, was in the range of 4 to 8. The project didn't have a roadmap or mechanism for directing resources, being driven by individual efforts to work on what seemed needed. The authors on the NumPy paper are the individuals who made the most significant and sustained contributions to the project over a period of 15 years (2005 - 2019). The lack of diversity on this author list is a reflection of the formative years of the Python and SciPy ecosystems.
+
+2018 has marked an important milestone in the history of the NumPy project. Receiving funding from The Gordon and Betty Moore Foundation and Alfred P. Sloan Foundation allowed us to provide full-time employment for two software engineers with years of experience contributing to the Python ecosystem. Those efforts brought NumPy to a much healthier technical state.
+
+This funding also created space for NumPy maintainers to focus on project governance, community development, and outreach to underrepresented groups. [The diversity statement](https://figshare.com/articles/online_resource/Diversity_and_Inclusion_Statement_NumPy_for_Chan_Zuckerberg_Initiative_EOSS_2019_round_1/12980852) written in mid 2019 for the CZI EOSS program grant application details some of the challenges as well as the advances in our efforts to bring in more diverse talent to the NumPy team.
+
+## The Present
+
+Offering employment opportunities is an effective way to attract and retain diverse talent in OSS. Therefore, we used two-thirds of our second grant that became available in Dec 2019 to employ Melissa Weber Mendonça and Mars Lee.
+
+As a result of several initiatives aimed at community development and engagement led by Inessa Pawson and Ralf Gommers, the NumPy project has received a number of valuable contributions from women and other underrepresented groups in open source in 2020:
+
+- Melissa Weber Mendonça gained commit rights, is maintaining numpy.f2py and is leading the documentation team,
+- Shaloo Shalini created all case studies on numpy.org,
+- Mars Lee contributed web design and led our accessibility improvements work,
+- Isabela Presedo-Floyd designed our new logo,
+- Stephanie Mendoza, Xiayoi Deng, Deji Suolang, and Mame Fatou Thiam designed and fielded the first NumPy user survey,
+- Yuki Dunn, Dayane Machado, Mahfuza Humayra Mohona, Sumera Priyadarsini, Shaloo Shalini, and Kriti Singh (former Outreachy intern) helped the survey team to reach out to non-English speaking NumPy users and developers by translating the questionnaire into their native languages,
+- Sayed Adel, Raghuveer Devulapalli, and Chunlin Fang are driving the work on SIMD optimizations in the core of NumPy.
+
+While we still have much more work to do, the NumPy team is starting to look much more representative of our user base. And we can assure you that the next NumPy paper will certainly have a more diverse group of authors.
+
+## The Future
+
+We are fully committed to fostering inclusion and diversity on our team and in our community, and to do our part in building a more just and equitable future.
+
+We are open to dialogue and welcome every opportunity to connect with organizations representing and supporting women and minorities in tech and science. We are ready to listen, learn, and support.
+
+Please get in touch with us on [our mailing list](https://scipy.org/scipylib/mailing-lists.html#mailing-lists), [GitHub](https://github.com/numpy/numpy/issues), [Slack](https://numpy.org/contribute/), in private at numpy-team@googlegroups.com, or join our [bi-weekly community meeting](https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg).
+
+
+_Sayed Adel, Sebastian Berg, Raghuveer Devulapalli, Chunlin Fang, Ralf Gommers, Allan Haldane, Stephan Hoyer, Mars Lee, Melissa Weber Mendonça, Jarrod Millman, Inessa Pawson, Matti Picus, Nathaniel Smith, Julian Taylor, Pauli Virtanen, Stéfan van der Walt, Eric Wieser, on behalf of the NumPy team_
+
From 74e85eb0ada0751f1ff7e7d25173949766ecd5af Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:37:46 +0000
Subject: [PATCH 073/909] New translations gw-discov.md (Spanish)
---
content/es/case-studies/gw-discov.md | 69 ++++++++++++++++++++++++++++
1 file changed, 69 insertions(+)
create mode 100644 content/es/case-studies/gw-discov.md
diff --git a/content/es/case-studies/gw-discov.md b/content/es/case-studies/gw-discov.md
new file mode 100644
index 0000000000..3d25090e13
--- /dev/null
+++ b/content/es/case-studies/gw-discov.md
@@ -0,0 +1,69 @@
+---
+title: "Case Study: Discovery of Gravitational Waves"
+sidebar: false
+---
+
+{{< figure src="/images/content_images/cs/gw_sxs_image.png" class="fig-center" caption="**Gravitational Waves**" alt="binary coalesce black hole generating gravitational waves" attr="*(Image Credits: The Simulating eXtreme Spacetimes (SXS) Project at LIGO)*" attrlink="https://youtu.be/Zt8Z_uzG71o" >}}
+
+
+
The scientific Python ecosystem is critical infrastructure for the research done at LIGO.
+
+
+
+## About [Gravitational Waves](https://www.nationalgeographic.com/news/2017/10/what-are-gravitational-waves-ligo-astronomy-science/) and [LIGO](https://www.ligo.caltech.edu)
+
+Gravitational waves are ripples in the fabric of space and time, generated by cataclysmic events in the universe such as collision and merging of two black holes or coalescing binary stars or supernovae. Observing GW can not only help in studying gravity but also in understanding some of the obscure phenomena in the distant universe and its impact.
+
+The [Laser Interferometer Gravitational-Wave Observatory (LIGO)](https://www.ligo.caltech.edu) was designed to open the field of gravitational-wave astrophysics through the direct detection of gravitational waves predicted by Einstein’s General Theory of Relativity. It comprises two widely-separated interferometers within the United States — one in Hanford, Washington and the other in Livingston, Louisiana — operated in unison to detect gravitational waves. Each of them has multi-kilometer-scale gravitational wave detectors that use laser interferometry. The LIGO Scientific Collaboration (LSC), is a group of more than 1000 scientists from universities around the United States and in 14 other countries supported by more than 90 universities and research institutes; approximately 250 students actively contributing to the collaboration. The new LIGO discovery is the first observation of gravitational waves themselves, made by measuring the tiny disturbances the waves make to space and time as they pass through the earth. It has opened up new astrophysical frontiers that explore the warped side of the universe—objects and phenomena that are made from warped spacetime.
+
+
+### Key Objectives
+
+* Though its [mission](https://www.ligo.caltech.edu/page/what-is-ligo) is to detect gravitational waves from some of the most violent and energetic processes in the Universe, the data LIGO collects may have far-reaching effects on many areas of physics including gravitation, relativity, astrophysics, cosmology, particle physics, and nuclear physics.
+* Crunch observed data via numerical relativity computations that involves complex maths in order to discern signal from noise, filter out relevant signal and statistically estimate significance of observed data
+* Data visualization so that the binary / numerical results can be comprehended.
+
+
+
+### The Challenges
+
+* **Computation**
+
+ Gravitational Waves are hard to detect as they produce a very small effect and have tiny interaction with matter. Processing and analyzing all of LIGO's data requires a vast computing infrastructure.After taking care of noise, which is billions of times of the signal, there is still very complex relativity equations and huge amounts of data which present a computational challenge: [O(10^7) CPU hrs needed for binary merger analyses](https://youtu.be/7mcHknWWzNI) spread on 6 dedicated LIGO clusters
+
+* **Data Deluge**
+
+ As observational devices become more sensitive and reliable, the challenges posed by data deluge and finding a needle in a haystack rise multi-fold. LIGO generates terabytes of data every day! Making sense of this data requires an enormous effort for each and every detection. For example, the signals being collected by LIGO must be matched by supercomputers against hundreds of thousands of templates of possible gravitational-wave signatures.
+
+* **Visualization**
+
+ Once the obstacles related to understanding Einstein’s equations well enough to solve them using supercomputers are taken care of, the next big challenge was making data comprehensible to the human brain. Simulation modeling as well as signal detection requires effective visualization techniques. Visualization also plays a role in lending more credibility to numerical relativity in the eyes of pure science aficionados, who did not give enough importance to numerical relativity until imaging and simulations made it easier to comprehend results for a larger audience. Speed of complex computations and rendering, re-rendering images and simulations using latest experimental inputs and insights can be a time consuming activity that challenges researchers in this domain.
+
+{{< figure src="/images/content_images/cs/gw_strain_amplitude.png" class="fig-center" alt="gravitational waves strain amplitude" caption="**Estimated gravitational-wave strain amplitude from GW150914**" attr="(**Graph Credits:** Observation of Gravitational Waves from a Binary Black Hole Merger, ResearchGate Publication)" attrlink="https://www.researchgate.net/publication/293886905_Observation_of_Gravitational_Waves_from_a_Binary_Black_Hole_Merger" >}}
+
+## NumPy’s Role in the Detection of Gravitational Waves
+
+Gravitational waves emitted from the merger cannot be computed using any technique except brute force numerical relativity using supercomputers. The amount of data LIGO collects is as incomprehensibly large as gravitational wave signals are small.
+
+NumPy, the standard numerical analysis package for Python, was utilized by the software used for various tasks performed during the GW detection project at LIGO. NumPy helped in solving complex maths and data manipulation at high speed. Here are some examples:
+
+* [Signal Processing](https://www.uv.es/virgogroup/Denoising_ROF.html): Glitch detection, [Noise identification and Data Characterization](https://ep2016.europython.eu/media/conference/slides/pyhton-in-gravitational-waves-research-communities.pdf) (NumPy, scikit-learn, scipy, matplotlib, pandas, pyCharm)
+* Data retrieval: Deciding which data can be analyzed, figuring out whether it contains a signal - needle in a haystack
+* Statistical analysis: estimate the statistical significance of observational data, estimating the signal parameters (e.g. masses of stars, spin velocity, and distance) by comparison with a model.
+* Visualization of data
+ - Time series
+ - Spectrograms
+* Compute Correlations
+* Key [Software](https://github.com/lscsoft) developed in GW data analysis such as [GwPy](https://gwpy.github.io/docs/stable/overview.html) and [PyCBC](https://pycbc.org) uses NumPy and AstroPy under the hood for providing object based interfaces to utilities, tools, and methods for studying data from gravitational-wave detectors.
+
+{{< figure src="/images/content_images/cs/gwpy-numpy-dep-graph.png" class="fig-center" alt="gwpy-numpy depgraph" caption="**Dependency graph showing how GwPy package depends on NumPy**" >}}
+
+----
+
+{{< figure src="/images/content_images/cs/PyCBC-numpy-dep-graph.png" class="fig-center" alt="PyCBC-numpy depgraph" caption="**Dependency graph showing how PyCBC package depends on NumPy**" >}}
+
+## Summary
+
+GW detection has enabled researchers to discover entirely unexpected phenomena while providing new insight into many of the most profound astrophysical phenomena known. Number crunching and data visualization is a crucial step that helps scientists gain insights into data gathered from the scientific observations and understand the results. The computations are complex and cannot be comprehended by humans unless it is visualized using computer simulations that are fed with the real observed data and analysis. NumPy along with other Python packages such as matplotlib, pandas, and scikit-learn is [enabling researchers](https://www.gw-openscience.org/events/GW150914/) to answer complex questions and discover new horizons in our understanding of the universe.
+
+{{< figure src="/images/content_images/cs/numpy_gw_benefits.png" class="fig-center" alt="numpy benefits" caption="**Key NumPy Capabilities utilized**" >}}
From 365104e94487874574ad6a3e9f07c7cf5d62c85d Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:37:48 +0000
Subject: [PATCH 074/909] New translations deeplabcut-dnn.md (Spanish)
---
content/es/case-studies/deeplabcut-dnn.md | 90 +++++++++++++++++++++++
1 file changed, 90 insertions(+)
create mode 100644 content/es/case-studies/deeplabcut-dnn.md
diff --git a/content/es/case-studies/deeplabcut-dnn.md b/content/es/case-studies/deeplabcut-dnn.md
new file mode 100644
index 0000000000..b40ed2af50
--- /dev/null
+++ b/content/es/case-studies/deeplabcut-dnn.md
@@ -0,0 +1,90 @@
+---
+title: "Case Study: DeepLabCut 3D Pose Estimation"
+sidebar: false
+---
+
+{{< figure src="/images/content_images/cs/mice-hand.gif" class="fig-center" caption="**Analyzing mice hand-movement using DeepLapCut**" alt="micehandanim" attr="*(Source: www.deeplabcut.org )*" attrlink="http://www.mousemotorlab.org/deeplabcut">}}
+
+
+
Open Source Software is accelerating Biomedicine. DeepLabCut enables automated video analysis of animal behavior using Deep Learning.
+
+
+
+## About DeepLabCut
+
+[DeepLabCut](https://github.com/DeepLabCut/DeepLabCut) is an open source toolbox that empowers researchers at hundreds of institutions worldwide to track behaviour of laboratory animals, with very little training data, at human-level accuracy. With DeepLabCut technology, scientists can delve deeper into the scientific understanding of motor control and behavior across animal species and timescales.
+
+Several areas of research, including neuroscience, medicine, and biomechanics, use data from tracking animal movement. DeepLabCut helps in understanding what humans and other animals are doing by parsing actions that have been recorded on film. Using automation for laborious tasks of tagging and monitoring, along with deep neural network based data analysis, DeepLabCut makes scientific studies involving observing animals, such as primates, mice, fish, flies etc., much faster and more accurate.
+
+{{< figure src="/images/content_images/cs/race-horse.gif" class="fig-center" caption="**Colored dots track the positions of a racehorse’s body part**" alt="horserideranim" attr="*(Source: Mackenzie Mathis)*">}}
+
+DeepLabCut's non-invasive behavioral tracking of animals by extracting the poses of animals is crucial for scientific pursuits in domains such as biomechanics, genetics, ethology & neuroscience. Measuring animal poses non-invasively from video - without markers - in dynamically changing backgrounds is computationally challenging, both technically as well as in terms of resource needs and training data required.
+
+DeepLabCut allows researchers to estimate the pose of the subject, efficiently enabling them to quantify the behavior through a Python based software toolkit. With DeepLabCut, researchers can identify distinct frames from videos, digitally label specific body parts in a few dozen frames with a tailored GUI, and then the deep learning based pose estimation architectures in DeepLabCut learn how to pick out those same features in the rest of the video and in other similar videos of animals. It works across species of animals, from common laboratory animals such as flies and mice to more unusual animals like [cheetahs][cheetah-movement].
+
+DeepLabCut uses a principle called [transfer learning](https://arxiv.org/pdf/1909.11229), which greatly reduces the amount of training data required and speeds up the convergence of the training period. Depending on the needs, users can pick different network architectures that provide faster inference (e.g. MobileNetV2), which can also be combined with real-time experimental feedback. DeepLabCut originally used the feature detectors from a top-performing human pose estimation architecture, called [DeeperCut](https://arxiv.org/abs/1605.03170), which inspired the name. The package now has been significantly changed to include additional architectures, augmentation methods, and a full front-end user experience. Furthermore, to support large-scale biological experiments DeepLabCut provides active learning capabilities so that users can increase the training set over time to cover edge cases and make their pose estimation algorithm robust within the specific context.
+
+Recently, the [DeepLabCut model zoo](http://www.mousemotorlab.org/dlc-modelzoo) was introduced, which provides pre-trained models for various species and experimental conditions from facial analysis in primates to dog posture. This can be run for instance in the cloud without any labeling of new data, or neural network training, and no programming experience is necessary.
+
+### Key Goals and Results
+
+* **Automation of animal pose analysis for scientific studies:**
+
+ The primary objective of DeepLabCut technology is to measure and track posture of animals in a diverse settings. This data can be used, for example, in neuroscience studies to understand how the brain controls movement, or to elucidate how animals socially interact. Researchers have observed a [tenfold performance boost](https://www.biorxiv.org/content/10.1101/457242v1) with DeepLabCut. Poses can be inferred offline at up to 1200 frames per second (FPS).
+
+* **Creation of an easy-to-use Python toolkit for pose estimation:**
+
+ DeepLabCut wanted to share their animal pose-estimation technology in the form of an easy to use tool that can be adopted by researchers easily. So they have created a complete, easy-to-use Python toolbox with project management features as well. These enable not only automation of pose-estimation but also managing the project end-to-end by helping the DeepLabCut Toolkit user right from the dataset collection stage to creating shareable and reusable analysis pipelines.
+
+ Their [toolkit][DLCToolkit] is now available as open source.
+
+ A typical DeepLabCut Workflow includes:
+
+ - creation and refining of training sets via active learning
+ - creation of tailored neural networks for specific animals and scenarios
+ - code for large-scale inference on videos
+ - draw inferences using integrated visualization tools
+
+{{< figure src="/images/content_images/cs/deeplabcut-toolkit-steps.png" class="csfigcaption" caption="**Pose estimation steps with DeepLabCut**" alt="dlcsteps" align="middle" attr="(Source: DeepLabCut)" attrlink="https://twitter.com/DeepLabCut/status/1198046918284210176/photo/1" >}}
+
+### The Challenges
+
+* **Speed**
+
+ Fast processing of animal behavior videos in order to measure their behavior and at the same time make scientific experiments more efficient, accurate. Extracting detailed animal poses for laboratory experiments, without markers, in dynamically changing backgrounds, can be challenging, both technically as well as in terms of resource needs and training data required. Coming up with a tool that is easy to use without the need for skills such as computer vision expertise that enables scientists to do research in more real-world contexts, is a non-trivial problem to solve.
+
+* **Combinatorics**
+
+ Combinatorics involves assembly and integration of movement of multiple limbs into individual animal behavior. Assembling keypoints and their connections into individual animal movements and linking them across time is a complex process that requires heavy-duty numerical analysis, especially in case of multi-animal movement tracking in experiment videos.
+
+* **Data Processing**
+
+ Last but not the least, array manipulation - processing large stacks of arrays corresponding to various images, target tensors and keypoints is fairly challenging.
+
+{{< figure src="/images/content_images/cs/pose-estimation.png" class="csfigcaption" caption="**Pose estimation variety and complexity**" alt="challengesfig" align="middle" attr="(Source: Mackenzie Mathis)" attrlink="https://www.biorxiv.org/content/10.1101/476531v1.full.pdf" >}}
+
+## NumPy's Role in meeting Pose Estimation Challenges
+
+NumPy addresses DeepLabCut technology's core need of numerical computations at high speed for behavioural analytics. Besides NumPy, DeepLabCut employs various Python software that utilize NumPy at their core, such as [SciPy](https://www.scipy.org), [Pandas](https://pandas.pydata.org), [matplotlib](https://matplotlib.org), [Tensorpack](https://github.com/tensorpack/tensorpack), [imgaug](https://github.com/aleju/imgaug), [scikit-learn](https://scikit-learn.org/stable/), [scikit-image](https://scikit-image.org) and [Tensorflow](https://www.tensorflow.org).
+
+The following features of NumPy played a key role in addressing the image processing, combinatorics requirements and need for fast computation in DeepLabCut pose estimation algorithms:
+
+* Vectorization
+* Masked Array Operations
+* Linear Algebra
+* Random Sampling
+* Reshaping of large arrays
+
+DeepLabCut utilizes NumPy’s array capabilities throughout the workflow offered by the toolkit. In particular, NumPy is used for sampling distinct frames for human annotation labeling, and for writing, editing and processing annotation data. Within TensorFlow the neural network is trained by DeepLabCut technology over thousands of iterations to predict the ground truth annotations from frames. For this purpose, target densities (scoremaps) are created to cast pose estimation as a image-to-image translation problem. To make the neural networks robust, data augmentation is employed, which requires the calculation of target scoremaps subject to various geometric and image processing steps. To make training fast, NumPy’s vectorization capabilities are leveraged. For inference, the most likely predictions from target scoremaps need to extracted and one needs to efficiently “link predictions to assemble individual animals”.
+
+{{< figure src="/images/content_images/cs/deeplabcut-workflow.png" class="fig-center" caption="**DeepLabCut Workflow**" alt="workflow" attr="*(Source: Mackenzie Mathis)*" attrlink="https://www.researchgate.net/figure/DeepLabCut-work-flow-The-diagram-delineates-the-work-flow-as-well-as-the-directory-and_fig1_329185962">}}
+
+## Summary
+
+Observing and efficiently describing behavior is a core tenant of modern ethology, neuroscience, medicine, and technology. [DeepLabCut](http://orga.cvss.cc/wp-content/uploads/2019/05/NathMathis2019.pdf) allows researchers to estimate the pose of the subject, efficiently enabling them to quantify the behavior. With only a small set of training images, the DeepLabCut Python toolbox allows training a neural network to within human level labeling accuracy, thus expanding its application to not only behavior analysis in the laboratory, but to potentially also in sports, gait analysis, medicine and rehabilitation studies. Complex combinatorics, data processing challenges faced by DeepLabCut algorithms are addressed through the use of NumPy's array manipulation capabilities.
+
+{{< figure src="/images/content_images/cs/numpy_dlc_benefits.png" class="fig-center" alt="numpy benefits" caption="**Key NumPy Capabilities utilized**" >}}
+
+[cheetah-movement]: https://www.technologynetworks.com/neuroscience/articles/interview-a-deeper-cut-into-behavior-with-mackenzie-mathis-327618
+
+[DLCToolkit]: https://github.com/DeepLabCut/DeepLabCut
From 58d2330958272432f97f6b1cc32feb2a44721ed2 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:37:50 +0000
Subject: [PATCH 075/909] New translations cricket-analytics.md (Spanish)
---
content/es/case-studies/cricket-analytics.md | 64 ++++++++++++++++++++
1 file changed, 64 insertions(+)
create mode 100644 content/es/case-studies/cricket-analytics.md
diff --git a/content/es/case-studies/cricket-analytics.md b/content/es/case-studies/cricket-analytics.md
new file mode 100644
index 0000000000..987b38fb68
--- /dev/null
+++ b/content/es/case-studies/cricket-analytics.md
@@ -0,0 +1,64 @@
+---
+title: "Case Study: Cricket Analytics, the game changer!"
+sidebar: false
+---
+
+{{< figure src="/images/content_images/cs/ipl-stadium.png" caption="**IPLT20, the biggest Cricket Festival in India**" alt="Indian Premier League Cricket cup and stadium" attr="*(Image credits: IPLT20 (cup and logo) & Akash Yadav (stadium))*" attrlink="https://unsplash.com/@aksh1802" >}}
+
+
+
You don't play for the crowd, you play for the country.
+
+
+
+## About Cricket
+
+It would be an understatement to state that Indians love cricket. The game is played in just about every nook and cranny of India, rural or urban, popular with the young and the old alike, connecting billions in India unlike any other sport. Cricket enjoys lots of media attention. There is a significant amount of [money](https://www.statista.com/topics/4543/indian-premier-league-ipl/) and fame at stake. Over the last several years, technology has literally been a game changer. Audiences are spoilt for choice with streaming media, tournaments, affordable access to mobile based live cricket watching, and more.
+
+The Indian Premier League (IPL) is a professional Twenty20 cricket league, founded in 2008. It is one of the most attended cricketing events in the world, valued at [$6.7 billion](https://en.wikipedia.org/wiki/Indian_Premier_League) in 2019.
+
+Cricket is a game of numbers - the runs scored by a batsman, the wickets taken by a bowler, the matches won by a cricket team, the number of times a batsman responds in a certain way to a kind of bowling attack, etc. The capability to dig into cricketing numbers for both improving performance and studying the business opportunities, overall market, and economics of cricket via powerful analytics tools, powered by numerical computing software such as NumPy, is a big deal. Cricket analytics provides interesting insights into the game and predictive intelligence regarding game outcomes.
+
+Today, there are rich and almost infinite troves of cricket game records and statistics available, e.g., [ESPN cricinfo](https://stats.espncricinfo.com/ci/engine/stats/index.html) and [cricsheet](https://cricsheet.org). These and several such cricket databases have been used for [cricket analysis](https://www.researchgate.net/publication/336886516_Data_visualization_and_toss_related_analysis_of_IPL_teams_and_batsmen_performances) using the latest machine learning and predictive modelling algorithms. Media and entertainment platforms along with professional sports bodies associated with the game use technology and analytics for determining key metrics for improving match winning chances:
+
+* batting performance moving average,
+* score forecasting,
+* gaining insights into fitness and performance of a player against different opposition,
+* player contribution to wins and losses for making strategic decisions on team composition
+
+{{< figure src="/images/content_images/cs/cricket-pitch.png" class="csfigcaption" caption="**Cricket Pitch, the focal point in the field**" alt="A cricket pitch with bowler and batsmen" align="middle" attr="*(Image credit: Debarghya Das)*" attrlink="http://debarghyadas.com/files/IPLpaper.pdf" >}}
+
+### Key Data Analytics Objectives
+
+* Sports data analytics are used not only in cricket but many [other sports](https://adtmag.com/blogs/dev-watch/2017/07/sports-analytics.aspx) for improving the overall team performance and maximizing winning chances.
+* Real-time data analytics can help in gaining insights even during the game for changing tactics by the team and by associated businesses for economic benefits and growth.
+* Besides historical analysis, predictive models are harnessed to determine the possible match outcomes that require significant number crunching and data science know-how, visualization tools and capability to include newer observations in the analysis.
+
+{{< figure src="/images/content_images/cs/player-pose-estimator.png" class="fig-center" alt="pose estimator" caption="**Cricket Pose Estimator**" attr="*(Image credit: connect.vin)*" attrlink="https://connect.vin/2019/05/ai-for-cricket-batsman-pose-analysis/" >}}
+
+### The Challenges
+
+* **Data Cleaning and preprocessing**
+
+ IPL has expanded cricket beyond the classic test match format to a much larger scale. The number of matches played every season across various formats has increased and so has the data, the algorithms, newer sports data analysis technologies and simulation models. Cricket data analysis requires field mapping, player tracking, ball tracking, player shot analysis, and several other aspects involved in how the ball is delivered, its angle, spin, velocity, and trajectory. All these factors together have increased the complexity of data cleaning and preprocessing.
+
+* **Dynamic Modeling**
+
+ In cricket, just like any other sport, there can be a large number of variables related to tracking various numbers of players on the field, their attributes, the ball, and several possibilities of potential actions. The complexity of data analytics and modeling is directly proportional to the kind of predictive questions that are put forth during analysis and are highly dependent on data representation and the model. Things get even more challenging in terms of computation, data comparisons when dynamic cricket play predictions are sought such as what would have happened if the batsman had hit the ball at a different angle or velocity.
+
+* **Predictive Analytics Complexity**
+
+ Much of the decision making in cricket is based on questions such as "how often does a batsman play a certain kind of shot if the ball delivery is of a particular type", or "how does a bowler change his line and length if the batsman responds to his delivery in a certain way". This kind of predictive analytics query requires highly granular dataset availability and the capability to synthesize data and create generative models that are highly accurate.
+
+## NumPy’s Role in Cricket Analytics
+
+Sports Analytics is a thriving field. Many researchers and companies [use NumPy](https://adtmag.com/blogs/dev-watch/2017/07/sports-analytics.aspx) and other PyData packages like Scikit-learn, SciPy, Matplotlib, and Jupyter, besides using the latest machine learning and AI techniques. NumPy has been used for various kinds of cricket related sporting analytics such as:
+
+* **Statistical Analysis:** NumPy's numerical capabilities help estimate the statistical significance of observational data or match events in the context of various player and game tactics, estimating the game outcome by comparison with a generative or static model. [Causal analysis](https://amplitude.com/blog/2017/01/19/causation-correlation) and [big data approaches](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4996805/) are used for tactical analysis.
+
+* **Data Visualization:** Data graphing and [visualization](https://towardsdatascience.com/advanced-sports-visualization-with-pandas-matplotlib-and-seaborn-9c16df80a81b) provides useful insights into relationship between various datasets.
+
+## Summary
+
+Sports Analytics is a game changer when it comes to how professional games are played, especially how strategic decision making happens, which until recently was primarily done based on “gut feeling" or adherence to past traditions. NumPy forms a solid foundation for a large set of Python packages which provide higher level functions related to data analytics, machine learning, and AI algorithms. These packages are widely deployed to gain real-time insights that help in decision making for game-changing outcomes, both on field as well as to draw inferences and drive business around the game of cricket. Finding out the hidden parameters, patterns, and attributes that lead to the outcome of a cricket match helps the stakeholders to take notice of game insights that are otherwise hidden in numbers and statistics.
+
+{{< figure src="/images/content_images/cs/numpy_ca_benefits.png" class="fig-center" alt="Diagram showing benefits of using NumPy for cricket analytics" caption="**Key NumPy Capabilities utilized**" >}}
From aacd7c183e0d17358b03d8ecb715f660becbe9fd Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:37:51 +0000
Subject: [PATCH 076/909] New translations blackhole-image.md (Spanish)
---
content/es/case-studies/blackhole-image.md | 70 ++++++++++++++++++++++
1 file changed, 70 insertions(+)
create mode 100644 content/es/case-studies/blackhole-image.md
diff --git a/content/es/case-studies/blackhole-image.md b/content/es/case-studies/blackhole-image.md
new file mode 100644
index 0000000000..2906e12ece
--- /dev/null
+++ b/content/es/case-studies/blackhole-image.md
@@ -0,0 +1,70 @@
+---
+title: "Case Study: First Image of a Black Hole"
+sidebar: false
+---
+
+{{< figure src="/images/content_images/cs/blackhole.jpg" caption="**Black Hole M87**" alt="black hole image" attr="*(Image Credits: Event Horizon Telescope Collaboration)*" attrlink="https://www.jpl.nasa.gov/images/universe/20190410/blackhole20190410.jpg" >}}
+
+
+
Imaging the M87 Black Hole is like trying to see something that is by definition impossible to see.
+
+
+
+## A telescope the size of the earth
+
+The [Event Horizon telescope (EHT)](https://eventhorizontelescope.org) is an array of eight ground-based radio telescopes forming a computational telescope the size of the earth, studing the universe with unprecedented sensitivity and resolution. The huge virtual telescope, which uses a technique called very-long-baseline interferometry (VLBI), has an angular resolution of [20 micro-arcseconds][resolution] — enough to read a newspaper in New York from a sidewalk café in Paris!
+
+### Objetivos clave y resultados
+
+* **A New View of the Universe:** The groundwork for the EHT's groundbreaking image had been laid 100 years earlier when [Sir Arthur Eddington][eddington] yielded the first observational support of Einstein's theory of general relativity.
+
+* **The Black Hole:** EHT was trained on a supermassive black hole approximately 55 million light-years from Earth, lying at the center of the galaxy Messier 87 (M87) in the Virgo galaxy cluster. Its mass is 6.5 billion times the Sun's. It had been studied for [over 100 years](https://www.jpl.nasa.gov/news/news.php?feature=7385), but never before had a black hole been visually observed.
+
+* **Comparing Observations to Theory:** From Einstein’s general theory of relativity, scientists expected to find a shadow-like region caused by gravitational bending and capture of light. Scientists could use it to measure the black hole's enormous mass.
+
+### The Challenges
+
+* **Computational scale**
+
+ EHT poses massive data-processing challenges, including rapid atmospheric phase fluctuations, large recording bandwidth, and telescopes that are widely dissimilar and geographically dispersed.
+
+* **Too much information**
+
+ Each day EHT generates over 350 terabytes of observations, stored on helium-filled hard drives. Reducing the volume and complexity of this much data is enormously difficult.
+
+* **Into the unknown**
+
+ When the goal is to see something never before seen, how can scientists be confident the image is correct?
+
+{{< figure src="/images/content_images/cs/dataprocessbh.png" class="csfigcaption" caption="**EHT Data Processing Pipeline**" alt="data pipeline" align="middle" attr="(Diagram Credits: The Astrophysical Journal, Event Horizon Telescope Collaboration)" attrlink="https://iopscience.iop.org/article/10.3847/2041-8213/ab0c57" >}}
+
+## NumPy’s Role
+
+What if there's a problem with the data? Or perhaps an algorithm relies too heavily on a particular assumption. Will the image change drastically if a single parameter is changed?
+
+The EHT collaboration met these challenges by having independent teams evaluate the data, using both established and cutting-edge image reconstruction techniques. When results proved consistent, they were combined to yield the first-of-a-kind image of the black hole.
+
+Their work illustrates the role the scientific Python ecosystem plays in advancing science through collaborative data analysis.
+
+{{< figure src="/images/content_images/cs/bh_numpy_role.png" class="fig-center" alt="role of numpy" caption="**The role of NumPy in Black Hole imaging**" >}}
+
+For example, the [`eht-imaging`][ehtim] Python package provides tools for simulating and performing image reconstruction on VLBI data. NumPy is at the core of array data processing used in this package, as illustrated by the partial software dependency chart below.
+
+{{< figure src="/images/content_images/cs/ehtim_numpy.png" class="fig-center" alt="ehtim dependency map highlighting numpy" caption="**Software dependency chart of ehtim package highlighting NumPy**" >}}
+
+Besides NumPy, many other packages, such as [SciPy](https://www.scipy.org) and [Pandas](https://pandas.io), are part of the data processing pipeline for imaging the black hole. The standard astronomical file formats and time/coordinate transformations were handled by [Astropy][astropy], while [Matplotlib][mpl] was used in visualizing data throughout the analysis pipeline, including the generation of the final image of the black hole.
+
+## Summary
+
+The efficient and adaptable n-dimensional array that is NumPy's central feature enabled researchers to manipulate large numerical datasets, providing a foundation for the first-ever image of a black hole. A landmark moment in science, it gives stunning visual evidence of Einstein’s theory. The achievement encompasses not only technological breakthroughs but also international collaboration among over 200 scientists and some of the world's best radio observatories. Innovative algorithms and data processing techniques, improving upon existing astronomical models, helped unfold a mystery of the universe.
+
+{{< figure src="/images/content_images/cs/numpy_bh_benefits.png" class="fig-center" alt="numpy benefits" caption="**Key NumPy Capabilities utilized**" >}}
+
+[resolution]: https://eventhorizontelescope.org/press-release-april-10-2019-astronomers-capture-first-image-black-hole
+
+[eddington]: https://en.wikipedia.org/wiki/Eddington_experiment
+
+[ehtim]: https://github.com/achael/eht-imaging
+
+[astropy]: https://www.astropy.org/
+[mpl]: https://matplotlib.org/
From c19f0e2eb898ae6d80f10b9ae87e9947c905b78f Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:37:53 +0000
Subject: [PATCH 077/909] New translations news.md (Spanish)
---
content/es/news.md | 83 ++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 83 insertions(+)
create mode 100644 content/es/news.md
diff --git a/content/es/news.md b/content/es/news.md
new file mode 100644
index 0000000000..5dcb849596
--- /dev/null
+++ b/content/es/news.md
@@ -0,0 +1,83 @@
+---
+title: News
+sidebar: false
+---
+
+### Diversity in the NumPy project
+
+_Sep 20, 2020_ -- We wrote a [statement on the state of, and discussion on social media around, diversity and inclusion in the NumPy project](/diversity_sep2020).
+
+
+### First official NumPy paper published in Nature!
+
+_Sep 16, 2020_ -- We are pleased to announce the publication of [the first official paper on NumPy](https://www.nature.com/articles/s41586-020-2649-2) as a review article in Nature. This comes 14 years after the release of NumPy 1.0. The paper covers applications and fundamental concepts of array programming, the rich scientific Python ecosystem built on top of NumPy, and the recently added array protocols to facilitate interoperability with external array and tensor libraries like CuPy, Dask, and JAX.
+
+
+### Python 3.9 is coming, when will NumPy release binary wheels?
+
+_Sept 14, 2020_ -- Python 3.9 will be released in a few weeks. If you are an early adopter of Python versions, you may be dissapointed to find that NumPy (and other binary packages like SciPy) will not have binary wheels ready on the day of the release. It is a major effort to adapt the build infrastructure to a new Python version and it typically takes a few weeks for the packages to appear on PyPI and conda-forge. In preparation for this event, please make sure to
+- update your `pip` to version 20.1 at least to support `manylinux2010` and `manylinux2014`
+- use [`--only-binary=numpy`](https://pip.pypa.io/en/stable/reference/pip_install/#cmdoption-only-binary) or `--only-binary=:all:` to prevent `pip` from trying to build from source.
+
+
+### Numpy 1.19.2 release
+
+_Sept 10, 2020_ -- [NumPy 1.19.2](https://numpy.org/devdocs/release/1.19.2-notes.html) is now available. This latest release in the 1.19 series fixes several bugs, prepares for the [upcoming Cython 3.x release](http://docs.cython.org/en/latest/src/changes.html) and pins setuptools to keep distutils working while upstream modifications are ongoing. The aarch64 wheels are built with the latest manylinux2014 release that fixes the problem of differing page sizes used by different linux distros.
+
+### The inaugural NumPy survey is live!
+
+_Jul 2, 2020_ -- This survey is meant to guide and set priorities for decision-making about the development of NumPy as software and as a community. The survey is available in 8 additional languages besides English: Bangla, Hindi, Japanese, Mandarin, Portuguese, Russian, Spanish and French.
+
+Please help us make NumPy better and take the survey [here](https://umdsurvey.umd.edu/jfe/form/SV_8bJrXjbhXf7saAl).
+
+
+### NumPy has a new logo!
+
+_Jun 24, 2020_ -- NumPy now has a new logo:
+
+
+
+The logo is a modern take on the old one, with a cleaner design. Thanks to Isabela Presedo-Floyd for designing the new logo, as well as to Travis Vaught for the old logo that served us well for 15+ years.
+
+
+### NumPy 1.19.0 release
+
+_Jun 20, 2020_ -- NumPy 1.19.0 is now available. This is the first release without Python 2 support, hence it was a "clean-up release". The minimum supported Python version is now Python 3.6. An important new feature is that the random number generation infrastructure that was introduced in NumPy 1.17.0 is now accessible from Cython.
+
+
+### Season of Docs acceptance
+
+_May 11, 2020_ -- NumPy has been accepted as one of the mentor organizations for the Google Season of Docs program. We are excited about the opportunity to work with a technical writer to improve NumPy's documentation once again! For more details, please see [the official Season of Docs site](https://developers.google.com/season-of-docs/) and our [ideas page](https://github.com/numpy/numpy/wiki/Google-Season-of-Docs-2020-Project-Ideas).
+
+
+### NumPy 1.18.0 release
+
+_Dec 22, 2019_ -- NumPy 1.18.0 is now available. After the major changes in 1.17.0, this is a consolidation release. It is the last minor release that will support Python 3.5. Highlights of the release includes the addition of basic infrastructure for linking with 64-bit BLAS and LAPACK libraries, and a new C-API for `numpy.random`.
+
+Please see the [release notes](https://github.com/numpy/numpy/releases/tag/v1.18.0) for more details.
+
+
+### NumPy receives a grant from the Chan Zuckerberg Initiative
+
+_Nov 15, 2019_ -- We are pleased to announce that NumPy and OpenBLAS, one of NumPy's key dependencies, have received a joint grant for $195,000 from the Chan Zuckerberg Initiative through their [Essential Open Source Software for Science program](https://chanzuckerberg.com/eoss/) that supports software maintenance, growth, development, and community engagement for open source tools critical to science.
+
+This grant will be used to ramp up the efforts in improving NumPy documentation, website redesign, and community development to better serve our large and rapidly growing user base, and ensure the long-term sustainability of the project. While the OpenBLAS team will focus on addressing sets of key technical issues, in particular thread-safety, AVX-512, and thread-local storage (TLS) issues, as well as algorithmic improvements in ReLAPACK (Recursive LAPACK) on which OpenBLAS depends.
+
+More details on our proposed initiatives and deliverables can be found in the [full grant proposal](https://figshare.com/articles/Proposal_NumPy_OpenBLAS_for_Chan_Zuckerberg_Initiative_EOSS_2019_round_1/10302167). The work is scheduled to start on Dec 1st, 2019 and continue for the next 12 months.
+
+
+## Releases
+
+Here is a list of NumPy releases, with links to release notes. All bugfix releases (only the `z` changes in the `x.y.z` version number) have no new features; minor releases (the `y` increases) do.
+
+- NumPy 1.18.4 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.18.4)) -- _3 May 2020_.
+- NumPy 1.18.3 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.18.3)) -- _19 Apr 2020_.
+- NumPy 1.18.2 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.18.2)) -- _17 Mar 2020_.
+- NumPy 1.18.1 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.18.1)) -- _6 Jan 2020_.
+- NumPy 1.17.5 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.17.5)) -- _1 Jan 2020_.
+- NumPy 1.18.0 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.18.0)) -- _22 Dec 2019_.
+- NumPy 1.17.4 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.17.4)) -- _11 Nov 2019_.
+- NumPy 1.17.0 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.17.0)) -- _26 Jul 2019_.
+- NumPy 1.16.0 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.16.0)) -- _14 Jan 2019_.
+- NumPy 1.15.0 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.15.0)) -- _23 Jul 2018_.
+- NumPy 1.14.0 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.14.0)) -- _7 Jan 2018_.
From 217c831234f4f66143b070846ce8c40b58e29311 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:37:55 +0000
Subject: [PATCH 078/909] New translations history.md (Spanish)
---
content/es/history.md | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
create mode 100644 content/es/history.md
diff --git a/content/es/history.md b/content/es/history.md
new file mode 100644
index 0000000000..fc79a621af
--- /dev/null
+++ b/content/es/history.md
@@ -0,0 +1,21 @@
+---
+title: History of NumPy
+sidebar: false
+---
+
+NumPy is a foundational Python library that provides array data structures and related fast numerical routines. When started, the library had little funding, and was written mainly by graduate students—many of them without computer science education, and often without a blessing of their advisors. To even imagine that a small group of “rogue” student programmers could upend the already well-established ecosystem of research software—backed by millions in funding and many hundreds of highly qualified engineers — was preposterous. Yet, the philosophical motivations behind a fully open tool stack, in combination with the excited, friendly community with a singular focus, have proven auspicious in the long run. Nowadays, NumPy is relied upon by scientists, engineers, and many other professionals around the world. For example, the published scripts used in the analysis of gravitational waves import NumPy, and the M87 black hole imaging project directly cites NumPy.
+
+For the in-depth account on milestones in the development of NumPy and related libraries please see [arxiv.org](arxiv.org/abs/1907.10121).
+
+If you’d like to obtain a copy of the original Numeric and Numarray libraries, follow the links below:
+
+[Download Page for *Numeric*](https://sourceforge.net/projects/numpy/files/Old%20Numeric/)*
+
+[Download Page for *Numarray*](https://sourceforge.net/projects/numpy/files/Old%20Numarray/)*
+
+*Please note that these older array packages are no longer maintained, and users are strongly advised to use NumPy for any array-related purposes or refactor any pre-existing code to utilize the NumPy library.
+
+### Historic Documentation
+
+[Download *`Numeric'* Manual](static/numeric-manual.pdf)
+
From 8ff3407049b739c840194fe2d4419a8fd4a74023 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:37:57 +0000
Subject: [PATCH 079/909] New translations report-handling-manual.md (Spanish)
---
content/es/report-handling-manual.md | 95 ++++++++++++++++++++++++++++
1 file changed, 95 insertions(+)
create mode 100644 content/es/report-handling-manual.md
diff --git a/content/es/report-handling-manual.md b/content/es/report-handling-manual.md
new file mode 100644
index 0000000000..5586668cba
--- /dev/null
+++ b/content/es/report-handling-manual.md
@@ -0,0 +1,95 @@
+---
+title: NumPy Code of Conduct - How to follow up on a report
+sidebar: false
+---
+
+This is the manual followed by NumPy’s Code of Conduct Committee. It’s used when we respond to an issue to make sure we’re consistent and fair.
+
+Enforcing the [Code of Conduct](/code-of-conduct) impacts our community today and for the future. It’s an action that we do not take lightly. When reviewing enforcement measures, the Code of Conduct Committee will keep the following values and guidelines in mind:
+
+* Act in a personal manner rather than impersonal. The Committee can engage the parties to understand the situation while respecting the privacy and any necessary confidentiality of reporters. However, sometimes it is necessary to communicate with one or more individuals directly: the Committee’s goal is to improve the health of our community rather than only produce a formal decision.
+* Emphasize empathy for individuals rather than judging behavior, avoiding binary labels of “good” and “bad/evil”. Overt, clear-cut aggression and harassment exist, and we will address them firmly. But many scenarios that can prove challenging to resolve are those where normal disagreements devolve into unhelpful or harmful behavior from multiple parties. Understanding the full context and finding a path that re-engages all is hard, but ultimately the most productive for our community.
+* We understand that email is a difficult medium and can be isolating. Receiving criticism over email, without personal contact, can be particularly painful. This makes it especially important to keep an atmosphere of open-minded respect for the views of others. It also means that we must be transparent in our actions, and that we will do everything in our power to make sure that all our members are treated fairly and with sympathy.
+* Discrimination can be subtle and it can be unconscious. It can show itself as unfairness and hostility in otherwise ordinary interactions. We know that this does occur, and we will take care to look out for it. We would very much like to hear from you if you feel you have been treated unfairly, and we will use these procedures to make sure that your complaint is heard and addressed.
+* Help increase engagement in good discussion practice: try to identify where discussion may have broken down, and provide actionable information, pointers, and resources that can lead to positive change on these points.
+* Be mindful of the needs of new members: provide them with explicit support and consideration, with the aim of increasing participation from underrepresented groups in particular.
+* Individuals come from different cultural backgrounds and native languages. Try to identify any honest misunderstandings caused by a non-native speaker and help them understand the issue and what they can change to avoid causing offence. Complex discussion in a foreign language can be very intimidating, and we want to grow our diversity also across nationalities and cultures.
+
+
+## Mediation
+
+Voluntary informal mediation is a tool at our disposal. In contexts such as when two or more parties have all escalated to the point of inappropriate behavior (something sadly common in human conflict), it may be useful to facilitate a mediation process. This is only an example: the Committee can consider mediation in any case, mindful that the process is meant to be strictly voluntary and no party can be pressured to participate. If the Committee suggests mediation, it should:
+
+* Find a candidate who can serve as a mediator.
+* Obtain the agreement of the reporter(s). The reporter(s) have complete freedom to decline the mediation idea or to propose an alternate mediator.
+* Obtain the agreement of the reported person(s).
+* Settle on the mediator: while parties can propose a different mediator than the suggested candidate, only if a common agreement is reached on all terms can the process move forward.
+* Establish a timeline for mediation to complete, ideally within two weeks.
+
+The mediator will engage with all the parties and seek a resolution that is satisfactory to all. Upon completion, the mediator will provide a report (vetted by all parties to the process) to the Committee, with recommendations on further steps. The Committee will then evaluate these results (whether a satisfactory resolution was achieved or not) and decide on any additional action deemed necessary.
+
+
+## How the Committee will respond to reports
+
+When the Committee (or a Committee member) receives a report, they will first determine whether the report is about a clear and severe breach (as defined below). If so, immediate action needs to be taken in addition to the regular report handling process.
+
+
+## Clear and severe breach actions
+
+We know that it is painfully common for internet communication to start at or devolve into obvious and flagrant abuse. We will deal quickly with clear and severe breaches like personal threats, violent, sexist or racist language.
+
+When a member of the Code of Conduct Committee becomes aware of a clear and severe breach, they will do the following:
+
+* Immediately disconnect the originator from all NumPy communication channels.
+* Reply to the reporter that their report has been received and that the originator has been disconnected.
+* In every case, the moderator should make a reasonable effort to contact the originator, and tell them specifically how their language or actions qualify as a “clear and severe breach”. The moderator should also say that, if the originator believes this is unfair or they want to be reconnected to NumPy, they have the right to ask for a review, as below, by the Code of Conduct Committee. The moderator should copy this explanation to the Code of Conduct Committee.
+* The Code of Conduct Committee will formally review and sign off on all cases where this mechanism has been applied to make sure it is not being used to control ordinary heated disagreement.
+
+
+## Report handling
+
+When a report is sent to the Committee they will immediately reply to the reporter to confirm receipt. This reply must be sent within 72 hours, and the group should strive to respond much quicker than that.
+
+If a report doesn’t contain enough information, the Committee will obtain all relevant data before acting. The Committee is empowered to act on the Steering Council’s behalf in contacting any individuals involved to get a more complete account of events.
+
+The Committee will then review the incident and determine, to the best of their ability:
+
+* What happened.
+* Whether this event constitutes a Code of Conduct violation.
+* Who are the responsible party(ies).
+* Whether this is an ongoing situation, and there is a threat to anyone’s physical safety.
+
+This information will be collected in writing, and whenever possible the group’s deliberations will be recorded and retained (i.e. chat transcripts, email discussions, recorded conference calls, summaries of voice conversations, etc).
+
+It is important to retain an archive of all activities of this Committee to ensure consistency in behavior and provide institutional memory for the project. To assist in this, the default channel of discussion for this Committee will be a private mailing list accessible to current and future members of the Committee as well as members of the Steering Council upon justified request. If the Committee finds the need to use off-list communications (e.g. phone calls for early/rapid response), it should in all cases summarize these back to the list so there’s a good record of the process.
+
+The Code of Conduct Committee should aim to have a resolution agreed upon within two weeks. In the event that a resolution can’t be determined in that time, the Committee will respond to the reporter(s) with an update and projected timeline for resolution.
+
+
+## Resolutions
+
+The Committee must agree on a resolution by consensus. If the group cannot reach consensus and deadlocks for over a week, the group will turn the matter over to the Steering Council for resolution.
+
+Possible responses may include:
+
+* Taking no further action:
+ - if we determine no violations have occurred;
+ - if the matter has been resolved publicly while the Committee was considering responses.
+* Coordinating voluntary mediation: if all involved parties agree, the Committee may facilitate a mediation process as detailed above.
+* Remind publicly, and point out that some behavior/actions/language have been judged inappropriate and why in the current context, or can but hurtful to some people, requesting the community to self-adjust.
+* A private reprimand from the Committee to the individual(s) involved. In this case, the group chair will deliver that reprimand to the individual(s) over email, cc’ing the group.
+* A public reprimand. In this case, the Committee chair will deliver that reprimand in the same venue that the violation occurred, within the limits of practicality. E.g., the original mailing list for an email violation, but for a chat room discussion where the person/context may be gone, they can be reached by other means. The group may choose to publish this message elsewhere for documentation purposes.
+* A request for a public or private apology, assuming the reporter agrees to this idea: they may at their discretion refuse further contact with the violator. The chair will deliver this request. The Committee may, if it chooses, attach “strings” to this request: for example, the group may ask a violator to apologize in order to retain one’s membership on a mailing list.
+* A “mutually agreed upon hiatus” where the Committee asks the individual to temporarily refrain from community participation. If the individual chooses not to take a temporary break voluntarily, the Committee may issue a “mandatory cooling off period”.
+* A permanent or temporary ban from some or all NumPy spaces (mailing lists, gitter.im, etc.). The group will maintain records of all such bans so that they may be reviewed in the future or otherwise maintained.
+
+Once a resolution is agreed upon, but before it is enacted, the Committee will contact the original reporter and any other affected parties and explain the proposed resolution. The Committee will ask if this resolution is acceptable, and must note feedback for the record.
+
+Finally, the Committee will make a report to the NumPy Steering Council (as well as the NumPy core team in the event of an ongoing resolution, such as a ban).
+
+The Committee will never publicly discuss the issue; all public statements will be made by the chair of the Code of Conduct Committee or the NumPy Steering Council.
+
+
+## Conflicts of Interest
+
+In the event of any conflict of interest, a Committee member must immediately notify the other members, and recuse themselves if necessary.
From bb4008b0329368c3db053e23ee81f8821a838caa Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:37:58 +0000
Subject: [PATCH 080/909] New translations press-kit.md (Japanese)
---
content/ja/press-kit.md | 8 ++++++++
1 file changed, 8 insertions(+)
create mode 100644 content/ja/press-kit.md
diff --git a/content/ja/press-kit.md b/content/ja/press-kit.md
new file mode 100644
index 0000000000..a523b1d296
--- /dev/null
+++ b/content/ja/press-kit.md
@@ -0,0 +1,8 @@
+---
+title: プレス用資料
+sidebar: false
+---
+
+私達はユーザーの皆さんの次の学術論文や、コース教材、プレゼンテーションにNumPyプロジェクトのロゴなどを簡単に盛り込めるようにしたいと考えています。
+
+こちらから様々な解像度のNumPyロゴのファイルをダウンロードできます: [ロゴリンク](https://github.com/numpy/numpy/tree/master/branding/logo). ちなみに、numpy.orgのリソースを使用するということは、 [Numpy行動規範](/code-of-conduct) を受け入れることを意味していることに注意してください。
From de59b95b5294b2c53475846ef0c798f6bbc9aa65 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:38:00 +0000
Subject: [PATCH 081/909] New translations terms.md (Spanish)
---
content/es/terms.md | 178 ++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 178 insertions(+)
create mode 100644 content/es/terms.md
diff --git a/content/es/terms.md b/content/es/terms.md
new file mode 100644
index 0000000000..9a66045505
--- /dev/null
+++ b/content/es/terms.md
@@ -0,0 +1,178 @@
+---
+title: Terms of Use
+sidebar: false
+---
+
+*Last updated January 4, 2020*
+
+
+## AGREEMENT TO TERMS
+
+These Terms of Use constitute a legally binding agreement made between you, whether personally or on behalf of an entity (“you”) and NumPy ("**Project**", “**we**”, “**us**”, or “**our**”), concerning your access to and use of the numpy.org website as well as any other media form, media channel, mobile website or mobile application related, linked, or otherwise connected thereto (collectively, the “Site”). You agree that by accessing the Site, you have read, understood, and agreed to be bound by all of these Terms of Use. IF YOU DO NOT AGREE WITH ALL OF THESE TERMS OF USE, THEN YOU ARE EXPRESSLY PROHIBITED FROM USING THE SITE AND YOU MUST DISCONTINUE USE IMMEDIATELY.
+
+
+
+Supplemental terms and conditions or documents that may be posted on the Site from time to time are hereby expressly incorporated herein by reference. We reserve the right, in our sole discretion, to make changes or modifications to these Terms of Use at any time and for any reason. We will alert you about any changes by updating the “Last updated” date of these Terms of Use, and you waive any right to receive specific notice of each such change. It is your responsibility to periodically review these Terms of Use to stay informed of updates. You will be subject to, and will be deemed to have been made aware of and to have accepted, the changes in any revised Terms of Use by your continued use of the Site after the date such revised Terms of Use are posted.
+
+
+
+The information provided on the Site is not intended for distribution to or use by any person or entity in any jurisdiction or country where such distribution or use would be contrary to law or regulation or which would subject us to any registration requirement within such jurisdiction or country. Accordingly, those persons who choose to access the Site from other locations do so on their own initiative and are solely responsible for compliance with local laws, if and to the extent local laws are applicable.
+
+
+## USER REPRESENTATIONS
+
+By using the Site, you represent and warrant that: (1) you have the legal capacity and you agree to comply with these Terms of Use; (2) you will not use the Site for any illegal or unauthorized purpose; and (3) your use of the Site will not violate any applicable law or regulation.
+
+
+If you provide any information that is untrue, inaccurate, not current, or incomplete, we have the right to refuse any and all current or future use of the Site (or any portion thereof).
+
+
+## PROHIBITED ACTIVITIES
+
+You may not access or use the Site for any purpose other than that for which we make the Site available.
+
+As a user of the Site, you agree not to:
+
+1. Systematically retrieve data or other content from the Site to create or compile, directly or indirectly, a collection, compilation, database, or directory without written permission from us.
+
+2. Make any unauthorized use of the Site, including collecting usernames and/or email addresses of users by electronic or other means for the purpose of sending unsolicited email, or creating user accounts by automated means or under false pretenses.
+
+3. Use the Site to advertise or offer to sell goods and services.
+
+4. Circumvent, disable, or otherwise interfere with security-related features of the Site.
+
+5. Engage in unauthorized framing of or linking to the Site.
+
+6. Trick, defraud, or mislead us and other users, especially in any attempt to learn sensitive account information such as user passwords.
+
+7. Make improper use of our support services or submit false reports of abuse or misconduct.
+
+8. Engage in any automated use of the system, such as using scripts to send comments or messages, or using any data mining, robots, or similar data gathering and extraction tools.
+
+9. Interfere with, disrupt, or create an undue burden on the Site or the networks or services connected to the Site.
+
+10. Attempt to impersonate another user or person or use the username of another user.
+
+11. Use any information obtained from the Site in order to harass, abuse, or harm another person.
+
+12. Disparage, tarnish, or otherwise harm, in our opinion, us and/or the Site.
+
+13. Except as may be the result of standard search engine or Internet browser usage, use, launch, develop, or distribute any automated system, including without limitation, any spider, robot, cheat utility, scraper, or offline reader that accesses the Site, or using or launching any unauthorized script or other software.
+
+14. Upload or transmit (or attempt to upload or to transmit) any material that acts as a passive or active information collection or transmission mechanism, including without limitation, clear graphics interchange formats (“gifs”), 1×1 pixels, web bugs, cookies, or other similar devices (sometimes referred to as “spyware” or “passive collection mechanisms” or “pcms”).
+
+15. Upload or transmit (or attempt to upload or to transmit) viruses, Trojan horses, or other material, including excessive use of capital letters and spamming (continuous posting of repetitive text), that interferes with any party’s uninterrupted use and enjoyment of the Site or modifies, impairs, disrupts, alters, or interferes with the use, features, functions, operation, or maintenance of the Site.
+
+16. Harass, annoy, intimidate, or threaten any of our employees or agents engaged in providing any portion of the Site to you.
+
+17. Attempt to bypass any measures of the Site designed to prevent or restrict access to the Site, or any portion of the Site.
+
+
+## SUBMISSIONS
+
+You acknowledge and agree that any questions, comments, suggestions, ideas, feedback, or other information regarding the Site ("Submissions") provided by you to us are non-confidential and shall become our sole property. We shall own exclusive rights, including all intellectual property rights, and shall be entitled to the unrestricted use and dissemination of these Submissions for any lawful purpose, commercial or otherwise, without acknowledgment or compensation to you. You hereby waive all moral rights to any such Submissions, and you hereby warrant that any such Submissions are original with you or that you have the right to submit such Submissions. You agree there shall be no recourse against us for any alleged or actual infringement or misappropriation of any proprietary right in your Submissions.
+
+## THIRD-PARTY WEBSITES AND CONTENT
+
+The Site may contain (or you may be sent via the Site) links to other websites ("Third-Party Websites") as well as articles, photographs, text, graphics, pictures, designs, music, sound, video, information, applications, software, and other content or items belonging to or originating from third parties ("Third-Party Content"). Such Third-Party Websites and Third-Party Content are not investigated, monitored, or checked for accuracy, appropriateness, or completeness by us, and we are not responsible for any Third-Party Websites accessed through the Site or any Third-Party Content posted on, available through, or installed from the Site, including the content, accuracy, offensiveness, opinions, reliability, privacy practices, or other policies of or contained in the Third-Party Websites or the Third-Party Content. Inclusion of, linking to, or permitting the use or installation of any Third-Party Websites or any Third-Party Content does not imply approval or endorsement thereof by us. If you decide to leave the Site and access the Third-Party Websites or to use or install any Third-Party Content, you do so at your own risk, and you should be aware these Terms of Use no longer govern. You should review the applicable terms and policies, including privacy and data gathering practices, of any website to which you navigate from the Site or relating to any applications you use or install from the Site. Any purchases you make through Third-Party Websites will be through other websites and from other companies, and we take no responsibility whatsoever in relation to such purchases which are exclusively between you and the applicable third party. You agree and acknowledge that we do not endorse the products or services offered on Third-Party Websites and you shall hold us harmless from any harm caused by your purchase of such products or services. Additionally, you shall hold us harmless from any losses sustained by you or harm caused to you relating to or resulting in any way from any Third-Party Content or any contact with Third-Party Websites.
+
+
+## SITE MANAGEMENT
+
+We reserve the right, but not the obligation, to: (1) monitor the Site for violations of these Terms of Use; (2) take appropriate legal action against anyone who, in our sole discretion, violates the law or these Terms of Use, including without limitation, reporting such user to law enforcement authorities; (3) in our sole discretion and without limitation, refuse, restrict access to, limit the availability of, or disable (to the extent technologically feasible) any of your Contributions or any portion thereof; (4) in our sole discretion and without limitation, notice, or liability, to remove from the Site or otherwise disable all files and content that are excessive in size or are in any way burdensome to our systems; and (5) otherwise manage the Site in a manner designed to protect our rights and property and to facilitate the proper functioning of the Site.
+
+
+## PRIVACY POLICY
+
+We care about data privacy and security. Please review our [Privacy Policy](/privacy). By using the Site, you agree to be bound by our Privacy Policy, which is incorporated into these Terms of Use. Please be advised the Site is hosted in the United States. If you access the Site from the European Union, Asia, or any other region of the world with laws or other requirements governing personal data collection, use, or disclosure that differ from applicable laws in the United States, then through your continued use of the Site, you are transferring your data to the United States, and you expressly consent to have your data transferred to and processed in the United States. Further, we do not knowingly accept, request, or solicit information from children or knowingly market to children. Therefore, in accordance with the U.S. Children’s Online Privacy Protection Act, if we receive actual knowledge that anyone under the age of 13 has provided personal information to us without the requisite and verifiable parental consent, we will delete that information from the Site as quickly as is reasonably practical.
+
+## TERM AND TERMINATION
+
+These Terms of Use shall remain in full force and effect while you use the Site. WITHOUT LIMITING ANY OTHER PROVISION OF THESE TERMS OF USE, WE RESERVE THE RIGHT TO, IN OUR SOLE DISCRETION AND WITHOUT NOTICE OR LIABILITY, DENY ACCESS TO AND USE OF THE SITE (INCLUDING BLOCKING CERTAIN IP ADDRESSES), TO ANY PERSON FOR ANY REASON OR FOR NO REASON, INCLUDING WITHOUT LIMITATION FOR BREACH OF ANY REPRESENTATION, WARRANTY, OR COVENANT CONTAINED IN THESE TERMS OF USE OR OF ANY APPLICABLE LAW OR REGULATION. WE MAY TERMINATE YOUR USE OR PARTICIPATION IN THE SITE OR DELETE ANY CONTENT OR INFORMATION THAT YOU POSTED AT ANY TIME, WITHOUT WARNING, IN OUR SOLE DISCRETION.
+
+
+## MODIFICATIONS AND INTERRUPTIONS
+
+We reserve the right to change, modify, or remove the contents of the Site at any time or for any reason at our sole discretion without notice. However, we have no obligation to update any information on our Site. We also reserve the right to modify or discontinue all or part of the Site without notice at any time. We will not be liable to you or any third party for any modification, suspension, or discontinuance of the Site.
+
+We cannot guarantee the Site will be available at all times. We may experience hardware, software, or other problems or need to perform maintenance related to the Site, resulting in interruptions, delays, or errors. We reserve the right to change, revise, update, suspend, discontinue, or otherwise modify the Site at any time or for any reason without notice to you. You agree that we have no liability whatsoever for any loss, damage, or inconvenience caused by your inability to access or use the Site during any downtime or discontinuance of the Site. Nothing in these Terms of Use will be construed to obligate us to maintain and support the Site or to supply any corrections, updates, or releases in connection therewith.
+
+
+## GOVERNING LAW
+
+These Terms of Use and your use of the Site are governed by and construed in accordance with the laws of the State of Texas applicable to agreements made and to be entirely performed within the State of Texas, without regard to its conflict of law principles.
+
+
+## DISPUTE RESOLUTION
+
+### Informal Negotiations
+
+To expedite resolution and control the cost of any dispute, controversy, or claim related to these Terms of Use (each a "Dispute" and collectively, the “Disputes”) brought by either you or us (individually, a “Party” and collectively, the “Parties”), the Parties agree to first attempt to negotiate any Dispute (except those Disputes expressly provided below) informally for at least thirty (30) days before initiating arbitration. Such informal negotiations commence upon written notice from one Party to the other Party.
+
+
+### Binding Arbitration
+
+If the Parties are unable to resolve a Dispute through informal negotiations, the Dispute (except those Disputes expressly excluded below) will be finally and exclusively resolved by binding arbitration. YOU UNDERSTAND THAT WITHOUT THIS PROVISION, YOU WOULD HAVE THE RIGHT TO SUE IN COURT AND HAVE A JURY TRIAL. The arbitration shall be commenced and conducted under the Commercial Arbitration Rules of the American Arbitration Association ("AAA") and, where appropriate, the AAA’s Supplementary Procedures for Consumer Related Disputes ("AAA Consumer Rules"), both of which are available at the AAA website www.adr.org. Your arbitration fees and your share of arbitrator compensation shall be governed by the AAA Consumer Rules and, where appropriate, limited by the AAA Consumer Rules. If such costs are determined to by the arbitrator to be excessive, we will pay all arbitration fees and expenses. The arbitration may be conducted in person, through the submission of documents, by phone, or online. The arbitrator will make a decision in writing, but need not provide a statement of reasons unless requested by either Party. The arbitrator must follow applicable law, and any award may be challenged if the arbitrator fails to do so. Except where otherwise required by the applicable AAA rules or applicable law, the arbitration will take place in Travis County, Texas. Except as otherwise provided herein, the Parties may litigate in court to compel arbitration, stay proceedings pending arbitration, or to confirm, modify, vacate, or enter judgment on the award entered by the arbitrator.
+
+If for any reason, a Dispute proceeds in court rather than arbitration, the Dispute shall be commenced or prosecuted in the state and federal courts located in Travis County, Texas, and the Parties hereby consent to, and waive all defenses of lack of personal jurisdiction, and forum non conveniens with respect to venue and jurisdiction in such state and federal courts. Application of the United Nations Convention on Contracts for the International Sale of Goods and the the Uniform Computer Information Transaction Act (UCITA) are excluded from these Terms of Use.
+
+In no event shall any Dispute brought by either Party related in any way to the Site be commenced more than one (1) years after the cause of action arose. If this provision is found to be illegal or unenforceable, then neither Party will elect to arbitrate any Dispute falling within that portion of this provision found to be illegal or unenforceable and such Dispute shall be decided by a court of competent jurisdiction within the courts listed for jurisdiction above, and the Parties agree to submit to the personal jurisdiction of that court.
+
+
+### Restrictions
+
+The Parties agree that any arbitration shall be limited to the Dispute between the Parties individually. To the full extent permitted by law, (a) no arbitration shall be joined with any other proceeding; (b) there is no right or authority for any Dispute to be arbitrated on a class-action basis or to utilize class action procedures; and (c) there is no right or authority for any Dispute to be brought in a purported representative capacity on behalf of the general public or any other persons.
+
+
+### Exceptions to Informal Negotiations and Arbitration
+
+The Parties agree that the following Disputes are not subject to the above provisions concerning informal negotiations and binding arbitration: (a) any Disputes seeking to enforce or protect, or concerning the validity of, any of the intellectual property rights of a Party; (b) any Dispute related to, or arising from, allegations of theft, piracy, invasion of privacy, or unauthorized use; and (c) any claim for injunctive relief. If this provision is found to be illegal or unenforceable, then neither Party will elect to arbitrate any Dispute falling within that portion of this provision found to be illegal or unenforceable and such Dispute shall be decided by a court of competent jurisdiction within the courts listed for jurisdiction above, and the Parties agree to submit to the personal jurisdiction of that court.
+
+
+## CORRECTIONS
+
+There may be information on the Site that contains typographical errors, inaccuracies, or omissions. We reserve the right to correct any errors, inaccuracies, or omissions and to change or update the information on the Site at any time, without prior notice.
+
+
+## DISCLAIMER
+
+THE SITE IS PROVIDED ON AN AS-IS AND AS-AVAILABLE BASIS. YOU AGREE THAT YOUR USE OF THE SITE AND OUR SERVICES WILL BE AT YOUR SOLE RISK. TO THE FULLEST EXTENT PERMITTED BY LAW, WE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, IN CONNECTION WITH THE SITE AND YOUR USE THEREOF, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. WE MAKE NO WARRANTIES OR REPRESENTATIONS ABOUT THE ACCURACY OR COMPLETENESS OF THE SITE’S CONTENT OR THE CONTENT OF ANY WEBSITES LINKED TO THE SITE AND WE WILL ASSUME NO LIABILITY OR RESPONSIBILITY FOR ANY (1) ERRORS, MISTAKES, OR INACCURACIES OF CONTENT AND MATERIALS, (2) PERSONAL INJURY OR PROPERTY DAMAGE, OF ANY NATURE WHATSOEVER, RESULTING FROM YOUR ACCESS TO AND USE OF THE SITE, (3) ANY UNAUTHORIZED ACCESS TO OR USE OF OUR SECURE SERVERS AND/OR ANY AND ALL PERSONAL INFORMATION AND/OR FINANCIAL INFORMATION STORED THEREIN, (4) ANY INTERRUPTION OR CESSATION OF TRANSMISSION TO OR FROM THE SITE, (5) ANY BUGS, VIRUSES, TROJAN HORSES, OR THE LIKE WHICH MAY BE TRANSMITTED TO OR THROUGH THE SITE BY ANY THIRD PARTY, AND/OR (6) ANY ERRORS OR OMISSIONS IN ANY CONTENT AND MATERIALS OR FOR ANY LOSS OR DAMAGE OF ANY KIND INCURRED AS A RESULT OF THE USE OF ANY CONTENT POSTED, TRANSMITTED, OR OTHERWISE MADE AVAILABLE VIA THE SITE. WE DO NOT WARRANT, ENDORSE, GUARANTEE, OR ASSUME RESPONSIBILITY FOR ANY PRODUCT OR SERVICE ADVERTISED OR OFFERED BY A THIRD PARTY THROUGH THE SITE, ANY HYPERLINKED WEBSITE, OR ANY WEBSITE OR MOBILE APPLICATION FEATURED IN ANY BANNER OR OTHER ADVERTISING, AND WE WILL NOT BE A PARTY TO OR IN ANY WAY BE RESPONSIBLE FOR MONITORING ANY TRANSACTION BETWEEN YOU AND ANY THIRD-PARTY PROVIDERS OF PRODUCTS OR SERVICES. AS WITH THE PURCHASE OF A PRODUCT OR SERVICE THROUGH ANY MEDIUM OR IN ANY ENVIRONMENT, YOU SHOULD USE YOUR BEST JUDGMENT AND EXERCISE CAUTION WHERE APPROPRIATE.
+
+
+## LIMITATIONS OF LIABILITY
+
+IN NO EVENT WILL WE OR OUR DIRECTORS, EMPLOYEES, OR AGENTS BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, EXEMPLARY, INCIDENTAL, SPECIAL, OR PUNITIVE DAMAGES, INCLUDING LOST PROFIT, LOST REVENUE, LOSS OF DATA, OR OTHER DAMAGES ARISING FROM YOUR USE OF THE SITE, EVEN IF WE HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. NOTWITHSTANDING ANYTHING TO THE CONTRARY CONTAINED HEREIN, OUR LIABILITY TO YOU FOR ANY CAUSE WHATSOEVER AND REGARDLESS OF THE FORM OF THE ACTION, WILL AT ALL TIMES BE LIMITED TO THE AMOUNT PAID, IF ANY, BY YOU TO US DURING THE SIX (6) MONTH PERIOD PRIOR TO ANY CAUSE OF ACTION ARISING. CERTAIN STATE LAWS DO NOT ALLOW LIMITATIONS ON IMPLIED WARRANTIES OR THE EXCLUSION OR LIMITATION OF CERTAIN DAMAGES. IF THESE LAWS APPLY TO YOU, SOME OR ALL OF THE ABOVE DISCLAIMERS OR LIMITATIONS MAY NOT APPLY TO YOU, AND YOU MAY HAVE ADDITIONAL RIGHTS.
+
+
+## INDEMNIFICATION
+
+You agree to defend, indemnify, and hold us harmless, including our subsidiaries, affiliates, and all of our respective officers, agents, partners, and employees, from and against any loss, damage, liability, claim, or demand, including reasonable attorneys’ fees and expenses, made by any third party due to or arising out of: (1) use of the Site; (2) breach of these Terms of Use; (3) any breach of your representations and warranties set forth in these Terms of Use; (4) your violation of the rights of a third party, including but not limited to intellectual property rights; or (5) any overt harmful act toward any other user of the Site with whom you connected via the Site. Notwithstanding the foregoing, we reserve the right, at your expense, to assume the exclusive defense and control of any matter for which you are required to indemnify us, and you agree to cooperate, at your expense, with our defense of such claims. We will use reasonable efforts to notify you of any such claim, action, or proceeding which is subject to this indemnification upon becoming aware of it.
+
+
+## USER DATA
+
+We will maintain certain data that you transmit to the Site for the purpose of managing the performance of the Site, as well as data relating to your use of the Site. Although we perform regular routine backups of data, you are solely responsible for all data that you transmit or that relates to any activity you have undertaken using the Site. You agree that we shall have no liability to you for any loss or corruption of any such data, and you hereby waive any right of action against us arising from any such loss or corruption of such data.
+
+
+## ELECTRONIC COMMUNICATIONS, TRANSACTIONS, AND SIGNATURES
+
+Visiting the Site, sending us emails, and completing online forms constitute electronic communications. You consent to receive electronic communications, and you agree that all agreements, notices, disclosures, and other communications we provide to you electronically, via email and on the Site, satisfy any legal requirement that such communication be in writing. YOU HEREBY AGREE TO THE USE OF ELECTRONIC SIGNATURES, CONTRACTS, ORDERS, AND OTHER RECORDS, AND TO ELECTRONIC DELIVERY OF NOTICES, POLICIES, AND RECORDS OF TRANSACTIONS INITIATED OR COMPLETED BY US OR VIA THE SITE. You hereby waive any rights or requirements under any statutes, regulations, rules, ordinances, or other laws in any jurisdiction which require an original signature or delivery or retention of non-electronic records, or to payments or the granting of credits by any means other than electronic means.
+
+
+## CALIFORNIA USERS AND RESIDENTS
+
+If any complaint with us is not satisfactorily resolved, you can contact the Complaint Assistance Unit of the Division of Consumer Services of the California Department of Consumer Affairs in writing at 1625 North Market Blvd., Suite N 112, Sacramento, California 95834 or by telephone at (800) 952-5210 or (916) 445-1254.
+
+
+## MISCELLANEOUS
+
+These Terms of Use and any policies or operating rules posted by us on the Site or in respect to the Site constitute the entire agreement and understanding between you and us. Our failure to exercise or enforce any right or provision of these Terms of Use shall not operate as a waiver of such right or provision. These Terms of Use operate to the fullest extent permissible by law. We may assign any or all of our rights and obligations to others at any time. We shall not be responsible or liable for any loss, damage, delay, or failure to act caused by any cause beyond our reasonable control. If any provision or part of a provision of these Terms of Use is determined to be unlawful, void, or unenforceable, that provision or part of the provision is deemed severable from these Terms of Use and does not affect the validity and enforceability of any remaining provisions. There is no joint venture, partnership, employment or agency relationship created between you and us as a result of these Terms of Use or use of the Site. You agree that these Terms of Use will not be construed against us by virtue of having drafted them. You hereby waive any and all defenses you may have based on the electronic form of these Terms of Use and the lack of signing by the parties hereto to execute these Terms of Use.
+
+## CONTACT US
+
+In order to resolve a complaint regarding the Site or to receive further information regarding use of the Site, please contact us at:
+
+NumFOCUS, Inc. P.O. Box 90596 Austin, TX, USA 78709 info@numfocus.org +1 (512) 222-5449
+
+
+
From 003752f706c3a77867fa37e1266486172f3fb2c1 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:38:02 +0000
Subject: [PATCH 082/909] New translations privacy.md (Spanish)
---
content/es/privacy.md | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
create mode 100644 content/es/privacy.md
diff --git a/content/es/privacy.md b/content/es/privacy.md
new file mode 100644
index 0000000000..a3674dd48a
--- /dev/null
+++ b/content/es/privacy.md
@@ -0,0 +1,18 @@
+---
+title: Privacy Policy
+sidebar: false
+---
+
+**numpy.org** is operated by [NumFOCUS, Inc.](https://numfocus.org), the fiscal sponsor of the NumPy project. For the Privacy Policy of this website please refer to https://numfocus.org/privacy-policy.
+
+If you have any questions about the policy or NumFOCUS’s data collection, use, and disclosure practices, please contact the NumFOCUS staff at privacy@numfocus.org.
+
+
+
+
+
+
+
+
+
+
From 0c217298dec674cf05908dce07a5b80d97227487 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:38:04 +0000
Subject: [PATCH 083/909] New translations press-kit.md (Spanish)
---
content/es/press-kit.md | 8 ++++++++
1 file changed, 8 insertions(+)
create mode 100644 content/es/press-kit.md
diff --git a/content/es/press-kit.md b/content/es/press-kit.md
new file mode 100644
index 0000000000..2309040ad2
--- /dev/null
+++ b/content/es/press-kit.md
@@ -0,0 +1,8 @@
+---
+title: Press kit
+sidebar: false
+---
+
+We would like to make it easy for you to include the NumPy project identity in your next academic paper, course materials, or presentation.
+
+You will find several high-resolution versions of the NumPy logo [here](https://github.com/numpy/numpy/tree/master/branding/logo). Note that by using the numpy.org resources, you accept the [NumPy Code of Conduct](/code-of-conduct).
From 78cb3c10740b7dafe6e809c27b9879bc5bab8fd8 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:38:05 +0000
Subject: [PATCH 084/909] New translations learn.md (Spanish)
---
content/es/learn.md | 84 +++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 84 insertions(+)
create mode 100644 content/es/learn.md
diff --git a/content/es/learn.md b/content/es/learn.md
new file mode 100644
index 0000000000..264677ac48
--- /dev/null
+++ b/content/es/learn.md
@@ -0,0 +1,84 @@
+---
+title: Learn
+sidebar: false
+---
+
+**The official NumPy documentation lives [here](https://numpy.org/doc/stable).**
+
+Below is a curated collection of external resources. To contribute, see the [end of this page](#add-to-this-list).
+***
+
+## Beginners
+
+There's a ton of information about NumPy out there. If you are new, we'd strongly recommend these:
+
+ **Tutorials**
+
+* [NumPy Quickstart Tutorial](https://numpy.org/devdocs/user/quickstart.html)
+* [SciPy Lectures](https://scipy-lectures.org/) Besides covering NumPy, these lectures offer a broader introduction to the scientific Python ecosystem.
+* [NumPy: the absolute basics for beginners](https://numpy.org/devdocs/user/absolute_beginners.html)
+* [Machine Learning Plus - Introduction to ndarray](https://www.machinelearningplus.com/python/numpy-tutorial-part1-array-python-examples/)
+* [Edureka - Learn NumPy Arrays with Examples ](https://www.edureka.co/blog/python-numpy-tutorial/)
+* [Dataquest - NumPy Tutorial: Data Analysis with Python](https://www.dataquest.io/blog/numpy-tutorial-python/)
+* [NumPy tutorial *by Nicolas Rougier*](https://github.com/rougier/numpy-tutorial)
+* [Stanford CS231 *by Justin Johnson*](http://cs231n.github.io/python-numpy-tutorial/)
+* [NumPy User Guide](https://numpy.org/devdocs)
+
+ **Books**
+
+* [Guide to NumPy *by Travis E. Oliphant*](http://web.mit.edu/dvp/Public/numpybook.pdf) This is a free version 1 from 2006. For the latest copy (2015) see [here](https://www.barnesandnoble.com/w/guide-to-numpy-travis-e-oliphant-phd/1122853007).
+* [From Python to NumPy *by Nicolas P. Rougier*](https://www.labri.fr/perso/nrougier/from-python-to-numpy/)
+* [Elegant SciPy](https://www.amazon.com/Elegant-SciPy-Art-Scientific-Python/dp/1491922877) *by Juan Nunez-Iglesias, Stefan van der Walt, and Harriet Dashnow*
+
+You may also want to check out the [Goodreads list](https://www.goodreads.com/shelf/show/python-scipy) on the subject of "Python+SciPy." Most books there are about the "SciPy ecosystem," which has NumPy at its core.
+
+ **Videos**
+
+* [Introduction to Numerical Computing with NumPy](http://youtu.be/ZB7BZMhfPgk) *by Alex Chabot-Leclerc*
+
+***
+
+## Advanced
+
+Try these advanced resources for a better understanding of NumPy concepts like advanced indexing, splitting, stacking, linear algebra, and more.
+
+ **Tutorials**
+
+* [100 NumPy Exercises](http://www.labri.fr/perso/nrougier/teaching/numpy.100/index.html) *by Nicolas P. Rougier*
+* [An Introduction to NumPy and Scipy](https://engineering.ucsb.edu/~shell/che210d/numpy.pdf) *by M. Scott Shell*
+* [Numpy Medkits](http://mentat.za.net/numpy/numpy_advanced_slides/) *by Stéfan van der Walt*
+* [NumPy in Python (Advanced)](https://www.geeksforgeeks.org/numpy-python-set-2-advanced/)
+* [Advanced Indexing](https://www.tutorialspoint.com/numpy/numpy_advanced_indexing.htm)
+* [Machine Learning and Data Analytics with NumPy](https://www.machinelearningplus.com/python/numpy-tutorial-python-part2/)
+
+ **Books**
+
+* [Python Data Science Handbook](https://www.amazon.com/Python-Data-Science-Handbook-Essential/dp/1491912057) *by Jake Vanderplas*
+* [Python for Data Analysis](https://www.amazon.com/Python-Data-Analysis-Wrangling-IPython/dp/1491957662) *by Wes McKinney*
+* [Numerical Python: Scientific Computing and Data Science Applications with Numpy, SciPy, and Matplotlib](https://www.amazon.com/Numerical-Python-Scientific-Applications-Matplotlib/dp/1484242459) *by Robert Johansson*
+
+ **Videos**
+
+* [Advanced NumPy - broadcasting rules, strides, and advanced indexing](https://www.youtube.com/watch?v=cYugp9IN1-Q) *by Juan Nunuz-Iglesias*
+* [Advanced Indexing Operations in NumPy Arrays](https://www.youtube.com/watch?v=2WTDrSkQBng) *by Amuls Academy*
+
+***
+
+## NumPy Talks
+
+* [The Future of NumPy Indexing](https://www.youtube.com/watch?v=o0EacbIbf58) *by Jaime Fernández* (2016)
+* [Evolution of Array Computing in Python](https://www.youtube.com/watch?v=HVLPJnvInzM&t=10s) *by Ralf Gommers* (2019)
+* [NumPy: what has changed and what is going to change?](https://www.youtube.com/watch?v=YFLVQFjRmPY) *by Matti Picus* (2019)
+* [Inside NumPy](https://www.youtube.com/watch?v=dBTJD_FDVjU) *by Ralf Gommers, Sebastian Berg, Matti Picus, Tyler Reddy, Stefan van der Walt, Charles Harris* (2019)
+* [Brief Review of Array Computing in Python](https://www.youtube.com/watch?v=f176j2g2eNc) *by Travis Oliphant* (2019)
+
+***
+
+## Citing NumPy
+
+If NumPy has been significant in your research, and you would like to acknowledge the project in your academic publication, please see [this citation information](/citing-numpy).
+
+## Contribute to this list
+
+
+To add to this collection, submit a recommendation [via a pull request](https://github.com/numpy/numpy.org/blob/master/content/en/learn.md). Say why your recommendation deserves mention on this page and also which audience would benefit most.
From 8eff61bfc0c5995a25b40ddc4b6d0300ea1f1503 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:38:07 +0000
Subject: [PATCH 085/909] New translations install.md (Spanish)
---
content/es/install.md | 142 ++++++++++++++++++++++++++++++++++++++++++
1 file changed, 142 insertions(+)
create mode 100644 content/es/install.md
diff --git a/content/es/install.md b/content/es/install.md
new file mode 100644
index 0000000000..43dd44cb12
--- /dev/null
+++ b/content/es/install.md
@@ -0,0 +1,142 @@
+---
+title: Installing NumPy
+sidebar: false
+---
+
+The only prerequisite for installing NumPy is Python itself. If you don't have Python yet and want the simplest way to get started, we recommend you use the [Anaconda Distribution](https://www.anaconda.com/distribution) - it includes Python, NumPy, and many other commonly used packages for scientific computing and data science.
+
+NumPy can be installed with `conda`, with `pip`, with a package manager on macOS and Linux, or [from source](https://numpy.org/devdocs/user/building.html). For more detailed instructions, consult our [Python and NumPy installation guide](#python-numpy-install-guide) below.
+
+**CONDA**
+
+If you use `conda`, you can install NumPy from the `defaults` or `conda-forge` channels:
+
+```bash
+# Best practice, use an environment rather than install in the base env
+conda create -n my-env
+conda activate my-env
+# If you want to install from conda-forge
+conda config --env --add channels conda-forge
+# The actual install command
+conda install numpy
+```
+
+**PIP**
+
+If you use `pip`, you can install NumPy with:
+
+```bash
+pip install numpy
+```
+Also when using pip, it's good practice to use a virtual environment - see [Reproducible Installs](#reproducible-installs) below for why, and [this guide](https://dev.to/bowmanjd/python-tools-for-managing-virtual-environments-3bko#howto) for details on using virtual environments.
+
+
+
+# Python and NumPy installation guide
+
+Installing and managing packages in Python is complicated, there are a number of alternative solutions for most tasks. This guide tries to give the reader a sense of the best (or most popular) solutions, and give clear recommendations. It focuses on users of Python, NumPy, and the PyData (or numerical computing) stack on common operating systems and hardware.
+
+## Recommendations
+
+We'll start with recommendations based on the user's experience level and operating system of interest. If you're in between "beginning" and "advanced", please go with "beginning" if you want to keep things simple, and with "advanced" if you want to work according to best practices that go a longer way in the future.
+
+### Beginning users
+
+On all of Windows, macOS, and Linux:
+
+- Install [Anaconda](https://www.anaconda.com/distribution/) (it installs all packages you need and all other tools mentioned below).
+- For writing and executing code, use notebooks in [JupyterLab](https://jupyterlab.readthedocs.io/en/stable/index.html) for exploratory and interactive computing, and [Spyder](https://www.spyder-ide.org/) or [Visual Studio Code](https://code.visualstudio.com/) for writing scripts and packages.
+- Use [Anaconda Navigator](https://docs.anaconda.com/anaconda/navigator/) to manage your packages and start JupyterLab, Spyder, or Visual Studio Code.
+
+
+### Advanced users
+
+#### Windows or macOS
+
+- Install [Miniconda](https://docs.conda.io/en/latest/miniconda.html).
+- Keep the `base` conda environment minimal, and use one or more [conda environments](https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#) to install the package you need for the task or project you're working on.
+- Unless you're fine with only the packages in the `defaults` channel, make `conda-forge` your default channel via [setting the channel priority](https://conda-forge.org/docs/user/introduction.html#how-can-i-install-packages-from-conda-forge).
+
+
+#### Linux
+
+If you're fine with slightly outdated packages and prefer stability over being able to use the latest versions of libraries:
+- Use your OS package manager for as much as possible (Python itself, NumPy, and other libraries).
+- Install packages not provided by your package manager with `pip install somepackage --user`.
+
+If you use a GPU:
+- Install [Miniconda](https://docs.conda.io/en/latest/miniconda.html).
+- Keep the `base` conda environment minimal, and use one or more [conda environments](https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#) to install the package you need for the task or project you're working on.
+- Use the `defaults` conda channel (`conda-forge` doesn't have good support for GPU packages yet).
+
+Otherwise:
+- Install [Miniforge](https://github.com/conda-forge/miniforge).
+- Keep the `base` conda environment minimal, and use one or more [conda environments](https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#) to install the package you need for the task or project you're working on.
+
+
+#### Alternative if you prefer pip/PyPI
+
+For users who know, from personal preference or reading about the main differences between conda and pip below, they prefer a pip/PyPI-based solution, we recommend:
+- Install Python from, for example, [python.org](https://www.python.org/downloads/), [Homebrew](https://brew.sh/), or your Linux package manager.
+- Use [Poetry](https://python-poetry.org/) as the most well-maintained tool that provides a dependency resolver and environment management capabilities in a similar fashion as conda does.
+
+
+## Python package management
+
+Managing packages is a challenging problem, and, as a result, there are lots of tools. For web and general purpose Python development there's a whole [host of tools](https://packaging.python.org/guides/tool-recommendations/) complementary with pip. For high-performance computing (HPC), [Spack](https://github.com/spack/spack) is worth considering. For most NumPy users though, [conda](https://conda.io/en/latest/) and [pip](https://pip.pypa.io/en/stable/) are the two most popular tools.
+
+
+### Pip & conda
+
+The two main tools that install Python packages are `pip` and `conda`. Their functionality partially overlaps (e.g. both can install `numpy`), however, they can also work together. We'll discuss the major differences between pip and conda here - this is important to understand if you want to manage packages effectively.
+
+The first difference is that conda is cross-language and it can install Python, while pip is installed for a particular Python on your system and installs other packages to that same Python install only. This also means conda can install non-Python libraries and tools you may need (e.g. compilers, CUDA, HDF5), while pip can't.
+
+The second difference is that pip installs from the Python Packaging Index (PyPI), while conda installs from its own channels (typically "defaults" or "conda-forge"). PyPI is the largest collection of packages by far, however, all popular packages are available for conda as well.
+
+The third difference is that conda is an integrated solution for managing packages, dependencies and environments, while with pip you may need another tool (there are many!) for dealing with environments or complex dependencies.
+
+
+### Reproducible installs
+
+As libraries get updated, results from running your code can change, or your code can break completely. It's important to be able to reconstruct the set of packages and versions you're using. Best practice is to:
+
+1. use a different environment per project you're working on,
+2. record package names and versions using your package installer; each has its own metadata format for this:
+ - Conda: [conda environments and environment.yml](https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#)
+ - Pip: [virtual environments](https://docs.python.org/3/tutorial/venv.html) and [requirements.txt](https://pip.readthedocs.io/en/latest/user_guide/#requirements-files)
+ - Poetry: [virtual environments and pyproject.toml](https://python-poetry.org/docs/basic-usage/)
+
+
+
+## NumPy packages & accelerated linear algebra libraries
+
+NumPy doesn't depend on any other Python packages, however, it does depend on an accelerated linear algebra library - typically [Intel MKL](https://software.intel.com/en-us/mkl) or [OpenBLAS](https://www.openblas.net/). Users don't have to worry about installing those (they're automatically included in all NumPy install methods). Power users may still want to know the details, because the used BLAS can affect performance, behavior and size on disk:
+
+- The NumPy wheels on PyPI, which is what pip installs, are built with OpenBLAS. The OpenBLAS libraries are included in the wheel. This makes the wheel larger, and if a user installs (for example) SciPy as well, they will now have two copies of OpenBLAS on disk.
+
+- In the conda defaults channel, NumPy is built against Intel MKL. MKL is a separate package that will be installed in the users' environment when they install NumPy.
+
+- In the conda-forge channel, NumPy is built against a dummy "BLAS" package. When a user installs NumPy from conda-forge, that BLAS package then gets installed together with the actual library - this defaults to OpenBLAS, but it can also be MKL (from the defaults channel), or even [BLIS](https://github.com/flame/blis) or reference BLAS.
+
+- The MKL package is a lot larger than OpenBLAS, it's about 700 MB on disk while OpenBLAS is about 30 MB.
+
+- MKL is typically a little faster and more robust than OpenBLAS.
+
+Besides install sizes, performance and robustness, there are two more things to consider:
+
+- Intel MKL is not open source. For normal use this is not a problem, but if a user needs to redistribute an application built with NumPy, this could be an issue.
+- Both MKL and OpenBLAS will use multi-threading for function calls like `np.dot`, with the number of threads being determined by both a build-time option and an environment variable. Often all CPU cores will be used. This is sometimes unexpected for users; NumPy itself doesn't auto-parallelize any function calls. It typically yields better performance, but can also be harmful - for example when using another level of parallelization with Dask, scikit-learn or multiprocessing.
+
+
+## Troubleshooting
+
+If your installation fails with the message below, see [Troubleshooting ImportError](https://numpy.org/doc/stable/user/troubleshooting-importerror.html).
+
+```
+IMPORTANT: PLEASE READ THIS FOR ADVICE ON HOW TO SOLVE THIS ISSUE!
+
+Importing the numpy c-extensions failed. This error can happen for
+different reasons, often due to issues with your setup.
+```
+
From c596d42b7dba8e3633152b56491e8a3210f187bf Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:38:09 +0000
Subject: [PATCH 086/909] New translations code-of-conduct.md (Spanish)
---
content/es/code-of-conduct.md | 83 +++++++++++++++++++++++++++++++++++
1 file changed, 83 insertions(+)
create mode 100644 content/es/code-of-conduct.md
diff --git a/content/es/code-of-conduct.md b/content/es/code-of-conduct.md
new file mode 100644
index 0000000000..efcde754ae
--- /dev/null
+++ b/content/es/code-of-conduct.md
@@ -0,0 +1,83 @@
+---
+title: NumPy Code of Conduct
+sidebar: false
+aliases:
+ - /conduct.html
+---
+
+### Introduction
+
+This Code of Conduct applies to all spaces managed by the NumPy project, including all public and private mailing lists, issue trackers, wikis, blogs, Twitter, and any other communication channel used by our community. The NumPy project does not organise in-person events, however events related to our community should have a code of conduct similar in spirit to this one.
+
+This Code of Conduct should be honored by everyone who participates in the NumPy community formally or informally, or claims any affiliation with the project, in any project-related activities and especially when representing the project, in any role.
+
+This code is not exhaustive or complete. It serves to distill our common understanding of a collaborative, shared environment and goals. Please try to follow this code in spirit as much as in letter, to create a friendly and productive environment that enriches the surrounding community.
+
+### Specific Guidelines
+
+We strive to:
+
+1. Be open. We invite anyone to participate in our community. We prefer to use public methods of communication for project-related messages, unless discussing something sensitive. This applies to messages for help or project-related support, too; not only is a public support request much more likely to result in an answer to a question, it also ensures that any inadvertent mistakes in answering are more easily detected and corrected.
+2. Be empathetic, welcoming, friendly, and patient. We work together to resolve conflict, and assume good intentions. We may all experience some frustration from time to time, but we do not allow frustration to turn into a personal attack. A community where people feel uncomfortable or threatened is not a productive one.
+3. Be collaborative. Our work will be used by other people, and in turn we will depend on the work of others. When we make something for the benefit of the project, we are willing to explain to others how it works, so that they can build on the work to make it even better. Any decision we make will affect users and colleagues, and we take those consequences seriously when making decisions.
+4. Be inquisitive. Nobody knows everything! Asking questions early avoids many problems later, so we encourage questions, although we may direct them to the appropriate forum. We will try hard to be responsive and helpful.
+5. Be careful in the words that we choose. We are careful and respectful in our communication, and we take responsibility for our own speech. Be kind to others. Do not insult or put down other participants. We will not accept harassment or other exclusionary behaviour, such as:
+ * Violent threats or language directed against another person.
+ * Sexist, racist, or otherwise discriminatory jokes and language.
+ * Posting sexually explicit or violent material.
+ * Posting (or threatening to post) other people’s personally identifying information (“doxing”).
+ * Sharing private content, such as emails sent privately or non-publicly, or unlogged forums such as IRC channel history, without the sender’s consent.
+ * Personal insults, especially those using racist or sexist terms.
+ * Unwelcome sexual attention.
+ * Excessive profanity. Please avoid swearwords; people differ greatly in their sensitivity to swearing.
+ * Repeated harassment of others. In general, if someone asks you to stop, then stop.
+ * Advocating for, or encouraging, any of the above behaviour.
+
+### Diversity Statement
+
+The NumPy project welcomes and encourages participation by everyone. We are committed to being a community that everyone enjoys being part of. Although we may not always be able to accommodate each individual’s preferences, we try our best to treat everyone kindly.
+
+No matter how you identify yourself or how others perceive you: we welcome you. Though no list can hope to be comprehensive, we explicitly honour diversity in: age, culture, ethnicity, genotype, gender identity or expression, language, national origin, neurotype, phenotype, political beliefs, profession, race, religion, sexual orientation, socioeconomic status, subculture and technical ability, to the extent that these do not conflict with this code of conduct.
+
+Though we welcome people fluent in all languages, NumPy development is conducted in English.
+
+Standards for behaviour in the NumPy community are detailed in the Code of Conduct above. Participants in our community should uphold these standards in all their interactions and help others to do so as well (see next section).
+
+### Reporting Guidelines
+
+We know that it is painfully common for internet communication to start at or devolve into obvious and flagrant abuse. We also recognize that sometimes people may have a bad day, or be unaware of some of the guidelines in this Code of Conduct. Please keep this in mind when deciding on how to respond to a breach of this Code.
+
+For clearly intentional breaches, report those to the Code of Conduct Committee (see below). For possibly unintentional breaches, you may reply to the person and point out this code of conduct (either in public or in private, whatever is most appropriate). If you would prefer not to do that, please feel free to report to the Code of Conduct Committee directly, or ask the Committee for advice, in confidence.
+
+You can report issues to the NumPy Code of Conduct Committee at numpy-conduct@googlegroups.com.
+
+Currently, the Committee consists of:
+
+* Stefan van der Walt
+* Melissa Weber Mendonça
+* Anirudh Subramanian
+
+If your report involves any members of the Committee, or if they feel they have a conflict of interest in handling it, then they will recuse themselves from considering your report. Alternatively, if for any reason you feel uncomfortable making a report to the Committee, then you can also contact senior NumFOCUS staff at [conduct@numfocus.org](https://numfocus.org/code-of-conduct#persons-responsible).
+
+### Incident reporting resolution & Code of Conduct enforcement
+
+_This section summarizes the most important points, more details can be found in_ [NumPy Code of Conduct - How to follow up on a report](/report-handling-manual).
+
+We will investigate and respond to all complaints. The NumPy Code of Conduct Committee and the NumPy Steering Committee (if involved) will protect the identity of the reporter, and treat the content of complaints as confidential (unless the reporter agrees otherwise).
+
+In case of severe and obvious breaches, e.g. personal threat or violent, sexist or racist language, we will immediately disconnect the originator from NumPy communication channels; please see the manual for details.
+
+In cases not involving clear severe and obvious breaches of this Code of Conduct the process for acting on any received Code of Conduct violation report will be:
+
+1. acknowledge report is received,
+2. reasonable discussion/feedback,
+3. mediation (if feedback didn’t help, and only if both reporter and reportee agree to this),
+4. enforcement via transparent decision (see [Resolutions](/report-handling-manual#resolutions)) by the Code of Conduct Committee.
+
+The Committee will respond to any report as soon as possible, and at most within 72 hours.
+
+### Endnotes
+
+We are thankful to the groups behind the following documents, from which we drew content and inspiration:
+
+- [The SciPy Code of Conduct](https://docs.scipy.org/doc/scipy/reference/dev/conduct/code_of_conduct.html)
From db8ac7d00cfb11d83993a95b79fc5ed2d115cff1 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:38:11 +0000
Subject: [PATCH 087/909] New translations citing-numpy.md (Spanish)
---
content/es/citing-numpy.md | 35 +++++++++++++++++++++++++++++++++++
1 file changed, 35 insertions(+)
create mode 100644 content/es/citing-numpy.md
diff --git a/content/es/citing-numpy.md b/content/es/citing-numpy.md
new file mode 100644
index 0000000000..cf20ae59cf
--- /dev/null
+++ b/content/es/citing-numpy.md
@@ -0,0 +1,35 @@
+---
+title: Citing NumPy
+sidebar: false
+---
+
+If NumPy has been significant in your research, and you would like to acknowledge the project in your academic publication, we suggest citing the following paper:
+
+* Harris, C.R., Millman, K.J., van der Walt, S.J. et al. _Array programming with NumPy_. Nature 585, 357–362 (2020). DOI: [0.1038/s41586-020-2649-2](https://doi.org/10.1038/s41586-020-2649-2). ([Publisher link](https://www.nature.com/articles/s41586-020-2649-2)).
+
+_In BibTeX format:_
+
+ ```
+@Article{ harris2020array,
+ title = {Array programming with {NumPy}},
+ author = {Charles R. Harris and K. Jarrod Millman and St{'{e}}fan J.
+ van der Walt and Ralf Gommers and Pauli Virtanen and David
+ Cournapeau and Eric Wieser and Julian Taylor and Sebastian
+ Berg and Nathaniel J. Smith and Robert Kern and Matti Picus
+ and Stephan Hoyer and Marten H. van Kerkwijk and Matthew
+ Brett and Allan Haldane and Jaime Fern{'{a}}ndez del
+ R{'{\i}}o and Mark Wiebe and Pearu Peterson and Pierre
+ G{'{e}}rard-Marchant and Kevin Sheppard and Tyler Reddy and
+ Warren Weckesser and Hameer Abbasi and Christoph Gohlke and
+ Travis E. Oliphant},
+ year = {2020},
+ month = sep,
+ journal = {Nature},
+ volume = {585},
+ number = {7825},
+ pages = {357--362},
+ doi = {10.1038/s41586-020-2649-2},
+ publisher = {Springer Science and Business Media {LLC}},
+ url = {https://doi.org/10.1038/s41586-020-2649-2}
+}
+```
From bb05dbfdbf93720422cfa3bb489b9df1784d3481 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:38:12 +0000
Subject: [PATCH 088/909] New translations arraycomputing.md (Spanish)
---
content/es/arraycomputing.md | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
create mode 100644 content/es/arraycomputing.md
diff --git a/content/es/arraycomputing.md b/content/es/arraycomputing.md
new file mode 100644
index 0000000000..abd29d11c1
--- /dev/null
+++ b/content/es/arraycomputing.md
@@ -0,0 +1,21 @@
+---
+title: Array Computing
+sidebar: false
+---
+
+*Array computing is the foundation of statistical, mathematical, scientific computing in various contemporary data science and analytics applications such as data visualization, digital signal processing, image processing, bioinformatics, machine learning, AI, and several others.*
+
+Large scale data manipulation and transformation depends on efficient, high-performance array computing. The language of choice for data analytics, machine learning, and productive numerical computing is **Python.**
+
+**Num**erical **Py**thon or NumPy is its de-facto standard Python programming language library that supports large, multi-dimensional arrays and matrices, and comes with a vast collection of high-level mathematical functions to operate on these arrays.
+
+Since the launch of NumPy in 2006, Pandas appeared on the landscape in 2008, and it was not until a couple of years ago that several array computing libraries showed up in succession, crowding the array computing landscape. Many of these newer libraries mimic NumPy-like features and capabilities, and pack newer algorithms and features geared towards machine learning and artificial intelligence applications.
+
+
+
+**Array computing** is based on **arrays** data structures. *Arrays* are used to organize vast amounts of data such that a related set of values can be easily sorted, searched, mathematically manipulated, and transformed easily and quickly.
+
+Array computing is *unique* as it involves operating on the data array *at once*. What this means is that any array operation applies to an entire set of values in one shot. This vectorized approach provides speed and simplicity by enabling programmers to code and operate on aggregates of data, without having to use loops of individual scalar operations.
From 3cad8c76cb072e7565dc75d04cfff2fa988b3b3e Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:38:14 +0000
Subject: [PATCH 089/909] New translations about.md (Spanish)
---
content/es/about.md | 69 +++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 69 insertions(+)
create mode 100644 content/es/about.md
diff --git a/content/es/about.md b/content/es/about.md
new file mode 100644
index 0000000000..df89bff1f5
--- /dev/null
+++ b/content/es/about.md
@@ -0,0 +1,69 @@
+---
+title: About Us
+sidebar: false
+---
+
+_Some information about the NumPy project and community_
+
+NumPy is an open source project aiming to enable numerical computing with Python. It was created in 2005, building on the early work of the Numerical and Numarray libraries. NumPy will always be 100% open source software, free for all to use and released under the liberal terms of the [modified BSD license](https://github.com/numpy/numpy/blob/master/LICENSE.txt).
+
+NumPy is developed in the open on GitHub, through the consensus of the NumPy and wider scientific Python community. For more information on our governance approach, please see our [Governance Document](https://www.numpy.org/devdocs/dev/governance/index.html).
+
+
+## Steering Council
+
+The role of the NumPy Steering Council is to ensure, through working with and serving the broader NumPy community, the long-term well-being of the project, both technically and as a community. The NumPy Steering Council currently consists of the following members (in alphabetical order):
+
+- Sebastian Berg
+- Jaime Fernández del Río
+- Ralf Gommers
+- Allan Haldane
+- Charles Harris
+- Stephan Hoyer
+- Matti Picus
+- Nathaniel Smith
+- Julian Taylor
+- Pauli Virtanen
+- Stéfan van der Walt
+- Eric Wieser
+
+Emeritus:
+
+- Travis Oliphant (project founder, 2005-2012)
+- Alex Griffing (2015-2017)
+- Marten van Kerkwijk (2017-2019)
+
+## Teams
+
+The NumPy project is growing; we have teams for
+
+- code
+- documentation
+- website
+- triage
+- funding and grants
+
+See the [Team](/gallery/team.html) page for individual team members.
+
+## Sponsors
+
+NumPy receives direct funding from the following sources:
+{{< sponsors >}}
+
+
+## Institutional Partners
+
+Institutional Partners are organizations that support the project by employing people that contribute to NumPy as part of their job. Current Institutional Partners include:
+{{< partners >}}
+
+
+## Donate
+
+If you have found NumPy useful in your work, research, or company, please consider a donation to the project commensurate with your resources. Any amount helps! All donations will be used strictly to fund the development of NumPy’s open source software, documentation, and community.
+
+NumPy is a Sponsored Project of NumFOCUS, a 501(c)(3) nonprofit charity in the United States. NumFOCUS provides NumPy with fiscal, legal, and administrative support to help ensure the health and sustainability of the project. Visit [numfocus.org](https://numfocus.org) for more information.
+
+Donations to NumPy are managed by [NumFOCUS](https://numfocus.org). For donors in the United States, your gift is tax-deductible to the extent provided by law. As with any donation, you should consult with your tax advisor about your particular tax situation.
+
+NumPy's Steering Council will make the decisions on how to best use any funds received. Technical and infrastructure priorities are documented on the [NumPy Roadmap](https://www.numpy.org/neps/index.html#roadmap).
+{{< numfocus >}}
From e48e69c74b61313950f3d86c9cb3885385a77157 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:38:16 +0000
Subject: [PATCH 090/909] New translations 404.md (Spanish)
---
content/es/404.md | 8 ++++++++
1 file changed, 8 insertions(+)
create mode 100644 content/es/404.md
diff --git a/content/es/404.md b/content/es/404.md
new file mode 100644
index 0000000000..e0e7272719
--- /dev/null
+++ b/content/es/404.md
@@ -0,0 +1,8 @@
+---
+title: 404
+sidebar: false
+---
+
+¡Ups! Has llegado a un callejón sin salida.
+
+Si crees que algo debería estar aquí, puedes [reportar este problema](https://github.com/numpy/numpy.org/issues) en GitHub.
From 66727e8d040583932c3031cb39ae5031bb6342d3 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:38:18 +0000
Subject: [PATCH 091/909] New translations community.md (Portuguese, Brazilian)
---
content/pt/community.md | 65 +++++++++++++++++++++++++++++++++++++++++
1 file changed, 65 insertions(+)
create mode 100644 content/pt/community.md
diff --git a/content/pt/community.md b/content/pt/community.md
new file mode 100644
index 0000000000..14c5f35420
--- /dev/null
+++ b/content/pt/community.md
@@ -0,0 +1,65 @@
+---
+title: Comunidade
+sidebar: false
+---
+
+NumPy é um projeto de código aberto impulsionado pela comunidade desenvolvido por um grupo muito diversificado de [contribuidores](/gallery/team.html). A liderança da NumPy assumiu um forte compromisso de criar uma comunidade aberta, inclusiva e positiva. Por favor, leia [o Código de Conduta NumPy](/code-of-conduct) para orientações sobre como interagir com os outros de uma forma que faça a comunidade prosperar.
+
+Oferecemos vários canais de comunicação para aprender, compartilhar seu conhecimento e se conectar com outros dentro da comunidade NumPy.
+
+
+## Participar online
+
+Abaixo, listamos algumas formas de se envolver diretamente com o projeto e a comunidade do NumPy. _Por favor, note que encorajamos os usuários e membros da comunidade a apoiarem-se uns aos outros para perguntas sobre utilização - veja [Obter Ajuda](/gethelp)._
+
+
+### [Lista de discussões NumPy](https://mail.python.org/mailman/listinfo/numpy-discussion)
+
+Esta lista é o principal fórum para discussões mais longas, como adicionar novos recursos ao NumPy, fazer alterações no roadmap do NumPy e em todos os tipos de tomada de decisão para todo o projeto. Anúncios sobre o NumPy, como novas versões, reuniões de desenvolvedores, sprints ou palestras de conferência também são feitas nesta lista.
+
+Nesta lista, por favor, use *bottom posting*, responda à lista (em vez de a outro remetente), e não responda aos *digests*. Um arquivo pesquisável desta lista está disponível [aqui](http://numpy-discussion.10968.n7.nabble.com/).
+
+***
+
+### [Página de issues do GitHub](https://github.com/numpy/numpy/issues)
+
+- Para relatórios de bugs (por exemplo, "`np.arange(3).shape` retorna `(5,)`, quando deveria retornar `(3,)`");
+- problemas de documentação (ex. "Eu achei esta seção confusa");
+- e pedidos de recursos (por exemplo, "Eu gostaria de ter um novo método de interpolação em `np.percentile`").
+
+_Por favor, note que o GitHub não é o lugar certo para relatar uma vulnerabilidade de segurança. Se você acha que encontrou uma vulnerabilidade de segurança no NumPy, relate-a [aqui](https://tidelift.com/docs/security)._
+
+***
+
+### [Slack](https://numpy-team.slack.com)
+
+Uma sala de bate-papo em tempo real para fazer perguntas sobre _contribuir_ para o NumPy. Este é um fórum privado, especificamente para pessoas hesitantes em levantar suas perguntas ou idéias em uma grande lista de e-mails públicos ou no GitHub. Por favor, clique [aqui](https://numpy.org/devdocs/dev/index.html#contributing-to-numpy) para mais detalhes e como obter um convite.
+
+
+## Grupos de Estudo e Meetups
+
+Se você gostaria de encontrar um encontro ou grupo de estudo local para aprender mais sobre o NumPy e o ecossistema mais amplo de pacotes Python para ciência de dados e computação científica, recomendamos explorar os [meetups PyData](https://www.meetup.com/pro/pydata/) (mais de 150 encontros, mais de 100.000 membros).
+
+O NumPy também organiza sprints presenciais para sua equipe e colaboradores interessados ocasionalmente. Estes eventos são normalmente planejados com vários meses de antecedência e serão anunciados na [lista de discussão](https://mail.python.org/mailman/listinfo/numpy-discussion) e no [Twitter](https://twitter.com/numpy_team).
+
+
+## Conferências
+
+O projeto NumPy não organiza suas próprias conferências. As conferências que tradicionalmente têm sido mais populares com mantenedores, colaboradores e usuários são as conferências SciPy e PyData:
+
+- [SciPy US](https://conference.scipy.org)
+- [EuroSciPy](https://www.euroscipy.org)
+- [SciPy Latin America](https://www.scipyla.org)
+- [SciPy India](https://scipy.in)
+- [SciPy Japan](https://conference.scipy.org)
+- [conferências PyData](https://pydata.org/event-schedule/) (15-20 eventos por ano espalhados por muitos países)
+
+Muitas dessas conferências incluem dias de tutorial sobre o NumPy e/ou sprints onde você pode aprender como contribuir com o NumPy ou projetos de código aberto relacionados.
+
+
+## Junte-se à comunidade NumPy
+
+Para prosperar, o projeto NumPy precisa de sua experiência e entusiasmo. Não é uma pessoa programadora? Sem problemas! Existem muitas maneiras de contribuir com o NumPy.
+
+Se você está interessado em se tornar um contribuidor do NumPy (oba!) recomendamos que você confira nossa página sobre [Contribuições](/contribute).
+
From 38c3c300a19d089448e9f366df201517ae30c056 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:38:19 +0000
Subject: [PATCH 092/909] New translations community.md (Chinese Simplified)
---
content/zh/community.md | 65 +++++++++++++++++++++++++++++++++++++++++
1 file changed, 65 insertions(+)
create mode 100644 content/zh/community.md
diff --git a/content/zh/community.md b/content/zh/community.md
new file mode 100644
index 0000000000..4e24a83784
--- /dev/null
+++ b/content/zh/community.md
@@ -0,0 +1,65 @@
+---
+title: Community
+sidebar: false
+---
+
+NumPy is a community-driven open source project developed by a very diverse group of [contributors](/gallery/team.html). The NumPy leadership has made a strong commitment to creating an open, inclusive, and positive community. Please read the [NumPy Code of Conduct](/code-of-conduct) for guidance on how to interact with others in a way that makes the community thrive.
+
+We offer several communication channels to learn, share your knowledge and connect with others within the NumPy community.
+
+
+## Participate online
+
+The following are ways to engage directly with the NumPy project and community. _Please note that we encourage users and community members to support each other for usage questions - see [Get Help](/gethelp)._
+
+
+### [NumPy mailing list](https://mail.python.org/mailman/listinfo/numpy-discussion)
+
+This list is the main forum for longer-form discussions, like adding new features to NumPy, making changes to the NumPy Roadmap, and all kinds of project-wide decision making. Announcements about NumPy, such as for releases, developer meetings, sprints or conference talks are also made on this list.
+
+On this list please use bottom posting, reply to the list (rather than to another sender), and don't reply to digests. A searchable archive of this list is available [here](http://numpy-discussion.10968.n7.nabble.com/).
+
+***
+
+### [GitHub issue tracker](https://github.com/numpy/numpy/issues)
+
+- For bug reports (e.g. "`np.arange(3).shape` returns `(5,)`, when it should return `(3,)`");
+- documentation issues (e.g. "I found this section unclear");
+- and feature requests (e.g. "I would like to have a new interpolation method in `np.percentile`").
+
+_Please note that GitHub is not the right place to report a security vulnerability. If you think you have found a security vulnerability in NumPy, please report it [here](https://tidelift.com/docs/security)._
+
+***
+
+### [Slack](https://numpy-team.slack.com)
+
+A real-time chat room to ask questions about _contributing_ to NumPy. This is a private space, specifically meant for people who are hesitant to bring up their questions or ideas on a large public mailing list or GitHub. Please see [here](https://numpy.org/devdocs/dev/index.html#contributing-to-numpy) for more details and how to get an invite.
+
+
+## Study Groups and Meetups
+
+If you would like to find a local meetup or study group to learn more about NumPy and the wider ecosystem of Python packages for data science and scientific computing, we recommend exploring the [PyData meetups](https://www.meetup.com/pro/pydata/) (150+ meetups, 100,000+ members).
+
+NumPy also organizes in-person sprints for its team and interested contributors occasionally. These are typically planned several months in advance and will be announced on the [mailing list](https://mail.python.org/mailman/listinfo/numpy-discussion) and [Twitter](https://twitter.com/numpy_team).
+
+
+## Conferences
+
+The NumPy project doesn't organize its own conferences. The conferences that have traditionally been most popular with NumPy maintainers, contributors and users are the SciPy and PyData conference series:
+
+- [SciPy US](https://conference.scipy.org)
+- [EuroSciPy](https://www.euroscipy.org)
+- [SciPy Latin America](https://www.scipyla.org)
+- [SciPy India](https://scipy.in)
+- [SciPy Japan](https://conference.scipy.org)
+- [PyData conferences](https://pydata.org/event-schedule/) (15-20 events a year spread over many countries)
+
+Many of these conferences include tutorial days that cover NumPy and/or sprints where you can learn how to contribute to NumPy or related open source projects.
+
+
+## Join the NumPy community
+
+To thrive, the NumPy project needs your expertise and enthusiasm. Not a coder? Not a problem! There are many ways to contribute to NumPy.
+
+If you are interested in becoming a NumPy contributor (yay!) we recommend checking out our [Contribute](/contribute) page.
+
From 032016043d3dba50ec0d765de78848c73d3f5c82 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:38:21 +0000
Subject: [PATCH 093/909] New translations community.md (Korean)
---
content/ko/community.md | 65 +++++++++++++++++++++++++++++++++++++++++
1 file changed, 65 insertions(+)
create mode 100644 content/ko/community.md
diff --git a/content/ko/community.md b/content/ko/community.md
new file mode 100644
index 0000000000..4e24a83784
--- /dev/null
+++ b/content/ko/community.md
@@ -0,0 +1,65 @@
+---
+title: Community
+sidebar: false
+---
+
+NumPy is a community-driven open source project developed by a very diverse group of [contributors](/gallery/team.html). The NumPy leadership has made a strong commitment to creating an open, inclusive, and positive community. Please read the [NumPy Code of Conduct](/code-of-conduct) for guidance on how to interact with others in a way that makes the community thrive.
+
+We offer several communication channels to learn, share your knowledge and connect with others within the NumPy community.
+
+
+## Participate online
+
+The following are ways to engage directly with the NumPy project and community. _Please note that we encourage users and community members to support each other for usage questions - see [Get Help](/gethelp)._
+
+
+### [NumPy mailing list](https://mail.python.org/mailman/listinfo/numpy-discussion)
+
+This list is the main forum for longer-form discussions, like adding new features to NumPy, making changes to the NumPy Roadmap, and all kinds of project-wide decision making. Announcements about NumPy, such as for releases, developer meetings, sprints or conference talks are also made on this list.
+
+On this list please use bottom posting, reply to the list (rather than to another sender), and don't reply to digests. A searchable archive of this list is available [here](http://numpy-discussion.10968.n7.nabble.com/).
+
+***
+
+### [GitHub issue tracker](https://github.com/numpy/numpy/issues)
+
+- For bug reports (e.g. "`np.arange(3).shape` returns `(5,)`, when it should return `(3,)`");
+- documentation issues (e.g. "I found this section unclear");
+- and feature requests (e.g. "I would like to have a new interpolation method in `np.percentile`").
+
+_Please note that GitHub is not the right place to report a security vulnerability. If you think you have found a security vulnerability in NumPy, please report it [here](https://tidelift.com/docs/security)._
+
+***
+
+### [Slack](https://numpy-team.slack.com)
+
+A real-time chat room to ask questions about _contributing_ to NumPy. This is a private space, specifically meant for people who are hesitant to bring up their questions or ideas on a large public mailing list or GitHub. Please see [here](https://numpy.org/devdocs/dev/index.html#contributing-to-numpy) for more details and how to get an invite.
+
+
+## Study Groups and Meetups
+
+If you would like to find a local meetup or study group to learn more about NumPy and the wider ecosystem of Python packages for data science and scientific computing, we recommend exploring the [PyData meetups](https://www.meetup.com/pro/pydata/) (150+ meetups, 100,000+ members).
+
+NumPy also organizes in-person sprints for its team and interested contributors occasionally. These are typically planned several months in advance and will be announced on the [mailing list](https://mail.python.org/mailman/listinfo/numpy-discussion) and [Twitter](https://twitter.com/numpy_team).
+
+
+## Conferences
+
+The NumPy project doesn't organize its own conferences. The conferences that have traditionally been most popular with NumPy maintainers, contributors and users are the SciPy and PyData conference series:
+
+- [SciPy US](https://conference.scipy.org)
+- [EuroSciPy](https://www.euroscipy.org)
+- [SciPy Latin America](https://www.scipyla.org)
+- [SciPy India](https://scipy.in)
+- [SciPy Japan](https://conference.scipy.org)
+- [PyData conferences](https://pydata.org/event-schedule/) (15-20 events a year spread over many countries)
+
+Many of these conferences include tutorial days that cover NumPy and/or sprints where you can learn how to contribute to NumPy or related open source projects.
+
+
+## Join the NumPy community
+
+To thrive, the NumPy project needs your expertise and enthusiasm. Not a coder? Not a problem! There are many ways to contribute to NumPy.
+
+If you are interested in becoming a NumPy contributor (yay!) we recommend checking out our [Contribute](/contribute) page.
+
From ba73a90cbc24c11e9de68ae866015c5e8f869360 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:38:23 +0000
Subject: [PATCH 094/909] New translations learn.md (Japanese)
---
content/ja/learn.md | 84 +++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 84 insertions(+)
create mode 100644 content/ja/learn.md
diff --git a/content/ja/learn.md b/content/ja/learn.md
new file mode 100644
index 0000000000..264677ac48
--- /dev/null
+++ b/content/ja/learn.md
@@ -0,0 +1,84 @@
+---
+title: Learn
+sidebar: false
+---
+
+**The official NumPy documentation lives [here](https://numpy.org/doc/stable).**
+
+Below is a curated collection of external resources. To contribute, see the [end of this page](#add-to-this-list).
+***
+
+## Beginners
+
+There's a ton of information about NumPy out there. If you are new, we'd strongly recommend these:
+
+ **Tutorials**
+
+* [NumPy Quickstart Tutorial](https://numpy.org/devdocs/user/quickstart.html)
+* [SciPy Lectures](https://scipy-lectures.org/) Besides covering NumPy, these lectures offer a broader introduction to the scientific Python ecosystem.
+* [NumPy: the absolute basics for beginners](https://numpy.org/devdocs/user/absolute_beginners.html)
+* [Machine Learning Plus - Introduction to ndarray](https://www.machinelearningplus.com/python/numpy-tutorial-part1-array-python-examples/)
+* [Edureka - Learn NumPy Arrays with Examples ](https://www.edureka.co/blog/python-numpy-tutorial/)
+* [Dataquest - NumPy Tutorial: Data Analysis with Python](https://www.dataquest.io/blog/numpy-tutorial-python/)
+* [NumPy tutorial *by Nicolas Rougier*](https://github.com/rougier/numpy-tutorial)
+* [Stanford CS231 *by Justin Johnson*](http://cs231n.github.io/python-numpy-tutorial/)
+* [NumPy User Guide](https://numpy.org/devdocs)
+
+ **Books**
+
+* [Guide to NumPy *by Travis E. Oliphant*](http://web.mit.edu/dvp/Public/numpybook.pdf) This is a free version 1 from 2006. For the latest copy (2015) see [here](https://www.barnesandnoble.com/w/guide-to-numpy-travis-e-oliphant-phd/1122853007).
+* [From Python to NumPy *by Nicolas P. Rougier*](https://www.labri.fr/perso/nrougier/from-python-to-numpy/)
+* [Elegant SciPy](https://www.amazon.com/Elegant-SciPy-Art-Scientific-Python/dp/1491922877) *by Juan Nunez-Iglesias, Stefan van der Walt, and Harriet Dashnow*
+
+You may also want to check out the [Goodreads list](https://www.goodreads.com/shelf/show/python-scipy) on the subject of "Python+SciPy." Most books there are about the "SciPy ecosystem," which has NumPy at its core.
+
+ **Videos**
+
+* [Introduction to Numerical Computing with NumPy](http://youtu.be/ZB7BZMhfPgk) *by Alex Chabot-Leclerc*
+
+***
+
+## Advanced
+
+Try these advanced resources for a better understanding of NumPy concepts like advanced indexing, splitting, stacking, linear algebra, and more.
+
+ **Tutorials**
+
+* [100 NumPy Exercises](http://www.labri.fr/perso/nrougier/teaching/numpy.100/index.html) *by Nicolas P. Rougier*
+* [An Introduction to NumPy and Scipy](https://engineering.ucsb.edu/~shell/che210d/numpy.pdf) *by M. Scott Shell*
+* [Numpy Medkits](http://mentat.za.net/numpy/numpy_advanced_slides/) *by Stéfan van der Walt*
+* [NumPy in Python (Advanced)](https://www.geeksforgeeks.org/numpy-python-set-2-advanced/)
+* [Advanced Indexing](https://www.tutorialspoint.com/numpy/numpy_advanced_indexing.htm)
+* [Machine Learning and Data Analytics with NumPy](https://www.machinelearningplus.com/python/numpy-tutorial-python-part2/)
+
+ **Books**
+
+* [Python Data Science Handbook](https://www.amazon.com/Python-Data-Science-Handbook-Essential/dp/1491912057) *by Jake Vanderplas*
+* [Python for Data Analysis](https://www.amazon.com/Python-Data-Analysis-Wrangling-IPython/dp/1491957662) *by Wes McKinney*
+* [Numerical Python: Scientific Computing and Data Science Applications with Numpy, SciPy, and Matplotlib](https://www.amazon.com/Numerical-Python-Scientific-Applications-Matplotlib/dp/1484242459) *by Robert Johansson*
+
+ **Videos**
+
+* [Advanced NumPy - broadcasting rules, strides, and advanced indexing](https://www.youtube.com/watch?v=cYugp9IN1-Q) *by Juan Nunuz-Iglesias*
+* [Advanced Indexing Operations in NumPy Arrays](https://www.youtube.com/watch?v=2WTDrSkQBng) *by Amuls Academy*
+
+***
+
+## NumPy Talks
+
+* [The Future of NumPy Indexing](https://www.youtube.com/watch?v=o0EacbIbf58) *by Jaime Fernández* (2016)
+* [Evolution of Array Computing in Python](https://www.youtube.com/watch?v=HVLPJnvInzM&t=10s) *by Ralf Gommers* (2019)
+* [NumPy: what has changed and what is going to change?](https://www.youtube.com/watch?v=YFLVQFjRmPY) *by Matti Picus* (2019)
+* [Inside NumPy](https://www.youtube.com/watch?v=dBTJD_FDVjU) *by Ralf Gommers, Sebastian Berg, Matti Picus, Tyler Reddy, Stefan van der Walt, Charles Harris* (2019)
+* [Brief Review of Array Computing in Python](https://www.youtube.com/watch?v=f176j2g2eNc) *by Travis Oliphant* (2019)
+
+***
+
+## Citing NumPy
+
+If NumPy has been significant in your research, and you would like to acknowledge the project in your academic publication, please see [this citation information](/citing-numpy).
+
+## Contribute to this list
+
+
+To add to this collection, submit a recommendation [via a pull request](https://github.com/numpy/numpy.org/blob/master/content/en/learn.md). Say why your recommendation deserves mention on this page and also which audience would benefit most.
From 887552039683019c39dc7f55b9fad0ca0449bee5 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:38:24 +0000
Subject: [PATCH 095/909] New translations privacy.md (Japanese)
---
content/ja/privacy.md | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
create mode 100644 content/ja/privacy.md
diff --git a/content/ja/privacy.md b/content/ja/privacy.md
new file mode 100644
index 0000000000..9f259a4210
--- /dev/null
+++ b/content/ja/privacy.md
@@ -0,0 +1,18 @@
+---
+title: プライバシーポリシー
+sidebar: false
+---
+
+**numpy.org** は、Numpyプロジェクトの資金援助のスポンサーでもある、[NumFOCUS, Inc.](https://numfocus.org)によって運営されています。 このウェブサイトのプライバシーポリシーについては、https://numfocus.org/privacy-policyを参照してください。
+
+ポリシーまたはNumFOCUSのデータ収集、使用、および開示方法についてご質問がある場合は、privacy@numfocus.orgのNumFOCUSスタッフにお問い合わせください。
+
+
+
+
+
+
+
+
+
+
From da413f3a75c41fda552bcb8088ec6bd92e3522af Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:38:26 +0000
Subject: [PATCH 096/909] New translations 404.md (Chinese Simplified)
---
content/zh/404.md | 8 ++++++++
1 file changed, 8 insertions(+)
create mode 100644 content/zh/404.md
diff --git a/content/zh/404.md b/content/zh/404.md
new file mode 100644
index 0000000000..0f27a36ee9
--- /dev/null
+++ b/content/zh/404.md
@@ -0,0 +1,8 @@
+---
+title: 404
+sidebar: false
+---
+
+抱歉······ 目标网页并不存在。
+
+如果您认为这个页面应该展示些什么东西,请在 GitHub 上面 [发起一个 issue](https://github.com/numpy/numpy.org/issues).
From 238b825712e722dea90f696283e984d4846061c9 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:38:27 +0000
Subject: [PATCH 097/909] New translations install.md (Korean)
---
content/ko/install.md | 142 ++++++++++++++++++++++++++++++++++++++++++
1 file changed, 142 insertions(+)
create mode 100644 content/ko/install.md
diff --git a/content/ko/install.md b/content/ko/install.md
new file mode 100644
index 0000000000..43dd44cb12
--- /dev/null
+++ b/content/ko/install.md
@@ -0,0 +1,142 @@
+---
+title: Installing NumPy
+sidebar: false
+---
+
+The only prerequisite for installing NumPy is Python itself. If you don't have Python yet and want the simplest way to get started, we recommend you use the [Anaconda Distribution](https://www.anaconda.com/distribution) - it includes Python, NumPy, and many other commonly used packages for scientific computing and data science.
+
+NumPy can be installed with `conda`, with `pip`, with a package manager on macOS and Linux, or [from source](https://numpy.org/devdocs/user/building.html). For more detailed instructions, consult our [Python and NumPy installation guide](#python-numpy-install-guide) below.
+
+**CONDA**
+
+If you use `conda`, you can install NumPy from the `defaults` or `conda-forge` channels:
+
+```bash
+# Best practice, use an environment rather than install in the base env
+conda create -n my-env
+conda activate my-env
+# If you want to install from conda-forge
+conda config --env --add channels conda-forge
+# The actual install command
+conda install numpy
+```
+
+**PIP**
+
+If you use `pip`, you can install NumPy with:
+
+```bash
+pip install numpy
+```
+Also when using pip, it's good practice to use a virtual environment - see [Reproducible Installs](#reproducible-installs) below for why, and [this guide](https://dev.to/bowmanjd/python-tools-for-managing-virtual-environments-3bko#howto) for details on using virtual environments.
+
+
+
+# Python and NumPy installation guide
+
+Installing and managing packages in Python is complicated, there are a number of alternative solutions for most tasks. This guide tries to give the reader a sense of the best (or most popular) solutions, and give clear recommendations. It focuses on users of Python, NumPy, and the PyData (or numerical computing) stack on common operating systems and hardware.
+
+## Recommendations
+
+We'll start with recommendations based on the user's experience level and operating system of interest. If you're in between "beginning" and "advanced", please go with "beginning" if you want to keep things simple, and with "advanced" if you want to work according to best practices that go a longer way in the future.
+
+### Beginning users
+
+On all of Windows, macOS, and Linux:
+
+- Install [Anaconda](https://www.anaconda.com/distribution/) (it installs all packages you need and all other tools mentioned below).
+- For writing and executing code, use notebooks in [JupyterLab](https://jupyterlab.readthedocs.io/en/stable/index.html) for exploratory and interactive computing, and [Spyder](https://www.spyder-ide.org/) or [Visual Studio Code](https://code.visualstudio.com/) for writing scripts and packages.
+- Use [Anaconda Navigator](https://docs.anaconda.com/anaconda/navigator/) to manage your packages and start JupyterLab, Spyder, or Visual Studio Code.
+
+
+### Advanced users
+
+#### Windows or macOS
+
+- Install [Miniconda](https://docs.conda.io/en/latest/miniconda.html).
+- Keep the `base` conda environment minimal, and use one or more [conda environments](https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#) to install the package you need for the task or project you're working on.
+- Unless you're fine with only the packages in the `defaults` channel, make `conda-forge` your default channel via [setting the channel priority](https://conda-forge.org/docs/user/introduction.html#how-can-i-install-packages-from-conda-forge).
+
+
+#### Linux
+
+If you're fine with slightly outdated packages and prefer stability over being able to use the latest versions of libraries:
+- Use your OS package manager for as much as possible (Python itself, NumPy, and other libraries).
+- Install packages not provided by your package manager with `pip install somepackage --user`.
+
+If you use a GPU:
+- Install [Miniconda](https://docs.conda.io/en/latest/miniconda.html).
+- Keep the `base` conda environment minimal, and use one or more [conda environments](https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#) to install the package you need for the task or project you're working on.
+- Use the `defaults` conda channel (`conda-forge` doesn't have good support for GPU packages yet).
+
+Otherwise:
+- Install [Miniforge](https://github.com/conda-forge/miniforge).
+- Keep the `base` conda environment minimal, and use one or more [conda environments](https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#) to install the package you need for the task or project you're working on.
+
+
+#### Alternative if you prefer pip/PyPI
+
+For users who know, from personal preference or reading about the main differences between conda and pip below, they prefer a pip/PyPI-based solution, we recommend:
+- Install Python from, for example, [python.org](https://www.python.org/downloads/), [Homebrew](https://brew.sh/), or your Linux package manager.
+- Use [Poetry](https://python-poetry.org/) as the most well-maintained tool that provides a dependency resolver and environment management capabilities in a similar fashion as conda does.
+
+
+## Python package management
+
+Managing packages is a challenging problem, and, as a result, there are lots of tools. For web and general purpose Python development there's a whole [host of tools](https://packaging.python.org/guides/tool-recommendations/) complementary with pip. For high-performance computing (HPC), [Spack](https://github.com/spack/spack) is worth considering. For most NumPy users though, [conda](https://conda.io/en/latest/) and [pip](https://pip.pypa.io/en/stable/) are the two most popular tools.
+
+
+### Pip & conda
+
+The two main tools that install Python packages are `pip` and `conda`. Their functionality partially overlaps (e.g. both can install `numpy`), however, they can also work together. We'll discuss the major differences between pip and conda here - this is important to understand if you want to manage packages effectively.
+
+The first difference is that conda is cross-language and it can install Python, while pip is installed for a particular Python on your system and installs other packages to that same Python install only. This also means conda can install non-Python libraries and tools you may need (e.g. compilers, CUDA, HDF5), while pip can't.
+
+The second difference is that pip installs from the Python Packaging Index (PyPI), while conda installs from its own channels (typically "defaults" or "conda-forge"). PyPI is the largest collection of packages by far, however, all popular packages are available for conda as well.
+
+The third difference is that conda is an integrated solution for managing packages, dependencies and environments, while with pip you may need another tool (there are many!) for dealing with environments or complex dependencies.
+
+
+### Reproducible installs
+
+As libraries get updated, results from running your code can change, or your code can break completely. It's important to be able to reconstruct the set of packages and versions you're using. Best practice is to:
+
+1. use a different environment per project you're working on,
+2. record package names and versions using your package installer; each has its own metadata format for this:
+ - Conda: [conda environments and environment.yml](https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#)
+ - Pip: [virtual environments](https://docs.python.org/3/tutorial/venv.html) and [requirements.txt](https://pip.readthedocs.io/en/latest/user_guide/#requirements-files)
+ - Poetry: [virtual environments and pyproject.toml](https://python-poetry.org/docs/basic-usage/)
+
+
+
+## NumPy packages & accelerated linear algebra libraries
+
+NumPy doesn't depend on any other Python packages, however, it does depend on an accelerated linear algebra library - typically [Intel MKL](https://software.intel.com/en-us/mkl) or [OpenBLAS](https://www.openblas.net/). Users don't have to worry about installing those (they're automatically included in all NumPy install methods). Power users may still want to know the details, because the used BLAS can affect performance, behavior and size on disk:
+
+- The NumPy wheels on PyPI, which is what pip installs, are built with OpenBLAS. The OpenBLAS libraries are included in the wheel. This makes the wheel larger, and if a user installs (for example) SciPy as well, they will now have two copies of OpenBLAS on disk.
+
+- In the conda defaults channel, NumPy is built against Intel MKL. MKL is a separate package that will be installed in the users' environment when they install NumPy.
+
+- In the conda-forge channel, NumPy is built against a dummy "BLAS" package. When a user installs NumPy from conda-forge, that BLAS package then gets installed together with the actual library - this defaults to OpenBLAS, but it can also be MKL (from the defaults channel), or even [BLIS](https://github.com/flame/blis) or reference BLAS.
+
+- The MKL package is a lot larger than OpenBLAS, it's about 700 MB on disk while OpenBLAS is about 30 MB.
+
+- MKL is typically a little faster and more robust than OpenBLAS.
+
+Besides install sizes, performance and robustness, there are two more things to consider:
+
+- Intel MKL is not open source. For normal use this is not a problem, but if a user needs to redistribute an application built with NumPy, this could be an issue.
+- Both MKL and OpenBLAS will use multi-threading for function calls like `np.dot`, with the number of threads being determined by both a build-time option and an environment variable. Often all CPU cores will be used. This is sometimes unexpected for users; NumPy itself doesn't auto-parallelize any function calls. It typically yields better performance, but can also be harmful - for example when using another level of parallelization with Dask, scikit-learn or multiprocessing.
+
+
+## Troubleshooting
+
+If your installation fails with the message below, see [Troubleshooting ImportError](https://numpy.org/doc/stable/user/troubleshooting-importerror.html).
+
+```
+IMPORTANT: PLEASE READ THIS FOR ADVICE ON HOW TO SOLVE THIS ISSUE!
+
+Importing the numpy c-extensions failed. This error can happen for
+different reasons, often due to issues with your setup.
+```
+
From 789923cf7e4ee9da4cb9601c2f33d5ced53c7328 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:38:29 +0000
Subject: [PATCH 098/909] New translations diversity_sep2020.md (Korean)
---
content/ko/diversity_sep2020.md | 48 +++++++++++++++++++++++++++++++++
1 file changed, 48 insertions(+)
create mode 100644 content/ko/diversity_sep2020.md
diff --git a/content/ko/diversity_sep2020.md b/content/ko/diversity_sep2020.md
new file mode 100644
index 0000000000..ef3030d5f7
--- /dev/null
+++ b/content/ko/diversity_sep2020.md
@@ -0,0 +1,48 @@
+---
+title: NumPy Diversity and Inclusion Statement
+sidebar: false
+---
+
+
+_In light of the foregoing discussion on social media after publication of the NumPy paper in Nature and the concerns raised about the state of diversity and inclusion on the NumPy team, we would like to issue the following statement:_
+
+
+It is our strong belief that we are at our best, as a team and community, when we are inclusive and equitable. Being an international team from the onset, we recognize the value of collaborating with individuals from diverse backgrounds and expertise. A culture where everyone is welcomed, supported, and valued is at the core of the NumPy project.
+
+## The Past
+
+Contributing to open source has always been a pastime in which most historically marginalized groups, especially women, faced more obstacles to participate due to a number of societal constraints and expectations. Open source has a severe diversity gap that is well documented (see, e.g., the [2017 GitHub Open Source Survey](https://opensourcesurvey.org/2017/) and [this blog post](https://medium.com/tech-diversity-files/if-you-think-women-in-tech-is-just-a-pipeline-problem-you-haven-t-been-paying-attention-cb7a2073b996)).
+
+Since its inception and until 2018, NumPy was maintained by a handful of volunteers often working nights and weekends outside of their day jobs. At any one time, the number of active core developers, the ones doing most of the heavy lifting as well as code review and integration of contributions from the community, was in the range of 4 to 8. The project didn't have a roadmap or mechanism for directing resources, being driven by individual efforts to work on what seemed needed. The authors on the NumPy paper are the individuals who made the most significant and sustained contributions to the project over a period of 15 years (2005 - 2019). The lack of diversity on this author list is a reflection of the formative years of the Python and SciPy ecosystems.
+
+2018 has marked an important milestone in the history of the NumPy project. Receiving funding from The Gordon and Betty Moore Foundation and Alfred P. Sloan Foundation allowed us to provide full-time employment for two software engineers with years of experience contributing to the Python ecosystem. Those efforts brought NumPy to a much healthier technical state.
+
+This funding also created space for NumPy maintainers to focus on project governance, community development, and outreach to underrepresented groups. [The diversity statement](https://figshare.com/articles/online_resource/Diversity_and_Inclusion_Statement_NumPy_for_Chan_Zuckerberg_Initiative_EOSS_2019_round_1/12980852) written in mid 2019 for the CZI EOSS program grant application details some of the challenges as well as the advances in our efforts to bring in more diverse talent to the NumPy team.
+
+## The Present
+
+Offering employment opportunities is an effective way to attract and retain diverse talent in OSS. Therefore, we used two-thirds of our second grant that became available in Dec 2019 to employ Melissa Weber Mendonça and Mars Lee.
+
+As a result of several initiatives aimed at community development and engagement led by Inessa Pawson and Ralf Gommers, the NumPy project has received a number of valuable contributions from women and other underrepresented groups in open source in 2020:
+
+- Melissa Weber Mendonça gained commit rights, is maintaining numpy.f2py and is leading the documentation team,
+- Shaloo Shalini created all case studies on numpy.org,
+- Mars Lee contributed web design and led our accessibility improvements work,
+- Isabela Presedo-Floyd designed our new logo,
+- Stephanie Mendoza, Xiayoi Deng, Deji Suolang, and Mame Fatou Thiam designed and fielded the first NumPy user survey,
+- Yuki Dunn, Dayane Machado, Mahfuza Humayra Mohona, Sumera Priyadarsini, Shaloo Shalini, and Kriti Singh (former Outreachy intern) helped the survey team to reach out to non-English speaking NumPy users and developers by translating the questionnaire into their native languages,
+- Sayed Adel, Raghuveer Devulapalli, and Chunlin Fang are driving the work on SIMD optimizations in the core of NumPy.
+
+While we still have much more work to do, the NumPy team is starting to look much more representative of our user base. And we can assure you that the next NumPy paper will certainly have a more diverse group of authors.
+
+## The Future
+
+We are fully committed to fostering inclusion and diversity on our team and in our community, and to do our part in building a more just and equitable future.
+
+We are open to dialogue and welcome every opportunity to connect with organizations representing and supporting women and minorities in tech and science. We are ready to listen, learn, and support.
+
+Please get in touch with us on [our mailing list](https://scipy.org/scipylib/mailing-lists.html#mailing-lists), [GitHub](https://github.com/numpy/numpy/issues), [Slack](https://numpy.org/contribute/), in private at numpy-team@googlegroups.com, or join our [bi-weekly community meeting](https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg).
+
+
+_Sayed Adel, Sebastian Berg, Raghuveer Devulapalli, Chunlin Fang, Ralf Gommers, Allan Haldane, Stephan Hoyer, Mars Lee, Melissa Weber Mendonça, Jarrod Millman, Inessa Pawson, Matti Picus, Nathaniel Smith, Julian Taylor, Pauli Virtanen, Stéfan van der Walt, Eric Wieser, on behalf of the NumPy team_
+
From a0f40fc6b12a77cef680683c21bc915ca9fb36eb Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:38:32 +0000
Subject: [PATCH 099/909] New translations gw-discov.md (Korean)
---
content/ko/case-studies/gw-discov.md | 69 ++++++++++++++++++++++++++++
1 file changed, 69 insertions(+)
create mode 100644 content/ko/case-studies/gw-discov.md
diff --git a/content/ko/case-studies/gw-discov.md b/content/ko/case-studies/gw-discov.md
new file mode 100644
index 0000000000..3d25090e13
--- /dev/null
+++ b/content/ko/case-studies/gw-discov.md
@@ -0,0 +1,69 @@
+---
+title: "Case Study: Discovery of Gravitational Waves"
+sidebar: false
+---
+
+{{< figure src="/images/content_images/cs/gw_sxs_image.png" class="fig-center" caption="**Gravitational Waves**" alt="binary coalesce black hole generating gravitational waves" attr="*(Image Credits: The Simulating eXtreme Spacetimes (SXS) Project at LIGO)*" attrlink="https://youtu.be/Zt8Z_uzG71o" >}}
+
+
+
The scientific Python ecosystem is critical infrastructure for the research done at LIGO.
+
+
+
+## About [Gravitational Waves](https://www.nationalgeographic.com/news/2017/10/what-are-gravitational-waves-ligo-astronomy-science/) and [LIGO](https://www.ligo.caltech.edu)
+
+Gravitational waves are ripples in the fabric of space and time, generated by cataclysmic events in the universe such as collision and merging of two black holes or coalescing binary stars or supernovae. Observing GW can not only help in studying gravity but also in understanding some of the obscure phenomena in the distant universe and its impact.
+
+The [Laser Interferometer Gravitational-Wave Observatory (LIGO)](https://www.ligo.caltech.edu) was designed to open the field of gravitational-wave astrophysics through the direct detection of gravitational waves predicted by Einstein’s General Theory of Relativity. It comprises two widely-separated interferometers within the United States — one in Hanford, Washington and the other in Livingston, Louisiana — operated in unison to detect gravitational waves. Each of them has multi-kilometer-scale gravitational wave detectors that use laser interferometry. The LIGO Scientific Collaboration (LSC), is a group of more than 1000 scientists from universities around the United States and in 14 other countries supported by more than 90 universities and research institutes; approximately 250 students actively contributing to the collaboration. The new LIGO discovery is the first observation of gravitational waves themselves, made by measuring the tiny disturbances the waves make to space and time as they pass through the earth. It has opened up new astrophysical frontiers that explore the warped side of the universe—objects and phenomena that are made from warped spacetime.
+
+
+### Key Objectives
+
+* Though its [mission](https://www.ligo.caltech.edu/page/what-is-ligo) is to detect gravitational waves from some of the most violent and energetic processes in the Universe, the data LIGO collects may have far-reaching effects on many areas of physics including gravitation, relativity, astrophysics, cosmology, particle physics, and nuclear physics.
+* Crunch observed data via numerical relativity computations that involves complex maths in order to discern signal from noise, filter out relevant signal and statistically estimate significance of observed data
+* Data visualization so that the binary / numerical results can be comprehended.
+
+
+
+### The Challenges
+
+* **Computation**
+
+ Gravitational Waves are hard to detect as they produce a very small effect and have tiny interaction with matter. Processing and analyzing all of LIGO's data requires a vast computing infrastructure.After taking care of noise, which is billions of times of the signal, there is still very complex relativity equations and huge amounts of data which present a computational challenge: [O(10^7) CPU hrs needed for binary merger analyses](https://youtu.be/7mcHknWWzNI) spread on 6 dedicated LIGO clusters
+
+* **Data Deluge**
+
+ As observational devices become more sensitive and reliable, the challenges posed by data deluge and finding a needle in a haystack rise multi-fold. LIGO generates terabytes of data every day! Making sense of this data requires an enormous effort for each and every detection. For example, the signals being collected by LIGO must be matched by supercomputers against hundreds of thousands of templates of possible gravitational-wave signatures.
+
+* **Visualization**
+
+ Once the obstacles related to understanding Einstein’s equations well enough to solve them using supercomputers are taken care of, the next big challenge was making data comprehensible to the human brain. Simulation modeling as well as signal detection requires effective visualization techniques. Visualization also plays a role in lending more credibility to numerical relativity in the eyes of pure science aficionados, who did not give enough importance to numerical relativity until imaging and simulations made it easier to comprehend results for a larger audience. Speed of complex computations and rendering, re-rendering images and simulations using latest experimental inputs and insights can be a time consuming activity that challenges researchers in this domain.
+
+{{< figure src="/images/content_images/cs/gw_strain_amplitude.png" class="fig-center" alt="gravitational waves strain amplitude" caption="**Estimated gravitational-wave strain amplitude from GW150914**" attr="(**Graph Credits:** Observation of Gravitational Waves from a Binary Black Hole Merger, ResearchGate Publication)" attrlink="https://www.researchgate.net/publication/293886905_Observation_of_Gravitational_Waves_from_a_Binary_Black_Hole_Merger" >}}
+
+## NumPy’s Role in the Detection of Gravitational Waves
+
+Gravitational waves emitted from the merger cannot be computed using any technique except brute force numerical relativity using supercomputers. The amount of data LIGO collects is as incomprehensibly large as gravitational wave signals are small.
+
+NumPy, the standard numerical analysis package for Python, was utilized by the software used for various tasks performed during the GW detection project at LIGO. NumPy helped in solving complex maths and data manipulation at high speed. Here are some examples:
+
+* [Signal Processing](https://www.uv.es/virgogroup/Denoising_ROF.html): Glitch detection, [Noise identification and Data Characterization](https://ep2016.europython.eu/media/conference/slides/pyhton-in-gravitational-waves-research-communities.pdf) (NumPy, scikit-learn, scipy, matplotlib, pandas, pyCharm)
+* Data retrieval: Deciding which data can be analyzed, figuring out whether it contains a signal - needle in a haystack
+* Statistical analysis: estimate the statistical significance of observational data, estimating the signal parameters (e.g. masses of stars, spin velocity, and distance) by comparison with a model.
+* Visualization of data
+ - Time series
+ - Spectrograms
+* Compute Correlations
+* Key [Software](https://github.com/lscsoft) developed in GW data analysis such as [GwPy](https://gwpy.github.io/docs/stable/overview.html) and [PyCBC](https://pycbc.org) uses NumPy and AstroPy under the hood for providing object based interfaces to utilities, tools, and methods for studying data from gravitational-wave detectors.
+
+{{< figure src="/images/content_images/cs/gwpy-numpy-dep-graph.png" class="fig-center" alt="gwpy-numpy depgraph" caption="**Dependency graph showing how GwPy package depends on NumPy**" >}}
+
+----
+
+{{< figure src="/images/content_images/cs/PyCBC-numpy-dep-graph.png" class="fig-center" alt="PyCBC-numpy depgraph" caption="**Dependency graph showing how PyCBC package depends on NumPy**" >}}
+
+## Summary
+
+GW detection has enabled researchers to discover entirely unexpected phenomena while providing new insight into many of the most profound astrophysical phenomena known. Number crunching and data visualization is a crucial step that helps scientists gain insights into data gathered from the scientific observations and understand the results. The computations are complex and cannot be comprehended by humans unless it is visualized using computer simulations that are fed with the real observed data and analysis. NumPy along with other Python packages such as matplotlib, pandas, and scikit-learn is [enabling researchers](https://www.gw-openscience.org/events/GW150914/) to answer complex questions and discover new horizons in our understanding of the universe.
+
+{{< figure src="/images/content_images/cs/numpy_gw_benefits.png" class="fig-center" alt="numpy benefits" caption="**Key NumPy Capabilities utilized**" >}}
From 650ee7f1a2a798fc483cc3489f549e32e284dc85 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:38:33 +0000
Subject: [PATCH 100/909] New translations deeplabcut-dnn.md (Korean)
---
content/ko/case-studies/deeplabcut-dnn.md | 90 +++++++++++++++++++++++
1 file changed, 90 insertions(+)
create mode 100644 content/ko/case-studies/deeplabcut-dnn.md
diff --git a/content/ko/case-studies/deeplabcut-dnn.md b/content/ko/case-studies/deeplabcut-dnn.md
new file mode 100644
index 0000000000..b40ed2af50
--- /dev/null
+++ b/content/ko/case-studies/deeplabcut-dnn.md
@@ -0,0 +1,90 @@
+---
+title: "Case Study: DeepLabCut 3D Pose Estimation"
+sidebar: false
+---
+
+{{< figure src="/images/content_images/cs/mice-hand.gif" class="fig-center" caption="**Analyzing mice hand-movement using DeepLapCut**" alt="micehandanim" attr="*(Source: www.deeplabcut.org )*" attrlink="http://www.mousemotorlab.org/deeplabcut">}}
+
+
+
Open Source Software is accelerating Biomedicine. DeepLabCut enables automated video analysis of animal behavior using Deep Learning.
+
+
+
+## About DeepLabCut
+
+[DeepLabCut](https://github.com/DeepLabCut/DeepLabCut) is an open source toolbox that empowers researchers at hundreds of institutions worldwide to track behaviour of laboratory animals, with very little training data, at human-level accuracy. With DeepLabCut technology, scientists can delve deeper into the scientific understanding of motor control and behavior across animal species and timescales.
+
+Several areas of research, including neuroscience, medicine, and biomechanics, use data from tracking animal movement. DeepLabCut helps in understanding what humans and other animals are doing by parsing actions that have been recorded on film. Using automation for laborious tasks of tagging and monitoring, along with deep neural network based data analysis, DeepLabCut makes scientific studies involving observing animals, such as primates, mice, fish, flies etc., much faster and more accurate.
+
+{{< figure src="/images/content_images/cs/race-horse.gif" class="fig-center" caption="**Colored dots track the positions of a racehorse’s body part**" alt="horserideranim" attr="*(Source: Mackenzie Mathis)*">}}
+
+DeepLabCut's non-invasive behavioral tracking of animals by extracting the poses of animals is crucial for scientific pursuits in domains such as biomechanics, genetics, ethology & neuroscience. Measuring animal poses non-invasively from video - without markers - in dynamically changing backgrounds is computationally challenging, both technically as well as in terms of resource needs and training data required.
+
+DeepLabCut allows researchers to estimate the pose of the subject, efficiently enabling them to quantify the behavior through a Python based software toolkit. With DeepLabCut, researchers can identify distinct frames from videos, digitally label specific body parts in a few dozen frames with a tailored GUI, and then the deep learning based pose estimation architectures in DeepLabCut learn how to pick out those same features in the rest of the video and in other similar videos of animals. It works across species of animals, from common laboratory animals such as flies and mice to more unusual animals like [cheetahs][cheetah-movement].
+
+DeepLabCut uses a principle called [transfer learning](https://arxiv.org/pdf/1909.11229), which greatly reduces the amount of training data required and speeds up the convergence of the training period. Depending on the needs, users can pick different network architectures that provide faster inference (e.g. MobileNetV2), which can also be combined with real-time experimental feedback. DeepLabCut originally used the feature detectors from a top-performing human pose estimation architecture, called [DeeperCut](https://arxiv.org/abs/1605.03170), which inspired the name. The package now has been significantly changed to include additional architectures, augmentation methods, and a full front-end user experience. Furthermore, to support large-scale biological experiments DeepLabCut provides active learning capabilities so that users can increase the training set over time to cover edge cases and make their pose estimation algorithm robust within the specific context.
+
+Recently, the [DeepLabCut model zoo](http://www.mousemotorlab.org/dlc-modelzoo) was introduced, which provides pre-trained models for various species and experimental conditions from facial analysis in primates to dog posture. This can be run for instance in the cloud without any labeling of new data, or neural network training, and no programming experience is necessary.
+
+### Key Goals and Results
+
+* **Automation of animal pose analysis for scientific studies:**
+
+ The primary objective of DeepLabCut technology is to measure and track posture of animals in a diverse settings. This data can be used, for example, in neuroscience studies to understand how the brain controls movement, or to elucidate how animals socially interact. Researchers have observed a [tenfold performance boost](https://www.biorxiv.org/content/10.1101/457242v1) with DeepLabCut. Poses can be inferred offline at up to 1200 frames per second (FPS).
+
+* **Creation of an easy-to-use Python toolkit for pose estimation:**
+
+ DeepLabCut wanted to share their animal pose-estimation technology in the form of an easy to use tool that can be adopted by researchers easily. So they have created a complete, easy-to-use Python toolbox with project management features as well. These enable not only automation of pose-estimation but also managing the project end-to-end by helping the DeepLabCut Toolkit user right from the dataset collection stage to creating shareable and reusable analysis pipelines.
+
+ Their [toolkit][DLCToolkit] is now available as open source.
+
+ A typical DeepLabCut Workflow includes:
+
+ - creation and refining of training sets via active learning
+ - creation of tailored neural networks for specific animals and scenarios
+ - code for large-scale inference on videos
+ - draw inferences using integrated visualization tools
+
+{{< figure src="/images/content_images/cs/deeplabcut-toolkit-steps.png" class="csfigcaption" caption="**Pose estimation steps with DeepLabCut**" alt="dlcsteps" align="middle" attr="(Source: DeepLabCut)" attrlink="https://twitter.com/DeepLabCut/status/1198046918284210176/photo/1" >}}
+
+### The Challenges
+
+* **Speed**
+
+ Fast processing of animal behavior videos in order to measure their behavior and at the same time make scientific experiments more efficient, accurate. Extracting detailed animal poses for laboratory experiments, without markers, in dynamically changing backgrounds, can be challenging, both technically as well as in terms of resource needs and training data required. Coming up with a tool that is easy to use without the need for skills such as computer vision expertise that enables scientists to do research in more real-world contexts, is a non-trivial problem to solve.
+
+* **Combinatorics**
+
+ Combinatorics involves assembly and integration of movement of multiple limbs into individual animal behavior. Assembling keypoints and their connections into individual animal movements and linking them across time is a complex process that requires heavy-duty numerical analysis, especially in case of multi-animal movement tracking in experiment videos.
+
+* **Data Processing**
+
+ Last but not the least, array manipulation - processing large stacks of arrays corresponding to various images, target tensors and keypoints is fairly challenging.
+
+{{< figure src="/images/content_images/cs/pose-estimation.png" class="csfigcaption" caption="**Pose estimation variety and complexity**" alt="challengesfig" align="middle" attr="(Source: Mackenzie Mathis)" attrlink="https://www.biorxiv.org/content/10.1101/476531v1.full.pdf" >}}
+
+## NumPy's Role in meeting Pose Estimation Challenges
+
+NumPy addresses DeepLabCut technology's core need of numerical computations at high speed for behavioural analytics. Besides NumPy, DeepLabCut employs various Python software that utilize NumPy at their core, such as [SciPy](https://www.scipy.org), [Pandas](https://pandas.pydata.org), [matplotlib](https://matplotlib.org), [Tensorpack](https://github.com/tensorpack/tensorpack), [imgaug](https://github.com/aleju/imgaug), [scikit-learn](https://scikit-learn.org/stable/), [scikit-image](https://scikit-image.org) and [Tensorflow](https://www.tensorflow.org).
+
+The following features of NumPy played a key role in addressing the image processing, combinatorics requirements and need for fast computation in DeepLabCut pose estimation algorithms:
+
+* Vectorization
+* Masked Array Operations
+* Linear Algebra
+* Random Sampling
+* Reshaping of large arrays
+
+DeepLabCut utilizes NumPy’s array capabilities throughout the workflow offered by the toolkit. In particular, NumPy is used for sampling distinct frames for human annotation labeling, and for writing, editing and processing annotation data. Within TensorFlow the neural network is trained by DeepLabCut technology over thousands of iterations to predict the ground truth annotations from frames. For this purpose, target densities (scoremaps) are created to cast pose estimation as a image-to-image translation problem. To make the neural networks robust, data augmentation is employed, which requires the calculation of target scoremaps subject to various geometric and image processing steps. To make training fast, NumPy’s vectorization capabilities are leveraged. For inference, the most likely predictions from target scoremaps need to extracted and one needs to efficiently “link predictions to assemble individual animals”.
+
+{{< figure src="/images/content_images/cs/deeplabcut-workflow.png" class="fig-center" caption="**DeepLabCut Workflow**" alt="workflow" attr="*(Source: Mackenzie Mathis)*" attrlink="https://www.researchgate.net/figure/DeepLabCut-work-flow-The-diagram-delineates-the-work-flow-as-well-as-the-directory-and_fig1_329185962">}}
+
+## Summary
+
+Observing and efficiently describing behavior is a core tenant of modern ethology, neuroscience, medicine, and technology. [DeepLabCut](http://orga.cvss.cc/wp-content/uploads/2019/05/NathMathis2019.pdf) allows researchers to estimate the pose of the subject, efficiently enabling them to quantify the behavior. With only a small set of training images, the DeepLabCut Python toolbox allows training a neural network to within human level labeling accuracy, thus expanding its application to not only behavior analysis in the laboratory, but to potentially also in sports, gait analysis, medicine and rehabilitation studies. Complex combinatorics, data processing challenges faced by DeepLabCut algorithms are addressed through the use of NumPy's array manipulation capabilities.
+
+{{< figure src="/images/content_images/cs/numpy_dlc_benefits.png" class="fig-center" alt="numpy benefits" caption="**Key NumPy Capabilities utilized**" >}}
+
+[cheetah-movement]: https://www.technologynetworks.com/neuroscience/articles/interview-a-deeper-cut-into-behavior-with-mackenzie-mathis-327618
+
+[DLCToolkit]: https://github.com/DeepLabCut/DeepLabCut
From dd33c60340298c1845c20de078a8023291b670de Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:38:35 +0000
Subject: [PATCH 101/909] New translations cricket-analytics.md (Korean)
---
content/ko/case-studies/cricket-analytics.md | 64 ++++++++++++++++++++
1 file changed, 64 insertions(+)
create mode 100644 content/ko/case-studies/cricket-analytics.md
diff --git a/content/ko/case-studies/cricket-analytics.md b/content/ko/case-studies/cricket-analytics.md
new file mode 100644
index 0000000000..987b38fb68
--- /dev/null
+++ b/content/ko/case-studies/cricket-analytics.md
@@ -0,0 +1,64 @@
+---
+title: "Case Study: Cricket Analytics, the game changer!"
+sidebar: false
+---
+
+{{< figure src="/images/content_images/cs/ipl-stadium.png" caption="**IPLT20, the biggest Cricket Festival in India**" alt="Indian Premier League Cricket cup and stadium" attr="*(Image credits: IPLT20 (cup and logo) & Akash Yadav (stadium))*" attrlink="https://unsplash.com/@aksh1802" >}}
+
+
+
You don't play for the crowd, you play for the country.
+
+
+
+## About Cricket
+
+It would be an understatement to state that Indians love cricket. The game is played in just about every nook and cranny of India, rural or urban, popular with the young and the old alike, connecting billions in India unlike any other sport. Cricket enjoys lots of media attention. There is a significant amount of [money](https://www.statista.com/topics/4543/indian-premier-league-ipl/) and fame at stake. Over the last several years, technology has literally been a game changer. Audiences are spoilt for choice with streaming media, tournaments, affordable access to mobile based live cricket watching, and more.
+
+The Indian Premier League (IPL) is a professional Twenty20 cricket league, founded in 2008. It is one of the most attended cricketing events in the world, valued at [$6.7 billion](https://en.wikipedia.org/wiki/Indian_Premier_League) in 2019.
+
+Cricket is a game of numbers - the runs scored by a batsman, the wickets taken by a bowler, the matches won by a cricket team, the number of times a batsman responds in a certain way to a kind of bowling attack, etc. The capability to dig into cricketing numbers for both improving performance and studying the business opportunities, overall market, and economics of cricket via powerful analytics tools, powered by numerical computing software such as NumPy, is a big deal. Cricket analytics provides interesting insights into the game and predictive intelligence regarding game outcomes.
+
+Today, there are rich and almost infinite troves of cricket game records and statistics available, e.g., [ESPN cricinfo](https://stats.espncricinfo.com/ci/engine/stats/index.html) and [cricsheet](https://cricsheet.org). These and several such cricket databases have been used for [cricket analysis](https://www.researchgate.net/publication/336886516_Data_visualization_and_toss_related_analysis_of_IPL_teams_and_batsmen_performances) using the latest machine learning and predictive modelling algorithms. Media and entertainment platforms along with professional sports bodies associated with the game use technology and analytics for determining key metrics for improving match winning chances:
+
+* batting performance moving average,
+* score forecasting,
+* gaining insights into fitness and performance of a player against different opposition,
+* player contribution to wins and losses for making strategic decisions on team composition
+
+{{< figure src="/images/content_images/cs/cricket-pitch.png" class="csfigcaption" caption="**Cricket Pitch, the focal point in the field**" alt="A cricket pitch with bowler and batsmen" align="middle" attr="*(Image credit: Debarghya Das)*" attrlink="http://debarghyadas.com/files/IPLpaper.pdf" >}}
+
+### Key Data Analytics Objectives
+
+* Sports data analytics are used not only in cricket but many [other sports](https://adtmag.com/blogs/dev-watch/2017/07/sports-analytics.aspx) for improving the overall team performance and maximizing winning chances.
+* Real-time data analytics can help in gaining insights even during the game for changing tactics by the team and by associated businesses for economic benefits and growth.
+* Besides historical analysis, predictive models are harnessed to determine the possible match outcomes that require significant number crunching and data science know-how, visualization tools and capability to include newer observations in the analysis.
+
+{{< figure src="/images/content_images/cs/player-pose-estimator.png" class="fig-center" alt="pose estimator" caption="**Cricket Pose Estimator**" attr="*(Image credit: connect.vin)*" attrlink="https://connect.vin/2019/05/ai-for-cricket-batsman-pose-analysis/" >}}
+
+### The Challenges
+
+* **Data Cleaning and preprocessing**
+
+ IPL has expanded cricket beyond the classic test match format to a much larger scale. The number of matches played every season across various formats has increased and so has the data, the algorithms, newer sports data analysis technologies and simulation models. Cricket data analysis requires field mapping, player tracking, ball tracking, player shot analysis, and several other aspects involved in how the ball is delivered, its angle, spin, velocity, and trajectory. All these factors together have increased the complexity of data cleaning and preprocessing.
+
+* **Dynamic Modeling**
+
+ In cricket, just like any other sport, there can be a large number of variables related to tracking various numbers of players on the field, their attributes, the ball, and several possibilities of potential actions. The complexity of data analytics and modeling is directly proportional to the kind of predictive questions that are put forth during analysis and are highly dependent on data representation and the model. Things get even more challenging in terms of computation, data comparisons when dynamic cricket play predictions are sought such as what would have happened if the batsman had hit the ball at a different angle or velocity.
+
+* **Predictive Analytics Complexity**
+
+ Much of the decision making in cricket is based on questions such as "how often does a batsman play a certain kind of shot if the ball delivery is of a particular type", or "how does a bowler change his line and length if the batsman responds to his delivery in a certain way". This kind of predictive analytics query requires highly granular dataset availability and the capability to synthesize data and create generative models that are highly accurate.
+
+## NumPy’s Role in Cricket Analytics
+
+Sports Analytics is a thriving field. Many researchers and companies [use NumPy](https://adtmag.com/blogs/dev-watch/2017/07/sports-analytics.aspx) and other PyData packages like Scikit-learn, SciPy, Matplotlib, and Jupyter, besides using the latest machine learning and AI techniques. NumPy has been used for various kinds of cricket related sporting analytics such as:
+
+* **Statistical Analysis:** NumPy's numerical capabilities help estimate the statistical significance of observational data or match events in the context of various player and game tactics, estimating the game outcome by comparison with a generative or static model. [Causal analysis](https://amplitude.com/blog/2017/01/19/causation-correlation) and [big data approaches](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4996805/) are used for tactical analysis.
+
+* **Data Visualization:** Data graphing and [visualization](https://towardsdatascience.com/advanced-sports-visualization-with-pandas-matplotlib-and-seaborn-9c16df80a81b) provides useful insights into relationship between various datasets.
+
+## Summary
+
+Sports Analytics is a game changer when it comes to how professional games are played, especially how strategic decision making happens, which until recently was primarily done based on “gut feeling" or adherence to past traditions. NumPy forms a solid foundation for a large set of Python packages which provide higher level functions related to data analytics, machine learning, and AI algorithms. These packages are widely deployed to gain real-time insights that help in decision making for game-changing outcomes, both on field as well as to draw inferences and drive business around the game of cricket. Finding out the hidden parameters, patterns, and attributes that lead to the outcome of a cricket match helps the stakeholders to take notice of game insights that are otherwise hidden in numbers and statistics.
+
+{{< figure src="/images/content_images/cs/numpy_ca_benefits.png" class="fig-center" alt="Diagram showing benefits of using NumPy for cricket analytics" caption="**Key NumPy Capabilities utilized**" >}}
From c2bdfe372934798f5fb4c4f3b8b769b3456a2c13 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:38:37 +0000
Subject: [PATCH 102/909] New translations blackhole-image.md (Korean)
---
content/ko/case-studies/blackhole-image.md | 70 ++++++++++++++++++++++
1 file changed, 70 insertions(+)
create mode 100644 content/ko/case-studies/blackhole-image.md
diff --git a/content/ko/case-studies/blackhole-image.md b/content/ko/case-studies/blackhole-image.md
new file mode 100644
index 0000000000..f2460d3d5b
--- /dev/null
+++ b/content/ko/case-studies/blackhole-image.md
@@ -0,0 +1,70 @@
+---
+title: "Case Study: First Image of a Black Hole"
+sidebar: false
+---
+
+{{< figure src="/images/content_images/cs/blackhole.jpg" caption="**Black Hole M87**" alt="black hole image" attr="*(Image Credits: Event Horizon Telescope Collaboration)*" attrlink="https://www.jpl.nasa.gov/images/universe/20190410/blackhole20190410.jpg" >}}
+
+
+
Imaging the M87 Black Hole is like trying to see something that is by definition impossible to see.
+
+
+
+## A telescope the size of the earth
+
+The [Event Horizon telescope (EHT)](https://eventhorizontelescope.org) is an array of eight ground-based radio telescopes forming a computational telescope the size of the earth, studing the universe with unprecedented sensitivity and resolution. The huge virtual telescope, which uses a technique called very-long-baseline interferometry (VLBI), has an angular resolution of [20 micro-arcseconds][resolution] — enough to read a newspaper in New York from a sidewalk café in Paris!
+
+### Key Goals and Results
+
+* **A New View of the Universe:** The groundwork for the EHT's groundbreaking image had been laid 100 years earlier when [Sir Arthur Eddington][eddington] yielded the first observational support of Einstein's theory of general relativity.
+
+* **The Black Hole:** EHT was trained on a supermassive black hole approximately 55 million light-years from Earth, lying at the center of the galaxy Messier 87 (M87) in the Virgo galaxy cluster. Its mass is 6.5 billion times the Sun's. It had been studied for [over 100 years](https://www.jpl.nasa.gov/news/news.php?feature=7385), but never before had a black hole been visually observed.
+
+* **Comparing Observations to Theory:** From Einstein’s general theory of relativity, scientists expected to find a shadow-like region caused by gravitational bending and capture of light. Scientists could use it to measure the black hole's enormous mass.
+
+### The Challenges
+
+* **Computational scale**
+
+ EHT poses massive data-processing challenges, including rapid atmospheric phase fluctuations, large recording bandwidth, and telescopes that are widely dissimilar and geographically dispersed.
+
+* **Too much information**
+
+ Each day EHT generates over 350 terabytes of observations, stored on helium-filled hard drives. Reducing the volume and complexity of this much data is enormously difficult.
+
+* **Into the unknown**
+
+ When the goal is to see something never before seen, how can scientists be confident the image is correct?
+
+{{< figure src="/images/content_images/cs/dataprocessbh.png" class="csfigcaption" caption="**EHT Data Processing Pipeline**" alt="data pipeline" align="middle" attr="(Diagram Credits: The Astrophysical Journal, Event Horizon Telescope Collaboration)" attrlink="https://iopscience.iop.org/article/10.3847/2041-8213/ab0c57" >}}
+
+## NumPy’s Role
+
+What if there's a problem with the data? Or perhaps an algorithm relies too heavily on a particular assumption. Will the image change drastically if a single parameter is changed?
+
+The EHT collaboration met these challenges by having independent teams evaluate the data, using both established and cutting-edge image reconstruction techniques. When results proved consistent, they were combined to yield the first-of-a-kind image of the black hole.
+
+Their work illustrates the role the scientific Python ecosystem plays in advancing science through collaborative data analysis.
+
+{{< figure src="/images/content_images/cs/bh_numpy_role.png" class="fig-center" alt="role of numpy" caption="**The role of NumPy in Black Hole imaging**" >}}
+
+For example, the [`eht-imaging`][ehtim] Python package provides tools for simulating and performing image reconstruction on VLBI data. NumPy is at the core of array data processing used in this package, as illustrated by the partial software dependency chart below.
+
+{{< figure src="/images/content_images/cs/ehtim_numpy.png" class="fig-center" alt="ehtim dependency map highlighting numpy" caption="**Software dependency chart of ehtim package highlighting NumPy**" >}}
+
+Besides NumPy, many other packages, such as [SciPy](https://www.scipy.org) and [Pandas](https://pandas.io), are part of the data processing pipeline for imaging the black hole. The standard astronomical file formats and time/coordinate transformations were handled by [Astropy][astropy], while [Matplotlib][mpl] was used in visualizing data throughout the analysis pipeline, including the generation of the final image of the black hole.
+
+## Summary
+
+The efficient and adaptable n-dimensional array that is NumPy's central feature enabled researchers to manipulate large numerical datasets, providing a foundation for the first-ever image of a black hole. A landmark moment in science, it gives stunning visual evidence of Einstein’s theory. The achievement encompasses not only technological breakthroughs but also international collaboration among over 200 scientists and some of the world's best radio observatories. Innovative algorithms and data processing techniques, improving upon existing astronomical models, helped unfold a mystery of the universe.
+
+{{< figure src="/images/content_images/cs/numpy_bh_benefits.png" class="fig-center" alt="numpy benefits" caption="**Key NumPy Capabilities utilized**" >}}
+
+[resolution]: https://eventhorizontelescope.org/press-release-april-10-2019-astronomers-capture-first-image-black-hole
+
+[eddington]: https://en.wikipedia.org/wiki/Eddington_experiment
+
+[ehtim]: https://github.com/achael/eht-imaging
+
+[astropy]: https://www.astropy.org/
+[mpl]: https://matplotlib.org/
From 452b861db6572e8a1249e910b6b2b81117bcded9 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:38:39 +0000
Subject: [PATCH 103/909] New translations news.md (Korean)
---
content/ko/news.md | 83 ++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 83 insertions(+)
create mode 100644 content/ko/news.md
diff --git a/content/ko/news.md b/content/ko/news.md
new file mode 100644
index 0000000000..5dcb849596
--- /dev/null
+++ b/content/ko/news.md
@@ -0,0 +1,83 @@
+---
+title: News
+sidebar: false
+---
+
+### Diversity in the NumPy project
+
+_Sep 20, 2020_ -- We wrote a [statement on the state of, and discussion on social media around, diversity and inclusion in the NumPy project](/diversity_sep2020).
+
+
+### First official NumPy paper published in Nature!
+
+_Sep 16, 2020_ -- We are pleased to announce the publication of [the first official paper on NumPy](https://www.nature.com/articles/s41586-020-2649-2) as a review article in Nature. This comes 14 years after the release of NumPy 1.0. The paper covers applications and fundamental concepts of array programming, the rich scientific Python ecosystem built on top of NumPy, and the recently added array protocols to facilitate interoperability with external array and tensor libraries like CuPy, Dask, and JAX.
+
+
+### Python 3.9 is coming, when will NumPy release binary wheels?
+
+_Sept 14, 2020_ -- Python 3.9 will be released in a few weeks. If you are an early adopter of Python versions, you may be dissapointed to find that NumPy (and other binary packages like SciPy) will not have binary wheels ready on the day of the release. It is a major effort to adapt the build infrastructure to a new Python version and it typically takes a few weeks for the packages to appear on PyPI and conda-forge. In preparation for this event, please make sure to
+- update your `pip` to version 20.1 at least to support `manylinux2010` and `manylinux2014`
+- use [`--only-binary=numpy`](https://pip.pypa.io/en/stable/reference/pip_install/#cmdoption-only-binary) or `--only-binary=:all:` to prevent `pip` from trying to build from source.
+
+
+### Numpy 1.19.2 release
+
+_Sept 10, 2020_ -- [NumPy 1.19.2](https://numpy.org/devdocs/release/1.19.2-notes.html) is now available. This latest release in the 1.19 series fixes several bugs, prepares for the [upcoming Cython 3.x release](http://docs.cython.org/en/latest/src/changes.html) and pins setuptools to keep distutils working while upstream modifications are ongoing. The aarch64 wheels are built with the latest manylinux2014 release that fixes the problem of differing page sizes used by different linux distros.
+
+### The inaugural NumPy survey is live!
+
+_Jul 2, 2020_ -- This survey is meant to guide and set priorities for decision-making about the development of NumPy as software and as a community. The survey is available in 8 additional languages besides English: Bangla, Hindi, Japanese, Mandarin, Portuguese, Russian, Spanish and French.
+
+Please help us make NumPy better and take the survey [here](https://umdsurvey.umd.edu/jfe/form/SV_8bJrXjbhXf7saAl).
+
+
+### NumPy has a new logo!
+
+_Jun 24, 2020_ -- NumPy now has a new logo:
+
+
+
+The logo is a modern take on the old one, with a cleaner design. Thanks to Isabela Presedo-Floyd for designing the new logo, as well as to Travis Vaught for the old logo that served us well for 15+ years.
+
+
+### NumPy 1.19.0 release
+
+_Jun 20, 2020_ -- NumPy 1.19.0 is now available. This is the first release without Python 2 support, hence it was a "clean-up release". The minimum supported Python version is now Python 3.6. An important new feature is that the random number generation infrastructure that was introduced in NumPy 1.17.0 is now accessible from Cython.
+
+
+### Season of Docs acceptance
+
+_May 11, 2020_ -- NumPy has been accepted as one of the mentor organizations for the Google Season of Docs program. We are excited about the opportunity to work with a technical writer to improve NumPy's documentation once again! For more details, please see [the official Season of Docs site](https://developers.google.com/season-of-docs/) and our [ideas page](https://github.com/numpy/numpy/wiki/Google-Season-of-Docs-2020-Project-Ideas).
+
+
+### NumPy 1.18.0 release
+
+_Dec 22, 2019_ -- NumPy 1.18.0 is now available. After the major changes in 1.17.0, this is a consolidation release. It is the last minor release that will support Python 3.5. Highlights of the release includes the addition of basic infrastructure for linking with 64-bit BLAS and LAPACK libraries, and a new C-API for `numpy.random`.
+
+Please see the [release notes](https://github.com/numpy/numpy/releases/tag/v1.18.0) for more details.
+
+
+### NumPy receives a grant from the Chan Zuckerberg Initiative
+
+_Nov 15, 2019_ -- We are pleased to announce that NumPy and OpenBLAS, one of NumPy's key dependencies, have received a joint grant for $195,000 from the Chan Zuckerberg Initiative through their [Essential Open Source Software for Science program](https://chanzuckerberg.com/eoss/) that supports software maintenance, growth, development, and community engagement for open source tools critical to science.
+
+This grant will be used to ramp up the efforts in improving NumPy documentation, website redesign, and community development to better serve our large and rapidly growing user base, and ensure the long-term sustainability of the project. While the OpenBLAS team will focus on addressing sets of key technical issues, in particular thread-safety, AVX-512, and thread-local storage (TLS) issues, as well as algorithmic improvements in ReLAPACK (Recursive LAPACK) on which OpenBLAS depends.
+
+More details on our proposed initiatives and deliverables can be found in the [full grant proposal](https://figshare.com/articles/Proposal_NumPy_OpenBLAS_for_Chan_Zuckerberg_Initiative_EOSS_2019_round_1/10302167). The work is scheduled to start on Dec 1st, 2019 and continue for the next 12 months.
+
+
+## Releases
+
+Here is a list of NumPy releases, with links to release notes. All bugfix releases (only the `z` changes in the `x.y.z` version number) have no new features; minor releases (the `y` increases) do.
+
+- NumPy 1.18.4 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.18.4)) -- _3 May 2020_.
+- NumPy 1.18.3 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.18.3)) -- _19 Apr 2020_.
+- NumPy 1.18.2 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.18.2)) -- _17 Mar 2020_.
+- NumPy 1.18.1 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.18.1)) -- _6 Jan 2020_.
+- NumPy 1.17.5 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.17.5)) -- _1 Jan 2020_.
+- NumPy 1.18.0 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.18.0)) -- _22 Dec 2019_.
+- NumPy 1.17.4 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.17.4)) -- _11 Nov 2019_.
+- NumPy 1.17.0 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.17.0)) -- _26 Jul 2019_.
+- NumPy 1.16.0 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.16.0)) -- _14 Jan 2019_.
+- NumPy 1.15.0 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.15.0)) -- _23 Jul 2018_.
+- NumPy 1.14.0 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.14.0)) -- _7 Jan 2018_.
From 212c24d14476f35ef36cc81c942d97b2043ccf31 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:38:40 +0000
Subject: [PATCH 104/909] New translations history.md (Korean)
---
content/ko/history.md | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
create mode 100644 content/ko/history.md
diff --git a/content/ko/history.md b/content/ko/history.md
new file mode 100644
index 0000000000..fc79a621af
--- /dev/null
+++ b/content/ko/history.md
@@ -0,0 +1,21 @@
+---
+title: History of NumPy
+sidebar: false
+---
+
+NumPy is a foundational Python library that provides array data structures and related fast numerical routines. When started, the library had little funding, and was written mainly by graduate students—many of them without computer science education, and often without a blessing of their advisors. To even imagine that a small group of “rogue” student programmers could upend the already well-established ecosystem of research software—backed by millions in funding and many hundreds of highly qualified engineers — was preposterous. Yet, the philosophical motivations behind a fully open tool stack, in combination with the excited, friendly community with a singular focus, have proven auspicious in the long run. Nowadays, NumPy is relied upon by scientists, engineers, and many other professionals around the world. For example, the published scripts used in the analysis of gravitational waves import NumPy, and the M87 black hole imaging project directly cites NumPy.
+
+For the in-depth account on milestones in the development of NumPy and related libraries please see [arxiv.org](arxiv.org/abs/1907.10121).
+
+If you’d like to obtain a copy of the original Numeric and Numarray libraries, follow the links below:
+
+[Download Page for *Numeric*](https://sourceforge.net/projects/numpy/files/Old%20Numeric/)*
+
+[Download Page for *Numarray*](https://sourceforge.net/projects/numpy/files/Old%20Numarray/)*
+
+*Please note that these older array packages are no longer maintained, and users are strongly advised to use NumPy for any array-related purposes or refactor any pre-existing code to utilize the NumPy library.
+
+### Historic Documentation
+
+[Download *`Numeric'* Manual](static/numeric-manual.pdf)
+
From 4d0d0fdf26eb56843e9282442ae9170bf5c8c3d7 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:38:42 +0000
Subject: [PATCH 105/909] New translations gethelp.md (Korean)
---
content/ko/gethelp.md | 34 ++++++++++++++++++++++++++++++++++
1 file changed, 34 insertions(+)
create mode 100644 content/ko/gethelp.md
diff --git a/content/ko/gethelp.md b/content/ko/gethelp.md
new file mode 100644
index 0000000000..a427b5b1f5
--- /dev/null
+++ b/content/ko/gethelp.md
@@ -0,0 +1,34 @@
+---
+title: Get Help
+sidebar: false
+---
+
+**User questions:** The best way to get help is to post your question to a site like [StackOverflow](http://stackoverflow.com/questions/tagged/numpy), with thousands of users available to answer. Smaller alternatives include [IRC](https://webchat.freenode.net/?channels=%23numpy), [Gitter](https://gitter.im/numpy/numpy), and [Reddit](https://www.reddit.com/r/Numpy/). We wish we could keep an eye on these sites, or answer questions directly, but the volume is just a little overwhelming!
+
+**Development issues:** For NumPy development-related matters (e.g. bug reports), please see [Community](/community).
+
+
+
+### [StackOverflow](http://stackoverflow.com/questions/tagged/numpy)
+
+A forum for asking usage questions, e.g. "How do I do X in NumPy?”. Please [use the `#numpy` tag](https://stackoverflow.com/help/tagging)
+
+***
+
+### [Reddit](https://www.reddit.com/r/Numpy/)
+
+Another forum for usage questions.
+
+***
+
+### [Gitter](https://gitter.im/numpy/numpy)
+
+A real-time chat room where users and community members help each other.
+
+***
+
+### [IRC](https://webchat.freenode.net/?channels=%23numpy)
+
+Another real-time chat room where users and community members help each other.
+
+***
From 2d25def5ff044908833e83af71213a9fb2e934e1 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:38:44 +0000
Subject: [PATCH 106/909] New translations report-handling-manual.md (Korean)
---
content/ko/report-handling-manual.md | 95 ++++++++++++++++++++++++++++
1 file changed, 95 insertions(+)
create mode 100644 content/ko/report-handling-manual.md
diff --git a/content/ko/report-handling-manual.md b/content/ko/report-handling-manual.md
new file mode 100644
index 0000000000..5586668cba
--- /dev/null
+++ b/content/ko/report-handling-manual.md
@@ -0,0 +1,95 @@
+---
+title: NumPy Code of Conduct - How to follow up on a report
+sidebar: false
+---
+
+This is the manual followed by NumPy’s Code of Conduct Committee. It’s used when we respond to an issue to make sure we’re consistent and fair.
+
+Enforcing the [Code of Conduct](/code-of-conduct) impacts our community today and for the future. It’s an action that we do not take lightly. When reviewing enforcement measures, the Code of Conduct Committee will keep the following values and guidelines in mind:
+
+* Act in a personal manner rather than impersonal. The Committee can engage the parties to understand the situation while respecting the privacy and any necessary confidentiality of reporters. However, sometimes it is necessary to communicate with one or more individuals directly: the Committee’s goal is to improve the health of our community rather than only produce a formal decision.
+* Emphasize empathy for individuals rather than judging behavior, avoiding binary labels of “good” and “bad/evil”. Overt, clear-cut aggression and harassment exist, and we will address them firmly. But many scenarios that can prove challenging to resolve are those where normal disagreements devolve into unhelpful or harmful behavior from multiple parties. Understanding the full context and finding a path that re-engages all is hard, but ultimately the most productive for our community.
+* We understand that email is a difficult medium and can be isolating. Receiving criticism over email, without personal contact, can be particularly painful. This makes it especially important to keep an atmosphere of open-minded respect for the views of others. It also means that we must be transparent in our actions, and that we will do everything in our power to make sure that all our members are treated fairly and with sympathy.
+* Discrimination can be subtle and it can be unconscious. It can show itself as unfairness and hostility in otherwise ordinary interactions. We know that this does occur, and we will take care to look out for it. We would very much like to hear from you if you feel you have been treated unfairly, and we will use these procedures to make sure that your complaint is heard and addressed.
+* Help increase engagement in good discussion practice: try to identify where discussion may have broken down, and provide actionable information, pointers, and resources that can lead to positive change on these points.
+* Be mindful of the needs of new members: provide them with explicit support and consideration, with the aim of increasing participation from underrepresented groups in particular.
+* Individuals come from different cultural backgrounds and native languages. Try to identify any honest misunderstandings caused by a non-native speaker and help them understand the issue and what they can change to avoid causing offence. Complex discussion in a foreign language can be very intimidating, and we want to grow our diversity also across nationalities and cultures.
+
+
+## Mediation
+
+Voluntary informal mediation is a tool at our disposal. In contexts such as when two or more parties have all escalated to the point of inappropriate behavior (something sadly common in human conflict), it may be useful to facilitate a mediation process. This is only an example: the Committee can consider mediation in any case, mindful that the process is meant to be strictly voluntary and no party can be pressured to participate. If the Committee suggests mediation, it should:
+
+* Find a candidate who can serve as a mediator.
+* Obtain the agreement of the reporter(s). The reporter(s) have complete freedom to decline the mediation idea or to propose an alternate mediator.
+* Obtain the agreement of the reported person(s).
+* Settle on the mediator: while parties can propose a different mediator than the suggested candidate, only if a common agreement is reached on all terms can the process move forward.
+* Establish a timeline for mediation to complete, ideally within two weeks.
+
+The mediator will engage with all the parties and seek a resolution that is satisfactory to all. Upon completion, the mediator will provide a report (vetted by all parties to the process) to the Committee, with recommendations on further steps. The Committee will then evaluate these results (whether a satisfactory resolution was achieved or not) and decide on any additional action deemed necessary.
+
+
+## How the Committee will respond to reports
+
+When the Committee (or a Committee member) receives a report, they will first determine whether the report is about a clear and severe breach (as defined below). If so, immediate action needs to be taken in addition to the regular report handling process.
+
+
+## Clear and severe breach actions
+
+We know that it is painfully common for internet communication to start at or devolve into obvious and flagrant abuse. We will deal quickly with clear and severe breaches like personal threats, violent, sexist or racist language.
+
+When a member of the Code of Conduct Committee becomes aware of a clear and severe breach, they will do the following:
+
+* Immediately disconnect the originator from all NumPy communication channels.
+* Reply to the reporter that their report has been received and that the originator has been disconnected.
+* In every case, the moderator should make a reasonable effort to contact the originator, and tell them specifically how their language or actions qualify as a “clear and severe breach”. The moderator should also say that, if the originator believes this is unfair or they want to be reconnected to NumPy, they have the right to ask for a review, as below, by the Code of Conduct Committee. The moderator should copy this explanation to the Code of Conduct Committee.
+* The Code of Conduct Committee will formally review and sign off on all cases where this mechanism has been applied to make sure it is not being used to control ordinary heated disagreement.
+
+
+## Report handling
+
+When a report is sent to the Committee they will immediately reply to the reporter to confirm receipt. This reply must be sent within 72 hours, and the group should strive to respond much quicker than that.
+
+If a report doesn’t contain enough information, the Committee will obtain all relevant data before acting. The Committee is empowered to act on the Steering Council’s behalf in contacting any individuals involved to get a more complete account of events.
+
+The Committee will then review the incident and determine, to the best of their ability:
+
+* What happened.
+* Whether this event constitutes a Code of Conduct violation.
+* Who are the responsible party(ies).
+* Whether this is an ongoing situation, and there is a threat to anyone’s physical safety.
+
+This information will be collected in writing, and whenever possible the group’s deliberations will be recorded and retained (i.e. chat transcripts, email discussions, recorded conference calls, summaries of voice conversations, etc).
+
+It is important to retain an archive of all activities of this Committee to ensure consistency in behavior and provide institutional memory for the project. To assist in this, the default channel of discussion for this Committee will be a private mailing list accessible to current and future members of the Committee as well as members of the Steering Council upon justified request. If the Committee finds the need to use off-list communications (e.g. phone calls for early/rapid response), it should in all cases summarize these back to the list so there’s a good record of the process.
+
+The Code of Conduct Committee should aim to have a resolution agreed upon within two weeks. In the event that a resolution can’t be determined in that time, the Committee will respond to the reporter(s) with an update and projected timeline for resolution.
+
+
+## Resolutions
+
+The Committee must agree on a resolution by consensus. If the group cannot reach consensus and deadlocks for over a week, the group will turn the matter over to the Steering Council for resolution.
+
+Possible responses may include:
+
+* Taking no further action:
+ - if we determine no violations have occurred;
+ - if the matter has been resolved publicly while the Committee was considering responses.
+* Coordinating voluntary mediation: if all involved parties agree, the Committee may facilitate a mediation process as detailed above.
+* Remind publicly, and point out that some behavior/actions/language have been judged inappropriate and why in the current context, or can but hurtful to some people, requesting the community to self-adjust.
+* A private reprimand from the Committee to the individual(s) involved. In this case, the group chair will deliver that reprimand to the individual(s) over email, cc’ing the group.
+* A public reprimand. In this case, the Committee chair will deliver that reprimand in the same venue that the violation occurred, within the limits of practicality. E.g., the original mailing list for an email violation, but for a chat room discussion where the person/context may be gone, they can be reached by other means. The group may choose to publish this message elsewhere for documentation purposes.
+* A request for a public or private apology, assuming the reporter agrees to this idea: they may at their discretion refuse further contact with the violator. The chair will deliver this request. The Committee may, if it chooses, attach “strings” to this request: for example, the group may ask a violator to apologize in order to retain one’s membership on a mailing list.
+* A “mutually agreed upon hiatus” where the Committee asks the individual to temporarily refrain from community participation. If the individual chooses not to take a temporary break voluntarily, the Committee may issue a “mandatory cooling off period”.
+* A permanent or temporary ban from some or all NumPy spaces (mailing lists, gitter.im, etc.). The group will maintain records of all such bans so that they may be reviewed in the future or otherwise maintained.
+
+Once a resolution is agreed upon, but before it is enacted, the Committee will contact the original reporter and any other affected parties and explain the proposed resolution. The Committee will ask if this resolution is acceptable, and must note feedback for the record.
+
+Finally, the Committee will make a report to the NumPy Steering Council (as well as the NumPy core team in the event of an ongoing resolution, such as a ban).
+
+The Committee will never publicly discuss the issue; all public statements will be made by the chair of the Code of Conduct Committee or the NumPy Steering Council.
+
+
+## Conflicts of Interest
+
+In the event of any conflict of interest, a Committee member must immediately notify the other members, and recuse themselves if necessary.
From e02d37996d2e61ad56944fb620563d9af758843e Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:38:45 +0000
Subject: [PATCH 107/909] New translations terms.md (Korean)
---
content/ko/terms.md | 178 ++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 178 insertions(+)
create mode 100644 content/ko/terms.md
diff --git a/content/ko/terms.md b/content/ko/terms.md
new file mode 100644
index 0000000000..9a66045505
--- /dev/null
+++ b/content/ko/terms.md
@@ -0,0 +1,178 @@
+---
+title: Terms of Use
+sidebar: false
+---
+
+*Last updated January 4, 2020*
+
+
+## AGREEMENT TO TERMS
+
+These Terms of Use constitute a legally binding agreement made between you, whether personally or on behalf of an entity (“you”) and NumPy ("**Project**", “**we**”, “**us**”, or “**our**”), concerning your access to and use of the numpy.org website as well as any other media form, media channel, mobile website or mobile application related, linked, or otherwise connected thereto (collectively, the “Site”). You agree that by accessing the Site, you have read, understood, and agreed to be bound by all of these Terms of Use. IF YOU DO NOT AGREE WITH ALL OF THESE TERMS OF USE, THEN YOU ARE EXPRESSLY PROHIBITED FROM USING THE SITE AND YOU MUST DISCONTINUE USE IMMEDIATELY.
+
+
+
+Supplemental terms and conditions or documents that may be posted on the Site from time to time are hereby expressly incorporated herein by reference. We reserve the right, in our sole discretion, to make changes or modifications to these Terms of Use at any time and for any reason. We will alert you about any changes by updating the “Last updated” date of these Terms of Use, and you waive any right to receive specific notice of each such change. It is your responsibility to periodically review these Terms of Use to stay informed of updates. You will be subject to, and will be deemed to have been made aware of and to have accepted, the changes in any revised Terms of Use by your continued use of the Site after the date such revised Terms of Use are posted.
+
+
+
+The information provided on the Site is not intended for distribution to or use by any person or entity in any jurisdiction or country where such distribution or use would be contrary to law or regulation or which would subject us to any registration requirement within such jurisdiction or country. Accordingly, those persons who choose to access the Site from other locations do so on their own initiative and are solely responsible for compliance with local laws, if and to the extent local laws are applicable.
+
+
+## USER REPRESENTATIONS
+
+By using the Site, you represent and warrant that: (1) you have the legal capacity and you agree to comply with these Terms of Use; (2) you will not use the Site for any illegal or unauthorized purpose; and (3) your use of the Site will not violate any applicable law or regulation.
+
+
+If you provide any information that is untrue, inaccurate, not current, or incomplete, we have the right to refuse any and all current or future use of the Site (or any portion thereof).
+
+
+## PROHIBITED ACTIVITIES
+
+You may not access or use the Site for any purpose other than that for which we make the Site available.
+
+As a user of the Site, you agree not to:
+
+1. Systematically retrieve data or other content from the Site to create or compile, directly or indirectly, a collection, compilation, database, or directory without written permission from us.
+
+2. Make any unauthorized use of the Site, including collecting usernames and/or email addresses of users by electronic or other means for the purpose of sending unsolicited email, or creating user accounts by automated means or under false pretenses.
+
+3. Use the Site to advertise or offer to sell goods and services.
+
+4. Circumvent, disable, or otherwise interfere with security-related features of the Site.
+
+5. Engage in unauthorized framing of or linking to the Site.
+
+6. Trick, defraud, or mislead us and other users, especially in any attempt to learn sensitive account information such as user passwords.
+
+7. Make improper use of our support services or submit false reports of abuse or misconduct.
+
+8. Engage in any automated use of the system, such as using scripts to send comments or messages, or using any data mining, robots, or similar data gathering and extraction tools.
+
+9. Interfere with, disrupt, or create an undue burden on the Site or the networks or services connected to the Site.
+
+10. Attempt to impersonate another user or person or use the username of another user.
+
+11. Use any information obtained from the Site in order to harass, abuse, or harm another person.
+
+12. Disparage, tarnish, or otherwise harm, in our opinion, us and/or the Site.
+
+13. Except as may be the result of standard search engine or Internet browser usage, use, launch, develop, or distribute any automated system, including without limitation, any spider, robot, cheat utility, scraper, or offline reader that accesses the Site, or using or launching any unauthorized script or other software.
+
+14. Upload or transmit (or attempt to upload or to transmit) any material that acts as a passive or active information collection or transmission mechanism, including without limitation, clear graphics interchange formats (“gifs”), 1×1 pixels, web bugs, cookies, or other similar devices (sometimes referred to as “spyware” or “passive collection mechanisms” or “pcms”).
+
+15. Upload or transmit (or attempt to upload or to transmit) viruses, Trojan horses, or other material, including excessive use of capital letters and spamming (continuous posting of repetitive text), that interferes with any party’s uninterrupted use and enjoyment of the Site or modifies, impairs, disrupts, alters, or interferes with the use, features, functions, operation, or maintenance of the Site.
+
+16. Harass, annoy, intimidate, or threaten any of our employees or agents engaged in providing any portion of the Site to you.
+
+17. Attempt to bypass any measures of the Site designed to prevent or restrict access to the Site, or any portion of the Site.
+
+
+## SUBMISSIONS
+
+You acknowledge and agree that any questions, comments, suggestions, ideas, feedback, or other information regarding the Site ("Submissions") provided by you to us are non-confidential and shall become our sole property. We shall own exclusive rights, including all intellectual property rights, and shall be entitled to the unrestricted use and dissemination of these Submissions for any lawful purpose, commercial or otherwise, without acknowledgment or compensation to you. You hereby waive all moral rights to any such Submissions, and you hereby warrant that any such Submissions are original with you or that you have the right to submit such Submissions. You agree there shall be no recourse against us for any alleged or actual infringement or misappropriation of any proprietary right in your Submissions.
+
+## THIRD-PARTY WEBSITES AND CONTENT
+
+The Site may contain (or you may be sent via the Site) links to other websites ("Third-Party Websites") as well as articles, photographs, text, graphics, pictures, designs, music, sound, video, information, applications, software, and other content or items belonging to or originating from third parties ("Third-Party Content"). Such Third-Party Websites and Third-Party Content are not investigated, monitored, or checked for accuracy, appropriateness, or completeness by us, and we are not responsible for any Third-Party Websites accessed through the Site or any Third-Party Content posted on, available through, or installed from the Site, including the content, accuracy, offensiveness, opinions, reliability, privacy practices, or other policies of or contained in the Third-Party Websites or the Third-Party Content. Inclusion of, linking to, or permitting the use or installation of any Third-Party Websites or any Third-Party Content does not imply approval or endorsement thereof by us. If you decide to leave the Site and access the Third-Party Websites or to use or install any Third-Party Content, you do so at your own risk, and you should be aware these Terms of Use no longer govern. You should review the applicable terms and policies, including privacy and data gathering practices, of any website to which you navigate from the Site or relating to any applications you use or install from the Site. Any purchases you make through Third-Party Websites will be through other websites and from other companies, and we take no responsibility whatsoever in relation to such purchases which are exclusively between you and the applicable third party. You agree and acknowledge that we do not endorse the products or services offered on Third-Party Websites and you shall hold us harmless from any harm caused by your purchase of such products or services. Additionally, you shall hold us harmless from any losses sustained by you or harm caused to you relating to or resulting in any way from any Third-Party Content or any contact with Third-Party Websites.
+
+
+## SITE MANAGEMENT
+
+We reserve the right, but not the obligation, to: (1) monitor the Site for violations of these Terms of Use; (2) take appropriate legal action against anyone who, in our sole discretion, violates the law or these Terms of Use, including without limitation, reporting such user to law enforcement authorities; (3) in our sole discretion and without limitation, refuse, restrict access to, limit the availability of, or disable (to the extent technologically feasible) any of your Contributions or any portion thereof; (4) in our sole discretion and without limitation, notice, or liability, to remove from the Site or otherwise disable all files and content that are excessive in size or are in any way burdensome to our systems; and (5) otherwise manage the Site in a manner designed to protect our rights and property and to facilitate the proper functioning of the Site.
+
+
+## PRIVACY POLICY
+
+We care about data privacy and security. Please review our [Privacy Policy](/privacy). By using the Site, you agree to be bound by our Privacy Policy, which is incorporated into these Terms of Use. Please be advised the Site is hosted in the United States. If you access the Site from the European Union, Asia, or any other region of the world with laws or other requirements governing personal data collection, use, or disclosure that differ from applicable laws in the United States, then through your continued use of the Site, you are transferring your data to the United States, and you expressly consent to have your data transferred to and processed in the United States. Further, we do not knowingly accept, request, or solicit information from children or knowingly market to children. Therefore, in accordance with the U.S. Children’s Online Privacy Protection Act, if we receive actual knowledge that anyone under the age of 13 has provided personal information to us without the requisite and verifiable parental consent, we will delete that information from the Site as quickly as is reasonably practical.
+
+## TERM AND TERMINATION
+
+These Terms of Use shall remain in full force and effect while you use the Site. WITHOUT LIMITING ANY OTHER PROVISION OF THESE TERMS OF USE, WE RESERVE THE RIGHT TO, IN OUR SOLE DISCRETION AND WITHOUT NOTICE OR LIABILITY, DENY ACCESS TO AND USE OF THE SITE (INCLUDING BLOCKING CERTAIN IP ADDRESSES), TO ANY PERSON FOR ANY REASON OR FOR NO REASON, INCLUDING WITHOUT LIMITATION FOR BREACH OF ANY REPRESENTATION, WARRANTY, OR COVENANT CONTAINED IN THESE TERMS OF USE OR OF ANY APPLICABLE LAW OR REGULATION. WE MAY TERMINATE YOUR USE OR PARTICIPATION IN THE SITE OR DELETE ANY CONTENT OR INFORMATION THAT YOU POSTED AT ANY TIME, WITHOUT WARNING, IN OUR SOLE DISCRETION.
+
+
+## MODIFICATIONS AND INTERRUPTIONS
+
+We reserve the right to change, modify, or remove the contents of the Site at any time or for any reason at our sole discretion without notice. However, we have no obligation to update any information on our Site. We also reserve the right to modify or discontinue all or part of the Site without notice at any time. We will not be liable to you or any third party for any modification, suspension, or discontinuance of the Site.
+
+We cannot guarantee the Site will be available at all times. We may experience hardware, software, or other problems or need to perform maintenance related to the Site, resulting in interruptions, delays, or errors. We reserve the right to change, revise, update, suspend, discontinue, or otherwise modify the Site at any time or for any reason without notice to you. You agree that we have no liability whatsoever for any loss, damage, or inconvenience caused by your inability to access or use the Site during any downtime or discontinuance of the Site. Nothing in these Terms of Use will be construed to obligate us to maintain and support the Site or to supply any corrections, updates, or releases in connection therewith.
+
+
+## GOVERNING LAW
+
+These Terms of Use and your use of the Site are governed by and construed in accordance with the laws of the State of Texas applicable to agreements made and to be entirely performed within the State of Texas, without regard to its conflict of law principles.
+
+
+## DISPUTE RESOLUTION
+
+### Informal Negotiations
+
+To expedite resolution and control the cost of any dispute, controversy, or claim related to these Terms of Use (each a "Dispute" and collectively, the “Disputes”) brought by either you or us (individually, a “Party” and collectively, the “Parties”), the Parties agree to first attempt to negotiate any Dispute (except those Disputes expressly provided below) informally for at least thirty (30) days before initiating arbitration. Such informal negotiations commence upon written notice from one Party to the other Party.
+
+
+### Binding Arbitration
+
+If the Parties are unable to resolve a Dispute through informal negotiations, the Dispute (except those Disputes expressly excluded below) will be finally and exclusively resolved by binding arbitration. YOU UNDERSTAND THAT WITHOUT THIS PROVISION, YOU WOULD HAVE THE RIGHT TO SUE IN COURT AND HAVE A JURY TRIAL. The arbitration shall be commenced and conducted under the Commercial Arbitration Rules of the American Arbitration Association ("AAA") and, where appropriate, the AAA’s Supplementary Procedures for Consumer Related Disputes ("AAA Consumer Rules"), both of which are available at the AAA website www.adr.org. Your arbitration fees and your share of arbitrator compensation shall be governed by the AAA Consumer Rules and, where appropriate, limited by the AAA Consumer Rules. If such costs are determined to by the arbitrator to be excessive, we will pay all arbitration fees and expenses. The arbitration may be conducted in person, through the submission of documents, by phone, or online. The arbitrator will make a decision in writing, but need not provide a statement of reasons unless requested by either Party. The arbitrator must follow applicable law, and any award may be challenged if the arbitrator fails to do so. Except where otherwise required by the applicable AAA rules or applicable law, the arbitration will take place in Travis County, Texas. Except as otherwise provided herein, the Parties may litigate in court to compel arbitration, stay proceedings pending arbitration, or to confirm, modify, vacate, or enter judgment on the award entered by the arbitrator.
+
+If for any reason, a Dispute proceeds in court rather than arbitration, the Dispute shall be commenced or prosecuted in the state and federal courts located in Travis County, Texas, and the Parties hereby consent to, and waive all defenses of lack of personal jurisdiction, and forum non conveniens with respect to venue and jurisdiction in such state and federal courts. Application of the United Nations Convention on Contracts for the International Sale of Goods and the the Uniform Computer Information Transaction Act (UCITA) are excluded from these Terms of Use.
+
+In no event shall any Dispute brought by either Party related in any way to the Site be commenced more than one (1) years after the cause of action arose. If this provision is found to be illegal or unenforceable, then neither Party will elect to arbitrate any Dispute falling within that portion of this provision found to be illegal or unenforceable and such Dispute shall be decided by a court of competent jurisdiction within the courts listed for jurisdiction above, and the Parties agree to submit to the personal jurisdiction of that court.
+
+
+### Restrictions
+
+The Parties agree that any arbitration shall be limited to the Dispute between the Parties individually. To the full extent permitted by law, (a) no arbitration shall be joined with any other proceeding; (b) there is no right or authority for any Dispute to be arbitrated on a class-action basis or to utilize class action procedures; and (c) there is no right or authority for any Dispute to be brought in a purported representative capacity on behalf of the general public or any other persons.
+
+
+### Exceptions to Informal Negotiations and Arbitration
+
+The Parties agree that the following Disputes are not subject to the above provisions concerning informal negotiations and binding arbitration: (a) any Disputes seeking to enforce or protect, or concerning the validity of, any of the intellectual property rights of a Party; (b) any Dispute related to, or arising from, allegations of theft, piracy, invasion of privacy, or unauthorized use; and (c) any claim for injunctive relief. If this provision is found to be illegal or unenforceable, then neither Party will elect to arbitrate any Dispute falling within that portion of this provision found to be illegal or unenforceable and such Dispute shall be decided by a court of competent jurisdiction within the courts listed for jurisdiction above, and the Parties agree to submit to the personal jurisdiction of that court.
+
+
+## CORRECTIONS
+
+There may be information on the Site that contains typographical errors, inaccuracies, or omissions. We reserve the right to correct any errors, inaccuracies, or omissions and to change or update the information on the Site at any time, without prior notice.
+
+
+## DISCLAIMER
+
+THE SITE IS PROVIDED ON AN AS-IS AND AS-AVAILABLE BASIS. YOU AGREE THAT YOUR USE OF THE SITE AND OUR SERVICES WILL BE AT YOUR SOLE RISK. TO THE FULLEST EXTENT PERMITTED BY LAW, WE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, IN CONNECTION WITH THE SITE AND YOUR USE THEREOF, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. WE MAKE NO WARRANTIES OR REPRESENTATIONS ABOUT THE ACCURACY OR COMPLETENESS OF THE SITE’S CONTENT OR THE CONTENT OF ANY WEBSITES LINKED TO THE SITE AND WE WILL ASSUME NO LIABILITY OR RESPONSIBILITY FOR ANY (1) ERRORS, MISTAKES, OR INACCURACIES OF CONTENT AND MATERIALS, (2) PERSONAL INJURY OR PROPERTY DAMAGE, OF ANY NATURE WHATSOEVER, RESULTING FROM YOUR ACCESS TO AND USE OF THE SITE, (3) ANY UNAUTHORIZED ACCESS TO OR USE OF OUR SECURE SERVERS AND/OR ANY AND ALL PERSONAL INFORMATION AND/OR FINANCIAL INFORMATION STORED THEREIN, (4) ANY INTERRUPTION OR CESSATION OF TRANSMISSION TO OR FROM THE SITE, (5) ANY BUGS, VIRUSES, TROJAN HORSES, OR THE LIKE WHICH MAY BE TRANSMITTED TO OR THROUGH THE SITE BY ANY THIRD PARTY, AND/OR (6) ANY ERRORS OR OMISSIONS IN ANY CONTENT AND MATERIALS OR FOR ANY LOSS OR DAMAGE OF ANY KIND INCURRED AS A RESULT OF THE USE OF ANY CONTENT POSTED, TRANSMITTED, OR OTHERWISE MADE AVAILABLE VIA THE SITE. WE DO NOT WARRANT, ENDORSE, GUARANTEE, OR ASSUME RESPONSIBILITY FOR ANY PRODUCT OR SERVICE ADVERTISED OR OFFERED BY A THIRD PARTY THROUGH THE SITE, ANY HYPERLINKED WEBSITE, OR ANY WEBSITE OR MOBILE APPLICATION FEATURED IN ANY BANNER OR OTHER ADVERTISING, AND WE WILL NOT BE A PARTY TO OR IN ANY WAY BE RESPONSIBLE FOR MONITORING ANY TRANSACTION BETWEEN YOU AND ANY THIRD-PARTY PROVIDERS OF PRODUCTS OR SERVICES. AS WITH THE PURCHASE OF A PRODUCT OR SERVICE THROUGH ANY MEDIUM OR IN ANY ENVIRONMENT, YOU SHOULD USE YOUR BEST JUDGMENT AND EXERCISE CAUTION WHERE APPROPRIATE.
+
+
+## LIMITATIONS OF LIABILITY
+
+IN NO EVENT WILL WE OR OUR DIRECTORS, EMPLOYEES, OR AGENTS BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, EXEMPLARY, INCIDENTAL, SPECIAL, OR PUNITIVE DAMAGES, INCLUDING LOST PROFIT, LOST REVENUE, LOSS OF DATA, OR OTHER DAMAGES ARISING FROM YOUR USE OF THE SITE, EVEN IF WE HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. NOTWITHSTANDING ANYTHING TO THE CONTRARY CONTAINED HEREIN, OUR LIABILITY TO YOU FOR ANY CAUSE WHATSOEVER AND REGARDLESS OF THE FORM OF THE ACTION, WILL AT ALL TIMES BE LIMITED TO THE AMOUNT PAID, IF ANY, BY YOU TO US DURING THE SIX (6) MONTH PERIOD PRIOR TO ANY CAUSE OF ACTION ARISING. CERTAIN STATE LAWS DO NOT ALLOW LIMITATIONS ON IMPLIED WARRANTIES OR THE EXCLUSION OR LIMITATION OF CERTAIN DAMAGES. IF THESE LAWS APPLY TO YOU, SOME OR ALL OF THE ABOVE DISCLAIMERS OR LIMITATIONS MAY NOT APPLY TO YOU, AND YOU MAY HAVE ADDITIONAL RIGHTS.
+
+
+## INDEMNIFICATION
+
+You agree to defend, indemnify, and hold us harmless, including our subsidiaries, affiliates, and all of our respective officers, agents, partners, and employees, from and against any loss, damage, liability, claim, or demand, including reasonable attorneys’ fees and expenses, made by any third party due to or arising out of: (1) use of the Site; (2) breach of these Terms of Use; (3) any breach of your representations and warranties set forth in these Terms of Use; (4) your violation of the rights of a third party, including but not limited to intellectual property rights; or (5) any overt harmful act toward any other user of the Site with whom you connected via the Site. Notwithstanding the foregoing, we reserve the right, at your expense, to assume the exclusive defense and control of any matter for which you are required to indemnify us, and you agree to cooperate, at your expense, with our defense of such claims. We will use reasonable efforts to notify you of any such claim, action, or proceeding which is subject to this indemnification upon becoming aware of it.
+
+
+## USER DATA
+
+We will maintain certain data that you transmit to the Site for the purpose of managing the performance of the Site, as well as data relating to your use of the Site. Although we perform regular routine backups of data, you are solely responsible for all data that you transmit or that relates to any activity you have undertaken using the Site. You agree that we shall have no liability to you for any loss or corruption of any such data, and you hereby waive any right of action against us arising from any such loss or corruption of such data.
+
+
+## ELECTRONIC COMMUNICATIONS, TRANSACTIONS, AND SIGNATURES
+
+Visiting the Site, sending us emails, and completing online forms constitute electronic communications. You consent to receive electronic communications, and you agree that all agreements, notices, disclosures, and other communications we provide to you electronically, via email and on the Site, satisfy any legal requirement that such communication be in writing. YOU HEREBY AGREE TO THE USE OF ELECTRONIC SIGNATURES, CONTRACTS, ORDERS, AND OTHER RECORDS, AND TO ELECTRONIC DELIVERY OF NOTICES, POLICIES, AND RECORDS OF TRANSACTIONS INITIATED OR COMPLETED BY US OR VIA THE SITE. You hereby waive any rights or requirements under any statutes, regulations, rules, ordinances, or other laws in any jurisdiction which require an original signature or delivery or retention of non-electronic records, or to payments or the granting of credits by any means other than electronic means.
+
+
+## CALIFORNIA USERS AND RESIDENTS
+
+If any complaint with us is not satisfactorily resolved, you can contact the Complaint Assistance Unit of the Division of Consumer Services of the California Department of Consumer Affairs in writing at 1625 North Market Blvd., Suite N 112, Sacramento, California 95834 or by telephone at (800) 952-5210 or (916) 445-1254.
+
+
+## MISCELLANEOUS
+
+These Terms of Use and any policies or operating rules posted by us on the Site or in respect to the Site constitute the entire agreement and understanding between you and us. Our failure to exercise or enforce any right or provision of these Terms of Use shall not operate as a waiver of such right or provision. These Terms of Use operate to the fullest extent permissible by law. We may assign any or all of our rights and obligations to others at any time. We shall not be responsible or liable for any loss, damage, delay, or failure to act caused by any cause beyond our reasonable control. If any provision or part of a provision of these Terms of Use is determined to be unlawful, void, or unenforceable, that provision or part of the provision is deemed severable from these Terms of Use and does not affect the validity and enforceability of any remaining provisions. There is no joint venture, partnership, employment or agency relationship created between you and us as a result of these Terms of Use or use of the Site. You agree that these Terms of Use will not be construed against us by virtue of having drafted them. You hereby waive any and all defenses you may have based on the electronic form of these Terms of Use and the lack of signing by the parties hereto to execute these Terms of Use.
+
+## CONTACT US
+
+In order to resolve a complaint regarding the Site or to receive further information regarding use of the Site, please contact us at:
+
+NumFOCUS, Inc. P.O. Box 90596 Austin, TX, USA 78709 info@numfocus.org +1 (512) 222-5449
+
+
+
From 3ee533343dfc5abc6eee1a8393aa3b3853ad51d0 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:38:47 +0000
Subject: [PATCH 108/909] New translations privacy.md (Korean)
---
content/ko/privacy.md | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
create mode 100644 content/ko/privacy.md
diff --git a/content/ko/privacy.md b/content/ko/privacy.md
new file mode 100644
index 0000000000..a3674dd48a
--- /dev/null
+++ b/content/ko/privacy.md
@@ -0,0 +1,18 @@
+---
+title: Privacy Policy
+sidebar: false
+---
+
+**numpy.org** is operated by [NumFOCUS, Inc.](https://numfocus.org), the fiscal sponsor of the NumPy project. For the Privacy Policy of this website please refer to https://numfocus.org/privacy-policy.
+
+If you have any questions about the policy or NumFOCUS’s data collection, use, and disclosure practices, please contact the NumFOCUS staff at privacy@numfocus.org.
+
+
+
+
+
+
+
+
+
+
From 5c9787da061761cc31d9a54ea83728536ca6f78c Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:38:49 +0000
Subject: [PATCH 109/909] New translations press-kit.md (Korean)
---
content/ko/press-kit.md | 8 ++++++++
1 file changed, 8 insertions(+)
create mode 100644 content/ko/press-kit.md
diff --git a/content/ko/press-kit.md b/content/ko/press-kit.md
new file mode 100644
index 0000000000..2309040ad2
--- /dev/null
+++ b/content/ko/press-kit.md
@@ -0,0 +1,8 @@
+---
+title: Press kit
+sidebar: false
+---
+
+We would like to make it easy for you to include the NumPy project identity in your next academic paper, course materials, or presentation.
+
+You will find several high-resolution versions of the NumPy logo [here](https://github.com/numpy/numpy/tree/master/branding/logo). Note that by using the numpy.org resources, you accept the [NumPy Code of Conduct](/code-of-conduct).
From 1aed54a172c48beb604324333fd5679609ec4005 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:38:50 +0000
Subject: [PATCH 110/909] New translations learn.md (Korean)
---
content/ko/learn.md | 84 +++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 84 insertions(+)
create mode 100644 content/ko/learn.md
diff --git a/content/ko/learn.md b/content/ko/learn.md
new file mode 100644
index 0000000000..87d12db866
--- /dev/null
+++ b/content/ko/learn.md
@@ -0,0 +1,84 @@
+---
+title: Learn
+sidebar: false
+---
+
+**공식 NumPy 문서는 [여기](https://numpy.org/doc/stable)에 있습니다.**
+
+아래는 선별된 외부 자료들의 모음입니다. 이곳에 기여하고 싶다면, [이 페이지의 끝](#add-to-this-list)을 참조하세요.
+***
+
+## Beginners
+
+여기에 NumPy에 대한 많은 자료가 있습니다. NumPy가 처음이라면 이 자료들을 강력하게 권장합니다.
+
+ **튜토리얼**
+
+* [NumPy Quickstart Tutorial](https://numpy.org/devdocs/user/quickstart.html)
+* [SciPy Lectures](https://scipy-lectures.org/) Besides covering NumPy, these lectures offer a broader introduction to the scientific Python ecosystem.
+* [NumPy: the absolute basics for beginners](https://numpy.org/devdocs/user/absolute_beginners.html)
+* [Machine Learning Plus - Introduction to ndarray](https://www.machinelearningplus.com/python/numpy-tutorial-part1-array-python-examples/)
+* [Edureka - Learn NumPy Arrays with Examples ](https://www.edureka.co/blog/python-numpy-tutorial/)
+* [Dataquest - NumPy Tutorial: Data Analysis with Python](https://www.dataquest.io/blog/numpy-tutorial-python/)
+* [NumPy tutorial *by Nicolas Rougier*](https://github.com/rougier/numpy-tutorial)
+* [Stanford CS231 *by Justin Johnson*](http://cs231n.github.io/python-numpy-tutorial/)
+* [NumPy User Guide](https://numpy.org/devdocs)
+
+ **도서**
+
+* [Guide to NumPy *by Travis E. Oliphant*](http://web.mit.edu/dvp/Public/numpybook.pdf) This is a free version 1 from 2006. For the latest copy (2015) see [here](https://www.barnesandnoble.com/w/guide-to-numpy-travis-e-oliphant-phd/1122853007).
+* [From Python to NumPy *by Nicolas P. Rougier*](https://www.labri.fr/perso/nrougier/from-python-to-numpy/)
+* [Elegant SciPy](https://www.amazon.com/Elegant-SciPy-Art-Scientific-Python/dp/1491922877) *by Juan Nunez-Iglesias, Stefan van der Walt, and Harriet Dashnow*
+
+You may also want to check out the [Goodreads list](https://www.goodreads.com/shelf/show/python-scipy) on the subject of "Python+SciPy." Most books there are about the "SciPy ecosystem," which has NumPy at its core.
+
+ **영상**
+
+* [Introduction to Numerical Computing with NumPy](http://youtu.be/ZB7BZMhfPgk) *by Alex Chabot-Leclerc*
+
+***
+
+## Advanced
+
+Indexing, Splitting, Stacking, 선형대수 등과 같은 NumPy의 개념을 더 잘 이해하러면 이 고급 자료들을 참조 해보세요.
+
+ **튜토리얼**
+
+* [100 NumPy Exercises](http://www.labri.fr/perso/nrougier/teaching/numpy.100/index.html) *by Nicolas P. Rougier*
+* [An Introduction to NumPy and Scipy](https://engineering.ucsb.edu/~shell/che210d/numpy.pdf) *by M. Scott Shell*
+* [Numpy Medkits](http://mentat.za.net/numpy/numpy_advanced_slides/) *by Stéfan van der Walt*
+* [NumPy in Python (Advanced)](https://www.geeksforgeeks.org/numpy-python-set-2-advanced/)
+* [Advanced Indexing](https://www.tutorialspoint.com/numpy/numpy_advanced_indexing.htm)
+* [Machine Learning and Data Analytics with NumPy](https://www.machinelearningplus.com/python/numpy-tutorial-python-part2/)
+
+ **도서**
+
+* [Python Data Science Handbook](https://www.amazon.com/Python-Data-Science-Handbook-Essential/dp/1491912057) *by Jake Vanderplas*
+* [Python for Data Analysis](https://www.amazon.com/Python-Data-Analysis-Wrangling-IPython/dp/1491957662) *by Wes McKinney*
+* [Numerical Python: Scientific Computing and Data Science Applications with Numpy, SciPy, and Matplotlib](https://www.amazon.com/Numerical-Python-Scientific-Applications-Matplotlib/dp/1484242459) *by Robert Johansson*
+
+ **영상**
+
+* [Advanced NumPy - broadcasting rules, strides, and advanced indexing](https://www.youtube.com/watch?v=cYugp9IN1-Q) *by Juan Nunuz-Iglesias*
+* [Advanced Indexing Operations in NumPy Arrays](https://www.youtube.com/watch?v=2WTDrSkQBng) *by Amuls Academy*
+
+***
+
+## NumPy Talks
+
+* [The Future of NumPy Indexing](https://www.youtube.com/watch?v=o0EacbIbf58) *by Jaime Fernández* (2016)
+* [Evolution of Array Computing in Python](https://www.youtube.com/watch?v=HVLPJnvInzM&t=10s) *by Ralf Gommers* (2019)
+* [NumPy: what has changed and what is going to change?](https://www.youtube.com/watch?v=YFLVQFjRmPY) *by Matti Picus* (2019)
+* [Inside NumPy](https://www.youtube.com/watch?v=dBTJD_FDVjU) *by Ralf Gommers, Sebastian Berg, Matti Picus, Tyler Reddy, Stefan van der Walt, Charles Harris* (2019)
+* [Brief Review of Array Computing in Python](https://www.youtube.com/watch?v=f176j2g2eNc) *by Travis Oliphant* (2019)
+
+***
+
+## NumPy 인용하기
+
+만약 당신의 연구에서 NumPy가 중요한 역할을 수행하였고 학술 간행물에서 출판하기 위해서는 [이 인용 정보](/citing-numpy)를 참조하세요.
+
+## 이 목록에 기여하기
+
+
+이 목록에 자료를 추가하려면 [Pull Request](https://github.com/numpy/numpy.org/blob/master/content/en/learn.md)를 통해서 제출하세요. 당신이 추천한 자료가 왜 이 페이지에 올라야하는지, 또한 어떤 사람들이 가장 좋아할지 말해주세요.
From e944fcce3ebe7566b7bf8b28577b99b0154c30fd Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:38:52 +0000
Subject: [PATCH 111/909] New translations code-of-conduct.md (Korean)
---
content/ko/code-of-conduct.md | 83 +++++++++++++++++++++++++++++++++++
1 file changed, 83 insertions(+)
create mode 100644 content/ko/code-of-conduct.md
diff --git a/content/ko/code-of-conduct.md b/content/ko/code-of-conduct.md
new file mode 100644
index 0000000000..efcde754ae
--- /dev/null
+++ b/content/ko/code-of-conduct.md
@@ -0,0 +1,83 @@
+---
+title: NumPy Code of Conduct
+sidebar: false
+aliases:
+ - /conduct.html
+---
+
+### Introduction
+
+This Code of Conduct applies to all spaces managed by the NumPy project, including all public and private mailing lists, issue trackers, wikis, blogs, Twitter, and any other communication channel used by our community. The NumPy project does not organise in-person events, however events related to our community should have a code of conduct similar in spirit to this one.
+
+This Code of Conduct should be honored by everyone who participates in the NumPy community formally or informally, or claims any affiliation with the project, in any project-related activities and especially when representing the project, in any role.
+
+This code is not exhaustive or complete. It serves to distill our common understanding of a collaborative, shared environment and goals. Please try to follow this code in spirit as much as in letter, to create a friendly and productive environment that enriches the surrounding community.
+
+### Specific Guidelines
+
+We strive to:
+
+1. Be open. We invite anyone to participate in our community. We prefer to use public methods of communication for project-related messages, unless discussing something sensitive. This applies to messages for help or project-related support, too; not only is a public support request much more likely to result in an answer to a question, it also ensures that any inadvertent mistakes in answering are more easily detected and corrected.
+2. Be empathetic, welcoming, friendly, and patient. We work together to resolve conflict, and assume good intentions. We may all experience some frustration from time to time, but we do not allow frustration to turn into a personal attack. A community where people feel uncomfortable or threatened is not a productive one.
+3. Be collaborative. Our work will be used by other people, and in turn we will depend on the work of others. When we make something for the benefit of the project, we are willing to explain to others how it works, so that they can build on the work to make it even better. Any decision we make will affect users and colleagues, and we take those consequences seriously when making decisions.
+4. Be inquisitive. Nobody knows everything! Asking questions early avoids many problems later, so we encourage questions, although we may direct them to the appropriate forum. We will try hard to be responsive and helpful.
+5. Be careful in the words that we choose. We are careful and respectful in our communication, and we take responsibility for our own speech. Be kind to others. Do not insult or put down other participants. We will not accept harassment or other exclusionary behaviour, such as:
+ * Violent threats or language directed against another person.
+ * Sexist, racist, or otherwise discriminatory jokes and language.
+ * Posting sexually explicit or violent material.
+ * Posting (or threatening to post) other people’s personally identifying information (“doxing”).
+ * Sharing private content, such as emails sent privately or non-publicly, or unlogged forums such as IRC channel history, without the sender’s consent.
+ * Personal insults, especially those using racist or sexist terms.
+ * Unwelcome sexual attention.
+ * Excessive profanity. Please avoid swearwords; people differ greatly in their sensitivity to swearing.
+ * Repeated harassment of others. In general, if someone asks you to stop, then stop.
+ * Advocating for, or encouraging, any of the above behaviour.
+
+### Diversity Statement
+
+The NumPy project welcomes and encourages participation by everyone. We are committed to being a community that everyone enjoys being part of. Although we may not always be able to accommodate each individual’s preferences, we try our best to treat everyone kindly.
+
+No matter how you identify yourself or how others perceive you: we welcome you. Though no list can hope to be comprehensive, we explicitly honour diversity in: age, culture, ethnicity, genotype, gender identity or expression, language, national origin, neurotype, phenotype, political beliefs, profession, race, religion, sexual orientation, socioeconomic status, subculture and technical ability, to the extent that these do not conflict with this code of conduct.
+
+Though we welcome people fluent in all languages, NumPy development is conducted in English.
+
+Standards for behaviour in the NumPy community are detailed in the Code of Conduct above. Participants in our community should uphold these standards in all their interactions and help others to do so as well (see next section).
+
+### Reporting Guidelines
+
+We know that it is painfully common for internet communication to start at or devolve into obvious and flagrant abuse. We also recognize that sometimes people may have a bad day, or be unaware of some of the guidelines in this Code of Conduct. Please keep this in mind when deciding on how to respond to a breach of this Code.
+
+For clearly intentional breaches, report those to the Code of Conduct Committee (see below). For possibly unintentional breaches, you may reply to the person and point out this code of conduct (either in public or in private, whatever is most appropriate). If you would prefer not to do that, please feel free to report to the Code of Conduct Committee directly, or ask the Committee for advice, in confidence.
+
+You can report issues to the NumPy Code of Conduct Committee at numpy-conduct@googlegroups.com.
+
+Currently, the Committee consists of:
+
+* Stefan van der Walt
+* Melissa Weber Mendonça
+* Anirudh Subramanian
+
+If your report involves any members of the Committee, or if they feel they have a conflict of interest in handling it, then they will recuse themselves from considering your report. Alternatively, if for any reason you feel uncomfortable making a report to the Committee, then you can also contact senior NumFOCUS staff at [conduct@numfocus.org](https://numfocus.org/code-of-conduct#persons-responsible).
+
+### Incident reporting resolution & Code of Conduct enforcement
+
+_This section summarizes the most important points, more details can be found in_ [NumPy Code of Conduct - How to follow up on a report](/report-handling-manual).
+
+We will investigate and respond to all complaints. The NumPy Code of Conduct Committee and the NumPy Steering Committee (if involved) will protect the identity of the reporter, and treat the content of complaints as confidential (unless the reporter agrees otherwise).
+
+In case of severe and obvious breaches, e.g. personal threat or violent, sexist or racist language, we will immediately disconnect the originator from NumPy communication channels; please see the manual for details.
+
+In cases not involving clear severe and obvious breaches of this Code of Conduct the process for acting on any received Code of Conduct violation report will be:
+
+1. acknowledge report is received,
+2. reasonable discussion/feedback,
+3. mediation (if feedback didn’t help, and only if both reporter and reportee agree to this),
+4. enforcement via transparent decision (see [Resolutions](/report-handling-manual#resolutions)) by the Code of Conduct Committee.
+
+The Committee will respond to any report as soon as possible, and at most within 72 hours.
+
+### Endnotes
+
+We are thankful to the groups behind the following documents, from which we drew content and inspiration:
+
+- [The SciPy Code of Conduct](https://docs.scipy.org/doc/scipy/reference/dev/conduct/code_of_conduct.html)
From 4a0891c7cea9d5a25ddf8d4c8d08f29caf8857ad Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:38:53 +0000
Subject: [PATCH 112/909] New translations terms.md (Japanese)
---
content/ja/terms.md | 178 ++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 178 insertions(+)
create mode 100644 content/ja/terms.md
diff --git a/content/ja/terms.md b/content/ja/terms.md
new file mode 100644
index 0000000000..9a66045505
--- /dev/null
+++ b/content/ja/terms.md
@@ -0,0 +1,178 @@
+---
+title: Terms of Use
+sidebar: false
+---
+
+*Last updated January 4, 2020*
+
+
+## AGREEMENT TO TERMS
+
+These Terms of Use constitute a legally binding agreement made between you, whether personally or on behalf of an entity (“you”) and NumPy ("**Project**", “**we**”, “**us**”, or “**our**”), concerning your access to and use of the numpy.org website as well as any other media form, media channel, mobile website or mobile application related, linked, or otherwise connected thereto (collectively, the “Site”). You agree that by accessing the Site, you have read, understood, and agreed to be bound by all of these Terms of Use. IF YOU DO NOT AGREE WITH ALL OF THESE TERMS OF USE, THEN YOU ARE EXPRESSLY PROHIBITED FROM USING THE SITE AND YOU MUST DISCONTINUE USE IMMEDIATELY.
+
+
+
+Supplemental terms and conditions or documents that may be posted on the Site from time to time are hereby expressly incorporated herein by reference. We reserve the right, in our sole discretion, to make changes or modifications to these Terms of Use at any time and for any reason. We will alert you about any changes by updating the “Last updated” date of these Terms of Use, and you waive any right to receive specific notice of each such change. It is your responsibility to periodically review these Terms of Use to stay informed of updates. You will be subject to, and will be deemed to have been made aware of and to have accepted, the changes in any revised Terms of Use by your continued use of the Site after the date such revised Terms of Use are posted.
+
+
+
+The information provided on the Site is not intended for distribution to or use by any person or entity in any jurisdiction or country where such distribution or use would be contrary to law or regulation or which would subject us to any registration requirement within such jurisdiction or country. Accordingly, those persons who choose to access the Site from other locations do so on their own initiative and are solely responsible for compliance with local laws, if and to the extent local laws are applicable.
+
+
+## USER REPRESENTATIONS
+
+By using the Site, you represent and warrant that: (1) you have the legal capacity and you agree to comply with these Terms of Use; (2) you will not use the Site for any illegal or unauthorized purpose; and (3) your use of the Site will not violate any applicable law or regulation.
+
+
+If you provide any information that is untrue, inaccurate, not current, or incomplete, we have the right to refuse any and all current or future use of the Site (or any portion thereof).
+
+
+## PROHIBITED ACTIVITIES
+
+You may not access or use the Site for any purpose other than that for which we make the Site available.
+
+As a user of the Site, you agree not to:
+
+1. Systematically retrieve data or other content from the Site to create or compile, directly or indirectly, a collection, compilation, database, or directory without written permission from us.
+
+2. Make any unauthorized use of the Site, including collecting usernames and/or email addresses of users by electronic or other means for the purpose of sending unsolicited email, or creating user accounts by automated means or under false pretenses.
+
+3. Use the Site to advertise or offer to sell goods and services.
+
+4. Circumvent, disable, or otherwise interfere with security-related features of the Site.
+
+5. Engage in unauthorized framing of or linking to the Site.
+
+6. Trick, defraud, or mislead us and other users, especially in any attempt to learn sensitive account information such as user passwords.
+
+7. Make improper use of our support services or submit false reports of abuse or misconduct.
+
+8. Engage in any automated use of the system, such as using scripts to send comments or messages, or using any data mining, robots, or similar data gathering and extraction tools.
+
+9. Interfere with, disrupt, or create an undue burden on the Site or the networks or services connected to the Site.
+
+10. Attempt to impersonate another user or person or use the username of another user.
+
+11. Use any information obtained from the Site in order to harass, abuse, or harm another person.
+
+12. Disparage, tarnish, or otherwise harm, in our opinion, us and/or the Site.
+
+13. Except as may be the result of standard search engine or Internet browser usage, use, launch, develop, or distribute any automated system, including without limitation, any spider, robot, cheat utility, scraper, or offline reader that accesses the Site, or using or launching any unauthorized script or other software.
+
+14. Upload or transmit (or attempt to upload or to transmit) any material that acts as a passive or active information collection or transmission mechanism, including without limitation, clear graphics interchange formats (“gifs”), 1×1 pixels, web bugs, cookies, or other similar devices (sometimes referred to as “spyware” or “passive collection mechanisms” or “pcms”).
+
+15. Upload or transmit (or attempt to upload or to transmit) viruses, Trojan horses, or other material, including excessive use of capital letters and spamming (continuous posting of repetitive text), that interferes with any party’s uninterrupted use and enjoyment of the Site or modifies, impairs, disrupts, alters, or interferes with the use, features, functions, operation, or maintenance of the Site.
+
+16. Harass, annoy, intimidate, or threaten any of our employees or agents engaged in providing any portion of the Site to you.
+
+17. Attempt to bypass any measures of the Site designed to prevent or restrict access to the Site, or any portion of the Site.
+
+
+## SUBMISSIONS
+
+You acknowledge and agree that any questions, comments, suggestions, ideas, feedback, or other information regarding the Site ("Submissions") provided by you to us are non-confidential and shall become our sole property. We shall own exclusive rights, including all intellectual property rights, and shall be entitled to the unrestricted use and dissemination of these Submissions for any lawful purpose, commercial or otherwise, without acknowledgment or compensation to you. You hereby waive all moral rights to any such Submissions, and you hereby warrant that any such Submissions are original with you or that you have the right to submit such Submissions. You agree there shall be no recourse against us for any alleged or actual infringement or misappropriation of any proprietary right in your Submissions.
+
+## THIRD-PARTY WEBSITES AND CONTENT
+
+The Site may contain (or you may be sent via the Site) links to other websites ("Third-Party Websites") as well as articles, photographs, text, graphics, pictures, designs, music, sound, video, information, applications, software, and other content or items belonging to or originating from third parties ("Third-Party Content"). Such Third-Party Websites and Third-Party Content are not investigated, monitored, or checked for accuracy, appropriateness, or completeness by us, and we are not responsible for any Third-Party Websites accessed through the Site or any Third-Party Content posted on, available through, or installed from the Site, including the content, accuracy, offensiveness, opinions, reliability, privacy practices, or other policies of or contained in the Third-Party Websites or the Third-Party Content. Inclusion of, linking to, or permitting the use or installation of any Third-Party Websites or any Third-Party Content does not imply approval or endorsement thereof by us. If you decide to leave the Site and access the Third-Party Websites or to use or install any Third-Party Content, you do so at your own risk, and you should be aware these Terms of Use no longer govern. You should review the applicable terms and policies, including privacy and data gathering practices, of any website to which you navigate from the Site or relating to any applications you use or install from the Site. Any purchases you make through Third-Party Websites will be through other websites and from other companies, and we take no responsibility whatsoever in relation to such purchases which are exclusively between you and the applicable third party. You agree and acknowledge that we do not endorse the products or services offered on Third-Party Websites and you shall hold us harmless from any harm caused by your purchase of such products or services. Additionally, you shall hold us harmless from any losses sustained by you or harm caused to you relating to or resulting in any way from any Third-Party Content or any contact with Third-Party Websites.
+
+
+## SITE MANAGEMENT
+
+We reserve the right, but not the obligation, to: (1) monitor the Site for violations of these Terms of Use; (2) take appropriate legal action against anyone who, in our sole discretion, violates the law or these Terms of Use, including without limitation, reporting such user to law enforcement authorities; (3) in our sole discretion and without limitation, refuse, restrict access to, limit the availability of, or disable (to the extent technologically feasible) any of your Contributions or any portion thereof; (4) in our sole discretion and without limitation, notice, or liability, to remove from the Site or otherwise disable all files and content that are excessive in size or are in any way burdensome to our systems; and (5) otherwise manage the Site in a manner designed to protect our rights and property and to facilitate the proper functioning of the Site.
+
+
+## PRIVACY POLICY
+
+We care about data privacy and security. Please review our [Privacy Policy](/privacy). By using the Site, you agree to be bound by our Privacy Policy, which is incorporated into these Terms of Use. Please be advised the Site is hosted in the United States. If you access the Site from the European Union, Asia, or any other region of the world with laws or other requirements governing personal data collection, use, or disclosure that differ from applicable laws in the United States, then through your continued use of the Site, you are transferring your data to the United States, and you expressly consent to have your data transferred to and processed in the United States. Further, we do not knowingly accept, request, or solicit information from children or knowingly market to children. Therefore, in accordance with the U.S. Children’s Online Privacy Protection Act, if we receive actual knowledge that anyone under the age of 13 has provided personal information to us without the requisite and verifiable parental consent, we will delete that information from the Site as quickly as is reasonably practical.
+
+## TERM AND TERMINATION
+
+These Terms of Use shall remain in full force and effect while you use the Site. WITHOUT LIMITING ANY OTHER PROVISION OF THESE TERMS OF USE, WE RESERVE THE RIGHT TO, IN OUR SOLE DISCRETION AND WITHOUT NOTICE OR LIABILITY, DENY ACCESS TO AND USE OF THE SITE (INCLUDING BLOCKING CERTAIN IP ADDRESSES), TO ANY PERSON FOR ANY REASON OR FOR NO REASON, INCLUDING WITHOUT LIMITATION FOR BREACH OF ANY REPRESENTATION, WARRANTY, OR COVENANT CONTAINED IN THESE TERMS OF USE OR OF ANY APPLICABLE LAW OR REGULATION. WE MAY TERMINATE YOUR USE OR PARTICIPATION IN THE SITE OR DELETE ANY CONTENT OR INFORMATION THAT YOU POSTED AT ANY TIME, WITHOUT WARNING, IN OUR SOLE DISCRETION.
+
+
+## MODIFICATIONS AND INTERRUPTIONS
+
+We reserve the right to change, modify, or remove the contents of the Site at any time or for any reason at our sole discretion without notice. However, we have no obligation to update any information on our Site. We also reserve the right to modify or discontinue all or part of the Site without notice at any time. We will not be liable to you or any third party for any modification, suspension, or discontinuance of the Site.
+
+We cannot guarantee the Site will be available at all times. We may experience hardware, software, or other problems or need to perform maintenance related to the Site, resulting in interruptions, delays, or errors. We reserve the right to change, revise, update, suspend, discontinue, or otherwise modify the Site at any time or for any reason without notice to you. You agree that we have no liability whatsoever for any loss, damage, or inconvenience caused by your inability to access or use the Site during any downtime or discontinuance of the Site. Nothing in these Terms of Use will be construed to obligate us to maintain and support the Site or to supply any corrections, updates, or releases in connection therewith.
+
+
+## GOVERNING LAW
+
+These Terms of Use and your use of the Site are governed by and construed in accordance with the laws of the State of Texas applicable to agreements made and to be entirely performed within the State of Texas, without regard to its conflict of law principles.
+
+
+## DISPUTE RESOLUTION
+
+### Informal Negotiations
+
+To expedite resolution and control the cost of any dispute, controversy, or claim related to these Terms of Use (each a "Dispute" and collectively, the “Disputes”) brought by either you or us (individually, a “Party” and collectively, the “Parties”), the Parties agree to first attempt to negotiate any Dispute (except those Disputes expressly provided below) informally for at least thirty (30) days before initiating arbitration. Such informal negotiations commence upon written notice from one Party to the other Party.
+
+
+### Binding Arbitration
+
+If the Parties are unable to resolve a Dispute through informal negotiations, the Dispute (except those Disputes expressly excluded below) will be finally and exclusively resolved by binding arbitration. YOU UNDERSTAND THAT WITHOUT THIS PROVISION, YOU WOULD HAVE THE RIGHT TO SUE IN COURT AND HAVE A JURY TRIAL. The arbitration shall be commenced and conducted under the Commercial Arbitration Rules of the American Arbitration Association ("AAA") and, where appropriate, the AAA’s Supplementary Procedures for Consumer Related Disputes ("AAA Consumer Rules"), both of which are available at the AAA website www.adr.org. Your arbitration fees and your share of arbitrator compensation shall be governed by the AAA Consumer Rules and, where appropriate, limited by the AAA Consumer Rules. If such costs are determined to by the arbitrator to be excessive, we will pay all arbitration fees and expenses. The arbitration may be conducted in person, through the submission of documents, by phone, or online. The arbitrator will make a decision in writing, but need not provide a statement of reasons unless requested by either Party. The arbitrator must follow applicable law, and any award may be challenged if the arbitrator fails to do so. Except where otherwise required by the applicable AAA rules or applicable law, the arbitration will take place in Travis County, Texas. Except as otherwise provided herein, the Parties may litigate in court to compel arbitration, stay proceedings pending arbitration, or to confirm, modify, vacate, or enter judgment on the award entered by the arbitrator.
+
+If for any reason, a Dispute proceeds in court rather than arbitration, the Dispute shall be commenced or prosecuted in the state and federal courts located in Travis County, Texas, and the Parties hereby consent to, and waive all defenses of lack of personal jurisdiction, and forum non conveniens with respect to venue and jurisdiction in such state and federal courts. Application of the United Nations Convention on Contracts for the International Sale of Goods and the the Uniform Computer Information Transaction Act (UCITA) are excluded from these Terms of Use.
+
+In no event shall any Dispute brought by either Party related in any way to the Site be commenced more than one (1) years after the cause of action arose. If this provision is found to be illegal or unenforceable, then neither Party will elect to arbitrate any Dispute falling within that portion of this provision found to be illegal or unenforceable and such Dispute shall be decided by a court of competent jurisdiction within the courts listed for jurisdiction above, and the Parties agree to submit to the personal jurisdiction of that court.
+
+
+### Restrictions
+
+The Parties agree that any arbitration shall be limited to the Dispute between the Parties individually. To the full extent permitted by law, (a) no arbitration shall be joined with any other proceeding; (b) there is no right or authority for any Dispute to be arbitrated on a class-action basis or to utilize class action procedures; and (c) there is no right or authority for any Dispute to be brought in a purported representative capacity on behalf of the general public or any other persons.
+
+
+### Exceptions to Informal Negotiations and Arbitration
+
+The Parties agree that the following Disputes are not subject to the above provisions concerning informal negotiations and binding arbitration: (a) any Disputes seeking to enforce or protect, or concerning the validity of, any of the intellectual property rights of a Party; (b) any Dispute related to, or arising from, allegations of theft, piracy, invasion of privacy, or unauthorized use; and (c) any claim for injunctive relief. If this provision is found to be illegal or unenforceable, then neither Party will elect to arbitrate any Dispute falling within that portion of this provision found to be illegal or unenforceable and such Dispute shall be decided by a court of competent jurisdiction within the courts listed for jurisdiction above, and the Parties agree to submit to the personal jurisdiction of that court.
+
+
+## CORRECTIONS
+
+There may be information on the Site that contains typographical errors, inaccuracies, or omissions. We reserve the right to correct any errors, inaccuracies, or omissions and to change or update the information on the Site at any time, without prior notice.
+
+
+## DISCLAIMER
+
+THE SITE IS PROVIDED ON AN AS-IS AND AS-AVAILABLE BASIS. YOU AGREE THAT YOUR USE OF THE SITE AND OUR SERVICES WILL BE AT YOUR SOLE RISK. TO THE FULLEST EXTENT PERMITTED BY LAW, WE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, IN CONNECTION WITH THE SITE AND YOUR USE THEREOF, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. WE MAKE NO WARRANTIES OR REPRESENTATIONS ABOUT THE ACCURACY OR COMPLETENESS OF THE SITE’S CONTENT OR THE CONTENT OF ANY WEBSITES LINKED TO THE SITE AND WE WILL ASSUME NO LIABILITY OR RESPONSIBILITY FOR ANY (1) ERRORS, MISTAKES, OR INACCURACIES OF CONTENT AND MATERIALS, (2) PERSONAL INJURY OR PROPERTY DAMAGE, OF ANY NATURE WHATSOEVER, RESULTING FROM YOUR ACCESS TO AND USE OF THE SITE, (3) ANY UNAUTHORIZED ACCESS TO OR USE OF OUR SECURE SERVERS AND/OR ANY AND ALL PERSONAL INFORMATION AND/OR FINANCIAL INFORMATION STORED THEREIN, (4) ANY INTERRUPTION OR CESSATION OF TRANSMISSION TO OR FROM THE SITE, (5) ANY BUGS, VIRUSES, TROJAN HORSES, OR THE LIKE WHICH MAY BE TRANSMITTED TO OR THROUGH THE SITE BY ANY THIRD PARTY, AND/OR (6) ANY ERRORS OR OMISSIONS IN ANY CONTENT AND MATERIALS OR FOR ANY LOSS OR DAMAGE OF ANY KIND INCURRED AS A RESULT OF THE USE OF ANY CONTENT POSTED, TRANSMITTED, OR OTHERWISE MADE AVAILABLE VIA THE SITE. WE DO NOT WARRANT, ENDORSE, GUARANTEE, OR ASSUME RESPONSIBILITY FOR ANY PRODUCT OR SERVICE ADVERTISED OR OFFERED BY A THIRD PARTY THROUGH THE SITE, ANY HYPERLINKED WEBSITE, OR ANY WEBSITE OR MOBILE APPLICATION FEATURED IN ANY BANNER OR OTHER ADVERTISING, AND WE WILL NOT BE A PARTY TO OR IN ANY WAY BE RESPONSIBLE FOR MONITORING ANY TRANSACTION BETWEEN YOU AND ANY THIRD-PARTY PROVIDERS OF PRODUCTS OR SERVICES. AS WITH THE PURCHASE OF A PRODUCT OR SERVICE THROUGH ANY MEDIUM OR IN ANY ENVIRONMENT, YOU SHOULD USE YOUR BEST JUDGMENT AND EXERCISE CAUTION WHERE APPROPRIATE.
+
+
+## LIMITATIONS OF LIABILITY
+
+IN NO EVENT WILL WE OR OUR DIRECTORS, EMPLOYEES, OR AGENTS BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, EXEMPLARY, INCIDENTAL, SPECIAL, OR PUNITIVE DAMAGES, INCLUDING LOST PROFIT, LOST REVENUE, LOSS OF DATA, OR OTHER DAMAGES ARISING FROM YOUR USE OF THE SITE, EVEN IF WE HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. NOTWITHSTANDING ANYTHING TO THE CONTRARY CONTAINED HEREIN, OUR LIABILITY TO YOU FOR ANY CAUSE WHATSOEVER AND REGARDLESS OF THE FORM OF THE ACTION, WILL AT ALL TIMES BE LIMITED TO THE AMOUNT PAID, IF ANY, BY YOU TO US DURING THE SIX (6) MONTH PERIOD PRIOR TO ANY CAUSE OF ACTION ARISING. CERTAIN STATE LAWS DO NOT ALLOW LIMITATIONS ON IMPLIED WARRANTIES OR THE EXCLUSION OR LIMITATION OF CERTAIN DAMAGES. IF THESE LAWS APPLY TO YOU, SOME OR ALL OF THE ABOVE DISCLAIMERS OR LIMITATIONS MAY NOT APPLY TO YOU, AND YOU MAY HAVE ADDITIONAL RIGHTS.
+
+
+## INDEMNIFICATION
+
+You agree to defend, indemnify, and hold us harmless, including our subsidiaries, affiliates, and all of our respective officers, agents, partners, and employees, from and against any loss, damage, liability, claim, or demand, including reasonable attorneys’ fees and expenses, made by any third party due to or arising out of: (1) use of the Site; (2) breach of these Terms of Use; (3) any breach of your representations and warranties set forth in these Terms of Use; (4) your violation of the rights of a third party, including but not limited to intellectual property rights; or (5) any overt harmful act toward any other user of the Site with whom you connected via the Site. Notwithstanding the foregoing, we reserve the right, at your expense, to assume the exclusive defense and control of any matter for which you are required to indemnify us, and you agree to cooperate, at your expense, with our defense of such claims. We will use reasonable efforts to notify you of any such claim, action, or proceeding which is subject to this indemnification upon becoming aware of it.
+
+
+## USER DATA
+
+We will maintain certain data that you transmit to the Site for the purpose of managing the performance of the Site, as well as data relating to your use of the Site. Although we perform regular routine backups of data, you are solely responsible for all data that you transmit or that relates to any activity you have undertaken using the Site. You agree that we shall have no liability to you for any loss or corruption of any such data, and you hereby waive any right of action against us arising from any such loss or corruption of such data.
+
+
+## ELECTRONIC COMMUNICATIONS, TRANSACTIONS, AND SIGNATURES
+
+Visiting the Site, sending us emails, and completing online forms constitute electronic communications. You consent to receive electronic communications, and you agree that all agreements, notices, disclosures, and other communications we provide to you electronically, via email and on the Site, satisfy any legal requirement that such communication be in writing. YOU HEREBY AGREE TO THE USE OF ELECTRONIC SIGNATURES, CONTRACTS, ORDERS, AND OTHER RECORDS, AND TO ELECTRONIC DELIVERY OF NOTICES, POLICIES, AND RECORDS OF TRANSACTIONS INITIATED OR COMPLETED BY US OR VIA THE SITE. You hereby waive any rights or requirements under any statutes, regulations, rules, ordinances, or other laws in any jurisdiction which require an original signature or delivery or retention of non-electronic records, or to payments or the granting of credits by any means other than electronic means.
+
+
+## CALIFORNIA USERS AND RESIDENTS
+
+If any complaint with us is not satisfactorily resolved, you can contact the Complaint Assistance Unit of the Division of Consumer Services of the California Department of Consumer Affairs in writing at 1625 North Market Blvd., Suite N 112, Sacramento, California 95834 or by telephone at (800) 952-5210 or (916) 445-1254.
+
+
+## MISCELLANEOUS
+
+These Terms of Use and any policies or operating rules posted by us on the Site or in respect to the Site constitute the entire agreement and understanding between you and us. Our failure to exercise or enforce any right or provision of these Terms of Use shall not operate as a waiver of such right or provision. These Terms of Use operate to the fullest extent permissible by law. We may assign any or all of our rights and obligations to others at any time. We shall not be responsible or liable for any loss, damage, delay, or failure to act caused by any cause beyond our reasonable control. If any provision or part of a provision of these Terms of Use is determined to be unlawful, void, or unenforceable, that provision or part of the provision is deemed severable from these Terms of Use and does not affect the validity and enforceability of any remaining provisions. There is no joint venture, partnership, employment or agency relationship created between you and us as a result of these Terms of Use or use of the Site. You agree that these Terms of Use will not be construed against us by virtue of having drafted them. You hereby waive any and all defenses you may have based on the electronic form of these Terms of Use and the lack of signing by the parties hereto to execute these Terms of Use.
+
+## CONTACT US
+
+In order to resolve a complaint regarding the Site or to receive further information regarding use of the Site, please contact us at:
+
+NumFOCUS, Inc. P.O. Box 90596 Austin, TX, USA 78709 info@numfocus.org +1 (512) 222-5449
+
+
+
From b06be866f3c27356e321771282bb5f36e3bc0f4e Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:38:55 +0000
Subject: [PATCH 113/909] New translations citing-numpy.md (Korean)
---
content/ko/citing-numpy.md | 35 +++++++++++++++++++++++++++++++++++
1 file changed, 35 insertions(+)
create mode 100644 content/ko/citing-numpy.md
diff --git a/content/ko/citing-numpy.md b/content/ko/citing-numpy.md
new file mode 100644
index 0000000000..cf20ae59cf
--- /dev/null
+++ b/content/ko/citing-numpy.md
@@ -0,0 +1,35 @@
+---
+title: Citing NumPy
+sidebar: false
+---
+
+If NumPy has been significant in your research, and you would like to acknowledge the project in your academic publication, we suggest citing the following paper:
+
+* Harris, C.R., Millman, K.J., van der Walt, S.J. et al. _Array programming with NumPy_. Nature 585, 357–362 (2020). DOI: [0.1038/s41586-020-2649-2](https://doi.org/10.1038/s41586-020-2649-2). ([Publisher link](https://www.nature.com/articles/s41586-020-2649-2)).
+
+_In BibTeX format:_
+
+ ```
+@Article{ harris2020array,
+ title = {Array programming with {NumPy}},
+ author = {Charles R. Harris and K. Jarrod Millman and St{'{e}}fan J.
+ van der Walt and Ralf Gommers and Pauli Virtanen and David
+ Cournapeau and Eric Wieser and Julian Taylor and Sebastian
+ Berg and Nathaniel J. Smith and Robert Kern and Matti Picus
+ and Stephan Hoyer and Marten H. van Kerkwijk and Matthew
+ Brett and Allan Haldane and Jaime Fern{'{a}}ndez del
+ R{'{\i}}o and Mark Wiebe and Pearu Peterson and Pierre
+ G{'{e}}rard-Marchant and Kevin Sheppard and Tyler Reddy and
+ Warren Weckesser and Hameer Abbasi and Christoph Gohlke and
+ Travis E. Oliphant},
+ year = {2020},
+ month = sep,
+ journal = {Nature},
+ volume = {585},
+ number = {7825},
+ pages = {357--362},
+ doi = {10.1038/s41586-020-2649-2},
+ publisher = {Springer Science and Business Media {LLC}},
+ url = {https://doi.org/10.1038/s41586-020-2649-2}
+}
+```
From 64e4af95ee0cd8029742b2b54550f4a40b001e71 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:38:57 +0000
Subject: [PATCH 114/909] New translations arraycomputing.md (Korean)
---
content/ko/arraycomputing.md | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
create mode 100644 content/ko/arraycomputing.md
diff --git a/content/ko/arraycomputing.md b/content/ko/arraycomputing.md
new file mode 100644
index 0000000000..abd29d11c1
--- /dev/null
+++ b/content/ko/arraycomputing.md
@@ -0,0 +1,21 @@
+---
+title: Array Computing
+sidebar: false
+---
+
+*Array computing is the foundation of statistical, mathematical, scientific computing in various contemporary data science and analytics applications such as data visualization, digital signal processing, image processing, bioinformatics, machine learning, AI, and several others.*
+
+Large scale data manipulation and transformation depends on efficient, high-performance array computing. The language of choice for data analytics, machine learning, and productive numerical computing is **Python.**
+
+**Num**erical **Py**thon or NumPy is its de-facto standard Python programming language library that supports large, multi-dimensional arrays and matrices, and comes with a vast collection of high-level mathematical functions to operate on these arrays.
+
+Since the launch of NumPy in 2006, Pandas appeared on the landscape in 2008, and it was not until a couple of years ago that several array computing libraries showed up in succession, crowding the array computing landscape. Many of these newer libraries mimic NumPy-like features and capabilities, and pack newer algorithms and features geared towards machine learning and artificial intelligence applications.
+
+
+
+**Array computing** is based on **arrays** data structures. *Arrays* are used to organize vast amounts of data such that a related set of values can be easily sorted, searched, mathematically manipulated, and transformed easily and quickly.
+
+Array computing is *unique* as it involves operating on the data array *at once*. What this means is that any array operation applies to an entire set of values in one shot. This vectorized approach provides speed and simplicity by enabling programmers to code and operate on aggregates of data, without having to use loops of individual scalar operations.
From 6b3dc2d257ef7ca670278f6ef9c9c5529fbdaa1b Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:38:58 +0000
Subject: [PATCH 115/909] New translations about.md (Korean)
---
content/ko/about.md | 69 +++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 69 insertions(+)
create mode 100644 content/ko/about.md
diff --git a/content/ko/about.md b/content/ko/about.md
new file mode 100644
index 0000000000..2317add1fe
--- /dev/null
+++ b/content/ko/about.md
@@ -0,0 +1,69 @@
+---
+title: About Us
+sidebar: false
+---
+
+_NumPy 프로젝트와 커뮤니티에 대한 몇가지 정보_
+
+NumPy는 Python에서 Numerical Computing을 할 수 있도록 도와주는 오픈소스 프로젝트입니다. Numerical와 Numarray라는 라이브러리의 초기 작업을 기반으로 2005년에 만들어졌습니다. NumPy는 항상 100% 오픈소스 소프트웨어 일것이며, [수정된 BSD 라이센스](https://github.com/numpy/numpy/blob/master/LICENSE.txt)에 따라서 누구나 무료로 사용하고 배포할 수 있습니디.
+
+NumPy는 광범위한 Scientific Python 커뮤니티의 협의를 통해 GitHub에서 공개적으로 개발되었습니다. 우리의 거버넌스 접근 방식에 대한 더 자세한 내용은 [거버넌스 문서](https://www.numpy.org/devdocs/dev/governance/index.html)를 참조해 주세요.
+
+
+## 운영 위원회
+
+NumPy 운영 위원회의 역할은 더 광범위한 NumPy 커뮤니티와 협력하고 서비스를 통해서 기술적으로나 커뮤니티로서 프로젝트의 장기적인 안녕을 보장하는 것입니다. NumPy 운영 위원회는 현재 다음과 같은 회원들로 구성되어 있습니다. (알파벳 순서)
+
+- Sebastian Berg
+- Jaime Fernández del Río
+- Ralf Gommers
+- Allan Haldane
+- Charles Harris
+- Stephan Hoyer
+- Matti Picus
+- Nathaniel Smith
+- Julian Taylor
+- Pauli Virtanen
+- Stéfan van der Walt
+- Eric Wieser
+
+명예 회원
+
+- Travis Oliphant (project founder, 2005-2012)
+- Alex Griffing (2015-2017)
+- Marten van Kerkwijk (2017-2019)
+
+## 팀
+
+NumPy 프로젝트는 성장하고 있습니다. 그리고 우리는 다음과 같은 팀들이 있습니다.
+
+- 코드
+- 문서
+- 웹사이트
+- 심사
+- 자원 및 보조금
+
+개발 팀원들은 [팀](/gallery/team.html) 페이지를 참조하세요.
+
+## 스폰서
+
+NumPy는 다음과 같은 곳들에서 직접적으로 자금을 받습니다.
+{{< sponsors >}}
+
+
+## 기관 파트너
+
+기관 파트너는 그들의 업무의 일환으로 NumPy에 기여하는 직원을 고용하여 프로젝트를 지원하는 조직입니다. 현재 기관 파트너는 다음과 같습니다.
+{{< partners >}}
+
+
+## 후원
+
+만약 NumPy가 당신의 업무, 연구 혹은 회사에서 유용하다고 판단된다면 당신의 자원에 맞는 프로젝트에 기여하는 것을 고려해보세요. 그것이 얼마든 도움이 됩니다! 모든 후원은 NumPy의 소프트웨어 개발, 문서 작성과 커뮤니티 운영의 자금으로 엄격하게 사용될 것입니다.
+
+NumPy는 미국의 501(c)(3) 비영리 단체인 NumFOCUS의 후원 프로젝트입니다. NumFOCUS는 NumPy에 재정적, 법적, 행정적 지원을 제공하고 프로젝트의 건강과 지속 가능성을 보장할 수 있도록 도와줍니다. 더 자세한 정보를 알고싶다면 [numfocus.org](https://numfocus.org)를 방문하세요.
+
+NumPy에 대한 후원은 [NumFOCUS](https://numfocus.org)가 관리합니다. 미국에 거주하는 후원자의 경우에는, 당신의 후원은 법이 제공하는 한도 내에서 세금 공제를 받을 수 있습니다. 기부와 마찬가지로 특정 세금 상황에 대해서는 세금 전문가와 상담해야합니다.
+
+NumPy 운영 위원회는 후원받은 후원금을 가장 잘 활용하는 방안을 결정합니다. 기술 및 인프라의 우선 순위는 NumPy [NumPy Roadmap](https://www.numpy.org/neps/index.html#roadmap)에 문서화되어 있습니다.
+{{< numfocus >}}
From 8b98b4000d1dec405adaed361fa95b543a58b045 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:39:00 +0000
Subject: [PATCH 116/909] New translations 404.md (Korean)
---
content/ko/404.md | 8 ++++++++
1 file changed, 8 insertions(+)
create mode 100644 content/ko/404.md
diff --git a/content/ko/404.md b/content/ko/404.md
new file mode 100644
index 0000000000..41504d0c8a
--- /dev/null
+++ b/content/ko/404.md
@@ -0,0 +1,8 @@
+---
+title: 404
+sidebar: false
+---
+
+앗! 잘못된 접근입니다.
+
+만약 이곳에 어떤 페이지가 있어야 한다면 [Issue 열기](https://github.com/numpy/numpy.org/issues)에서 문제를 제기할 수 있습니다.
From cba9667db922ed42653c0c6bf69e9a5c94fc8153 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:39:01 +0000
Subject: [PATCH 117/909] New translations diversity_sep2020.md (Japanese)
---
content/ja/diversity_sep2020.md | 48 +++++++++++++++++++++++++++++++++
1 file changed, 48 insertions(+)
create mode 100644 content/ja/diversity_sep2020.md
diff --git a/content/ja/diversity_sep2020.md b/content/ja/diversity_sep2020.md
new file mode 100644
index 0000000000..e85b3dfb2e
--- /dev/null
+++ b/content/ja/diversity_sep2020.md
@@ -0,0 +1,48 @@
+---
+title: Numpyの多様性とチームの参加に関する声明
+sidebar: false
+---
+
+
+_Natureに掲載されたNumPyの論文が発表された後のソーシャルメディアで議論が行われ、Numpyの多様性とチームへの参加に関する懸念が提起されました。 そこで以下の声明を発表したいと思います_
+
+
+私たちがチームに加わりたい人にオープンで平等であるとき、私たちはチームとコミュニティに最善を尽くしていると強く信じることが出来ます。 プロジェクトの発足当初からの私達は国際的なチームでありたいと思っていました。また、私たちは多様なバックグラウンドや専門知識を持つ個人同士のコラボレーションの価値を認識しています。 誰もが歓迎され、助け合い、評価される文化は、Numpy プロジェクトの中核です。
+
+## 過去
+
+オープンソースへ貢献することは、歴史的に疎外されてきた人達、特に女性や、多くの社会的制約や期待のために参加するためにより多くの障害に直面してきた人達に取って、娯楽であり続けてきました。 オープンソースのプロジェクトでは、大きな多様性の問題があり、レポートとしてもまとめられています。(例えば、 [2017 GitHub Open Source Survey](https://opensourcesurvey.org/2017/) と [こちらのブログ投稿](https://medium.com/tech-diversity-files/if-you-think-women-in-tech-is-just-a-pipeline-problem-you-haven-t-been-paying-attention-cb7a2073b996)).
+
+プロジェクトがスタートしてから2018年まで、NumPyは一握りのボランティアによって維持されていました。 ほとんどの場合、コードレビューやコミュニティからの貢献をマージする、アクティブなコア開発者の数は、4~8の範囲でした。 Numpyのプロジェクトには当時はロードマップやリソースを配分する仕組みがなく、必要と思われることが個々の努力によって進められていました。 Natureの論文の著者の人達は、15年間(2005年から2019年) の期間に渡って、このプロジェクトに最も重要で持続的な貢献をした人達です。 この著者リストの多様性の欠如は、PythonとSciPyエコシステムの形成する年数を反映しているといえます。
+
+2018年はNumPyプロジェクトの歴史において重要な節目となりました。 ゴードン・ベティムーア財団とアルフレッド・P・ソロラン財団により資金援助を受け、Pythonエコシステムに貢献する長年の経験を持つ二人のエンジニア。フルタイム雇用することができました。 これらの取り組みにより、NumPyは技術的により健康的な状態になりました。
+
+加えて、この資金調達により、Numpy メンテナーはプロジェクトガバナンス、コミュニティ開発、あまりプロジェクトに参加していないグループへのアウトリーチなどにも取り組めるようになりました。 [CZI EOSSプログラムのために2019年半ばに書かれた多様性に関する声明](https://figshare.com/articles/online_resource/Diversity_and_Inclusion_Statement_NumPy_for_Chan_Zuckerberg_Initiative_EOSS_2019_round_1/12980852) では、いくつかの課題と、NumPyチームに多様な 才能ある人達を参加してもらうための取り組みについて詳しく説明しています。
+
+## 現在
+
+雇用機会を提供することは、OSSにおいて、 多様な人材を引き寄せ、維持するために効果的な方法です。 よって、私たちはMelissa Weber Mendonça とMars Leeを採用するために、2019年12月に利用できるようになった2回目の助成金の3分の2を利用することにしました。
+
+Inessa PawsonとRalf Gommersによるコミュニティの発展を目的としたいくつかの取り組みの結果として、NumPyプロジェクトには女性や2020年のOSSにはあまり参加してこなかった人から、貴重な投稿が多数寄せられています。
+
+- Melissa Weber Mendonça はコミット権限を取得し、numpy.f2py をメンテナンスし、ドキュメンテーションチームを率いています。
+- Shaloo Shaliniはnumpy.org のすべてのケーススタディを作成しました。
+- Mars Leeはウェブデザインに貢献し、アクセシビリティの向上に貢献しました。
+- Isabela Presedo-Floydは新しいNumpyのロゴをデザインしました。
+- Stephanie Mendoza, Xiayoi Deng, Deji Suolang, Mame Fatou Thiamは、Numpy ユーザー調査を設計し実施しました。
+- Yuki Dunn, Dayane Machado, Mahfuza Humayra Mohona, Sumera Priyadarsini, Shaloo Shalini, and Kriti Singh (前回のアウトリーチインターン) は英語を母国語としないNumPyユーザーや開発者にアンケートを母国語に翻訳することで、調査チームを支援しました。
+- Sayed Adel, Raghuveer Devulapalli, Chunlin Fangは、NumpyのコアのためにSIMD最適化に取り組んでいます。
+
+私たちにはまだ多くのやるべきことがあるため、より一層の参加者を探しています。 そして私達は次のNumPy論文の著者は、確実に、より多様的になっていることでしょう。
+
+## 未来
+
+私たちは、チームとコミュニティにおける参加のしやすさと多様性を育成することに力を注ぎ、より公正で公平な未来を築くために我々の役割を果たそうとしています。
+
+私たちとの対話は開かれており、技術と 科学分野における女性やマイノリティを代表し支援する組織と連携したいと思っています。 私たちは対話し、学び、サポートする準備ができています。
+
+是非以下の連絡手段を使ってご連絡下さい:[メーリングリスト](https://scipy.org/scipylib/mailing-lists.html#mailing-lists), [GitHub](https://github.com/numpy/numpy/issues), [Slack](https://numpy.org/contribute/)。非公開な連絡ではこちらのEmailを使ってください: numpy-team@googlegroups.com, または [2週間に1回のミーティング](https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg)に参加してください。
+
+
+_以下の人達がNumpyチームの代表してこれらの宣言をします: Sayed Adel, Sebastian Berg, Raghuveer Devulapalli, Chunlin Fang, Ralf Gommers, Allan Haldane, Stephan Hoyer, Mars Lee, Melissa Weber Mendonça, Jarrod Millman, Inessa Pawson, Matti Picus, Nathaniel Smith, Julian Taylor, Pauli Virtanen, Stéfan van der Walt, Eric Wieser_
+
From 2587fcdb236c056db346ff8f3b12e6c5c1fa7844 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:39:03 +0000
Subject: [PATCH 118/909] New translations gw-discov.md (Japanese)
---
content/ja/case-studies/gw-discov.md | 69 ++++++++++++++++++++++++++++
1 file changed, 69 insertions(+)
create mode 100644 content/ja/case-studies/gw-discov.md
diff --git a/content/ja/case-studies/gw-discov.md b/content/ja/case-studies/gw-discov.md
new file mode 100644
index 0000000000..3d25090e13
--- /dev/null
+++ b/content/ja/case-studies/gw-discov.md
@@ -0,0 +1,69 @@
+---
+title: "Case Study: Discovery of Gravitational Waves"
+sidebar: false
+---
+
+{{< figure src="/images/content_images/cs/gw_sxs_image.png" class="fig-center" caption="**Gravitational Waves**" alt="binary coalesce black hole generating gravitational waves" attr="*(Image Credits: The Simulating eXtreme Spacetimes (SXS) Project at LIGO)*" attrlink="https://youtu.be/Zt8Z_uzG71o" >}}
+
+
+
The scientific Python ecosystem is critical infrastructure for the research done at LIGO.
+
+
+
+## About [Gravitational Waves](https://www.nationalgeographic.com/news/2017/10/what-are-gravitational-waves-ligo-astronomy-science/) and [LIGO](https://www.ligo.caltech.edu)
+
+Gravitational waves are ripples in the fabric of space and time, generated by cataclysmic events in the universe such as collision and merging of two black holes or coalescing binary stars or supernovae. Observing GW can not only help in studying gravity but also in understanding some of the obscure phenomena in the distant universe and its impact.
+
+The [Laser Interferometer Gravitational-Wave Observatory (LIGO)](https://www.ligo.caltech.edu) was designed to open the field of gravitational-wave astrophysics through the direct detection of gravitational waves predicted by Einstein’s General Theory of Relativity. It comprises two widely-separated interferometers within the United States — one in Hanford, Washington and the other in Livingston, Louisiana — operated in unison to detect gravitational waves. Each of them has multi-kilometer-scale gravitational wave detectors that use laser interferometry. The LIGO Scientific Collaboration (LSC), is a group of more than 1000 scientists from universities around the United States and in 14 other countries supported by more than 90 universities and research institutes; approximately 250 students actively contributing to the collaboration. The new LIGO discovery is the first observation of gravitational waves themselves, made by measuring the tiny disturbances the waves make to space and time as they pass through the earth. It has opened up new astrophysical frontiers that explore the warped side of the universe—objects and phenomena that are made from warped spacetime.
+
+
+### Key Objectives
+
+* Though its [mission](https://www.ligo.caltech.edu/page/what-is-ligo) is to detect gravitational waves from some of the most violent and energetic processes in the Universe, the data LIGO collects may have far-reaching effects on many areas of physics including gravitation, relativity, astrophysics, cosmology, particle physics, and nuclear physics.
+* Crunch observed data via numerical relativity computations that involves complex maths in order to discern signal from noise, filter out relevant signal and statistically estimate significance of observed data
+* Data visualization so that the binary / numerical results can be comprehended.
+
+
+
+### The Challenges
+
+* **Computation**
+
+ Gravitational Waves are hard to detect as they produce a very small effect and have tiny interaction with matter. Processing and analyzing all of LIGO's data requires a vast computing infrastructure.After taking care of noise, which is billions of times of the signal, there is still very complex relativity equations and huge amounts of data which present a computational challenge: [O(10^7) CPU hrs needed for binary merger analyses](https://youtu.be/7mcHknWWzNI) spread on 6 dedicated LIGO clusters
+
+* **Data Deluge**
+
+ As observational devices become more sensitive and reliable, the challenges posed by data deluge and finding a needle in a haystack rise multi-fold. LIGO generates terabytes of data every day! Making sense of this data requires an enormous effort for each and every detection. For example, the signals being collected by LIGO must be matched by supercomputers against hundreds of thousands of templates of possible gravitational-wave signatures.
+
+* **Visualization**
+
+ Once the obstacles related to understanding Einstein’s equations well enough to solve them using supercomputers are taken care of, the next big challenge was making data comprehensible to the human brain. Simulation modeling as well as signal detection requires effective visualization techniques. Visualization also plays a role in lending more credibility to numerical relativity in the eyes of pure science aficionados, who did not give enough importance to numerical relativity until imaging and simulations made it easier to comprehend results for a larger audience. Speed of complex computations and rendering, re-rendering images and simulations using latest experimental inputs and insights can be a time consuming activity that challenges researchers in this domain.
+
+{{< figure src="/images/content_images/cs/gw_strain_amplitude.png" class="fig-center" alt="gravitational waves strain amplitude" caption="**Estimated gravitational-wave strain amplitude from GW150914**" attr="(**Graph Credits:** Observation of Gravitational Waves from a Binary Black Hole Merger, ResearchGate Publication)" attrlink="https://www.researchgate.net/publication/293886905_Observation_of_Gravitational_Waves_from_a_Binary_Black_Hole_Merger" >}}
+
+## NumPy’s Role in the Detection of Gravitational Waves
+
+Gravitational waves emitted from the merger cannot be computed using any technique except brute force numerical relativity using supercomputers. The amount of data LIGO collects is as incomprehensibly large as gravitational wave signals are small.
+
+NumPy, the standard numerical analysis package for Python, was utilized by the software used for various tasks performed during the GW detection project at LIGO. NumPy helped in solving complex maths and data manipulation at high speed. Here are some examples:
+
+* [Signal Processing](https://www.uv.es/virgogroup/Denoising_ROF.html): Glitch detection, [Noise identification and Data Characterization](https://ep2016.europython.eu/media/conference/slides/pyhton-in-gravitational-waves-research-communities.pdf) (NumPy, scikit-learn, scipy, matplotlib, pandas, pyCharm)
+* Data retrieval: Deciding which data can be analyzed, figuring out whether it contains a signal - needle in a haystack
+* Statistical analysis: estimate the statistical significance of observational data, estimating the signal parameters (e.g. masses of stars, spin velocity, and distance) by comparison with a model.
+* Visualization of data
+ - Time series
+ - Spectrograms
+* Compute Correlations
+* Key [Software](https://github.com/lscsoft) developed in GW data analysis such as [GwPy](https://gwpy.github.io/docs/stable/overview.html) and [PyCBC](https://pycbc.org) uses NumPy and AstroPy under the hood for providing object based interfaces to utilities, tools, and methods for studying data from gravitational-wave detectors.
+
+{{< figure src="/images/content_images/cs/gwpy-numpy-dep-graph.png" class="fig-center" alt="gwpy-numpy depgraph" caption="**Dependency graph showing how GwPy package depends on NumPy**" >}}
+
+----
+
+{{< figure src="/images/content_images/cs/PyCBC-numpy-dep-graph.png" class="fig-center" alt="PyCBC-numpy depgraph" caption="**Dependency graph showing how PyCBC package depends on NumPy**" >}}
+
+## Summary
+
+GW detection has enabled researchers to discover entirely unexpected phenomena while providing new insight into many of the most profound astrophysical phenomena known. Number crunching and data visualization is a crucial step that helps scientists gain insights into data gathered from the scientific observations and understand the results. The computations are complex and cannot be comprehended by humans unless it is visualized using computer simulations that are fed with the real observed data and analysis. NumPy along with other Python packages such as matplotlib, pandas, and scikit-learn is [enabling researchers](https://www.gw-openscience.org/events/GW150914/) to answer complex questions and discover new horizons in our understanding of the universe.
+
+{{< figure src="/images/content_images/cs/numpy_gw_benefits.png" class="fig-center" alt="numpy benefits" caption="**Key NumPy Capabilities utilized**" >}}
From 494109b2908653f5957010609738092979bac889 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:39:05 +0000
Subject: [PATCH 119/909] New translations deeplabcut-dnn.md (Japanese)
---
content/ja/case-studies/deeplabcut-dnn.md | 90 +++++++++++++++++++++++
1 file changed, 90 insertions(+)
create mode 100644 content/ja/case-studies/deeplabcut-dnn.md
diff --git a/content/ja/case-studies/deeplabcut-dnn.md b/content/ja/case-studies/deeplabcut-dnn.md
new file mode 100644
index 0000000000..b40ed2af50
--- /dev/null
+++ b/content/ja/case-studies/deeplabcut-dnn.md
@@ -0,0 +1,90 @@
+---
+title: "Case Study: DeepLabCut 3D Pose Estimation"
+sidebar: false
+---
+
+{{< figure src="/images/content_images/cs/mice-hand.gif" class="fig-center" caption="**Analyzing mice hand-movement using DeepLapCut**" alt="micehandanim" attr="*(Source: www.deeplabcut.org )*" attrlink="http://www.mousemotorlab.org/deeplabcut">}}
+
+
+
Open Source Software is accelerating Biomedicine. DeepLabCut enables automated video analysis of animal behavior using Deep Learning.
+
+
+
+## About DeepLabCut
+
+[DeepLabCut](https://github.com/DeepLabCut/DeepLabCut) is an open source toolbox that empowers researchers at hundreds of institutions worldwide to track behaviour of laboratory animals, with very little training data, at human-level accuracy. With DeepLabCut technology, scientists can delve deeper into the scientific understanding of motor control and behavior across animal species and timescales.
+
+Several areas of research, including neuroscience, medicine, and biomechanics, use data from tracking animal movement. DeepLabCut helps in understanding what humans and other animals are doing by parsing actions that have been recorded on film. Using automation for laborious tasks of tagging and monitoring, along with deep neural network based data analysis, DeepLabCut makes scientific studies involving observing animals, such as primates, mice, fish, flies etc., much faster and more accurate.
+
+{{< figure src="/images/content_images/cs/race-horse.gif" class="fig-center" caption="**Colored dots track the positions of a racehorse’s body part**" alt="horserideranim" attr="*(Source: Mackenzie Mathis)*">}}
+
+DeepLabCut's non-invasive behavioral tracking of animals by extracting the poses of animals is crucial for scientific pursuits in domains such as biomechanics, genetics, ethology & neuroscience. Measuring animal poses non-invasively from video - without markers - in dynamically changing backgrounds is computationally challenging, both technically as well as in terms of resource needs and training data required.
+
+DeepLabCut allows researchers to estimate the pose of the subject, efficiently enabling them to quantify the behavior through a Python based software toolkit. With DeepLabCut, researchers can identify distinct frames from videos, digitally label specific body parts in a few dozen frames with a tailored GUI, and then the deep learning based pose estimation architectures in DeepLabCut learn how to pick out those same features in the rest of the video and in other similar videos of animals. It works across species of animals, from common laboratory animals such as flies and mice to more unusual animals like [cheetahs][cheetah-movement].
+
+DeepLabCut uses a principle called [transfer learning](https://arxiv.org/pdf/1909.11229), which greatly reduces the amount of training data required and speeds up the convergence of the training period. Depending on the needs, users can pick different network architectures that provide faster inference (e.g. MobileNetV2), which can also be combined with real-time experimental feedback. DeepLabCut originally used the feature detectors from a top-performing human pose estimation architecture, called [DeeperCut](https://arxiv.org/abs/1605.03170), which inspired the name. The package now has been significantly changed to include additional architectures, augmentation methods, and a full front-end user experience. Furthermore, to support large-scale biological experiments DeepLabCut provides active learning capabilities so that users can increase the training set over time to cover edge cases and make their pose estimation algorithm robust within the specific context.
+
+Recently, the [DeepLabCut model zoo](http://www.mousemotorlab.org/dlc-modelzoo) was introduced, which provides pre-trained models for various species and experimental conditions from facial analysis in primates to dog posture. This can be run for instance in the cloud without any labeling of new data, or neural network training, and no programming experience is necessary.
+
+### Key Goals and Results
+
+* **Automation of animal pose analysis for scientific studies:**
+
+ The primary objective of DeepLabCut technology is to measure and track posture of animals in a diverse settings. This data can be used, for example, in neuroscience studies to understand how the brain controls movement, or to elucidate how animals socially interact. Researchers have observed a [tenfold performance boost](https://www.biorxiv.org/content/10.1101/457242v1) with DeepLabCut. Poses can be inferred offline at up to 1200 frames per second (FPS).
+
+* **Creation of an easy-to-use Python toolkit for pose estimation:**
+
+ DeepLabCut wanted to share their animal pose-estimation technology in the form of an easy to use tool that can be adopted by researchers easily. So they have created a complete, easy-to-use Python toolbox with project management features as well. These enable not only automation of pose-estimation but also managing the project end-to-end by helping the DeepLabCut Toolkit user right from the dataset collection stage to creating shareable and reusable analysis pipelines.
+
+ Their [toolkit][DLCToolkit] is now available as open source.
+
+ A typical DeepLabCut Workflow includes:
+
+ - creation and refining of training sets via active learning
+ - creation of tailored neural networks for specific animals and scenarios
+ - code for large-scale inference on videos
+ - draw inferences using integrated visualization tools
+
+{{< figure src="/images/content_images/cs/deeplabcut-toolkit-steps.png" class="csfigcaption" caption="**Pose estimation steps with DeepLabCut**" alt="dlcsteps" align="middle" attr="(Source: DeepLabCut)" attrlink="https://twitter.com/DeepLabCut/status/1198046918284210176/photo/1" >}}
+
+### The Challenges
+
+* **Speed**
+
+ Fast processing of animal behavior videos in order to measure their behavior and at the same time make scientific experiments more efficient, accurate. Extracting detailed animal poses for laboratory experiments, without markers, in dynamically changing backgrounds, can be challenging, both technically as well as in terms of resource needs and training data required. Coming up with a tool that is easy to use without the need for skills such as computer vision expertise that enables scientists to do research in more real-world contexts, is a non-trivial problem to solve.
+
+* **Combinatorics**
+
+ Combinatorics involves assembly and integration of movement of multiple limbs into individual animal behavior. Assembling keypoints and their connections into individual animal movements and linking them across time is a complex process that requires heavy-duty numerical analysis, especially in case of multi-animal movement tracking in experiment videos.
+
+* **Data Processing**
+
+ Last but not the least, array manipulation - processing large stacks of arrays corresponding to various images, target tensors and keypoints is fairly challenging.
+
+{{< figure src="/images/content_images/cs/pose-estimation.png" class="csfigcaption" caption="**Pose estimation variety and complexity**" alt="challengesfig" align="middle" attr="(Source: Mackenzie Mathis)" attrlink="https://www.biorxiv.org/content/10.1101/476531v1.full.pdf" >}}
+
+## NumPy's Role in meeting Pose Estimation Challenges
+
+NumPy addresses DeepLabCut technology's core need of numerical computations at high speed for behavioural analytics. Besides NumPy, DeepLabCut employs various Python software that utilize NumPy at their core, such as [SciPy](https://www.scipy.org), [Pandas](https://pandas.pydata.org), [matplotlib](https://matplotlib.org), [Tensorpack](https://github.com/tensorpack/tensorpack), [imgaug](https://github.com/aleju/imgaug), [scikit-learn](https://scikit-learn.org/stable/), [scikit-image](https://scikit-image.org) and [Tensorflow](https://www.tensorflow.org).
+
+The following features of NumPy played a key role in addressing the image processing, combinatorics requirements and need for fast computation in DeepLabCut pose estimation algorithms:
+
+* Vectorization
+* Masked Array Operations
+* Linear Algebra
+* Random Sampling
+* Reshaping of large arrays
+
+DeepLabCut utilizes NumPy’s array capabilities throughout the workflow offered by the toolkit. In particular, NumPy is used for sampling distinct frames for human annotation labeling, and for writing, editing and processing annotation data. Within TensorFlow the neural network is trained by DeepLabCut technology over thousands of iterations to predict the ground truth annotations from frames. For this purpose, target densities (scoremaps) are created to cast pose estimation as a image-to-image translation problem. To make the neural networks robust, data augmentation is employed, which requires the calculation of target scoremaps subject to various geometric and image processing steps. To make training fast, NumPy’s vectorization capabilities are leveraged. For inference, the most likely predictions from target scoremaps need to extracted and one needs to efficiently “link predictions to assemble individual animals”.
+
+{{< figure src="/images/content_images/cs/deeplabcut-workflow.png" class="fig-center" caption="**DeepLabCut Workflow**" alt="workflow" attr="*(Source: Mackenzie Mathis)*" attrlink="https://www.researchgate.net/figure/DeepLabCut-work-flow-The-diagram-delineates-the-work-flow-as-well-as-the-directory-and_fig1_329185962">}}
+
+## Summary
+
+Observing and efficiently describing behavior is a core tenant of modern ethology, neuroscience, medicine, and technology. [DeepLabCut](http://orga.cvss.cc/wp-content/uploads/2019/05/NathMathis2019.pdf) allows researchers to estimate the pose of the subject, efficiently enabling them to quantify the behavior. With only a small set of training images, the DeepLabCut Python toolbox allows training a neural network to within human level labeling accuracy, thus expanding its application to not only behavior analysis in the laboratory, but to potentially also in sports, gait analysis, medicine and rehabilitation studies. Complex combinatorics, data processing challenges faced by DeepLabCut algorithms are addressed through the use of NumPy's array manipulation capabilities.
+
+{{< figure src="/images/content_images/cs/numpy_dlc_benefits.png" class="fig-center" alt="numpy benefits" caption="**Key NumPy Capabilities utilized**" >}}
+
+[cheetah-movement]: https://www.technologynetworks.com/neuroscience/articles/interview-a-deeper-cut-into-behavior-with-mackenzie-mathis-327618
+
+[DLCToolkit]: https://github.com/DeepLabCut/DeepLabCut
From 38f335951e2a09af5e3ec86755a11311a4c0fec9 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:39:07 +0000
Subject: [PATCH 120/909] New translations cricket-analytics.md (Japanese)
---
content/ja/case-studies/cricket-analytics.md | 64 ++++++++++++++++++++
1 file changed, 64 insertions(+)
create mode 100644 content/ja/case-studies/cricket-analytics.md
diff --git a/content/ja/case-studies/cricket-analytics.md b/content/ja/case-studies/cricket-analytics.md
new file mode 100644
index 0000000000..987b38fb68
--- /dev/null
+++ b/content/ja/case-studies/cricket-analytics.md
@@ -0,0 +1,64 @@
+---
+title: "Case Study: Cricket Analytics, the game changer!"
+sidebar: false
+---
+
+{{< figure src="/images/content_images/cs/ipl-stadium.png" caption="**IPLT20, the biggest Cricket Festival in India**" alt="Indian Premier League Cricket cup and stadium" attr="*(Image credits: IPLT20 (cup and logo) & Akash Yadav (stadium))*" attrlink="https://unsplash.com/@aksh1802" >}}
+
+
+
You don't play for the crowd, you play for the country.
+
+
+
+## About Cricket
+
+It would be an understatement to state that Indians love cricket. The game is played in just about every nook and cranny of India, rural or urban, popular with the young and the old alike, connecting billions in India unlike any other sport. Cricket enjoys lots of media attention. There is a significant amount of [money](https://www.statista.com/topics/4543/indian-premier-league-ipl/) and fame at stake. Over the last several years, technology has literally been a game changer. Audiences are spoilt for choice with streaming media, tournaments, affordable access to mobile based live cricket watching, and more.
+
+The Indian Premier League (IPL) is a professional Twenty20 cricket league, founded in 2008. It is one of the most attended cricketing events in the world, valued at [$6.7 billion](https://en.wikipedia.org/wiki/Indian_Premier_League) in 2019.
+
+Cricket is a game of numbers - the runs scored by a batsman, the wickets taken by a bowler, the matches won by a cricket team, the number of times a batsman responds in a certain way to a kind of bowling attack, etc. The capability to dig into cricketing numbers for both improving performance and studying the business opportunities, overall market, and economics of cricket via powerful analytics tools, powered by numerical computing software such as NumPy, is a big deal. Cricket analytics provides interesting insights into the game and predictive intelligence regarding game outcomes.
+
+Today, there are rich and almost infinite troves of cricket game records and statistics available, e.g., [ESPN cricinfo](https://stats.espncricinfo.com/ci/engine/stats/index.html) and [cricsheet](https://cricsheet.org). These and several such cricket databases have been used for [cricket analysis](https://www.researchgate.net/publication/336886516_Data_visualization_and_toss_related_analysis_of_IPL_teams_and_batsmen_performances) using the latest machine learning and predictive modelling algorithms. Media and entertainment platforms along with professional sports bodies associated with the game use technology and analytics for determining key metrics for improving match winning chances:
+
+* batting performance moving average,
+* score forecasting,
+* gaining insights into fitness and performance of a player against different opposition,
+* player contribution to wins and losses for making strategic decisions on team composition
+
+{{< figure src="/images/content_images/cs/cricket-pitch.png" class="csfigcaption" caption="**Cricket Pitch, the focal point in the field**" alt="A cricket pitch with bowler and batsmen" align="middle" attr="*(Image credit: Debarghya Das)*" attrlink="http://debarghyadas.com/files/IPLpaper.pdf" >}}
+
+### Key Data Analytics Objectives
+
+* Sports data analytics are used not only in cricket but many [other sports](https://adtmag.com/blogs/dev-watch/2017/07/sports-analytics.aspx) for improving the overall team performance and maximizing winning chances.
+* Real-time data analytics can help in gaining insights even during the game for changing tactics by the team and by associated businesses for economic benefits and growth.
+* Besides historical analysis, predictive models are harnessed to determine the possible match outcomes that require significant number crunching and data science know-how, visualization tools and capability to include newer observations in the analysis.
+
+{{< figure src="/images/content_images/cs/player-pose-estimator.png" class="fig-center" alt="pose estimator" caption="**Cricket Pose Estimator**" attr="*(Image credit: connect.vin)*" attrlink="https://connect.vin/2019/05/ai-for-cricket-batsman-pose-analysis/" >}}
+
+### The Challenges
+
+* **Data Cleaning and preprocessing**
+
+ IPL has expanded cricket beyond the classic test match format to a much larger scale. The number of matches played every season across various formats has increased and so has the data, the algorithms, newer sports data analysis technologies and simulation models. Cricket data analysis requires field mapping, player tracking, ball tracking, player shot analysis, and several other aspects involved in how the ball is delivered, its angle, spin, velocity, and trajectory. All these factors together have increased the complexity of data cleaning and preprocessing.
+
+* **Dynamic Modeling**
+
+ In cricket, just like any other sport, there can be a large number of variables related to tracking various numbers of players on the field, their attributes, the ball, and several possibilities of potential actions. The complexity of data analytics and modeling is directly proportional to the kind of predictive questions that are put forth during analysis and are highly dependent on data representation and the model. Things get even more challenging in terms of computation, data comparisons when dynamic cricket play predictions are sought such as what would have happened if the batsman had hit the ball at a different angle or velocity.
+
+* **Predictive Analytics Complexity**
+
+ Much of the decision making in cricket is based on questions such as "how often does a batsman play a certain kind of shot if the ball delivery is of a particular type", or "how does a bowler change his line and length if the batsman responds to his delivery in a certain way". This kind of predictive analytics query requires highly granular dataset availability and the capability to synthesize data and create generative models that are highly accurate.
+
+## NumPy’s Role in Cricket Analytics
+
+Sports Analytics is a thriving field. Many researchers and companies [use NumPy](https://adtmag.com/blogs/dev-watch/2017/07/sports-analytics.aspx) and other PyData packages like Scikit-learn, SciPy, Matplotlib, and Jupyter, besides using the latest machine learning and AI techniques. NumPy has been used for various kinds of cricket related sporting analytics such as:
+
+* **Statistical Analysis:** NumPy's numerical capabilities help estimate the statistical significance of observational data or match events in the context of various player and game tactics, estimating the game outcome by comparison with a generative or static model. [Causal analysis](https://amplitude.com/blog/2017/01/19/causation-correlation) and [big data approaches](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4996805/) are used for tactical analysis.
+
+* **Data Visualization:** Data graphing and [visualization](https://towardsdatascience.com/advanced-sports-visualization-with-pandas-matplotlib-and-seaborn-9c16df80a81b) provides useful insights into relationship between various datasets.
+
+## Summary
+
+Sports Analytics is a game changer when it comes to how professional games are played, especially how strategic decision making happens, which until recently was primarily done based on “gut feeling" or adherence to past traditions. NumPy forms a solid foundation for a large set of Python packages which provide higher level functions related to data analytics, machine learning, and AI algorithms. These packages are widely deployed to gain real-time insights that help in decision making for game-changing outcomes, both on field as well as to draw inferences and drive business around the game of cricket. Finding out the hidden parameters, patterns, and attributes that lead to the outcome of a cricket match helps the stakeholders to take notice of game insights that are otherwise hidden in numbers and statistics.
+
+{{< figure src="/images/content_images/cs/numpy_ca_benefits.png" class="fig-center" alt="Diagram showing benefits of using NumPy for cricket analytics" caption="**Key NumPy Capabilities utilized**" >}}
From bd1c92a40d70ea2be01817f349fef722407201a9 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:39:09 +0000
Subject: [PATCH 121/909] New translations blackhole-image.md (Japanese)
---
content/ja/case-studies/blackhole-image.md | 70 ++++++++++++++++++++++
1 file changed, 70 insertions(+)
create mode 100644 content/ja/case-studies/blackhole-image.md
diff --git a/content/ja/case-studies/blackhole-image.md b/content/ja/case-studies/blackhole-image.md
new file mode 100644
index 0000000000..299d80cf2d
--- /dev/null
+++ b/content/ja/case-studies/blackhole-image.md
@@ -0,0 +1,70 @@
+---
+title: "ケーススタディ:世界初のブラックホールの画像"
+sidebar: false
+---
+
+{{< figure src="/images/content_images/cs/blackhole.jpg" caption="**Black Hole M87**" alt="black hole image" attr="*(Image Credits: Event Horizon Telescope Collaboration)*" attrk="https://www.jpl.nasa.gov/images/universe/90410/blackhole20190410.jpg" >}}
+
+
+
+## 地球の大きさの望遠鏡。
+
+[ Event Horizon telescope(EHT)](https:/eventhorizontelescope.org)は、地球サイズの解析望遠鏡を形成する8台の地上型電波望遠鏡から成るシステムで、これまでに前例のない感度と解像度で宇宙を研究することができます。 超長基線干渉法(VLBI) と呼ばれる手法を用いた巨大な仮想望遠鏡の角度分解能は、[20マイクロ秒][resolution]で、ニューヨークにある新聞をパリの歩道のカフェから読むのに十分な解像度です。
+
+### 主な目標と結果
+
+* **宇宙の新しい見方:** EHTの画期的な考え方の基礎が築かれたのは、100年前に [Sir Arthur Eddington][eddington] がアインシュタインの一般相対性理論に沿った最初の観測を実施したことが始まりでした。
+
+* **ブラックホール:** EHTは、おとめ座銀河団のメシエ87銀河 (M87) の中心にある、地球から約5500万光年の距離にある超巨大ブラックホールを観測しました。 その質量は、太陽の65億倍です。 この取り組みは[ 100年以上 ](https://www.jpl.nasa.gov/news/news.php?feature=7385)に渡って研究されてきたが、これまでに視覚的にブラックホールを観測できたことはありませんでした。
+
+* **観測と理論の比較:** 科学者達は、アインシュタインの一般相対性理論から、重力による光の曲げや光の捕獲による影のような領域を観測できるのではないかと期待していました。 科学者たちは、ブラックホールの巨大な質量を測定するためにその情報を利用することができます。
+
+### 課題
+
+* **大規模な計算**
+
+ EHTは、急速な大気の位相変動、大規模な記録帯域幅、広く性能が異なり地理的に分散した望遠鏡などに対して、膨大なデータ処理の課題を抱えていました。
+
+* **大量のデータ**
+
+ EHTは一日で350テラバイトを超える観測データを生成し、ヘリウムで満たされたハードドライブに保存しています。 この大量のデータとデータの複雑さを軽減することは非常に難しいことです。
+
+* **よくわからないものを観測する**
+
+ 研究の目標が今までに見たことのないものを見ることであるとき、どのようにして科学者はその画像が正しいと確信することができるのでしょうか?
+
+{{< figure src="/images/content_images/cs/dataprocessbh.png" class="csfigcaption" caption="**EHTのデータ処理パイプライン**" alt="data pipeline" align="middle" attr="(Diagram Credits: The Astrophysical Journal, Event Horizon Telescope Collaboration)" attrlink="https://iopscience.iop.org/article/10.3847/2041-8213/ab0c57" >}}
+
+## NumPyが果たした役割
+
+データに問題がある場合はどうなるでしょう? あるいは、アルゴリズムが特定の仮定に あまりにも大きく依存しているかもしれません。 もしあるパラメータを変更した場合、画像は大きく変化するのでしょうか?
+
+EHTの共同研究では、最先端の画像再構成技術を使用して、それぞれのチームがデータを評価することによって、これらの課題に対処しました。 それぞれのチームの解析結果が同じであることが証明されると、それらの結果を組み合わせることで、ブラックホール画像を得ることができました。
+
+彼らの研究は、共同のデータ解析を通じて科学を進歩させる、科学的なPythonエコシステムが果たす役割を如実に表しています。
+
+{{< figure src="/images/content_images/cs/bh_numpy_role.png" class="fig-center" alt="role of numpy" caption="**ブラックホールの画像化でNumpyが果たした役割**" >}}
+
+例えば、 [`eht-imaging`][ehtim] というPython パッケージは VLBI データで画像の再構築をシミュレートし、実行するためのツールです。 NumPyは、以下のソフトウェア依存関係チャートで示されているように、このパッケージで使用される配列データ処理の中核を担っています。
+
+{{< figure src="/images/content_images/cs/ehtim_numpy.png" class="fig-center" alt="ehtim dependency map highlighting numpy" caption="**Numpyの中心としたehtimのソフトウェア依存図**" >}}
+
+Numpyだけでなく、[SciPy](https://www.scipy.org)や[Pandas](https://pandas.io)などのパッケージもブラックホールの画像化のデータ処理パイプラインに利用されています。 天文学の標準的なファイル形式や時間/座標変換 は[Astropy][astropy]で実施し、ブラックホールの最終画像の生成を含め、解析パイプライン全体でのデータ可視化には [Matplotlib][mpl]が利用されました。
+
+## まとめ
+
+NumPyの中心的な機能である、効率的で適用性の高いn次元配列は、研究者が大規模な数値データを操作することを可能にし、世界で初めてのブラックホールの画像化の基礎を築きました。 アインシュタインの理論に素晴らしい視覚的証拠を与えたのは、科学の画期的な瞬間だといえます。 この科学的に偉大な達成には、技術的の飛躍的な進歩だけでなく、200人以上の科学者と世界で 最高の電波観測所の間での国際協力も寄与しました。 革新的なアルゴリズムとデータ処理技術は、既存の天文学モデルを改良し、宇宙の謎を解き明かす助けになったといえます。
+
+{{< figure src="/images/content_images/cs/numpy_bh_benefits.png" class="fig-center" alt="numpy benefits" caption== "**利用されたNumpyの主要機能**" >}}
+
+[resolution]: https://eventhorizontelescope.org/press-release-april-10-2019-astronomers-capture-first-image-black-hole
+
+[eddington]: https://en.wikipedia.org/wiki/Eddington_experiment
+
+[ehtim]: https://github.com/achael/eht-imaging
+
+[astropy]: https://www.astropy.org/
+[mpl]: https://matplotlib.org/
From 8db5668aed06c7f44ad33e68a3ab3be86c5aef05 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:39:10 +0000
Subject: [PATCH 122/909] New translations news.md (Japanese)
---
content/ja/news.md | 83 ++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 83 insertions(+)
create mode 100644 content/ja/news.md
diff --git a/content/ja/news.md b/content/ja/news.md
new file mode 100644
index 0000000000..5dcb849596
--- /dev/null
+++ b/content/ja/news.md
@@ -0,0 +1,83 @@
+---
+title: News
+sidebar: false
+---
+
+### Diversity in the NumPy project
+
+_Sep 20, 2020_ -- We wrote a [statement on the state of, and discussion on social media around, diversity and inclusion in the NumPy project](/diversity_sep2020).
+
+
+### First official NumPy paper published in Nature!
+
+_Sep 16, 2020_ -- We are pleased to announce the publication of [the first official paper on NumPy](https://www.nature.com/articles/s41586-020-2649-2) as a review article in Nature. This comes 14 years after the release of NumPy 1.0. The paper covers applications and fundamental concepts of array programming, the rich scientific Python ecosystem built on top of NumPy, and the recently added array protocols to facilitate interoperability with external array and tensor libraries like CuPy, Dask, and JAX.
+
+
+### Python 3.9 is coming, when will NumPy release binary wheels?
+
+_Sept 14, 2020_ -- Python 3.9 will be released in a few weeks. If you are an early adopter of Python versions, you may be dissapointed to find that NumPy (and other binary packages like SciPy) will not have binary wheels ready on the day of the release. It is a major effort to adapt the build infrastructure to a new Python version and it typically takes a few weeks for the packages to appear on PyPI and conda-forge. In preparation for this event, please make sure to
+- update your `pip` to version 20.1 at least to support `manylinux2010` and `manylinux2014`
+- use [`--only-binary=numpy`](https://pip.pypa.io/en/stable/reference/pip_install/#cmdoption-only-binary) or `--only-binary=:all:` to prevent `pip` from trying to build from source.
+
+
+### Numpy 1.19.2 release
+
+_Sept 10, 2020_ -- [NumPy 1.19.2](https://numpy.org/devdocs/release/1.19.2-notes.html) is now available. This latest release in the 1.19 series fixes several bugs, prepares for the [upcoming Cython 3.x release](http://docs.cython.org/en/latest/src/changes.html) and pins setuptools to keep distutils working while upstream modifications are ongoing. The aarch64 wheels are built with the latest manylinux2014 release that fixes the problem of differing page sizes used by different linux distros.
+
+### The inaugural NumPy survey is live!
+
+_Jul 2, 2020_ -- This survey is meant to guide and set priorities for decision-making about the development of NumPy as software and as a community. The survey is available in 8 additional languages besides English: Bangla, Hindi, Japanese, Mandarin, Portuguese, Russian, Spanish and French.
+
+Please help us make NumPy better and take the survey [here](https://umdsurvey.umd.edu/jfe/form/SV_8bJrXjbhXf7saAl).
+
+
+### NumPy has a new logo!
+
+_Jun 24, 2020_ -- NumPy now has a new logo:
+
+
+
+The logo is a modern take on the old one, with a cleaner design. Thanks to Isabela Presedo-Floyd for designing the new logo, as well as to Travis Vaught for the old logo that served us well for 15+ years.
+
+
+### NumPy 1.19.0 release
+
+_Jun 20, 2020_ -- NumPy 1.19.0 is now available. This is the first release without Python 2 support, hence it was a "clean-up release". The minimum supported Python version is now Python 3.6. An important new feature is that the random number generation infrastructure that was introduced in NumPy 1.17.0 is now accessible from Cython.
+
+
+### Season of Docs acceptance
+
+_May 11, 2020_ -- NumPy has been accepted as one of the mentor organizations for the Google Season of Docs program. We are excited about the opportunity to work with a technical writer to improve NumPy's documentation once again! For more details, please see [the official Season of Docs site](https://developers.google.com/season-of-docs/) and our [ideas page](https://github.com/numpy/numpy/wiki/Google-Season-of-Docs-2020-Project-Ideas).
+
+
+### NumPy 1.18.0 release
+
+_Dec 22, 2019_ -- NumPy 1.18.0 is now available. After the major changes in 1.17.0, this is a consolidation release. It is the last minor release that will support Python 3.5. Highlights of the release includes the addition of basic infrastructure for linking with 64-bit BLAS and LAPACK libraries, and a new C-API for `numpy.random`.
+
+Please see the [release notes](https://github.com/numpy/numpy/releases/tag/v1.18.0) for more details.
+
+
+### NumPy receives a grant from the Chan Zuckerberg Initiative
+
+_Nov 15, 2019_ -- We are pleased to announce that NumPy and OpenBLAS, one of NumPy's key dependencies, have received a joint grant for $195,000 from the Chan Zuckerberg Initiative through their [Essential Open Source Software for Science program](https://chanzuckerberg.com/eoss/) that supports software maintenance, growth, development, and community engagement for open source tools critical to science.
+
+This grant will be used to ramp up the efforts in improving NumPy documentation, website redesign, and community development to better serve our large and rapidly growing user base, and ensure the long-term sustainability of the project. While the OpenBLAS team will focus on addressing sets of key technical issues, in particular thread-safety, AVX-512, and thread-local storage (TLS) issues, as well as algorithmic improvements in ReLAPACK (Recursive LAPACK) on which OpenBLAS depends.
+
+More details on our proposed initiatives and deliverables can be found in the [full grant proposal](https://figshare.com/articles/Proposal_NumPy_OpenBLAS_for_Chan_Zuckerberg_Initiative_EOSS_2019_round_1/10302167). The work is scheduled to start on Dec 1st, 2019 and continue for the next 12 months.
+
+
+## Releases
+
+Here is a list of NumPy releases, with links to release notes. All bugfix releases (only the `z` changes in the `x.y.z` version number) have no new features; minor releases (the `y` increases) do.
+
+- NumPy 1.18.4 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.18.4)) -- _3 May 2020_.
+- NumPy 1.18.3 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.18.3)) -- _19 Apr 2020_.
+- NumPy 1.18.2 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.18.2)) -- _17 Mar 2020_.
+- NumPy 1.18.1 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.18.1)) -- _6 Jan 2020_.
+- NumPy 1.17.5 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.17.5)) -- _1 Jan 2020_.
+- NumPy 1.18.0 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.18.0)) -- _22 Dec 2019_.
+- NumPy 1.17.4 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.17.4)) -- _11 Nov 2019_.
+- NumPy 1.17.0 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.17.0)) -- _26 Jul 2019_.
+- NumPy 1.16.0 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.16.0)) -- _14 Jan 2019_.
+- NumPy 1.15.0 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.15.0)) -- _23 Jul 2018_.
+- NumPy 1.14.0 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.14.0)) -- _7 Jan 2018_.
From 1134d03794f880ceeaaa6cc03e48a385c4d41341 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:39:12 +0000
Subject: [PATCH 123/909] New translations history.md (Japanese)
---
content/ja/history.md | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
create mode 100644 content/ja/history.md
diff --git a/content/ja/history.md b/content/ja/history.md
new file mode 100644
index 0000000000..0dae1ff01d
--- /dev/null
+++ b/content/ja/history.md
@@ -0,0 +1,21 @@
+---
+title: NumPyの歴史
+sidebar: false
+---
+
+Numpy は配列形式のデータ構造と配列形式に関連する高速な数値ルーチンを提供する Python の基礎的なライブラリです。 このライブラリの開発開始当初は資金も少なく、主に大学院生が開発していましたが、その多くはコンピュータサイエンスの教育を受けておらず、指導教官のサポートも受けていませんでした。 何百万もの資金調達と何百人もの優秀なエンジニアに支えられている当時の商用研究ソフトウェアのエコシステムを、少数の "野良"学生プログラマーのグループがひっくり返すことができると想像することさえ、当時は馬鹿げていると考えられていました。 しかし、完全にオープンなツールスタックの背後にある哲学的な動機と、独特の焦点を持つことによるコミュニティの盛り上がりと、フレンドリーなコミュニティの組み合わせは、長い目で見ると良い結果を得られることが知られていました。 現在では、Numpy は科学者、技術者、および世界中の多くの専門家によって信頼され、使われています。 例えば、重力波の解析に用いられた公開スクリプトはNumpyを利用していますし、「M87ブラックホール画像化プロジェクト」では、Numpyのことを引用しています。
+
+Numpy および関連ライブラリの開発におけるマイルストーンの詳細については、 [arxiv.org](arxiv.org/abs/1907.10121) を参照してください。
+
+NumpyのベースとなったNumericとNumarrayライブラリのコピーを入手したい場合は、以下のリンクを参照してください。
+
+[ *Numeric*](https://sourceforge.net/projects/numpy/files/Old%20Numeric/) のダウンロード*
+
+[*Numarray *](https://sourceforge.net/projects/numpy/files/Old%20Numarray/) のダウンロード*
+
+*これらの古いパッケージはもはや保守されていないことに注意してください。配列関連の処理をしたい場合は、NumPyを使用するか、NumPyライブラリを利用するために既存のコードをリファクタリングすることを強くお勧めします。
+
+### 過去の資料
+
+[*Numeric*マニュアルのダウンロード](static/numeric-manual.pdf)
+
From 7291de96b321ecba1d225eaf215498356c566bfc Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:39:14 +0000
Subject: [PATCH 124/909] New translations gethelp.md (Japanese)
---
content/ja/gethelp.md | 34 ++++++++++++++++++++++++++++++++++
1 file changed, 34 insertions(+)
create mode 100644 content/ja/gethelp.md
diff --git a/content/ja/gethelp.md b/content/ja/gethelp.md
new file mode 100644
index 0000000000..d378333ebb
--- /dev/null
+++ b/content/ja/gethelp.md
@@ -0,0 +1,34 @@
+---
+title: サポートを得る方法
+sidebar: false
+---
+
+**ユーザーからの質問:** ユーザーからの質問に対して回答を得る最も良い方法は、[StackOverflow](http://stackoverflow.com/questions/tagged/numpy)に質問を投稿することです。すでに数千ものユーザーからの回答を見ることができます。 規模は小さいですが、下記のような質問をする場所もあります: [IRC](https://webchat.freenode.net/?channels=%23numpy), [Gitter](https://gitter.im/numpy/numpy), [Reddit](https://www.reddit.com/r/Numpy/)。 私たちはこれらのサイトを定期的に確認して、直接質問に答えるようにしていますが、質問の数は膨大です。
+
+**開発関連の問題:** NumPyの開発関連の問題 (例: バグレポート) については、[コミュニティ](/community) のページを参照してください。
+
+
+
+### [StackOverflow](http://stackoverflow.com/questions/tagged/numpy)
+
+Numpyの使用方法に関する質問をするためのフォーラムです。例えば、「NumPyでXをするにはどうすればいいですか?」というような質問です。 質問をする時は、[ `#numpy` タグ](https://stackoverflow.com/help/tagging) を使用してください。
+
+***
+
+### [Reddit](https://www.reddit.com/r/Numpy/)
+
+もう一つの使い方に関する質問の場です。
+
+***
+
+### [Gitter](https://gitter.im/numpy/numpy)
+
+ユーザーとコミュニティメンバーがお互いに助け合うリアルタイムのチャットルームです。
+
+***
+
+### [IRC](https://webchat.freenode.net/?channels=%23numpy)
+
+ユーザーとコミュニティメンバーがお互いを助け合うもう一つのリアルタイムチャットルームです。
+
+***
From f0a8e746c12664bea60945344e12d3134d77f67c Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:39:16 +0000
Subject: [PATCH 125/909] New translations report-handling-manual.md (Japanese)
---
content/ja/report-handling-manual.md | 95 ++++++++++++++++++++++++++++
1 file changed, 95 insertions(+)
create mode 100644 content/ja/report-handling-manual.md
diff --git a/content/ja/report-handling-manual.md b/content/ja/report-handling-manual.md
new file mode 100644
index 0000000000..5586668cba
--- /dev/null
+++ b/content/ja/report-handling-manual.md
@@ -0,0 +1,95 @@
+---
+title: NumPy Code of Conduct - How to follow up on a report
+sidebar: false
+---
+
+This is the manual followed by NumPy’s Code of Conduct Committee. It’s used when we respond to an issue to make sure we’re consistent and fair.
+
+Enforcing the [Code of Conduct](/code-of-conduct) impacts our community today and for the future. It’s an action that we do not take lightly. When reviewing enforcement measures, the Code of Conduct Committee will keep the following values and guidelines in mind:
+
+* Act in a personal manner rather than impersonal. The Committee can engage the parties to understand the situation while respecting the privacy and any necessary confidentiality of reporters. However, sometimes it is necessary to communicate with one or more individuals directly: the Committee’s goal is to improve the health of our community rather than only produce a formal decision.
+* Emphasize empathy for individuals rather than judging behavior, avoiding binary labels of “good” and “bad/evil”. Overt, clear-cut aggression and harassment exist, and we will address them firmly. But many scenarios that can prove challenging to resolve are those where normal disagreements devolve into unhelpful or harmful behavior from multiple parties. Understanding the full context and finding a path that re-engages all is hard, but ultimately the most productive for our community.
+* We understand that email is a difficult medium and can be isolating. Receiving criticism over email, without personal contact, can be particularly painful. This makes it especially important to keep an atmosphere of open-minded respect for the views of others. It also means that we must be transparent in our actions, and that we will do everything in our power to make sure that all our members are treated fairly and with sympathy.
+* Discrimination can be subtle and it can be unconscious. It can show itself as unfairness and hostility in otherwise ordinary interactions. We know that this does occur, and we will take care to look out for it. We would very much like to hear from you if you feel you have been treated unfairly, and we will use these procedures to make sure that your complaint is heard and addressed.
+* Help increase engagement in good discussion practice: try to identify where discussion may have broken down, and provide actionable information, pointers, and resources that can lead to positive change on these points.
+* Be mindful of the needs of new members: provide them with explicit support and consideration, with the aim of increasing participation from underrepresented groups in particular.
+* Individuals come from different cultural backgrounds and native languages. Try to identify any honest misunderstandings caused by a non-native speaker and help them understand the issue and what they can change to avoid causing offence. Complex discussion in a foreign language can be very intimidating, and we want to grow our diversity also across nationalities and cultures.
+
+
+## Mediation
+
+Voluntary informal mediation is a tool at our disposal. In contexts such as when two or more parties have all escalated to the point of inappropriate behavior (something sadly common in human conflict), it may be useful to facilitate a mediation process. This is only an example: the Committee can consider mediation in any case, mindful that the process is meant to be strictly voluntary and no party can be pressured to participate. If the Committee suggests mediation, it should:
+
+* Find a candidate who can serve as a mediator.
+* Obtain the agreement of the reporter(s). The reporter(s) have complete freedom to decline the mediation idea or to propose an alternate mediator.
+* Obtain the agreement of the reported person(s).
+* Settle on the mediator: while parties can propose a different mediator than the suggested candidate, only if a common agreement is reached on all terms can the process move forward.
+* Establish a timeline for mediation to complete, ideally within two weeks.
+
+The mediator will engage with all the parties and seek a resolution that is satisfactory to all. Upon completion, the mediator will provide a report (vetted by all parties to the process) to the Committee, with recommendations on further steps. The Committee will then evaluate these results (whether a satisfactory resolution was achieved or not) and decide on any additional action deemed necessary.
+
+
+## How the Committee will respond to reports
+
+When the Committee (or a Committee member) receives a report, they will first determine whether the report is about a clear and severe breach (as defined below). If so, immediate action needs to be taken in addition to the regular report handling process.
+
+
+## Clear and severe breach actions
+
+We know that it is painfully common for internet communication to start at or devolve into obvious and flagrant abuse. We will deal quickly with clear and severe breaches like personal threats, violent, sexist or racist language.
+
+When a member of the Code of Conduct Committee becomes aware of a clear and severe breach, they will do the following:
+
+* Immediately disconnect the originator from all NumPy communication channels.
+* Reply to the reporter that their report has been received and that the originator has been disconnected.
+* In every case, the moderator should make a reasonable effort to contact the originator, and tell them specifically how their language or actions qualify as a “clear and severe breach”. The moderator should also say that, if the originator believes this is unfair or they want to be reconnected to NumPy, they have the right to ask for a review, as below, by the Code of Conduct Committee. The moderator should copy this explanation to the Code of Conduct Committee.
+* The Code of Conduct Committee will formally review and sign off on all cases where this mechanism has been applied to make sure it is not being used to control ordinary heated disagreement.
+
+
+## Report handling
+
+When a report is sent to the Committee they will immediately reply to the reporter to confirm receipt. This reply must be sent within 72 hours, and the group should strive to respond much quicker than that.
+
+If a report doesn’t contain enough information, the Committee will obtain all relevant data before acting. The Committee is empowered to act on the Steering Council’s behalf in contacting any individuals involved to get a more complete account of events.
+
+The Committee will then review the incident and determine, to the best of their ability:
+
+* What happened.
+* Whether this event constitutes a Code of Conduct violation.
+* Who are the responsible party(ies).
+* Whether this is an ongoing situation, and there is a threat to anyone’s physical safety.
+
+This information will be collected in writing, and whenever possible the group’s deliberations will be recorded and retained (i.e. chat transcripts, email discussions, recorded conference calls, summaries of voice conversations, etc).
+
+It is important to retain an archive of all activities of this Committee to ensure consistency in behavior and provide institutional memory for the project. To assist in this, the default channel of discussion for this Committee will be a private mailing list accessible to current and future members of the Committee as well as members of the Steering Council upon justified request. If the Committee finds the need to use off-list communications (e.g. phone calls for early/rapid response), it should in all cases summarize these back to the list so there’s a good record of the process.
+
+The Code of Conduct Committee should aim to have a resolution agreed upon within two weeks. In the event that a resolution can’t be determined in that time, the Committee will respond to the reporter(s) with an update and projected timeline for resolution.
+
+
+## Resolutions
+
+The Committee must agree on a resolution by consensus. If the group cannot reach consensus and deadlocks for over a week, the group will turn the matter over to the Steering Council for resolution.
+
+Possible responses may include:
+
+* Taking no further action:
+ - if we determine no violations have occurred;
+ - if the matter has been resolved publicly while the Committee was considering responses.
+* Coordinating voluntary mediation: if all involved parties agree, the Committee may facilitate a mediation process as detailed above.
+* Remind publicly, and point out that some behavior/actions/language have been judged inappropriate and why in the current context, or can but hurtful to some people, requesting the community to self-adjust.
+* A private reprimand from the Committee to the individual(s) involved. In this case, the group chair will deliver that reprimand to the individual(s) over email, cc’ing the group.
+* A public reprimand. In this case, the Committee chair will deliver that reprimand in the same venue that the violation occurred, within the limits of practicality. E.g., the original mailing list for an email violation, but for a chat room discussion where the person/context may be gone, they can be reached by other means. The group may choose to publish this message elsewhere for documentation purposes.
+* A request for a public or private apology, assuming the reporter agrees to this idea: they may at their discretion refuse further contact with the violator. The chair will deliver this request. The Committee may, if it chooses, attach “strings” to this request: for example, the group may ask a violator to apologize in order to retain one’s membership on a mailing list.
+* A “mutually agreed upon hiatus” where the Committee asks the individual to temporarily refrain from community participation. If the individual chooses not to take a temporary break voluntarily, the Committee may issue a “mandatory cooling off period”.
+* A permanent or temporary ban from some or all NumPy spaces (mailing lists, gitter.im, etc.). The group will maintain records of all such bans so that they may be reviewed in the future or otherwise maintained.
+
+Once a resolution is agreed upon, but before it is enacted, the Committee will contact the original reporter and any other affected parties and explain the proposed resolution. The Committee will ask if this resolution is acceptable, and must note feedback for the record.
+
+Finally, the Committee will make a report to the NumPy Steering Council (as well as the NumPy core team in the event of an ongoing resolution, such as a ban).
+
+The Committee will never publicly discuss the issue; all public statements will be made by the chair of the Code of Conduct Committee or the NumPy Steering Council.
+
+
+## Conflicts of Interest
+
+In the event of any conflict of interest, a Committee member must immediately notify the other members, and recuse themselves if necessary.
From 83ee91ce825bf783e5e32731582714ec424f6f58 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 15:39:18 +0000
Subject: [PATCH 126/909] New translations contribute.md (Portuguese,
Brazilian)
---
content/pt/contribute.md | 78 ++++++++++++++++++++++++++++++++++++++++
1 file changed, 78 insertions(+)
create mode 100644 content/pt/contribute.md
diff --git a/content/pt/contribute.md b/content/pt/contribute.md
new file mode 100644
index 0000000000..74998f1e44
--- /dev/null
+++ b/content/pt/contribute.md
@@ -0,0 +1,78 @@
+- - -
+title: Contribua com o NumPy sidebar: false
+- - -
+
+The NumPy project welcomes your expertise and enthusiasm! Your choices aren't limited to programming -- in addition to
+
+- [Writing code](#writing-code)
+
+you can
+
+- [Review pull requests](#reviewing-pull-requests)
+- [Develop tutorials, presentations, and other educational material](#developing-educational-materials)
+- [Triage issues](#issue-triaging)
+- [Work on our website](#website-development)
+- [Contribute graphic design](#graphic-design)
+- [Translate website content](#translating-website-content)
+- [Serve as a community coordinator](#community-coordination-and-outreach)
+- [Write grant proposals and help with other fundraising](#fundraising)
+
+If you're unsure where to start or how your skills fit in, _reach out!_ You can ask on the [mailing list](https://mail.python.org/mailman/listinfo/numpy-discussion) or [GitHub](http://github.com/numpy/numpy) (open an [issue](https://github.com/numpy/numpy/issues) or comment on a relevant issue).
+
+Those are our preferred channels (open source is open by nature), but if you prefer to talk privately, contact our community coordinators at or on [Slack](https://numpy-team.slack.com) (write for an invite).
+
+We also have a biweekly _community call_, details of which are announced on the [mailing list](https://mail.python.org/mailman/listinfo/numpy-discussion). You are very welcome to join. If you are new to contributing to open source, we also highly recommend reading [this guide](https://opensource.guide/how-to-contribute/).
+
+Our community aspires to treat everyone equally and to value all contributions. We have a [Code of Conduct](/code-of-conduct) to foster an open and welcoming environment.
+
+### Writing code
+
+Programmers, this [guide](https://numpy.org/devdocs/dev/index.html#development-process-summary) explains how to contribute to the codebase.
+
+### Reviewing pull requests
+The project has more than 250 open pull requests -- meaning many potential improvements and many open-source contributors waiting for feedback. If you're a developer who knows NumPy, you can help even if you're not familiar with the codebase. You can:
+* summarize a long-running discussion
+* triage documentation PRs
+* test proposed changes
+
+
+### Developing educational materials
+
+NumPy's [User Guide](https://numpy.org/devdocs) is undergoing rehabilitation. We're in need of new tutorials, how-to's, and deep-dive explanations, and the site needs restructuring. Opportunities aren't limited to writers. We'd also welcome worked examples, notebooks, and videos. [NEP 44 — Restructuring the NumPyDocumentation](https://numpy.org/neps/nep-0044-restructuring-numpy-docs.html) lays out our ideas -- and you may have others.
+
+
+### Issue triaging
+
+The [NumPy issue tracker](https://github.com/numpy/numpy/issues) has a _lot_ of open issues. Some are no longer valid, some should be prioritized, and some would make good issues for new contributors. You can:
+
+* check if older bugs are still present
+* find duplicate issues and link related ones
+* add good self-contained reproducers to issues
+* label issues correctly (this requires triage rights -- just ask)
+
+Please just dive in.
+
+
+### Website development
+
+We've just revamped our website, but we're far from done. If you love web development, these [issues](https://github.com/numpy/numpy.org/issues?q=is%3Aissue+is%3Aopen+label%3Adesign) list some of our unmet needs -- and feel free to share your own ideas.
+
+
+### Graphic design
+
+We can barely begin to list the contributions a graphic designer can make here. Our docs are parched for illustration; our growing website craves images -- opportunities abound.
+
+
+### Translating website content
+
+We plan multiple translations of [numpy.org](https://numpy.org) to make NumPy accessible to users in their native language. Volunteer translators are at the heart of this effort. See [here](https://numpy.org/neps/nep-0028-website-redesign.html#translation-multilingual-i18n) for background; comment on [this GitHub issue](https://github.com/numpy/numpy.org/issues/55) to sign up.
+
+
+### Community coordination and outreach
+
+Through community contact we share our work more widely and learn where we're falling short. We're eager to get more people involved in efforts like our [Twitter](https://twitter.com/numpy_team) account, organizing NumPy [code sprints](https://scisprints.github.io/), a newsletter, and perhaps a blog.
+
+### Fundraising
+
+NumPy was all-volunteer for many years, but as its importance grew it became clear that to ensure stability and growth we'd need financial support. [This SciPy'19 talk](https://www.youtube.com/watch?v=dBTJD_FDVjU) explains how much difference that support has made. Like all the nonprofit world, we're constantly searching for grants, sponsorships, and other kinds of support. We have a number of ideas and of course we welcome more. Fundraising is a scarce skill here -- we'd appreciate your help.
+
From 1a06c79adc297e13af28713b9241de8a2d7d8be9 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 23 Jan 2021 23:33:34 +0000
Subject: [PATCH 127/909] New translations cricket-analytics.md (Japanese)
---
content/ja/case-studies/cricket-analytics.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/content/ja/case-studies/cricket-analytics.md b/content/ja/case-studies/cricket-analytics.md
index 987b38fb68..37ea8448cf 100644
--- a/content/ja/case-studies/cricket-analytics.md
+++ b/content/ja/case-studies/cricket-analytics.md
@@ -1,9 +1,9 @@
---
-title: "Case Study: Cricket Analytics, the game changer!"
+title: "ケーススタディ: クリケット分析、ゲームチェンジャー!"
sidebar: false
---
-{{< figure src="/images/content_images/cs/ipl-stadium.png" caption="**IPLT20, the biggest Cricket Festival in India**" alt="Indian Premier League Cricket cup and stadium" attr="*(Image credits: IPLT20 (cup and logo) & Akash Yadav (stadium))*" attrlink="https://unsplash.com/@aksh1802" >}}
+{{< figure src="/images/content_images/cs/ipl-stadium.png" caption="** IPLT20、インド最大のクリケットフェスティバル**" alt="Indian Premier League Cricket cup and stadium" attr="*(Image credits: IPLT20 (cup and logo) & Akash Yadav (stadium))*" attrlink="https://unsplash.com/@aksh1802" >}}
You don't play for the crowd, you play for the country.
From ef2492b64c159061209f9732ecc4ea85130df80e Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sun, 24 Jan 2021 00:33:00 +0000
Subject: [PATCH 128/909] New translations cricket-analytics.md (Japanese)
---
content/ja/case-studies/cricket-analytics.md | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/content/ja/case-studies/cricket-analytics.md b/content/ja/case-studies/cricket-analytics.md
index 37ea8448cf..2d0485c69a 100644
--- a/content/ja/case-studies/cricket-analytics.md
+++ b/content/ja/case-studies/cricket-analytics.md
@@ -6,17 +6,17 @@ sidebar: false
{{< figure src="/images/content_images/cs/ipl-stadium.png" caption="** IPLT20、インド最大のクリケットフェスティバル**" alt="Indian Premier League Cricket cup and stadium" attr="*(Image credits: IPLT20 (cup and logo) & Akash Yadav (stadium))*" attrlink="https://unsplash.com/@aksh1802" >}}
-
You don't play for the crowd, you play for the country.
-
+
観客のために競技をするのではなく、国のために競技するのです。
+
-## About Cricket
+## クリケットについて
-It would be an understatement to state that Indians love cricket. The game is played in just about every nook and cranny of India, rural or urban, popular with the young and the old alike, connecting billions in India unlike any other sport. Cricket enjoys lots of media attention. There is a significant amount of [money](https://www.statista.com/topics/4543/indian-premier-league-ipl/) and fame at stake. Over the last several years, technology has literally been a game changer. Audiences are spoilt for choice with streaming media, tournaments, affordable access to mobile based live cricket watching, and more.
+インド人はクリケットが大好きだと言っても過言ではないでしょう。 この競技は、他のスポーツと異なり、インドの農村部や都市部を問わず、あらゆる場所でプレイされており、若者から年配の方まで広く人気があり、インドでは何十億人もの人々を結びつける役割を担っています。 クリケットは多くのメディアの注目を集めています。 非常に [多額のお金](https://www.statista.com/topics/4543/indian-premier-league-ipl/)と名声がかかっています。 過去数年間、テクノロジーは文字通りクリケットの試合を変えてきました。 視聴者は、ストリーミングメディアや、トーナメント、モバイルベースの手頃なアクセスによるライブクリケット視聴や、その他の方法に甘やかされています。
-The Indian Premier League (IPL) is a professional Twenty20 cricket league, founded in 2008. It is one of the most attended cricketing events in the world, valued at [$6.7 billion](https://en.wikipedia.org/wiki/Indian_Premier_League) in 2019.
+インドプレミアリーグ (IPL) は、2008年に設立された20チームから成るプロクリケットリーグです。 これは、2019年に [67億ドル](https://en.wikipedia.org/wiki/Indian_Premier_League) の市場規模と評価される世界で最も参加者が多いクリケットイベントの1つです。
-Cricket is a game of numbers - the runs scored by a batsman, the wickets taken by a bowler, the matches won by a cricket team, the number of times a batsman responds in a certain way to a kind of bowling attack, etc. The capability to dig into cricketing numbers for both improving performance and studying the business opportunities, overall market, and economics of cricket via powerful analytics tools, powered by numerical computing software such as NumPy, is a big deal. Cricket analytics provides interesting insights into the game and predictive intelligence regarding game outcomes.
+クリケットは数のゲームです - バッツマンによってスコアされたランの数、ボウラーによって取られたウィケットの数、クリケットチームによって獲得した試合の数、バッツマンがボウリング攻撃に特定の方法で応答する回数など。 クリケットの数字を掘り下げてパフォーマンスを向上させるとともに、NumPyなどの数値計算ソフトウェアを利用した強力な分析ツールを介して、クリケットのビジネスチャンス、市場全体、経済性を研究することは、大きな意味を持ちます。 クリケット分析は、試合に関する興味深い洞察と、ゲームの結果に関する予測AIを提供します。
Today, there are rich and almost infinite troves of cricket game records and statistics available, e.g., [ESPN cricinfo](https://stats.espncricinfo.com/ci/engine/stats/index.html) and [cricsheet](https://cricsheet.org). These and several such cricket databases have been used for [cricket analysis](https://www.researchgate.net/publication/336886516_Data_visualization_and_toss_related_analysis_of_IPL_teams_and_batsmen_performances) using the latest machine learning and predictive modelling algorithms. Media and entertainment platforms along with professional sports bodies associated with the game use technology and analytics for determining key metrics for improving match winning chances:
From 1adbb62f3d46980bc9afac13d25ae8cd187506b6 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Mon, 25 Jan 2021 10:05:31 +0000
Subject: [PATCH 129/909] New translations cricket-analytics.md (Japanese)
---
content/ja/case-studies/cricket-analytics.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/content/ja/case-studies/cricket-analytics.md b/content/ja/case-studies/cricket-analytics.md
index 2d0485c69a..1f8372667f 100644
--- a/content/ja/case-studies/cricket-analytics.md
+++ b/content/ja/case-studies/cricket-analytics.md
@@ -18,10 +18,10 @@ sidebar: false
クリケットは数のゲームです - バッツマンによってスコアされたランの数、ボウラーによって取られたウィケットの数、クリケットチームによって獲得した試合の数、バッツマンがボウリング攻撃に特定の方法で応答する回数など。 クリケットの数字を掘り下げてパフォーマンスを向上させるとともに、NumPyなどの数値計算ソフトウェアを利用した強力な分析ツールを介して、クリケットのビジネスチャンス、市場全体、経済性を研究することは、大きな意味を持ちます。 クリケット分析は、試合に関する興味深い洞察と、ゲームの結果に関する予測AIを提供します。
-Today, there are rich and almost infinite troves of cricket game records and statistics available, e.g., [ESPN cricinfo](https://stats.espncricinfo.com/ci/engine/stats/index.html) and [cricsheet](https://cricsheet.org). These and several such cricket databases have been used for [cricket analysis](https://www.researchgate.net/publication/336886516_Data_visualization_and_toss_related_analysis_of_IPL_teams_and_batsmen_performances) using the latest machine learning and predictive modelling algorithms. Media and entertainment platforms along with professional sports bodies associated with the game use technology and analytics for determining key metrics for improving match winning chances:
+現在では、クリケットゲームの記録と 利用可能な統計データは豊富で、ほぼ無限の宝の山だと言えます。: [ESPN cricinfo や](https://stats.espncricinfo.com/ci/engine/stats/index.html) [cricsheet](https://cricsheet.org). これらのクリケットデータベースは、最新の機械学習と予測モデリングアルゴリズムを使用して、 [クリケット 分析](https://www.researchgate.net/publication/336886516_Data_visualization_and_toss_related_analysis_of_IPL_teams_and_batsmen_performances) に使用されています。 メディアやプロスポーツ団体のエンターテインメントプラットフォームは、技術や分析を利用し、試合勝率を向上させるための主要なメトリックを下記のような要素だと考え始めています:
-* batting performance moving average,
-* score forecasting,
+* バッティングの記録の移動平均
+* スコア予測
* gaining insights into fitness and performance of a player against different opposition,
* player contribution to wins and losses for making strategic decisions on team composition
From b932f902829af701cfafc56474f8a76e73b73404 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Mon, 25 Jan 2021 11:08:10 +0000
Subject: [PATCH 130/909] New translations cricket-analytics.md (Japanese)
---
content/ja/case-studies/cricket-analytics.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/content/ja/case-studies/cricket-analytics.md b/content/ja/case-studies/cricket-analytics.md
index 1f8372667f..a3845cc7da 100644
--- a/content/ja/case-studies/cricket-analytics.md
+++ b/content/ja/case-studies/cricket-analytics.md
@@ -22,8 +22,8 @@ sidebar: false
* バッティングの記録の移動平均
* スコア予測
-* gaining insights into fitness and performance of a player against different opposition,
-* player contribution to wins and losses for making strategic decisions on team composition
+* プレイヤーの体力やパフォーマンスについての知識を得ること
+* チーム構成に戦略的な決定を下すための、各勝敗へのプレイヤーの貢献
{{< figure src="/images/content_images/cs/cricket-pitch.png" class="csfigcaption" caption="**Cricket Pitch, the focal point in the field**" alt="A cricket pitch with bowler and batsmen" align="middle" attr="*(Image credit: Debarghya Das)*" attrlink="http://debarghyadas.com/files/IPLpaper.pdf" >}}
From dcfb9cd777ff94e159d12372d86a397f8551581b Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Fri, 29 Jan 2021 23:23:53 +0000
Subject: [PATCH 131/909] New translations cricket-analytics.md (Japanese)
---
content/ja/case-studies/cricket-analytics.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/content/ja/case-studies/cricket-analytics.md b/content/ja/case-studies/cricket-analytics.md
index a3845cc7da..6aa76fc7a3 100644
--- a/content/ja/case-studies/cricket-analytics.md
+++ b/content/ja/case-studies/cricket-analytics.md
@@ -25,11 +25,11 @@ sidebar: false
* プレイヤーの体力やパフォーマンスについての知識を得ること
* チーム構成に戦略的な決定を下すための、各勝敗へのプレイヤーの貢献
-{{< figure src="/images/content_images/cs/cricket-pitch.png" class="csfigcaption" caption="**Cricket Pitch, the focal point in the field**" alt="A cricket pitch with bowler and batsmen" align="middle" attr="*(Image credit: Debarghya Das)*" attrlink="http://debarghyadas.com/files/IPLpaper.pdf" >}}
+{{< figure src="/images/content_images/cs/cricket-pitch.png" class="csfigcaption" caption="** フィールドのフォーカルポイントとなるクリケットピッチ**" alt="A cricket pitch with bowler and batsmen" align="middle" attr="*(Image credit: Debarghya Das)*" attrlink="http://debarghyadas.com/files/IPLpaper.pdf" >}}
-### Key Data Analytics Objectives
+### データ分析の主要な目標
-* Sports data analytics are used not only in cricket but many [other sports](https://adtmag.com/blogs/dev-watch/2017/07/sports-analytics.aspx) for improving the overall team performance and maximizing winning chances.
+* スポーツデータ分析はクリケットだけでなく、チーム全体のパフォーマンスを向上させ、勝利率を最大限に高めるために、 [ 他のスポーツ](https://adtmag.com/blogs/dev-watch/2017/07/sports-analytics.aspx)でも使用されています。
* Real-time data analytics can help in gaining insights even during the game for changing tactics by the team and by associated businesses for economic benefits and growth.
* Besides historical analysis, predictive models are harnessed to determine the possible match outcomes that require significant number crunching and data science know-how, visualization tools and capability to include newer observations in the analysis.
From c3b52acd7861282e7152a676e2867fa3d2fd87f2 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 30 Jan 2021 00:21:04 +0000
Subject: [PATCH 132/909] New translations cricket-analytics.md (Japanese)
---
content/ja/case-studies/cricket-analytics.md | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/content/ja/case-studies/cricket-analytics.md b/content/ja/case-studies/cricket-analytics.md
index 6aa76fc7a3..8295d1b66d 100644
--- a/content/ja/case-studies/cricket-analytics.md
+++ b/content/ja/case-studies/cricket-analytics.md
@@ -30,20 +30,20 @@ sidebar: false
### データ分析の主要な目標
* スポーツデータ分析はクリケットだけでなく、チーム全体のパフォーマンスを向上させ、勝利率を最大限に高めるために、 [ 他のスポーツ](https://adtmag.com/blogs/dev-watch/2017/07/sports-analytics.aspx)でも使用されています。
-* Real-time data analytics can help in gaining insights even during the game for changing tactics by the team and by associated businesses for economic benefits and growth.
-* Besides historical analysis, predictive models are harnessed to determine the possible match outcomes that require significant number crunching and data science know-how, visualization tools and capability to include newer observations in the analysis.
+* リアルタイムデータ分析は、ゲーム中の洞察を得ることができ、チームや関連ビジネスが経済的利益と成長のために戦術を変更するためも役立ちます。
+* 履歴分析に加えて、予測モデルは可能性のある結果を求めることができますが、かなりの数のナンバークランチングとデータサイエンスのノウハウ、可視化ツール、および分析に新しい観測データを含める機能などが必要になります。
-{{< figure src="/images/content_images/cs/player-pose-estimator.png" class="fig-center" alt="pose estimator" caption="**Cricket Pose Estimator**" attr="*(Image credit: connect.vin)*" attrlink="https://connect.vin/2019/05/ai-for-cricket-batsman-pose-analysis/" >}}
+{{< figure src="/images/content_images/cs/player-pose-estimator.png" class="fig-center" alt="pose estimator" caption="**クリケットの姿勢推定**" attr="*(Image credit: connect.vin)*" attrlink="https://connect.vin/2019/05/ai-for-cricket-batsman-pose-analysis/" >}}
-### The Challenges
+### 課題
-* **Data Cleaning and preprocessing**
+* **データのクリーニングと前処理**
- IPL has expanded cricket beyond the classic test match format to a much larger scale. The number of matches played every season across various formats has increased and so has the data, the algorithms, newer sports data analysis technologies and simulation models. Cricket data analysis requires field mapping, player tracking, ball tracking, player shot analysis, and several other aspects involved in how the ball is delivered, its angle, spin, velocity, and trajectory. All these factors together have increased the complexity of data cleaning and preprocessing.
+ IPLは、クリケットを古典的なテストマッチ形式をから、はるかに大規模に拡大させました。 毎シーズン、様々なフォーマットで行われる試合の数は増加しており、データ、アルゴリズム、最新のスポーツデータ分析技術、シミュレーションモデルも増加しています。 クリケットのデータ分析には、フィールドマッピング、プレイヤートラッキング、ボールトラッキング、プレイヤーショット分析、およびボールがどのように動くのか、その角度、スピン、速度、軌道など、他の沢山の種類のデータを必要とします。 これらの要因により、データクリーニングと前処理の複雑さが増してしまいました。
-* **Dynamic Modeling**
+* **動的モデリング**
- In cricket, just like any other sport, there can be a large number of variables related to tracking various numbers of players on the field, their attributes, the ball, and several possibilities of potential actions. The complexity of data analytics and modeling is directly proportional to the kind of predictive questions that are put forth during analysis and are highly dependent on data representation and the model. Things get even more challenging in terms of computation, data comparisons when dynamic cricket play predictions are sought such as what would have happened if the batsman had hit the ball at a different angle or velocity.
+ クリケットも、他のスポーツのように、フィールド上の選手の様々な数字を追跡するために、関連する変数の数が多くなってしまいがちです。たとえば、ボールやその属性情報、および潜在的なアクションのいくつかの可能性などの変数です。 データ分析とモデリングの複雑さは、分析中に必要となる予測のための質問の種類に正比例しており、データ表現とモデルにも大きく依存しています。 Things get even more challenging in terms of computation, data comparisons when dynamic cricket play predictions are sought such as what would have happened if the batsman had hit the ball at a different angle or velocity.
* **Predictive Analytics Complexity**
From fac5520853e0b92776013547ce5e37653ac1afcc Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 30 Jan 2021 07:50:40 +0000
Subject: [PATCH 133/909] New translations cricket-analytics.md (Japanese)
---
content/ja/case-studies/cricket-analytics.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/content/ja/case-studies/cricket-analytics.md b/content/ja/case-studies/cricket-analytics.md
index 8295d1b66d..0cda3c7651 100644
--- a/content/ja/case-studies/cricket-analytics.md
+++ b/content/ja/case-studies/cricket-analytics.md
@@ -43,11 +43,11 @@ sidebar: false
* **動的モデリング**
- クリケットも、他のスポーツのように、フィールド上の選手の様々な数字を追跡するために、関連する変数の数が多くなってしまいがちです。たとえば、ボールやその属性情報、および潜在的なアクションのいくつかの可能性などの変数です。 データ分析とモデリングの複雑さは、分析中に必要となる予測のための質問の種類に正比例しており、データ表現とモデルにも大きく依存しています。 Things get even more challenging in terms of computation, data comparisons when dynamic cricket play predictions are sought such as what would have happened if the batsman had hit the ball at a different angle or velocity.
+ クリケットも、他のスポーツのように、フィールド上の選手の様々な数字を追跡するために、関連する変数の数が多くなってしまいがちです。たとえば、ボールやその属性情報、および潜在的なアクションのいくつかの可能性などの変数です。 データ分析とモデリングの複雑さは、分析中に必要となる予測のための質問の種類に正比例しており、データ表現とモデルにも大きく依存しています。 打者が異なる角度や速度でボールを打った場合に何が起こるのかのような、動的なクリケットのプレーの予測が必要な場合、計算量やデータ比較が更に困難になります。
-* **Predictive Analytics Complexity**
+* **予測分析の複雑さ**
- Much of the decision making in cricket is based on questions such as "how often does a batsman play a certain kind of shot if the ball delivery is of a particular type", or "how does a bowler change his line and length if the batsman responds to his delivery in a certain way". This kind of predictive analytics query requires highly granular dataset availability and the capability to synthesize data and create generative models that are highly accurate.
+ クリケットの意思決定の多くは、"ボール運びがある特定のタイプの場合、バッツマンはどのくらいの頻度で特定の種類のショットを打つのか?"や、"バッツマンが特定の方法であるボール運びに反応した場合、ボウラーはどのように彼のラインと長さを変更するのか "などの質問に基づいています。 This kind of predictive analytics query requires highly granular dataset availability and the capability to synthesize data and create generative models that are highly accurate.
## NumPy’s Role in Cricket Analytics
From ef297032eb62afa6b5bc797ec9375177e93ea7ba Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 30 Jan 2021 08:57:35 +0000
Subject: [PATCH 134/909] New translations cricket-analytics.md (Japanese)
---
content/ja/case-studies/cricket-analytics.md | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/content/ja/case-studies/cricket-analytics.md b/content/ja/case-studies/cricket-analytics.md
index 0cda3c7651..ceedd0743a 100644
--- a/content/ja/case-studies/cricket-analytics.md
+++ b/content/ja/case-studies/cricket-analytics.md
@@ -47,18 +47,18 @@ sidebar: false
* **予測分析の複雑さ**
- クリケットの意思決定の多くは、"ボール運びがある特定のタイプの場合、バッツマンはどのくらいの頻度で特定の種類のショットを打つのか?"や、"バッツマンが特定の方法であるボール運びに反応した場合、ボウラーはどのように彼のラインと長さを変更するのか "などの質問に基づいています。 This kind of predictive analytics query requires highly granular dataset availability and the capability to synthesize data and create generative models that are highly accurate.
+ クリケットの意思決定の多くは、"ボール運びがある特定のタイプの場合、バッツマンはどのくらいの頻度で特定の種類のショットを打つのか?"や、"バッツマンが特定の方法であるボール運びに反応した場合、ボウラーはどのように彼のラインと長さを変更するのか "などの質問に基づいています。 この種の予測分析クエリには、精度の良いデータセットが利用できること、データを合成して高精度な生成モデルを作成する能力が必要です。
-## NumPy’s Role in Cricket Analytics
+## クリケット解析におけるNumPyの役割
-Sports Analytics is a thriving field. Many researchers and companies [use NumPy](https://adtmag.com/blogs/dev-watch/2017/07/sports-analytics.aspx) and other PyData packages like Scikit-learn, SciPy, Matplotlib, and Jupyter, besides using the latest machine learning and AI techniques. NumPy has been used for various kinds of cricket related sporting analytics such as:
+スポーツ分析は現在、非常に盛んな分野です。 多くの研究者や企業は、最新の機械学習やAI技術以外にも、Numpyや、Scikit-learn, SciPy, Matplotlib, Jupyter などの他の PyData パッケージを [使っています](https://adtmag.com/blogs/dev-watch/2017/07/sports-analytics.aspx)。 Numpy は 以下のような様々な種類のクリケット関連のスポーツ分析に使用されています:
-* **Statistical Analysis:** NumPy's numerical capabilities help estimate the statistical significance of observational data or match events in the context of various player and game tactics, estimating the game outcome by comparison with a generative or static model. [Causal analysis](https://amplitude.com/blog/2017/01/19/causation-correlation) and [big data approaches](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4996805/) are used for tactical analysis.
+* **統計分析:** NumPyの数値計算機能は、様々なプレイヤーやゲーム戦術のコンテキストでの観測データで、試合中のイベントの統計的有意性を推定し、生成モデルや静的モデルと比較して試合結果を推定するのに役立ちます。 [因果分析](https://amplitude.com/blog/2017/01/19/causation-correlation) と [ビッグデータアプローチ](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4996805/) は戦術的分析に使用されています。
-* **Data Visualization:** Data graphing and [visualization](https://towardsdatascience.com/advanced-sports-visualization-with-pandas-matplotlib-and-seaborn-9c16df80a81b) provides useful insights into relationship between various datasets.
+* **データ可視化:** データのグラフ化と [視覚化](https://towardsdatascience.com/advanced-sports-visualization-with-pandas-matplotlib-and-seaborn-9c16df80a81b) は、さまざまなデータセット間の関係に関する、有益な洞察を与えてくれます。
-## Summary
+## まとめ
-Sports Analytics is a game changer when it comes to how professional games are played, especially how strategic decision making happens, which until recently was primarily done based on “gut feeling" or adherence to past traditions. NumPy forms a solid foundation for a large set of Python packages which provide higher level functions related to data analytics, machine learning, and AI algorithms. These packages are widely deployed to gain real-time insights that help in decision making for game-changing outcomes, both on field as well as to draw inferences and drive business around the game of cricket. Finding out the hidden parameters, patterns, and attributes that lead to the outcome of a cricket match helps the stakeholders to take notice of game insights that are otherwise hidden in numbers and statistics.
+スポーツアナリティクスは、それがプロの試合がどのように実施されるか、特に最近まで主に "直感 "や過去の伝統的な考え方に基づいて行われていた戦略的な意思決定が、どのように起こるかという面で、世界を変えた技術的であるといえます。 NumPyは、データ分析や機械学習、人工知能のアルゴリズムに関連する高レベルの関数を提供する 沢山のPython パッケージ群に対して、堅固な基盤として利用されています。 これらのパッケージは、クリケットの試合だけでなくクリケットの試合周辺の推論やビジネスを推進しつつ、ゲームの結果を変えるような意思決定を支援するリアルタイムのインサイトを得るために広く利用されています。 クリケットの試合の結果につながる隠れたパラメータや、パターン、属性を見つけることは、ステークホルダーが数字や統計に隠されているゲームの洞察方法を見つけるのにも役に立つのです。
-{{< figure src="/images/content_images/cs/numpy_ca_benefits.png" class="fig-center" alt="Diagram showing benefits of using NumPy for cricket analytics" caption="**Key NumPy Capabilities utilized**" >}}
+{{< figure src="/images/content_images/cs/numpy_ca_benefits.png" class="fig-center" alt="クリケット分析にNumPyを使用するメリットを示す図" caption="** 利用されている主なNumPy機能 **" >}
From 44f486f2d3371871c96897f4fcbaf8a9fd9ca6dd Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 30 Jan 2021 08:57:37 +0000
Subject: [PATCH 135/909] New translations deeplabcut-dnn.md (Japanese)
---
content/ja/case-studies/deeplabcut-dnn.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/ja/case-studies/deeplabcut-dnn.md b/content/ja/case-studies/deeplabcut-dnn.md
index b40ed2af50..8f5e4fb0b4 100644
--- a/content/ja/case-studies/deeplabcut-dnn.md
+++ b/content/ja/case-studies/deeplabcut-dnn.md
@@ -1,5 +1,5 @@
---
-title: "Case Study: DeepLabCut 3D Pose Estimation"
+title: "ケーススタディ: DeepLabCut 三次元姿勢推定"
sidebar: false
---
From 1b5e2a3f8b744c00250139d4a2c8d67d122145d0 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sun, 31 Jan 2021 10:42:43 +0000
Subject: [PATCH 136/909] New translations news.md (Chinese Simplified)
---
content/zh/news.md | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/content/zh/news.md b/content/zh/news.md
index 5dcb849596..d45a2fbe06 100644
--- a/content/zh/news.md
+++ b/content/zh/news.md
@@ -3,6 +3,12 @@ title: News
sidebar: false
---
+### Numpy 1.20.0 release
+
+_Jan 30, 2021_ -- [NumPy 1.20.0](https://numpy.org/doc/stable/release/1.20.0-notes.html) is now available. This is the largest NumPy release to date, thanks to 180+ contributors. The two most exciting new features are:
+- Type annotations for large parts of NumPy, and a new `numpy.typing` submodule containing `ArrayLike` and `DtypeLike` aliases that users and downstream libraries can use when adding type annotations in their own code.
+- Multi-platform SIMD compiler optimizations, with support for x86 (SSE, AVX), ARM64 (Neon), and PowerPC (VSX) instructions. This yielded significant performance improvements for many functions (examples: [sin/cos](https://github.com/numpy/numpy/pull/17587), [einsum](https://github.com/numpy/numpy/pull/18194)).
+
### Diversity in the NumPy project
_Sep 20, 2020_ -- We wrote a [statement on the state of, and discussion on social media around, diversity and inclusion in the NumPy project](/diversity_sep2020).
@@ -22,7 +28,7 @@ _Sept 14, 2020_ -- Python 3.9 will be released in a few weeks. If you are an ear
### Numpy 1.19.2 release
-_Sept 10, 2020_ -- [NumPy 1.19.2](https://numpy.org/devdocs/release/1.19.2-notes.html) is now available. This latest release in the 1.19 series fixes several bugs, prepares for the [upcoming Cython 3.x release](http://docs.cython.org/en/latest/src/changes.html) and pins setuptools to keep distutils working while upstream modifications are ongoing. The aarch64 wheels are built with the latest manylinux2014 release that fixes the problem of differing page sizes used by different linux distros.
+_Sep 10, 2020_ -- [NumPy 1.19.2](https://numpy.org/devdocs/release/1.19.2-notes.html) is now available. This latest release in the 1.19 series fixes several bugs, prepares for the [upcoming Cython 3.x release](http://docs.cython.org/en/latest/src/changes.html) and pins setuptools to keep distutils working while upstream modifications are ongoing. The aarch64 wheels are built with the latest manylinux2014 release that fixes the problem of differing page sizes used by different linux distros.
### The inaugural NumPy survey is live!
From 3af463cde23d4531ca9c64c3a0a360da94e34a9f Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sun, 31 Jan 2021 10:43:07 +0000
Subject: [PATCH 137/909] New translations news.md (Arabic)
---
content/ar/news.md | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/content/ar/news.md b/content/ar/news.md
index 5dcb849596..d45a2fbe06 100644
--- a/content/ar/news.md
+++ b/content/ar/news.md
@@ -3,6 +3,12 @@ title: News
sidebar: false
---
+### Numpy 1.20.0 release
+
+_Jan 30, 2021_ -- [NumPy 1.20.0](https://numpy.org/doc/stable/release/1.20.0-notes.html) is now available. This is the largest NumPy release to date, thanks to 180+ contributors. The two most exciting new features are:
+- Type annotations for large parts of NumPy, and a new `numpy.typing` submodule containing `ArrayLike` and `DtypeLike` aliases that users and downstream libraries can use when adding type annotations in their own code.
+- Multi-platform SIMD compiler optimizations, with support for x86 (SSE, AVX), ARM64 (Neon), and PowerPC (VSX) instructions. This yielded significant performance improvements for many functions (examples: [sin/cos](https://github.com/numpy/numpy/pull/17587), [einsum](https://github.com/numpy/numpy/pull/18194)).
+
### Diversity in the NumPy project
_Sep 20, 2020_ -- We wrote a [statement on the state of, and discussion on social media around, diversity and inclusion in the NumPy project](/diversity_sep2020).
@@ -22,7 +28,7 @@ _Sept 14, 2020_ -- Python 3.9 will be released in a few weeks. If you are an ear
### Numpy 1.19.2 release
-_Sept 10, 2020_ -- [NumPy 1.19.2](https://numpy.org/devdocs/release/1.19.2-notes.html) is now available. This latest release in the 1.19 series fixes several bugs, prepares for the [upcoming Cython 3.x release](http://docs.cython.org/en/latest/src/changes.html) and pins setuptools to keep distutils working while upstream modifications are ongoing. The aarch64 wheels are built with the latest manylinux2014 release that fixes the problem of differing page sizes used by different linux distros.
+_Sep 10, 2020_ -- [NumPy 1.19.2](https://numpy.org/devdocs/release/1.19.2-notes.html) is now available. This latest release in the 1.19 series fixes several bugs, prepares for the [upcoming Cython 3.x release](http://docs.cython.org/en/latest/src/changes.html) and pins setuptools to keep distutils working while upstream modifications are ongoing. The aarch64 wheels are built with the latest manylinux2014 release that fixes the problem of differing page sizes used by different linux distros.
### The inaugural NumPy survey is live!
From 6c43fb9a2c80b6b501c38cfc48a5193353b0b83f Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sun, 31 Jan 2021 10:43:27 +0000
Subject: [PATCH 138/909] New translations news.md (Portuguese, Brazilian)
---
content/pt/news.md | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/content/pt/news.md b/content/pt/news.md
index d922c2e0e2..4e7060b82a 100644
--- a/content/pt/news.md
+++ b/content/pt/news.md
@@ -3,6 +3,12 @@ title: Notícias
sidebar: false
---
+### Numpy 1.20.0 release
+
+_Jan 30, 2021_ -- [NumPy 1.20.0](https://numpy.org/doc/stable/release/1.20.0-notes.html) is now available. This is the largest NumPy release to date, thanks to 180+ contributors. The two most exciting new features are:
+- Type annotations for large parts of NumPy, and a new `numpy.typing` submodule containing `ArrayLike` and `DtypeLike` aliases that users and downstream libraries can use when adding type annotations in their own code.
+- Multi-platform SIMD compiler optimizations, with support for x86 (SSE, AVX), ARM64 (Neon), and PowerPC (VSX) instructions. This yielded significant performance improvements for many functions (examples: [sin/cos](https://github.com/numpy/numpy/pull/17587), [einsum](https://github.com/numpy/numpy/pull/18194)).
+
### Diversity in the NumPy project
_Sep 20, 2020_ -- We wrote a [statement on the state of, and discussion on social media around, diversity and inclusion in the NumPy project](/diversity_sep2020).
@@ -22,7 +28,7 @@ _Sept 14, 2020_ -- Python 3.9 will be released in a few weeks. If you are an ear
### Numpy 1.19.2 release
-_Sept 10, 2020_ -- [NumPy 1.19.2](https://numpy.org/devdocs/release/1.19.2-notes.html) is now available. This latest release in the 1.19 series fixes several bugs, prepares for the [upcoming Cython 3.x release](http://docs.cython.org/en/latest/src/changes.html) and pins setuptools to keep distutils working while upstream modifications are ongoing. The aarch64 wheels are built with the latest manylinux2014 release that fixes the problem of differing page sizes used by different linux distros.
+_Sep 10, 2020_ -- [NumPy 1.19.2](https://numpy.org/devdocs/release/1.19.2-notes.html) is now available. This latest release in the 1.19 series fixes several bugs, prepares for the [upcoming Cython 3.x release](http://docs.cython.org/en/latest/src/changes.html) and pins setuptools to keep distutils working while upstream modifications are ongoing. The aarch64 wheels are built with the latest manylinux2014 release that fixes the problem of differing page sizes used by different linux distros.
### The inaugural NumPy survey is live!
From 5dbe92991b31fd114529484921c3bd64b83f8f8b Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sun, 31 Jan 2021 10:43:41 +0000
Subject: [PATCH 139/909] New translations news.md (Spanish)
---
content/es/news.md | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/content/es/news.md b/content/es/news.md
index 5dcb849596..d45a2fbe06 100644
--- a/content/es/news.md
+++ b/content/es/news.md
@@ -3,6 +3,12 @@ title: News
sidebar: false
---
+### Numpy 1.20.0 release
+
+_Jan 30, 2021_ -- [NumPy 1.20.0](https://numpy.org/doc/stable/release/1.20.0-notes.html) is now available. This is the largest NumPy release to date, thanks to 180+ contributors. The two most exciting new features are:
+- Type annotations for large parts of NumPy, and a new `numpy.typing` submodule containing `ArrayLike` and `DtypeLike` aliases that users and downstream libraries can use when adding type annotations in their own code.
+- Multi-platform SIMD compiler optimizations, with support for x86 (SSE, AVX), ARM64 (Neon), and PowerPC (VSX) instructions. This yielded significant performance improvements for many functions (examples: [sin/cos](https://github.com/numpy/numpy/pull/17587), [einsum](https://github.com/numpy/numpy/pull/18194)).
+
### Diversity in the NumPy project
_Sep 20, 2020_ -- We wrote a [statement on the state of, and discussion on social media around, diversity and inclusion in the NumPy project](/diversity_sep2020).
@@ -22,7 +28,7 @@ _Sept 14, 2020_ -- Python 3.9 will be released in a few weeks. If you are an ear
### Numpy 1.19.2 release
-_Sept 10, 2020_ -- [NumPy 1.19.2](https://numpy.org/devdocs/release/1.19.2-notes.html) is now available. This latest release in the 1.19 series fixes several bugs, prepares for the [upcoming Cython 3.x release](http://docs.cython.org/en/latest/src/changes.html) and pins setuptools to keep distutils working while upstream modifications are ongoing. The aarch64 wheels are built with the latest manylinux2014 release that fixes the problem of differing page sizes used by different linux distros.
+_Sep 10, 2020_ -- [NumPy 1.19.2](https://numpy.org/devdocs/release/1.19.2-notes.html) is now available. This latest release in the 1.19 series fixes several bugs, prepares for the [upcoming Cython 3.x release](http://docs.cython.org/en/latest/src/changes.html) and pins setuptools to keep distutils working while upstream modifications are ongoing. The aarch64 wheels are built with the latest manylinux2014 release that fixes the problem of differing page sizes used by different linux distros.
### The inaugural NumPy survey is live!
From df2192e43c3a65c73e10a687e608cf61e7e73de1 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sun, 31 Jan 2021 10:44:03 +0000
Subject: [PATCH 140/909] New translations news.md (Korean)
---
content/ko/news.md | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/content/ko/news.md b/content/ko/news.md
index 5dcb849596..d45a2fbe06 100644
--- a/content/ko/news.md
+++ b/content/ko/news.md
@@ -3,6 +3,12 @@ title: News
sidebar: false
---
+### Numpy 1.20.0 release
+
+_Jan 30, 2021_ -- [NumPy 1.20.0](https://numpy.org/doc/stable/release/1.20.0-notes.html) is now available. This is the largest NumPy release to date, thanks to 180+ contributors. The two most exciting new features are:
+- Type annotations for large parts of NumPy, and a new `numpy.typing` submodule containing `ArrayLike` and `DtypeLike` aliases that users and downstream libraries can use when adding type annotations in their own code.
+- Multi-platform SIMD compiler optimizations, with support for x86 (SSE, AVX), ARM64 (Neon), and PowerPC (VSX) instructions. This yielded significant performance improvements for many functions (examples: [sin/cos](https://github.com/numpy/numpy/pull/17587), [einsum](https://github.com/numpy/numpy/pull/18194)).
+
### Diversity in the NumPy project
_Sep 20, 2020_ -- We wrote a [statement on the state of, and discussion on social media around, diversity and inclusion in the NumPy project](/diversity_sep2020).
@@ -22,7 +28,7 @@ _Sept 14, 2020_ -- Python 3.9 will be released in a few weeks. If you are an ear
### Numpy 1.19.2 release
-_Sept 10, 2020_ -- [NumPy 1.19.2](https://numpy.org/devdocs/release/1.19.2-notes.html) is now available. This latest release in the 1.19 series fixes several bugs, prepares for the [upcoming Cython 3.x release](http://docs.cython.org/en/latest/src/changes.html) and pins setuptools to keep distutils working while upstream modifications are ongoing. The aarch64 wheels are built with the latest manylinux2014 release that fixes the problem of differing page sizes used by different linux distros.
+_Sep 10, 2020_ -- [NumPy 1.19.2](https://numpy.org/devdocs/release/1.19.2-notes.html) is now available. This latest release in the 1.19 series fixes several bugs, prepares for the [upcoming Cython 3.x release](http://docs.cython.org/en/latest/src/changes.html) and pins setuptools to keep distutils working while upstream modifications are ongoing. The aarch64 wheels are built with the latest manylinux2014 release that fixes the problem of differing page sizes used by different linux distros.
### The inaugural NumPy survey is live!
From 4f423f320ef313b2b904ce14f7aa0a848321331f Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sun, 31 Jan 2021 10:44:22 +0000
Subject: [PATCH 141/909] New translations news.md (Japanese)
---
content/ja/news.md | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/content/ja/news.md b/content/ja/news.md
index 5dcb849596..d45a2fbe06 100644
--- a/content/ja/news.md
+++ b/content/ja/news.md
@@ -3,6 +3,12 @@ title: News
sidebar: false
---
+### Numpy 1.20.0 release
+
+_Jan 30, 2021_ -- [NumPy 1.20.0](https://numpy.org/doc/stable/release/1.20.0-notes.html) is now available. This is the largest NumPy release to date, thanks to 180+ contributors. The two most exciting new features are:
+- Type annotations for large parts of NumPy, and a new `numpy.typing` submodule containing `ArrayLike` and `DtypeLike` aliases that users and downstream libraries can use when adding type annotations in their own code.
+- Multi-platform SIMD compiler optimizations, with support for x86 (SSE, AVX), ARM64 (Neon), and PowerPC (VSX) instructions. This yielded significant performance improvements for many functions (examples: [sin/cos](https://github.com/numpy/numpy/pull/17587), [einsum](https://github.com/numpy/numpy/pull/18194)).
+
### Diversity in the NumPy project
_Sep 20, 2020_ -- We wrote a [statement on the state of, and discussion on social media around, diversity and inclusion in the NumPy project](/diversity_sep2020).
@@ -22,7 +28,7 @@ _Sept 14, 2020_ -- Python 3.9 will be released in a few weeks. If you are an ear
### Numpy 1.19.2 release
-_Sept 10, 2020_ -- [NumPy 1.19.2](https://numpy.org/devdocs/release/1.19.2-notes.html) is now available. This latest release in the 1.19 series fixes several bugs, prepares for the [upcoming Cython 3.x release](http://docs.cython.org/en/latest/src/changes.html) and pins setuptools to keep distutils working while upstream modifications are ongoing. The aarch64 wheels are built with the latest manylinux2014 release that fixes the problem of differing page sizes used by different linux distros.
+_Sep 10, 2020_ -- [NumPy 1.19.2](https://numpy.org/devdocs/release/1.19.2-notes.html) is now available. This latest release in the 1.19 series fixes several bugs, prepares for the [upcoming Cython 3.x release](http://docs.cython.org/en/latest/src/changes.html) and pins setuptools to keep distutils working while upstream modifications are ongoing. The aarch64 wheels are built with the latest manylinux2014 release that fixes the problem of differing page sizes used by different linux distros.
### The inaugural NumPy survey is live!
From 775d42f5b87f8f08eb1ce80958d78415b40d296e Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Thu, 4 Feb 2021 18:56:33 +0000
Subject: [PATCH 142/909] New translations about.md (Portuguese, Brazilian)
---
content/pt/about.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/pt/about.md b/content/pt/about.md
index bb240c155e..d24405565f 100644
--- a/content/pt/about.md
+++ b/content/pt/about.md
@@ -5,7 +5,7 @@ sidebar: false
_Algumas informações sobre o projeto NumPy e a comunidade_
-NumPy é um projeto de código aberto visando habilitar a computação numérica com Python. Foi criado em 2005, com base no trabalho inicial das bibliotecas Numerical e Numarray. O NumPy sempre será um software 100% de código aberto, livre para que todos usem e disponibilizados sob os termos liberais da [licença BSD modificada](https://github.com/numpy/numpy/blob/master/LICENSE.txt).
+NumPy é um projeto de código aberto visando habilitar a computação numérica com Python. It was created in 2005, building on the early work of the Numeric and Numarray libraries. O NumPy sempre será um software 100% de código aberto, livre para que todos usem e disponibilizados sob os termos liberais da [licença BSD modificada](https://github.com/numpy/numpy/blob/master/LICENSE.txt).
O NumPy é desenvolvido no GitHub, através do consenso da comunidade NumPy e de uma comunidade científica em Python mais ampla. Para obter mais informações sobre nossa abordagem de governança, por favor, consulte nosso [Documento de Governança](https://www.numpy.org/devdocs/dev/governance/index.html).
From 39b58eaf03af61ad3b9ecf8fbd5e23e231b7f5a8 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Thu, 4 Feb 2021 18:57:01 +0000
Subject: [PATCH 143/909] New translations about.md (Chinese Simplified)
---
content/zh/about.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/zh/about.md b/content/zh/about.md
index cccadd7da0..116caa48c3 100644
--- a/content/zh/about.md
+++ b/content/zh/about.md
@@ -5,7 +5,7 @@ sidebar: false
_下面是 NumPy 项目和社区的一些信息:_
-NumPy 是一个使 Python 支持数值计算的开源项目, 它诞生于 2005 年,早期由 Numerical 和 Numarray 库发展而来。 NumPy 将始终保证项目完整开源,所有人都可以根据 [修改后的 BSD 条款](https://github.com/numpy/numpy/blob/master/LICENSE.txt) 免费对其进行使用和分发。
+NumPy 是一个使 Python 支持数值计算的开源项目, It was created in 2005, building on the early work of the Numeric and Numarray libraries. NumPy 将始终保证项目完整开源,所有人都可以根据 [修改后的 BSD 条款](https://github.com/numpy/numpy/blob/master/LICENSE.txt) 免费对其进行使用和分发。
经过 Numpy 和 Python 科学计算社区协商讨论,最终决定将 Numpy 在 GitHub 上开源。 想要了解更多与社区治理有关的信息,请参阅我们的[治理文件](https://www.numpy.org/devdocs/dev/governance/index.html)。
From ced92a2fb32d5324bb22b119a498dcbdb006290d Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Thu, 4 Feb 2021 18:57:27 +0000
Subject: [PATCH 144/909] New translations about.md (Arabic)
---
content/ar/about.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/ar/about.md b/content/ar/about.md
index df89bff1f5..1779f7531f 100644
--- a/content/ar/about.md
+++ b/content/ar/about.md
@@ -5,7 +5,7 @@ sidebar: false
_Some information about the NumPy project and community_
-NumPy is an open source project aiming to enable numerical computing with Python. It was created in 2005, building on the early work of the Numerical and Numarray libraries. NumPy will always be 100% open source software, free for all to use and released under the liberal terms of the [modified BSD license](https://github.com/numpy/numpy/blob/master/LICENSE.txt).
+NumPy is an open source project aiming to enable numerical computing with Python. It was created in 2005, building on the early work of the Numeric and Numarray libraries. NumPy will always be 100% open source software, free for all to use and released under the liberal terms of the [modified BSD license](https://github.com/numpy/numpy/blob/master/LICENSE.txt).
NumPy is developed in the open on GitHub, through the consensus of the NumPy and wider scientific Python community. For more information on our governance approach, please see our [Governance Document](https://www.numpy.org/devdocs/dev/governance/index.html).
From 12faa005e944adc05d82801770292dd85b46878c Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Thu, 4 Feb 2021 18:57:43 +0000
Subject: [PATCH 145/909] New translations about.md (Japanese)
---
content/ja/about.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/ja/about.md b/content/ja/about.md
index e13172f599..95a7507a54 100644
--- a/content/ja/about.md
+++ b/content/ja/about.md
@@ -5,7 +5,7 @@ sidebar: false
_このページでは、NumPyのプロジェクトとそれを支えるコミュニティについて説明します。_
-Numpy は Python を使った数値計算のためのオープンソースプロジェクトです。 Numpyは、Numerical and Numarrayライブラリの初期のコードを基に、2005年から開発がスタートしました。 NumPyは開発当初から100%オープンソースソフトウェアとして開発されてきました。[修正BSD ライセンス](https://github.com/numpy/numpy/blob/master/LICENSE.txt) の条項の下で、すべての人が利用可能です。
+Numpy は Python を使った数値計算のためのオープンソースプロジェクトです。 It was created in 2005, building on the early work of the Numeric and Numarray libraries. NumPyは開発当初から100%オープンソースソフトウェアとして開発されてきました。[修正BSD ライセンス](https://github.com/numpy/numpy/blob/master/LICENSE.txt) の条項の下で、すべての人が利用可能です。
Numpy は 、様々な科学Python コミュニティとのコンセンサスを得ながら、GitHub 上でオープンに開発されています。 Numpyのガバナンス方法の詳細については、 [Governance Document](https://www.numpy.org/devdocs/dev/governance/index.html) をご覧ください。
From 597d64b5108eb8d70a70a24d3f6309ce8070440b Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Thu, 4 Feb 2021 18:58:04 +0000
Subject: [PATCH 146/909] New translations about.md (Spanish)
---
content/es/about.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/es/about.md b/content/es/about.md
index df89bff1f5..1779f7531f 100644
--- a/content/es/about.md
+++ b/content/es/about.md
@@ -5,7 +5,7 @@ sidebar: false
_Some information about the NumPy project and community_
-NumPy is an open source project aiming to enable numerical computing with Python. It was created in 2005, building on the early work of the Numerical and Numarray libraries. NumPy will always be 100% open source software, free for all to use and released under the liberal terms of the [modified BSD license](https://github.com/numpy/numpy/blob/master/LICENSE.txt).
+NumPy is an open source project aiming to enable numerical computing with Python. It was created in 2005, building on the early work of the Numeric and Numarray libraries. NumPy will always be 100% open source software, free for all to use and released under the liberal terms of the [modified BSD license](https://github.com/numpy/numpy/blob/master/LICENSE.txt).
NumPy is developed in the open on GitHub, through the consensus of the NumPy and wider scientific Python community. For more information on our governance approach, please see our [Governance Document](https://www.numpy.org/devdocs/dev/governance/index.html).
From 2a72c7d1719232f2e595a2d4124e4eb7fcfe53c0 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Thu, 4 Feb 2021 18:58:28 +0000
Subject: [PATCH 147/909] New translations about.md (Korean)
---
content/ko/about.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/ko/about.md b/content/ko/about.md
index 2317add1fe..871d435f9a 100644
--- a/content/ko/about.md
+++ b/content/ko/about.md
@@ -5,7 +5,7 @@ sidebar: false
_NumPy 프로젝트와 커뮤니티에 대한 몇가지 정보_
-NumPy는 Python에서 Numerical Computing을 할 수 있도록 도와주는 오픈소스 프로젝트입니다. Numerical와 Numarray라는 라이브러리의 초기 작업을 기반으로 2005년에 만들어졌습니다. NumPy는 항상 100% 오픈소스 소프트웨어 일것이며, [수정된 BSD 라이센스](https://github.com/numpy/numpy/blob/master/LICENSE.txt)에 따라서 누구나 무료로 사용하고 배포할 수 있습니디.
+NumPy는 Python에서 Numerical Computing을 할 수 있도록 도와주는 오픈소스 프로젝트입니다. It was created in 2005, building on the early work of the Numeric and Numarray libraries. NumPy는 항상 100% 오픈소스 소프트웨어 일것이며, [수정된 BSD 라이센스](https://github.com/numpy/numpy/blob/master/LICENSE.txt)에 따라서 누구나 무료로 사용하고 배포할 수 있습니디.
NumPy는 광범위한 Scientific Python 커뮤니티의 협의를 통해 GitHub에서 공개적으로 개발되었습니다. 우리의 거버넌스 접근 방식에 대한 더 자세한 내용은 [거버넌스 문서](https://www.numpy.org/devdocs/dev/governance/index.html)를 참조해 주세요.
From 1df8ff9b8439076c061061c8af84fd97663aca19 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Fri, 5 Feb 2021 23:34:46 +0000
Subject: [PATCH 148/909] New translations deeplabcut-dnn.md (Japanese)
---
content/ja/case-studies/deeplabcut-dnn.md | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/content/ja/case-studies/deeplabcut-dnn.md b/content/ja/case-studies/deeplabcut-dnn.md
index 8f5e4fb0b4..39e80846d0 100644
--- a/content/ja/case-studies/deeplabcut-dnn.md
+++ b/content/ja/case-studies/deeplabcut-dnn.md
@@ -3,16 +3,16 @@ title: "ケーススタディ: DeepLabCut 三次元姿勢推定"
sidebar: false
---
-{{< figure src="/images/content_images/cs/mice-hand.gif" class="fig-center" caption="**Analyzing mice hand-movement using DeepLapCut**" alt="micehandanim" attr="*(Source: www.deeplabcut.org )*" attrlink="http://www.mousemotorlab.org/deeplabcut">}}
+{{< figure src="/images/content_images/cs/mice-hand.gif" class="fig-center" caption="**DeepLapCutを用いたマウスの手の動きの解析 **" alt="micehandanim" attr="*(Source: www.deeplabcut.org )*" attrlink="http://www.mousemotorlab.org/deeplabcut">}}
-
Open Source Software is accelerating Biomedicine. DeepLabCut enables automated video analysis of animal behavior using Deep Learning.
-## About DeepLabCut
+## DeepLabCut について
-[DeepLabCut](https://github.com/DeepLabCut/DeepLabCut) is an open source toolbox that empowers researchers at hundreds of institutions worldwide to track behaviour of laboratory animals, with very little training data, at human-level accuracy. With DeepLabCut technology, scientists can delve deeper into the scientific understanding of motor control and behavior across animal species and timescales.
+[DeepLabCut](https://github.com/DeepLabCut/DeepLabCut) は世界中の何百もの研究機関の研究者が、ごくわずかなトレーニングデータで、人間レベルの精度で実験動物の行動を追跡可能にするオープンソースのツールボックスです。 With DeepLabCut technology, scientists can delve deeper into the scientific understanding of motor control and behavior across animal species and timescales.
Several areas of research, including neuroscience, medicine, and biomechanics, use data from tracking animal movement. DeepLabCut helps in understanding what humans and other animals are doing by parsing actions that have been recorded on film. Using automation for laborious tasks of tagging and monitoring, along with deep neural network based data analysis, DeepLabCut makes scientific studies involving observing animals, such as primates, mice, fish, flies etc., much faster and more accurate.
From 85ca0b36717b220e5874c3c46fcc21f1624e6785 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 6 Feb 2021 00:41:56 +0000
Subject: [PATCH 149/909] New translations deeplabcut-dnn.md (Japanese)
---
content/ja/case-studies/deeplabcut-dnn.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/ja/case-studies/deeplabcut-dnn.md b/content/ja/case-studies/deeplabcut-dnn.md
index 39e80846d0..12dcd07ad9 100644
--- a/content/ja/case-studies/deeplabcut-dnn.md
+++ b/content/ja/case-studies/deeplabcut-dnn.md
@@ -12,7 +12,7 @@ sidebar: false
## DeepLabCut について
-[DeepLabCut](https://github.com/DeepLabCut/DeepLabCut) は世界中の何百もの研究機関の研究者が、ごくわずかなトレーニングデータで、人間レベルの精度で実験動物の行動を追跡可能にするオープンソースのツールボックスです。 With DeepLabCut technology, scientists can delve deeper into the scientific understanding of motor control and behavior across animal species and timescales.
+[DeepLabCut](https://github.com/DeepLabCut/DeepLabCut) は世界中の何百もの研究機関の研究者が、ごくわずかなトレーニングデータで、人間レベルの精度で実験動物の行動を追跡可能にするオープンソースのツールボックスです。 DeepLabCutの技術により、科学者は動物の種類と時系列のデータを元に、運動制御と行動に関する科学的な理解を深めることができるようになりました。
Several areas of research, including neuroscience, medicine, and biomechanics, use data from tracking animal movement. DeepLabCut helps in understanding what humans and other animals are doing by parsing actions that have been recorded on film. Using automation for laborious tasks of tagging and monitoring, along with deep neural network based data analysis, DeepLabCut makes scientific studies involving observing animals, such as primates, mice, fish, flies etc., much faster and more accurate.
From 03b49ec0ff323b892c440f97e5fae91fa72a58e4 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 6 Feb 2021 23:31:42 +0000
Subject: [PATCH 150/909] New translations deeplabcut-dnn.md (Japanese)
---
content/ja/case-studies/deeplabcut-dnn.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/ja/case-studies/deeplabcut-dnn.md b/content/ja/case-studies/deeplabcut-dnn.md
index 12dcd07ad9..699042bff1 100644
--- a/content/ja/case-studies/deeplabcut-dnn.md
+++ b/content/ja/case-studies/deeplabcut-dnn.md
@@ -14,7 +14,7 @@ sidebar: false
[DeepLabCut](https://github.com/DeepLabCut/DeepLabCut) は世界中の何百もの研究機関の研究者が、ごくわずかなトレーニングデータで、人間レベルの精度で実験動物の行動を追跡可能にするオープンソースのツールボックスです。 DeepLabCutの技術により、科学者は動物の種類と時系列のデータを元に、運動制御と行動に関する科学的な理解を深めることができるようになりました。
-Several areas of research, including neuroscience, medicine, and biomechanics, use data from tracking animal movement. DeepLabCut helps in understanding what humans and other animals are doing by parsing actions that have been recorded on film. Using automation for laborious tasks of tagging and monitoring, along with deep neural network based data analysis, DeepLabCut makes scientific studies involving observing animals, such as primates, mice, fish, flies etc., much faster and more accurate.
+神経科学、医学、生体力学などのいくつかの研究分野では、動物の動きを追跡したデータを使用しています。 DeepLabCut は、動画に記録された動きを解析することで、人間やその他の動物が何をしているのかを理解することができます。 タグ付けや監視などの、手間のかかる作業に自動化を利用し、深層学習ベースのデータ解析を実施します。DeepLabCut は、霊長類、マウス、魚、ハエなどの動物を観察する科学的研究に利用されており、より速く、正確な結果をもたらしました。
{{< figure src="/images/content_images/cs/race-horse.gif" class="fig-center" caption="**Colored dots track the positions of a racehorse’s body part**" alt="horserideranim" attr="*(Source: Mackenzie Mathis)*">}}
From 677163f0f1a8a6884affc77184400e5bd05af41b Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sun, 7 Feb 2021 00:31:53 +0000
Subject: [PATCH 151/909] New translations deeplabcut-dnn.md (Japanese)
---
content/ja/case-studies/deeplabcut-dnn.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/content/ja/case-studies/deeplabcut-dnn.md b/content/ja/case-studies/deeplabcut-dnn.md
index 699042bff1..d4cd731a3e 100644
--- a/content/ja/case-studies/deeplabcut-dnn.md
+++ b/content/ja/case-studies/deeplabcut-dnn.md
@@ -16,9 +16,9 @@ sidebar: false
神経科学、医学、生体力学などのいくつかの研究分野では、動物の動きを追跡したデータを使用しています。 DeepLabCut は、動画に記録された動きを解析することで、人間やその他の動物が何をしているのかを理解することができます。 タグ付けや監視などの、手間のかかる作業に自動化を利用し、深層学習ベースのデータ解析を実施します。DeepLabCut は、霊長類、マウス、魚、ハエなどの動物を観察する科学的研究に利用されており、より速く、正確な結果をもたらしました。
-{{< figure src="/images/content_images/cs/race-horse.gif" class="fig-center" caption="**Colored dots track the positions of a racehorse’s body part**" alt="horserideranim" attr="*(Source: Mackenzie Mathis)*">}}
+{{< figure src="/images/content_images/cs/race-hore. if" class="fig-center" caption="**色のついた点は競走馬の体の位置を追跡**" alt="horserideranim" attr="*(Source: Mackenzie Mathis)*">}}
-DeepLabCut's non-invasive behavioral tracking of animals by extracting the poses of animals is crucial for scientific pursuits in domains such as biomechanics, genetics, ethology & neuroscience. Measuring animal poses non-invasively from video - without markers - in dynamically changing backgrounds is computationally challenging, both technically as well as in terms of resource needs and training data required.
+DeepLabCutによる動物の姿勢を抽出することによる、非侵襲的な行動追跡は、生体力学や、遺伝学、倫理学、神経科学などの分野における科学的な研究に必要不可欠です。 動的に変化する背景の中で、動物の姿勢をビデオデータから非侵襲的に測定することは、計算処理的に非常に困難です。 例えば、必要な計算リソースやトレーニングデータが問題になります。
DeepLabCut allows researchers to estimate the pose of the subject, efficiently enabling them to quantify the behavior through a Python based software toolkit. With DeepLabCut, researchers can identify distinct frames from videos, digitally label specific body parts in a few dozen frames with a tailored GUI, and then the deep learning based pose estimation architectures in DeepLabCut learn how to pick out those same features in the rest of the video and in other similar videos of animals. It works across species of animals, from common laboratory animals such as flies and mice to more unusual animals like [cheetahs][cheetah-movement].
From a08cea9d648ce2ce1fcc8348d8b9b63ef0c7001a Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Fri, 12 Feb 2021 23:37:00 +0000
Subject: [PATCH 152/909] New translations deeplabcut-dnn.md (Japanese)
---
content/ja/case-studies/deeplabcut-dnn.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/ja/case-studies/deeplabcut-dnn.md b/content/ja/case-studies/deeplabcut-dnn.md
index d4cd731a3e..74a585a8cc 100644
--- a/content/ja/case-studies/deeplabcut-dnn.md
+++ b/content/ja/case-studies/deeplabcut-dnn.md
@@ -20,7 +20,7 @@ sidebar: false
DeepLabCutによる動物の姿勢を抽出することによる、非侵襲的な行動追跡は、生体力学や、遺伝学、倫理学、神経科学などの分野における科学的な研究に必要不可欠です。 動的に変化する背景の中で、動物の姿勢をビデオデータから非侵襲的に測定することは、計算処理的に非常に困難です。 例えば、必要な計算リソースやトレーニングデータが問題になります。
-DeepLabCut allows researchers to estimate the pose of the subject, efficiently enabling them to quantify the behavior through a Python based software toolkit. With DeepLabCut, researchers can identify distinct frames from videos, digitally label specific body parts in a few dozen frames with a tailored GUI, and then the deep learning based pose estimation architectures in DeepLabCut learn how to pick out those same features in the rest of the video and in other similar videos of animals. It works across species of animals, from common laboratory animals such as flies and mice to more unusual animals like [cheetahs][cheetah-movement].
+DeepLabCutは、研究者が対象の姿勢をを推定することができ、Pythonベースのソフトウェアを使って効率的に対象の行動を定量化することを可能にします。 With DeepLabCut, researchers can identify distinct frames from videos, digitally label specific body parts in a few dozen frames with a tailored GUI, and then the deep learning based pose estimation architectures in DeepLabCut learn how to pick out those same features in the rest of the video and in other similar videos of animals. It works across species of animals, from common laboratory animals such as flies and mice to more unusual animals like [cheetahs][cheetah-movement].
DeepLabCut uses a principle called [transfer learning](https://arxiv.org/pdf/1909.11229), which greatly reduces the amount of training data required and speeds up the convergence of the training period. Depending on the needs, users can pick different network architectures that provide faster inference (e.g. MobileNetV2), which can also be combined with real-time experimental feedback. DeepLabCut originally used the feature detectors from a top-performing human pose estimation architecture, called [DeeperCut](https://arxiv.org/abs/1605.03170), which inspired the name. The package now has been significantly changed to include additional architectures, augmentation methods, and a full front-end user experience. Furthermore, to support large-scale biological experiments DeepLabCut provides active learning capabilities so that users can increase the training set over time to cover edge cases and make their pose estimation algorithm robust within the specific context.
From af192c0f0691c872e1cf1cd9782e972429af0832 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 13 Feb 2021 00:37:28 +0000
Subject: [PATCH 153/909] New translations deeplabcut-dnn.md (Japanese)
---
content/ja/case-studies/deeplabcut-dnn.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/content/ja/case-studies/deeplabcut-dnn.md b/content/ja/case-studies/deeplabcut-dnn.md
index 74a585a8cc..badecebde8 100644
--- a/content/ja/case-studies/deeplabcut-dnn.md
+++ b/content/ja/case-studies/deeplabcut-dnn.md
@@ -20,9 +20,9 @@ sidebar: false
DeepLabCutによる動物の姿勢を抽出することによる、非侵襲的な行動追跡は、生体力学や、遺伝学、倫理学、神経科学などの分野における科学的な研究に必要不可欠です。 動的に変化する背景の中で、動物の姿勢をビデオデータから非侵襲的に測定することは、計算処理的に非常に困難です。 例えば、必要な計算リソースやトレーニングデータが問題になります。
-DeepLabCutは、研究者が対象の姿勢をを推定することができ、Pythonベースのソフトウェアを使って効率的に対象の行動を定量化することを可能にします。 With DeepLabCut, researchers can identify distinct frames from videos, digitally label specific body parts in a few dozen frames with a tailored GUI, and then the deep learning based pose estimation architectures in DeepLabCut learn how to pick out those same features in the rest of the video and in other similar videos of animals. It works across species of animals, from common laboratory animals such as flies and mice to more unusual animals like [cheetahs][cheetah-movement].
+DeepLabCutは、研究者が対象の姿勢をを推定することができ、Pythonベースのソフトウェアを使って効率的に対象の行動を定量化することを可能にします。 DeepLabCutを使用すると、研究者は動画から異なるフレームを識別し、数十個のフレームの特定の身体部位にデジタルなラベルを貼ることができます。また、DeepLabCutのディープラーニングベースのポーズ推定アーキテクチャが、動画の残りの部分や動物の他の類似した動画から同じ特徴を抽出する方法を学習することもできます。 ハエやマウスなどの一般的な実験動物から [チーター][cheetah-movement]のようなより珍しい動物まで、動物の種類を問わず利用する事ができます。
-DeepLabCut uses a principle called [transfer learning](https://arxiv.org/pdf/1909.11229), which greatly reduces the amount of training data required and speeds up the convergence of the training period. Depending on the needs, users can pick different network architectures that provide faster inference (e.g. MobileNetV2), which can also be combined with real-time experimental feedback. DeepLabCut originally used the feature detectors from a top-performing human pose estimation architecture, called [DeeperCut](https://arxiv.org/abs/1605.03170), which inspired the name. The package now has been significantly changed to include additional architectures, augmentation methods, and a full front-end user experience. Furthermore, to support large-scale biological experiments DeepLabCut provides active learning capabilities so that users can increase the training set over time to cover edge cases and make their pose estimation algorithm robust within the specific context.
+DeepLabCut では [transfer learning](https://arxiv.org/pdf/1909.11229)という技術を使用しています。これにより必要な学習データの量を大幅に削減し、学習の収束を加速させることができます。 必要に応じて、より高速な推論を提供するさまざまなネットワークアーキテクチャ(MobileNetV2など)を選択することができ、リアルタイムの実験データフィードバックと組み合わせることもできます。 DeepLabCutはもともと、ツールの名前の元となった [DeeperCut](https://arxiv.org/abs/1605.03170)と呼ばれる、パフォーマンスの高い人像推定アーキテクチャからの特徴検出器を使用しています。 その過程で、このパッケージには、追加のアーキテクチャや、拡張メソッド、および一通りのフロントエンドユーザエクスペリエンスが得られるように大幅に変更されました。 Furthermore, to support large-scale biological experiments DeepLabCut provides active learning capabilities so that users can increase the training set over time to cover edge cases and make their pose estimation algorithm robust within the specific context.
Recently, the [DeepLabCut model zoo](http://www.mousemotorlab.org/dlc-modelzoo) was introduced, which provides pre-trained models for various species and experimental conditions from facial analysis in primates to dog posture. This can be run for instance in the cloud without any labeling of new data, or neural network training, and no programming experience is necessary.
From 7c18b005d36c8d95f07fefc8cbc7cbf069b150c4 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 13 Feb 2021 23:31:47 +0000
Subject: [PATCH 154/909] New translations deeplabcut-dnn.md (Japanese)
---
content/ja/case-studies/deeplabcut-dnn.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/ja/case-studies/deeplabcut-dnn.md b/content/ja/case-studies/deeplabcut-dnn.md
index badecebde8..a58ee2c0ab 100644
--- a/content/ja/case-studies/deeplabcut-dnn.md
+++ b/content/ja/case-studies/deeplabcut-dnn.md
@@ -22,7 +22,7 @@ DeepLabCutによる動物の姿勢を抽出することによる、非侵襲的
DeepLabCutは、研究者が対象の姿勢をを推定することができ、Pythonベースのソフトウェアを使って効率的に対象の行動を定量化することを可能にします。 DeepLabCutを使用すると、研究者は動画から異なるフレームを識別し、数十個のフレームの特定の身体部位にデジタルなラベルを貼ることができます。また、DeepLabCutのディープラーニングベースのポーズ推定アーキテクチャが、動画の残りの部分や動物の他の類似した動画から同じ特徴を抽出する方法を学習することもできます。 ハエやマウスなどの一般的な実験動物から [チーター][cheetah-movement]のようなより珍しい動物まで、動物の種類を問わず利用する事ができます。
-DeepLabCut では [transfer learning](https://arxiv.org/pdf/1909.11229)という技術を使用しています。これにより必要な学習データの量を大幅に削減し、学習の収束を加速させることができます。 必要に応じて、より高速な推論を提供するさまざまなネットワークアーキテクチャ(MobileNetV2など)を選択することができ、リアルタイムの実験データフィードバックと組み合わせることもできます。 DeepLabCutはもともと、ツールの名前の元となった [DeeperCut](https://arxiv.org/abs/1605.03170)と呼ばれる、パフォーマンスの高い人像推定アーキテクチャからの特徴検出器を使用しています。 その過程で、このパッケージには、追加のアーキテクチャや、拡張メソッド、および一通りのフロントエンドユーザエクスペリエンスが得られるように大幅に変更されました。 Furthermore, to support large-scale biological experiments DeepLabCut provides active learning capabilities so that users can increase the training set over time to cover edge cases and make their pose estimation algorithm robust within the specific context.
+DeepLabCut では [transfer learning](https://arxiv.org/pdf/1909.11229)という技術を使用しています。これにより必要な学習データの量を大幅に削減し、学習の収束を加速させることができます。 必要に応じて、より高速な推論を提供するさまざまなネットワークアーキテクチャ(MobileNetV2など)を選択することができ、リアルタイムの実験データフィードバックと組み合わせることもできます。 DeepLabCutはもともと、ツールの名前の元となった [DeeperCut](https://arxiv.org/abs/1605.03170)と呼ばれる、パフォーマンスの高い人像推定アーキテクチャからの特徴検出器を使用しています。 その過程で、このパッケージには、追加のアーキテクチャや、拡張メソッド、および一通りのフロントエンドユーザエクスペリエンスが得られるように大幅に変更されました。 さらに、 大規模な生物学的実験をサポートするために DeepLabCut はアクティブな学習機能を提供しています。例えば、エッジケースをカバーしたり、特定のコンテキスト内でポーズ推定アルゴリズムを堅牢にするために、時間経過しても学習データを増やすことができます。
Recently, the [DeepLabCut model zoo](http://www.mousemotorlab.org/dlc-modelzoo) was introduced, which provides pre-trained models for various species and experimental conditions from facial analysis in primates to dog posture. This can be run for instance in the cloud without any labeling of new data, or neural network training, and no programming experience is necessary.
From 6c0e3a88b642ce35e34360cddf16f061f56a6742 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sun, 14 Feb 2021 00:33:14 +0000
Subject: [PATCH 155/909] New translations deeplabcut-dnn.md (Japanese)
---
content/ja/case-studies/deeplabcut-dnn.md | 28 +++++++++++------------
1 file changed, 14 insertions(+), 14 deletions(-)
diff --git a/content/ja/case-studies/deeplabcut-dnn.md b/content/ja/case-studies/deeplabcut-dnn.md
index a58ee2c0ab..a9f74cbdb2 100644
--- a/content/ja/case-studies/deeplabcut-dnn.md
+++ b/content/ja/case-studies/deeplabcut-dnn.md
@@ -24,30 +24,30 @@ DeepLabCutは、研究者が対象の姿勢をを推定することができ、P
DeepLabCut では [transfer learning](https://arxiv.org/pdf/1909.11229)という技術を使用しています。これにより必要な学習データの量を大幅に削減し、学習の収束を加速させることができます。 必要に応じて、より高速な推論を提供するさまざまなネットワークアーキテクチャ(MobileNetV2など)を選択することができ、リアルタイムの実験データフィードバックと組み合わせることもできます。 DeepLabCutはもともと、ツールの名前の元となった [DeeperCut](https://arxiv.org/abs/1605.03170)と呼ばれる、パフォーマンスの高い人像推定アーキテクチャからの特徴検出器を使用しています。 その過程で、このパッケージには、追加のアーキテクチャや、拡張メソッド、および一通りのフロントエンドユーザエクスペリエンスが得られるように大幅に変更されました。 さらに、 大規模な生物学的実験をサポートするために DeepLabCut はアクティブな学習機能を提供しています。例えば、エッジケースをカバーしたり、特定のコンテキスト内でポーズ推定アルゴリズムを堅牢にするために、時間経過しても学習データを増やすことができます。
-Recently, the [DeepLabCut model zoo](http://www.mousemotorlab.org/dlc-modelzoo) was introduced, which provides pre-trained models for various species and experimental conditions from facial analysis in primates to dog posture. This can be run for instance in the cloud without any labeling of new data, or neural network training, and no programming experience is necessary.
+最近、[DeepLabCut model zoo](http://www.mousemotorlab.org/dlc-modelzoo)が発表されました。これは、霊長類の顔分析から犬の姿勢まで、様々な種や実験条件に対応した事前訓練済みモデルを提供しています。 これにより、例えば、新しいデータのラベルを付けることなくクラウドで予測を実行することができたり、ニューラルネットワーク学習を実行することができます。また、プログラミング経験は必要ありません。
-### Key Goals and Results
+### 主な目標と結果
-* **Automation of animal pose analysis for scientific studies:**
+* **科学研究のための動物姿勢解析の自動化:**
- The primary objective of DeepLabCut technology is to measure and track posture of animals in a diverse settings. This data can be used, for example, in neuroscience studies to understand how the brain controls movement, or to elucidate how animals socially interact. Researchers have observed a [tenfold performance boost](https://www.biorxiv.org/content/10.1101/457242v1) with DeepLabCut. Poses can be inferred offline at up to 1200 frames per second (FPS).
+ DeepLabCut 技術の主な目的は、多様な環境で動物の姿勢を測定し追跡することです。 このデータは、例えば、脳がどのように運動を制御しているかを理解するための神経科学の研究や、動物がどのように社会的に交流しているかを明らかにするために利用することができます。 研究者はDeepLabCutで [10倍のパフォーマンス向上](https://www.biorxiv.org/content/10.1101/457242v1) が可能であると発表しています。 オフラインでは最大1200フレーム/秒(FPS) で姿勢推定することができます。
-* **Creation of an easy-to-use Python toolkit for pose estimation:**
+* **姿勢推定のための使いやすいPythonツールキットの作成:**
- DeepLabCut wanted to share their animal pose-estimation technology in the form of an easy to use tool that can be adopted by researchers easily. So they have created a complete, easy-to-use Python toolbox with project management features as well. These enable not only automation of pose-estimation but also managing the project end-to-end by helping the DeepLabCut Toolkit user right from the dataset collection stage to creating shareable and reusable analysis pipelines.
+ DeepLabCutは、動物の姿勢推定技術を研究者が簡単に利用できるツールとして共有したいという考えから開発されています。 そこでらはプロジェクト管理機能 を備えた、単独で機能し、使いやすいPythonツールボックスとしてこのツールを作成しました。 これにより、姿勢推定の自動化だけでなく、 データセット収集段階から共有可能て、再利用可能な分析パイプラインを作成するDeepLabCut Toolkitを提供し、プロジェクトのエンドツーエンドの管理も可能になりました。
- Their [toolkit][DLCToolkit] is now available as open source.
+ この[ツールキット][DLCToolkit] はオープンソースとして利用できます。
- A typical DeepLabCut Workflow includes:
+ DeepLabCut ワークフローは以下のようになります。
- - creation and refining of training sets via active learning
- - creation of tailored neural networks for specific animals and scenarios
- - code for large-scale inference on videos
- - draw inferences using integrated visualization tools
+ - アクティブ学習によるトレーニングセットの作成と調整を行います
+ - 特定の動物やシナリオに合わせたニューラルネットワークの構築
+ - 動画における大規模推論のためのコード作成
+ - 統合された可視化ツールを使用して推論の描画
-{{< figure src="/images/content_images/cs/deeplabcut-toolkit-steps.png" class="csfigcaption" caption="**Pose estimation steps with DeepLabCut**" alt="dlcsteps" align="middle" attr="(Source: DeepLabCut)" attrlink="https://twitter.com/DeepLabCut/status/1198046918284210176/photo/1" >}}
+{{< figure src="/images/content_images/cs/deeplabcut-toolkit-steps.png" class="csfigcaption" caption="**DeepLabCutによる姿勢推定のステップ**" alt="dlcsteps" align="middle" attr="(Source: DeepLabCut)" attrlink="https://twitter.com/DeepLabCut/status/1198046918284210176/photo/1" >}}
-### The Challenges
+### 課題
* **Speed**
From cab2a9db7578d8bfaccfe2416ad8fea8ffaaaa64 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Thu, 18 Feb 2021 11:10:18 +0000
Subject: [PATCH 156/909] New translations learn.md (Spanish)
---
content/es/learn.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/es/learn.md b/content/es/learn.md
index 264677ac48..4611d3a402 100644
--- a/content/es/learn.md
+++ b/content/es/learn.md
@@ -3,7 +3,7 @@ title: Learn
sidebar: false
---
-**The official NumPy documentation lives [here](https://numpy.org/doc/stable).**
+For the **official NumPy documentation** visit [numpy.org/doc/stable](https://numpy.org/doc/stable).
Below is a curated collection of external resources. To contribute, see the [end of this page](#add-to-this-list).
***
From 8d16150a813e11116d0358237abf553321b476a0 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Thu, 18 Feb 2021 11:10:19 +0000
Subject: [PATCH 157/909] New translations learn.md (Portuguese, Brazilian)
---
content/pt/learn.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/pt/learn.md b/content/pt/learn.md
index 66ef85cc38..4f339d762f 100644
--- a/content/pt/learn.md
+++ b/content/pt/learn.md
@@ -3,7 +3,7 @@ title: Aprenda
sidebar: false
---
-**A documentação oficial do NumPy mora [aqui](https://numpy.org/doc/stable).**
+For the **official NumPy documentation** visit [numpy.org/doc/stable](https://numpy.org/doc/stable).
Abaixo está uma coleção de recursos externos selecionados. Para contribuir, veja o [fim desta página](#add-to-this-list).
***
From 8f7fb31bd74eb6854167b6f7d8a79f7a70b344db Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Thu, 18 Feb 2021 11:11:01 +0000
Subject: [PATCH 158/909] New translations learn.md (Arabic)
---
content/ar/learn.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/ar/learn.md b/content/ar/learn.md
index 264677ac48..4611d3a402 100644
--- a/content/ar/learn.md
+++ b/content/ar/learn.md
@@ -3,7 +3,7 @@ title: Learn
sidebar: false
---
-**The official NumPy documentation lives [here](https://numpy.org/doc/stable).**
+For the **official NumPy documentation** visit [numpy.org/doc/stable](https://numpy.org/doc/stable).
Below is a curated collection of external resources. To contribute, see the [end of this page](#add-to-this-list).
***
From c421d99203ff6805bfc8f9318a4f450d5e8a6ae3 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Thu, 18 Feb 2021 11:11:31 +0000
Subject: [PATCH 159/909] New translations learn.md (Japanese)
---
content/ja/learn.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/ja/learn.md b/content/ja/learn.md
index 264677ac48..4611d3a402 100644
--- a/content/ja/learn.md
+++ b/content/ja/learn.md
@@ -3,7 +3,7 @@ title: Learn
sidebar: false
---
-**The official NumPy documentation lives [here](https://numpy.org/doc/stable).**
+For the **official NumPy documentation** visit [numpy.org/doc/stable](https://numpy.org/doc/stable).
Below is a curated collection of external resources. To contribute, see the [end of this page](#add-to-this-list).
***
From 0d0250d2d0afc7c39344f6fb00abdaa34009e196 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Thu, 18 Feb 2021 11:11:44 +0000
Subject: [PATCH 160/909] New translations learn.md (Chinese Simplified)
---
content/zh/learn.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/zh/learn.md b/content/zh/learn.md
index 264677ac48..4611d3a402 100644
--- a/content/zh/learn.md
+++ b/content/zh/learn.md
@@ -3,7 +3,7 @@ title: Learn
sidebar: false
---
-**The official NumPy documentation lives [here](https://numpy.org/doc/stable).**
+For the **official NumPy documentation** visit [numpy.org/doc/stable](https://numpy.org/doc/stable).
Below is a curated collection of external resources. To contribute, see the [end of this page](#add-to-this-list).
***
From 2ceb7ded958f8d5e395c4c0cb75ea8493ebe8342 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Thu, 18 Feb 2021 11:12:06 +0000
Subject: [PATCH 161/909] New translations learn.md (Korean)
---
content/ko/learn.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/ko/learn.md b/content/ko/learn.md
index 87d12db866..04e49d32d6 100644
--- a/content/ko/learn.md
+++ b/content/ko/learn.md
@@ -3,7 +3,7 @@ title: Learn
sidebar: false
---
-**공식 NumPy 문서는 [여기](https://numpy.org/doc/stable)에 있습니다.**
+For the **official NumPy documentation** visit [numpy.org/doc/stable](https://numpy.org/doc/stable).
아래는 선별된 외부 자료들의 모음입니다. 이곳에 기여하고 싶다면, [이 페이지의 끝](#add-to-this-list)을 참조하세요.
***
From 0960474fc16b998c4ca5b7d8e19f484ef67e892e Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Thu, 18 Feb 2021 23:34:52 +0000
Subject: [PATCH 162/909] New translations deeplabcut-dnn.md (Japanese)
---
content/ja/case-studies/deeplabcut-dnn.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/ja/case-studies/deeplabcut-dnn.md b/content/ja/case-studies/deeplabcut-dnn.md
index a9f74cbdb2..de8c976893 100644
--- a/content/ja/case-studies/deeplabcut-dnn.md
+++ b/content/ja/case-studies/deeplabcut-dnn.md
@@ -49,7 +49,7 @@ DeepLabCut では [transfer learning](https://arxiv.org/pdf/1909.11229)という
### 課題
-* **Speed**
+* **速度**
Fast processing of animal behavior videos in order to measure their behavior and at the same time make scientific experiments more efficient, accurate. Extracting detailed animal poses for laboratory experiments, without markers, in dynamically changing backgrounds, can be challenging, both technically as well as in terms of resource needs and training data required. Coming up with a tool that is easy to use without the need for skills such as computer vision expertise that enables scientists to do research in more real-world contexts, is a non-trivial problem to solve.
From ef2bd76601bf4b55de08e2ea7411f7476ce81935 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Fri, 19 Feb 2021 00:32:53 +0000
Subject: [PATCH 163/909] New translations deeplabcut-dnn.md (Japanese)
---
content/ja/case-studies/deeplabcut-dnn.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/ja/case-studies/deeplabcut-dnn.md b/content/ja/case-studies/deeplabcut-dnn.md
index de8c976893..cfc7ed1cf8 100644
--- a/content/ja/case-studies/deeplabcut-dnn.md
+++ b/content/ja/case-studies/deeplabcut-dnn.md
@@ -51,7 +51,7 @@ DeepLabCut では [transfer learning](https://arxiv.org/pdf/1909.11229)という
* **速度**
- Fast processing of animal behavior videos in order to measure their behavior and at the same time make scientific experiments more efficient, accurate. Extracting detailed animal poses for laboratory experiments, without markers, in dynamically changing backgrounds, can be challenging, both technically as well as in terms of resource needs and training data required. Coming up with a tool that is easy to use without the need for skills such as computer vision expertise that enables scientists to do research in more real-world contexts, is a non-trivial problem to solve.
+ 動物行動動画の高速処理は、彼らの行動を測定し、同時に科学実験をより効率的で正確にするために重要です。 動的に変化する背景の中で、マーカーを使用せずに、実験室での実験のために動物の詳細な姿勢を抽出することは、技術的にも、必要なリソース的にも、必要なトレーニングデータの面でも、困難な場合があります。 Coming up with a tool that is easy to use without the need for skills such as computer vision expertise that enables scientists to do research in more real-world contexts, is a non-trivial problem to solve.
* **Combinatorics**
From 67e88e991d9558d1f578d3d0ae7bbee70adbcbc7 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Fri, 19 Feb 2021 08:46:46 +0000
Subject: [PATCH 164/909] New translations deeplabcut-dnn.md (Japanese)
---
content/ja/case-studies/deeplabcut-dnn.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/content/ja/case-studies/deeplabcut-dnn.md b/content/ja/case-studies/deeplabcut-dnn.md
index cfc7ed1cf8..0157360e15 100644
--- a/content/ja/case-studies/deeplabcut-dnn.md
+++ b/content/ja/case-studies/deeplabcut-dnn.md
@@ -51,13 +51,13 @@ DeepLabCut では [transfer learning](https://arxiv.org/pdf/1909.11229)という
* **速度**
- 動物行動動画の高速処理は、彼らの行動を測定し、同時に科学実験をより効率的で正確にするために重要です。 動的に変化する背景の中で、マーカーを使用せずに、実験室での実験のために動物の詳細な姿勢を抽出することは、技術的にも、必要なリソース的にも、必要なトレーニングデータの面でも、困難な場合があります。 Coming up with a tool that is easy to use without the need for skills such as computer vision expertise that enables scientists to do research in more real-world contexts, is a non-trivial problem to solve.
+ 動物行動動画の高速処理は、彼らの行動を測定し、同時に科学実験をより効率的で正確にするために重要です。 動的に変化する背景の中で、マーカーを使用せずに、実験室での実験のために動物の詳細な姿勢を抽出することは、技術的にも、必要なリソース的にも、必要なトレーニングデータの面でも、困難な場合があります。 科学者が、より現実的な状況で研究を行うために、コンピュータビジョンなどの専門知識のスキルを必要とせずに使うことができるツールを開発することは、解決すべき重要な問題です。
-* **Combinatorics**
+* **組み合わせ問題**
- Combinatorics involves assembly and integration of movement of multiple limbs into individual animal behavior. Assembling keypoints and their connections into individual animal movements and linking them across time is a complex process that requires heavy-duty numerical analysis, especially in case of multi-animal movement tracking in experiment videos.
+ 組合せ問題とは、複数の四肢の動きを個々の動物行動に統合することを指します。 キーポイントとそ個々の動物の動きを関連性に基づき組み合わせ、それらを時間的に結びつけることは、複雑なプロセスであり、特に実験映像の中で複数の動物の動きを追跡する場合には、非常に膨大な数値解析が必要となります。
-* **Data Processing**
+* **データ処理**
Last but not the least, array manipulation - processing large stacks of arrays corresponding to various images, target tensors and keypoints is fairly challenging.
From 72b789d7c5df976fbf932bea3f5f02cf7e08615e Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Fri, 19 Feb 2021 10:02:14 +0000
Subject: [PATCH 165/909] New translations deeplabcut-dnn.md (Japanese)
---
content/ja/case-studies/deeplabcut-dnn.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/content/ja/case-studies/deeplabcut-dnn.md b/content/ja/case-studies/deeplabcut-dnn.md
index 0157360e15..f978ebddcb 100644
--- a/content/ja/case-studies/deeplabcut-dnn.md
+++ b/content/ja/case-studies/deeplabcut-dnn.md
@@ -59,11 +59,11 @@ DeepLabCut では [transfer learning](https://arxiv.org/pdf/1909.11229)という
* **データ処理**
- Last but not the least, array manipulation - processing large stacks of arrays corresponding to various images, target tensors and keypoints is fairly challenging.
+ 最後に、配列の操作、 様々な画像処理、目標のテンソル処理、キーポイントに対応する大きな配列のスタックを処理することは、かなり難しい問題です。
-{{< figure src="/images/content_images/cs/pose-estimation.png" class="csfigcaption" caption="**Pose estimation variety and complexity**" alt="challengesfig" align="middle" attr="(Source: Mackenzie Mathis)" attrlink="https://www.biorxiv.org/content/10.1101/476531v1.full.pdf" >}}
+{{< figure src="/images/content_images/cs/pose-estimation.png" class="csfigcaption" caption="**姿勢推定の多様性と難しさ**" alt="challengesfig" align="middle" attr="(Source: Mackenzie Mathis)" attrlink="https://www.biorxiv.org/content/10.1101/476531v1.full.pdf" >}}
-## NumPy's Role in meeting Pose Estimation Challenges
+## 姿勢推定の課題に対応するためのNumPyの役割
NumPy addresses DeepLabCut technology's core need of numerical computations at high speed for behavioural analytics. Besides NumPy, DeepLabCut employs various Python software that utilize NumPy at their core, such as [SciPy](https://www.scipy.org), [Pandas](https://pandas.pydata.org), [matplotlib](https://matplotlib.org), [Tensorpack](https://github.com/tensorpack/tensorpack), [imgaug](https://github.com/aleju/imgaug), [scikit-learn](https://scikit-learn.org/stable/), [scikit-image](https://scikit-image.org) and [Tensorflow](https://www.tensorflow.org).
From e1482228f0c1487e5f91c6cc268d20a7d2bf8bf1 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Fri, 19 Feb 2021 23:39:56 +0000
Subject: [PATCH 166/909] New translations deeplabcut-dnn.md (Japanese)
---
content/ja/case-studies/deeplabcut-dnn.md | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/content/ja/case-studies/deeplabcut-dnn.md b/content/ja/case-studies/deeplabcut-dnn.md
index f978ebddcb..d301b47ec5 100644
--- a/content/ja/case-studies/deeplabcut-dnn.md
+++ b/content/ja/case-studies/deeplabcut-dnn.md
@@ -65,15 +65,15 @@ DeepLabCut では [transfer learning](https://arxiv.org/pdf/1909.11229)という
## 姿勢推定の課題に対応するためのNumPyの役割
-NumPy addresses DeepLabCut technology's core need of numerical computations at high speed for behavioural analytics. Besides NumPy, DeepLabCut employs various Python software that utilize NumPy at their core, such as [SciPy](https://www.scipy.org), [Pandas](https://pandas.pydata.org), [matplotlib](https://matplotlib.org), [Tensorpack](https://github.com/tensorpack/tensorpack), [imgaug](https://github.com/aleju/imgaug), [scikit-learn](https://scikit-learn.org/stable/), [scikit-image](https://scikit-image.org) and [Tensorflow](https://www.tensorflow.org).
+Numpy は DeepLabCutにおける、行動分析の高速化のための数値計算の核となっています。 NumPyだけでなく、 DeepLabCutは様々なNumpyをベースとしているPythonライブラリを利用しています。: [SciPy](https://www.scipy.org), [Pandas](https://pandas.pydata.org), [matplotlib](https://matplotlib.org), [Tensorpack](https://github.com/tensorpack/tensorpack), [imgaug](https://github.com/aleju/imgaug), [scikit-learn](https://scikit-learn.org/stable/), [scikit-image](https://scikit-image.org) and [Tensorflow](https://www.tensorflow.org).
-The following features of NumPy played a key role in addressing the image processing, combinatorics requirements and need for fast computation in DeepLabCut pose estimation algorithms:
+NumPyの特徴である、画像処理、組み合わせ処理、そして高速計算は、DeepLabCutの姿勢推定アルゴリズムにおいて重要な役割を果たしました。
-* Vectorization
-* Masked Array Operations
-* Linear Algebra
-* Random Sampling
-* Reshaping of large arrays
+* ベクトル化
+* マスクされた配列操作
+* 線形代数
+* ランダムサンプリング
+* 大きな配列の再構成
DeepLabCut utilizes NumPy’s array capabilities throughout the workflow offered by the toolkit. In particular, NumPy is used for sampling distinct frames for human annotation labeling, and for writing, editing and processing annotation data. Within TensorFlow the neural network is trained by DeepLabCut technology over thousands of iterations to predict the ground truth annotations from frames. For this purpose, target densities (scoremaps) are created to cast pose estimation as a image-to-image translation problem. To make the neural networks robust, data augmentation is employed, which requires the calculation of target scoremaps subject to various geometric and image processing steps. To make training fast, NumPy’s vectorization capabilities are leveraged. For inference, the most likely predictions from target scoremaps need to extracted and one needs to efficiently “link predictions to assemble individual animals”.
From 2119807ec40f20c69da4a6414ba142cea79d1e22 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 20 Feb 2021 00:56:11 +0000
Subject: [PATCH 167/909] New translations deeplabcut-dnn.md (Japanese)
---
content/ja/case-studies/deeplabcut-dnn.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/ja/case-studies/deeplabcut-dnn.md b/content/ja/case-studies/deeplabcut-dnn.md
index d301b47ec5..a64f843188 100644
--- a/content/ja/case-studies/deeplabcut-dnn.md
+++ b/content/ja/case-studies/deeplabcut-dnn.md
@@ -75,7 +75,7 @@ NumPyの特徴である、画像処理、組み合わせ処理、そして高速
* ランダムサンプリング
* 大きな配列の再構成
-DeepLabCut utilizes NumPy’s array capabilities throughout the workflow offered by the toolkit. In particular, NumPy is used for sampling distinct frames for human annotation labeling, and for writing, editing and processing annotation data. Within TensorFlow the neural network is trained by DeepLabCut technology over thousands of iterations to predict the ground truth annotations from frames. For this purpose, target densities (scoremaps) are created to cast pose estimation as a image-to-image translation problem. To make the neural networks robust, data augmentation is employed, which requires the calculation of target scoremaps subject to various geometric and image processing steps. To make training fast, NumPy’s vectorization capabilities are leveraged. For inference, the most likely predictions from target scoremaps need to extracted and one needs to efficiently “link predictions to assemble individual animals”.
+DeepLabCutは、ツールキットが提供する ワークフローを通じてNumPyの配列機能を利用しています。 特にNumpy はヒューマンアノテーションのラベル付けや、アノテーションの書き込み、編集、処理のために、特定のフレームをサンプリングするために使用されています。 TensorFlowを使ったニューラルネットワークは、DeepLabCut技術によって何千回も訓練され、 フレームから真アノテーション情報を予測します。 For this purpose, target densities (scoremaps) are created to cast pose estimation as a image-to-image translation problem. To make the neural networks robust, data augmentation is employed, which requires the calculation of target scoremaps subject to various geometric and image processing steps. To make training fast, NumPy’s vectorization capabilities are leveraged. For inference, the most likely predictions from target scoremaps need to extracted and one needs to efficiently “link predictions to assemble individual animals”.
{{< figure src="/images/content_images/cs/deeplabcut-workflow.png" class="fig-center" caption="**DeepLabCut Workflow**" alt="workflow" attr="*(Source: Mackenzie Mathis)*" attrlink="https://www.researchgate.net/figure/DeepLabCut-work-flow-The-diagram-delineates-the-work-flow-as-well-as-the-directory-and_fig1_329185962">}}
From 4d757000c1ef3232c383c479d148ed51ecc43477 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 20 Feb 2021 02:15:42 +0000
Subject: [PATCH 168/909] New translations deeplabcut-dnn.md (Japanese)
---
content/ja/case-studies/deeplabcut-dnn.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/ja/case-studies/deeplabcut-dnn.md b/content/ja/case-studies/deeplabcut-dnn.md
index a64f843188..0744c7ba8f 100644
--- a/content/ja/case-studies/deeplabcut-dnn.md
+++ b/content/ja/case-studies/deeplabcut-dnn.md
@@ -75,7 +75,7 @@ NumPyの特徴である、画像処理、組み合わせ処理、そして高速
* ランダムサンプリング
* 大きな配列の再構成
-DeepLabCutは、ツールキットが提供する ワークフローを通じてNumPyの配列機能を利用しています。 特にNumpy はヒューマンアノテーションのラベル付けや、アノテーションの書き込み、編集、処理のために、特定のフレームをサンプリングするために使用されています。 TensorFlowを使ったニューラルネットワークは、DeepLabCut技術によって何千回も訓練され、 フレームから真アノテーション情報を予測します。 For this purpose, target densities (scoremaps) are created to cast pose estimation as a image-to-image translation problem. To make the neural networks robust, data augmentation is employed, which requires the calculation of target scoremaps subject to various geometric and image processing steps. To make training fast, NumPy’s vectorization capabilities are leveraged. For inference, the most likely predictions from target scoremaps need to extracted and one needs to efficiently “link predictions to assemble individual animals”.
+DeepLabCutは、ツールキットが提供する ワークフローを通じてNumPyの配列機能を利用しています。 特にNumpy はヒューマンアノテーションのラベル付けや、アノテーションの書き込み、編集、処理のために、特定のフレームをサンプリングするために使用されています。 TensorFlowを使ったニューラルネットワークは、DeepLabCut技術によって何千回も訓練され、 フレームから真アノテーション情報を予測します。 この目的のために、姿勢推定問題を、画像-画像変換問題として変換するための目標密(スコアマップ) を作成します。 To make the neural networks robust, data augmentation is employed, which requires the calculation of target scoremaps subject to various geometric and image processing steps. To make training fast, NumPy’s vectorization capabilities are leveraged. For inference, the most likely predictions from target scoremaps need to extracted and one needs to efficiently “link predictions to assemble individual animals”.
{{< figure src="/images/content_images/cs/deeplabcut-workflow.png" class="fig-center" caption="**DeepLabCut Workflow**" alt="workflow" attr="*(Source: Mackenzie Mathis)*" attrlink="https://www.researchgate.net/figure/DeepLabCut-work-flow-The-diagram-delineates-the-work-flow-as-well-as-the-directory-and_fig1_329185962">}}
From 73eda3019351b1a2d1503f51ebd46f5dadb1408f Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 20 Feb 2021 03:15:26 +0000
Subject: [PATCH 169/909] New translations deeplabcut-dnn.md (Japanese)
---
content/ja/case-studies/deeplabcut-dnn.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/content/ja/case-studies/deeplabcut-dnn.md b/content/ja/case-studies/deeplabcut-dnn.md
index 0744c7ba8f..ea18ed6dc9 100644
--- a/content/ja/case-studies/deeplabcut-dnn.md
+++ b/content/ja/case-studies/deeplabcut-dnn.md
@@ -75,13 +75,13 @@ NumPyの特徴である、画像処理、組み合わせ処理、そして高速
* ランダムサンプリング
* 大きな配列の再構成
-DeepLabCutは、ツールキットが提供する ワークフローを通じてNumPyの配列機能を利用しています。 特にNumpy はヒューマンアノテーションのラベル付けや、アノテーションの書き込み、編集、処理のために、特定のフレームをサンプリングするために使用されています。 TensorFlowを使ったニューラルネットワークは、DeepLabCut技術によって何千回も訓練され、 フレームから真アノテーション情報を予測します。 この目的のために、姿勢推定問題を、画像-画像変換問題として変換するための目標密(スコアマップ) を作成します。 To make the neural networks robust, data augmentation is employed, which requires the calculation of target scoremaps subject to various geometric and image processing steps. To make training fast, NumPy’s vectorization capabilities are leveraged. For inference, the most likely predictions from target scoremaps need to extracted and one needs to efficiently “link predictions to assemble individual animals”.
+DeepLabCutは、ツールキットが提供する ワークフローを通じてNumPyの配列機能を利用しています。 特にNumpy はヒューマンアノテーションのラベル付けや、アノテーションの書き込み、編集、処理のために、特定のフレームをサンプリングするために使用されています。 TensorFlowを使ったニューラルネットワークは、DeepLabCut技術によって何千回も訓練され、 フレームから真アノテーション情報を予測します。 この目的のために、姿勢推定問題を、画像-画像変換問題として変換するための目標密(スコアマップ) を作成します。 ニューラルネットワークのロバスト化のために、幾何学・画像的処理を施した、スコアマップの計算を行うデータオーグメンテーションを採用しています。 また学習を高速化するために、NumPyのベクトル化機能が利用されています。 推論のためには、ターゲットスコアマップから最も可能性の高い予測値を抽出し、効率的に「予測値をリンクさせて個々の動物を組み立てる」ことが必要になります。
-{{< figure src="/images/content_images/cs/deeplabcut-workflow.png" class="fig-center" caption="**DeepLabCut Workflow**" alt="workflow" attr="*(Source: Mackenzie Mathis)*" attrlink="https://www.researchgate.net/figure/DeepLabCut-work-flow-The-diagram-delineates-the-work-flow-as-well-as-the-directory-and_fig1_329185962">}}
+{{< figure src="/images/content_images/cs/deeplabcut-workflow.png" class="fig-center" caption="**DeepLabCutのワークフロー**" alt="workflow" attr="*(Source: Mackenzie Mathis)*" attrlink="https://www.researchgate.net/figure/DeepLabCut-work-flow-The-diagram-delineates-the-work-flow-as-well-as-the-directory-and_fig1_329185962">}}
-## Summary
+## まとめ
-Observing and efficiently describing behavior is a core tenant of modern ethology, neuroscience, medicine, and technology. [DeepLabCut](http://orga.cvss.cc/wp-content/uploads/2019/05/NathMathis2019.pdf) allows researchers to estimate the pose of the subject, efficiently enabling them to quantify the behavior. With only a small set of training images, the DeepLabCut Python toolbox allows training a neural network to within human level labeling accuracy, thus expanding its application to not only behavior analysis in the laboratory, but to potentially also in sports, gait analysis, medicine and rehabilitation studies. Complex combinatorics, data processing challenges faced by DeepLabCut algorithms are addressed through the use of NumPy's array manipulation capabilities.
+行動を観察し、効率的に表現することは、現代倫理学、神経科学、医学、工学の根幹です。 [DeepLabCut](http://orga.cvss.cc/wp-content/uploads/2019/05/NathMathis2019.pdf) allows researchers to estimate the pose of the subject, efficiently enabling them to quantify the behavior. With only a small set of training images, the DeepLabCut Python toolbox allows training a neural network to within human level labeling accuracy, thus expanding its application to not only behavior analysis in the laboratory, but to potentially also in sports, gait analysis, medicine and rehabilitation studies. Complex combinatorics, data processing challenges faced by DeepLabCut algorithms are addressed through the use of NumPy's array manipulation capabilities.
{{< figure src="/images/content_images/cs/numpy_dlc_benefits.png" class="fig-center" alt="numpy benefits" caption="**Key NumPy Capabilities utilized**" >}}
From a0f744f5e0f47ff15a061e3c5d40740a6197a57e Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 20 Feb 2021 08:01:46 +0000
Subject: [PATCH 170/909] New translations deeplabcut-dnn.md (Japanese)
---
content/ja/case-studies/deeplabcut-dnn.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/ja/case-studies/deeplabcut-dnn.md b/content/ja/case-studies/deeplabcut-dnn.md
index ea18ed6dc9..e3e2750d9b 100644
--- a/content/ja/case-studies/deeplabcut-dnn.md
+++ b/content/ja/case-studies/deeplabcut-dnn.md
@@ -81,7 +81,7 @@ DeepLabCutは、ツールキットが提供する ワークフローを通じて
## まとめ
-行動を観察し、効率的に表現することは、現代倫理学、神経科学、医学、工学の根幹です。 [DeepLabCut](http://orga.cvss.cc/wp-content/uploads/2019/05/NathMathis2019.pdf) allows researchers to estimate the pose of the subject, efficiently enabling them to quantify the behavior. With only a small set of training images, the DeepLabCut Python toolbox allows training a neural network to within human level labeling accuracy, thus expanding its application to not only behavior analysis in the laboratory, but to potentially also in sports, gait analysis, medicine and rehabilitation studies. Complex combinatorics, data processing challenges faced by DeepLabCut algorithms are addressed through the use of NumPy's array manipulation capabilities.
+行動を観察し、効率的に表現することは、現代倫理学、神経科学、医学、工学の根幹です。 [DeepLabCut](http://orga.cvss.cc/wp-content/uploads/2019/05/NathMathis2019.pdf) により、研究者は対象の姿勢を推定し、行動を効率的に定量化できるようになりました。 With only a small set of training images, the DeepLabCut Python toolbox allows training a neural network to within human level labeling accuracy, thus expanding its application to not only behavior analysis in the laboratory, but to potentially also in sports, gait analysis, medicine and rehabilitation studies. Complex combinatorics, data processing challenges faced by DeepLabCut algorithms are addressed through the use of NumPy's array manipulation capabilities.
{{< figure src="/images/content_images/cs/numpy_dlc_benefits.png" class="fig-center" alt="numpy benefits" caption="**Key NumPy Capabilities utilized**" >}}
From 1118e9ff750d3471103d8fe8a89df61c05a07b88 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 20 Feb 2021 09:07:24 +0000
Subject: [PATCH 171/909] New translations deeplabcut-dnn.md (Japanese)
---
content/ja/case-studies/deeplabcut-dnn.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/content/ja/case-studies/deeplabcut-dnn.md b/content/ja/case-studies/deeplabcut-dnn.md
index e3e2750d9b..50b5316673 100644
--- a/content/ja/case-studies/deeplabcut-dnn.md
+++ b/content/ja/case-studies/deeplabcut-dnn.md
@@ -81,9 +81,9 @@ DeepLabCutは、ツールキットが提供する ワークフローを通じて
## まとめ
-行動を観察し、効率的に表現することは、現代倫理学、神経科学、医学、工学の根幹です。 [DeepLabCut](http://orga.cvss.cc/wp-content/uploads/2019/05/NathMathis2019.pdf) により、研究者は対象の姿勢を推定し、行動を効率的に定量化できるようになりました。 With only a small set of training images, the DeepLabCut Python toolbox allows training a neural network to within human level labeling accuracy, thus expanding its application to not only behavior analysis in the laboratory, but to potentially also in sports, gait analysis, medicine and rehabilitation studies. Complex combinatorics, data processing challenges faced by DeepLabCut algorithms are addressed through the use of NumPy's array manipulation capabilities.
+行動を観察し、効率的に表現することは、現代倫理学、神経科学、医学、工学の根幹です。 [DeepLabCut](http://orga.cvss.cc/wp-content/uploads/2019/05/NathMathis2019.pdf) により、研究者は対象の姿勢を推定し、行動を効率的に定量化できるようになりました。 DeepLabCutのPythonツールボックスでは、わずかな学習画像のセットで、ニューラルネットワークを人間レベルのラベリング精度で学習することができ、実験室での行動分析だけでなく、スポーツ、歩行分析、医学、リハビリテーション研究などへの応用が可能になります。 DeepLabCut アルゴリズムに必要な、複雑な組み合わせ処理や、データ処理の問題は、Numpy の配列操作機能を使用して対応することになります。
-{{< figure src="/images/content_images/cs/numpy_dlc_benefits.png" class="fig-center" alt="numpy benefits" caption="**Key NumPy Capabilities utilized**" >}}
+{{< figure src="/images/content_images/cs/numpy_dlc_benefits.png" class="fig-center" alt="numpy benefits" caption="**NumPyの主要機能**" >}
[cheetah-movement]: https://www.technologynetworks.com/neuroscience/articles/interview-a-deeper-cut-into-behavior-with-mackenzie-mathis-327618
From b4f4e9760549335a4632538ff20c578f1e8c138f Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 20 Feb 2021 09:07:25 +0000
Subject: [PATCH 172/909] New translations gw-discov.md (Japanese)
---
content/ja/case-studies/gw-discov.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/ja/case-studies/gw-discov.md b/content/ja/case-studies/gw-discov.md
index 3d25090e13..6860907164 100644
--- a/content/ja/case-studies/gw-discov.md
+++ b/content/ja/case-studies/gw-discov.md
@@ -1,5 +1,5 @@
---
-title: "Case Study: Discovery of Gravitational Waves"
+title: "ケーススタディ: 重力波の発見"
sidebar: false
---
From 306749113df31fdedf9da5daed45833878c0fc8e Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Fri, 26 Feb 2021 03:55:28 +0000
Subject: [PATCH 173/909] New translations about.md (Chinese Simplified)
---
content/zh/about.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/zh/about.md b/content/zh/about.md
index 116caa48c3..0632e61ae4 100644
--- a/content/zh/about.md
+++ b/content/zh/about.md
@@ -5,7 +5,7 @@ sidebar: false
_下面是 NumPy 项目和社区的一些信息:_
-NumPy 是一个使 Python 支持数值计算的开源项目, It was created in 2005, building on the early work of the Numeric and Numarray libraries. NumPy 将始终保证项目完整开源,所有人都可以根据 [修改后的 BSD 条款](https://github.com/numpy/numpy/blob/master/LICENSE.txt) 免费对其进行使用和分发。
+NumPy 是一个使 Python 支持数值计算的开源项目, 它诞生于 2005 年,早期由 Numeric 和 Numarray 库发展而来。 NumPy 将始终保证项目完整开源,所有人都可以根据 [修改后的 BSD 条款](https://github.com/numpy/numpy/blob/master/LICENSE.txt) 免费对其进行使用和分发。
经过 Numpy 和 Python 科学计算社区协商讨论,最终决定将 Numpy 在 GitHub 上开源。 想要了解更多与社区治理有关的信息,请参阅我们的[治理文件](https://www.numpy.org/devdocs/dev/governance/index.html)。
From 5be6940873ad66dfa0e77c9f7250d4770bfe5dce Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Fri, 26 Feb 2021 04:53:13 +0000
Subject: [PATCH 174/909] New translations arraycomputing.md (Chinese
Simplified)
---
content/zh/arraycomputing.md | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/content/zh/arraycomputing.md b/content/zh/arraycomputing.md
index abd29d11c1..c5502d259d 100644
--- a/content/zh/arraycomputing.md
+++ b/content/zh/arraycomputing.md
@@ -1,21 +1,21 @@
---
-title: Array Computing
+title: 数组计算
sidebar: false
---
*Array computing is the foundation of statistical, mathematical, scientific computing in various contemporary data science and analytics applications such as data visualization, digital signal processing, image processing, bioinformatics, machine learning, AI, and several others.*
-Large scale data manipulation and transformation depends on efficient, high-performance array computing. The language of choice for data analytics, machine learning, and productive numerical computing is **Python.**
+大规模数据操作和转换取决于高效率高性能的数组计算。 数据分析、机器学习和数值计算首选的语言是 **Python**。
-**Num**erical **Py**thon or NumPy is its de-facto standard Python programming language library that supports large, multi-dimensional arrays and matrices, and comes with a vast collection of high-level mathematical functions to operate on these arrays.
+NumPy 是 Python 语言中支持大型、多维数组和矩阵计算、并附有大量高级数学功能的默认标准库。
-Since the launch of NumPy in 2006, Pandas appeared on the landscape in 2008, and it was not until a couple of years ago that several array computing libraries showed up in succession, crowding the array computing landscape. Many of these newer libraries mimic NumPy-like features and capabilities, and pack newer algorithms and features geared towards machine learning and artificial intelligence applications.
+自2006年NumPy推出以来,Pandas于2008年出现,直到几年前,更多数组计算库才连续出现,充实数组计算领域。 许多这些较新库都具有类似NumPy的功能,包含较新的算法和功能,适合机器学习和人工智能应用。
-**Array computing** is based on **arrays** data structures. *Arrays* are used to organize vast amounts of data such that a related set of values can be easily sorted, searched, mathematically manipulated, and transformed easily and quickly.
+**数组计算** 基于 **数组** 这一数据结构。 *数组*用于处理大量数据,使他们便于有效存储、搜索、计算和变换。
-Array computing is *unique* as it involves operating on the data array *at once*. What this means is that any array operation applies to an entire set of values in one shot. This vectorized approach provides speed and simplicity by enabling programmers to code and operate on aggregates of data, without having to use loops of individual scalar operations.
+数组计算是 *独特*的 ,因为它需要 *同时*操作整个数据阵列。 这意味着任何数组操作应用于整个数组的每个值。 这种向量化的方法使得程序员能够对数据进行整体操作,无需使用循环操作标量,从而使代码更高效和简洁。
From 0f630256e705ac3e857faa5c0eb28e43a2370193 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Fri, 26 Feb 2021 04:53:14 +0000
Subject: [PATCH 175/909] New translations citing-numpy.md (Chinese Simplified)
---
content/zh/citing-numpy.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/content/zh/citing-numpy.md b/content/zh/citing-numpy.md
index cf20ae59cf..cbfa873b9f 100644
--- a/content/zh/citing-numpy.md
+++ b/content/zh/citing-numpy.md
@@ -1,13 +1,13 @@
---
-title: Citing NumPy
+title: 引用 NumPy
sidebar: false
---
-If NumPy has been significant in your research, and you would like to acknowledge the project in your academic publication, we suggest citing the following paper:
+如果 NumPy 在您的研究中很重要, 您想在您的学术出版物中致谢这个项目,我们建议您引用以下论文:
* Harris, C.R., Millman, K.J., van der Walt, S.J. et al. _Array programming with NumPy_. Nature 585, 357–362 (2020). DOI: [0.1038/s41586-020-2649-2](https://doi.org/10.1038/s41586-020-2649-2). ([Publisher link](https://www.nature.com/articles/s41586-020-2649-2)).
-_In BibTeX format:_
+_BibTeX 格式:_
```
@Article{ harris2020array,
From 6141eacd2967318a1cf9b6bbeb1de6bc09f645f7 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 6 Mar 2021 00:52:10 +0100
Subject: [PATCH 176/909] New translations gw-discov.md (Japanese)
---
content/ja/case-studies/gw-discov.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/ja/case-studies/gw-discov.md b/content/ja/case-studies/gw-discov.md
index 6860907164..4d6dc6c95a 100644
--- a/content/ja/case-studies/gw-discov.md
+++ b/content/ja/case-studies/gw-discov.md
@@ -3,7 +3,7 @@ title: "ケーススタディ: 重力波の発見"
sidebar: false
---
-{{< figure src="/images/content_images/cs/gw_sxs_image.png" class="fig-center" caption="**Gravitational Waves**" alt="binary coalesce black hole generating gravitational waves" attr="*(Image Credits: The Simulating eXtreme Spacetimes (SXS) Project at LIGO)*" attrlink="https://youtu.be/Zt8Z_uzG71o" >}}
+{{< figure src="/images/content_images/cs/gw_sxs_image.png" class="fig-center" caption="**重力波**" alt="binary coalesce black hole generating gravitational waves" attr="*(Image Credits: The Simulating eXtreme Spacetimes (SXS) Project at LIGO)*" attrlink="https://youtu.be/Zt8Z_uzG71o" >}}
The scientific Python ecosystem is critical infrastructure for the research done at LIGO.
The scientific Python ecosystem is critical infrastructure for the research done at LIGO.
-
+
科学計算のためのPythonエコシステムはLIGOで行われている研究のための重要なインフラです。
+
-## About [Gravitational Waves](https://www.nationalgeographic.com/news/2017/10/what-are-gravitational-waves-ligo-astronomy-science/) and [LIGO](https://www.ligo.caltech.edu)
+## [重力波](https://www.nationalgeographic.com/news/2017/10/what-are-gravitational-waves-ligo-astronomy-science/) と [LIGO](https://www.ligo.caltech.edu) について
-Gravitational waves are ripples in the fabric of space and time, generated by cataclysmic events in the universe such as collision and merging of two black holes or coalescing binary stars or supernovae. Observing GW can not only help in studying gravity but also in understanding some of the obscure phenomena in the distant universe and its impact.
+重力波は、空間と時間の基本構造の波紋です。 2つのブラックホールの衝突や合体、2連星や超新星の合体など、大きな変動現象によって生成されます。 Observing GW can not only help in studying gravity but also in understanding some of the obscure phenomena in the distant universe and its impact.
The [Laser Interferometer Gravitational-Wave Observatory (LIGO)](https://www.ligo.caltech.edu) was designed to open the field of gravitational-wave astrophysics through the direct detection of gravitational waves predicted by Einstein’s General Theory of Relativity. It comprises two widely-separated interferometers within the United States — one in Hanford, Washington and the other in Livingston, Louisiana — operated in unison to detect gravitational waves. Each of them has multi-kilometer-scale gravitational wave detectors that use laser interferometry. The LIGO Scientific Collaboration (LSC), is a group of more than 1000 scientists from universities around the United States and in 14 other countries supported by more than 90 universities and research institutes; approximately 250 students actively contributing to the collaboration. The new LIGO discovery is the first observation of gravitational waves themselves, made by measuring the tiny disturbances the waves make to space and time as they pass through the earth. It has opened up new astrophysical frontiers that explore the warped side of the universe—objects and phenomena that are made from warped spacetime.
From 2780108ecb6ee7244df4e8f04aa93b3ae234d9d5 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sun, 14 Mar 2021 01:37:53 +0100
Subject: [PATCH 178/909] New translations gw-discov.md (Japanese)
---
content/ja/case-studies/gw-discov.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/content/ja/case-studies/gw-discov.md b/content/ja/case-studies/gw-discov.md
index 4135bee39d..99e2acfb54 100644
--- a/content/ja/case-studies/gw-discov.md
+++ b/content/ja/case-studies/gw-discov.md
@@ -12,9 +12,9 @@ sidebar: false
## [重力波](https://www.nationalgeographic.com/news/2017/10/what-are-gravitational-waves-ligo-astronomy-science/) と [LIGO](https://www.ligo.caltech.edu) について
-重力波は、空間と時間の基本構造の波紋です。 2つのブラックホールの衝突や合体、2連星や超新星の合体など、大きな変動現象によって生成されます。 Observing GW can not only help in studying gravity but also in understanding some of the obscure phenomena in the distant universe and its impact.
+重力波は、空間と時間の基本構造の波紋です。 2つのブラックホールの衝突や合体、2連星や超新星の合体など、大きな変動現象によって生成されます。 重力波を観測することは、重力を研究する上で 重要なだけでなく、遠い宇宙とその影響におけるいくつかの不明瞭な現象の理解するためにも役立ちます。
-The [Laser Interferometer Gravitational-Wave Observatory (LIGO)](https://www.ligo.caltech.edu) was designed to open the field of gravitational-wave astrophysics through the direct detection of gravitational waves predicted by Einstein’s General Theory of Relativity. It comprises two widely-separated interferometers within the United States — one in Hanford, Washington and the other in Livingston, Louisiana — operated in unison to detect gravitational waves. Each of them has multi-kilometer-scale gravitational wave detectors that use laser interferometry. The LIGO Scientific Collaboration (LSC), is a group of more than 1000 scientists from universities around the United States and in 14 other countries supported by more than 90 universities and research institutes; approximately 250 students actively contributing to the collaboration. The new LIGO discovery is the first observation of gravitational waves themselves, made by measuring the tiny disturbances the waves make to space and time as they pass through the earth. It has opened up new astrophysical frontiers that explore the warped side of the universe—objects and phenomena that are made from warped spacetime.
+[レーザー干渉計重力波天文台(LIGO)](https://www. ligo. caltech. edu)は、アインシュタインの一般相対性理論によって予測された重力波の直接検出を通して、重力波天体物理学の分野を切り開くように設計されました。 このシステムは、アメリカのワシントン州ハンフォードとルイジアナ州リビングストンにある2つの干渉計が一体となって構成され、重力波を検出します。 Each of them has multi-kilometer-scale gravitational wave detectors that use laser interferometry. The LIGO Scientific Collaboration (LSC), is a group of more than 1000 scientists from universities around the United States and in 14 other countries supported by more than 90 universities and research institutes; approximately 250 students actively contributing to the collaboration. The new LIGO discovery is the first observation of gravitational waves themselves, made by measuring the tiny disturbances the waves make to space and time as they pass through the earth. It has opened up new astrophysical frontiers that explore the warped side of the universe—objects and phenomena that are made from warped spacetime.
### Key Objectives
From c7e1ca319a46e9c8ec83ebbc12c4227af0e8e364 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sun, 14 Mar 2021 07:21:24 +0100
Subject: [PATCH 179/909] New translations gw-discov.md (Japanese)
---
content/ja/case-studies/gw-discov.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/ja/case-studies/gw-discov.md b/content/ja/case-studies/gw-discov.md
index 99e2acfb54..e59e2056b4 100644
--- a/content/ja/case-studies/gw-discov.md
+++ b/content/ja/case-studies/gw-discov.md
@@ -14,7 +14,7 @@ sidebar: false
重力波は、空間と時間の基本構造の波紋です。 2つのブラックホールの衝突や合体、2連星や超新星の合体など、大きな変動現象によって生成されます。 重力波を観測することは、重力を研究する上で 重要なだけでなく、遠い宇宙とその影響におけるいくつかの不明瞭な現象の理解するためにも役立ちます。
-[レーザー干渉計重力波天文台(LIGO)](https://www. ligo. caltech. edu)は、アインシュタインの一般相対性理論によって予測された重力波の直接検出を通して、重力波天体物理学の分野を切り開くように設計されました。 このシステムは、アメリカのワシントン州ハンフォードとルイジアナ州リビングストンにある2つの干渉計が一体となって構成され、重力波を検出します。 Each of them has multi-kilometer-scale gravitational wave detectors that use laser interferometry. The LIGO Scientific Collaboration (LSC), is a group of more than 1000 scientists from universities around the United States and in 14 other countries supported by more than 90 universities and research institutes; approximately 250 students actively contributing to the collaboration. The new LIGO discovery is the first observation of gravitational waves themselves, made by measuring the tiny disturbances the waves make to space and time as they pass through the earth. It has opened up new astrophysical frontiers that explore the warped side of the universe—objects and phenomena that are made from warped spacetime.
+[レーザー干渉計重力波天文台(LIGO)](https://www. ligo. caltech. edu)は、アインシュタインの一般相対性理論によって予測された重力波の直接検出を通して、重力波天体物理学の分野を切り開くように設計されました。 このシステムは、アメリカのワシントン州ハンフォードとルイジアナ州リビングストンにある2つの干渉計が一体となって構成され、重力波を検出します。 それぞれのシステムには、レーザー干渉法を用いた数キロ規模の重力波検出器が設置されています。 LIGO Scientific Collaboration(LSC)は、米国をはじめとする14カ国の大学から1000人以上の科学者が集まり、90以上の大学・研究機関によって支援されています。また、約250人の学生も参加しています。 今回のLIGOの重要な発見は、重力波が地球を通過する際に生じる空間と時間の微小な乱れを測定することで、重力波そのものを観測した初めての例であることです。 それは、ゆがんだ時空から作られた 物体と現象を宇宙の歪んだ側面を探索する、新しい天体物理学フロンティア を開きました。
### Key Objectives
From f7442f403fdb375c8fd58b4b31efbe559bdac008 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sun, 14 Mar 2021 08:18:30 +0100
Subject: [PATCH 180/909] New translations gw-discov.md (Japanese)
---
content/ja/case-studies/gw-discov.md | 20 ++++++++++----------
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/content/ja/case-studies/gw-discov.md b/content/ja/case-studies/gw-discov.md
index e59e2056b4..1e169dc175 100644
--- a/content/ja/case-studies/gw-discov.md
+++ b/content/ja/case-studies/gw-discov.md
@@ -14,26 +14,26 @@ sidebar: false
重力波は、空間と時間の基本構造の波紋です。 2つのブラックホールの衝突や合体、2連星や超新星の合体など、大きな変動現象によって生成されます。 重力波を観測することは、重力を研究する上で 重要なだけでなく、遠い宇宙とその影響におけるいくつかの不明瞭な現象の理解するためにも役立ちます。
-[レーザー干渉計重力波天文台(LIGO)](https://www. ligo. caltech. edu)は、アインシュタインの一般相対性理論によって予測された重力波の直接検出を通して、重力波天体物理学の分野を切り開くように設計されました。 このシステムは、アメリカのワシントン州ハンフォードとルイジアナ州リビングストンにある2つの干渉計が一体となって構成され、重力波を検出します。 それぞれのシステムには、レーザー干渉法を用いた数キロ規模の重力波検出器が設置されています。 LIGO Scientific Collaboration(LSC)は、米国をはじめとする14カ国の大学から1000人以上の科学者が集まり、90以上の大学・研究機関によって支援されています。また、約250人の学生も参加しています。 今回のLIGOの重要な発見は、重力波が地球を通過する際に生じる空間と時間の微小な乱れを測定することで、重力波そのものを観測した初めての例であることです。 それは、ゆがんだ時空から作られた 物体と現象を宇宙の歪んだ側面を探索する、新しい天体物理学フロンティア を開きました。
+[レーザー干渉計重力波天文台(LIGO)](https://www. ligo. caltech. edu)は、アインシュタインの一般相対性理論によって予測された重力波の直接検出を通して、重力波天体物理学の分野を切り開くように設計されました。 このシステムは、アメリカのワシントン州ハンフォードとルイジアナ州リビングストンにある2つの干渉計が一体となって構成され、重力波を検出します。 それぞれのシステムには、レーザー干渉法を用いた数キロ規模の重力波検出器が設置されています。 LIGO Scientific Collaboration(LSC)は、米国をはじめとする14カ国の大学から1000人以上の科学者が集まり、90以上の大学・研究機関によって支援されています。また、約250人の学生も参加しています。 今回のLIGOの重要な発見は、重力波が地球を通過する際に生じる空間と時間の微小な乱れを測定することで、重力波そのものを観測した初めての例であることです。 これにより、ゆがんだ時空から作られた 物体とそれに伴う現象を、宇宙の歪んだ側面から探索する、新しい天体物理学のフロンティア が開かれました。
-### Key Objectives
+### 主な目的
-* Though its [mission](https://www.ligo.caltech.edu/page/what-is-ligo) is to detect gravitational waves from some of the most violent and energetic processes in the Universe, the data LIGO collects may have far-reaching effects on many areas of physics including gravitation, relativity, astrophysics, cosmology, particle physics, and nuclear physics.
-* Crunch observed data via numerical relativity computations that involves complex maths in order to discern signal from noise, filter out relevant signal and statistically estimate significance of observed data
-* Data visualization so that the binary / numerical results can be comprehended.
+* LIGOの[ミッション](https://www.ligo.caltech.edu/page/what-is-ligo)は、宇宙で最も激しくエネルギーに満ちたプロセスからの重力波を検出することですが、LIGOが収集するデータは、重力、相対性理論、天体物理学、宇宙論、素粒子物理学、原子核物理学など、物理学の多くの分野に広く影響を与える可能性があります。
+* 複雑な数学を含む相対性理論の数値計算によって観測データを解析し、信号とノイズを識別し、関連性のある信号をフィルタリングし、観測データの有意性を統計的に推定することで、宇宙の始まりのクランチを観測できるようになります。
+* バイナリや数値の結果を理解しやすいのようにデータを可視化することも必要です。
-### The Challenges
+### 課題
-* **Computation**
+* **計算**
- Gravitational Waves are hard to detect as they produce a very small effect and have tiny interaction with matter. Processing and analyzing all of LIGO's data requires a vast computing infrastructure.After taking care of noise, which is billions of times of the signal, there is still very complex relativity equations and huge amounts of data which present a computational challenge: [O(10^7) CPU hrs needed for binary merger analyses](https://youtu.be/7mcHknWWzNI) spread on 6 dedicated LIGO clusters
+ 重力波は非常に小さい効果を生み、物質と微小な相互作用を持つため、検出が困難です。 LIGOのすべてのデータを処理・分析するには、膨大な計算インフラが必要です。信号の数十億倍のノイズを除去した後も、非常に複雑な相対性理論の方程式と膨大な量のデータがあり、計算上の課題となっています。例えば6つのLIGO専用クラスターに分散されたバイナリ結合解析には[O(10^7)個のCPU時間](https:/youtu.be7mcHknWWzNI)が必要です。
-* **Data Deluge**
+* **データの氾濫**
- As observational devices become more sensitive and reliable, the challenges posed by data deluge and finding a needle in a haystack rise multi-fold. LIGO generates terabytes of data every day! Making sense of this data requires an enormous effort for each and every detection. For example, the signals being collected by LIGO must be matched by supercomputers against hundreds of thousands of templates of possible gravitational-wave signatures.
+ 観測装置がより高感度で信頼性を持つようになると、データの大洪水によって、干し草の中から針を探すような問題が、多重に発生することがわかります。 LIGOは毎日テラバイトのデータを生成しているからです! Making sense of this data requires an enormous effort for each and every detection. For example, the signals being collected by LIGO must be matched by supercomputers against hundreds of thousands of templates of possible gravitational-wave signatures.
* **Visualization**
From a7af040742f329674eab8247556564a0f04949c1 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 20 Mar 2021 00:54:35 +0100
Subject: [PATCH 181/909] New translations gw-discov.md (Japanese)
---
content/ja/case-studies/gw-discov.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/content/ja/case-studies/gw-discov.md b/content/ja/case-studies/gw-discov.md
index 1e169dc175..b292e85aa7 100644
--- a/content/ja/case-studies/gw-discov.md
+++ b/content/ja/case-studies/gw-discov.md
@@ -33,11 +33,11 @@ sidebar: false
* **データの氾濫**
- 観測装置がより高感度で信頼性を持つようになると、データの大洪水によって、干し草の中から針を探すような問題が、多重に発生することがわかります。 LIGOは毎日テラバイトのデータを生成しているからです! Making sense of this data requires an enormous effort for each and every detection. For example, the signals being collected by LIGO must be matched by supercomputers against hundreds of thousands of templates of possible gravitational-wave signatures.
+ 観測装置がより高感度で信頼性を持つようになると、データの大洪水によって、干し草の中から針を探すような問題が、多重に発生することがわかります。 LIGOは毎日テラバイトのデータを生成しているからです! この大量のデータを解釈するには、各検出ごとに多大な労力が必要です。 例えば、LIGOによって収集される信号は、数十万個の重力波シグネチャのテンプレートで構成されており、スーパーコンピュータでしか解析できません。
-* **Visualization**
+* **可視化**
- Once the obstacles related to understanding Einstein’s equations well enough to solve them using supercomputers are taken care of, the next big challenge was making data comprehensible to the human brain. Simulation modeling as well as signal detection requires effective visualization techniques. Visualization also plays a role in lending more credibility to numerical relativity in the eyes of pure science aficionados, who did not give enough importance to numerical relativity until imaging and simulations made it easier to comprehend results for a larger audience. Speed of complex computations and rendering, re-rendering images and simulations using latest experimental inputs and insights can be a time consuming activity that challenges researchers in this domain.
+ アインシュタインの方程式を元にスーパーコンピュータでデータを解析できるようになったら、次はデータを人間の脳で理解できるようにしなければなりません。 シミュレーションのモデリングや信号の検出には、わかりやすい可視化技術が必要です。 Visualization also plays a role in lending more credibility to numerical relativity in the eyes of pure science aficionados, who did not give enough importance to numerical relativity until imaging and simulations made it easier to comprehend results for a larger audience. Speed of complex computations and rendering, re-rendering images and simulations using latest experimental inputs and insights can be a time consuming activity that challenges researchers in this domain.
{{< figure src="/images/content_images/cs/gw_strain_amplitude.png" class="fig-center" alt="gravitational waves strain amplitude" caption="**Estimated gravitational-wave strain amplitude from GW150914**" attr="(**Graph Credits:** Observation of Gravitational Waves from a Binary Black Hole Merger, ResearchGate Publication)" attrlink="https://www.researchgate.net/publication/293886905_Observation_of_Gravitational_Waves_from_a_Binary_Black_Hole_Merger" >}}
From 6cc0ac6fe0fa57029954e823f33c7ea4b283f01a Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 20 Mar 2021 01:53:07 +0100
Subject: [PATCH 182/909] New translations gw-discov.md (Japanese)
---
content/ja/case-studies/gw-discov.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/ja/case-studies/gw-discov.md b/content/ja/case-studies/gw-discov.md
index b292e85aa7..9ffbe21861 100644
--- a/content/ja/case-studies/gw-discov.md
+++ b/content/ja/case-studies/gw-discov.md
@@ -37,7 +37,7 @@ sidebar: false
* **可視化**
- アインシュタインの方程式を元にスーパーコンピュータでデータを解析できるようになったら、次はデータを人間の脳で理解できるようにしなければなりません。 シミュレーションのモデリングや信号の検出には、わかりやすい可視化技術が必要です。 Visualization also plays a role in lending more credibility to numerical relativity in the eyes of pure science aficionados, who did not give enough importance to numerical relativity until imaging and simulations made it easier to comprehend results for a larger audience. Speed of complex computations and rendering, re-rendering images and simulations using latest experimental inputs and insights can be a time consuming activity that challenges researchers in this domain.
+ アインシュタインの方程式を元にスーパーコンピュータでデータを解析できるようになったら、次はデータを人間の脳で理解できるようにしなければなりません。 シミュレーションのモデリングや信号の検出には、わかりやすい可視化技術が必要です。 画像処理やシミュレーションによって、解析結果をより多くの人に理解してもらえる状態になる前の段階において、可視化は、数値相対性を十分に重要視していなかった純粋な科学愛好家の目に、数値相対性が、より信頼性の高いものとして映るようにするという役割も果たしています。 実験データの処理や考察のために、複雑な計算をしたり、画像やシミュレーションの再レンダリングしたりすることは、この分野の研究者にとって時間のかかる作業となります。
{{< figure src="/images/content_images/cs/gw_strain_amplitude.png" class="fig-center" alt="gravitational waves strain amplitude" caption="**Estimated gravitational-wave strain amplitude from GW150914**" attr="(**Graph Credits:** Observation of Gravitational Waves from a Binary Black Hole Merger, ResearchGate Publication)" attrlink="https://www.researchgate.net/publication/293886905_Observation_of_Gravitational_Waves_from_a_Binary_Black_Hole_Merger" >}}
From 2f4db6b4d5e3b1866bc47373459ced1a313506f1 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 20 Mar 2021 02:52:32 +0100
Subject: [PATCH 183/909] New translations gw-discov.md (Japanese)
---
content/ja/case-studies/gw-discov.md | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/content/ja/case-studies/gw-discov.md b/content/ja/case-studies/gw-discov.md
index 9ffbe21861..64431027d9 100644
--- a/content/ja/case-studies/gw-discov.md
+++ b/content/ja/case-studies/gw-discov.md
@@ -39,17 +39,17 @@ sidebar: false
アインシュタインの方程式を元にスーパーコンピュータでデータを解析できるようになったら、次はデータを人間の脳で理解できるようにしなければなりません。 シミュレーションのモデリングや信号の検出には、わかりやすい可視化技術が必要です。 画像処理やシミュレーションによって、解析結果をより多くの人に理解してもらえる状態になる前の段階において、可視化は、数値相対性を十分に重要視していなかった純粋な科学愛好家の目に、数値相対性が、より信頼性の高いものとして映るようにするという役割も果たしています。 実験データの処理や考察のために、複雑な計算をしたり、画像やシミュレーションの再レンダリングしたりすることは、この分野の研究者にとって時間のかかる作業となります。
-{{< figure src="/images/content_images/cs/gw_strain_amplitude.png" class="fig-center" alt="gravitational waves strain amplitude" caption="**Estimated gravitational-wave strain amplitude from GW150914**" attr="(**Graph Credits:** Observation of Gravitational Waves from a Binary Black Hole Merger, ResearchGate Publication)" attrlink="https://www.researchgate.net/publication/293886905_Observation_of_Gravitational_Waves_from_a_Binary_Black_Hole_Merger" >}}
+{{< figure src="/images/content_images/cs/gw_strain_amplitude.png" class="fig-center" alt="gravitational waves strain amplitude" caption="**GW150914から推定される重力波の歪みの振幅**" attr="(**Graph Credits:** Observation of Gravitational Waves from a Binary Black Hole Merger, ResearchGate Publication)" attrlink="https://www.researchgate.net/publication/293886905_Observation_of_Gravitational_Waves_from_a_Binary_Black_Hole_Merger" >}}
-## NumPy’s Role in the Detection of Gravitational Waves
+## 重力波の検出におけるNumPyの役割
-Gravitational waves emitted from the merger cannot be computed using any technique except brute force numerical relativity using supercomputers. The amount of data LIGO collects is as incomprehensibly large as gravitational wave signals are small.
+合成により放出される重力波は、スーパーコンピュータを用いたブルートフォースの数値相対性処理以外の手法では計算できません。 LIGOが収集するデータ量は、重力波の信号が少ないのと同じくらい不可解です。
-NumPy, the standard numerical analysis package for Python, was utilized by the software used for various tasks performed during the GW detection project at LIGO. NumPy helped in solving complex maths and data manipulation at high speed. Here are some examples:
+Python用の標準的な数値解析パッケージNumPyは、LIGOの重力波検出プロジェクトで実行される様々なタスクに使用されるソフトウェアで利用されています。 Numpyは、複雑な数学と高速なデータ操作に役立ちました。 次にいくつかの例を示します。
-* [Signal Processing](https://www.uv.es/virgogroup/Denoising_ROF.html): Glitch detection, [Noise identification and Data Characterization](https://ep2016.europython.eu/media/conference/slides/pyhton-in-gravitational-waves-research-communities.pdf) (NumPy, scikit-learn, scipy, matplotlib, pandas, pyCharm)
-* Data retrieval: Deciding which data can be analyzed, figuring out whether it contains a signal - needle in a haystack
-* Statistical analysis: estimate the statistical significance of observational data, estimating the signal parameters (e.g. masses of stars, spin velocity, and distance) by comparison with a model.
+* [信号処理](https://www.uv.es/virgogroup/Denoising_ROF.html): グリッジ検出, [ノイズ同定とデータ判定](https://ep2016.europython.eu/media/conference/slides/pyhton-in-gravitational-waves-research-communities.pdf) (NumPy, scikit-learn, scipy, matplotlib, pandas, pyCharm)
+* データ取得: どのデータが解析できるかを決定し、干し草の中の針のような信号が入っているかどうかを突き止める。
+* 統計解析:観測データの統計的有意性を推定し、モデルとの比較により信号パラメータ(星の質量、スピン速度、距離など)を推定する。
* Visualization of data
- Time series
- Spectrograms
From b41fb85594f65c67ef3c34e413dd528607d44cfd Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 20 Mar 2021 03:51:21 +0100
Subject: [PATCH 184/909] New translations gw-discov.md (Japanese)
---
content/ja/case-studies/gw-discov.md | 20 ++++++++++----------
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/content/ja/case-studies/gw-discov.md b/content/ja/case-studies/gw-discov.md
index 64431027d9..52332839a7 100644
--- a/content/ja/case-studies/gw-discov.md
+++ b/content/ja/case-studies/gw-discov.md
@@ -50,20 +50,20 @@ Python用の標準的な数値解析パッケージNumPyは、LIGOの重力波
* [信号処理](https://www.uv.es/virgogroup/Denoising_ROF.html): グリッジ検出, [ノイズ同定とデータ判定](https://ep2016.europython.eu/media/conference/slides/pyhton-in-gravitational-waves-research-communities.pdf) (NumPy, scikit-learn, scipy, matplotlib, pandas, pyCharm)
* データ取得: どのデータが解析できるかを決定し、干し草の中の針のような信号が入っているかどうかを突き止める。
* 統計解析:観測データの統計的有意性を推定し、モデルとの比較により信号パラメータ(星の質量、スピン速度、距離など)を推定する。
-* Visualization of data
- - Time series
- - Spectrograms
-* Compute Correlations
-* Key [Software](https://github.com/lscsoft) developed in GW data analysis such as [GwPy](https://gwpy.github.io/docs/stable/overview.html) and [PyCBC](https://pycbc.org) uses NumPy and AstroPy under the hood for providing object based interfaces to utilities, tools, and methods for studying data from gravitational-wave detectors.
+* データの可視化
+ - 時系列データ
+ - スペクトログラム
+* 相関計算
+* 重力波データ解析のために開発された [ソフトウェア](https://github.com/lscsoft)である[GwPy](https://gwpy.github.io/docs/stable/overview.html)や [PyCBC](https://pycbc.org)はNumPy やAstroPyを重力波検出器からのデータを研究するためのユーティリティー、ツール、およびメソッドへのオブジェクトベースのインターフェースを提供するために利用しています。
-{{< figure src="/images/content_images/cs/gwpy-numpy-dep-graph.png" class="fig-center" alt="gwpy-numpy depgraph" caption="**Dependency graph showing how GwPy package depends on NumPy**" >}}
+{{< figure src="/images/content_images/cs/gwpy-numpy-dep-graph.png" class="fig-center" alt="gwpy-numpy depgraph" caption=""**GwPyのNumpy依存グラフ**" >}}
----
-{{< figure src="/images/content_images/cs/PyCBC-numpy-dep-graph.png" class="fig-center" alt="PyCBC-numpy depgraph" caption="**Dependency graph showing how PyCBC package depends on NumPy**" >}}
+{{< figure src="/images/content_images/cs/PyCBC-numpy-dep-graph.png" class="fig-center" alt="PyCBC-numpy depgraph" caption=""**PyCBCのNumPy依存グラフ**" >}}
-## Summary
+## まとめ
-GW detection has enabled researchers to discover entirely unexpected phenomena while providing new insight into many of the most profound astrophysical phenomena known. Number crunching and data visualization is a crucial step that helps scientists gain insights into data gathered from the scientific observations and understand the results. The computations are complex and cannot be comprehended by humans unless it is visualized using computer simulations that are fed with the real observed data and analysis. NumPy along with other Python packages such as matplotlib, pandas, and scikit-learn is [enabling researchers](https://www.gw-openscience.org/events/GW150914/) to answer complex questions and discover new horizons in our understanding of the universe.
+重力波の検出により、研究者はこれまでに予期しなかった現象を発見することができました。 一方で、これまで知られてきた深遠な天体物理学の現象に、多くに新たな洞察を提供しました。 データ解釈とデータの可視化は、科学者が科学的な観測から収集したデータについての洞察を得て、その結果を理解するのに役立つ重要なステップです。 しかし、その計算は複雑であり、実際の観測データと分析を用いたコンピュータシミュレーションを用いて可視化されない限り、人間が理解することはできませんでした。 Numpy、matplotlib、pandasなどの、Pythonパッケージとともに、 scikit-learningは 、研究者 [が](https://www.gw-openscience.org/events/GW150914/) 複雑な質問に答え、 私たちの宇宙についての理解において、新しい地平を発見することを可能にしてきたのです。
-{{< figure src="/images/content_images/cs/numpy_gw_benefits.png" class="fig-center" alt="numpy benefits" caption="**Key NumPy Capabilities utilized**" >}}
+{{< figure src="/images/content_images/cs/numpy_bh_benefits.png" class="fig-center" alt="numpy benefits" caption== "**利用されたNumpyの主要機能**" >}}
From 329d32a6fe6b6b212623566f40a60efd9dda59b2 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 20 Mar 2021 03:51:22 +0100
Subject: [PATCH 185/909] New translations learn.md (Japanese)
---
content/ja/learn.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/ja/learn.md b/content/ja/learn.md
index 4611d3a402..fe5ea1b88b 100644
--- a/content/ja/learn.md
+++ b/content/ja/learn.md
@@ -1,5 +1,5 @@
---
-title: Learn
+title: Numpyの学び方
sidebar: false
---
From 225c918357a318507dba9c89cd438767ec6e7cc6 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sun, 21 Mar 2021 00:37:01 +0100
Subject: [PATCH 186/909] New translations learn.md (Japanese)
---
content/ja/learn.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/content/ja/learn.md b/content/ja/learn.md
index fe5ea1b88b..486aa7fb87 100644
--- a/content/ja/learn.md
+++ b/content/ja/learn.md
@@ -3,14 +3,14 @@ title: Numpyの学び方
sidebar: false
---
-For the **official NumPy documentation** visit [numpy.org/doc/stable](https://numpy.org/doc/stable).
+**公式の Numpy ドキュメント** については [numpy.org/doc/stable](https://numpy.org/doc/stable) を参照してください。
-Below is a curated collection of external resources. To contribute, see the [end of this page](#add-to-this-list).
+以下は、キュレーションされた外部リソースのリストです。 こちらのリストに貢献するには、 [このページの末尾](#add-to-this-list) を参照してください。
***
-## Beginners
+## 初心者向け
-There's a ton of information about NumPy out there. If you are new, we'd strongly recommend these:
+NumPyについての資料は多数存在しています。 初心者の方にはこちらの資料をお勧めします:
**Tutorials**
From ab4793b2c9af7499cf80f563499b4dda6200cc93 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sun, 21 Mar 2021 01:35:24 +0100
Subject: [PATCH 187/909] New translations learn.md (Japanese)
---
content/ja/learn.md | 64 ++++++++++++++++++++++-----------------------
1 file changed, 32 insertions(+), 32 deletions(-)
diff --git a/content/ja/learn.md b/content/ja/learn.md
index 486aa7fb87..6e42b81f4c 100644
--- a/content/ja/learn.md
+++ b/content/ja/learn.md
@@ -12,54 +12,54 @@ sidebar: false
NumPyについての資料は多数存在しています。 初心者の方にはこちらの資料をお勧めします:
- **Tutorials**
-
-* [NumPy Quickstart Tutorial](https://numpy.org/devdocs/user/quickstart.html)
-* [SciPy Lectures](https://scipy-lectures.org/) Besides covering NumPy, these lectures offer a broader introduction to the scientific Python ecosystem.
-* [NumPy: the absolute basics for beginners](https://numpy.org/devdocs/user/absolute_beginners.html)
-* [Machine Learning Plus - Introduction to ndarray](https://www.machinelearningplus.com/python/numpy-tutorial-part1-array-python-examples/)
-* [Edureka - Learn NumPy Arrays with Examples ](https://www.edureka.co/blog/python-numpy-tutorial/)
-* [Dataquest - NumPy Tutorial: Data Analysis with Python](https://www.dataquest.io/blog/numpy-tutorial-python/)
-* [NumPy tutorial *by Nicolas Rougier*](https://github.com/rougier/numpy-tutorial)
+ **チュートリアル**
+
+* [NumPy Quickstart チュートリアル](https://numpy.org/devdocs/user/quickstart.html)
+* [SciPyレクチャー](https://scipy-lectures.org/) NumPyだけでなく、科学的なPythonソフトウェアエコシステムを広く紹介しています。
+* [Numpy: 初心者のための基本](https://numpy.org/devdocs/user/absolute_beginners.html)
+* [機械学習プラス - ndarray入門](https://www.machinelearningplus.com/python/numpy-tutorial-part1-array-python-examples/)
+* [Edureka - NumPy配列を例題で学ぶ ](https://www.edureka.co/blog/python-numpy-tutorial/)
+* [Dataquest - NumPyチュートリアル: Python を使ったデータ解析](https://www.dataquest.io/blog/numpy-tutorial-python/)
+* [Numpy チュートリアル *by Nicolas Rougier*](https://github.com/rougier/numpy-tutorial)
* [Stanford CS231 *by Justin Johnson*](http://cs231n.github.io/python-numpy-tutorial/)
-* [NumPy User Guide](https://numpy.org/devdocs)
+* [Numpyユーザーガイド](https://numpy.org/devdocs)
- **Books**
+ **書籍**
-* [Guide to NumPy *by Travis E. Oliphant*](http://web.mit.edu/dvp/Public/numpybook.pdf) This is a free version 1 from 2006. For the latest copy (2015) see [here](https://www.barnesandnoble.com/w/guide-to-numpy-travis-e-oliphant-phd/1122853007).
-* [From Python to NumPy *by Nicolas P. Rougier*](https://www.labri.fr/perso/nrougier/from-python-to-numpy/)
-* [Elegant SciPy](https://www.amazon.com/Elegant-SciPy-Art-Scientific-Python/dp/1491922877) *by Juan Nunez-Iglesias, Stefan van der Walt, and Harriet Dashnow*
+* [NumPガイド*by Travelis E. Oliphant*](http://web.mit.edu/dvp/Public/numpybook.pdf) これは2006年の無料版の初版です 最新版(2015年)については、こちら [を参照ください](https://www.barnesandnoble.com/w/guide-to-numpy-travis-e-oliphant-phd/1122853007).
+* [PythonからNumPyまで*by Nicolas P. Rougier*](https://www.labri.fr/perso/nrougier/from-python-to-numpy/)
+* [エレガントなSciPy](https://www.amazon.com/Elegant-SciPy-Art-Scientific-Python/dp/1491922877) *by Juan Nunez-Iglesias, Stefan van der Walt, and Harriet Dashnow*
-You may also want to check out the [Goodreads list](https://www.goodreads.com/shelf/show/python-scipy) on the subject of "Python+SciPy." Most books there are about the "SciPy ecosystem," which has NumPy at its core.
+また、"Python+SciPy"を題材にした [おすすめリスト](https://www.goodreads.com/shelf/show/python-scipy) をもチェックしてみてください。 ほとんどの本にはNumPyを核とした「SciPyエコシステム」が説明されています。
- **Videos**
+ **動画**
-* [Introduction to Numerical Computing with NumPy](http://youtu.be/ZB7BZMhfPgk) *by Alex Chabot-Leclerc*
+* [Numpy を使った数値計算入門](http://youtu.be/ZB7BZMhfPgk) *by Alex Chabot-Leclerc*
***
-## Advanced
+## 上級者向け
-Try these advanced resources for a better understanding of NumPy concepts like advanced indexing, splitting, stacking, linear algebra, and more.
+より高度なインデックス作成、分割、スタック、線形代数など、Numpy の概念をより深く理解するためには、これらのリソースを試してみてください。
- **Tutorials**
+ **チュートリアル**
-* [100 NumPy Exercises](http://www.labri.fr/perso/nrougier/teaching/numpy.100/index.html) *by Nicolas P. Rougier*
-* [An Introduction to NumPy and Scipy](https://engineering.ucsb.edu/~shell/che210d/numpy.pdf) *by M. Scott Shell*
-* [Numpy Medkits](http://mentat.za.net/numpy/numpy_advanced_slides/) *by Stéfan van der Walt*
-* [NumPy in Python (Advanced)](https://www.geeksforgeeks.org/numpy-python-set-2-advanced/)
-* [Advanced Indexing](https://www.tutorialspoint.com/numpy/numpy_advanced_indexing.htm)
-* [Machine Learning and Data Analytics with NumPy](https://www.machinelearningplus.com/python/numpy-tutorial-python-part2/)
+* [NumPy 100演習](http://www.labri.fr/perso/nrougier/teaching/numpy.100/index.html) *Nicolas P. Rougier*
+* [NumPyとSciPyイントロダクション](https://engineering.ucsb.edu/~shell/che210d/numpy.pdf) *by M. Scott Shell*
+* [Numpy救急キット](http://mentat.za.net/numpy/numpy_advanced_slides/) *by Stéfan van der Walt*
+* [PythonにおけるNumPy (発展編)](https://www.geeksforgeeks.org/numpy-python-set-2-advanced/)
+* [高度なインデックシング](https://www.tutorialspoint.com/numpy/numpy_advanced_indexing.htm)
+* [NumPy による機械学習とデータ分析](https://www.machinelearningplus.com/python/numpy-tutorial-python-part2/)
- **Books**
+ **書籍**
-* [Python Data Science Handbook](https://www.amazon.com/Python-Data-Science-Handbook-Essential/dp/1491912057) *by Jake Vanderplas*
-* [Python for Data Analysis](https://www.amazon.com/Python-Data-Analysis-Wrangling-IPython/dp/1491957662) *by Wes McKinney*
-* [Numerical Python: Scientific Computing and Data Science Applications with Numpy, SciPy, and Matplotlib](https://www.amazon.com/Numerical-Python-Scientific-Applications-Matplotlib/dp/1484242459) *by Robert Johansson*
+* [Pythonデータサイエンスハンドブック](https://www.amazon.com/Python-Data-Science-Handbook-Essential/dp/1491912057) *by Jake Vanderplas*
+* [Pythonデータ解析](https://www.amazon.com/Python-Data-Analysis-Wrangling-IPython/dp/1491957662) *by Wes McKinney*
+* [数値解析Python: Numpy, SciPy, Matplotlibによる数値計算とデータサイエンスアプリケーション](https://www.amazon.com/Numerical-Python-Scientific-Applications-Matplotlib/dp/1484242459) *by Robert Johansson*
- **Videos**
+ **動画**
-* [Advanced NumPy - broadcasting rules, strides, and advanced indexing](https://www.youtube.com/watch?v=cYugp9IN1-Q) *by Juan Nunuz-Iglesias*
+* [アドバンスドNumPy -](https://www.youtube.com/watch?v=cYugp9IN1-Q) *ブロードキャストルール、ストライド、および高度なインデックシング* by Fan Nunuz-Iglesias
* [Advanced Indexing Operations in NumPy Arrays](https://www.youtube.com/watch?v=2WTDrSkQBng) *by Amuls Academy*
***
From b94963e4355861e8274c15be2dcb57427296b7d2 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sun, 21 Mar 2021 02:31:58 +0100
Subject: [PATCH 188/909] New translations learn.md (Japanese)
---
content/ja/learn.md | 22 +++++++++++-----------
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git a/content/ja/learn.md b/content/ja/learn.md
index 6e42b81f4c..665f16893c 100644
--- a/content/ja/learn.md
+++ b/content/ja/learn.md
@@ -60,25 +60,25 @@ NumPyについての資料は多数存在しています。 初心者の方に
**動画**
* [アドバンスドNumPy -](https://www.youtube.com/watch?v=cYugp9IN1-Q) *ブロードキャストルール、ストライド、および高度なインデックシング* by Fan Nunuz-Iglesias
-* [Advanced Indexing Operations in NumPy Arrays](https://www.youtube.com/watch?v=2WTDrSkQBng) *by Amuls Academy*
+* [NumPy配列における高度なインデクシング処理](https://www.youtube.com/watch?v=2WTDrSkQBng) *by Amuls Academy*
***
-## NumPy Talks
+## NumPyに関するトーク
-* [The Future of NumPy Indexing](https://www.youtube.com/watch?v=o0EacbIbf58) *by Jaime Fernández* (2016)
-* [Evolution of Array Computing in Python](https://www.youtube.com/watch?v=HVLPJnvInzM&t=10s) *by Ralf Gommers* (2019)
-* [NumPy: what has changed and what is going to change?](https://www.youtube.com/watch?v=YFLVQFjRmPY) *by Matti Picus* (2019)
-* [Inside NumPy](https://www.youtube.com/watch?v=dBTJD_FDVjU) *by Ralf Gommers, Sebastian Berg, Matti Picus, Tyler Reddy, Stefan van der Walt, Charles Harris* (2019)
-* [Brief Review of Array Computing in Python](https://www.youtube.com/watch?v=f176j2g2eNc) *by Travis Oliphant* (2019)
+* [Numpy Indexing の未来](https://www.youtube.com/watch?v=o0EacbIbf58) *by Jaime Fernadez* (2016)
+* [Python における配列計算革命](https://www.youtube.com/watch?v=HVLPJnvInzM&t=10s) *by Ralf Gommers* (2019)
+* [Numpy: 何が変わり、そして何が今後変わるのか?](https://www.youtube.com/watch?v=YFLVQFjRmPY) *by Matti Picus* (2019)
+* [NumPyの内部](https://www.youtube.com/watch?v=dBTJD_FDVjU) *by Ralf Gommers, Sebastian Berg, Matti Picus, Tyler Reddy, Stefan van der Walt, Charles Harris* (2019)
+* [Python における配列計算の概要](https://www.youtube.com/watch?v=f176j2g2eNc) *by Travis Oliphant* (2019)
***
-## Citing NumPy
+## NumPy を引用する場合
-If NumPy has been significant in your research, and you would like to acknowledge the project in your academic publication, please see [this citation information](/citing-numpy).
+もし、あなたの研究においてNumpyが重要な役割を果たし、論文でこのプロジェクトについて言及したい場合は、こちらの[ページ](/citing-numpy)を参照して下さい。
-## Contribute to this list
+## このページへの貢献
-To add to this collection, submit a recommendation [via a pull request](https://github.com/numpy/numpy.org/blob/master/content/en/learn.md). Say why your recommendation deserves mention on this page and also which audience would benefit most.
+このページのリストに新しいリンクを追加するには、[プルリクエスト](https://github.com/numpy/numpy.org/blob/master/content/en/learn.md)を使って提案してみて下さい。 あなたが推薦する情報が、このページで紹介するに値する理由と、その情報によってどのような人が最も恩恵を受けるかを説明して下さい。
From 00b8cc0008a786248b632359b5de16550d71c8e9 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sun, 21 Mar 2021 02:31:59 +0100
Subject: [PATCH 189/909] New translations news.md (Japanese)
---
content/ja/news.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/ja/news.md b/content/ja/news.md
index d45a2fbe06..9d6245b530 100644
--- a/content/ja/news.md
+++ b/content/ja/news.md
@@ -1,5 +1,5 @@
---
-title: News
+title: ニュース
sidebar: false
---
From 5420fb712987bf83c640eb900f90dca50b846bec Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Mon, 22 Mar 2021 00:37:38 +0100
Subject: [PATCH 190/909] New translations news.md (Japanese)
---
content/ja/news.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/content/ja/news.md b/content/ja/news.md
index 9d6245b530..da99c0b51f 100644
--- a/content/ja/news.md
+++ b/content/ja/news.md
@@ -3,9 +3,9 @@ title: ニュース
sidebar: false
---
-### Numpy 1.20.0 release
+### Numpy 1.20.0 リリース
-_Jan 30, 2021_ -- [NumPy 1.20.0](https://numpy.org/doc/stable/release/1.20.0-notes.html) is now available. This is the largest NumPy release to date, thanks to 180+ contributors. The two most exciting new features are:
+_2021年1月30日_ -- [Numpy 1.20.0](https://numpy.org/doc/stable/release/1.20.0-notes.html) が利用可能になりました。 今回のリリースは180以上のコントリビューターのおかげで、これまでで最大の Numpyのリリースとなりました。 最も重要な2つの新機能は次のとおりです。
- Type annotations for large parts of NumPy, and a new `numpy.typing` submodule containing `ArrayLike` and `DtypeLike` aliases that users and downstream libraries can use when adding type annotations in their own code.
- Multi-platform SIMD compiler optimizations, with support for x86 (SSE, AVX), ARM64 (Neon), and PowerPC (VSX) instructions. This yielded significant performance improvements for many functions (examples: [sin/cos](https://github.com/numpy/numpy/pull/17587), [einsum](https://github.com/numpy/numpy/pull/18194)).
From 2d16f16b609c18463506b78ae12e9ae41d5a27bc Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Mon, 22 Mar 2021 01:37:22 +0100
Subject: [PATCH 191/909] New translations news.md (Japanese)
---
content/ja/news.md | 22 +++++++++++-----------
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git a/content/ja/news.md b/content/ja/news.md
index da99c0b51f..0ebefd34e7 100644
--- a/content/ja/news.md
+++ b/content/ja/news.md
@@ -6,27 +6,27 @@ sidebar: false
### Numpy 1.20.0 リリース
_2021年1月30日_ -- [Numpy 1.20.0](https://numpy.org/doc/stable/release/1.20.0-notes.html) が利用可能になりました。 今回のリリースは180以上のコントリビューターのおかげで、これまでで最大の Numpyのリリースとなりました。 最も重要な2つの新機能は次のとおりです。
-- Type annotations for large parts of NumPy, and a new `numpy.typing` submodule containing `ArrayLike` and `DtypeLike` aliases that users and downstream libraries can use when adding type annotations in their own code.
-- Multi-platform SIMD compiler optimizations, with support for x86 (SSE, AVX), ARM64 (Neon), and PowerPC (VSX) instructions. This yielded significant performance improvements for many functions (examples: [sin/cos](https://github.com/numpy/numpy/pull/17587), [einsum](https://github.com/numpy/numpy/pull/18194)).
+- NumPyの大部分のコードに型注釈が追加されました。そして新しいサブモジュールである`numpy.typing`が追加されました。このサブモジュールは`ArrayLike` や`DtypeLike`という型注釈のエイリアスが定義されており、これによりユーザーやダウンストリームのライブラリはこの型注釈を使うことができます。
+- X86(SSE、AVX)、ARM64(Neon)、およびPowerPC (VSX) 命令をサポートするマルチプラットフォームSIMDコンパイラの最適化が実施されました。 これにより、多くの関数で大きく パフォーマンスが向上しました (例: [sin/cos](https://github.com/numpy/numpy/pull/17587), [einsum](https://github.com/numpy/numpy/pull/18194)).
-### Diversity in the NumPy project
+### NumPyプロジェクトの多様性
-_Sep 20, 2020_ -- We wrote a [statement on the state of, and discussion on social media around, diversity and inclusion in the NumPy project](/diversity_sep2020).
+_2020年9月20日に_ 、私達は[ NumPyプロジェクトにおけるダイバーシティやインクルージョンの状況や、ソーシャルメディア上での議論についての宣言 ](/diversity_sep2020)について書きました。
-### First official NumPy paper published in Nature!
+### Natureに初めての公式のNumPy論文が掲載されました!
-_Sep 16, 2020_ -- We are pleased to announce the publication of [the first official paper on NumPy](https://www.nature.com/articles/s41586-020-2649-2) as a review article in Nature. This comes 14 years after the release of NumPy 1.0. The paper covers applications and fundamental concepts of array programming, the rich scientific Python ecosystem built on top of NumPy, and the recently added array protocols to facilitate interoperability with external array and tensor libraries like CuPy, Dask, and JAX.
+_2020年9月16日_ -- NumPyに関する最初の公式の論文 [](https://www.nature.com/articles/s41586-020-2649-2) が査読付き論文として掲載されました。 これはNumPy 1.0のリリースから14年後のことになります。 この論文では、配列プログラミングのアプリケーションと基本的なコンセプト、NumPyの上に構築された様々な科学的Pythonエコシステム、そしてCuPy、Dask、JAXのような外部の配列およびテンソルライブラリとの相互運用を容易にするために最近追加された配列プロトコルについて説明しています。
-### Python 3.9 is coming, when will NumPy release binary wheels?
+### Python 3.9 が登場し、Numpy はいつバイナリホイールをリリースするのか?
-_Sept 14, 2020_ -- Python 3.9 will be released in a few weeks. If you are an early adopter of Python versions, you may be dissapointed to find that NumPy (and other binary packages like SciPy) will not have binary wheels ready on the day of the release. It is a major effort to adapt the build infrastructure to a new Python version and it typically takes a few weeks for the packages to appear on PyPI and conda-forge. In preparation for this event, please make sure to
-- update your `pip` to version 20.1 at least to support `manylinux2010` and `manylinux2014`
-- use [`--only-binary=numpy`](https://pip.pypa.io/en/stable/reference/pip_install/#cmdoption-only-binary) or `--only-binary=:all:` to prevent `pip` from trying to build from source.
+_2020年9月14日_ -- Python 3.9 は数週間後にリリースされる予定です。 もしあなたが新しいPythonのバージョンをいち早く取り入れているのであれば、NumPy(およびSciPyのような他のパッケージ)がリリース当日にバイナリホイールを用意していないことを知ってがっかりしたかもしれません。 ビルドインフラを新しいPythonのバージョンに適応させるのは大変な作業で、PyPIやconda-forgeにパッケージが掲載されるまでには通常数週間かかります。 ホイールリリースのイベントに備えて、以下を確認してください。
+- `pip` が`manylinux2010` と `manylinux2014` をサポートするためにpipを少なくともバージョン 20.1 に更新する。
+- [`--only-binary=numpy`](https://pip.pypa.io/en/stable/reference/pip_install/#cmdoption-only-binary) または `--only-binary=:all:` を`pip`がソースからビルドしようとするのを防ぐために使用します。
-### Numpy 1.19.2 release
+### Numpy 1.19.2 リリース
_Sep 10, 2020_ -- [NumPy 1.19.2](https://numpy.org/devdocs/release/1.19.2-notes.html) is now available. This latest release in the 1.19 series fixes several bugs, prepares for the [upcoming Cython 3.x release](http://docs.cython.org/en/latest/src/changes.html) and pins setuptools to keep distutils working while upstream modifications are ongoing. The aarch64 wheels are built with the latest manylinux2014 release that fixes the problem of differing page sizes used by different linux distros.
From 92a08830fc5ef623df44df6158e880b9a9db1b8f Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Mon, 22 Mar 2021 02:35:46 +0100
Subject: [PATCH 192/909] New translations news.md (Japanese)
---
content/ja/news.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/content/ja/news.md b/content/ja/news.md
index 0ebefd34e7..90e71b7b9e 100644
--- a/content/ja/news.md
+++ b/content/ja/news.md
@@ -28,11 +28,11 @@ _2020年9月14日_ -- Python 3.9 は数週間後にリリースされる予定
### Numpy 1.19.2 リリース
-_Sep 10, 2020_ -- [NumPy 1.19.2](https://numpy.org/devdocs/release/1.19.2-notes.html) is now available. This latest release in the 1.19 series fixes several bugs, prepares for the [upcoming Cython 3.x release](http://docs.cython.org/en/latest/src/changes.html) and pins setuptools to keep distutils working while upstream modifications are ongoing. The aarch64 wheels are built with the latest manylinux2014 release that fixes the problem of differing page sizes used by different linux distros.
+_2020年1月10日_ -- [Numpy 19.2.0](https://numpy.org/devdocs/release/1.19.2-notes.html) がリリースされました。 この 1.19 シリーズの最新リリースでは、いくつかのバグが修正され、[来るべき Cython 3.xリリース](http:/docs.cython.orgenlatestsrcchanges.html)への準備が行われ、アップストリームの修正が進行中の間も distutils の動作を維持するためのsetuptoolsの固定がされています。 aarch64ホイールは最新のmanylinux2014リリースで構築されており、異なるLinuxディストリビューションで使用される異なるページサイズの問題を修正しています。
-### The inaugural NumPy survey is live!
+### 初めてのNumPyの調査が公開されました!!
-_Jul 2, 2020_ -- This survey is meant to guide and set priorities for decision-making about the development of NumPy as software and as a community. The survey is available in 8 additional languages besides English: Bangla, Hindi, Japanese, Mandarin, Portuguese, Russian, Spanish and French.
+_2020年7月2日_ -- このサーベイは、ソフトウェアとして、またコミュニティとしてのNumPyの開発に関する意思決定の指針となり、優先順位を設定するためのものになりました。 この調査結果は英語以外の8つの言語で利用可能です: バングラ, ヒンディー語, 日本語, マンダリン, ポルトガル語, ロシア語, スペイン語とフランス語.
Please help us make NumPy better and take the survey [here](https://umdsurvey.umd.edu/jfe/form/SV_8bJrXjbhXf7saAl).
From 1fb1e3ec9206298d1b6533eee9fa6b39257b7ed9 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Mon, 22 Mar 2021 08:33:21 +0100
Subject: [PATCH 193/909] New translations news.md (Japanese)
---
content/ja/news.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/ja/news.md b/content/ja/news.md
index 90e71b7b9e..1f63d97a9e 100644
--- a/content/ja/news.md
+++ b/content/ja/news.md
@@ -34,7 +34,7 @@ _2020年1月10日_ -- [Numpy 19.2.0](https://numpy.org/devdocs/release/1.19.2-no
_2020年7月2日_ -- このサーベイは、ソフトウェアとして、またコミュニティとしてのNumPyの開発に関する意思決定の指針となり、優先順位を設定するためのものになりました。 この調査結果は英語以外の8つの言語で利用可能です: バングラ, ヒンディー語, 日本語, マンダリン, ポルトガル語, ロシア語, スペイン語とフランス語.
-Please help us make NumPy better and take the survey [here](https://umdsurvey.umd.edu/jfe/form/SV_8bJrXjbhXf7saAl).
+NumPy をより良くするために、こちらの [アンケート](https://umdsurvey. umd. edu/jfe/form/SV_8bJrXjbhXf7saAl) に協力してもらえると嬉しいです。
### NumPy has a new logo!
From 05d2981cfc094fae6b66f8e493c9a3b347aaf515 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Mon, 22 Mar 2021 09:29:59 +0100
Subject: [PATCH 194/909] New translations news.md (Japanese)
---
content/ja/news.md | 56 +++++++++++++++++++++++-----------------------
1 file changed, 28 insertions(+), 28 deletions(-)
diff --git a/content/ja/news.md b/content/ja/news.md
index 1f63d97a9e..23413d7de7 100644
--- a/content/ja/news.md
+++ b/content/ja/news.md
@@ -37,53 +37,53 @@ _2020年7月2日_ -- このサーベイは、ソフトウェアとして、ま
NumPy をより良くするために、こちらの [アンケート](https://umdsurvey. umd. edu/jfe/form/SV_8bJrXjbhXf7saAl) に協力してもらえると嬉しいです。
-### NumPy has a new logo!
+### Numpy に新しいロゴができました!
-_Jun 24, 2020_ -- NumPy now has a new logo:
+_2020年6月24日_ -- NumPy に新しいロゴが作成されました:
-
+
-The logo is a modern take on the old one, with a cleaner design. Thanks to Isabela Presedo-Floyd for designing the new logo, as well as to Travis Vaught for the old logo that served us well for 15+ years.
+新しいロゴは、古いもの比べてモダンで、よりクリーンなデザインになりました。 新しいロゴをデザインしてくれたIsabela Presedo-Floydと、15年以上にわたって使用してきた旧ロゴをデザインしてくれたTravis Vaughtに感謝します。
-### NumPy 1.19.0 release
+### Numpy 1.19.0 リリース
-_Jun 20, 2020_ -- NumPy 1.19.0 is now available. This is the first release without Python 2 support, hence it was a "clean-up release". The minimum supported Python version is now Python 3.6. An important new feature is that the random number generation infrastructure that was introduced in NumPy 1.17.0 is now accessible from Cython.
+_2020年6月20日_ -- NumPy 1.19.0 が利用可能になりました。 これのリリースは Python 2系のサポートがない最初のリリースであり、"クリーンアップ用のリリース" です。 サポートされている一番古いPython のバージョンは Python 3.6 になりました。 今回の重要な新機能は、NumPy 1.17.0で導入された乱数生成用のインフラにCythonからアクセスできるようになったことです。
-### Season of Docs acceptance
+### ドキュメント受諾期間
-_May 11, 2020_ -- NumPy has been accepted as one of the mentor organizations for the Google Season of Docs program. We are excited about the opportunity to work with a technical writer to improve NumPy's documentation once again! For more details, please see [the official Season of Docs site](https://developers.google.com/season-of-docs/) and our [ideas page](https://github.com/numpy/numpy/wiki/Google-Season-of-Docs-2020-Project-Ideas).
+_2020年5月11日_ -- NumPyは、 Googleのシーズンオブドキュメントプログラムのメンター団体の1つとして選ばれました。 NumPy のドキュメントを改善するために、テクニカルライターと協力する機会を楽しみにしています! 詳細については、 [公式ドキュメントサイト](https://developers.google.com/season-of-docs/) と [アイデアページ](https://github.com/numpy/numpy/wiki/Google-Season-of-Docs-2020-Project-Ideas) をご覧ください。
-### NumPy 1.18.0 release
+### Numpy 1.18.0 リリース
-_Dec 22, 2019_ -- NumPy 1.18.0 is now available. After the major changes in 1.17.0, this is a consolidation release. It is the last minor release that will support Python 3.5. Highlights of the release includes the addition of basic infrastructure for linking with 64-bit BLAS and LAPACK libraries, and a new C-API for `numpy.random`.
+_2019年12月22日_ -- Numpy 1.18.0 が利用可能になりました。 このリリースは、1.17.0の主要な変更の後の、統合的なリリースです。 Python 3.5 をサポートする最後のマイナーリリースになります。 今回のリリースでは、64ビットのBLASおよびLAPACKライブラリとリンクするためのインフラの追加や、`numpy.random`のための新しいC-APIの追加などが行われました。
-Please see the [release notes](https://github.com/numpy/numpy/releases/tag/v1.18.0) for more details.
+詳細については、 [リリース ノート](https://github.com/numpy/numpy/releases/tag/v1.18.0) を参照してください。
-### NumPy receives a grant from the Chan Zuckerberg Initiative
+### NumPyはChan Zuckerberg財団から助成金を受けました。
-_Nov 15, 2019_ -- We are pleased to announce that NumPy and OpenBLAS, one of NumPy's key dependencies, have received a joint grant for $195,000 from the Chan Zuckerberg Initiative through their [Essential Open Source Software for Science program](https://chanzuckerberg.com/eoss/) that supports software maintenance, growth, development, and community engagement for open source tools critical to science.
+_2019年11月15日_ -- NumPyと、NumPyの重要な依存関係の1つであるOpenBLASが、Chan Zuckerberg財団の[Essential Open Source Software for Scienceプログラム](https:/chanzuckerberg.comeoss)を通じて、科学に不可欠なオープンソースツールのソフトウェアのメンテナンス、成長、開発、コミュニティへの参加を支援する195,000ドルの共同助成金を獲得したことを発表しました。
-This grant will be used to ramp up the efforts in improving NumPy documentation, website redesign, and community development to better serve our large and rapidly growing user base, and ensure the long-term sustainability of the project. While the OpenBLAS team will focus on addressing sets of key technical issues, in particular thread-safety, AVX-512, and thread-local storage (TLS) issues, as well as algorithmic improvements in ReLAPACK (Recursive LAPACK) on which OpenBLAS depends.
+この助成金は、Numpy ドキュメント、ウェブサイトの再設計の改善に向けた取り組みを促進するために使用されます。 大規模かつ急速に拡大するユーザー基盤をより良くし、プロジェクトの長期的な持続可能性を確保するためのコミュニティ開発を行っていきます。 OpenBLASチームは、技術的に重要な問題、特にスレッド安全性、AVX-512に対処することに焦点を当てます。 また、スレッドローカルストレージ(TLS) の問題や、OpenBLASが依存するReLAPACK(再帰的なLAPACK) のアルゴリズムの改善も行っています。
-More details on our proposed initiatives and deliverables can be found in the [full grant proposal](https://figshare.com/articles/Proposal_NumPy_OpenBLAS_for_Chan_Zuckerberg_Initiative_EOSS_2019_round_1/10302167). The work is scheduled to start on Dec 1st, 2019 and continue for the next 12 months.
+提案されたイニシアチブと成果物の詳細については、 [フルグラントプロポーザル](https://figshare.com/articles/Proposal_NumPy_OpenBLAS_for_Chan_Zuckerberg_Initiative_EOSS_2019_round_1/10302167) を参照してください。 この取り組みは2019年12月1日から始まり、今後12ヶ月間継続される予定です。
-## Releases
+## 過去のリリース
-Here is a list of NumPy releases, with links to release notes. All bugfix releases (only the `z` changes in the `x.y.z` version number) have no new features; minor releases (the `y` increases) do.
+こちらがより過去のNumPy リリースのリストで、各リリースノートへのリンクが記載されています。 全てのバグフィックスリリース(バージョン番号`x.y.z` の`z`だけが変更されたもの)は新しい機能追加はされず、マイナーリリース (`y` が増えたもの)は、新しい機能追加されています。
-- NumPy 1.18.4 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.18.4)) -- _3 May 2020_.
-- NumPy 1.18.3 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.18.3)) -- _19 Apr 2020_.
-- NumPy 1.18.2 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.18.2)) -- _17 Mar 2020_.
-- NumPy 1.18.1 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.18.1)) -- _6 Jan 2020_.
-- NumPy 1.17.5 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.17.5)) -- _1 Jan 2020_.
-- NumPy 1.18.0 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.18.0)) -- _22 Dec 2019_.
-- NumPy 1.17.4 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.17.4)) -- _11 Nov 2019_.
-- NumPy 1.17.0 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.17.0)) -- _26 Jul 2019_.
-- NumPy 1.16.0 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.16.0)) -- _14 Jan 2019_.
-- NumPy 1.15.0 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.15.0)) -- _23 Jul 2018_.
-- NumPy 1.14.0 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.14.0)) -- _7 Jan 2018_.
+- NumPy 1.18.4 ([リリースノート](https://github.com/numpy/numpy/releases/tag/v1.18.4)) -- _2020年5月3日_.
+- NumPy 1.18.4 ([リリースノート](https://github.com/numpy/numpy/releases/tag/v1.18.4)) -- _2020年4月19日_.
+- NumPy 1.18.2 ([リリースノート](https://github.com/numpy/numpy/releases/tag/v1.18.2)) -- _2020年3月17日_.
+- NumPy 1.18.1 ([リリースノート](https://github.com/numpy/numpy/releases/tag/v1.18.1)) -- _2020年1月6日_.
+- NumPy 1.17.5 ([リリースノート](https://github.com/numpy/numpy/releases/tag/v1.17.5)) -- _2020年1月1日_.
+- NumPy 1.18.0 ([リリースノート](https://github.com/numpy/numpy/releases/tag/v1.18.0)) -- _2019年12月22日_.
+- NumPy 1.17.4 ([リリースノート](https://github.com/numpy/numpy/releases/tag/v1.17.4)) -- _2019年10月11日_.
+- NumPy 1.17.0 ([リリースノート](https://github.com/numpy/numpy/releases/tag/v1.17.0)) -- _2019年7月26日_.
+- NumPy 1.16.0 ([リリースノート](https://github.com/numpy/numpy/releases/tag/v1.16.0)) -- _2019年1月14日_.
+- NumPy 1.15.0 ([リリースノート](https://github.com/numpy/numpy/releases/tag/v1.15.0)) -- _2018年7月23日_.
+- NumPy 1.14.0 ([リリースノート](https://github.com/numpy/numpy/releases/tag/v1.14.0)) -- _2018年1月7日_.
From 97c8b7fb4785f8357131f239f78eb0f40b198969 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Mon, 22 Mar 2021 09:30:01 +0100
Subject: [PATCH 195/909] New translations report-handling-manual.md (Japanese)
---
content/ja/report-handling-manual.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/ja/report-handling-manual.md b/content/ja/report-handling-manual.md
index 5586668cba..d29fe66471 100644
--- a/content/ja/report-handling-manual.md
+++ b/content/ja/report-handling-manual.md
@@ -1,5 +1,5 @@
---
-title: NumPy Code of Conduct - How to follow up on a report
+title: NumPy行動規範 - 報告書のフォローアップ方法
sidebar: false
---
From cf0cb76f7c5d9405e1dfff5f5a2b6cfebaa1b948 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Tue, 23 Mar 2021 07:56:50 +0100
Subject: [PATCH 196/909] New translations report-handling-manual.md (Japanese)
---
content/ja/report-handling-manual.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/content/ja/report-handling-manual.md b/content/ja/report-handling-manual.md
index d29fe66471..071d9bb036 100644
--- a/content/ja/report-handling-manual.md
+++ b/content/ja/report-handling-manual.md
@@ -3,11 +3,11 @@ title: NumPy行動規範 - 報告書のフォローアップ方法
sidebar: false
---
-This is the manual followed by NumPy’s Code of Conduct Committee. It’s used when we respond to an issue to make sure we’re consistent and fair.
+NumPyの行動規範委員会はこのマニュアルに従います。 このマニュアルは様々な問題に対応する際に使用され、一貫性と公平性を確保します。
-Enforcing the [Code of Conduct](/code-of-conduct) impacts our community today and for the future. It’s an action that we do not take lightly. When reviewing enforcement measures, the Code of Conduct Committee will keep the following values and guidelines in mind:
+[行動規範](/code-of-conduct) を施行することは、私たちのコミュニティの現在と未来に重要です。 私達はこのルールを重く受け止めています。 施行措置の見直しに際しては、行動規範委員会は以下の考え方とガイドラインに留意するようにします。
-* Act in a personal manner rather than impersonal. The Committee can engage the parties to understand the situation while respecting the privacy and any necessary confidentiality of reporters. However, sometimes it is necessary to communicate with one or more individuals directly: the Committee’s goal is to improve the health of our community rather than only produce a formal decision.
+* 機械的ではなく、人間的に行動します。 The Committee can engage the parties to understand the situation while respecting the privacy and any necessary confidentiality of reporters. However, sometimes it is necessary to communicate with one or more individuals directly: the Committee’s goal is to improve the health of our community rather than only produce a formal decision.
* Emphasize empathy for individuals rather than judging behavior, avoiding binary labels of “good” and “bad/evil”. Overt, clear-cut aggression and harassment exist, and we will address them firmly. But many scenarios that can prove challenging to resolve are those where normal disagreements devolve into unhelpful or harmful behavior from multiple parties. Understanding the full context and finding a path that re-engages all is hard, but ultimately the most productive for our community.
* We understand that email is a difficult medium and can be isolating. Receiving criticism over email, without personal contact, can be particularly painful. This makes it especially important to keep an atmosphere of open-minded respect for the views of others. It also means that we must be transparent in our actions, and that we will do everything in our power to make sure that all our members are treated fairly and with sympathy.
* Discrimination can be subtle and it can be unconscious. It can show itself as unfairness and hostility in otherwise ordinary interactions. We know that this does occur, and we will take care to look out for it. We would very much like to hear from you if you feel you have been treated unfairly, and we will use these procedures to make sure that your complaint is heard and addressed.
From a448cb60ca96ea76ad8380b51930519b74f648de Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Tue, 23 Mar 2021 08:55:48 +0100
Subject: [PATCH 197/909] New translations report-handling-manual.md (Japanese)
---
content/ja/report-handling-manual.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/content/ja/report-handling-manual.md b/content/ja/report-handling-manual.md
index 071d9bb036..3c0b5011fa 100644
--- a/content/ja/report-handling-manual.md
+++ b/content/ja/report-handling-manual.md
@@ -7,9 +7,9 @@ NumPyの行動規範委員会はこのマニュアルに従います。 この
[行動規範](/code-of-conduct) を施行することは、私たちのコミュニティの現在と未来に重要です。 私達はこのルールを重く受け止めています。 施行措置の見直しに際しては、行動規範委員会は以下の考え方とガイドラインに留意するようにします。
-* 機械的ではなく、人間的に行動します。 The Committee can engage the parties to understand the situation while respecting the privacy and any necessary confidentiality of reporters. However, sometimes it is necessary to communicate with one or more individuals directly: the Committee’s goal is to improve the health of our community rather than only produce a formal decision.
-* Emphasize empathy for individuals rather than judging behavior, avoiding binary labels of “good” and “bad/evil”. Overt, clear-cut aggression and harassment exist, and we will address them firmly. But many scenarios that can prove challenging to resolve are those where normal disagreements devolve into unhelpful or harmful behavior from multiple parties. Understanding the full context and finding a path that re-engages all is hard, but ultimately the most productive for our community.
-* We understand that email is a difficult medium and can be isolating. Receiving criticism over email, without personal contact, can be particularly painful. This makes it especially important to keep an atmosphere of open-minded respect for the views of others. It also means that we must be transparent in our actions, and that we will do everything in our power to make sure that all our members are treated fairly and with sympathy.
+* 機械的ではなく、人間的に行動します。 委員会は、当事者にプライバシーと報告者に必要な機密性を尊重しながら、状況を理解するように働きかけることができます. ただし、 1人以上の個人と直接連絡を取る必要がある場合もあります:委員会の目標は正しい決定を下すのではなく、コミュニティの健康を改善することなのです。
+* 行動を判断するのではなく、個人への共感を強調し、「良い」と「悪い」のバイナリラベルを避けようとします。 明確な攻撃性とハラスメントが存在した場合、私たちはそれらに対処します。 しかし、解決が困難なシナリオの多くは、通常の意見の相違が、複数の当事者による無益または有害な行動に発展した場合です。 完全な文脈を理解し、すべてを再び元に戻す道を見つけることは困難ですが、最終的にはコミュニティにとって最も生産的になると考えています。
+* 私たちは、電子メールが判断に困難な媒体であり、分けて利用できることを理解しています。 個人的な連絡なしで電子メール上で批判を受けることは特に苦痛である場合もあるのです。 This makes it especially important to keep an atmosphere of open-minded respect for the views of others. It also means that we must be transparent in our actions, and that we will do everything in our power to make sure that all our members are treated fairly and with sympathy.
* Discrimination can be subtle and it can be unconscious. It can show itself as unfairness and hostility in otherwise ordinary interactions. We know that this does occur, and we will take care to look out for it. We would very much like to hear from you if you feel you have been treated unfairly, and we will use these procedures to make sure that your complaint is heard and addressed.
* Help increase engagement in good discussion practice: try to identify where discussion may have broken down, and provide actionable information, pointers, and resources that can lead to positive change on these points.
* Be mindful of the needs of new members: provide them with explicit support and consideration, with the aim of increasing participation from underrepresented groups in particular.
From 43448ee8b0278ae9782503194da8fb7a45c1d38b Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Wed, 24 Mar 2021 00:02:53 +0100
Subject: [PATCH 198/909] New translations report-handling-manual.md (Japanese)
---
content/ja/report-handling-manual.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/ja/report-handling-manual.md b/content/ja/report-handling-manual.md
index 3c0b5011fa..66053242ed 100644
--- a/content/ja/report-handling-manual.md
+++ b/content/ja/report-handling-manual.md
@@ -9,7 +9,7 @@ NumPyの行動規範委員会はこのマニュアルに従います。 この
* 機械的ではなく、人間的に行動します。 委員会は、当事者にプライバシーと報告者に必要な機密性を尊重しながら、状況を理解するように働きかけることができます. ただし、 1人以上の個人と直接連絡を取る必要がある場合もあります:委員会の目標は正しい決定を下すのではなく、コミュニティの健康を改善することなのです。
* 行動を判断するのではなく、個人への共感を強調し、「良い」と「悪い」のバイナリラベルを避けようとします。 明確な攻撃性とハラスメントが存在した場合、私たちはそれらに対処します。 しかし、解決が困難なシナリオの多くは、通常の意見の相違が、複数の当事者による無益または有害な行動に発展した場合です。 完全な文脈を理解し、すべてを再び元に戻す道を見つけることは困難ですが、最終的にはコミュニティにとって最も生産的になると考えています。
-* 私たちは、電子メールが判断に困難な媒体であり、分けて利用できることを理解しています。 個人的な連絡なしで電子メール上で批判を受けることは特に苦痛である場合もあるのです。 This makes it especially important to keep an atmosphere of open-minded respect for the views of others. It also means that we must be transparent in our actions, and that we will do everything in our power to make sure that all our members are treated fairly and with sympathy.
+* 私たちは、電子メールが判断に困難な媒体であり、分けて利用できることを理解しています。 個人的な連絡なしで電子メール上で批判を受けることは特に苦痛である場合もあるのです。 ここでは他者の見解に対して、開放的で、敬意を持った雰囲気を保つことが重要になります。 それはまた、私たちの行動が透明でなければならないことを意味します。全てのメンバーが公平かつ同情をもって扱われるようにするため、 我々は全力を尽くします
* Discrimination can be subtle and it can be unconscious. It can show itself as unfairness and hostility in otherwise ordinary interactions. We know that this does occur, and we will take care to look out for it. We would very much like to hear from you if you feel you have been treated unfairly, and we will use these procedures to make sure that your complaint is heard and addressed.
* Help increase engagement in good discussion practice: try to identify where discussion may have broken down, and provide actionable information, pointers, and resources that can lead to positive change on these points.
* Be mindful of the needs of new members: provide them with explicit support and consideration, with the aim of increasing participation from underrepresented groups in particular.
From 5cb2392819eeaa5d99a2f052c8f1641c47dd0d27 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Wed, 24 Mar 2021 01:05:42 +0100
Subject: [PATCH 199/909] New translations report-handling-manual.md (Japanese)
---
content/ja/report-handling-manual.md | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/content/ja/report-handling-manual.md b/content/ja/report-handling-manual.md
index 66053242ed..045cbf3548 100644
--- a/content/ja/report-handling-manual.md
+++ b/content/ja/report-handling-manual.md
@@ -10,13 +10,13 @@ NumPyの行動規範委員会はこのマニュアルに従います。 この
* 機械的ではなく、人間的に行動します。 委員会は、当事者にプライバシーと報告者に必要な機密性を尊重しながら、状況を理解するように働きかけることができます. ただし、 1人以上の個人と直接連絡を取る必要がある場合もあります:委員会の目標は正しい決定を下すのではなく、コミュニティの健康を改善することなのです。
* 行動を判断するのではなく、個人への共感を強調し、「良い」と「悪い」のバイナリラベルを避けようとします。 明確な攻撃性とハラスメントが存在した場合、私たちはそれらに対処します。 しかし、解決が困難なシナリオの多くは、通常の意見の相違が、複数の当事者による無益または有害な行動に発展した場合です。 完全な文脈を理解し、すべてを再び元に戻す道を見つけることは困難ですが、最終的にはコミュニティにとって最も生産的になると考えています。
* 私たちは、電子メールが判断に困難な媒体であり、分けて利用できることを理解しています。 個人的な連絡なしで電子メール上で批判を受けることは特に苦痛である場合もあるのです。 ここでは他者の見解に対して、開放的で、敬意を持った雰囲気を保つことが重要になります。 それはまた、私たちの行動が透明でなければならないことを意味します。全てのメンバーが公平かつ同情をもって扱われるようにするため、 我々は全力を尽くします
-* Discrimination can be subtle and it can be unconscious. It can show itself as unfairness and hostility in otherwise ordinary interactions. We know that this does occur, and we will take care to look out for it. We would very much like to hear from you if you feel you have been treated unfairly, and we will use these procedures to make sure that your complaint is heard and addressed.
-* Help increase engagement in good discussion practice: try to identify where discussion may have broken down, and provide actionable information, pointers, and resources that can lead to positive change on these points.
-* Be mindful of the needs of new members: provide them with explicit support and consideration, with the aim of increasing participation from underrepresented groups in particular.
-* Individuals come from different cultural backgrounds and native languages. Try to identify any honest misunderstandings caused by a non-native speaker and help them understand the issue and what they can change to avoid causing offence. Complex discussion in a foreign language can be very intimidating, and we want to grow our diversity also across nationalities and cultures.
+* 差別というのは明確には断定できないことがあり、無意識で実施されている場合もあります。 これにより、普通の人との関わりの中で、不公平感や敵意として現れてくるのです。 私達は、このようなことが起こることはわかっているので、気をつけて見ていきたいと思います。 不当な扱いを受けたと思われる方は、ぜひご連絡ください。
+* 良い議論を実践することで、エンゲージメントの向上に取り組みます。: 例えば議論がどこで止まっているのかを特定したり、 実践的な情報、指針、資源を提供することで、これらの問題を前向きな方向に変えていきます。
+* 新メンバーのニーズに留意し、特に社会的地位の低いグループからの参加を増やすことを目的に、明確なサポートと配慮を提供していきます。
+* 一人一人の文化的背景や母国語は異なります。 ネイティブでない人が起こした悪気のない誤解を確認し、問題を理解してもらい、不快感を与えないために何を変えればよいかを教えてあげてください。 外国語での複雑な議論はとても難しいものであり、国籍や文化を超えて多様性を育てていきたいと考えています。
-## Mediation
+## 仲介
Voluntary informal mediation is a tool at our disposal. In contexts such as when two or more parties have all escalated to the point of inappropriate behavior (something sadly common in human conflict), it may be useful to facilitate a mediation process. This is only an example: the Committee can consider mediation in any case, mindful that the process is meant to be strictly voluntary and no party can be pressured to participate. If the Committee suggests mediation, it should:
From b65bd5866abf034b3af203473d0406781a25fe6a Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Wed, 24 Mar 2021 09:16:10 +0100
Subject: [PATCH 200/909] New translations report-handling-manual.md (Japanese)
---
content/ja/report-handling-manual.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/content/ja/report-handling-manual.md b/content/ja/report-handling-manual.md
index 045cbf3548..25110dff82 100644
--- a/content/ja/report-handling-manual.md
+++ b/content/ja/report-handling-manual.md
@@ -18,10 +18,10 @@ NumPyの行動規範委員会はこのマニュアルに従います。 この
## 仲介
-Voluntary informal mediation is a tool at our disposal. In contexts such as when two or more parties have all escalated to the point of inappropriate behavior (something sadly common in human conflict), it may be useful to facilitate a mediation process. This is only an example: the Committee can consider mediation in any case, mindful that the process is meant to be strictly voluntary and no party can be pressured to participate. If the Committee suggests mediation, it should:
+自主的な非公式の調停は、私たちの重要な役割です。 2つのグループ以上の当事者が不適切な行動をエスカレートした場合(人類の紛争では悲しいことに一般的なものですが)、調停プロセスを促進するは非常に重要です。 ちなみに、これは一例に過ぎません。委員会は、どのようなケースでも調停を検討することができますが、このプロセスはあくまでも自発的なものであり、当事者に参加を迫ることはできないことを念頭に置いて下さい。 委員会が調停を提案する場合は、次のようにすべきです。
-* Find a candidate who can serve as a mediator.
-* Obtain the agreement of the reporter(s). The reporter(s) have complete freedom to decline the mediation idea or to propose an alternate mediator.
+* 調停者として役立つ候補者を見つけます。
+* 報告者の合意を取得します。 The reporter(s) have complete freedom to decline the mediation idea or to propose an alternate mediator.
* Obtain the agreement of the reported person(s).
* Settle on the mediator: while parties can propose a different mediator than the suggested candidate, only if a common agreement is reached on all terms can the process move forward.
* Establish a timeline for mediation to complete, ideally within two weeks.
From e3b653050a4c7a8060bc1cdeab5dcf94a9307c07 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Wed, 24 Mar 2021 10:14:36 +0100
Subject: [PATCH 201/909] New translations report-handling-manual.md (Japanese)
---
content/ja/report-handling-manual.md | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/content/ja/report-handling-manual.md b/content/ja/report-handling-manual.md
index 25110dff82..5ccee2b2b5 100644
--- a/content/ja/report-handling-manual.md
+++ b/content/ja/report-handling-manual.md
@@ -21,15 +21,15 @@ NumPyの行動規範委員会はこのマニュアルに従います。 この
自主的な非公式の調停は、私たちの重要な役割です。 2つのグループ以上の当事者が不適切な行動をエスカレートした場合(人類の紛争では悲しいことに一般的なものですが)、調停プロセスを促進するは非常に重要です。 ちなみに、これは一例に過ぎません。委員会は、どのようなケースでも調停を検討することができますが、このプロセスはあくまでも自発的なものであり、当事者に参加を迫ることはできないことを念頭に置いて下さい。 委員会が調停を提案する場合は、次のようにすべきです。
* 調停者として役立つ候補者を見つけます。
-* 報告者の合意を取得します。 The reporter(s) have complete freedom to decline the mediation idea or to propose an alternate mediator.
-* Obtain the agreement of the reported person(s).
-* Settle on the mediator: while parties can propose a different mediator than the suggested candidate, only if a common agreement is reached on all terms can the process move forward.
-* Establish a timeline for mediation to complete, ideally within two weeks.
+* 報告者の合意を取得します。 報告者は、調停のアイデアを拒否したり、代替の調停者を提案する権利を持ちます。
+* 報告者の同意を取得します。
+* 調停人の決定:当事者は、提案された候補者とは別の調停人を提案することができ、すべての条件で共通の合意に達した場合のみ、プロセスを進めることができます。
+* 調停が完了するまでのタイムラインを設定し、理想的には2週間以内に完了させます。
-The mediator will engage with all the parties and seek a resolution that is satisfactory to all. Upon completion, the mediator will provide a report (vetted by all parties to the process) to the Committee, with recommendations on further steps. The Committee will then evaluate these results (whether a satisfactory resolution was achieved or not) and decide on any additional action deemed necessary.
+調停者は、すべての当事者と関わり、すべての人に満足のいく決議を求めていきます。 終了後、調停人は(プロセスの全当事者によって吟味された)報告書を委員会に提出し、今後のステップに関する推奨事項を提示します。 委員会は、これらの結果(満足のいく決議が達成されたか否か) を評価し、必要と判断される追加的な措置を決定します。
-## How the Committee will respond to reports
+## 報告に対する委員会の対応
When the Committee (or a Committee member) receives a report, they will first determine whether the report is about a clear and severe breach (as defined below). If so, immediate action needs to be taken in addition to the regular report handling process.
From d42844ec4cdc4fb5ddb40e90ed03faef9ee27cb3 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Wed, 24 Mar 2021 21:36:18 +0100
Subject: [PATCH 202/909] New translations blackhole-image.md (Spanish)
---
content/es/case-studies/blackhole-image.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/content/es/case-studies/blackhole-image.md b/content/es/case-studies/blackhole-image.md
index 2906e12ece..47ca6e5a19 100644
--- a/content/es/case-studies/blackhole-image.md
+++ b/content/es/case-studies/blackhole-image.md
@@ -1,5 +1,5 @@
---
-title: "Case Study: First Image of a Black Hole"
+title: "Caso de estudio: Primera imagen de un agujero negro"
sidebar: false
---
@@ -10,7 +10,7 @@ sidebar: false
-## A telescope the size of the earth
+## Un telescopio del tamaño del mundo
The [Event Horizon telescope (EHT)](https://eventhorizontelescope.org) is an array of eight ground-based radio telescopes forming a computational telescope the size of the earth, studing the universe with unprecedented sensitivity and resolution. The huge virtual telescope, which uses a technique called very-long-baseline interferometry (VLBI), has an angular resolution of [20 micro-arcseconds][resolution] — enough to read a newspaper in New York from a sidewalk café in Paris!
From 5553d40c7f0569b3c3aef609050b3d43405a5a62 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Thu, 25 Mar 2021 00:23:25 +0100
Subject: [PATCH 203/909] New translations report-handling-manual.md (Japanese)
---
content/ja/report-handling-manual.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/content/ja/report-handling-manual.md b/content/ja/report-handling-manual.md
index 5ccee2b2b5..6e33baea9c 100644
--- a/content/ja/report-handling-manual.md
+++ b/content/ja/report-handling-manual.md
@@ -31,12 +31,12 @@ NumPyの行動規範委員会はこのマニュアルに従います。 この
## 報告に対する委員会の対応
-When the Committee (or a Committee member) receives a report, they will first determine whether the report is about a clear and severe breach (as defined below). If so, immediate action needs to be taken in addition to the regular report handling process.
+委員会(または委員) が行動規範違反報告を受けた時、その報告が明確で深刻な違反であるかどうかは判断されます(以下に違反項目を定義します)。 違反判定された場合は、通常のレポート処理プロセスに加えて、即時の対応が必要になります。
-## Clear and severe breach actions
+## 明確かつ深刻な違反行為の解決
-We know that it is painfully common for internet communication to start at or devolve into obvious and flagrant abuse. We will deal quickly with clear and severe breaches like personal threats, violent, sexist or racist language.
+私たちは、インターネットでの会話が簡単にひどい誹謗中傷になってしまうことを、痛いほど知っています. We will deal quickly with clear and severe breaches like personal threats, violent, sexist or racist language.
When a member of the Code of Conduct Committee becomes aware of a clear and severe breach, they will do the following:
From ba2633edb5df14bb9d58c176e876a53186562d5b Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Thu, 25 Mar 2021 01:29:44 +0100
Subject: [PATCH 204/909] New translations report-handling-manual.md (Japanese)
---
content/ja/report-handling-manual.md | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/content/ja/report-handling-manual.md b/content/ja/report-handling-manual.md
index 6e33baea9c..f705037654 100644
--- a/content/ja/report-handling-manual.md
+++ b/content/ja/report-handling-manual.md
@@ -36,17 +36,17 @@ NumPyの行動規範委員会はこのマニュアルに従います。 この
## 明確かつ深刻な違反行為の解決
-私たちは、インターネットでの会話が簡単にひどい誹謗中傷になってしまうことを、痛いほど知っています. We will deal quickly with clear and severe breaches like personal threats, violent, sexist or racist language.
+私たちは、インターネットでの会話が簡単にひどい誹謗中傷になってしまうことを、痛いほど知っています. 個人的な脅迫、暴力的、性差別的、人種差別的な言葉など、明らかで深刻な違反に対しては、迅速に対処します。
-When a member of the Code of Conduct Committee becomes aware of a clear and severe breach, they will do the following:
+行動規範委員会のメンバーは、明確かつ深刻な違反に気づいた場合、以下のように行動します。
-* Immediately disconnect the originator from all NumPy communication channels.
-* Reply to the reporter that their report has been received and that the originator has been disconnected.
-* In every case, the moderator should make a reasonable effort to contact the originator, and tell them specifically how their language or actions qualify as a “clear and severe breach”. The moderator should also say that, if the originator believes this is unfair or they want to be reconnected to NumPy, they have the right to ask for a review, as below, by the Code of Conduct Committee. The moderator should copy this explanation to the Code of Conduct Committee.
-* The Code of Conduct Committee will formally review and sign off on all cases where this mechanism has been applied to make sure it is not being used to control ordinary heated disagreement.
+* 直ちにすべてのNumpy 通信チャンネルから違反者を排除します。
+* 報告が受信され、違反者が排除されたことを報告者に連絡します。
+* どのような場合でも、モデレーターは違反者に連絡するための合理的な努力を行い、違反者の言葉や行動がどのように「明確かつ重大な違反」に該当するのかを具体的に伝えるべきです。 モデレーターは、違反者がこれは不当だと思う場合、あるいはNumPyチャンネルとの再接続を望む場合には、行動規範委員会による以下のような審査を求める権利があることも述べるべきです。 モデレータは、この説明を行動規範委員会に転送する必要があります。
+* 行動規範委員会は、このプロセスが適用されたすべてのケースを正式にレビューし、作業完了することで、よくある激しい意見の相違を制御するためにこのプロセスが使用されていないことを確認します。
-## Report handling
+## 報告の処理
When a report is sent to the Committee they will immediately reply to the reporter to confirm receipt. This reply must be sent within 72 hours, and the group should strive to respond much quicker than that.
From a054a0c9cf71a64098d4b6eb2e4dc4fc566a2811 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Thu, 25 Mar 2021 13:59:45 +0100
Subject: [PATCH 205/909] New translations blackhole-image.md (Spanish)
---
content/es/case-studies/blackhole-image.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/es/case-studies/blackhole-image.md b/content/es/case-studies/blackhole-image.md
index 47ca6e5a19..e5a63062aa 100644
--- a/content/es/case-studies/blackhole-image.md
+++ b/content/es/case-studies/blackhole-image.md
@@ -3,7 +3,7 @@ title: "Caso de estudio: Primera imagen de un agujero negro"
sidebar: false
---
-{{< figure src="/images/content_images/cs/blackhole.jpg" caption="**Black Hole M87**" alt="black hole image" attr="*(Image Credits: Event Horizon Telescope Collaboration)*" attrlink="https://www.jpl.nasa.gov/images/universe/20190410/blackhole20190410.jpg" >}}
+{{}}
Imaging the M87 Black Hole is like trying to see something that is by definition impossible to see.
From c6ed664b349ac33892100945751dc97790541619 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Thu, 25 Mar 2021 15:08:10 +0100
Subject: [PATCH 206/909] New translations blackhole-image.md (Spanish)
---
content/es/case-studies/blackhole-image.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/es/case-studies/blackhole-image.md b/content/es/case-studies/blackhole-image.md
index e5a63062aa..24c352dd18 100644
--- a/content/es/case-studies/blackhole-image.md
+++ b/content/es/case-studies/blackhole-image.md
@@ -3,7 +3,7 @@ title: "Caso de estudio: Primera imagen de un agujero negro"
sidebar: false
---
-{{}}
+{{< figure src="/images/content_images/cs/blackhole.jpg" caption="**Agujero Negro M87**" alt=black hole image" attr="*(Créditos de imagen: Colaboración del Telescopio de Horizonte de Eventos)*" attrlink="https://www.jpl.nasa.gov/images/universe/20190410/blackhole20190410.jpg">}}
Imaging the M87 Black Hole is like trying to see something that is by definition impossible to see.
From ed93955adbbb04f89d0c9d3ed5e0d4b0a511c9e4 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Fri, 26 Mar 2021 01:34:13 +0100
Subject: [PATCH 207/909] New translations blackhole-image.md (Spanish)
---
content/es/case-studies/blackhole-image.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/es/case-studies/blackhole-image.md b/content/es/case-studies/blackhole-image.md
index 24c352dd18..36e4b92ef0 100644
--- a/content/es/case-studies/blackhole-image.md
+++ b/content/es/case-studies/blackhole-image.md
@@ -3,7 +3,7 @@ title: "Caso de estudio: Primera imagen de un agujero negro"
sidebar: false
---
-{{< figure src="/images/content_images/cs/blackhole.jpg" caption="**Agujero Negro M87**" alt=black hole image" attr="*(Créditos de imagen: Colaboración del Telescopio de Horizonte de Eventos)*" attrlink="https://www.jpl.nasa.gov/images/universe/20190410/blackhole20190410.jpg">}}
+{{< figure src="/images/content_images/cs/blackhole.jpg" caption="**Agujero Negro M87**" alt=black hole image" attr="*(Créditos de imagen: Colaboración del Telescopio de Horizonte de Sucesos)*" attrlink="https://www.jpl.nasa.gov/images/universe/20190410/blackhole20190410.jpg">}}
Imaging the M87 Black Hole is like trying to see something that is by definition impossible to see.
From fcdab5a46852c0f8e9a5fcc4ab1dabd325e1f653 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Fri, 26 Mar 2021 02:38:06 +0100
Subject: [PATCH 208/909] New translations blackhole-image.md (Spanish)
---
content/es/case-studies/blackhole-image.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/es/case-studies/blackhole-image.md b/content/es/case-studies/blackhole-image.md
index 36e4b92ef0..e72f0b1f9d 100644
--- a/content/es/case-studies/blackhole-image.md
+++ b/content/es/case-studies/blackhole-image.md
@@ -12,7 +12,7 @@ sidebar: false
## Un telescopio del tamaño del mundo
-The [Event Horizon telescope (EHT)](https://eventhorizontelescope.org) is an array of eight ground-based radio telescopes forming a computational telescope the size of the earth, studing the universe with unprecedented sensitivity and resolution. The huge virtual telescope, which uses a technique called very-long-baseline interferometry (VLBI), has an angular resolution of [20 micro-arcseconds][resolution] — enough to read a newspaper in New York from a sidewalk café in Paris!
+El [ telescopio Horizonte de Sucesos (EHT) ](https://eventhorizontelescope.org), es un arreglo de ocho radio telescopios terrestres formando un telescopio computacional del tamaño del mundo, estudiando el universo con una sensibilidad y resolución sin precedente. The huge virtual telescope, which uses a technique called very-long-baseline interferometry (VLBI), has an angular resolution of [20 micro-arcseconds][resolution] — enough to read a newspaper in New York from a sidewalk café in Paris!
### Objetivos clave y resultados
From 5eb3d6e2d664422ce0a93f4996b1033f5884740d Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 27 Mar 2021 00:14:00 +0100
Subject: [PATCH 209/909] New translations report-handling-manual.md (Japanese)
---
content/ja/report-handling-manual.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/content/ja/report-handling-manual.md b/content/ja/report-handling-manual.md
index f705037654..885c7e9c2c 100644
--- a/content/ja/report-handling-manual.md
+++ b/content/ja/report-handling-manual.md
@@ -48,9 +48,9 @@ NumPyの行動規範委員会はこのマニュアルに従います。 この
## 報告の処理
-When a report is sent to the Committee they will immediately reply to the reporter to confirm receipt. This reply must be sent within 72 hours, and the group should strive to respond much quicker than that.
+報告が委員会に送られると、直ちに報告者に返信して報告を受領したことを確認します。 この返信は72時間以内に送信される必要があり、委員会はそれよりもはるかに迅速に対応するよう努める必要があります。
-If a report doesn’t contain enough information, the Committee will obtain all relevant data before acting. The Committee is empowered to act on the Steering Council’s behalf in contacting any individuals involved to get a more complete account of events.
+レポートに十分な情報が含まれていない場合、委員会は行動する前に、関連するすべてのデータを取得するようにします。 The Committee is empowered to act on the Steering Council’s behalf in contacting any individuals involved to get a more complete account of events.
The Committee will then review the incident and determine, to the best of their ability:
From 6277cd92e3867f24a4c368c81bf5c87885ba91e8 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 27 Mar 2021 01:12:59 +0100
Subject: [PATCH 210/909] New translations report-handling-manual.md (Japanese)
---
content/ja/report-handling-manual.md | 20 ++++++++++----------
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/content/ja/report-handling-manual.md b/content/ja/report-handling-manual.md
index 885c7e9c2c..51e4d74c22 100644
--- a/content/ja/report-handling-manual.md
+++ b/content/ja/report-handling-manual.md
@@ -50,23 +50,23 @@ NumPyの行動規範委員会はこのマニュアルに従います。 この
報告が委員会に送られると、直ちに報告者に返信して報告を受領したことを確認します。 この返信は72時間以内に送信される必要があり、委員会はそれよりもはるかに迅速に対応するよう努める必要があります。
-レポートに十分な情報が含まれていない場合、委員会は行動する前に、関連するすべてのデータを取得するようにします。 The Committee is empowered to act on the Steering Council’s behalf in contacting any individuals involved to get a more complete account of events.
+レポートに十分な情報が含まれていない場合、委員会は行動する前に、関連するすべてのデータを取得するようにします。 委員会は、今回の事象の全ての状況を知るために関係する個人に連絡する際に、運営協議会に代わって行動する権限を与えられています。
-The Committee will then review the incident and determine, to the best of their ability:
+その後、委員会は今回の問題を見直し、効果を最大限に発揮する対策を決定します。
-* What happened.
-* Whether this event constitutes a Code of Conduct violation.
-* Who are the responsible party(ies).
-* Whether this is an ongoing situation, and there is a threat to anyone’s physical safety.
+* 問題の種類
+* 今回の事情が行動規範違反であるかどうか。
+* 責任者が誰であるか
+* これが進行中の状況であるか、誰の物理的安全に脅威があるかどうか。
-This information will be collected in writing, and whenever possible the group’s deliberations will be recorded and retained (i.e. chat transcripts, email discussions, recorded conference calls, summaries of voice conversations, etc).
+これらの情報は書面で収集され、可能な限りグループの審議が記録され、保持されます (例えば、チャットの記録、Eメールのディスカッション、会議通話の記録、音声会話の概要など)。
-It is important to retain an archive of all activities of this Committee to ensure consistency in behavior and provide institutional memory for the project. To assist in this, the default channel of discussion for this Committee will be a private mailing list accessible to current and future members of the Committee as well as members of the Steering Council upon justified request. If the Committee finds the need to use off-list communications (e.g. phone calls for early/rapid response), it should in all cases summarize these back to the list so there’s a good record of the process.
+行動の一貫性を確保し、プロジェクトのために記録を残すために、委員会のすべての活動のアーカイブを保持することが重要です. この活動支援するために、委員会のデフォルトの議論チャネルは、正当化された要求に応じて、委員会の現在および将来のメンバー、および運営委員会のメンバーがアクセスできるプライベートメーリングリストにします。 委員会がリストにはない連絡方法を使用する必要がある場合(例: 早期/迅速な対応を求める電話など)、そのプロセスの良い記録となるように、これらをリストにまとめて戻すべきです。
-The Code of Conduct Committee should aim to have a resolution agreed upon within two weeks. In the event that a resolution can’t be determined in that time, the Committee will respond to the reporter(s) with an update and projected timeline for resolution.
+行動規範委員会は、2週間以内に決議の合意を目指すべきです。 その期間内に決議が確定できない場合。 委員会は、レポーターに対して現状の更新と今後のタイムラインを連絡します。
-## Resolutions
+## 解決方法
The Committee must agree on a resolution by consensus. If the group cannot reach consensus and deadlocks for over a week, the group will turn the matter over to the Steering Council for resolution.
From fce1e4a4272ce3237cd562207bbcf823bd16cf78 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sun, 28 Mar 2021 00:02:05 +0100
Subject: [PATCH 211/909] New translations report-handling-manual.md (Japanese)
---
content/ja/report-handling-manual.md | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/content/ja/report-handling-manual.md b/content/ja/report-handling-manual.md
index 51e4d74c22..85926b1d71 100644
--- a/content/ja/report-handling-manual.md
+++ b/content/ja/report-handling-manual.md
@@ -68,14 +68,14 @@ NumPyの行動規範委員会はこのマニュアルに従います。 この
## 解決方法
-The Committee must agree on a resolution by consensus. If the group cannot reach consensus and deadlocks for over a week, the group will turn the matter over to the Steering Council for resolution.
+委員会は、合意により決議について決定しなければなりません。 検討グループが一週間以上、合意かデッドロックに達しなかった場合、グループは、ステアリング評議会にこの問題を引き渡すことができます。
-Possible responses may include:
+ありうる返答は次のとおりです:
-* Taking no further action:
- - if we determine no violations have occurred;
- - if the matter has been resolved publicly while the Committee was considering responses.
-* Coordinating voluntary mediation: if all involved parties agree, the Committee may facilitate a mediation process as detailed above.
+* これ以上アクションを取らない:
+ - 違反が起きていないと判断された
+ - 検討中に問題が明らかに解決された
+* 調停の調整: すべての関係者が合意した場合、委員会は上記のように調停プロセスを促進することができます。
* Remind publicly, and point out that some behavior/actions/language have been judged inappropriate and why in the current context, or can but hurtful to some people, requesting the community to self-adjust.
* A private reprimand from the Committee to the individual(s) involved. In this case, the group chair will deliver that reprimand to the individual(s) over email, cc’ing the group.
* A public reprimand. In this case, the Committee chair will deliver that reprimand in the same venue that the violation occurred, within the limits of practicality. E.g., the original mailing list for an email violation, but for a chat room discussion where the person/context may be gone, they can be reached by other means. The group may choose to publish this message elsewhere for documentation purposes.
From cdcd83ccac907b5a916b5603e16e22bc5b459b3a Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sun, 28 Mar 2021 01:01:59 +0100
Subject: [PATCH 212/909] New translations report-handling-manual.md (Japanese)
---
content/ja/report-handling-manual.md | 22 +++++++++++-----------
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git a/content/ja/report-handling-manual.md b/content/ja/report-handling-manual.md
index 85926b1d71..72648a80b6 100644
--- a/content/ja/report-handling-manual.md
+++ b/content/ja/report-handling-manual.md
@@ -76,20 +76,20 @@ NumPyの行動規範委員会はこのマニュアルに従います。 この
- 違反が起きていないと判断された
- 検討中に問題が明らかに解決された
* 調停の調整: すべての関係者が合意した場合、委員会は上記のように調停プロセスを促進することができます。
-* Remind publicly, and point out that some behavior/actions/language have been judged inappropriate and why in the current context, or can but hurtful to some people, requesting the community to self-adjust.
-* A private reprimand from the Committee to the individual(s) involved. In this case, the group chair will deliver that reprimand to the individual(s) over email, cc’ing the group.
-* A public reprimand. In this case, the Committee chair will deliver that reprimand in the same venue that the violation occurred, within the limits of practicality. E.g., the original mailing list for an email violation, but for a chat room discussion where the person/context may be gone, they can be reached by other means. The group may choose to publish this message elsewhere for documentation purposes.
-* A request for a public or private apology, assuming the reporter agrees to this idea: they may at their discretion refuse further contact with the violator. The chair will deliver this request. The Committee may, if it chooses, attach “strings” to this request: for example, the group may ask a violator to apologize in order to retain one’s membership on a mailing list.
-* A “mutually agreed upon hiatus” where the Committee asks the individual to temporarily refrain from community participation. If the individual chooses not to take a temporary break voluntarily, the Committee may issue a “mandatory cooling off period”.
-* A permanent or temporary ban from some or all NumPy spaces (mailing lists, gitter.im, etc.). The group will maintain records of all such bans so that they may be reviewed in the future or otherwise maintained.
+* 公の場において、いくつかの行動/言動/言語が不適切で、現在の状況がなぜか引き起こされたのか指摘し、人々を傷つけることができルール言動であったことを説明するなど、コミュニティに自己調整を要求することもあります。
+* 委員会から関係者(複数可) への非公開処分の実施。 この場合、委員会は、電子メールを介して、グループにccを入れながら、対象者に問題の指摘を連絡します。
+* 公の場での指摘。 この場合、委員会の議長は、違反が発生したのと同じ場所で、実用性の範囲内で叱責を行います。 例えば、メールルールの違反の元のメーリングリストなどです。しかし、人や状況がかわるかもしれないチャットルームなどの場合、他の手段を利用する可能性もあります。 対策グループは、文書化のために、この問題のメッセージを他の場所で公開することを選択することもできます。
+* 報告者がこの考えに同意することを前提とした、公的または私的な謝罪の要求:報告者は自分の裁量で、違反者とのさらなる接触を拒否することもできます。 委員会がこの要求をお届けします。 委員会は、必要に応じてこの要求に「条件」を付けることができます。例えば、メーリングリストの会員資格を維持するために、違反者に謝罪を求めることができます。
+* 委員会が個人にコミュニティへの参加を一時的に控える「相互に合意した休止」を要求できます。 対象者が自発的に一時的な休みを取らないことを選択した場合、委員会は「冷却期限」を準備することがあります。
+* これは、一部またはすべての Numpy スペース (メーリングリスト、gitter.im など) からの永続的または一時的な禁止のことです。 対策グループは、将来的な見直しや、または別の方法で対策されるように、すべてのそのような禁止の記録を記録します。
-Once a resolution is agreed upon, but before it is enacted, the Committee will contact the original reporter and any other affected parties and explain the proposed resolution. The Committee will ask if this resolution is acceptable, and must note feedback for the record.
+決議が合意されると制定される前に、委員会は、元の報告者およびその他の影響を受けた当事者に連絡し、提案された決議を説明します。 委員会は、この決議が受け入れられるかどうかを尋ねます。そして、記録のためのフィードバックに注意を払います。
-Finally, the Committee will make a report to the NumPy Steering Council (as well as the NumPy core team in the event of an ongoing resolution, such as a ban).
+最後に 委員会は、Numpy Steering CouncilとNumPy Coreチームに報告を行います。(例えば禁止事項など)
-The Committee will never publicly discuss the issue; all public statements will be made by the chair of the Code of Conduct Committee or the NumPy Steering Council.
+委員会はこの問題について公に議論することはありません。 すべての公開声明は、行動規範委員会またはNumpy Steering Councilの議長によって行われます。
-## Conflicts of Interest
+## 利益相反
-In the event of any conflict of interest, a Committee member must immediately notify the other members, and recuse themselves if necessary.
+利益相反が発生した場合、委員会メンバーは直ちに他のメンバーに通知し、必要に応じて対応を辞退しなければなりません。
From ebd6c1e28c0e731f4f06e1a0bba938c277f75a61 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sun, 28 Mar 2021 03:22:28 +0200
Subject: [PATCH 213/909] New translations blackhole-image.md (Spanish)
---
content/es/case-studies/blackhole-image.md | 26 ++++++++++++++--------
1 file changed, 17 insertions(+), 9 deletions(-)
diff --git a/content/es/case-studies/blackhole-image.md b/content/es/case-studies/blackhole-image.md
index e72f0b1f9d..8963bbed5b 100644
--- a/content/es/case-studies/blackhole-image.md
+++ b/content/es/case-studies/blackhole-image.md
@@ -12,7 +12,11 @@ sidebar: false
## Un telescopio del tamaño del mundo
-El [ telescopio Horizonte de Sucesos (EHT) ](https://eventhorizontelescope.org), es un arreglo de ocho radio telescopios terrestres formando un telescopio computacional del tamaño del mundo, estudiando el universo con una sensibilidad y resolución sin precedente. The huge virtual telescope, which uses a technique called very-long-baseline interferometry (VLBI), has an angular resolution of [20 micro-arcseconds][resolution] — enough to read a newspaper in New York from a sidewalk café in Paris!
+El [ telescopio Horizonte de Sucesos (EHT) ](https://eventhorizontelescope.org), es un arreglo de ocho radio telescopios terrestres formando un telescopio computacional del tamaño del mundo, estudiando el universo con una sensibilidad y resolución sin precedente. El enorme telescopio virtual, que utiliza una técnica llamada interferometría de linea de base muy larga (VLBI), tiene una resolución angular de
+
+20 microsegundos de arco<0> - ¡suficiente para leer un periódico en Nueva York desde un café en la acera en París!
+
+
### Objetivos clave y resultados
@@ -22,22 +26,26 @@ El [ telescopio Horizonte de Sucesos (EHT) ](https://eventhorizontelescope.org),
* **Comparing Observations to Theory:** From Einstein’s general theory of relativity, scientists expected to find a shadow-like region caused by gravitational bending and capture of light. Scientists could use it to measure the black hole's enormous mass.
+
+
### The Challenges
* **Computational scale**
-
- EHT poses massive data-processing challenges, including rapid atmospheric phase fluctuations, large recording bandwidth, and telescopes that are widely dissimilar and geographically dispersed.
+
+ EHT poses massive data-processing challenges, including rapid atmospheric phase fluctuations, large recording bandwidth, and telescopes that are widely dissimilar and geographically dispersed.
* **Too much information**
-
- Each day EHT generates over 350 terabytes of observations, stored on helium-filled hard drives. Reducing the volume and complexity of this much data is enormously difficult.
+
+ Each day EHT generates over 350 terabytes of observations, stored on helium-filled hard drives. Reducing the volume and complexity of this much data is enormously difficult.
* **Into the unknown**
-
- When the goal is to see something never before seen, how can scientists be confident the image is correct?
+
+ When the goal is to see something never before seen, how can scientists be confident the image is correct?
{{< figure src="/images/content_images/cs/dataprocessbh.png" class="csfigcaption" caption="**EHT Data Processing Pipeline**" alt="data pipeline" align="middle" attr="(Diagram Credits: The Astrophysical Journal, Event Horizon Telescope Collaboration)" attrlink="https://iopscience.iop.org/article/10.3847/2041-8213/ab0c57" >}}
+
+
## NumPy’s Role
What if there's a problem with the data? Or perhaps an algorithm relies too heavily on a particular assumption. Will the image change drastically if a single parameter is changed?
@@ -54,14 +62,14 @@ For example, the [`eht-imaging`][ehtim] Python package provides tools for simula
Besides NumPy, many other packages, such as [SciPy](https://www.scipy.org) and [Pandas](https://pandas.io), are part of the data processing pipeline for imaging the black hole. The standard astronomical file formats and time/coordinate transformations were handled by [Astropy][astropy], while [Matplotlib][mpl] was used in visualizing data throughout the analysis pipeline, including the generation of the final image of the black hole.
+
+
## Summary
The efficient and adaptable n-dimensional array that is NumPy's central feature enabled researchers to manipulate large numerical datasets, providing a foundation for the first-ever image of a black hole. A landmark moment in science, it gives stunning visual evidence of Einstein’s theory. The achievement encompasses not only technological breakthroughs but also international collaboration among over 200 scientists and some of the world's best radio observatories. Innovative algorithms and data processing techniques, improving upon existing astronomical models, helped unfold a mystery of the universe.
{{< figure src="/images/content_images/cs/numpy_bh_benefits.png" class="fig-center" alt="numpy benefits" caption="**Key NumPy Capabilities utilized**" >}}
-[resolution]: https://eventhorizontelescope.org/press-release-april-10-2019-astronomers-capture-first-image-black-hole
-
[eddington]: https://en.wikipedia.org/wiki/Eddington_experiment
[ehtim]: https://github.com/achael/eht-imaging
From 7f3dbf79afe2a962f48fe644cbf11f43b283b2c0 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sun, 28 Mar 2021 14:42:52 +0200
Subject: [PATCH 214/909] New translations install.md (Chinese Simplified)
---
content/zh/install.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/zh/install.md b/content/zh/install.md
index 43dd44cb12..3ec0dc58b7 100644
--- a/content/zh/install.md
+++ b/content/zh/install.md
@@ -77,7 +77,7 @@ Otherwise:
#### Alternative if you prefer pip/PyPI
For users who know, from personal preference or reading about the main differences between conda and pip below, they prefer a pip/PyPI-based solution, we recommend:
-- Install Python from, for example, [python.org](https://www.python.org/downloads/), [Homebrew](https://brew.sh/), or your Linux package manager.
+- Install Python from [python.org](https://www.python.org/downloads/), [Homebrew](https://brew.sh/), or your Linux package manager.
- Use [Poetry](https://python-poetry.org/) as the most well-maintained tool that provides a dependency resolver and environment management capabilities in a similar fashion as conda does.
From bceacfa622e0fe7fb561c9e29ef2aaf9a019c7a4 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sun, 28 Mar 2021 14:43:10 +0200
Subject: [PATCH 215/909] New translations install.md (Korean)
---
content/ko/install.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/ko/install.md b/content/ko/install.md
index 43dd44cb12..3ec0dc58b7 100644
--- a/content/ko/install.md
+++ b/content/ko/install.md
@@ -77,7 +77,7 @@ Otherwise:
#### Alternative if you prefer pip/PyPI
For users who know, from personal preference or reading about the main differences between conda and pip below, they prefer a pip/PyPI-based solution, we recommend:
-- Install Python from, for example, [python.org](https://www.python.org/downloads/), [Homebrew](https://brew.sh/), or your Linux package manager.
+- Install Python from [python.org](https://www.python.org/downloads/), [Homebrew](https://brew.sh/), or your Linux package manager.
- Use [Poetry](https://python-poetry.org/) as the most well-maintained tool that provides a dependency resolver and environment management capabilities in a similar fashion as conda does.
From b3a1f3d01ceba8d3996979fff57eb789eb7fb292 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sun, 28 Mar 2021 14:43:28 +0200
Subject: [PATCH 216/909] New translations install.md (Portuguese, Brazilian)
---
content/pt/install.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/pt/install.md b/content/pt/install.md
index 319caaf9e2..ccaad9e92f 100644
--- a/content/pt/install.md
+++ b/content/pt/install.md
@@ -77,7 +77,7 @@ Otherwise:
#### Alternativa se você preferir pip/PyPI
For users who know, from personal preference or reading about the main differences between conda and pip below, they prefer a pip/PyPI-based solution, we recommend:
-- Instale o Python a partir de, por exemplo, [python.org](https://www.python.org/downloads/), [Homebrew](https://brew.sh/), ou seu gerenciador de pacotes Linux.
+- Install Python from [python.org](https://www.python.org/downloads/), [Homebrew](https://brew.sh/), or your Linux package manager.
- Use [Poetry](https://python-poetry.org/) como a ferramenta mais bem mantida que fornece um resolvedor de dependências e recursos de gerenciamento de ambiente de forma semelhante ao que o conda faz.
From 79fff2744879f57dd76397dd1b2c6f609c9bf5f3 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sun, 28 Mar 2021 14:43:59 +0200
Subject: [PATCH 217/909] New translations install.md (Spanish)
---
content/es/install.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/es/install.md b/content/es/install.md
index 43dd44cb12..3ec0dc58b7 100644
--- a/content/es/install.md
+++ b/content/es/install.md
@@ -77,7 +77,7 @@ Otherwise:
#### Alternative if you prefer pip/PyPI
For users who know, from personal preference or reading about the main differences between conda and pip below, they prefer a pip/PyPI-based solution, we recommend:
-- Install Python from, for example, [python.org](https://www.python.org/downloads/), [Homebrew](https://brew.sh/), or your Linux package manager.
+- Install Python from [python.org](https://www.python.org/downloads/), [Homebrew](https://brew.sh/), or your Linux package manager.
- Use [Poetry](https://python-poetry.org/) as the most well-maintained tool that provides a dependency resolver and environment management capabilities in a similar fashion as conda does.
From 6956437ab193f1b9a4d3d9cb843aa65587eb995c Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sun, 28 Mar 2021 14:44:18 +0200
Subject: [PATCH 218/909] New translations install.md (Japanese)
---
content/ja/install.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/ja/install.md b/content/ja/install.md
index 61f58002df..82c9aa0e3e 100644
--- a/content/ja/install.md
+++ b/content/ja/install.md
@@ -77,7 +77,7 @@ GPUを使用する場合:
#### pip/PyPI を利用したい場合
個人的な好みや、下記のcondaとpipの違いを理解した上で、pip/PyPIベースの方法を使いたいユーザーには、下記をお勧めします:
-- Pythonをインストールします。例えば、 [python.org](https://www.python.org/downloads/), [Homebrew](https://brew.sh/), または Linux パッケージマネージャを使うことができます。
+- Install Python from [python.org](https://www.python.org/downloads/), [Homebrew](https://brew.sh/), or your Linux package manager.
- 依存関係の解決と環境の管理を提供する最もよくメンテナンスされているツールとして、[Poetry](https://python-poetry. org/) をconda と同様な方法で使用することができます。
From 0826c0979e79be30f6922352b4a44ed9d162cbeb Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sun, 28 Mar 2021 14:44:24 +0200
Subject: [PATCH 219/909] New translations install.md (Arabic)
---
content/ar/install.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/ar/install.md b/content/ar/install.md
index 43dd44cb12..3ec0dc58b7 100644
--- a/content/ar/install.md
+++ b/content/ar/install.md
@@ -77,7 +77,7 @@ Otherwise:
#### Alternative if you prefer pip/PyPI
For users who know, from personal preference or reading about the main differences between conda and pip below, they prefer a pip/PyPI-based solution, we recommend:
-- Install Python from, for example, [python.org](https://www.python.org/downloads/), [Homebrew](https://brew.sh/), or your Linux package manager.
+- Install Python from [python.org](https://www.python.org/downloads/), [Homebrew](https://brew.sh/), or your Linux package manager.
- Use [Poetry](https://python-poetry.org/) as the most well-maintained tool that provides a dependency resolver and environment management capabilities in a similar fashion as conda does.
From d0812f6c487c7ca5a2c093b610b04e2c6c3869b2 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sun, 28 Mar 2021 16:51:52 +0200
Subject: [PATCH 220/909] New translations code-of-conduct.md (Arabic)
---
content/ar/code-of-conduct.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/content/ar/code-of-conduct.md b/content/ar/code-of-conduct.md
index efcde754ae..58e7bc7a7c 100644
--- a/content/ar/code-of-conduct.md
+++ b/content/ar/code-of-conduct.md
@@ -1,13 +1,13 @@
---
-title: NumPy Code of Conduct
+title: القواعد التنظيمية لنمباي
sidebar: false
aliases:
- /conduct.html
---
-### Introduction
+### المقدمة
-This Code of Conduct applies to all spaces managed by the NumPy project, including all public and private mailing lists, issue trackers, wikis, blogs, Twitter, and any other communication channel used by our community. The NumPy project does not organise in-person events, however events related to our community should have a code of conduct similar in spirit to this one.
+هذه القواعد التنظيمية تنطبق علي جميع المجالات التي تدار من قبل مشروع نمباي, بما في ذلك كل قوائم البريد سواء كانت خاصة أم عامة ومتعقبات القضايا والويكي والمدونات وتويتر وأي قناة اتصال تستخدم من قبل مجتمعنا. The NumPy project does not organise in-person events, however events related to our community should have a code of conduct similar in spirit to this one.
This Code of Conduct should be honored by everyone who participates in the NumPy community formally or informally, or claims any affiliation with the project, in any project-related activities and especially when representing the project, in any role.
From d6bac4aa6cd4a71f03914e647f4c7d866e801596 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sun, 28 Mar 2021 17:52:25 +0200
Subject: [PATCH 221/909] New translations code-of-conduct.md (Arabic)
---
content/ar/code-of-conduct.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/content/ar/code-of-conduct.md b/content/ar/code-of-conduct.md
index 58e7bc7a7c..a17e7fe3ae 100644
--- a/content/ar/code-of-conduct.md
+++ b/content/ar/code-of-conduct.md
@@ -1,5 +1,5 @@
---
-title: القواعد التنظيمية لنمباي
+title: القواعد السلوكية لنمباي
sidebar: false
aliases:
- /conduct.html
@@ -7,7 +7,7 @@ aliases:
### المقدمة
-هذه القواعد التنظيمية تنطبق علي جميع المجالات التي تدار من قبل مشروع نمباي, بما في ذلك كل قوائم البريد سواء كانت خاصة أم عامة ومتعقبات القضايا والويكي والمدونات وتويتر وأي قناة اتصال تستخدم من قبل مجتمعنا. The NumPy project does not organise in-person events, however events related to our community should have a code of conduct similar in spirit to this one.
+هذه القواعد السلوكية تنطبق علي جميع المجالات التي تدار من قبل مشروع نمباي, بما في ذلك كل قوائم البريد سواء كانت خاصة أم عامة ومتعقبات القضايا والويكي والمدونات وتويتر وأي قناة اتصال تستخدم من قبل مجتمعنا. مشروع نمباي لا يقوم بتنظيم أي فعاليات شخصية ومع ذلك أي فعاليات متعلقة لمجتمعنا ينبغي أن تكون لها قواعد سلوكية مشابهة لروح هذا المستند.
This Code of Conduct should be honored by everyone who participates in the NumPy community formally or informally, or claims any affiliation with the project, in any project-related activities and especially when representing the project, in any role.
From 19d4cab1eee5f74ddcf0dd0f5b9daf722ebfd8e4 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sun, 28 Mar 2021 19:34:56 +0200
Subject: [PATCH 222/909] New translations code-of-conduct.md (Arabic)
---
content/ar/code-of-conduct.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/content/ar/code-of-conduct.md b/content/ar/code-of-conduct.md
index a17e7fe3ae..d6e85bdcf9 100644
--- a/content/ar/code-of-conduct.md
+++ b/content/ar/code-of-conduct.md
@@ -9,9 +9,9 @@ aliases:
هذه القواعد السلوكية تنطبق علي جميع المجالات التي تدار من قبل مشروع نمباي, بما في ذلك كل قوائم البريد سواء كانت خاصة أم عامة ومتعقبات القضايا والويكي والمدونات وتويتر وأي قناة اتصال تستخدم من قبل مجتمعنا. مشروع نمباي لا يقوم بتنظيم أي فعاليات شخصية ومع ذلك أي فعاليات متعلقة لمجتمعنا ينبغي أن تكون لها قواعد سلوكية مشابهة لروح هذا المستند.
-This Code of Conduct should be honored by everyone who participates in the NumPy community formally or informally, or claims any affiliation with the project, in any project-related activities and especially when representing the project, in any role.
+ينبغي علي كل شخص مشارك في مجتمع نمباي أن يحتذي بهذه القواعد سواء كان مشترك بصورة رسمية أو غير رسمية، أو يدعي انتمائه للمشروع في أي انشطه متعلقة للمشروع وخاصة عندما يمثل المشروع تحت أي دور.
-This code is not exhaustive or complete. It serves to distill our common understanding of a collaborative, shared environment and goals. Please try to follow this code in spirit as much as in letter, to create a friendly and productive environment that enriches the surrounding community.
+هذه القواعد ليست شاملة أو كاملة. It serves to distill our common understanding of a collaborative, shared environment and goals. Please try to follow this code in spirit as much as in letter, to create a friendly and productive environment that enriches the surrounding community.
### Specific Guidelines
From e718ad2eaecaf60aae1bc51aa90571a1fa3ffcf9 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sun, 28 Mar 2021 20:36:29 +0200
Subject: [PATCH 223/909] New translations code-of-conduct.md (Arabic)
---
content/ar/code-of-conduct.md | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/content/ar/code-of-conduct.md b/content/ar/code-of-conduct.md
index d6e85bdcf9..3fcdbd2288 100644
--- a/content/ar/code-of-conduct.md
+++ b/content/ar/code-of-conduct.md
@@ -11,14 +11,14 @@ aliases:
ينبغي علي كل شخص مشارك في مجتمع نمباي أن يحتذي بهذه القواعد سواء كان مشترك بصورة رسمية أو غير رسمية، أو يدعي انتمائه للمشروع في أي انشطه متعلقة للمشروع وخاصة عندما يمثل المشروع تحت أي دور.
-هذه القواعد ليست شاملة أو كاملة. It serves to distill our common understanding of a collaborative, shared environment and goals. Please try to follow this code in spirit as much as in letter, to create a friendly and productive environment that enriches the surrounding community.
+هذه القواعد ليست شاملة أو كاملة. لكنها تساعد علي استخلاص فهمنا المشترك للتعاون في ظل بيئة وأهداف مشتركة. من فضلك حاول أن تتبع هذه القواعد روحا ونصا من أجل إنشاء بيئة ودودة ومنتجة نثري بها المجتمع المحيط.
-### Specific Guidelines
+### مبادئ توجيهية محددة
-We strive to:
+نحن نسعى إلي:
-1. Be open. We invite anyone to participate in our community. We prefer to use public methods of communication for project-related messages, unless discussing something sensitive. This applies to messages for help or project-related support, too; not only is a public support request much more likely to result in an answer to a question, it also ensures that any inadvertent mistakes in answering are more easily detected and corrected.
-2. Be empathetic, welcoming, friendly, and patient. We work together to resolve conflict, and assume good intentions. We may all experience some frustration from time to time, but we do not allow frustration to turn into a personal attack. A community where people feel uncomfortable or threatened is not a productive one.
+1. أن نكون منفتحين. نحن ندعو الجميع للمشاركة في مجتمعنا. نحن نفضل استخدام وسائل الاتصال العامة للرسائل المتعلقة بالمشروع، ما لم نناقش شيئا حساسا. ينطبق هذا علي الرسائل الخاصة بطلب المساعدة أوالمتعلقة بدعم المشروع ، ليس فقط ﻷن طلبات الدعم العام محببة لاحتمالية الوصول للإجابة عن الاستفسارات بشكل اكبر، ولكن أيضا لضمان سهولة الكشف والتصحيح عن أي أخطاء غير مقصودة في الإجابات.
+2. أن نكون عطوفين ومرحبين واكثر ودا وصبرا. نحن نعمل معا لحل الخلافات ونفترض حسن النوايا. قد نواجه بعض الإحباط من حين ألي أخر لكننا لا نسمح للإحباط أن يتحول إلي هجوم شخصي. فالمجتمع الذي يشعر فيه الناس بعدم الارتياح أو بالتهديد ليس مجتمعا منتجا.
3. Be collaborative. Our work will be used by other people, and in turn we will depend on the work of others. When we make something for the benefit of the project, we are willing to explain to others how it works, so that they can build on the work to make it even better. Any decision we make will affect users and colleagues, and we take those consequences seriously when making decisions.
4. Be inquisitive. Nobody knows everything! Asking questions early avoids many problems later, so we encourage questions, although we may direct them to the appropriate forum. We will try hard to be responsive and helpful.
5. Be careful in the words that we choose. We are careful and respectful in our communication, and we take responsibility for our own speech. Be kind to others. Do not insult or put down other participants. We will not accept harassment or other exclusionary behaviour, such as:
From 013dd825379db3ba0e019a0e57797fcf66bcaf39 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sun, 28 Mar 2021 21:35:14 +0200
Subject: [PATCH 224/909] New translations code-of-conduct.md (Arabic)
---
content/ar/code-of-conduct.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/content/ar/code-of-conduct.md b/content/ar/code-of-conduct.md
index 3fcdbd2288..5efaa3c351 100644
--- a/content/ar/code-of-conduct.md
+++ b/content/ar/code-of-conduct.md
@@ -19,8 +19,8 @@ aliases:
1. أن نكون منفتحين. نحن ندعو الجميع للمشاركة في مجتمعنا. نحن نفضل استخدام وسائل الاتصال العامة للرسائل المتعلقة بالمشروع، ما لم نناقش شيئا حساسا. ينطبق هذا علي الرسائل الخاصة بطلب المساعدة أوالمتعلقة بدعم المشروع ، ليس فقط ﻷن طلبات الدعم العام محببة لاحتمالية الوصول للإجابة عن الاستفسارات بشكل اكبر، ولكن أيضا لضمان سهولة الكشف والتصحيح عن أي أخطاء غير مقصودة في الإجابات.
2. أن نكون عطوفين ومرحبين واكثر ودا وصبرا. نحن نعمل معا لحل الخلافات ونفترض حسن النوايا. قد نواجه بعض الإحباط من حين ألي أخر لكننا لا نسمح للإحباط أن يتحول إلي هجوم شخصي. فالمجتمع الذي يشعر فيه الناس بعدم الارتياح أو بالتهديد ليس مجتمعا منتجا.
-3. Be collaborative. Our work will be used by other people, and in turn we will depend on the work of others. When we make something for the benefit of the project, we are willing to explain to others how it works, so that they can build on the work to make it even better. Any decision we make will affect users and colleagues, and we take those consequences seriously when making decisions.
-4. Be inquisitive. Nobody knows everything! Asking questions early avoids many problems later, so we encourage questions, although we may direct them to the appropriate forum. We will try hard to be responsive and helpful.
+3. أن نكون متعاونين. كما سيستفيد بعملنا الآخرين سنستفيد نحن أيضا بعملهم. عندما نقوم بصنع شيئاً لمنفعة المشروع ، سوف نكون علي الاستعداد لشرح للآخرين كيفية عمله ، حتي يكونوا قادرين علي البناء عليه لجعله أفضل. أي قرار سنتخذه سيؤثر علي المستخدمين وعلي زملائنا في العمل لذا يجب أن تأخذ العواقب علي محمل الجد عندما نتخذ القرارات.
+4. أن نكون اكثر استطلاعاً. لا أحد علي دراية بكل شئ! Asking questions early avoids many problems later, so we encourage questions, although we may direct them to the appropriate forum. We will try hard to be responsive and helpful.
5. Be careful in the words that we choose. We are careful and respectful in our communication, and we take responsibility for our own speech. Be kind to others. Do not insult or put down other participants. We will not accept harassment or other exclusionary behaviour, such as:
* Violent threats or language directed against another person.
* Sexist, racist, or otherwise discriminatory jokes and language.
From 790c9163d7f07ee7039e57534038c90906237528 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sun, 28 Mar 2021 22:35:56 +0200
Subject: [PATCH 225/909] New translations code-of-conduct.md (Arabic)
---
content/ar/code-of-conduct.md | 20 ++++++++++----------
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/content/ar/code-of-conduct.md b/content/ar/code-of-conduct.md
index 5efaa3c351..6bed4d737d 100644
--- a/content/ar/code-of-conduct.md
+++ b/content/ar/code-of-conduct.md
@@ -20,16 +20,16 @@ aliases:
1. أن نكون منفتحين. نحن ندعو الجميع للمشاركة في مجتمعنا. نحن نفضل استخدام وسائل الاتصال العامة للرسائل المتعلقة بالمشروع، ما لم نناقش شيئا حساسا. ينطبق هذا علي الرسائل الخاصة بطلب المساعدة أوالمتعلقة بدعم المشروع ، ليس فقط ﻷن طلبات الدعم العام محببة لاحتمالية الوصول للإجابة عن الاستفسارات بشكل اكبر، ولكن أيضا لضمان سهولة الكشف والتصحيح عن أي أخطاء غير مقصودة في الإجابات.
2. أن نكون عطوفين ومرحبين واكثر ودا وصبرا. نحن نعمل معا لحل الخلافات ونفترض حسن النوايا. قد نواجه بعض الإحباط من حين ألي أخر لكننا لا نسمح للإحباط أن يتحول إلي هجوم شخصي. فالمجتمع الذي يشعر فيه الناس بعدم الارتياح أو بالتهديد ليس مجتمعا منتجا.
3. أن نكون متعاونين. كما سيستفيد بعملنا الآخرين سنستفيد نحن أيضا بعملهم. عندما نقوم بصنع شيئاً لمنفعة المشروع ، سوف نكون علي الاستعداد لشرح للآخرين كيفية عمله ، حتي يكونوا قادرين علي البناء عليه لجعله أفضل. أي قرار سنتخذه سيؤثر علي المستخدمين وعلي زملائنا في العمل لذا يجب أن تأخذ العواقب علي محمل الجد عندما نتخذ القرارات.
-4. أن نكون اكثر استطلاعاً. لا أحد علي دراية بكل شئ! Asking questions early avoids many problems later, so we encourage questions, although we may direct them to the appropriate forum. We will try hard to be responsive and helpful.
-5. Be careful in the words that we choose. We are careful and respectful in our communication, and we take responsibility for our own speech. Be kind to others. Do not insult or put down other participants. We will not accept harassment or other exclusionary behaviour, such as:
- * Violent threats or language directed against another person.
- * Sexist, racist, or otherwise discriminatory jokes and language.
- * Posting sexually explicit or violent material.
- * Posting (or threatening to post) other people’s personally identifying information (“doxing”).
- * Sharing private content, such as emails sent privately or non-publicly, or unlogged forums such as IRC channel history, without the sender’s consent.
- * Personal insults, especially those using racist or sexist terms.
- * Unwelcome sexual attention.
- * Excessive profanity. Please avoid swearwords; people differ greatly in their sensitivity to swearing.
+4. أن نكون اكثر استطلاعاً. لا أحد علي دراية بكل شئ! طرح الأسئلة في وقت مبكر قد يجنب العديد من المشاكل اللاحقة ، لذا نحن نشجع الأسئلة علي الرغم من أننا قد نعيد توجهها إلي المنتدي المناسب. وسنحاول جاهدين أن نكون متجاوبين ومفيدين.
+5. أن نكون حذريين في اختيار الكلمات. وأن نتوخى الحذر والاحترام في اتصالاتنا، ونتحمل المسؤولية عن خطابنا. وأن نكون عطوفين مع الأخريين. لا تهين أو تحط من قدر المشاركين الآخرين. نحن لن نتقبل المضايقات أو أي سلوك إستباعدي اخر ، مثل:
+ * التهديدات العنيفة أو الخطاب الموجه ضد الأخر.
+ * النكات والتلميحات القائمة علي الجنس أو العرق أو اي أشكال التمييز الأخري.
+ * نشر مواد جنسية صريحة أو مواد تشجع علي العنف.
+ * نشر (أو التهديد بنشر) المعلومات التعريفية الشخصية لأناس آخرين ("doxing").
+ * مشاركة المحتوى الخاص، مثل رسائل البريد الإلكتروني المرسلة بشكل خاص أو غير علني، أو المنتديات غير المسجلة مثل تاريخ قناة IRC، بدون موافقة المرسل.
+ * الإهانات الشخصية، خاصةً التي تستخدم مصطلحات عنصرية أو متحيزة جنسياً.
+ * الاهتمام الجنسي الغير مرحب به.
+ * البذائه المفرطه. Please avoid swearwords; people differ greatly in their sensitivity to swearing.
* Repeated harassment of others. In general, if someone asks you to stop, then stop.
* Advocating for, or encouraging, any of the above behaviour.
From 85b9b1bac2bc8d7b8fe1489cec2da8a7635a140d Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Mon, 29 Mar 2021 08:09:32 +0200
Subject: [PATCH 226/909] New translations code-of-conduct.md (Arabic)
---
content/ar/code-of-conduct.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/content/ar/code-of-conduct.md b/content/ar/code-of-conduct.md
index 6bed4d737d..ab66993697 100644
--- a/content/ar/code-of-conduct.md
+++ b/content/ar/code-of-conduct.md
@@ -29,8 +29,8 @@ aliases:
* مشاركة المحتوى الخاص، مثل رسائل البريد الإلكتروني المرسلة بشكل خاص أو غير علني، أو المنتديات غير المسجلة مثل تاريخ قناة IRC، بدون موافقة المرسل.
* الإهانات الشخصية، خاصةً التي تستخدم مصطلحات عنصرية أو متحيزة جنسياً.
* الاهتمام الجنسي الغير مرحب به.
- * البذائه المفرطه. Please avoid swearwords; people differ greatly in their sensitivity to swearing.
- * Repeated harassment of others. In general, if someone asks you to stop, then stop.
+ * البذائه المفرطه. يرجى تجنب الكلمات البذيئة، يختلف الناس اختلافا كبيرا في حساسيتهم للبذائه.
+ * • المضايقة المتكررة للآخرين. In general, if someone asks you to stop, then stop.
* Advocating for, or encouraging, any of the above behaviour.
### Diversity Statement
From f05cc9e7db49a54ffbe75cbaf57fa98d13e11348 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Mon, 29 Mar 2021 09:13:32 +0200
Subject: [PATCH 227/909] New translations code-of-conduct.md (Arabic)
---
content/ar/code-of-conduct.md | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/content/ar/code-of-conduct.md b/content/ar/code-of-conduct.md
index ab66993697..3785bef768 100644
--- a/content/ar/code-of-conduct.md
+++ b/content/ar/code-of-conduct.md
@@ -21,7 +21,7 @@ aliases:
2. أن نكون عطوفين ومرحبين واكثر ودا وصبرا. نحن نعمل معا لحل الخلافات ونفترض حسن النوايا. قد نواجه بعض الإحباط من حين ألي أخر لكننا لا نسمح للإحباط أن يتحول إلي هجوم شخصي. فالمجتمع الذي يشعر فيه الناس بعدم الارتياح أو بالتهديد ليس مجتمعا منتجا.
3. أن نكون متعاونين. كما سيستفيد بعملنا الآخرين سنستفيد نحن أيضا بعملهم. عندما نقوم بصنع شيئاً لمنفعة المشروع ، سوف نكون علي الاستعداد لشرح للآخرين كيفية عمله ، حتي يكونوا قادرين علي البناء عليه لجعله أفضل. أي قرار سنتخذه سيؤثر علي المستخدمين وعلي زملائنا في العمل لذا يجب أن تأخذ العواقب علي محمل الجد عندما نتخذ القرارات.
4. أن نكون اكثر استطلاعاً. لا أحد علي دراية بكل شئ! طرح الأسئلة في وقت مبكر قد يجنب العديد من المشاكل اللاحقة ، لذا نحن نشجع الأسئلة علي الرغم من أننا قد نعيد توجهها إلي المنتدي المناسب. وسنحاول جاهدين أن نكون متجاوبين ومفيدين.
-5. أن نكون حذريين في اختيار الكلمات. وأن نتوخى الحذر والاحترام في اتصالاتنا، ونتحمل المسؤولية عن خطابنا. وأن نكون عطوفين مع الأخريين. لا تهين أو تحط من قدر المشاركين الآخرين. نحن لن نتقبل المضايقات أو أي سلوك إستباعدي اخر ، مثل:
+5. أن نكون حذريين في اختيار الكلمات. وأن نتوخى الحذر والاحترام في اتصالاتنا، ونتحمل المسؤولية عن خطابنا. وأن نكون عطوفين مع الأخريين. لا تهين أو تحط من قدر المشاركين الآخرين. نحن لن نتقبل المضايقات أو أي سلوك استبعادي أخر ، مثل:
* التهديدات العنيفة أو الخطاب الموجه ضد الأخر.
* النكات والتلميحات القائمة علي الجنس أو العرق أو اي أشكال التمييز الأخري.
* نشر مواد جنسية صريحة أو مواد تشجع علي العنف.
@@ -30,14 +30,14 @@ aliases:
* الإهانات الشخصية، خاصةً التي تستخدم مصطلحات عنصرية أو متحيزة جنسياً.
* الاهتمام الجنسي الغير مرحب به.
* البذائه المفرطه. يرجى تجنب الكلمات البذيئة، يختلف الناس اختلافا كبيرا في حساسيتهم للبذائه.
- * • المضايقة المتكررة للآخرين. In general, if someone asks you to stop, then stop.
- * Advocating for, or encouraging, any of the above behaviour.
+ * • المضايقة المتكررة للآخرين. بشكل عام، إذا طلب منك شخص ما التوقف فيجب عليك التوقف.
+ * الدعوة إلى أي من السلوكيات المذكور أعلاه أو التشجيع إليها.
-### Diversity Statement
+### بيان التنوع
-The NumPy project welcomes and encourages participation by everyone. We are committed to being a community that everyone enjoys being part of. Although we may not always be able to accommodate each individual’s preferences, we try our best to treat everyone kindly.
+يرحب ويشجع مشروع نمباي بمشاركات الجميع. نحن ملتزمون بأن نكون مجتمعا يتمتع كل فرد فيه بكونه جزء منه. وبالرغم أننا قد لا نكون قادرين دوماً على استيعاب تفضيلات كل فرد، إلا إننا حريصين علي بذل قصارى جهدنا لمعاملة الجميع معاملة كريمة.
-No matter how you identify yourself or how others perceive you: we welcome you. Though no list can hope to be comprehensive, we explicitly honour diversity in: age, culture, ethnicity, genotype, gender identity or expression, language, national origin, neurotype, phenotype, political beliefs, profession, race, religion, sexual orientation, socioeconomic status, subculture and technical ability, to the extent that these do not conflict with this code of conduct.
+بغض النظر عن كيفية تعريفك لنفسك أو كيف يتصورك الآخرون: نحن نرحب بك. Though no list can hope to be comprehensive, we explicitly honour diversity in: age, culture, ethnicity, genotype, gender identity or expression, language, national origin, neurotype, phenotype, political beliefs, profession, race, religion, sexual orientation, socioeconomic status, subculture and technical ability, to the extent that these do not conflict with this code of conduct.
Though we welcome people fluent in all languages, NumPy development is conducted in English.
From 4ffc64462d4373d672fe2a014d1e6378594b995e Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Mon, 29 Mar 2021 12:32:15 +0200
Subject: [PATCH 228/909] New translations code-of-conduct.md (Arabic)
---
content/ar/code-of-conduct.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/content/ar/code-of-conduct.md b/content/ar/code-of-conduct.md
index 3785bef768..6ba1f75d2e 100644
--- a/content/ar/code-of-conduct.md
+++ b/content/ar/code-of-conduct.md
@@ -37,11 +37,11 @@ aliases:
يرحب ويشجع مشروع نمباي بمشاركات الجميع. نحن ملتزمون بأن نكون مجتمعا يتمتع كل فرد فيه بكونه جزء منه. وبالرغم أننا قد لا نكون قادرين دوماً على استيعاب تفضيلات كل فرد، إلا إننا حريصين علي بذل قصارى جهدنا لمعاملة الجميع معاملة كريمة.
-بغض النظر عن كيفية تعريفك لنفسك أو كيف يتصورك الآخرون: نحن نرحب بك. Though no list can hope to be comprehensive, we explicitly honour diversity in: age, culture, ethnicity, genotype, gender identity or expression, language, national origin, neurotype, phenotype, political beliefs, profession, race, religion, sexual orientation, socioeconomic status, subculture and technical ability, to the extent that these do not conflict with this code of conduct.
+بغض النظر عن كيفية تعريفك لنفسك أو كيف يتصورك الآخرون: نحن نرحب بك. وعلى الرغم من أنه لا يمكن لأي قائمة أن تكون شاملة، فإننا نكرم بوضوح التنوع في: السن والثقافة والأصل العرقي والوراثي والهوية الجنسية واللغة والأصل القومي وتنوع العصبي والتكوين الظاهري والمعتقد السياسي والمهنة والعرق والديانة والتوجه الجنسي والحالة الاجتماعية الاقتصادية وثقافات الفرعية والقدرات التقنية بما لا يتعارض مع هذه القواعد السلوكية.
-Though we welcome people fluent in all languages, NumPy development is conducted in English.
+على الرغم من أننا نتقبل الناس بجميع اللغات التي يتقنوها، إلا أن تطوير نمباي يجري باستخدام اللغة الإنجليزية.
-Standards for behaviour in the NumPy community are detailed in the Code of Conduct above. Participants in our community should uphold these standards in all their interactions and help others to do so as well (see next section).
+ترد في قواعد السلوكية المذكورة أعلاه تفاصيل معايير السلوك في مجتمع نمباي. Participants in our community should uphold these standards in all their interactions and help others to do so as well (see next section).
### Reporting Guidelines
From cbbf0738f31b54eec35854ff151842b5d2b861c9 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Mon, 29 Mar 2021 13:33:14 +0200
Subject: [PATCH 229/909] New translations code-of-conduct.md (Arabic)
---
content/ar/code-of-conduct.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/content/ar/code-of-conduct.md b/content/ar/code-of-conduct.md
index 6ba1f75d2e..a0d2b7910f 100644
--- a/content/ar/code-of-conduct.md
+++ b/content/ar/code-of-conduct.md
@@ -13,7 +13,7 @@ aliases:
هذه القواعد ليست شاملة أو كاملة. لكنها تساعد علي استخلاص فهمنا المشترك للتعاون في ظل بيئة وأهداف مشتركة. من فضلك حاول أن تتبع هذه القواعد روحا ونصا من أجل إنشاء بيئة ودودة ومنتجة نثري بها المجتمع المحيط.
-### مبادئ توجيهية محددة
+### القواعد الارشادية المحددة
نحن نسعى إلي:
@@ -41,9 +41,9 @@ aliases:
على الرغم من أننا نتقبل الناس بجميع اللغات التي يتقنوها، إلا أن تطوير نمباي يجري باستخدام اللغة الإنجليزية.
-ترد في قواعد السلوكية المذكورة أعلاه تفاصيل معايير السلوك في مجتمع نمباي. Participants in our community should uphold these standards in all their interactions and help others to do so as well (see next section).
+ترد في قواعد السلوكية المذكورة أعلاه تفاصيل معايير السلوك في مجتمع نمباي. وينبغي علي المشاركين في مجتمعنا أن يتمسكوا بهذه المعايير في جميع فعاليتهم وأن يساعدوا الآخرين على القيام بالمثل (انظر الفرع التالي).
-### Reporting Guidelines
+### القواعد الارشادية للإبلاغ
We know that it is painfully common for internet communication to start at or devolve into obvious and flagrant abuse. We also recognize that sometimes people may have a bad day, or be unaware of some of the guidelines in this Code of Conduct. Please keep this in mind when deciding on how to respond to a breach of this Code.
From b5e8daf280536e725f340cb6a34ccc6c6f58cabd Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Tue, 30 Mar 2021 16:26:27 +0200
Subject: [PATCH 230/909] New translations about.md (Japanese)
---
content/ja/about.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/ja/about.md b/content/ja/about.md
index 95a7507a54..e13172f599 100644
--- a/content/ja/about.md
+++ b/content/ja/about.md
@@ -5,7 +5,7 @@ sidebar: false
_このページでは、NumPyのプロジェクトとそれを支えるコミュニティについて説明します。_
-Numpy は Python を使った数値計算のためのオープンソースプロジェクトです。 It was created in 2005, building on the early work of the Numeric and Numarray libraries. NumPyは開発当初から100%オープンソースソフトウェアとして開発されてきました。[修正BSD ライセンス](https://github.com/numpy/numpy/blob/master/LICENSE.txt) の条項の下で、すべての人が利用可能です。
+Numpy は Python を使った数値計算のためのオープンソースプロジェクトです。 Numpyは、Numerical and Numarrayライブラリの初期のコードを基に、2005年から開発がスタートしました。 NumPyは開発当初から100%オープンソースソフトウェアとして開発されてきました。[修正BSD ライセンス](https://github.com/numpy/numpy/blob/master/LICENSE.txt) の条項の下で、すべての人が利用可能です。
Numpy は 、様々な科学Python コミュニティとのコンセンサスを得ながら、GitHub 上でオープンに開発されています。 Numpyのガバナンス方法の詳細については、 [Governance Document](https://www.numpy.org/devdocs/dev/governance/index.html) をご覧ください。
From d0ff2fb54cb56a98240c83b50768c42bf2e3cca9 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Tue, 30 Mar 2021 17:24:09 +0200
Subject: [PATCH 231/909] New translations about.md (Japanese)
---
content/ja/about.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/ja/about.md b/content/ja/about.md
index e13172f599..06843b687b 100644
--- a/content/ja/about.md
+++ b/content/ja/about.md
@@ -1,5 +1,5 @@
---
-title: Numpyプロジェクトについて
+title: 私たちについて
sidebar: false
---
From 882e5ab90ec37d3d425a86fd6addaf38eb66dc76 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Tue, 30 Mar 2021 23:18:43 +0200
Subject: [PATCH 232/909] New translations code-of-conduct.md (Arabic)
---
content/ar/code-of-conduct.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/ar/code-of-conduct.md b/content/ar/code-of-conduct.md
index a0d2b7910f..4f91f7f469 100644
--- a/content/ar/code-of-conduct.md
+++ b/content/ar/code-of-conduct.md
@@ -45,7 +45,7 @@ aliases:
### القواعد الارشادية للإبلاغ
-We know that it is painfully common for internet communication to start at or devolve into obvious and flagrant abuse. We also recognize that sometimes people may have a bad day, or be unaware of some of the guidelines in this Code of Conduct. Please keep this in mind when deciding on how to respond to a breach of this Code.
+نحن نعلم أنه شاع بشكل مؤلم إساءة استخدام الاتصالات عبر الإنترنت في انتهاكات واضحة وصارخة. We also recognize that sometimes people may have a bad day, or be unaware of some of the guidelines in this Code of Conduct. Please keep this in mind when deciding on how to respond to a breach of this Code.
For clearly intentional breaches, report those to the Code of Conduct Committee (see below). For possibly unintentional breaches, you may reply to the person and point out this code of conduct (either in public or in private, whatever is most appropriate). If you would prefer not to do that, please feel free to report to the Code of Conduct Committee directly, or ask the Committee for advice, in confidence.
From 12c717b7af3a088d6fcc67d349485f690915212b Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Wed, 31 Mar 2021 00:26:39 +0200
Subject: [PATCH 233/909] New translations code-of-conduct.md (Arabic)
---
content/ar/code-of-conduct.md | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/content/ar/code-of-conduct.md b/content/ar/code-of-conduct.md
index 4f91f7f469..c25bd00d54 100644
--- a/content/ar/code-of-conduct.md
+++ b/content/ar/code-of-conduct.md
@@ -45,19 +45,19 @@ aliases:
### القواعد الارشادية للإبلاغ
-نحن نعلم أنه شاع بشكل مؤلم إساءة استخدام الاتصالات عبر الإنترنت في انتهاكات واضحة وصارخة. We also recognize that sometimes people may have a bad day, or be unaware of some of the guidelines in this Code of Conduct. Please keep this in mind when deciding on how to respond to a breach of this Code.
+نحن نعلم أنه شاع بشكل مؤلم إساءة استخدام الاتصالات عبر الإنترنت في انتهاكات واضحة وصارخة. وندرك أيضاً أن الناس قد يمرون أحيانا بيوم سيئ أو قد لا يكونون علي دراية ببعض إرشادات القواعد السلوكية. لذا ضع هذا في عين الاعتبار عند اتخاذ القرار بشأن كيفية الرد علي انتهاك هذه القواعد.
-For clearly intentional breaches, report those to the Code of Conduct Committee (see below). For possibly unintentional breaches, you may reply to the person and point out this code of conduct (either in public or in private, whatever is most appropriate). If you would prefer not to do that, please feel free to report to the Code of Conduct Committee directly, or ask the Committee for advice, in confidence.
+أما بالنسبة للانتهاكات المتعمدة بشكل واضح فيجب إبلاغ لجنة قواعد السلوك عليها (انظر أدناه). في حالة حدوث خروفات غير متعمدة فيمكنك الرد على الشخص المعني والإشارة إلى قواعد السلوك هذه (سواء علناً أو سراً، أينما كان ذلك مناسباً). وإذا كنت تفضل عدم القيام بذلك، فلا تتردد في إبلاغ اللجنة المعنية بقواعد السلوك مباشرة ويمكنك أيضاً طلب المشورة من اللجنة بكل ثقة.
-You can report issues to the NumPy Code of Conduct Committee at numpy-conduct@googlegroups.com.
+يمكنك إبلاغ لجنة القواعد السلوكية لنمباي عبر numpy-conduct@googlegroups.com.
-Currently, the Committee consists of:
+وتتألف اللجنة حاليا مما يلي:
-* Stefan van der Walt
-* Melissa Weber Mendonça
-* Anirudh Subramanian
+* ستيفان فان دير والت (Stefan van der Walt)
+* ميليسا فيبر ميندونسا (Melissa Weber Mendonça)
+* أنيروده سوبرامانيان (Anirudh Subramanian)
-If your report involves any members of the Committee, or if they feel they have a conflict of interest in handling it, then they will recuse themselves from considering your report. Alternatively, if for any reason you feel uncomfortable making a report to the Committee, then you can also contact senior NumFOCUS staff at [conduct@numfocus.org](https://numfocus.org/code-of-conduct#persons-responsible).
+لو كان بلاغك متورط به أحد أعضاء اللجنة أو إذا كانوا يشعرون بأن لديهم تضارب في المصالح يحدهم عن التعامل معه. Alternatively, if for any reason you feel uncomfortable making a report to the Committee, then you can also contact senior NumFOCUS staff at [conduct@numfocus.org](https://numfocus.org/code-of-conduct#persons-responsible).
### Incident reporting resolution & Code of Conduct enforcement
From 9dde88bcd0bb3d775ea6caf0e6cde387d6b8a0ad Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Wed, 31 Mar 2021 16:15:13 +0200
Subject: [PATCH 234/909] New translations install.md (Japanese)
---
content/ja/install.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/ja/install.md b/content/ja/install.md
index 82c9aa0e3e..b2b29802a1 100644
--- a/content/ja/install.md
+++ b/content/ja/install.md
@@ -77,7 +77,7 @@ GPUを使用する場合:
#### pip/PyPI を利用したい場合
個人的な好みや、下記のcondaとpipの違いを理解した上で、pip/PyPIベースの方法を使いたいユーザーには、下記をお勧めします:
-- Install Python from [python.org](https://www.python.org/downloads/), [Homebrew](https://brew.sh/), or your Linux package manager.
+- [python.org](https://www.python.org/downloads/)からや、Macを使っている場合は[Homebrew](https://brew.sh/), Linuxを使っている場合は、Linuxのパッケージマネージャーを使ってPythonをインストールします。
- 依存関係の解決と環境の管理を提供する最もよくメンテナンスされているツールとして、[Poetry](https://python-poetry. org/) をconda と同様な方法で使用することができます。
From 00a091cf07316834bc4b24e475f9f7447d4ddf7f Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Wed, 31 Mar 2021 17:34:20 +0200
Subject: [PATCH 235/909] New translations about.md (Japanese)
---
content/ja/about.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/content/ja/about.md b/content/ja/about.md
index 06843b687b..96dbbc14f6 100644
--- a/content/ja/about.md
+++ b/content/ja/about.md
@@ -5,9 +5,9 @@ sidebar: false
_このページでは、NumPyのプロジェクトとそれを支えるコミュニティについて説明します。_
-Numpy は Python を使った数値計算のためのオープンソースプロジェクトです。 Numpyは、Numerical and Numarrayライブラリの初期のコードを基に、2005年から開発がスタートしました。 NumPyは開発当初から100%オープンソースソフトウェアとして開発されてきました。[修正BSD ライセンス](https://github.com/numpy/numpy/blob/master/LICENSE.txt) の条項の下で、すべての人が利用可能です。
+Numpy は Python を使った数値計算のためのオープンソースプロジェクトです。 NumPyは、NumericやNumarrayといった初期のライブラリのコードをもとに、2005年から開発が開始されました。 NumPyは完全にオープンソースなソフトウェアであり、[修正BSD ライセンス](https://github.com/numpy/numpy/blob/master/LICENSE.txt) の条項の下で、すべての人が利用可能です。
-Numpy は 、様々な科学Python コミュニティとのコンセンサスを得ながら、GitHub 上でオープンに開発されています。 Numpyのガバナンス方法の詳細については、 [Governance Document](https://www.numpy.org/devdocs/dev/governance/index.html) をご覧ください。
+NumPy は 、NumPyコミュニティやより広範な科学計算用Python コミュニティとの合意のもと、GitHub 上でオープンに開発されています。 Numpyのガバナンス方法の詳細については、 [Governance Document](https://www.numpy.org/devdocs/dev/governance/index.html) をご覧ください。
## 運営委員会
From 1979f1f759cc6a5b756a7990802a2281e2e90663 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Wed, 31 Mar 2021 17:34:22 +0200
Subject: [PATCH 236/909] New translations arraycomputing.md (Japanese)
---
content/ja/arraycomputing.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/content/ja/arraycomputing.md b/content/ja/arraycomputing.md
index 214d01e34e..a2ac5c4698 100644
--- a/content/ja/arraycomputing.md
+++ b/content/ja/arraycomputing.md
@@ -3,13 +3,13 @@ title: 配列演算
sidebar: false
---
-*配列演算は統計、数学、科学計算の基礎です。可視化、信号処理、画像処理、生命情報学、機械学習、人工知能など、現代のデータサイエンスやデータ分析の様々な分野でも配列演算は中核を担っています。*
+*配列演算は統計、数学、科学計算の基礎です。可視化、信号処理、画像処理、生命情報学、機械学習、人工知能など、現代のデータサイエンスやデータ分析の様々な分野で配列演算は中核を担っています。*
大規模なデータ処理やデータ変換には、効率的な配列演算が重要です。 データ分析や、機械学習、効率的な数値計算に最適な言語のひとつは **Python** です。
-**Num**erical **Py**thon: NumPyは、大規模な多次元配列や行列、そして、それらの配列を処理する様々な分野の数学ルーチンをサポートする、Pythonにおけるデファクトスタンダードなライブラリです。
+**Num**erical **Py**thon: NumPyは、Pythonにおけるデファクトスタンダードなライブラリであり、大規模な多次元配列や行列、そして、それらの配列を処理する様々な分野の数学ルーチンをサポートしています。
-2006年にNumpyが発表されてから、2008年にPandasが登場し、その後、数年間にいくつかの配列演算関連のライブラリが次々と現れるようになりました。そこから配列演算界隈は盛り上がり始めました。 これらの新しい配列演算ライブラリの多くは、Numpy 似た機能を模倣しており、機械学習や人工知能に適した、新しいアルゴリズムや機能を有しています。
+2006年にNumpyが発表されてから、2008年にPandasが登場し、その後、数年間にいくつかの配列演算関連のライブラリが次々と現れるようになりました。そこから配列演算界隈は盛り上がり始めました。 これらの新しい配列演算ライブラリの多くは、NumPyの機能や能力を模倣しており、機械学習や人工知能向けの新しいアルゴリズムや機能を持っています。
Date: Thu, 1 Apr 2021 17:09:31 +0200
Subject: [PATCH 237/909] New translations about.md (Japanese)
---
content/ja/about.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/ja/about.md b/content/ja/about.md
index 96dbbc14f6..f10c620a2b 100644
--- a/content/ja/about.md
+++ b/content/ja/about.md
@@ -5,7 +5,7 @@ sidebar: false
_このページでは、NumPyのプロジェクトとそれを支えるコミュニティについて説明します。_
-Numpy は Python を使った数値計算のためのオープンソースプロジェクトです。 NumPyは、NumericやNumarrayといった初期のライブラリのコードをもとに、2005年から開発が開始されました。 NumPyは完全にオープンソースなソフトウェアであり、[修正BSD ライセンス](https://github.com/numpy/numpy/blob/master/LICENSE.txt) の条項の下で、すべての人が利用可能です。
+NumPy は、Python で数値計算を可能にするためのオープンソースプロジェクトです。 NumPyは、NumericやNumarrayといった初期のライブラリのコードをもとに、2005年から開発が開始されました。 NumPyは完全にオープンソースなソフトウェアであり、[修正BSD ライセンス](https://github.com/numpy/numpy/blob/master/LICENSE.txt) の条項の下で、すべての人が利用可能です。
NumPy は 、NumPyコミュニティやより広範な科学計算用Python コミュニティとの合意のもと、GitHub 上でオープンに開発されています。 Numpyのガバナンス方法の詳細については、 [Governance Document](https://www.numpy.org/devdocs/dev/governance/index.html) をご覧ください。
From c42071957a309ac5f54304c24fca9d9657443a9e Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Thu, 1 Apr 2021 17:09:33 +0200
Subject: [PATCH 238/909] New translations citing-numpy.md (Japanese)
---
content/ja/citing-numpy.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/ja/citing-numpy.md b/content/ja/citing-numpy.md
index 1aa50fa270..587890c75d 100644
--- a/content/ja/citing-numpy.md
+++ b/content/ja/citing-numpy.md
@@ -3,7 +3,7 @@ title: NumPy を引用する場合
sidebar: false
---
-もしあなたの研究においてNumpyが重要な役割を果たし、論文でこのプロジェクトについて言及したい場合は、こちらの論文を引用して下さい。
+もしあなたの研究においてNumPyが重要な役割を果たし、論文でこのプロジェクトについて言及したい場合は、こちらの論文を引用して下さい。
* Harris, C.R., Millman, K.J., van der Walt, S.J. et al. _Array programming with NumPy_. Nature 585, 357–362 (2020). DOI: [0.1038/s41586-020-2649-2](https://doi. org/10.1038/s41586-020-2649-2). ([リンク](https://www.nature.com/articles/s41586-020-2649-2)).
From d0204f6fd20eccc860a0f7c0fb5281c0d82c63bb Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Thu, 1 Apr 2021 18:13:45 +0200
Subject: [PATCH 239/909] New translations about.md (Japanese)
---
content/ja/about.md | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/content/ja/about.md b/content/ja/about.md
index f10c620a2b..530f16d9cb 100644
--- a/content/ja/about.md
+++ b/content/ja/about.md
@@ -12,7 +12,7 @@ NumPy は 、NumPyコミュニティやより広範な科学計算用Python コ
## 運営委員会
-Numpy運営委員会の役割は、Numpyのコミュニティと協力しサポートすることを通じて、技術的にもコミュニティ的にも長期的にNumpyプロジェクトを良い状態に保つことです。 Numpy運営委員会は現在以下のメンバーで構成されています (アルファベット順):
+NumPy運営委員会の役割は、NumPyのコミュニティと協力しサポートすることを通じて、技術的にもコミュニティ的にも長期的にNumPyプロジェクトを良い状態に保つことです。 NumPy運営委員会は現在以下のメンバーで構成されています (アルファベット順):
- Sebastian Berg
- Jaime Fernández del Río
@@ -35,7 +35,7 @@ Numpy運営委員会の役割は、Numpyのコミュニティと協力しサポ
## チーム
-Numpy プロジェクトは拡大しているため、いくつかのチームが設置されています。
+NumPy プロジェクトは拡大しているため、いくつかのチームが設置されています。
- コード
- ドキュメント
@@ -47,23 +47,23 @@ Numpy プロジェクトは拡大しているため、いくつかのチーム
## スポンサー情報
-Numpyは以下の団体から直接資金援助を受けています。
+NumPyは以下の団体から直接資金援助を受けています。
{{< sponsors >}}
## パートナー団体
-パートナー団体は、Numpyへの開発を仕事の一つとして、社員を雇っている団体です。 現在のパートナー団体としては、下記の通りです。
+パートナー団体は、NumPyへの開発を仕事の一つとして、社員を雇っている団体です。 現在のパートナー団体としては、下記の通りです。
{{< partner >}}
## 寄付
-NumPy があなたの仕事や研究、ビジネスで役に立った場合、できる範囲で良いので、是非、Numpyプロジェクトへの寄付を検討して頂けると助かります。 少額の寄付でも大きな助けになります。 すべての寄付は、NumPyのオープンソースソフトウェア、ドキュメント、コミュニティの開発のために使用されることが約束されています。
+NumPy があなたの仕事や研究、ビジネスで役に立った場合、できる範囲で良いので、是非、NumPyプロジェクトへの寄付を検討して頂けると助かります。 少額の寄付でも大きな助けになります。 すべての寄付は、NumPyのオープンソースソフトウェア、ドキュメント、コミュニティの開発のために使用されることが約束されています。
-Numpy は NumFOCUS にスポンサーされたプロジェクトであり、米国の 501(c)(3) 非営利の慈善団体でもあります。 NumFOCUSは、Numpyプロジェクトに財政、法務、管理面でのサポートを提供し、プロジェクトの安定と持続可能性を保つ手助けをしています。 詳細については、 [numfocus.org](https://numfocus.org) をご覧ください。
+NumPy は NumFOCUS にスポンサーされたプロジェクトであり、米国の 501(c)(3) 非営利の慈善団体でもあります。 NumFOCUSは、NumPyプロジェクトに財政、法務、管理面でのサポートを提供し、プロジェクトの安定と持続可能性を保つ手助けをしています。 詳細については、 [numfocus.org](https://numfocus.org) をご覧ください。
-Numpy への寄付は [NumFOCUS](https://numfocus.org) によって管理されています。 米国の寄付提供者の場合、その人の寄付は法律によって定められる範囲で免税されます。 但し、他の寄付と同様に、あなたはあなたの税務状況について、あなたの税務担当と相談する必要があることを忘れないで下さい。
+NumPy への寄付は [NumFOCUS](https://numfocus.org) によって管理されています。 米国の寄付提供者の場合、その人の寄付は法律によって定められる範囲で免税されます。 但し、他の寄付と同様に、あなたはあなたの税務状況について、あなたの税務担当と相談する必要があることを忘れないで下さい。
-Numpyの運営委員会は、受け取った資金をどのように使えば良いかを検討し、使用する方法について決定します. Numpyに関する技術とインフラの投資の優先順位に関しては、[Numpy Roadmap](https://www.numpy.org/neps/index.html#roadmap) に記載されています。
+NumPyの運営委員会は、受け取った資金をどのように使えば良いかを検討し、使用する方法について決定します. NumPyに関する技術とインフラの投資の優先順位に関しては、[NumPy Roadmap](https://www.numpy.org/neps/index.html#roadmap) に記載されています。
{{< numfocus >}}
From fc74c3c9f2417a88ec33d6a8abeaf0a7edb7d489 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Thu, 1 Apr 2021 18:13:47 +0200
Subject: [PATCH 240/909] New translations code-of-conduct.md (Japanese)
---
content/ja/code-of-conduct.md | 36 +++++++++++++++++------------------
1 file changed, 18 insertions(+), 18 deletions(-)
diff --git a/content/ja/code-of-conduct.md b/content/ja/code-of-conduct.md
index 10853e5152..759b2b56c2 100644
--- a/content/ja/code-of-conduct.md
+++ b/content/ja/code-of-conduct.md
@@ -7,26 +7,26 @@ aliases:
### はじめに
-この行動規範は、NumPy プロジェクトによって管理されるすべての場所で適用されます。この場所とは、すべてのパブリックおよびプライベートのメーリングリスト、イシュートラッカー、Wiki、ブログ、Twitter、コミュニティで使用されているその他の通信チャンネルなどを含みます。 Numpy プロジェクトでは対面でのイベントは開催していません。しかし、我々のコミュニティでは、対面でもイベント同様の行動規範を持つ必要があります。
+この行動規範は、NumPy プロジェクトによって管理されるすべての場所で適用されます。この場所とは、すべてのパブリックおよびプライベートのメーリングリスト、イシュートラッカー、Wiki、ブログ、Twitter、コミュニティで使用されているその他の通信チャンネルなどを含みます。 NumPy プロジェクトでは対面でのイベントは開催していません。しかし、我々のコミュニティに関連するものであれば、対面のイベントでも同様の行動規範を持つ必要があります。
-この行動規範は、NumPy コミュニティに正式または非公式に参加するすべての人が順守する必要があります。その他にも、Numpyとの提携、関連するプロジェクト活動、特にそれらのプロジェクトを運営する場合、同様の行動規範に従う必要があります。
+この行動規範は、NumPy コミュニティに正式または非公式に参加するすべての人が順守する必要があります。その他にも、NumPyとの提携・関連するプロジェクト活動においては、特にそれらのプロジェクトを代表する場合、同様の行動規範に従う必要があります。
-この行動規範は完全ではありません。 しかし、行動規範は我々が理解すべき、互いの協力の仕方や、共通の場所のあるべき姿、我々のゴールなどをまとめるのに重要な役目を果たします。 是非、我々のコミュニティをより豊かにし、フレンドリーで生産的な環境を作るために、この行動規範に従ってください。
+この行動規範は完全ではありません。 しかし、行動規範は我々が理解すべき、互いの協力の仕方や、共通の場所のあるべき姿、我々のゴールなどをまとめるのに重要な役目を果たします。 フレンドリーで生産的な環境を生み出し、周囲のコミュニティにより良い影響を与えるため、ぜひこの行動規範に従ってください。
### ガイドラインの概要
私たちは下記の内容に真摯に取り組みます。
-1. 開けたコミュニティにしましょう。 私たちは、誰でもコミュニティに参加できるようにします。 私たちは、何かあまり公にすべきではない内容を議論しない限り、プロジェクト関連のメッセージにはパブリックな通信方法を使用するように努めます。 この行動規範はNumpyのヘルプやプロジェクト関連のサポートのメッセージにも適用されます。パブリックなサポートだけでなく、Numpyに関する質問に答える場合もこの行動規範に従うことがひです。 これにより、質問に答えた時の、無意識な間違いを、より簡単に検出し、訂正できるようになります。
-2. 共感し、歓迎し、友好的で、そして我慢強くありましょう。 私たちはお互いの意見の尊重しあい、互いの善意を信じ合います。 私達はたまに様々な種類の不満を感じるかもしれません。しかしそんな時でも、私達はそのような不満を個人的な攻撃に変えるのを許しません。 なぜなら人々が不快や脅威を感じるコミュニティは、生産的な場所ではないからです。
-3. 互いに協力し合おう。 私たちが開発したものは、他の人々によって使用され、一方で、私たちは他の人が開発しているものに依存しているのです。 私たちがプロジェクトために何かを作るとき、私たちはそれがどのように動作するかを他の人に説明する必要があります。しかし、この作業により、より良いものを作り上げることができるのです。 私達が実施する全ての決断は、全てのユーザと開発コミュニティに影響を与え、その決断による結果を私達は真摯に受け止めます。
-4. 好奇心を大事にしよう。 全てのことを理解している人は存在しません。 早め早めに質問を行うことは、後で多くの問題を回避することができます。なので私達は、それぞれの質問に対して、適切なフォーラムに案内することで、質問を奨励していきます。 私たちは、出来るだけ質問に対する対応を良くし、手助けできるように努力します。
-5. 使う言葉に注意しましょう。 私たちは、コミュニティにおけるコミュニケーションに注意と敬意を払います。そして、私たちは自分の言葉に責任を持つようにします。 他人に優しくしましょう。 他のコミュニティの参加者を侮辱しないでください。 私たちは、以下のようなハラスメントやその他の排斥行為を許しません。:
+1. 開けたコミュニティにしましょう。 私たちは、誰でもコミュニティに参加できるようにします。 私たちは、公にすべきではない内容を議論する場合以外、プロジェクトに関連するメッセージを公の場で告知することを選びます。 これは、NumPyに関するヘルプやプロジェクトサポートにも適用されます。公式なサポートだけでなく、NumPyに関する質問に答える場合もです。 これにより、質問に答えた際の意図しない間違いを、より簡単に検出し、訂正できるようになります。
+2. 共感し、歓迎し、友好的で、そして我慢強くありましょう。 私たちは互いに争いを解決し合い、互いの善意を信じ合います。 私たちは時折り不満を感じるかもしれません。しかしそのような場合も、不満を個人的な攻撃に変えることは許容されません。 人々が不快や脅威を感じるコミュニティは、生産的ではないからです。
+3. 互いに協力し合おう。 私たちの開発成果は他の人々によって利用され、一方で、たちは他の人々の開発成果に依存しているのです。 私たちがプロジェクトために何かを作るとき、私たちはそれがどのように動作するかを他の人に説明する必要があります。しかし、この作業により、より良いものを作り上げることができるのです。 私たちが下す全ての決断は、ユーザと開発コミュニティに影響を与えうるし、その決断がもたらす結果を私たちは真摯に受け止めます。
+4. 好奇心を大事にしよう。 全てを知っている人はいないのです! 早め早めに質問をすることで、後に生じうる多くの問題を回避できます。そのため私たちは質問を奨励しています。もっとも、その質問に対して、適切なフォーラムを紹介する場合もありますが。 私たちは、出来るだけ質問に良く対応し、手助けできるよう努力します。
+5. 使う言葉に注意しましょう。 私たちは、コミュニティにおけるコミュニケーションに注意と敬意を払います。そして、私たちは自分の言葉に責任を持ちます。 他人に優しくしましょう。 他のコミュニティの参加者を侮辱しないでください。 私たちは、以下のようなハラスメントやその他の排斥行為を許しません。:
* 他の人に向けられた暴力的な行為や言葉。
* 性差別や人種差別、その他の差別的なジョークや言動。
* 性的または暴力的な内容の投稿。
* 他のユーザーの個人情報を投稿すること。(または投稿すると脅すこと)。
- * 公開目的のない電子メールや、非公開フォーラム上でものIRCチャネル履歴などのプライベートコンテンツを、送信者の同意なしに共有すること。
+ * 公開目的のない電子メールや、ICRチャットのようなログの残らないフォーラムの履歴など、プライベートなコンテンツを送信者の同意なしに共有すること。
* 個人的な侮辱, 特に人種差別や性差別的な用語を使用して侮辱すること。
* 不快な思いをさせる性的な言動。
* 過度に粗暴に振る舞うこと。 ひどいな言葉を使うのを避けてください。 人々は怒りを覚える感度が、それぞれ大きく異なります。
@@ -35,21 +35,21 @@ aliases:
### 多様性に関する声明
-NumPyプロジェクトは、全ての人の参加を歓迎しています。 私たちは、誰もがコミュニティの一員であることを楽しめるように力を注いでいます。 全ての人が満足できるように対応できるとは限りませんが、全員を出来るだけ親切に扱えるように最善を尽くしていきます。
+NumPyプロジェクトは、全ての人々の参加を歓迎しています。 私たちは、誰もがコミュニティの一員であることを楽しめるように尽力します。 全ての人の好みを満足はさせられないかもしれませんが、全員に対し出来るだけ親切な対応ができるよう最善を尽くします。
-あなたがどのようにあなた自身を認識し、他の人があなたをどのように認識していても、私達 はあなたのプロジェクトへの参加を歓迎します。 下記のリストが全てを含んでいるとは言えませんが、私達は行動規範に反しない限り、下記の多様性を尊重することを明言します。: 年齢、文化。 民族、遺伝、性同一性あるいは関連する表現、言語、国籍、神経学的な差異、生物学的な差異、 政治的信条、職業、人種、宗教、性的指向、社会経済的地位、文化的な差異、技術的な能力。
+あなたの自己認識や、他者のあなたへの認識は関係ありません。私たちはあなたを歓迎します。 完璧なリストは望むべくもありませんが、私たちは行動規範に反しない限り、下記の多様性を尊重すると明言します: 年齢、文化。 民族、遺伝、性同一性あるいは関連する表現、言語、国籍、神経学的な差異、生物学的な差異、 政治的信条、職業、人種、宗教、性的指向、社会経済的地位、文化的な差異、技術的な能力。
-私たちはすべての種類の言語言語話者の参加を歓迎しますが、Numpy 開発は英語で実施します。
+私たちはすべての種類の言語言語話者の参加を歓迎しますが、NumPy 開発は英語で行われます。
-NumPy コミュニティの標準的なルールは、上記の行動規範で説明されています。 我々のコミュニティの参加者は、これらの行動基準をすべてのコミュニケーションにおいて順守し、他の人々にも同様な行動をすることを推奨すべきです。(次のセクションを参照)。
+NumPy コミュニティの標準的なルールは、上記の行動規範で説明されています。 NumPyコミュニティの参加者は、これらの行動基準をすべてのコミュニケーションにおいて順守し、他の人々にも同様な行動をすることを推奨すべきです (次のセクションを参照)。
### 報告ガイドライン
-私たちは、インターネットでの会話が簡単にひどい誹謗中傷になってしまうことを、痛いほど知っています. また、この行動規範のガイドラインにそのような行為が禁止されていることに気づいていない人もいることを認識しています。 行動規範の違反に対応する方法を決定する際には、この事実を覚心に留めておく必要があります。
+私たちは、インターネット上でのやりとりが簡単にひどい誹謗中傷に陥ってしまうことを、痛いほど知っています. 私たちはまた、嫌な日を過ごしてむしゃくしゃしている人や、行動規範ガイドラインの項目を見落としている人がいることも知っています。 行動規範の違反にどのように対処するかを決定する際には、このことを心に留めておく必要があります。
-意図的な行動規範違反については、行動規範委員会に報告してください(下記参照)。 もし、ある行動規範違反が意図的ではない可能性がある場合、あなたはその人にこの行動規範が存在していることを指摘することができます(方法としてはパブリックな方法でもプライベートな方法に、適切な方法であればはどの様な方法でも可能です。)。 もし、直接指摘するのが躊躇われる場合は、是非、行動規範委員会に連絡下さい。 委員会に助言を求めることもできます。
+意図的な行動規範違反については、行動規範委員会に報告してください (下記参照)。 もし、違反が意図的でない可能性がある場合、その人にこの行動規範の存在を知らせることも可能です (パブリックでもプライベートでも、適切な方法で)。 もし直接指摘したくない場合は、ぜひ、行動規範委員会に直接連絡するか、違反の確度について助言を求めて下さい。
-Numpy行動規範委員会に問題を報告する場合はこちらにご連絡下さい: numpy-conduct@googlegroups.com
+NumPy行動規範委員会に問題を報告する場合は、こちらにご連絡下さい: numpy-conduct@googlegroups.com。
現在、行動規範委員会は以下のメンバーで構成されています:
@@ -57,7 +57,7 @@ Numpy行動規範委員会に問題を報告する場合はこちらにご連絡
* Melissa Weber Mendonça
* Anirudh Subramanian
-もしあなたの違反報告に委員会のメンバーが含まれている場合, または彼らがそれを処理する上で利益相反をしていると感じる場合、そのメンバーはあなたの報告を評価する立場からは辞退してもらいます。 または、もしあなたが行動規範委員会に報告するのが躊躇われるばあい、こちらのNumFOCUSのスタッフに連絡することも可能です。:[conduct@numfocus.org](https://numfocus.org/code-of-conduct#persons-responsible).
+もしあなたの違反報告に委員会のメンバーが含まれている場合, または彼らがそれを処理する上で利益相反をしていると感じる場合、そのメンバーはあなたの報告を評価する立場からは辞退してもらいます。 もしくは、行動規範委員会に報告するのが躊躇われる場合は、こちらからNumFOCUSのシニアスタッフに連絡することも可能です:[conduct@numfocus.org](https://numfocus.org/code-of-conduct#persons-responsible) 。
### インシデント報告の解決 & 行動規範の実施
@@ -78,6 +78,6 @@ Numpy行動規範委員会に問題を報告する場合はこちらにご連絡
### 文末脚注:
-私たちは下記のドキュメントの作成したグループに感謝しています。このドキュメントから私たちは我々の行動規範の内容と発想を得ることが出来ました。
+私たちは下記のドキュメントを作成したグループに感謝します。内容・発想ともに大いに影響されています。
- [SciPy行動規範](https://docs.scipy.org/doc/scipy/reference/dev/conduct/code_of_conduct.html)
From f99a6ba8aea2846790ef20e69b791046361f069d Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Mon, 5 Apr 2021 23:20:21 +0200
Subject: [PATCH 241/909] New translations contribute.md (Portuguese,
Brazilian)
---
content/pt/contribute.md | 28 ++++++++++++++--------------
1 file changed, 14 insertions(+), 14 deletions(-)
diff --git a/content/pt/contribute.md b/content/pt/contribute.md
index 74998f1e44..90a4aa3d2d 100644
--- a/content/pt/contribute.md
+++ b/content/pt/contribute.md
@@ -2,26 +2,26 @@
title: Contribua com o NumPy sidebar: false
- - -
-The NumPy project welcomes your expertise and enthusiasm! Your choices aren't limited to programming -- in addition to
+O projeto NumPy precisa de sua experiência e entusiasmo! Suas opções de não são limitadas à programação -- além de
-- [Writing code](#writing-code)
+- [Escrever código](#writing-code)
-you can
+você pode:
-- [Review pull requests](#reviewing-pull-requests)
-- [Develop tutorials, presentations, and other educational material](#developing-educational-materials)
-- [Triage issues](#issue-triaging)
-- [Work on our website](#website-development)
-- [Contribute graphic design](#graphic-design)
-- [Translate website content](#translating-website-content)
-- [Serve as a community coordinator](#community-coordination-and-outreach)
-- [Write grant proposals and help with other fundraising](#fundraising)
+- [Revisar pull requests](#reviewing-pull-requests)
+- [Desenvolver tutoriais, apresentações e outros materiais educacionais](#developing-educational-materials)
+- [Fazer triagem em issues](#issue-triaging)
+- [Trabalhar no nosso site](#website-development)
+- [Contribuir com design gráfico](#graphic-design)
+- [Traduzir conteúdo do site](#translating-website-content)
+- [Trabalhar coordenando a comunidade](#community-coordination-and-outreach)
+- [Escrever propostas e ajudar com outras atividades para financiamento](#fundraising)
-If you're unsure where to start or how your skills fit in, _reach out!_ You can ask on the [mailing list](https://mail.python.org/mailman/listinfo/numpy-discussion) or [GitHub](http://github.com/numpy/numpy) (open an [issue](https://github.com/numpy/numpy/issues) or comment on a relevant issue).
+Se você não sabe por onde começar ou como suas habilidades podem ajudar, _fale conosco!_ Você pode perguntar na nossa [lista de emails](https://mail.python.org/mailman/listinfo/numpy-discussion) ou [GitHub](http://github.com/numpy/numpy) (abrindo uma [issue](https://github.com/numpy/numpy/issues) ou comentando em uma issue relevante).
-Those are our preferred channels (open source is open by nature), but if you prefer to talk privately, contact our community coordinators at or on [Slack](https://numpy-team.slack.com) (write for an invite).
+Estes são os nossos canais de comunicação preferidos (projetos de código aberto são abertos por natureza!). No entanto, se você preferir discutir em privado, entre em contato com os coordenadores da comunidade em ou no [Slack](https://numpy-team.slack.com) (envie um e-mail para para obter um convite antes de entrar).
-We also have a biweekly _community call_, details of which are announced on the [mailing list](https://mail.python.org/mailman/listinfo/numpy-discussion). You are very welcome to join. If you are new to contributing to open source, we also highly recommend reading [this guide](https://opensource.guide/how-to-contribute/).
+Nós também temos uma _reunião aberta da comunidade_ a cada duas semanas. Os detalhes são anunciados na nossa [lista de emails](https://mail.python.org/mailman/listinfo/numpy-discussion). Convidamos você a participar desta chamada se quiser. Se você nunca contribuiu para projetos de código aberto, recomendamos fortemente que você leita [esse guia](https://opensource.guide/how-to-contribute/).
Our community aspires to treat everyone equally and to value all contributions. We have a [Code of Conduct](/code-of-conduct) to foster an open and welcoming environment.
From 4633a44b1e47f870587e4317520cb6ac122270a0 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Mon, 5 Apr 2021 23:20:22 +0200
Subject: [PATCH 242/909] New translations blackhole-image.md (Portuguese,
Brazilian)
---
content/pt/case-studies/blackhole-image.md | 44 +++++++++++-----------
1 file changed, 22 insertions(+), 22 deletions(-)
diff --git a/content/pt/case-studies/blackhole-image.md b/content/pt/case-studies/blackhole-image.md
index e59861dfa2..d07ddd9776 100644
--- a/content/pt/case-studies/blackhole-image.md
+++ b/content/pt/case-studies/blackhole-image.md
@@ -1,5 +1,5 @@
---
-title: "Case Study: First Image of a Black Hole"
+title: "Estudo de Caso: A Primeira Imagem de um Buraco Negro"
sidebar: false
---
@@ -7,58 +7,58 @@ sidebar: false
Criar uma imagem do Buraco Negro M87 é como tentar ver algo que, por definição, é impossível de se ver.
-
+
-## A telescope the size of the earth
+## Um telescópio do tamanho da Terra
-The [Event Horizon telescope (EHT)](https://eventhorizontelescope.org) is an array of eight ground-based radio telescopes forming a computational telescope the size of the earth, studing the universe with unprecedented sensitivity and resolution. The huge virtual telescope, which uses a technique called very-long-baseline interferometry (VLBI), has an angular resolution of [20 micro-arcseconds][resolution] — enough to read a newspaper in New York from a sidewalk café in Paris!
+O [telescópio Event Horizon (EHT)](https://eventhorizontelescope.org), é um conjunto de oito telescópios em solo formando um telescópio computacional do tamanho da Terra, projetado para estudar o universo com sensibilidade e resolução sem precedentes. O enorme telescópio virtual, que usa uma técnica chamada interferometria de longa linha de base (VLBI), tem uma resolução angular de [20 micro-arcossegundos][resolution] — o suficiente para ler um jornal em Nova Iorque a partir de um café em uma calçada de Paris!
### Principais Objetivos e Resultados
-* **A New View of the Universe:** The groundwork for the EHT's groundbreaking image had been laid 100 years earlier when [Sir Arthur Eddington][eddington] yielded the first observational support of Einstein's theory of general relativity.
+* **Uma nova visão do universo:**A imagem inovadora do EHT foi publicada 100 anos após [o experimento de Sir Arthur Eddington][eddington] ter produzido as primeiras evidências observacionais apoiando a teoria da relatividade geral de Einstein.
-* **The Black Hole:** EHT was trained on a supermassive black hole approximately 55 million light-years from Earth, lying at the center of the galaxy Messier 87 (M87) in the Virgo galaxy cluster. Its mass is 6.5 billion times the Sun's. It had been studied for [over 100 years](https://www.jpl.nasa.gov/news/news.php?feature=7385), but never before had a black hole been visually observed.
+* **O Buraco Negro:** o EHT foi treinado em um buraco negro supermassivo a aproximadamente 55 milhões de anos-luz da Terra, localizado no centro do galáxia Messier 87 (M87) no aglomerado de Virgem. Sua massa é equivalente a 6,5 bilhões de vezes a do Sol. Ele vem sendo estudado [há mais de 100 anos](https://www.jpl.nasa.gov/news/news.php?feature=7385), mas um buraco negro nunca havia sido observado visualmente antes.
-* **Comparing Observations to Theory:** From Einstein’s general theory of relativity, scientists expected to find a shadow-like region caused by gravitational bending and capture of light. Scientists could use it to measure the black hole's enormous mass.
+* **Comparando observações com a teoria:** Da teoria geral da relatividade de Einstein, os cientistas esperavam encontrar uma região de sombra causada pela distorção e captura da luz causada pela influência gravitacional do buraco negro. Os cientistas poderiam usá-la para medir sua enorme massa.
### Desafios
-* **Computational scale**
+* **Escala computacional**
- EHT poses massive data-processing challenges, including rapid atmospheric phase fluctuations, large recording bandwidth, and telescopes that are widely dissimilar and geographically dispersed.
+ O EHT representa um desafio imenso em processamento de dados, incluindo flutuações de fase atmosféricas rápidas, uma largura grande de banda nas gravações e telescópios que são muito diferentes e geograficamente dispersos.
-* **Too much information**
+* **Muitas informações**
- Each day EHT generates over 350 terabytes of observations, stored on helium-filled hard drives. Reducing the volume and complexity of this much data is enormously difficult.
+ A cada dia, o EHT gera mais de 350 terabytes de observações, armazenadas em discos rígidos cheios de hélio. Reduzir o volume e a complexidade desse volume de dados é extremamente difícil.
-* **Into the unknown**
+* **Em direção ao desconhecido**
- When the goal is to see something never before seen, how can scientists be confident the image is correct?
+ Quando o objetivo é algo que nunca foi visto, como os cientistas podem ter confiança de que sua imagem está correta?
{{< figure src="/images/content_images/cs/dataprocessbh.png" class="csfigcaption" caption="**Etapas de Processamento de Dados do EHT**" alt="data pipeline" align="middle" attr="(Créditos do diagrama: The Astrophysical Journal, Event Horizon Telescope Collaboration)" attrlink="https://iopscience.iop.org/article/10.3847/2041-8213/ab0c57" >}}
## NumPy’s Role
-What if there's a problem with the data? Or perhaps an algorithm relies too heavily on a particular assumption. Will the image change drastically if a single parameter is changed?
+E se houver um problema com os dados? Ou talvez um algoritmo seja muito dependente de uma hipótese em particular. A imagem será alterada drasticamente se um único parâmetro for alterado?
-The EHT collaboration met these challenges by having independent teams evaluate the data, using both established and cutting-edge image reconstruction techniques. When results proved consistent, they were combined to yield the first-of-a-kind image of the black hole.
+A colaboração do EHT venceu esses desafios ao estabelecer equipes independentes que avaliaram os dados usando técnicas de reconstrução de imagem estabelecidas e de ponta para verificar se as imagens resultantes eram consistentes. Quando os resultados se provaram consistentes, eles foram combinados para produzir a imagem inédita do buraco negro.
-Their work illustrates the role the scientific Python ecosystem plays in advancing science through collaborative data analysis.
+O trabalho desse grupo ilustra o papel do ecossistema científico do Python no avanço da ciência através da análise de dados colaborativa.
-{{< figure src="/images/content_images/cs/bh_numpy_role.png" class="fig-center" alt="role of numpy" caption="**The role of NumPy in Black Hole imaging**" >}}
+{{< figure src="/images/content_images/cs/bh_numpy_role.png" class="fig-center" alt="role of numpy" caption="**O papel do NumPy na criação da primeira imagem de um Buraco Negro**" >}}
-For example, the [`eht-imaging`][ehtim] Python package provides tools for simulating and performing image reconstruction on VLBI data. NumPy is at the core of array data processing used in this package, as illustrated by the partial software dependency chart below.
+Por exemplo, o pacote Python [`eht-imaging`][ehtim] fornece ferramentas para simular e realizar reconstrução de imagem nos dados do VLBI. O NumPy está no coração do processamento de dados vetorial usado neste pacote, como ilustrado pelo gráfico parcial de dependências de software abaixo.
-{{< figure src="/images/content_images/cs/ehtim_numpy.png" class="fig-center" alt="ehtim dependency map highlighting numpy" caption="**Software dependency chart of ehtim package highlighting NumPy**" >}}
+{{< figure src="/images/content_images/cs/ehtim_numpy.png" class="fig-center" alt="ehtim dependency map highlighting numpy" caption="**Diagrama de dependência de software do pacote ehtim evidenciando o NumPy**" >}}
-Besides NumPy, many other packages, such as [SciPy](https://www.scipy.org) and [Pandas](https://pandas.io), are part of the data processing pipeline for imaging the black hole. The standard astronomical file formats and time/coordinate transformations were handled by [Astropy][astropy], while [Matplotlib][mpl] was used in visualizing data throughout the analysis pipeline, including the generation of the final image of the black hole.
+Além do NumPy, muitos outros pacotes como [SciPy](https://www.scipy.org) e [Pandas](https://pandas.io) foram usados na *pipeline* de processamento de dados para criar a imagem do buraco negro. Os formatos de arquivos astronômicos padrão e transformações de tempo/coordenadas foram tratados pelo [Astropy][astropy] enquanto a[Matplotlib][mpl] foi usada na visualização de dados em todas as etapas de análise, incluindo a geração da imagem final do buraco negro.
## Resumo
-The efficient and adaptable n-dimensional array that is NumPy's central feature enabled researchers to manipulate large numerical datasets, providing a foundation for the first-ever image of a black hole. A landmark moment in science, it gives stunning visual evidence of Einstein’s theory. The achievement encompasses not only technological breakthroughs but also international collaboration among over 200 scientists and some of the world's best radio observatories. Innovative algorithms and data processing techniques, improving upon existing astronomical models, helped unfold a mystery of the universe.
+A estrutura de dados n-dimensional que é a funcionalidade central do NumPy permitiu aos pesquisadores manipular grandes conjuntos de dados, fornecendo a base para a primeira imagem de um buraco negro. Esse momento marcante na ciência fornece evidências visuais impressionantes para a teoria de Einstein. Esta conquista abrange não apenas avanços tecnológicos, mas colaboração científica em escala internacional entre mais de 200 cientistas e alguns dos melhores observatórios de rádio do mundo. Eles usaram algoritmos e técnicas de processamento de dados inovadores que aperfeiçoaram os modelos astronômicos existentes para ajudar a descobrir alguns dos mistérios do universo.
-{{< figure src="/images/content_images/cs/numpy_bh_benefits.png" class="fig-center" alt="numpy benefits" caption="**Key NumPy Capabilities utilized**" >}}
+{{< figure src="/images/content_images/cs/numpy_bh_benefits.png" class="fig-center" alt="numpy benefits" caption="**Funcionalidades-chave do NumPy utilizadas**" >}}
[resolution]: https://eventhorizontelescope.org/press-release-april-10-2019-astronomers-capture-first-image-black-hole
From 342eaed90271ae78361cf4cf5b02babec3e59587 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Tue, 6 Apr 2021 00:26:26 +0200
Subject: [PATCH 243/909] New translations about.md (Portuguese, Brazilian)
---
content/pt/about.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/pt/about.md b/content/pt/about.md
index d24405565f..163d4eab78 100644
--- a/content/pt/about.md
+++ b/content/pt/about.md
@@ -5,7 +5,7 @@ sidebar: false
_Algumas informações sobre o projeto NumPy e a comunidade_
-NumPy é um projeto de código aberto visando habilitar a computação numérica com Python. It was created in 2005, building on the early work of the Numeric and Numarray libraries. O NumPy sempre será um software 100% de código aberto, livre para que todos usem e disponibilizados sob os termos liberais da [licença BSD modificada](https://github.com/numpy/numpy/blob/master/LICENSE.txt).
+NumPy é um projeto de código aberto visando habilitar a computação numérica com Python. Foi criado em 2005, com base no trabalho inicial das bibliotecas Numeric e Numarray. O NumPy sempre será um software 100% de código aberto, livre para que todos usem e disponibilizados sob os termos liberais da [licença BSD modificada](https://github.com/numpy/numpy/blob/master/LICENSE.txt).
O NumPy é desenvolvido no GitHub, através do consenso da comunidade NumPy e de uma comunidade científica em Python mais ampla. Para obter mais informações sobre nossa abordagem de governança, por favor, consulte nosso [Documento de Governança](https://www.numpy.org/devdocs/dev/governance/index.html).
From af5399a1cb28d92de13ed5e7890cc022c28b6b78 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Tue, 6 Apr 2021 00:26:27 +0200
Subject: [PATCH 244/909] New translations contribute.md (Portuguese,
Brazilian)
---
content/pt/contribute.md | 54 ++++++++++++++++++++--------------------
1 file changed, 27 insertions(+), 27 deletions(-)
diff --git a/content/pt/contribute.md b/content/pt/contribute.md
index 90a4aa3d2d..eef1b6d84c 100644
--- a/content/pt/contribute.md
+++ b/content/pt/contribute.md
@@ -23,56 +23,56 @@ Estes são os nossos canais de comunicação preferidos (projetos de código abe
Nós também temos uma _reunião aberta da comunidade_ a cada duas semanas. Os detalhes são anunciados na nossa [lista de emails](https://mail.python.org/mailman/listinfo/numpy-discussion). Convidamos você a participar desta chamada se quiser. Se você nunca contribuiu para projetos de código aberto, recomendamos fortemente que você leita [esse guia](https://opensource.guide/how-to-contribute/).
-Our community aspires to treat everyone equally and to value all contributions. We have a [Code of Conduct](/code-of-conduct) to foster an open and welcoming environment.
+Nossa comunidade deseja tratar todos da mesma forma e valorizar todas as contribuições. Temos um [Código de Conduta](/code-of-conduct) para promover um ambiente aberto e acolhedor.
-### Writing code
+### Escrevendo código
-Programmers, this [guide](https://numpy.org/devdocs/dev/index.html#development-process-summary) explains how to contribute to the codebase.
+Para pessoas programadoras, este [guia](https://numpy.org/devdocs/dev/index.html#development-process-summary) explica como contribuir para a base de código.
-### Reviewing pull requests
-The project has more than 250 open pull requests -- meaning many potential improvements and many open-source contributors waiting for feedback. If you're a developer who knows NumPy, you can help even if you're not familiar with the codebase. You can:
-* summarize a long-running discussion
-* triage documentation PRs
-* test proposed changes
+### Revisar pull requests
+O projeto tem mais de 250 pull requests abertos -- o que significa que muitas potenciais melhorias e muitos contribuidores de código aberto estão aguardando feedback. Se você é uma pessoa programadora que conhece o NumPy, você pode ajudar, mesmo que não tenha familiaridade com o código. Você pode:
+* resumir uma discussão longa
+* fazer triagem de PRs de documentação
+* testar alterações propostas
-### Developing educational materials
+### Desenvolvimento de materiais educacionais
-NumPy's [User Guide](https://numpy.org/devdocs) is undergoing rehabilitation. We're in need of new tutorials, how-to's, and deep-dive explanations, and the site needs restructuring. Opportunities aren't limited to writers. We'd also welcome worked examples, notebooks, and videos. [NEP 44 — Restructuring the NumPyDocumentation](https://numpy.org/neps/nep-0044-restructuring-numpy-docs.html) lays out our ideas -- and you may have others.
+O [Guia do Usuário](https://numpy.org/devdocs) do Numpy está sendo reformado. Precisamos de novos tutoriais, how-to's e de explicações de conceitos, e o site precisa de reestruturação. Oportunidades não se limitam a pessoas com experiência em escrita técnica. Também procuramos exemplos práticos, notebooks e vídeos. A [NEP 44](https://numpy.org/neps/nep-0044-restructuring-numpy-docs.html) explica nossas ideias para reestruturar a documentação do NumPy — talvez você também tenha outras ideias.
-### Issue triaging
+### Triagem de Issues
-The [NumPy issue tracker](https://github.com/numpy/numpy/issues) has a _lot_ of open issues. Some are no longer valid, some should be prioritized, and some would make good issues for new contributors. You can:
+O [*issue tracker* do NumPy](https://github.com/numpy/numpy/issues) tem _um monte_ de issues abertas. Algumas não são mais válidas, algumas deveriam ser priorizadas, e algumas poderiam ser boas para pessoas que estão procurando sua primeira contribuição. Você pode:
-* check if older bugs are still present
-* find duplicate issues and link related ones
-* add good self-contained reproducers to issues
-* label issues correctly (this requires triage rights -- just ask)
+* verificar se erros mais antigos ainda estão presentes
+* encontrar issues duplicadas e criar links entre issues relacionadas
+* adicionar bons exemplos autocontidos que reproduzam issues
+* rotular issues corretamente (isso requer direitos de triagem -- basta perguntar)
-Please just dive in.
+Sinta-se à vontade!
-### Website development
+### Desenvolvimento do site
-We've just revamped our website, but we're far from done. If you love web development, these [issues](https://github.com/numpy/numpy.org/issues?q=is%3Aissue+is%3Aopen+label%3Adesign) list some of our unmet needs -- and feel free to share your own ideas.
+Acabamos de renovar o nosso site, mas estamos longe de terminar. Se você adora o desenvolvimento web, estas [issues](https://github.com/numpy/numpy.org/issues?q=is%3Aissue+is%3Aopen+label%3Adesign) listam algumas de nossas necessidades não atendidas -- e sinta-se livre para compartilhar suas próprias ideias.
-### Graphic design
+### Design gráfico
-We can barely begin to list the contributions a graphic designer can make here. Our docs are parched for illustration; our growing website craves images -- opportunities abound.
+Nós mal podemos começar a listar as contribuições que uma pessoa com conhecimento em design gráfico pode fazer aqui. Nossa documentação precisa de ilustrações; nosso site crescente precisa de imagens -- há muitas oportunidades.
-### Translating website content
+### Traduzir conteúdo do site
-We plan multiple translations of [numpy.org](https://numpy.org) to make NumPy accessible to users in their native language. Volunteer translators are at the heart of this effort. See [here](https://numpy.org/neps/nep-0028-website-redesign.html#translation-multilingual-i18n) for background; comment on [this GitHub issue](https://github.com/numpy/numpy.org/issues/55) to sign up.
+Planejamos várias traduções do [numpy.org](https://numpy.org) para tornar o NumPy acessível aos usuários em seu idioma nativo. Tradutores voluntários estão no coração deste esforço. Veja [aqui](https://numpy.org/neps/nep-0028-website-redesign.html#translation-multilingual-i18n) para informações; comente [nesta issue do GitHub](https://github.com/numpy/numpy.org/issues/55) para se envolver.
-### Community coordination and outreach
+### Coordenação e promoção na comunidade
-Through community contact we share our work more widely and learn where we're falling short. We're eager to get more people involved in efforts like our [Twitter](https://twitter.com/numpy_team) account, organizing NumPy [code sprints](https://scisprints.github.io/), a newsletter, and perhaps a blog.
+Através do contato com a comunidade podemos compartilhar nosso trabalho para mais pessoas e descobrir onde precisamos trabalhar mais. Estamos ansiosos para que mais pessoas se envolvam em esforços como nossa conta no [Twitter](https://twitter.com/numpy_team), na organização de [sprints](https://scisprints.github.io/) sobre o NumPy, uma newsletter, e talvez um blog.
-### Fundraising
+### Financiamento
-NumPy was all-volunteer for many years, but as its importance grew it became clear that to ensure stability and growth we'd need financial support. [This SciPy'19 talk](https://www.youtube.com/watch?v=dBTJD_FDVjU) explains how much difference that support has made. Like all the nonprofit world, we're constantly searching for grants, sponsorships, and other kinds of support. We have a number of ideas and of course we welcome more. Fundraising is a scarce skill here -- we'd appreciate your help.
+O NumPy foi um projeto totalmente voluntário por muitos anos, mas conforme sua importância cresceu, tornou-se clara a necessidade de apoio financeiro para garantir estabilidade e crescimento. [Esta palestra na SciPy'19](https://www.youtube.com/watch?v=dBTJD_FDVjU) explica quanta diferença esse suporte fez. Como todo o mundo das organizações sem fins lucrativos, nós estamos constantemente procurando bolsas, patrocinadores e outros tipos de apoio. Nós temos uma série de ideias e é claro que nós damos as boas-vindas a mais. Habilidade de buscar financiamento é uma habilidade rara aqui -- apreciaríamos a sua ajuda.
From 82c6d9e3cceb9282ef91042a0c04437b071be236 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Tue, 6 Apr 2021 00:26:29 +0200
Subject: [PATCH 245/909] New translations install.md (Portuguese, Brazilian)
---
content/pt/install.md | 76 +++++++++++++++++++++----------------------
1 file changed, 38 insertions(+), 38 deletions(-)
diff --git a/content/pt/install.md b/content/pt/install.md
index ccaad9e92f..b86910dc56 100644
--- a/content/pt/install.md
+++ b/content/pt/install.md
@@ -3,46 +3,46 @@ title: Instalando o NumPy
sidebar: false
---
-The only prerequisite for installing NumPy is Python itself. If you don't have Python yet and want the simplest way to get started, we recommend you use the [Anaconda Distribution](https://www.anaconda.com/distribution) - it includes Python, NumPy, and many other commonly used packages for scientific computing and data science.
+O único pré-requisito para instalar o NumPy é o próprio Python. Se você ainda não tem o Python e quer começar do jeito mais simples, nós recomendamos que você use a [Distribuição Anaconda](https://www.anaconda.com/distribution) - inclui Python, NumPy e outros pacotes comumente usados para computação científica e ciência de dados.
-NumPy can be installed with `conda`, with `pip`, with a package manager on macOS and Linux, or [from source](https://numpy.org/devdocs/user/building.html). For more detailed instructions, consult our [Python and NumPy installation guide](#python-numpy-install-guide) below.
+O NumPy pode ser instalado com `conda`, com `pip`, com um gerenciador de pacotes no macOS e Linux, ou [da fonte](https://numpy.org/devdocs/user/building.html). Para obter instruções mais detalhadas, consulte nosso [guia de instalação do Python e do NumPy](#python-numpy-install-guide) abaixo.
**CONDA**
-If you use `conda`, you can install NumPy from the `defaults` or `conda-forge` channels:
+Se você usar o `conda`, você pode instalar o NumPy do canal `default` ou do `conda-forge`:
```bash
-# Best practice, use an environment rather than install in the base env
+# Recomenda-se usar um ambiente novo ao invés de instalar no ambiente-base
conda create -n my-env
conda activate my-env
-# If you want to install from conda-forge
+# Se quiser instalar do conda-forge
conda config --env --add channels conda-forge
-# The actual install command
+# O comando para instação
conda install numpy
```
**PIP**
-If you use `pip`, you can install NumPy with:
+Se você usa o `pip`, você pode instalar o NumPy com:
```bash
pip install numpy
```
-Also when using pip, it's good practice to use a virtual environment - see [Reproducible Installs](#reproducible-installs) below for why, and [this guide](https://dev.to/bowmanjd/python-tools-for-managing-virtual-environments-3bko#howto) for details on using virtual environments.
+Também ao usar o pip, é uma boa prática usar um ambiente virtual - veja em [Instalações Reprodutíveis](#reproducible-installs) abaixo por quê, e [esse guia](https://dev.to/bowmanjd/python-tools-for-managing-virtual-environments-3bko#howto) para detalhes sobre o uso de ambientes virtuais.
# Guia de instalação do Python e do NumPy
-Installing and managing packages in Python is complicated, there are a number of alternative solutions for most tasks. This guide tries to give the reader a sense of the best (or most popular) solutions, and give clear recommendations. It focuses on users of Python, NumPy, and the PyData (or numerical computing) stack on common operating systems and hardware.
+Instalar e gerenciar pacotes no Python pode ser complicado. Há várias soluções alternativas para a maioria das tarefas. Este guia tenta dar ao leitor um resumo das melhores (ou mais populares) soluções e dar recomendações claras. Ele se concentra em usuários do Python, NumPy e do PyData (ou computação numérica) em sistemas operacionais e hardware comuns.
-## Recommendations
+## Recomendações
-We'll start with recommendations based on the user's experience level and operating system of interest. If you're in between "beginning" and "advanced", please go with "beginning" if you want to keep things simple, and with "advanced" if you want to work according to best practices that go a longer way in the future.
+Vamos começar com recomendações baseadas no nível de experiência do usuário e no sistema operacional de interesse. Se você estiver entre "iniciante" e "avançado", por favor, escolha "iniciante" se você quiser manter as coisas simples, e "avançado" se você quiser trabalhar de acordo com as melhores práticas que te ajudarão a ir mais longe no futuro.
### Usuários iniciantes
-On all of Windows, macOS, and Linux:
+Em Windows, macOS e Linux:
- Instale o [Anaconda](https://www.anaconda.com/distribution/) (instala todos os pacotes que você precisa e todas as outras ferramentas mencionadas abaixo).
- Para escrever e executar código, use notebooks no [JupyterLab](https://jupyterlab.readthedocs.io/en/stable/index.html) para a computação exploratória e interativa, e o [Spyder](https://www.spyder-ide.org/) ou [Visual Studio Code](https://code.visualstudio.com/) para escrever scripts e pacotes.
@@ -60,78 +60,78 @@ On all of Windows, macOS, and Linux:
#### Linux
-If you're fine with slightly outdated packages and prefer stability over being able to use the latest versions of libraries:
+Se você não tiver problemas em ter pacotes um pouco desatualizados e preferir estabilidade ao invés de ser capaz de usar as últimas versões das bibliotecas:
- Use seu gerenciador de pacotes do SO o máximo possível (para o Python, NumPy e outras bibliotecas).
- Instale pacotes não fornecidos pelo seu gerenciador de pacotes com `pip install algumpacote --user`.
-If you use a GPU:
+Se você usa uma GPU:
- Instale o [Miniconda](https://docs.conda.io/en/latest/miniconda.html).
- Mantenha o ambiente conda `base` mínimo, e use um ou mais [ambientes conda](https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#) para instalar o pacote que você precisa para a tarefa ou projeto em que você está trabalhando.
- Use o canal conda`defaults` (`conda-forge` não tem bom suporte para pacotes de GPU).
-Otherwise:
+Caso contrário:
- Instale o [Miniforge](https://github.com/conda-forge/miniforge).
- Mantenha o ambiente conda `base` mínimo, e use um ou mais [ambientes conda](https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#) para instalar o pacote que você precisa para a tarefa ou projeto em que você está trabalhando.
#### Alternativa se você preferir pip/PyPI
-For users who know, from personal preference or reading about the main differences between conda and pip below, they prefer a pip/PyPI-based solution, we recommend:
-- Install Python from [python.org](https://www.python.org/downloads/), [Homebrew](https://brew.sh/), or your Linux package manager.
+Para usuários que preferem uma solução baseada em pip/PyPI, por preferência pessoal ou leitura sobre as principais diferenças entre o conda e o pip, nós recomendamos:
+- Instale o Python a partir de, por exemplo, [python.org](https://www.python.org/downloads/), [Homebrew](https://brew.sh/), ou seu gerenciador de pacotes Linux.
- Use [Poetry](https://python-poetry.org/) como a ferramenta mais bem mantida que fornece um resolvedor de dependências e recursos de gerenciamento de ambiente de forma semelhante ao que o conda faz.
-## Python package management
+## Gerenciamento de pacotes Python
-Managing packages is a challenging problem, and, as a result, there are lots of tools. For web and general purpose Python development there's a whole [host of tools](https://packaging.python.org/guides/tool-recommendations/) complementary with pip. For high-performance computing (HPC), [Spack](https://github.com/spack/spack) is worth considering. For most NumPy users though, [conda](https://conda.io/en/latest/) and [pip](https://pip.pypa.io/en/stable/) are the two most popular tools.
+Gerenciar pacotes é um problema desafiador e, como resultado, há muitas ferramentas. Para o desenvolvimento web e de propósito geral em Python, há uma [série de ferramentas](https://packaging.python.org/guides/tool-recommendations/) complementares com pip. Para computação de alto desempenho (HPC), vale a pena considerar o [Spack](https://github.com/spack/spack). Para a maioria dos usuários NumPy, porém, o [conda](https://conda.io/en/latest/) e o [pip](https://pip.pypa.io/en/stable/) são as duas ferramentas mais populares.
### Pip & conda
-The two main tools that install Python packages are `pip` and `conda`. Their functionality partially overlaps (e.g. both can install `numpy`), however, they can also work together. We'll discuss the major differences between pip and conda here - this is important to understand if you want to manage packages effectively.
+As duas principais ferramentas que instalam pacotes do Python são `pip` e `conda`. Algumas de suas funcionalidades são redundantes (por exemplo, ambos podem instalar o `numpy`). No entanto, elas também podem trabalhar juntas. Vamos discutir as principais diferenças entre o pip e o conda aqui - é importante entender isso se você deseja gerenciar pacotes de forma efetiva.
-The first difference is that conda is cross-language and it can install Python, while pip is installed for a particular Python on your system and installs other packages to that same Python install only. This also means conda can install non-Python libraries and tools you may need (e.g. compilers, CUDA, HDF5), while pip can't.
+A primeira diferença é que "conda" é multilinguagens e pode instalar o Python, enquanto o pip é instalado em um determinado Python em seu sistema e instala outros pacotes apenas para essa mesma instalação de Python. Isto também significa que o conda pode instalar bibliotecas e ferramentas não-Python das quais você pode precisar (por exemplo, compiladores, CUDA, HDF5), enquanto pip não pode.
-The second difference is that pip installs from the Python Packaging Index (PyPI), while conda installs from its own channels (typically "defaults" or "conda-forge"). PyPI is the largest collection of packages by far, however, all popular packages are available for conda as well.
+A segunda diferença é que o pip instala do Índice de Pacotes Python (Python Packaging Index - PyPI), enquanto o conda instala de seus próprios canais (tipicamente "defaults" ou "conda-forge"). PyPI é a maior coleção de pacotes, no entanto, todos os pacotes populares também estão disponíveis para conda.
-The third difference is that conda is an integrated solution for managing packages, dependencies and environments, while with pip you may need another tool (there are many!) for dealing with environments or complex dependencies.
+A terceira diferença é que o conda é uma solução integrada para gerenciar pacotes, dependências e ambientes, enquanto com o pip você pode precisar de outra ferramenta (há muitas!) para lidar com ambientes ou dependências complexas.
### Instalações reprodutíveis
-As libraries get updated, results from running your code can change, or your code can break completely. It's important to be able to reconstruct the set of packages and versions you're using. Best practice is to:
+À medida que as bibliotecas são atualizadas, os resultados obtidos ao executar seu código podem mudar, ou o seu código pode parar de funcionar. É importante poder reconstruir o conjunto de pacotes e versões que você está usando. A recomendação é:
-1. use a different environment per project you're working on,
-2. record package names and versions using your package installer; each has its own metadata format for this:
+1. usar um ambiente diferente para cada projeto em que você trabalha,
+2. gravar nomes de pacotes e versões usando seu instalador de pacotes; cada um tem seu próprio formato de metadados para essa tarefa:
- Conda: [ambientes conda e arquivos environment.yml](https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#)
- Pip: [ambientes virtuais](https://docs.python.org/3/tutorial/venv.html) e [requirements.txt](https://pip.readthedocs.io/en/latest/user_guide/#requirements-files)
- Poetry: [ambientes virtuais e pyproject.toml](https://python-poetry.org/docs/basic-usage/)
-## NumPy packages & accelerated linear algebra libraries
+## Pacotes NumPy & bibliotecas de álgebra linear aceleradas
-NumPy doesn't depend on any other Python packages, however, it does depend on an accelerated linear algebra library - typically [Intel MKL](https://software.intel.com/en-us/mkl) or [OpenBLAS](https://www.openblas.net/). Users don't have to worry about installing those (they're automatically included in all NumPy install methods). Power users may still want to know the details, because the used BLAS can affect performance, behavior and size on disk:
+O NumPy não depende de quaisquer outros pacotes Python. No entanto, depende de uma biblioteca de álgebra linear acelerada - tipicamente [Intel MKL](https://software.intel.com/en-us/mkl) ou [OpenBLAS](https://www.openblas.net/). Os usuários não precisam se preocupar com a instalação desses pacotes (eles são incluídos automaticamente em todos os métodos de instalação do NumPy). No entanto, usuários experientes podem querer saber os detalhes, porque o BLAS usado pode afetar o desempenho, o comportamento e o tamanho em disco:
-- The NumPy wheels on PyPI, which is what pip installs, are built with OpenBLAS. The OpenBLAS libraries are included in the wheel. This makes the wheel larger, and if a user installs (for example) SciPy as well, they will now have two copies of OpenBLAS on disk.
+- As wheels da NumPy no PyPI, que é o que o pip instala, são compiladas com OpenBLAS. As bibliotecas da OpenBLAS são empacotadas dentro da wheel. Isso faz com que a wheel fique maior, e se um usário também instalar (por exemplo) a SciPy, terá agora duas cópias da OpenBLAS no disco.
-- In the conda defaults channel, NumPy is built against Intel MKL. MKL is a separate package that will be installed in the users' environment when they install NumPy.
+- No canal defaults do conda, a NumPy é compilada com a Intel MKL. MKL é um pacote separado que será instalado no ambiente do usuário quando instalar a NumPy.
-- In the conda-forge channel, NumPy is built against a dummy "BLAS" package. When a user installs NumPy from conda-forge, that BLAS package then gets installed together with the actual library - this defaults to OpenBLAS, but it can also be MKL (from the defaults channel), or even [BLIS](https://github.com/flame/blis) or reference BLAS.
+- No canal do conda-Forge, a NumPy é compilada com um pacote "BLAS" fictício. Quando um usuário instala o NumPy do conda-forge, esse pacote BLAS então é instalado juntamente com a biblioteca real - o padrão é OpenBLAS, mas também pode ser MKL (do canal defaults), ou até mesmo [BLIS](https://github.com/flame/blis) ou *reference BLAS*.
-- The MKL package is a lot larger than OpenBLAS, it's about 700 MB on disk while OpenBLAS is about 30 MB.
+- O pacote MKL é muito maior que o OpenBLAS, ocupa cerca de 700 MB no disco enquanto OpenBLAS ocupa cerca de 30 MB.
-- MKL is typically a little faster and more robust than OpenBLAS.
+- A MKL é normalmente um pouco mais rápida e mais robusta do que a OpenBLAS.
-Besides install sizes, performance and robustness, there are two more things to consider:
+Além do tamanho instalado, desempenho e robustez, há mais duas coisas a se considerar:
-- Intel MKL is not open source. For normal use this is not a problem, but if a user needs to redistribute an application built with NumPy, this could be an issue.
-- Both MKL and OpenBLAS will use multi-threading for function calls like `np.dot`, with the number of threads being determined by both a build-time option and an environment variable. Often all CPU cores will be used. This is sometimes unexpected for users; NumPy itself doesn't auto-parallelize any function calls. It typically yields better performance, but can also be harmful - for example when using another level of parallelization with Dask, scikit-learn or multiprocessing.
+- A Intel MKL não é de código aberto. Para uso normal isto não é um problema, mas se um usuário precisa redistribuir uma aplicação compilada com a NumPy, isso pode ser um problema.
+- Tanto MKL quanto OpenBLAS usarão multi-threading para chamadas de função como `np.dot`, com o número de threads sendo determinado tanto por uma opção no momento da compilação quanto por uma variável de ambiente. Muitas vezes, todos os núcleos de CPU serão usados. Isto é, às vezes, inesperado para usuários; o NumPy em si não paraleliza automaticamente nenhuma chamada de função. Normalmente, isso produz melhor desempenho, mas também pode ser prejudicial - por exemplo, ao usar outro nível de paralelização com Dask, scikit-learn ou multiprocessamento.
-## Troubleshooting
+## Solução de problemas
-If your installation fails with the message below, see [Troubleshooting ImportError](https://numpy.org/doc/stable/user/troubleshooting-importerror.html).
+Se sua instalação falhar com a mensagem abaixo, consulte [Solucionando ImportError](https://numpy.org/doc/stable/user/troubleshooting-importerror.html).
```
IMPORTANT: PLEASE READ THIS FOR ADVICE ON HOW TO SOLVE THIS ISSUE!
From c128fa4fe4bb17d11ff2e3022447e0237ca0412f Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Tue, 6 Apr 2021 00:26:30 +0200
Subject: [PATCH 246/909] New translations learn.md (Portuguese, Brazilian)
---
content/pt/learn.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/pt/learn.md b/content/pt/learn.md
index 4f339d762f..6d8d5b6a24 100644
--- a/content/pt/learn.md
+++ b/content/pt/learn.md
@@ -3,7 +3,7 @@ title: Aprenda
sidebar: false
---
-For the **official NumPy documentation** visit [numpy.org/doc/stable](https://numpy.org/doc/stable).
+Para a **documentação oficial do NumPy** visite [numpy.org/doc/stable](https://numpy.org/doc/stable).
Abaixo está uma coleção de recursos externos selecionados. Para contribuir, veja o [fim desta página](#add-to-this-list).
***
From ff1e889e75374ed788fff45b13cfb7ef18c7366a Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Tue, 6 Apr 2021 00:26:31 +0200
Subject: [PATCH 247/909] New translations news.md (Portuguese, Brazilian)
---
content/pt/news.md | 88 +++++++++++++++++++++++-----------------------
1 file changed, 44 insertions(+), 44 deletions(-)
diff --git a/content/pt/news.md b/content/pt/news.md
index 4e7060b82a..dd7a55e3c8 100644
--- a/content/pt/news.md
+++ b/content/pt/news.md
@@ -3,87 +3,87 @@ title: Notícias
sidebar: false
---
-### Numpy 1.20.0 release
+### NumPy versão 1.20.0
-_Jan 30, 2021_ -- [NumPy 1.20.0](https://numpy.org/doc/stable/release/1.20.0-notes.html) is now available. This is the largest NumPy release to date, thanks to 180+ contributors. The two most exciting new features are:
-- Type annotations for large parts of NumPy, and a new `numpy.typing` submodule containing `ArrayLike` and `DtypeLike` aliases that users and downstream libraries can use when adding type annotations in their own code.
-- Multi-platform SIMD compiler optimizations, with support for x86 (SSE, AVX), ARM64 (Neon), and PowerPC (VSX) instructions. This yielded significant performance improvements for many functions (examples: [sin/cos](https://github.com/numpy/numpy/pull/17587), [einsum](https://github.com/numpy/numpy/pull/18194)).
+_30 de janeiro de 2021_ -- O [NumPy 1.20.0](https://numpy.org/doc/stable/release/1.20.0-notes.html) está disponível. Este é o maior release do NumPy até agora, graças a mais de 180 contribuidores. As duas novidades mais emocionantes são:
+- Anotações de tipos para grandes partes do NumPy, e um novo submódulo `numpy.typing` contendo aliases `ArrayLike` e `DtypeLike` que usuários e bibliotecas downstream podem usar quando quiserem adicionar anotações de tipos em seu próprio código.
+- Otimizações de compilação SIMD multi-plataforma, com suporte para instruções x86 (SSE, AVX), ARM64 (Neon) e PowerPC (VSX). Isso rendeu melhorias significativas de desempenho para muitas funções (exemplos: [sen/cos](https://github.com/numpy/numpy/pull/17587), [einsum](https://github.com/numpy/numpy/pull/18194)).
-### Diversity in the NumPy project
+### Diversidade no projeto NumPy
-_Sep 20, 2020_ -- We wrote a [statement on the state of, and discussion on social media around, diversity and inclusion in the NumPy project](/diversity_sep2020).
+_20 de setembro de 2020_ -- Escrevemos uma [declaração sobre o estado da diversidade e inclusão no projeto NumPy e discussões em redes sociais sobre isso.](/diversity_sep2020).
-### First official NumPy paper published in Nature!
+### Primeiro artigo oficial do NumPy publicado na Nature!
-_Sep 16, 2020_ -- We are pleased to announce the publication of [the first official paper on NumPy](https://www.nature.com/articles/s41586-020-2649-2) as a review article in Nature. This comes 14 years after the release of NumPy 1.0. The paper covers applications and fundamental concepts of array programming, the rich scientific Python ecosystem built on top of NumPy, and the recently added array protocols to facilitate interoperability with external array and tensor libraries like CuPy, Dask, and JAX.
+_16 de setembro de 2020_ -- Temos o prazer de anunciar a publicação do [primeiro artigo oficial do NumPy](https://www.nature.com/articles/s41586-020-2649-2) como um artigo de revisão na Nature. Isso ocorre 14 anos após o lançamento do NumPy 1.0. O artigo abrange aplicações e conceitos fundamentais da programação de matrizes, o rico ecossistema científico de Python construído em cima do NumPy, e os protocolos de array recentemente adicionados para facilitar a interoperabilidade com bibliotecas externas para computação com matrizes e tensores, como CuPy, Dask e JAX.
-### Python 3.9 is coming, when will NumPy release binary wheels?
+### O Python 3.9 está chegando, quando o NumPy vai liberar wheels binárias?
-_Sept 14, 2020_ -- Python 3.9 will be released in a few weeks. If you are an early adopter of Python versions, you may be dissapointed to find that NumPy (and other binary packages like SciPy) will not have binary wheels ready on the day of the release. It is a major effort to adapt the build infrastructure to a new Python version and it typically takes a few weeks for the packages to appear on PyPI and conda-forge. In preparation for this event, please make sure to
-- update your `pip` to version 20.1 at least to support `manylinux2010` and `manylinux2014`
-- use [`--only-binary=numpy`](https://pip.pypa.io/en/stable/reference/pip_install/#cmdoption-only-binary) or `--only-binary=:all:` to prevent `pip` from trying to build from source.
+_14 de setembro de 2020_ -- Python 3.9 será lançado em algumas semanas. Se você for quiser usar imediatamente a nova versão do Python, você pode ficar desapontado ao descobrir que o NumPy (e outros pacotes binários como SciPy) não terão wheels no dia do lançamento. É um grande esforço adaptar a infraestrutura de compilação a uma nova versão de Python e normalmente leva algumas semanas para que os pacotes apareçam no PyPI e no conda-forge. Em preparação para este evento, por favor, certifique-se de
+- atualizar seu `pip` para a versão 20.1 pelo menos para suportar `manylinux2010` e `manylinux2014`
+- usar [`--only-binary=numpy`](https://pip.pypa.io/en/stable/reference/pip_install/#cmdoption-only-binary) ou `--only-binary=:all:` para impedir `pip` de tentar compilar a partir do código fonte.
-### Numpy 1.19.2 release
+### NumPy versão 1.19.2
-_Sep 10, 2020_ -- [NumPy 1.19.2](https://numpy.org/devdocs/release/1.19.2-notes.html) is now available. This latest release in the 1.19 series fixes several bugs, prepares for the [upcoming Cython 3.x release](http://docs.cython.org/en/latest/src/changes.html) and pins setuptools to keep distutils working while upstream modifications are ongoing. The aarch64 wheels are built with the latest manylinux2014 release that fixes the problem of differing page sizes used by different linux distros.
+_10 de setembro de 2020_ -- O [NumPy 1.19.2](https://numpy.org/devdocs/release/1.19.2-notes.html) está disponível. Essa última versão da série 1.19 corrige vários bugs, inclui preparações para o lançamento [do Cython 3](http://docs.cython.org/en/latest/src/changes.html) e fixa o setuptools para que o distutils continue funcionando enquanto modificações upstream estão sendo feitas. As wheels para aarch64 são compiladas com manylinux2014 mais recente que conserta um problema com distribuições linux diferentes.
-### The inaugural NumPy survey is live!
+### A primeira pesquisa NumPy está aqui!
-_Jul 2, 2020_ -- This survey is meant to guide and set priorities for decision-making about the development of NumPy as software and as a community. The survey is available in 8 additional languages besides English: Bangla, Hindi, Japanese, Mandarin, Portuguese, Russian, Spanish and French.
+_2 de julho de 2020_ -- Esta pesquisa tem como objetivo guiar e definir prioridades para tomada de decisões sobre o desenvolvimento do NumPy como software e como comunidade. A pesquisa está disponível em mais 8 idiomas além do inglês: Bangla, Hindi, Japonês, Mandarim, Português, Russo, Espanhol e Francês.
-Please help us make NumPy better and take the survey [here](https://umdsurvey.umd.edu/jfe/form/SV_8bJrXjbhXf7saAl).
+Ajude-nos a melhorar o NumPy respondendo à pesquisa [aqui](https://umdsurvey.umd.edu/jfe/form/SV_8bJrXjbhXf7saAl).
-### NumPy has a new logo!
+### O NumPy tem um novo logo!
-_Jun 24, 2020_ -- NumPy now has a new logo:
+_24 de junho de 2020_ -- NumPy agora tem um novo logo:
-The logo is a modern take on the old one, with a cleaner design. Thanks to Isabela Presedo-Floyd for designing the new logo, as well as to Travis Vaught for the old logo that served us well for 15+ years.
+O logo é uma versão moderna do antigo, com um design mais limpo. Obrigado a Isabela Presedo-Floyd por projetar o novo logo, bem como o Travis Vaught pelo o logo antigo que nos serviu bem durante mais de 15 anos.
-### NumPy 1.19.0 release
+### NumPy versão 1.19.0
-_Jun 20, 2020_ -- NumPy 1.19.0 is now available. This is the first release without Python 2 support, hence it was a "clean-up release". The minimum supported Python version is now Python 3.6. An important new feature is that the random number generation infrastructure that was introduced in NumPy 1.17.0 is now accessible from Cython.
+_20 de junho de 2020_ -- O NumPy 1.19.0 está disponível. Esta é a primeira versão sem suporte ao Python 2, portanto foi uma "versão de limpeza". A versão mínima de Python suportada agora é Python 3.6. Uma característica nova importante é que a infraestrutura de geração de números aleatórios que foi introduzida na NumPy 1.17.0 agora está acessível a partir do Cython.
-### Season of Docs acceptance
+### Aceitação no programa Season of Docs
-_May 11, 2020_ -- NumPy has been accepted as one of the mentor organizations for the Google Season of Docs program. We are excited about the opportunity to work with a technical writer to improve NumPy's documentation once again! For more details, please see [the official Season of Docs site](https://developers.google.com/season-of-docs/) and our [ideas page](https://github.com/numpy/numpy/wiki/Google-Season-of-Docs-2020-Project-Ideas).
+_11 de maio de 2020_ -- O NumPy foi aceito como uma das organizações mentoras do programa Google Season of Docs. Estamos animados com a oportunidade de trabalhar com um *technical writer* para melhorar a documentação do NumPy mais uma vez! Para mais detalhes, consulte [o site oficial do programa Season of Docs](https://developers.google.com/season-of-docs/) e nossa [página de ideias](https://github.com/numpy/numpy/wiki/Google-Season-of-Docs-2020-Project-Ideas).
-### NumPy 1.18.0 release
+### NumPy versão 1.18.0
-_Dec 22, 2019_ -- NumPy 1.18.0 is now available. After the major changes in 1.17.0, this is a consolidation release. It is the last minor release that will support Python 3.5. Highlights of the release includes the addition of basic infrastructure for linking with 64-bit BLAS and LAPACK libraries, and a new C-API for `numpy.random`.
+_22 de dezembro de 2019_ -- O NumPy 1.18.0 está disponível. Após as principais mudanças em 1.17.0, esta é uma versão de consolidação. Esta é a última versão menor que irá suportar Python 3.5. Destaques dessa versão incluem a adição de uma infraestrutura básica para permitir o link com as bibliotecas BLAS e LAPACK em 64 bits durante a compilação, e uma nova C-API para `numpy.random`.
-Please see the [release notes](https://github.com/numpy/numpy/releases/tag/v1.18.0) for more details.
+Por favor, veja as [notas de lançamento](https://github.com/numpy/numpy/releases/tag/v1.18.0) para mais detalhes.
-### NumPy receives a grant from the Chan Zuckerberg Initiative
+### O NumPy recebe financiamento da Chan Zuckerberg Initiative
-_Nov 15, 2019_ -- We are pleased to announce that NumPy and OpenBLAS, one of NumPy's key dependencies, have received a joint grant for $195,000 from the Chan Zuckerberg Initiative through their [Essential Open Source Software for Science program](https://chanzuckerberg.com/eoss/) that supports software maintenance, growth, development, and community engagement for open source tools critical to science.
+_15 de novembro de 2019_ -- Estamos felizes em anunciar que o NumPy e a OpenBLAS, uma das dependências-chave da NumPy, receberam um auxílio conjunto de $195,000 da Chan Zuckerberg Initiative através do seu programa [Essential Open Source Software for Science](https://chanzuckerberg.com/eoss/) que apoia a manutenção, crescimento, desenvolvimento e envolvimento com a comunidade de ferramentas de software open source fundamentais para a ciência.
-This grant will be used to ramp up the efforts in improving NumPy documentation, website redesign, and community development to better serve our large and rapidly growing user base, and ensure the long-term sustainability of the project. While the OpenBLAS team will focus on addressing sets of key technical issues, in particular thread-safety, AVX-512, and thread-local storage (TLS) issues, as well as algorithmic improvements in ReLAPACK (Recursive LAPACK) on which OpenBLAS depends.
+Este auxílio será usado para aumentar os esforços de melhoria da documentação do NumPy, atualização do design do site, e desenvolvimento comunitário para servir melhor a nossa grande e rápida base de usuários, e garantir a sustentabilidade do projeto a longo prazo. Enquanto a equipe OpenBLAS se concentrará em tratar de um conjunto de questões técnicas fundamentais, em particular relacionadas a *thread-safety*, AVX-512, e *thread-local storage* (TLS), bem como melhorias algorítmicas na ReLAPACK (Recursive LAPACK) da qual a OpenBLAS depende.
-More details on our proposed initiatives and deliverables can be found in the [full grant proposal](https://figshare.com/articles/Proposal_NumPy_OpenBLAS_for_Chan_Zuckerberg_Initiative_EOSS_2019_round_1/10302167). The work is scheduled to start on Dec 1st, 2019 and continue for the next 12 months.
+Mais detalhes sobre nossas propostas e resultados esperados podem ser encontrados na [proposta completa de concessão de auxílio](https://figshare.com/articles/Proposal_NumPy_OpenBLAS_for_Chan_Zuckerberg_Initiative_EOSS_2019_round_1/10302167). O trabalho está agendado para começar no dia 1 de dezembro de 2019 e continuar pelos próximos 12 meses.
## Lançamentos
-Here is a list of NumPy releases, with links to release notes. All bugfix releases (only the `z` changes in the `x.y.z` version number) have no new features; minor releases (the `y` increases) do.
-
-- NumPy 1.18.4 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.18.4)) -- _3 May 2020_.
-- NumPy 1.18.3 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.18.3)) -- _19 Apr 2020_.
-- NumPy 1.18.2 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.18.2)) -- _17 Mar 2020_.
-- NumPy 1.18.1 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.18.1)) -- _6 Jan 2020_.
-- NumPy 1.17.5 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.17.5)) -- _1 Jan 2020_.
-- NumPy 1.18.0 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.18.0)) -- _22 Dec 2019_.
-- NumPy 1.17.4 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.17.4)) -- _11 Nov 2019_.
-- NumPy 1.17.0 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.17.0)) -- _26 Jul 2019_.
-- NumPy 1.16.0 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.16.0)) -- _14 Jan 2019_.
-- NumPy 1.15.0 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.15.0)) -- _23 Jul 2018_.
-- NumPy 1.14.0 ([release notes](https://github.com/numpy/numpy/releases/tag/v1.14.0)) -- _7 Jan 2018_.
+Aqui está uma lista de versões do NumPy, com links para notas de lançamento. Todos os lançamentos de bugfix (apenas o `z` muda no formato `x.y.z` do número da versão) não tem novos recursos; versões menores (o `y` aumenta) contém novos recursos.
+
+- NumPy 1.18.4 ([notas de lançamento](https://github.com/numpy/numpy/releases/tag/v1.18.4)) -- _3 de maio de 2020_.
+- NumPy 1.18.3 ([notas de lançamento](https://github.com/numpy/numpy/releases/tag/v1.18.3)) -- _19 de abril de 2020_.
+- NumPy 1.18.2 ([notas de lançamento](https://github.com/numpy/numpy/releases/tag/v1.18.2)) -- _17 de março de 2020_.
+- NumPy 1.18.1 ([notas de lançamento](https://github.com/numpy/numpy/releases/tag/v1.18.1)) -- _6 de janeiro de 2020_.
+- NumPy 1.17.5 ([notas de lançamento](https://github.com/numpy/numpy/releases/tag/v1.17.5)) -- _1 de janeiro de 2020_.
+- NumPy 1.18.0 ([notas de lançamento](https://github.com/numpy/numpy/releases/tag/v1.18.0)) -- _22 de dezembro de 2019_.
+- NumPy 1.17.4 ([notas de lançamento](https://github.com/numpy/numpy/releases/tag/v1.17.4)) -- _11 de novembro de 2019_.
+- NumPy 1.17.0 ([notas de lançamento](https://github.com/numpy/numpy/releases/tag/v1.17.0)) -- _26 de julho de 2019_.
+- NumPy 1.16.0 ([notas de lançamento](https://github.com/numpy/numpy/releases/tag/v1.16.0)) -- _14 de janeiro de 2019_.
+- NumPy 1.15.0 ([notas de lançamento](https://github.com/numpy/numpy/releases/tag/v1.15.0)) -- _23 de julho de 2018_.
+- NumPy 1.14.0 ([notas de lançamento](https://github.com/numpy/numpy/releases/tag/v1.14.0)) -- _7 de janeiro de 2018_.
From fff0da7696b311249f579169bbfd71e4b34a1456 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Tue, 6 Apr 2021 00:26:33 +0200
Subject: [PATCH 248/909] New translations blackhole-image.md (Portuguese,
Brazilian)
---
content/pt/case-studies/blackhole-image.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/pt/case-studies/blackhole-image.md b/content/pt/case-studies/blackhole-image.md
index d07ddd9776..e43effd2ad 100644
--- a/content/pt/case-studies/blackhole-image.md
+++ b/content/pt/case-studies/blackhole-image.md
@@ -38,7 +38,7 @@ O [telescópio Event Horizon (EHT)](https://eventhorizontelescope.org), é um co
{{< figure src="/images/content_images/cs/dataprocessbh.png" class="csfigcaption" caption="**Etapas de Processamento de Dados do EHT**" alt="data pipeline" align="middle" attr="(Créditos do diagrama: The Astrophysical Journal, Event Horizon Telescope Collaboration)" attrlink="https://iopscience.iop.org/article/10.3847/2041-8213/ab0c57" >}}
-## NumPy’s Role
+## O papel do NumPy
E se houver um problema com os dados? Ou talvez um algoritmo seja muito dependente de uma hipótese em particular. A imagem será alterada drasticamente se um único parâmetro for alterado?
From d61b9ecb67ac6cb3e480ae2721970c59390d0d53 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Tue, 6 Apr 2021 19:07:11 +0200
Subject: [PATCH 249/909] New translations blackhole-image.md (Portuguese,
Brazilian)
---
content/pt/case-studies/blackhole-image.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/pt/case-studies/blackhole-image.md b/content/pt/case-studies/blackhole-image.md
index e43effd2ad..04a8e873d1 100644
--- a/content/pt/case-studies/blackhole-image.md
+++ b/content/pt/case-studies/blackhole-image.md
@@ -26,7 +26,7 @@ O [telescópio Event Horizon (EHT)](https://eventhorizontelescope.org), é um co
* **Escala computacional**
- O EHT representa um desafio imenso em processamento de dados, incluindo flutuações de fase atmosféricas rápidas, uma largura grande de banda nas gravações e telescópios que são muito diferentes e geograficamente dispersos.
+ O EHT representa um desafio imenso em processamento de dados, incluindo flutuações rápidas de fase atmosférica, uma largura grande de banda nas gravações e telescópios que são muito diferentes e geograficamente dispersos.
* **Muitas informações**
From ac043a0b220b339bb46f26b34204017baac18842 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Tue, 6 Apr 2021 20:12:08 +0200
Subject: [PATCH 250/909] New translations blackhole-image.md (Portuguese,
Brazilian)
---
content/pt/case-studies/blackhole-image.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/pt/case-studies/blackhole-image.md b/content/pt/case-studies/blackhole-image.md
index 04a8e873d1..0920410694 100644
--- a/content/pt/case-studies/blackhole-image.md
+++ b/content/pt/case-studies/blackhole-image.md
@@ -20,7 +20,7 @@ O [telescópio Event Horizon (EHT)](https://eventhorizontelescope.org), é um co
* **O Buraco Negro:** o EHT foi treinado em um buraco negro supermassivo a aproximadamente 55 milhões de anos-luz da Terra, localizado no centro do galáxia Messier 87 (M87) no aglomerado de Virgem. Sua massa é equivalente a 6,5 bilhões de vezes a do Sol. Ele vem sendo estudado [há mais de 100 anos](https://www.jpl.nasa.gov/news/news.php?feature=7385), mas um buraco negro nunca havia sido observado visualmente antes.
-* **Comparando observações com a teoria:** Da teoria geral da relatividade de Einstein, os cientistas esperavam encontrar uma região de sombra causada pela distorção e captura da luz causada pela influência gravitacional do buraco negro. Os cientistas poderiam usá-la para medir sua enorme massa.
+* **Comparando observações com a teoria:** Pela teoria geral da relatividade de Einstein, os cientistas esperavam encontrar uma região de sombra causada pela distorção e captura da luz causada pela influência gravitacional do buraco negro. Os cientistas poderiam usá-la para medir a enorme massa do mesmo.
### Desafios
From dfe26b90120459f1a55ab1585358e34c5c7a3f34 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Tue, 6 Apr 2021 21:39:47 +0200
Subject: [PATCH 251/909] New translations blackhole-image.md (Portuguese,
Brazilian)
---
content/pt/case-studies/blackhole-image.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/content/pt/case-studies/blackhole-image.md b/content/pt/case-studies/blackhole-image.md
index 0920410694..3036337e0b 100644
--- a/content/pt/case-studies/blackhole-image.md
+++ b/content/pt/case-studies/blackhole-image.md
@@ -26,7 +26,7 @@ O [telescópio Event Horizon (EHT)](https://eventhorizontelescope.org), é um co
* **Escala computacional**
- O EHT representa um desafio imenso em processamento de dados, incluindo flutuações rápidas de fase atmosférica, uma largura grande de banda nas gravações e telescópios que são muito diferentes e geograficamente dispersos.
+ O EHT representa um desafio imenso em processamento de dados, incluindo rápidas flutuações de fase atmosférica, uma largura grande de banda nas gravações e telescópios que são muito diferentes e geograficamente dispersos.
* **Muitas informações**
@@ -48,11 +48,11 @@ O trabalho desse grupo ilustra o papel do ecossistema científico do Python no a
{{< figure src="/images/content_images/cs/bh_numpy_role.png" class="fig-center" alt="role of numpy" caption="**O papel do NumPy na criação da primeira imagem de um Buraco Negro**" >}}
-Por exemplo, o pacote Python [`eht-imaging`][ehtim] fornece ferramentas para simular e realizar reconstrução de imagem nos dados do VLBI. O NumPy está no coração do processamento de dados vetorial usado neste pacote, como ilustrado pelo gráfico parcial de dependências de software abaixo.
+Por exemplo, o pacote Python [`eht-imaging`][ehtim] fornece ferramentas para simular e realizar reconstrução de imagem nos dados do VLBI. O NumPy está no coração do processamento de dados vetoriais usado neste pacote, como ilustrado pelo gráfico parcial de dependências de software abaixo.
{{< figure src="/images/content_images/cs/ehtim_numpy.png" class="fig-center" alt="ehtim dependency map highlighting numpy" caption="**Diagrama de dependência de software do pacote ehtim evidenciando o NumPy**" >}}
-Além do NumPy, muitos outros pacotes como [SciPy](https://www.scipy.org) e [Pandas](https://pandas.io) foram usados na *pipeline* de processamento de dados para criar a imagem do buraco negro. Os formatos de arquivos astronômicos padrão e transformações de tempo/coordenadas foram tratados pelo [Astropy][astropy] enquanto a[Matplotlib][mpl] foi usada na visualização de dados em todas as etapas de análise, incluindo a geração da imagem final do buraco negro.
+Além do NumPy, muitos outros pacotes como [SciPy](https://www.scipy.org) e [Pandas](https://pandas.io) foram usados na *pipeline* de processamento de dados para criar a imagem do buraco negro. Os arquivos astronômicos de formato padrão e transformações de tempo/coordenadas foram tratados pelo [Astropy][astropy] enquanto a[Matplotlib][mpl] foi usada na visualização de dados em todas as etapas de análise, incluindo a geração da imagem final do buraco negro.
## Resumo
From 56ae040ec57ea3671890f54e97a36ad3459f0062 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Tue, 6 Apr 2021 22:36:41 +0200
Subject: [PATCH 252/909] New translations blackhole-image.md (Portuguese,
Brazilian)
---
content/pt/case-studies/blackhole-image.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/content/pt/case-studies/blackhole-image.md b/content/pt/case-studies/blackhole-image.md
index 3036337e0b..d84528f550 100644
--- a/content/pt/case-studies/blackhole-image.md
+++ b/content/pt/case-studies/blackhole-image.md
@@ -52,11 +52,11 @@ Por exemplo, o pacote Python [`eht-imaging`][ehtim] fornece ferramentas para sim
{{< figure src="/images/content_images/cs/ehtim_numpy.png" class="fig-center" alt="ehtim dependency map highlighting numpy" caption="**Diagrama de dependência de software do pacote ehtim evidenciando o NumPy**" >}}
-Além do NumPy, muitos outros pacotes como [SciPy](https://www.scipy.org) e [Pandas](https://pandas.io) foram usados na *pipeline* de processamento de dados para criar a imagem do buraco negro. Os arquivos astronômicos de formato padrão e transformações de tempo/coordenadas foram tratados pelo [Astropy][astropy] enquanto a[Matplotlib][mpl] foi usada na visualização de dados em todas as etapas de análise, incluindo a geração da imagem final do buraco negro.
+Além do NumPy, muitos outros pacotes como [SciPy](https://www.scipy.org) e [Pandas](https://pandas.io) foram usados na *pipeline* de processamento de dados para criar a imagem do buraco negro. Os arquivos astronômicos de formato padrão e transformações de tempo/coordenadas foram tratados pelo [Astropy][astropy] enquanto a [Matplotlib][mpl] foi usada na visualização de dados em todas as etapas de análise, incluindo a geração da imagem final do buraco negro.
## Resumo
-A estrutura de dados n-dimensional que é a funcionalidade central do NumPy permitiu aos pesquisadores manipular grandes conjuntos de dados, fornecendo a base para a primeira imagem de um buraco negro. Esse momento marcante na ciência fornece evidências visuais impressionantes para a teoria de Einstein. Esta conquista abrange não apenas avanços tecnológicos, mas colaboração científica em escala internacional entre mais de 200 cientistas e alguns dos melhores observatórios de rádio do mundo. Eles usaram algoritmos e técnicas de processamento de dados inovadores que aperfeiçoaram os modelos astronômicos existentes para ajudar a descobrir alguns dos mistérios do universo.
+A estrutura de dados n-dimensional que é a funcionalidade central do NumPy permitiu aos pesquisadores manipular grandes conjuntos de dados, fornecendo a base para a primeira imagem de um buraco negro. Esse momento marcante na ciência fornece evidências visuais impressionantes para a teoria de Einstein. Esta conquista abrange não apenas avanços tecnológicos, mas colaboração científica em escala internacional entre mais de 200 cientistas e alguns dos melhores observatórios de rádio do mundo. Eles usaram algoritmos e técnicas de processamento de dados inovadores, que aperfeiçoaram os modelos astronômicos existentes, para ajudar a descobrir um dos mistérios do universo.
{{< figure src="/images/content_images/cs/numpy_bh_benefits.png" class="fig-center" alt="numpy benefits" caption="**Funcionalidades-chave do NumPy utilizadas**" >}}
From 097a30bfeebce4a3df3e458d9abc331ff6b37e91 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Tue, 6 Apr 2021 22:36:42 +0200
Subject: [PATCH 253/909] New translations cricket-analytics.md (Portuguese,
Brazilian)
---
content/pt/case-studies/cricket-analytics.md | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/content/pt/case-studies/cricket-analytics.md b/content/pt/case-studies/cricket-analytics.md
index 2a6ecda3bd..c2fbcac9c8 100644
--- a/content/pt/case-studies/cricket-analytics.md
+++ b/content/pt/case-studies/cricket-analytics.md
@@ -14,7 +14,7 @@ sidebar: false
Dizer que os indianos adoram o críquete seria subestimar este sentimento. O jogo é jogado praticamente em todas as localidades da Índia, rurais ou urbanas, e é popular com os jovens e os anciões, conectando bilhões de pessoas na Índia como nenhum outro esporte. O cricket também recebe muita atenção da mídia. Há uma quantidade significativa de [dinheiro](https://www.statista.com/topics/4543/indian-premier-league-ipl/) e fama em jogo. Ao longo dos últimos anos, a tecnologia foi literalmente uma revolução. As audiências tem uma ampla possibilidade de escolha, com mídias de streaming, torneios, acesso barato a jogos de críquete ao vivo em dispositivos móveis, e mais.
-A Primeira Liga Indiana (*Indian Premier League* - IPL) é uma liga profissional de críquete [Twenty20](https://pt.wikipedia.org/wiki/Twenty20), fundada em 2008. É um dos eventos de críquete mais assistidos no mundo avaliado em [$6,7 bilhões de dólares](https://en.wikipedia.org/wiki/Indian_Premier_League) em 2019.
+A Primeira Liga Indiana (*Indian Premier League* - IPL) é uma liga profissional de críquete [Twenty20](https://pt.wikipedia.org/wiki/Twenty20), fundada em 2008. É um dos eventos de críquete mais assistidos no mundo, avaliado em [$6,7 bilhões de dólares](https://en.wikipedia.org/wiki/Indian_Premier_League) em 2019.
Críquete é um jogo dominado pelos números - as corridas executadas por um batsman, os wickets perdidos por um boleador, as partidas ganhas por uma equipe de críquete, o número de vezes que um batsman responde de certa maneira a um tipo de arremesso do boleador, etc. A capacidade de investigar números de críquete para melhorar o desempenho e estudar as oportunidades de negócio, mercado e economia de críquete através de poderosas ferramentas de análise, alimentadas por softwares numéricos de computação, como o NumPy, é um grande negócio. As análises de críquete fornecem informações interessantes sobre o jogo e informações preditivas sobre os resultados do jogo.
@@ -29,7 +29,7 @@ Hoje, existem conjuntos ricos e quase infinitos de estatísticas e informações
### Objetivos Principais da Análise de Dados
-* A análise de dados esportivos é usada não somente em críquete mas em muitos [outros esportes](https://adtmag.com/blogs/dev-watch/2017/07/sports-analytics.aspx) para melhorar o desempenho geral da equipe e maximizar as chances de vitória.
+* A análise de dados esportivos é usada não somente em críquete, mas em muitos [outros esportes](https://adtmag.com/blogs/dev-watch/2017/07/sports-analytics.aspx) para melhorar o desempenho geral da equipe e maximizar as chances de vitória.
* A análise de dados em tempo real pode ajudar a obtenção de informações mesmo durante o jogo para orientar mudanças nas táticas da equipe e dos negócios associados para benefícios e crescimento econômicos.
* Além da análise histórica, os modelos preditivos explorados para determinar os possíveis resultados das partidas requerem um conhecimento significativo sobre processamento numérico e ciência de dados, ferramentas de visualização e a possibilidade de incluir observações mais recentes na análise.
@@ -39,7 +39,7 @@ Hoje, existem conjuntos ricos e quase infinitos de estatísticas e informações
* **Limpeza e pré-processamento de dados**
- A IPL expandiu o cricket para além do formato de jogo clássico para uma escala muito maior. O número de partidas jogadas a cada temporada em vários formatos tem aumentado, assim como os dados, os algoritmos, tecnologias de análise de dados mais recentes e modelos de simulação. A análise de dados de críquete requer mapeamento de campo, rastreamento do jogador, rastreamento de bola e análise de tiros do jogador, análise de lances do jogador e vários outros aspectos envolvidos em como a bola é lançada, seu ângulo, giro, velocidade e trajetória. Todos esses fatores em conjunto aumentaram a complexidade da limpeza e pré-processamento de dados.
+ A IPL expandiu o formato de jogo clássico de cricket para uma escala muito maior. O número de partidas jogadas a cada temporada em vários formatos tem aumentado, assim como os dados, os algoritmos, as tecnologias de análise de dados mais recentes e modelos de simulação. A análise de dados de críquete requer mapeamento de campo, rastreamento do jogador, rastreamento de bola e análise de tiros do jogador, análise de lances do jogador e vários outros aspectos envolvidos em como a bola é lançada, seu ângulo, giro, velocidade e trajetória. Todos esses fatores em conjunto aumentaram a complexidade da limpeza e pré-processamento de dados.
* **Modelagem Dinâmica**
@@ -51,14 +51,14 @@ Hoje, existem conjuntos ricos e quase infinitos de estatísticas e informações
## Papel da NumPy na Análise de Críquete
-A análise de dados esportivos é um campo próspero. Muitos pesquisadores e empresas [usam NumPy](https://adtmag.com/blogs/dev-watch/2017/07/sports-analytics.aspx) e outros pacotes PyData como Scikit-learn, SciPy, Matplotlib, e Jupyter, além de usar as últimas técnicas de aprendizagem de máquina e IA. A NumPy foi usada para vários tipos de análise esportiva relacionada a críquete, como:
+A análise de dados esportivos é um campo próspero. Muitos pesquisadores e empresas [usam NumPy](https://adtmag.com/blogs/dev-watch/2017/07/sports-analytics.aspx) e outros pacotes PyData como Scikit-learn, SciPy, Matplotlib, e Jupyter, além de usar as últimas técnicas de aprendizagem de máquina e IA. O NumPy foi usado para vários tipos de análise esportiva relacionada a críquete, como:
-* **Análise Estatística:** Os recursos numéricos da NumPy ajudam a estimar o significado estatístico de dados observados ou de eventos ocorridos em partidas no contexto de vários jogadores e táticas de jogo, bem como estimar o resultado do jogo em comparação com um modelo generativo ou estático. [Análise Causal](https://amplitude.com/blog/2017/01/19/causation-correlation) e [abordagens em *big data*](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4996805/) são usados para análise tática.
+* **Análise Estatística:** Os recursos numéricos do NumPy ajudam a estimar o significado estatístico de dados observados ou de eventos ocorridos em partidas no contexto de vários jogadores e táticas de jogo, bem como estimar o resultado do jogo em comparação com um modelo generativo ou estático. [Análise Causal](https://amplitude.com/blog/2017/01/19/causation-correlation) e [abordagens em *big data*](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4996805/) são usados para análise tática.
* **Visualização de dados:** Gráficos e [visualizações](https://towardsdatascience.com/advanced-sports-visualization-with-pandas-matplotlib-and-seaborn-9c16df80a81b) fornecem informações úteis sobre as relações entre vários conjuntos de dados.
## Resumo
-A análise de dados esportivos é revolucionária quando se trata de como os jogos profissionais são jogados, especialmente se consideramos como acontece a tomada de decisões estratégicas, que até pouco tempo atrás era principalmente feito com base na "intuição" ou adesão a tradições passadas. A NumPy forma uma fundação sólida para um grande conjunto de pacotes Python que fornecem funções de alto nível relacionadas à análise de dados, aprendizagem de máquina e algoritmos de IA. Estes pacotes são amplamente implantados para se obter informações em tempo real que ajudam na tomada de decisão para resultados decisivos, tanto em campo como para se derivar inferências e orientar negócios em torno do jogo de críquete. Encontrar os parâmetros ocultos, padrões, e atributos que levam ao resultado de uma partida de críquete ajuda os envolvidos a tomar nota das percepções do jogo que estariam de outra forma ocultas nos números e estatísticas.
+A análise de dados esportivos é revolucionária quando se trata de como os jogos profissionais são jogados, especialmente se consideramos como acontece a tomada de decisões estratégicas, que até pouco tempo era principalmente feita com base na "intuição" ou adesão a tradições passadas. O NumPy forma uma fundação sólida para um grande conjunto de pacotes Python que fornecem funções de alto nível relacionadas à análise de dados, aprendizagem de máquina e algoritmos de IA. Estes pacotes são amplamente implantados para se obter informações em tempo real que ajudam na tomada de decisão para resultados decisivos, tanto em campo como para se derivar inferências e orientar negócios em torno do jogo de críquete. Encontrar os parâmetros ocultos, padrões, e atributos que levam ao resultado de uma partida de críquete ajuda os envolvidos a tomar nota das percepções do jogo que estariam de outra forma ocultas nos números e estatísticas.
{{< figure src="/images/content_images/cs/numpy_ca_benefits.png" class="fig-center" alt="Diagrama mostrando os benefícios de usar a NumPy para análise de críquete" caption="**Recursos principais da NumPy utilizados**" >}}
From 8682ece58d5530e49f001e98a2806f3b90e7957e Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Tue, 6 Apr 2021 22:36:44 +0200
Subject: [PATCH 254/909] New translations deeplabcut-dnn.md (Portuguese,
Brazilian)
---
content/pt/case-studies/deeplabcut-dnn.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/content/pt/case-studies/deeplabcut-dnn.md b/content/pt/case-studies/deeplabcut-dnn.md
index 3d54a281e0..1dd02b9f92 100644
--- a/content/pt/case-studies/deeplabcut-dnn.md
+++ b/content/pt/case-studies/deeplabcut-dnn.md
@@ -14,15 +14,15 @@ sidebar: false
[DeepLabCut](https://github.com/DeepLabCut/DeepLabCut) é uma toolbox de código aberto que permite que pesquisadores de centenas de instituições em todo o mundo rastreiem o comportamento de animais de laboratório, com muito poucos dados de treinamento, mas com precisão no nível humano. Com a tecnologia DeepLabCut, cientistas podem aprofundar a compreensão científica do controle motor e do comportamento em diversas espécies animais e escalas temporais.
-Várias áreas de pesquisa, incluindo a neurociência, a medicina e a biomecânica, utilizam dados de rastreamento da movimentação de animais. A DeepLabCut ajuda a compreender o que os seres humanos e outros animais estão fazendo, analisando ações que foram registradas em vídeo. Ao usar automação para tarefas penosas de monitoramento e marcação, junto com análise de dados baseada em redes neurais profundas, a DeepLabCut garante que estudos científicos envolvendo a observação de animais como primatas, camundongos, peixes, moscas etc. sejam mais rápidos e mais precisos.
+Várias áreas de pesquisa, incluindo a neurociência, a medicina e a biomecânica, utilizam dados de rastreamento da movimentação de animais. A DeepLabCut ajuda a compreender o que os seres humanos e outros animais estão fazendo, analisando ações que foram registradas em vídeo. Ao usar automação para tarefas trabalhosas de monitoramento e marcação, junto com análise de dados baseada em redes neurais profundas, a DeepLabCut garante que estudos científicos envolvendo a observação de animais como primatas, camundongos, peixes, moscas etc. sejam mais rápidos e precisos.
{{< figure src="/images/content_images/cs/race-horse.gif" class="fig-center" caption="**Pontos coloridos rastreiam as posições das partes do corpo de um cavalo de corrida**" alt="horserideranim" attr="*(Fonte: Mackenzie Mathis)*">}}
-O rastreamento não invasivo dos animais pela DeepLabCut através da extração de poses é crucial para pesquisas científicas em domínios como a biomecânica, genética, etologia e neurociência. Medir as poses dos animais de maneira não invasiva através de vídeo - sem marcadores - com fundos dinamicamente variáveis é computacionalmente desafiador, tanto tecnicamente quanto em termos de recursos necessários e dados de treinamento exigidos.
+O rastreamento não invasivo dos animais pela DeepLabCut através da extração de poses é crucial para pesquisas científicas em domínios como a biomecânica, genética, etologia e neurociência. Medir as poses dos animais de maneira não invasiva através de vídeo - sem marcadores - com fundos dinâmicos é computacionalmente desafiador, tanto tecnicamente quanto em termos de recursos e dados de treinamento necessários.
-A DeepLabCut permite que pesquisadores façam estimativas de poses para os sujeitos, permitindo que se possa quantificar de maneira eficiente seus comportamentos através de um conjunto de ferramentas de software baseado em Python. Com a DeepLabCut, pesquisadores podem identificar quadros (*frames*) distintos em vídeos, rotular digitalmente partes específicas do corpo em alguns quadros com uma GUI específica, e a partir disso a arquitetura de estimação de poses baseada em deep learning na DeepLabCut aprende a selecionar essas mesmas características no resto do vídeo e em outros vídeos similares. A ferramenta funciona para várias espécies de animais, desde animais comuns em laboratórios como moscas e camundongos até os mais incomuns como [guepardos][cheetah-movement].
+A DeepLabCut permite que pesquisadores façam estimativas de poses para os sujeitos, permitindo que se possa quantificar de maneira eficiente seus comportamentos através de um conjunto de ferramentas de software baseado em Python. Com a DeepLabCut, pesquisadores podem identificar quadros (*frames*) distintos em vídeos e rotular digitalmente partes específicas do corpo em alguns quadros com uma GUI especializada. A partir disso, a arquitetura de estimação de poses baseada em deep learning da DeepLabCut aprende a selecionar essas mesmas características no resto do vídeo e em outros vídeos similares. A ferramenta funciona para várias espécies de animais, desde animais comuns em laboratórios, como moscas e camundongos, até os mais incomuns, como [guepardos][cheetah-movement].
-A DeepLabCut usa um princípio chamado [aprendizado por transferência (*transfer learning*)](https://arxiv.org/pdf/1909.11229), o que reduz enormemente a quantidade de dados de treinamento necessários e acelera a convergência do período de treinamento. Dependendo das suas necessidades, usuários podem escolher diferentes arquiteturas de rede que forneçam inferência mais rápida (por exemplo, MobileNetV2), que também podem ser combinadas com feedback experimental em tempo real. A DeepLabCut usou originalmente os detectores de features de uma arquitetura de estimativa de poses humanas de alto desempenho, chamada [DeeperCut](https://arxiv.org/abs/1605.03170), que inspirou seu nome. O pacote agora foi significativamente alterado para incluir mais arquiteturas, métodos de ampliação e uma experiência de usuário completa no front-end. Além de possibilitar experiências biológicas em grande escala, DeepLabCut fornece capacidades ativas de aprendizado para que os usuários possam aumentar o conjunto de treinamento ao longo do tempo para incluir casos particulares e tornar seu algoritmo de estimativa de poses robusto no seu contexto específico.
+A DeepLabCut usa um princípio chamado [aprendizado por transferência (*transfer learning*)](https://arxiv.org/pdf/1909.11229), o que reduz enormemente a quantidade de dados de treinamento necessários e acelera a convergência do período de treinamento. Dependendo das suas necessidades, usuários podem escolher diferentes arquiteturas de rede que forneçam inferência mais rápida (por exemplo, MobileNetV2), e que também podem ser combinadas com feedback experimental em tempo real. A DeepLabCut usou originalmente os detectores de features de uma arquitetura de alto desempenho para estimativa de poses humanas, chamada [DeeperCut](https://arxiv.org/abs/1605.03170), que inspirou seu nome. O pacote foi significativamente alterado para incluir mais arquiteturas, métodos de ampliação e uma experiência de usuário completa no front-end. Além de possibilitar experimentos biológicos em grande escala, DeepLabCut fornece capacidades ativas de aprendizado para que os usuários possam aumentar o conjunto de treinamento ao longo do tempo, para incluir casos particulares e tornar seu algoritmo de estimativa de poses robusto no seu contexto específico.
Recentemente, foi introduzido o [modelo DeepLabCut zoo](http://www.mousemotorlab.org/dlc-modelzoo), que proporciona modelos pré-treinados para várias espécies e condições experimentais, desde a análise facial em primatas até à posição de cães. Isso pode ser executado na nuvem, por exemplo, sem qualquer rotulagem de novos dados ou treinamento em rede neural, e não é necessária nenhuma experiência em programação.
From 3dfb46ef3f4b3ce52148d133bbae487bacd426ee Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Tue, 6 Apr 2021 22:36:45 +0200
Subject: [PATCH 255/909] New translations gw-discov.md (Portuguese, Brazilian)
---
content/pt/case-studies/gw-discov.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/content/pt/case-studies/gw-discov.md b/content/pt/case-studies/gw-discov.md
index d189210057..6de7efed50 100644
--- a/content/pt/case-studies/gw-discov.md
+++ b/content/pt/case-studies/gw-discov.md
@@ -14,7 +14,7 @@ sidebar: false
Ondas gravitacionais são ondulações no tecido espaço-tempo, gerado por eventos cataclísmicos no universo, como colisão e fusão de dois buracos negros ou a coalescência de estrelas binárias ou supernovas. A observação de ondas gravitacionais pode ajudar não só no estudo da gravidade, mas também no entendimento de alguns dos fenômenos obscuros existentes no universo distante e seu impacto.
-O [Observatório Interferômetro Laser de Ondas Gravitacionais (LIGO)](https://www.ligo.caltech.edu) foi projetado para abrir o campo da astrofísica das ondas gravitacionais através da detecção direta de ondas gravitacionais previstas pela Teoria Geral da Relatividade de Einstein. O observatório consiste de dois interferômetros amplamente separados dentro dos Estados Unidos - um em Hanford, Washington e o outro em Livingston, Louisiana — operando em uníssono para detectar ondas gravitacionais. Cada um deles tem detectores em escala quilométrica de ondas gravitacionais que usam interferometria laser. A Colaboração Científica LIGO (LSC), é um grupo de mais de 1000 cientistas de universidades dos Estados Unidos e em 14 outros países apoiados por mais de 90 universidades e institutos de pesquisa; aproximadamente 250 estudantes contribuem ativamente com a colaboração. A nova descoberta do LIGO é a primeira observação de ondas gravitacionais em si, feita medindo os pequenos distúrbios que as ondas fazem ao espaço-tempo enquanto atravessam a terra. A descoberta abriu novas fronteiras astrofísicas que exploram o lado "curvado" do universo - objetos e fenômenos que são feitos a partir da curvatura do espaço-tempo.
+O [Observatório Interferômetro Laser de Ondas Gravitacionais (LIGO)](https://www.ligo.caltech.edu) foi projetado para abrir o campo da astrofísica das ondas gravitacionais através da detecção direta de ondas gravitacionais previstas pela Teoria Geral da Relatividade de Einstein. O observatório consiste de dois interferômetros amplamente separados dentro dos Estados Unidos - um em Hanford, Washington e o outro em Livingston, Louisiana — operando em uníssono para detectar ondas gravitacionais. Cada um deles tem detectores em escala quilométrica de ondas gravitacionais que usam interferometria laser. A Colaboração Científica LIGO (LSC), é um grupo de mais de 1000 cientistas de universidades dos Estados Unidos e em 14 outros países apoiados por mais de 90 universidades e institutos de pesquisa; aproximadamente 250 estudantes contribuem ativamente com a colaboração. A nova descoberta do LIGO é a primeira observação de ondas gravitacionais em si, feita medindo os pequenos distúrbios que as ondas fazem ao espaço-tempo enquanto atravessam a Terra. A descoberta abriu novas fronteiras astrofísicas que exploram o lado "curvado" do universo - objetos e fenômenos que são feitos a partir da curvatura do espaço-tempo.
### Objetivos
@@ -64,6 +64,6 @@ NumPy, o pacote padrão de análise numérica para Python, foi parte do software
## Resumo
-A detecção de ondas gravitacionais permitiu que pesquisadores descobrissem fenômenos totalmente inesperados ao mesmo tempo em que proporcionaram novas idéias sobre muitos dos fenômenos mais profundos conhecidos na astrofísica. O processamento e a visualização de dados é um passo crucial que ajuda cientistas a obter informações coletadas de observações científicas e a entender os resultados. Os cálculos são complexos e não podem ser compreendidos por humanos a não ser que sejam visualizados usando simulações de computador que são alimentadas com dados e análises reais observados. A NumPy, junto com outros pacotes Python, como matplotlib, pandas, e scikit-learn [permitem que pesquisadores](https://www.gw-openscience.org/events/GW150914/) respondam perguntas complexas e descubram novos horizontes em nossa compreensão do universo.
+A detecção de ondas gravitacionais permitiu que pesquisadores descobrissem fenômenos totalmente inesperados ao mesmo tempo em que proporcionaram novas idéias sobre muitos dos fenômenos mais profundos conhecidos na astrofísica. O processamento e a visualização de dados é um passo crucial que ajuda cientistas a obter informações coletadas de observações científicas e a entender os resultados. Os cálculos são complexos e não podem ser compreendidos por humanos a não ser que sejam visualizados usando simulações de computador que são alimentadas com dados e análises reais observados. A NumPy, junto com outras bibliotecas Python, como matplotlib, pandas, e scikit-learn [permitem que pesquisadores](https://www.gw-openscience.org/events/GW150914/) respondam perguntas complexas e descubram novos horizontes em nossa compreensão do universo.
{{< figure src="/images/content_images/cs/numpy_gw_benefits.png" class="fig-center" alt="numpy benefits" caption="**Recursos chave da NumPy utilizados**" >}}
From 25075d8df5a2001e6777af3475a39b94e84cdcf8 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Fri, 9 Apr 2021 03:26:13 +0200
Subject: [PATCH 256/909] New translations code-of-conduct.md (Arabic)
---
content/ar/code-of-conduct.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/content/ar/code-of-conduct.md b/content/ar/code-of-conduct.md
index c25bd00d54..c9ad39a707 100644
--- a/content/ar/code-of-conduct.md
+++ b/content/ar/code-of-conduct.md
@@ -57,13 +57,13 @@ aliases:
* ميليسا فيبر ميندونسا (Melissa Weber Mendonça)
* أنيروده سوبرامانيان (Anirudh Subramanian)
-لو كان بلاغك متورط به أحد أعضاء اللجنة أو إذا كانوا يشعرون بأن لديهم تضارب في المصالح يحدهم عن التعامل معه. Alternatively, if for any reason you feel uncomfortable making a report to the Committee, then you can also contact senior NumFOCUS staff at [conduct@numfocus.org](https://numfocus.org/code-of-conduct#persons-responsible).
+لو كان بلاغك متورط به أحد أعضاء اللجنة أو إذا كانوا يشعرون بأن لديهم تضارب في المصالح يحدهم عن التعامل معه. أو إذا شعرت بعدم الارتياح لأي سبب من الأسباب لإبلاغ اللجنة ، فبمكانك الاتصال عوضا عن ذلك بفريق NumFOCUS الأعلى على [conduct@numfocus.org](https://numfocus.org/code-of-conduct#persons-responsible).
-### Incident reporting resolution & Code of Conduct enforcement
+### تسوية بلاغات الحوادث & نفاذ القواعد السلوكية
-_This section summarizes the most important points, more details can be found in_ [NumPy Code of Conduct - How to follow up on a report](/report-handling-manual).
+_هذا القسم يلخص أهم النقاط، يمكنك العثور على مزيد من التفاصيل في_ [ قواعد سلوكيات نمباي - كيفية متابعة التقرير](/report-handling-manual).
-We will investigate and respond to all complaints. The NumPy Code of Conduct Committee and the NumPy Steering Committee (if involved) will protect the identity of the reporter, and treat the content of complaints as confidential (unless the reporter agrees otherwise).
+سوف نقوم بالتحقيق في جميع الشكاوى والرد عليها. وستقوم لجنة القواعد السلوكية واللجنة التوجيهية لنمباي (إذا اشتركت) بحماية هوية المبلِّغ وسوف يتم التعامل مع مضمون الشكاوى على أنها سرية (ما لم يوافق المبلغ على غير ذلك).
In case of severe and obvious breaches, e.g. personal threat or violent, sexist or racist language, we will immediately disconnect the originator from NumPy communication channels; please see the manual for details.
From a27db9c65aad3c320afefc008b716463f16d808a Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Fri, 9 Apr 2021 04:27:49 +0200
Subject: [PATCH 257/909] New translations 404.md (Arabic)
---
content/ar/404.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/content/ar/404.md b/content/ar/404.md
index da192c53c0..a12adc165c 100644
--- a/content/ar/404.md
+++ b/content/ar/404.md
@@ -3,6 +3,6 @@ title: 404
sidebar: false
---
-Oops! You've reached a dead end.
+عفواً! لقد وصلت إلى طريق مسدود.
-If you think something should be here, you can [open an issue](https://github.com/numpy/numpy.org/issues) on GitHub.
+إذا كنت تعتقد أنه يجب أن يكون شيء ما، فيمكنك [فتح مشكلة](https://github.com/numpy/numpy.org/issues) على GitHub.
From f8a835e9dc8f9abef755ee22da0bb5de1a101536 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Fri, 9 Apr 2021 04:27:50 +0200
Subject: [PATCH 258/909] New translations about.md (Arabic)
---
content/ar/about.md | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/content/ar/about.md b/content/ar/about.md
index 1779f7531f..0171632a52 100644
--- a/content/ar/about.md
+++ b/content/ar/about.md
@@ -1,18 +1,18 @@
---
-title: About Us
+title: من نحن
sidebar: false
---
-_Some information about the NumPy project and community_
+_بعض المعلومات حول مشروع ومجتمع نمباي_
-NumPy is an open source project aiming to enable numerical computing with Python. It was created in 2005, building on the early work of the Numeric and Numarray libraries. NumPy will always be 100% open source software, free for all to use and released under the liberal terms of the [modified BSD license](https://github.com/numpy/numpy/blob/master/LICENSE.txt).
+نمباي هو مشروع مفتوح المصدر يهدف إلي إتاحة الحوسبة الرقمية باستخدام لغة برمجة بايثون. وقد أنشئت في عام 2005، استنادا علي العمل المبكر للمكتبتان Numeric و Numarray. ستظل نمباي دائماُ مائة في المائة برمجية مفتوحة المصدر، مجانية للجميع وتصدر بموجب الشروط الليبرالية [لرخصة BSD المعدلة](https://github.com/numpy/numpy/blob/master/LICENSE.txt).
-NumPy is developed in the open on GitHub, through the consensus of the NumPy and wider scientific Python community. For more information on our governance approach, please see our [Governance Document](https://www.numpy.org/devdocs/dev/governance/index.html).
+وقد تم تطوير نمباي في العلن على GitHub ومن خلال توافق آراء مجتمع نمباي ونطاق أوسع لمجتمع بايثون العلمي. لمزيد من المعلومات حول نهج الإدارة، يرجى الاطلاع على [الوثيقة الإدارية](https://www.numpy.org/devdocs/dev/governance/index.html) الخاصة بنا.
-## Steering Council
+## المجلس التوجيهي
-The role of the NumPy Steering Council is to ensure, through working with and serving the broader NumPy community, the long-term well-being of the project, both technically and as a community. The NumPy Steering Council currently consists of the following members (in alphabetical order):
+The role of the NumPy Steering Council is to ensure, through working with and serving the broader NumPy community, the long-term well-being of the project, both technically and as a community. ويتألف المجلس التوجيهي المعني لنمباي حاليا علي الأعضاء التالية (بالترتيب الأبجدي):
- Sebastian Berg
- Jaime Fernández del Río
From c48288bfcf59b54f8422376802c422010db67f63 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Fri, 9 Apr 2021 04:27:51 +0200
Subject: [PATCH 259/909] New translations code-of-conduct.md (Arabic)
---
content/ar/code-of-conduct.md | 20 ++++++++++----------
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/content/ar/code-of-conduct.md b/content/ar/code-of-conduct.md
index c9ad39a707..4811c7c959 100644
--- a/content/ar/code-of-conduct.md
+++ b/content/ar/code-of-conduct.md
@@ -65,19 +65,19 @@ _هذا القسم يلخص أهم النقاط، يمكنك العثور على
سوف نقوم بالتحقيق في جميع الشكاوى والرد عليها. وستقوم لجنة القواعد السلوكية واللجنة التوجيهية لنمباي (إذا اشتركت) بحماية هوية المبلِّغ وسوف يتم التعامل مع مضمون الشكاوى على أنها سرية (ما لم يوافق المبلغ على غير ذلك).
-In case of severe and obvious breaches, e.g. personal threat or violent, sexist or racist language, we will immediately disconnect the originator from NumPy communication channels; please see the manual for details.
+في حالة حدوث إخلالات خطيرة وواضحة، مثل التهديد أو العنف الشخصي أو التحيز جنسياً أو عنصرياً، سنقوم على الفور بفصل المقدم عن قنوات الاتصال الخاصة بنمباي؛ يرجى الاطلاع على الدليل للحصول على التفاصيل.
-In cases not involving clear severe and obvious breaches of this Code of Conduct the process for acting on any received Code of Conduct violation report will be:
+وفي الحالات التي لا تنطوي على انتهاكات خطيرة وواضحة لقواعد السلوك هذه، تكون عملية التصرف بشأن أي تقرير يرد عن انتهاك القواعد السلوكية علي ما يلي:
-1. acknowledge report is received,
-2. reasonable discussion/feedback,
-3. mediation (if feedback didn’t help, and only if both reporter and reportee agree to this),
-4. enforcement via transparent decision (see [Resolutions](/report-handling-manual#resolutions)) by the Code of Conduct Committee.
+1. الإقرار بتلقي التقرير،
+2. مناقشات/ملاحظات معقولة،
+3. الوساطة (إذا لم تساعد ردود الفعل، وفقط إذا وافق كل من المبلّغ والمبلّغ على ذلك)،
+4. • الإنفاذ من خلال قرار شفاف (انظر [القرارات](/report-handling-manual#resolutions))الصادر عن لجنة قواعد السلوك.
-The Committee will respond to any report as soon as possible, and at most within 72 hours.
+واللجنة سترد على أي تقرير في أقرب وقت ممكن، وفي الأغلب 72 ساعة على الأكثر.
-### Endnotes
+### تعليق ختامي
-We are thankful to the groups behind the following documents, from which we drew content and inspiration:
+نحن ممتنون للمجموعات التي تقف وراء الوثائق التالية التي استخلصنا منها المضمون والإلهام:
-- [The SciPy Code of Conduct](https://docs.scipy.org/doc/scipy/reference/dev/conduct/code_of_conduct.html)
+- [القواعد السلوكية لسكابي](https://docs.scipy.org/doc/scipy/reference/dev/conduct/code_of_conduct.html)
From 2181f11ae7cdfe10466e3000e902b53b12a34cd6 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 10 Apr 2021 16:00:48 +0200
Subject: [PATCH 260/909] New translations community.md (Japanese)
---
content/ja/community.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/ja/community.md b/content/ja/community.md
index 5794d5626f..9f8734ed38 100644
--- a/content/ja/community.md
+++ b/content/ja/community.md
@@ -3,7 +3,7 @@ title: コミュニティ
sidebar: false
---
-Numpy は 常に多様な[コントリビュータ](/gallery/team.html) のグループによって開発されている、コミュニティ主導のオープンソースプロジェクトです。 Numpy を主導するグループは、オープンで協力的でポジティブなコミュニティを作ることを、約束しました。 コミュニティを繁栄させるために、コミュニティの人達と交流する方法については、 [NumPy 行動規範](/code-of-conduct) をご覧ください。
+NumPy は非常に多様な[コントリビュータ](/gallery/team.html) のグループによって開発されている、コミュニティ主導のオープンソースプロジェクトです。 Numpy を主導するグループは、オープンで協力的でポジティブなコミュニティを作ることを、約束しました。 コミュニティを繁栄させるために、コミュニティの人達と交流する方法については、 [NumPy 行動規範](/code-of-conduct) をご覧ください。
私たちは、NumPyコミュニティ内で学んだり、知識を共有したり、他の人と交流するためのいくつかのコミュニケーション方法を提供しています。
From 6d105134be2aff74e8275f4fe5235fe3e0217bd0 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 10 Apr 2021 17:02:33 +0200
Subject: [PATCH 261/909] New translations learn.md (Chinese Simplified)
---
content/zh/learn.md | 1 +
1 file changed, 1 insertion(+)
diff --git a/content/zh/learn.md b/content/zh/learn.md
index 4611d3a402..ea35371573 100644
--- a/content/zh/learn.md
+++ b/content/zh/learn.md
@@ -15,6 +15,7 @@ There's a ton of information about NumPy out there. If you are new, we'd strongl
**Tutorials**
* [NumPy Quickstart Tutorial](https://numpy.org/devdocs/user/quickstart.html)
+* [NumPy Illustrated: The Visual Guide to NumPy *by Lev Maximov*](https://betterprogramming.pub/3b1d4976de1d?sk=57b908a77aa44075a49293fa1631dd9b)
* [SciPy Lectures](https://scipy-lectures.org/) Besides covering NumPy, these lectures offer a broader introduction to the scientific Python ecosystem.
* [NumPy: the absolute basics for beginners](https://numpy.org/devdocs/user/absolute_beginners.html)
* [Machine Learning Plus - Introduction to ndarray](https://www.machinelearningplus.com/python/numpy-tutorial-part1-array-python-examples/)
From 1b8ef1346f8ccab0419fc3f3f28d4c11612325ec Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 10 Apr 2021 17:02:40 +0200
Subject: [PATCH 262/909] New translations about.md (Chinese Simplified)
---
content/zh/about.md | 15 +++++++++------
1 file changed, 9 insertions(+), 6 deletions(-)
diff --git a/content/zh/about.md b/content/zh/about.md
index 0632e61ae4..5dfd4e796f 100644
--- a/content/zh/about.md
+++ b/content/zh/about.md
@@ -15,16 +15,13 @@ NumPy 是一个使 Python 支持数值计算的开源项目, 它诞生于 2005
指导委员会的成员们通过与 Numpy 社区合作并提供服务的形式来确保项目的长期发展,包括技术层面和社区层面。 Numpy 指导委员会目前由下列成员组成(按字母顺序排列):
- Sebastian Berg
-- Jaime Fernández del Río
- Ralf Gommers
-- Allan Haldane
- Charles Harris
- Stephan Hoyer
+- Melissa Weber Mendonça
+- Inessa Pawson
- Matti Picus
-- Nathaniel Smith
-- Julian Taylor
-- Pauli Virtanen
-- Stéfan van der Walt
+- Stéfan van der Walt
- Eric Wieser
荣誉会员:
@@ -32,6 +29,12 @@ NumPy 是一个使 Python 支持数值计算的开源项目, 它诞生于 2005
- Travis Oliphant(项目创始人,2005-2012年)
- Alex Griffing(2015-2017年)
- Marten van Kerkwijk (2017-2019年)
+- Allan Haldane (2015-2021)
+- Nathaniel Smith (2012-2021)
+- Julian Taylor (2013-2021)
+- Pauli Virtanen (2008-2021)
+- Jaime Fernández del Río (2014-2021)
+
## 团队
From 0928b31840ad569aed418aa2df900a72d4d3b2a3 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 10 Apr 2021 17:02:51 +0200
Subject: [PATCH 263/909] New translations learn.md (Korean)
---
content/ko/learn.md | 1 +
1 file changed, 1 insertion(+)
diff --git a/content/ko/learn.md b/content/ko/learn.md
index 04e49d32d6..2441c963be 100644
--- a/content/ko/learn.md
+++ b/content/ko/learn.md
@@ -15,6 +15,7 @@ For the **official NumPy documentation** visit [numpy.org/doc/stable](https://nu
**튜토리얼**
* [NumPy Quickstart Tutorial](https://numpy.org/devdocs/user/quickstart.html)
+* [NumPy Illustrated: The Visual Guide to NumPy *by Lev Maximov*](https://betterprogramming.pub/3b1d4976de1d?sk=57b908a77aa44075a49293fa1631dd9b)
* [SciPy Lectures](https://scipy-lectures.org/) Besides covering NumPy, these lectures offer a broader introduction to the scientific Python ecosystem.
* [NumPy: the absolute basics for beginners](https://numpy.org/devdocs/user/absolute_beginners.html)
* [Machine Learning Plus - Introduction to ndarray](https://www.machinelearningplus.com/python/numpy-tutorial-part1-array-python-examples/)
From 0ba550f4674e11045233ef35dd81663d620c663a Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 10 Apr 2021 17:02:58 +0200
Subject: [PATCH 264/909] New translations about.md (Korean)
---
content/ko/about.md | 13 ++++++++-----
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git a/content/ko/about.md b/content/ko/about.md
index 871d435f9a..1cfe839c79 100644
--- a/content/ko/about.md
+++ b/content/ko/about.md
@@ -15,15 +15,12 @@ NumPy는 광범위한 Scientific Python 커뮤니티의 협의를 통해 GitHub
NumPy 운영 위원회의 역할은 더 광범위한 NumPy 커뮤니티와 협력하고 서비스를 통해서 기술적으로나 커뮤니티로서 프로젝트의 장기적인 안녕을 보장하는 것입니다. NumPy 운영 위원회는 현재 다음과 같은 회원들로 구성되어 있습니다. (알파벳 순서)
- Sebastian Berg
-- Jaime Fernández del Río
- Ralf Gommers
-- Allan Haldane
- Charles Harris
- Stephan Hoyer
+- Melissa Weber Mendonça
+- Inessa Pawson
- Matti Picus
-- Nathaniel Smith
-- Julian Taylor
-- Pauli Virtanen
- Stéfan van der Walt
- Eric Wieser
@@ -32,6 +29,12 @@ NumPy 운영 위원회의 역할은 더 광범위한 NumPy 커뮤니티와 협
- Travis Oliphant (project founder, 2005-2012)
- Alex Griffing (2015-2017)
- Marten van Kerkwijk (2017-2019)
+- Allan Haldane (2015-2021)
+- Nathaniel Smith (2012-2021)
+- Julian Taylor (2013-2021)
+- Pauli Virtanen (2008-2021)
+- Jaime Fernández del Río (2014-2021)
+
## 팀
From 9d16d9f019b8733a56879f53564ced8eff0a889a Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 10 Apr 2021 17:03:11 +0200
Subject: [PATCH 265/909] New translations learn.md (Portuguese, Brazilian)
---
content/pt/learn.md | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/content/pt/learn.md b/content/pt/learn.md
index 6d8d5b6a24..ee3d572e04 100644
--- a/content/pt/learn.md
+++ b/content/pt/learn.md
@@ -15,14 +15,15 @@ Há uma tonelada de informações sobre o NumPy lá fora. Se você está começa
**Tutoriais**
* [NumPy Quickstart Tutorial (Tutorial de Início Rápido)](https://numpy.org/devdocs/user/quickstart.html)
-* [SciPy Lectures](https://scipy-lectures.org/) Além de incluir conteúdo sobre a NumPy, estas aulas oferecem uma introdução mais ampla ao ecossistema científico do Python.
-* [NumPy: the absolute basics for beginners ("o básico absoluto para inciantes")](https://numpy.org/devdocs/user/absolute_beginners.html)
+* [NumPy Illustrated: The Visual Guide to NumPy *by Lev Maximov*](https://betterprogramming.pub/3b1d4976de1d?sk=57b908a77aa44075a49293fa1631dd9b)
+* [SciPy Lectures](https://scipy-lectures.org/) Besides covering NumPy, these lectures offer a broader introduction to the scientific Python ecosystem.
+* [NumPy: the absolute basics for beginners](https://numpy.org/devdocs/user/absolute_beginners.html)
* [Machine Learning Plus - Introduction to ndarray](https://www.machinelearningplus.com/python/numpy-tutorial-part1-array-python-examples/)
* [Edureka - Learn NumPy Arrays with Examples ](https://www.edureka.co/blog/python-numpy-tutorial/)
* [Dataquest - NumPy Tutorial: Data Analysis with Python](https://www.dataquest.io/blog/numpy-tutorial-python/)
-* [NumPy tutorial *por Nicolas Rougier*](https://github.com/rougier/numpy-tutorial)
+* [NumPy tutorial *by Nicolas Rougier*](https://github.com/rougier/numpy-tutorial)
* [Stanford CS231 *by Justin Johnson*](http://cs231n.github.io/python-numpy-tutorial/)
-* [NumPy User Guide (Guia de Usuário NumPy)](https://numpy.org/devdocs)
+* [NumPy User Guide](https://numpy.org/devdocs)
**Livros**
From ead18a3d9d6e50acb269575ccb6eb57271c23588 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 10 Apr 2021 17:03:18 +0200
Subject: [PATCH 266/909] New translations about.md (Portuguese, Brazilian)
---
content/pt/about.md | 13 ++++++++-----
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git a/content/pt/about.md b/content/pt/about.md
index 163d4eab78..a90423141f 100644
--- a/content/pt/about.md
+++ b/content/pt/about.md
@@ -15,15 +15,12 @@ O NumPy é desenvolvido no GitHub, através do consenso da comunidade NumPy e de
O papel do Conselho Diretor do NumPy consiste em assegurar o bem-estar a longo prazo do projeto, tanto nos aspectos técnicos quanto na comunidade. Isso é feito através do trabalho com e para a comunidade NumPy em geral. O Conselho Diretor do NumPy atualmente consiste dos seguintes membros (em ordem alfabética):
- Sebastian Berg
-- Jaime Fernández del Río
- Ralf Gommers
-- Allan Haldane
- Charles Harris
- Stephan Hoyer
+- Melissa Weber Mendonça
+- Inessa Pawson
- Matti Picus
-- Nathaniel Smith
-- Julian Taylor
-- Pauli Virtanen
- Stéfan van der Walt
- Eric Wieser
@@ -32,6 +29,12 @@ Membros Eméritos:
- Travis Oliphant (fundador do projeto, 2005-2012)
- Alex Griffing (2015-2017)
- Marten van Kerkwijk (2017-2019)
+- Allan Haldane (2015-2021)
+- Nathaniel Smith (2012-2021)
+- Julian Taylor (2013-2021)
+- Pauli Virtanen (2008-2021)
+- Jaime Fernández del Río (2014-2021)
+
## Times
From 17987868f431f2e74a80aa790fa1580f541f79e5 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 10 Apr 2021 17:03:28 +0200
Subject: [PATCH 267/909] New translations learn.md (Japanese)
---
content/ja/learn.md | 15 ++++++++-------
1 file changed, 8 insertions(+), 7 deletions(-)
diff --git a/content/ja/learn.md b/content/ja/learn.md
index 665f16893c..ccbc6bfdb1 100644
--- a/content/ja/learn.md
+++ b/content/ja/learn.md
@@ -15,14 +15,15 @@ NumPyについての資料は多数存在しています。 初心者の方に
**チュートリアル**
* [NumPy Quickstart チュートリアル](https://numpy.org/devdocs/user/quickstart.html)
-* [SciPyレクチャー](https://scipy-lectures.org/) NumPyだけでなく、科学的なPythonソフトウェアエコシステムを広く紹介しています。
-* [Numpy: 初心者のための基本](https://numpy.org/devdocs/user/absolute_beginners.html)
-* [機械学習プラス - ndarray入門](https://www.machinelearningplus.com/python/numpy-tutorial-part1-array-python-examples/)
-* [Edureka - NumPy配列を例題で学ぶ ](https://www.edureka.co/blog/python-numpy-tutorial/)
-* [Dataquest - NumPyチュートリアル: Python を使ったデータ解析](https://www.dataquest.io/blog/numpy-tutorial-python/)
-* [Numpy チュートリアル *by Nicolas Rougier*](https://github.com/rougier/numpy-tutorial)
+* [NumPy Illustrated: The Visual Guide to NumPy *by Lev Maximov*](https://betterprogramming.pub/3b1d4976de1d?sk=57b908a77aa44075a49293fa1631dd9b)
+* [SciPy Lectures](https://scipy-lectures.org/) Besides covering NumPy, these lectures offer a broader introduction to the scientific Python ecosystem.
+* [NumPy: the absolute basics for beginners](https://numpy.org/devdocs/user/absolute_beginners.html)
+* [Machine Learning Plus - Introduction to ndarray](https://www.machinelearningplus.com/python/numpy-tutorial-part1-array-python-examples/)
+* [Edureka - Learn NumPy Arrays with Examples ](https://www.edureka.co/blog/python-numpy-tutorial/)
+* [Dataquest - NumPy Tutorial: Data Analysis with Python](https://www.dataquest.io/blog/numpy-tutorial-python/)
+* [NumPy tutorial *by Nicolas Rougier*](https://github.com/rougier/numpy-tutorial)
* [Stanford CS231 *by Justin Johnson*](http://cs231n.github.io/python-numpy-tutorial/)
-* [Numpyユーザーガイド](https://numpy.org/devdocs)
+* [NumPy User Guide](https://numpy.org/devdocs)
**書籍**
From 27d0cfd0115fac70be4d600b0a1371e7b4889998 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 10 Apr 2021 17:03:31 +0200
Subject: [PATCH 268/909] New translations about.md (Arabic)
---
content/ar/about.md | 13 ++++++++-----
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git a/content/ar/about.md b/content/ar/about.md
index 0171632a52..29d4a19ad9 100644
--- a/content/ar/about.md
+++ b/content/ar/about.md
@@ -15,15 +15,12 @@ _بعض المعلومات حول مشروع ومجتمع نمباي_
The role of the NumPy Steering Council is to ensure, through working with and serving the broader NumPy community, the long-term well-being of the project, both technically and as a community. ويتألف المجلس التوجيهي المعني لنمباي حاليا علي الأعضاء التالية (بالترتيب الأبجدي):
- Sebastian Berg
-- Jaime Fernández del Río
- Ralf Gommers
-- Allan Haldane
- Charles Harris
- Stephan Hoyer
+- Melissa Weber Mendonça
+- Inessa Pawson
- Matti Picus
-- Nathaniel Smith
-- Julian Taylor
-- Pauli Virtanen
- Stéfan van der Walt
- Eric Wieser
@@ -32,6 +29,12 @@ Emeritus:
- Travis Oliphant (project founder, 2005-2012)
- Alex Griffing (2015-2017)
- Marten van Kerkwijk (2017-2019)
+- Allan Haldane (2015-2021)
+- Nathaniel Smith (2012-2021)
+- Julian Taylor (2013-2021)
+- Pauli Virtanen (2008-2021)
+- Jaime Fernández del Río (2014-2021)
+
## Teams
From c896bdb88758c766f5bae693acbe53043bf7d225 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 10 Apr 2021 17:03:42 +0200
Subject: [PATCH 269/909] New translations learn.md (Spanish)
---
content/es/learn.md | 1 +
1 file changed, 1 insertion(+)
diff --git a/content/es/learn.md b/content/es/learn.md
index 4611d3a402..ea35371573 100644
--- a/content/es/learn.md
+++ b/content/es/learn.md
@@ -15,6 +15,7 @@ There's a ton of information about NumPy out there. If you are new, we'd strongl
**Tutorials**
* [NumPy Quickstart Tutorial](https://numpy.org/devdocs/user/quickstart.html)
+* [NumPy Illustrated: The Visual Guide to NumPy *by Lev Maximov*](https://betterprogramming.pub/3b1d4976de1d?sk=57b908a77aa44075a49293fa1631dd9b)
* [SciPy Lectures](https://scipy-lectures.org/) Besides covering NumPy, these lectures offer a broader introduction to the scientific Python ecosystem.
* [NumPy: the absolute basics for beginners](https://numpy.org/devdocs/user/absolute_beginners.html)
* [Machine Learning Plus - Introduction to ndarray](https://www.machinelearningplus.com/python/numpy-tutorial-part1-array-python-examples/)
From b459b3f43f291545b4a3d3459283ef5c6cf46686 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 10 Apr 2021 17:03:47 +0200
Subject: [PATCH 270/909] New translations about.md (Spanish)
---
content/es/about.md | 13 ++++++++-----
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git a/content/es/about.md b/content/es/about.md
index 1779f7531f..1de6728185 100644
--- a/content/es/about.md
+++ b/content/es/about.md
@@ -15,15 +15,12 @@ NumPy is developed in the open on GitHub, through the consensus of the NumPy and
The role of the NumPy Steering Council is to ensure, through working with and serving the broader NumPy community, the long-term well-being of the project, both technically and as a community. The NumPy Steering Council currently consists of the following members (in alphabetical order):
- Sebastian Berg
-- Jaime Fernández del Río
- Ralf Gommers
-- Allan Haldane
- Charles Harris
- Stephan Hoyer
+- Melissa Weber Mendonça
+- Inessa Pawson
- Matti Picus
-- Nathaniel Smith
-- Julian Taylor
-- Pauli Virtanen
- Stéfan van der Walt
- Eric Wieser
@@ -32,6 +29,12 @@ Emeritus:
- Travis Oliphant (project founder, 2005-2012)
- Alex Griffing (2015-2017)
- Marten van Kerkwijk (2017-2019)
+- Allan Haldane (2015-2021)
+- Nathaniel Smith (2012-2021)
+- Julian Taylor (2013-2021)
+- Pauli Virtanen (2008-2021)
+- Jaime Fernández del Río (2014-2021)
+
## Teams
From 08e0f187e5e0e47bb0f13b9966726b1ffa5f302f Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 10 Apr 2021 17:03:54 +0200
Subject: [PATCH 271/909] New translations about.md (Japanese)
---
content/ja/about.md | 15 +++++++++------
1 file changed, 9 insertions(+), 6 deletions(-)
diff --git a/content/ja/about.md b/content/ja/about.md
index 530f16d9cb..a9c9232830 100644
--- a/content/ja/about.md
+++ b/content/ja/about.md
@@ -15,16 +15,13 @@ NumPy は 、NumPyコミュニティやより広範な科学計算用Python コ
NumPy運営委員会の役割は、NumPyのコミュニティと協力しサポートすることを通じて、技術的にもコミュニティ的にも長期的にNumPyプロジェクトを良い状態に保つことです。 NumPy運営委員会は現在以下のメンバーで構成されています (アルファベット順):
- Sebastian Berg
-- Jaime Fernández del Río
- Ralf Gommers
-- Allan Haldane
- Charles Harris
- Stephan Hoyer
+- Melissa Weber Mendonça
+- Inessa Pawson
- Matti Picus
-- Nathaniel Smith
-- Julian Taylor
-- Pauli Virtanen
-- Stéfan van der Walt
+- Stéfan van der Walt
- Eric Wieser
終身名誉委員
@@ -32,6 +29,12 @@ NumPy運営委員会の役割は、NumPyのコミュニティと協力しサポ
- Travis Oliphant (プロジェクト創設者, 2005-2012)
- Alex Griffing (2015-2017)
- Marten van Kerkwijk (2017-2019)
+- Allan Haldane (2015-2021)
+- Nathaniel Smith (2012-2021)
+- Julian Taylor (2013-2021)
+- Pauli Virtanen (2008-2021)
+- Jaime Fernández del Río (2014-2021)
+
## チーム
From 9e424ef7a7600ae97cb420c4e9b3c020537f8a43 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 10 Apr 2021 17:04:02 +0200
Subject: [PATCH 272/909] New translations community.md (Japanese)
---
content/ja/community.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/ja/community.md b/content/ja/community.md
index 9f8734ed38..b6a1480c45 100644
--- a/content/ja/community.md
+++ b/content/ja/community.md
@@ -3,7 +3,7 @@ title: コミュニティ
sidebar: false
---
-NumPy は非常に多様な[コントリビュータ](/gallery/team.html) のグループによって開発されている、コミュニティ主導のオープンソースプロジェクトです。 Numpy を主導するグループは、オープンで協力的でポジティブなコミュニティを作ることを、約束しました。 コミュニティを繁栄させるために、コミュニティの人達と交流する方法については、 [NumPy 行動規範](/code-of-conduct) をご覧ください。
+NumPy は非常に多様な[コントリビュータ](/gallery/team.html) のグループによって開発されている、コミュニティ主導のオープンソースプロジェクトです。 Numpy を主導するグループは、オープンで協力的でポジティブなコミュニティを作ることを、約束しました。 [NumPy 行動規範](/code-of-conduct) をぜひ参照してください。コミュニティの繁栄につながるようなかたちで、人々と交流する方法について書いてあります。
私たちは、NumPyコミュニティ内で学んだり、知識を共有したり、他の人と交流するためのいくつかのコミュニケーション方法を提供しています。
From b7812920f51201bb9f1cc8ce662c1a454d19e011 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 10 Apr 2021 17:04:16 +0200
Subject: [PATCH 273/909] New translations learn.md (Arabic)
---
content/ar/learn.md | 1 +
1 file changed, 1 insertion(+)
diff --git a/content/ar/learn.md b/content/ar/learn.md
index 4611d3a402..ea35371573 100644
--- a/content/ar/learn.md
+++ b/content/ar/learn.md
@@ -15,6 +15,7 @@ There's a ton of information about NumPy out there. If you are new, we'd strongl
**Tutorials**
* [NumPy Quickstart Tutorial](https://numpy.org/devdocs/user/quickstart.html)
+* [NumPy Illustrated: The Visual Guide to NumPy *by Lev Maximov*](https://betterprogramming.pub/3b1d4976de1d?sk=57b908a77aa44075a49293fa1631dd9b)
* [SciPy Lectures](https://scipy-lectures.org/) Besides covering NumPy, these lectures offer a broader introduction to the scientific Python ecosystem.
* [NumPy: the absolute basics for beginners](https://numpy.org/devdocs/user/absolute_beginners.html)
* [Machine Learning Plus - Introduction to ndarray](https://www.machinelearningplus.com/python/numpy-tutorial-part1-array-python-examples/)
From 1517109944ffea73e6f013524e5b46c9bb19cc21 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 10 Apr 2021 18:01:10 +0200
Subject: [PATCH 274/909] New translations community.md (Japanese)
---
content/ja/community.md | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/content/ja/community.md b/content/ja/community.md
index b6a1480c45..8e1052ff92 100644
--- a/content/ja/community.md
+++ b/content/ja/community.md
@@ -15,7 +15,7 @@ Numpy プロジェクトやコミュニティと直接交流する方法は次
### [NumPyメーリングリスト:](https://mail.python.org/mailman/listinfo/numpy-discussion)
-このメーリングリストは、Numpy に新しい機能を追加するなど、より長い期間の議論のための主なコミュニケーションの場です。 NumpyのRoadmapに変更を加えたり、プロジェクト全体での意思決定を行います。 このメーリングリストでは、リリース、開発者会議、スプリント、カンファレンストークなど、Numpy についてのアナウンスなどにも利用されます。
+このメーリングリストは、NumPyへの新機能追加するなど、より長い期間の議論のための主なコミュニケーションの場です。 NumPyロードマップの変更や、プロジェクト全体での意思決定を行います。 このメーリングリストでは、リリース、開発者会議、スプリント、カンファレンストークなど、Numpy についてのアナウンスなどにも利用されます。
このメーリングリストでは、一番下のメールを使用し、メーリングリストに返信して下さい( 他の送信者ではなく)。 また、自動送信のメールには返信しないでください。 このメーリングリストの検索可能なアーカイブは [こちら](http://numpy-discussion.10968.n7.nabble.com/) にあります。
@@ -38,14 +38,14 @@ SlackはNumpyに_ 貢献するための質問をする_、リアルタイムの
## 勉強会とミートアップ
-NumPyや、データサイエンス、科学技術計算などのより広いエコシステムのためのPythonパッケージついて、もっと学ぶためのローカルミートアップや勉強会を見つけたい場合、 [PyData ミートアップ](https://www.meetup.com/pro/pydata/) (150人以上のミートアップ、10万人以上のメンバーをまとめたもの) を調べてみることをお勧めします。
+NumPy、データサイエンス、科学技術計算などのより広いエコシステムのためのPythonパッケージについてもっと学ぶために、ローカルのミートアップや勉強会を見つけたい場合、 [PyData ミートアップス](https://www.meetup.com/pro/pydata/) (150人以上のミートアップ、10万人以上のメンバーをまとめたもの) を調べてみるのが良いでしょう。
加えて、NumPy では開発チームと参加に興味があるコントリビュータのために、対面でのスプリントを時折開催しています。 この開発スプリントは通常数ヶ月に一度に開催されており、 [ メーリングリスト ](https://mail. python. org/mailman/listinfo/numpy-discussion) と [ Twitter ](https://twitter. com/numpy_team) で開催連絡されます。
## カンファレンス
-Numpy プロジェクトは独自のカンファレンスは開催していません。 NumPy の管理者や、コントリビュータ、ユーザーに最も人気があったカンファレンスは、SciPy および PyDataのカンファレンスです。
+Numpy プロジェクトは独自のカンファレンスは開催していません。 伝統的には、SciPy および PyDataのカンファレンスシリーズが、NumPy のメンテナ・コントリビュータ・ユーザーに最も人気がありました。
- [SciPy US](https://conference.scipy.org)
- [EuroSciPy](https://www.euroscipy.org)
@@ -59,7 +59,7 @@ Numpy プロジェクトは独自のカンファレンスは開催していま
## NumPy コミュニティに参加する
-Numpyプロジェクトを成功させるには、あなたの専門知識とプロジェクトに関する熱意が必要です。 プログラマーじゃないから参加できない? そんなことはありません! Numpy に貢献する様々な方法があります。
+プロジェクトを成功させるために、NumPyはあなたの専門知識とプロジェクトに関する熱意を必要としています。 プログラマーではないから参加できない? そんなことはありません! NumPyに貢献するには、様々な方法があります。
-もし、Numpyに貢献したい場合は、 [コントリビュート](/contribute) ページをご覧いただくことをお勧めします。
+NumPyに貢献したい場合は、 [コントリビュート](/contribute) ページをご覧いただくことをお勧めします。
From a3009cc31da12fcc9de94c77d58f435fe049f7de Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Wed, 14 Apr 2021 21:17:24 +0200
Subject: [PATCH 275/909] New translations config.yaml (Chinese Simplified)
---
content/zh/config.yaml | 152 +++++++++++++++++++++++++++++++++++++++++
1 file changed, 152 insertions(+)
create mode 100644 content/zh/config.yaml
diff --git a/content/zh/config.yaml b/content/zh/config.yaml
new file mode 100644
index 0000000000..64c90d9a8b
--- /dev/null
+++ b/content/zh/config.yaml
@@ -0,0 +1,152 @@
+---
+languageName: English
+params:
+ description: Why NumPy? Powerful n-dimensional arrays. Numerical computing tools. Interoperable. Performant. Open source.
+ navbarlogo:
+ image: logos/numpy.svg
+ link: /
+ hero:
+ #Main hero title
+ title: NumPy
+ #Hero subtitle (optional)
+ subtitle: The fundamental package for scientific computing with Python
+ #Button text
+ buttontext: Get started
+ #Where the main hero button links to
+ buttonlink: "/install"
+ #Hero image (from static/images/___)
+ image: logos/numpy.svg
+ #Customizable navbar. For a dropdown, add a "sublinks" list.
+ news:
+ title: NumPy v1.20.0
+ content: Type annotation support - Performance improvements through multi-platform SIMD
+ url: /news
+ shell:
+ title: placeholder
+ casestudies:
+ title: CASE STUDIES
+ features:
+ -
+ title: First Image of a Black Hole
+ text: How NumPy, together with libraries like SciPy and Matplotlib that depend on NumPy, enabled the Event Horizon Telescope to produce the first ever image of a black hole
+ img: /images/content_images/case_studies/blackhole.png
+ alttext: First image of a black hole. It is an orange circle in a black background.
+ url: /case-studies/blackhole-image
+ -
+ title: Detection of Gravitational Waves
+ text: In 1916, Albert Einstein predicted gravitational waves; 100 years later their existence was confirmed by LIGO scientists using NumPy.
+ img: /images/content_images/case_studies/gravitional.png
+ alttext: Two orbs orbiting each other. They are displacing gravity around them.
+ url: /case-studies/gw-discov
+ -
+ title: Sports Analytics
+ text: Cricket Analytics is changing the game by improving player and team performance through statistical modelling and predictive analytics. NumPy enables many of these analyses.
+ img: /images/content_images/case_studies/sports.jpg
+ alttext: Cricket ball on green field.
+ url: /case-studies/cricket-analytics
+ -
+ title: Pose Estimation using deep learning
+ text: DeepLabCut uses NumPy for accelerating scientific studies that involve observing animal behavior for better understanding of motor control, across species and timescales.
+ img: /images/content_images/case_studies/deeplabcut.png
+ alttext: Cheetah pose analysis
+ url: /case-studies/deeplabcut-dnn
+ keyfeatures:
+ features:
+ -
+ title: Powerful N-dimensional arrays
+ text: Fast and versatile, the NumPy vectorization, indexing, and broadcasting concepts are the de-facto standards of array computing today.
+ -
+ title: Numerical computing tools
+ text: NumPy offers comprehensive mathematical functions, random number generators, linear algebra routines, Fourier transforms, and more.
+ -
+ title: Interoperable
+ text: NumPy supports a wide range of hardware and computing platforms, and plays well with distributed, GPU, and sparse array libraries.
+ -
+ title: Performant
+ text: The core of NumPy is well-optimized C code. Enjoy the flexibility of Python with the speed of compiled code.
+ -
+ title: Easy to use
+ text: NumPy's high level syntax makes it accessible and productive for programmers from any background or experience level.
+ -
+ title: Open source
+ text: Distributed under a liberal [BSD license](https://github.com/numpy/numpy/blob/master/LICENSE.txt), NumPy is developed and maintained [publicly on GitHub](https://github.com/numpy/numpy) by a vibrant, responsive, and diverse [community](/community).
+ tabs:
+ title: ECOSYSTEM
+ section5: false
+navbar:
+ -
+ title: Install
+ url: /install
+ -
+ title: Documentation
+ url: https://numpy.org/doc/stable
+ -
+ title: Learn
+ url: /learn
+ -
+ title: Community
+ url: /community
+ -
+ title: About Us
+ url: /about
+ -
+ title: Contribute
+ url: /contribute
+footer:
+ logo: numpy.svg
+ socialmediatitle: ""
+ socialmedia:
+ -
+ link: https://github.com/numpy/numpy
+ icon: github
+ -
+ link: https://twitter.com/numpy_team
+ icon: twitter
+ quicklinks:
+ column1:
+ title: ""
+ links:
+ -
+ text: Install
+ link: /install
+ -
+ text: Documentation
+ link: https://numpy.org/doc/stable
+ -
+ text: Learn
+ link: /learn
+ -
+ text: Citing Numpy
+ link: /citing-numpy
+ -
+ text: Roadmap
+ link: https://numpy.org/neps/roadmap.html
+ column2:
+ links:
+ -
+ text: About us
+ link: /about
+ -
+ text: Community
+ link: /community
+ -
+ text: Contribute
+ link: /contribute
+ -
+ text: Code of conduct
+ link: /code-of-conduct
+ column3:
+ links:
+ -
+ text: Get help
+ link: /gethelp
+ -
+ text: Terms of use
+ link: /terms
+ -
+ text: Privacy
+ link: /privacy
+ -
+ text: Press kit
+ link: /press-kit
+
From fd2174ff71f6259c83634cd826894c61c9fc6ab6 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Wed, 14 Apr 2021 21:17:25 +0200
Subject: [PATCH 276/909] New translations config.yaml (Korean)
---
content/ko/config.yaml | 152 +++++++++++++++++++++++++++++++++++++++++
1 file changed, 152 insertions(+)
create mode 100644 content/ko/config.yaml
diff --git a/content/ko/config.yaml b/content/ko/config.yaml
new file mode 100644
index 0000000000..64c90d9a8b
--- /dev/null
+++ b/content/ko/config.yaml
@@ -0,0 +1,152 @@
+---
+languageName: English
+params:
+ description: Why NumPy? Powerful n-dimensional arrays. Numerical computing tools. Interoperable. Performant. Open source.
+ navbarlogo:
+ image: logos/numpy.svg
+ link: /
+ hero:
+ #Main hero title
+ title: NumPy
+ #Hero subtitle (optional)
+ subtitle: The fundamental package for scientific computing with Python
+ #Button text
+ buttontext: Get started
+ #Where the main hero button links to
+ buttonlink: "/install"
+ #Hero image (from static/images/___)
+ image: logos/numpy.svg
+ #Customizable navbar. For a dropdown, add a "sublinks" list.
+ news:
+ title: NumPy v1.20.0
+ content: Type annotation support - Performance improvements through multi-platform SIMD
+ url: /news
+ shell:
+ title: placeholder
+ casestudies:
+ title: CASE STUDIES
+ features:
+ -
+ title: First Image of a Black Hole
+ text: How NumPy, together with libraries like SciPy and Matplotlib that depend on NumPy, enabled the Event Horizon Telescope to produce the first ever image of a black hole
+ img: /images/content_images/case_studies/blackhole.png
+ alttext: First image of a black hole. It is an orange circle in a black background.
+ url: /case-studies/blackhole-image
+ -
+ title: Detection of Gravitational Waves
+ text: In 1916, Albert Einstein predicted gravitational waves; 100 years later their existence was confirmed by LIGO scientists using NumPy.
+ img: /images/content_images/case_studies/gravitional.png
+ alttext: Two orbs orbiting each other. They are displacing gravity around them.
+ url: /case-studies/gw-discov
+ -
+ title: Sports Analytics
+ text: Cricket Analytics is changing the game by improving player and team performance through statistical modelling and predictive analytics. NumPy enables many of these analyses.
+ img: /images/content_images/case_studies/sports.jpg
+ alttext: Cricket ball on green field.
+ url: /case-studies/cricket-analytics
+ -
+ title: Pose Estimation using deep learning
+ text: DeepLabCut uses NumPy for accelerating scientific studies that involve observing animal behavior for better understanding of motor control, across species and timescales.
+ img: /images/content_images/case_studies/deeplabcut.png
+ alttext: Cheetah pose analysis
+ url: /case-studies/deeplabcut-dnn
+ keyfeatures:
+ features:
+ -
+ title: Powerful N-dimensional arrays
+ text: Fast and versatile, the NumPy vectorization, indexing, and broadcasting concepts are the de-facto standards of array computing today.
+ -
+ title: Numerical computing tools
+ text: NumPy offers comprehensive mathematical functions, random number generators, linear algebra routines, Fourier transforms, and more.
+ -
+ title: Interoperable
+ text: NumPy supports a wide range of hardware and computing platforms, and plays well with distributed, GPU, and sparse array libraries.
+ -
+ title: Performant
+ text: The core of NumPy is well-optimized C code. Enjoy the flexibility of Python with the speed of compiled code.
+ -
+ title: Easy to use
+ text: NumPy's high level syntax makes it accessible and productive for programmers from any background or experience level.
+ -
+ title: Open source
+ text: Distributed under a liberal [BSD license](https://github.com/numpy/numpy/blob/master/LICENSE.txt), NumPy is developed and maintained [publicly on GitHub](https://github.com/numpy/numpy) by a vibrant, responsive, and diverse [community](/community).
+ tabs:
+ title: ECOSYSTEM
+ section5: false
+navbar:
+ -
+ title: Install
+ url: /install
+ -
+ title: Documentation
+ url: https://numpy.org/doc/stable
+ -
+ title: Learn
+ url: /learn
+ -
+ title: Community
+ url: /community
+ -
+ title: About Us
+ url: /about
+ -
+ title: Contribute
+ url: /contribute
+footer:
+ logo: numpy.svg
+ socialmediatitle: ""
+ socialmedia:
+ -
+ link: https://github.com/numpy/numpy
+ icon: github
+ -
+ link: https://twitter.com/numpy_team
+ icon: twitter
+ quicklinks:
+ column1:
+ title: ""
+ links:
+ -
+ text: Install
+ link: /install
+ -
+ text: Documentation
+ link: https://numpy.org/doc/stable
+ -
+ text: Learn
+ link: /learn
+ -
+ text: Citing Numpy
+ link: /citing-numpy
+ -
+ text: Roadmap
+ link: https://numpy.org/neps/roadmap.html
+ column2:
+ links:
+ -
+ text: About us
+ link: /about
+ -
+ text: Community
+ link: /community
+ -
+ text: Contribute
+ link: /contribute
+ -
+ text: Code of conduct
+ link: /code-of-conduct
+ column3:
+ links:
+ -
+ text: Get help
+ link: /gethelp
+ -
+ text: Terms of use
+ link: /terms
+ -
+ text: Privacy
+ link: /privacy
+ -
+ text: Press kit
+ link: /press-kit
+
From 3ca361ec6f745a9467bb89fb751063c330d410a9 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Wed, 14 Apr 2021 21:17:26 +0200
Subject: [PATCH 277/909] New translations config.yaml (Japanese)
---
content/ja/config.yaml | 152 +++++++++++++++++++++++++++++++++++++++++
1 file changed, 152 insertions(+)
create mode 100644 content/ja/config.yaml
diff --git a/content/ja/config.yaml b/content/ja/config.yaml
new file mode 100644
index 0000000000..64c90d9a8b
--- /dev/null
+++ b/content/ja/config.yaml
@@ -0,0 +1,152 @@
+---
+languageName: English
+params:
+ description: Why NumPy? Powerful n-dimensional arrays. Numerical computing tools. Interoperable. Performant. Open source.
+ navbarlogo:
+ image: logos/numpy.svg
+ link: /
+ hero:
+ #Main hero title
+ title: NumPy
+ #Hero subtitle (optional)
+ subtitle: The fundamental package for scientific computing with Python
+ #Button text
+ buttontext: Get started
+ #Where the main hero button links to
+ buttonlink: "/install"
+ #Hero image (from static/images/___)
+ image: logos/numpy.svg
+ #Customizable navbar. For a dropdown, add a "sublinks" list.
+ news:
+ title: NumPy v1.20.0
+ content: Type annotation support - Performance improvements through multi-platform SIMD
+ url: /news
+ shell:
+ title: placeholder
+ casestudies:
+ title: CASE STUDIES
+ features:
+ -
+ title: First Image of a Black Hole
+ text: How NumPy, together with libraries like SciPy and Matplotlib that depend on NumPy, enabled the Event Horizon Telescope to produce the first ever image of a black hole
+ img: /images/content_images/case_studies/blackhole.png
+ alttext: First image of a black hole. It is an orange circle in a black background.
+ url: /case-studies/blackhole-image
+ -
+ title: Detection of Gravitational Waves
+ text: In 1916, Albert Einstein predicted gravitational waves; 100 years later their existence was confirmed by LIGO scientists using NumPy.
+ img: /images/content_images/case_studies/gravitional.png
+ alttext: Two orbs orbiting each other. They are displacing gravity around them.
+ url: /case-studies/gw-discov
+ -
+ title: Sports Analytics
+ text: Cricket Analytics is changing the game by improving player and team performance through statistical modelling and predictive analytics. NumPy enables many of these analyses.
+ img: /images/content_images/case_studies/sports.jpg
+ alttext: Cricket ball on green field.
+ url: /case-studies/cricket-analytics
+ -
+ title: Pose Estimation using deep learning
+ text: DeepLabCut uses NumPy for accelerating scientific studies that involve observing animal behavior for better understanding of motor control, across species and timescales.
+ img: /images/content_images/case_studies/deeplabcut.png
+ alttext: Cheetah pose analysis
+ url: /case-studies/deeplabcut-dnn
+ keyfeatures:
+ features:
+ -
+ title: Powerful N-dimensional arrays
+ text: Fast and versatile, the NumPy vectorization, indexing, and broadcasting concepts are the de-facto standards of array computing today.
+ -
+ title: Numerical computing tools
+ text: NumPy offers comprehensive mathematical functions, random number generators, linear algebra routines, Fourier transforms, and more.
+ -
+ title: Interoperable
+ text: NumPy supports a wide range of hardware and computing platforms, and plays well with distributed, GPU, and sparse array libraries.
+ -
+ title: Performant
+ text: The core of NumPy is well-optimized C code. Enjoy the flexibility of Python with the speed of compiled code.
+ -
+ title: Easy to use
+ text: NumPy's high level syntax makes it accessible and productive for programmers from any background or experience level.
+ -
+ title: Open source
+ text: Distributed under a liberal [BSD license](https://github.com/numpy/numpy/blob/master/LICENSE.txt), NumPy is developed and maintained [publicly on GitHub](https://github.com/numpy/numpy) by a vibrant, responsive, and diverse [community](/community).
+ tabs:
+ title: ECOSYSTEM
+ section5: false
+navbar:
+ -
+ title: Install
+ url: /install
+ -
+ title: Documentation
+ url: https://numpy.org/doc/stable
+ -
+ title: Learn
+ url: /learn
+ -
+ title: Community
+ url: /community
+ -
+ title: About Us
+ url: /about
+ -
+ title: Contribute
+ url: /contribute
+footer:
+ logo: numpy.svg
+ socialmediatitle: ""
+ socialmedia:
+ -
+ link: https://github.com/numpy/numpy
+ icon: github
+ -
+ link: https://twitter.com/numpy_team
+ icon: twitter
+ quicklinks:
+ column1:
+ title: ""
+ links:
+ -
+ text: Install
+ link: /install
+ -
+ text: Documentation
+ link: https://numpy.org/doc/stable
+ -
+ text: Learn
+ link: /learn
+ -
+ text: Citing Numpy
+ link: /citing-numpy
+ -
+ text: Roadmap
+ link: https://numpy.org/neps/roadmap.html
+ column2:
+ links:
+ -
+ text: About us
+ link: /about
+ -
+ text: Community
+ link: /community
+ -
+ text: Contribute
+ link: /contribute
+ -
+ text: Code of conduct
+ link: /code-of-conduct
+ column3:
+ links:
+ -
+ text: Get help
+ link: /gethelp
+ -
+ text: Terms of use
+ link: /terms
+ -
+ text: Privacy
+ link: /privacy
+ -
+ text: Press kit
+ link: /press-kit
+
From 3ca277e3612533d4cf119a350db7330014772eab Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Wed, 14 Apr 2021 21:17:27 +0200
Subject: [PATCH 278/909] New translations config.yaml (Arabic)
---
content/ar/config.yaml | 152 +++++++++++++++++++++++++++++++++++++++++
1 file changed, 152 insertions(+)
create mode 100644 content/ar/config.yaml
diff --git a/content/ar/config.yaml b/content/ar/config.yaml
new file mode 100644
index 0000000000..64c90d9a8b
--- /dev/null
+++ b/content/ar/config.yaml
@@ -0,0 +1,152 @@
+---
+languageName: English
+params:
+ description: Why NumPy? Powerful n-dimensional arrays. Numerical computing tools. Interoperable. Performant. Open source.
+ navbarlogo:
+ image: logos/numpy.svg
+ link: /
+ hero:
+ #Main hero title
+ title: NumPy
+ #Hero subtitle (optional)
+ subtitle: The fundamental package for scientific computing with Python
+ #Button text
+ buttontext: Get started
+ #Where the main hero button links to
+ buttonlink: "/install"
+ #Hero image (from static/images/___)
+ image: logos/numpy.svg
+ #Customizable navbar. For a dropdown, add a "sublinks" list.
+ news:
+ title: NumPy v1.20.0
+ content: Type annotation support - Performance improvements through multi-platform SIMD
+ url: /news
+ shell:
+ title: placeholder
+ casestudies:
+ title: CASE STUDIES
+ features:
+ -
+ title: First Image of a Black Hole
+ text: How NumPy, together with libraries like SciPy and Matplotlib that depend on NumPy, enabled the Event Horizon Telescope to produce the first ever image of a black hole
+ img: /images/content_images/case_studies/blackhole.png
+ alttext: First image of a black hole. It is an orange circle in a black background.
+ url: /case-studies/blackhole-image
+ -
+ title: Detection of Gravitational Waves
+ text: In 1916, Albert Einstein predicted gravitational waves; 100 years later their existence was confirmed by LIGO scientists using NumPy.
+ img: /images/content_images/case_studies/gravitional.png
+ alttext: Two orbs orbiting each other. They are displacing gravity around them.
+ url: /case-studies/gw-discov
+ -
+ title: Sports Analytics
+ text: Cricket Analytics is changing the game by improving player and team performance through statistical modelling and predictive analytics. NumPy enables many of these analyses.
+ img: /images/content_images/case_studies/sports.jpg
+ alttext: Cricket ball on green field.
+ url: /case-studies/cricket-analytics
+ -
+ title: Pose Estimation using deep learning
+ text: DeepLabCut uses NumPy for accelerating scientific studies that involve observing animal behavior for better understanding of motor control, across species and timescales.
+ img: /images/content_images/case_studies/deeplabcut.png
+ alttext: Cheetah pose analysis
+ url: /case-studies/deeplabcut-dnn
+ keyfeatures:
+ features:
+ -
+ title: Powerful N-dimensional arrays
+ text: Fast and versatile, the NumPy vectorization, indexing, and broadcasting concepts are the de-facto standards of array computing today.
+ -
+ title: Numerical computing tools
+ text: NumPy offers comprehensive mathematical functions, random number generators, linear algebra routines, Fourier transforms, and more.
+ -
+ title: Interoperable
+ text: NumPy supports a wide range of hardware and computing platforms, and plays well with distributed, GPU, and sparse array libraries.
+ -
+ title: Performant
+ text: The core of NumPy is well-optimized C code. Enjoy the flexibility of Python with the speed of compiled code.
+ -
+ title: Easy to use
+ text: NumPy's high level syntax makes it accessible and productive for programmers from any background or experience level.
+ -
+ title: Open source
+ text: Distributed under a liberal [BSD license](https://github.com/numpy/numpy/blob/master/LICENSE.txt), NumPy is developed and maintained [publicly on GitHub](https://github.com/numpy/numpy) by a vibrant, responsive, and diverse [community](/community).
+ tabs:
+ title: ECOSYSTEM
+ section5: false
+navbar:
+ -
+ title: Install
+ url: /install
+ -
+ title: Documentation
+ url: https://numpy.org/doc/stable
+ -
+ title: Learn
+ url: /learn
+ -
+ title: Community
+ url: /community
+ -
+ title: About Us
+ url: /about
+ -
+ title: Contribute
+ url: /contribute
+footer:
+ logo: numpy.svg
+ socialmediatitle: ""
+ socialmedia:
+ -
+ link: https://github.com/numpy/numpy
+ icon: github
+ -
+ link: https://twitter.com/numpy_team
+ icon: twitter
+ quicklinks:
+ column1:
+ title: ""
+ links:
+ -
+ text: Install
+ link: /install
+ -
+ text: Documentation
+ link: https://numpy.org/doc/stable
+ -
+ text: Learn
+ link: /learn
+ -
+ text: Citing Numpy
+ link: /citing-numpy
+ -
+ text: Roadmap
+ link: https://numpy.org/neps/roadmap.html
+ column2:
+ links:
+ -
+ text: About us
+ link: /about
+ -
+ text: Community
+ link: /community
+ -
+ text: Contribute
+ link: /contribute
+ -
+ text: Code of conduct
+ link: /code-of-conduct
+ column3:
+ links:
+ -
+ text: Get help
+ link: /gethelp
+ -
+ text: Terms of use
+ link: /terms
+ -
+ text: Privacy
+ link: /privacy
+ -
+ text: Press kit
+ link: /press-kit
+
From 9405c3eccae3419d4435c5aa6746e4034b3cda52 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Wed, 14 Apr 2021 21:17:28 +0200
Subject: [PATCH 279/909] New translations config.yaml (Spanish)
---
content/es/config.yaml | 152 +++++++++++++++++++++++++++++++++++++++++
1 file changed, 152 insertions(+)
create mode 100644 content/es/config.yaml
diff --git a/content/es/config.yaml b/content/es/config.yaml
new file mode 100644
index 0000000000..64c90d9a8b
--- /dev/null
+++ b/content/es/config.yaml
@@ -0,0 +1,152 @@
+---
+languageName: English
+params:
+ description: Why NumPy? Powerful n-dimensional arrays. Numerical computing tools. Interoperable. Performant. Open source.
+ navbarlogo:
+ image: logos/numpy.svg
+ link: /
+ hero:
+ #Main hero title
+ title: NumPy
+ #Hero subtitle (optional)
+ subtitle: The fundamental package for scientific computing with Python
+ #Button text
+ buttontext: Get started
+ #Where the main hero button links to
+ buttonlink: "/install"
+ #Hero image (from static/images/___)
+ image: logos/numpy.svg
+ #Customizable navbar. For a dropdown, add a "sublinks" list.
+ news:
+ title: NumPy v1.20.0
+ content: Type annotation support - Performance improvements through multi-platform SIMD
+ url: /news
+ shell:
+ title: placeholder
+ casestudies:
+ title: CASE STUDIES
+ features:
+ -
+ title: First Image of a Black Hole
+ text: How NumPy, together with libraries like SciPy and Matplotlib that depend on NumPy, enabled the Event Horizon Telescope to produce the first ever image of a black hole
+ img: /images/content_images/case_studies/blackhole.png
+ alttext: First image of a black hole. It is an orange circle in a black background.
+ url: /case-studies/blackhole-image
+ -
+ title: Detection of Gravitational Waves
+ text: In 1916, Albert Einstein predicted gravitational waves; 100 years later their existence was confirmed by LIGO scientists using NumPy.
+ img: /images/content_images/case_studies/gravitional.png
+ alttext: Two orbs orbiting each other. They are displacing gravity around them.
+ url: /case-studies/gw-discov
+ -
+ title: Sports Analytics
+ text: Cricket Analytics is changing the game by improving player and team performance through statistical modelling and predictive analytics. NumPy enables many of these analyses.
+ img: /images/content_images/case_studies/sports.jpg
+ alttext: Cricket ball on green field.
+ url: /case-studies/cricket-analytics
+ -
+ title: Pose Estimation using deep learning
+ text: DeepLabCut uses NumPy for accelerating scientific studies that involve observing animal behavior for better understanding of motor control, across species and timescales.
+ img: /images/content_images/case_studies/deeplabcut.png
+ alttext: Cheetah pose analysis
+ url: /case-studies/deeplabcut-dnn
+ keyfeatures:
+ features:
+ -
+ title: Powerful N-dimensional arrays
+ text: Fast and versatile, the NumPy vectorization, indexing, and broadcasting concepts are the de-facto standards of array computing today.
+ -
+ title: Numerical computing tools
+ text: NumPy offers comprehensive mathematical functions, random number generators, linear algebra routines, Fourier transforms, and more.
+ -
+ title: Interoperable
+ text: NumPy supports a wide range of hardware and computing platforms, and plays well with distributed, GPU, and sparse array libraries.
+ -
+ title: Performant
+ text: The core of NumPy is well-optimized C code. Enjoy the flexibility of Python with the speed of compiled code.
+ -
+ title: Easy to use
+ text: NumPy's high level syntax makes it accessible and productive for programmers from any background or experience level.
+ -
+ title: Open source
+ text: Distributed under a liberal [BSD license](https://github.com/numpy/numpy/blob/master/LICENSE.txt), NumPy is developed and maintained [publicly on GitHub](https://github.com/numpy/numpy) by a vibrant, responsive, and diverse [community](/community).
+ tabs:
+ title: ECOSYSTEM
+ section5: false
+navbar:
+ -
+ title: Install
+ url: /install
+ -
+ title: Documentation
+ url: https://numpy.org/doc/stable
+ -
+ title: Learn
+ url: /learn
+ -
+ title: Community
+ url: /community
+ -
+ title: About Us
+ url: /about
+ -
+ title: Contribute
+ url: /contribute
+footer:
+ logo: numpy.svg
+ socialmediatitle: ""
+ socialmedia:
+ -
+ link: https://github.com/numpy/numpy
+ icon: github
+ -
+ link: https://twitter.com/numpy_team
+ icon: twitter
+ quicklinks:
+ column1:
+ title: ""
+ links:
+ -
+ text: Install
+ link: /install
+ -
+ text: Documentation
+ link: https://numpy.org/doc/stable
+ -
+ text: Learn
+ link: /learn
+ -
+ text: Citing Numpy
+ link: /citing-numpy
+ -
+ text: Roadmap
+ link: https://numpy.org/neps/roadmap.html
+ column2:
+ links:
+ -
+ text: About us
+ link: /about
+ -
+ text: Community
+ link: /community
+ -
+ text: Contribute
+ link: /contribute
+ -
+ text: Code of conduct
+ link: /code-of-conduct
+ column3:
+ links:
+ -
+ text: Get help
+ link: /gethelp
+ -
+ text: Terms of use
+ link: /terms
+ -
+ text: Privacy
+ link: /privacy
+ -
+ text: Press kit
+ link: /press-kit
+
From 876a5872acca4c8919dbd3f1113dc3a7f9ac6df5 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Wed, 14 Apr 2021 21:17:52 +0200
Subject: [PATCH 280/909] New translations config.yaml (Portuguese, Brazilian)
---
content/pt/config.yaml | 152 +++++++++++++++++++++++++++++++++++++++++
1 file changed, 152 insertions(+)
create mode 100644 content/pt/config.yaml
diff --git a/content/pt/config.yaml b/content/pt/config.yaml
new file mode 100644
index 0000000000..64c90d9a8b
--- /dev/null
+++ b/content/pt/config.yaml
@@ -0,0 +1,152 @@
+---
+languageName: English
+params:
+ description: Why NumPy? Powerful n-dimensional arrays. Numerical computing tools. Interoperable. Performant. Open source.
+ navbarlogo:
+ image: logos/numpy.svg
+ link: /
+ hero:
+ #Main hero title
+ title: NumPy
+ #Hero subtitle (optional)
+ subtitle: The fundamental package for scientific computing with Python
+ #Button text
+ buttontext: Get started
+ #Where the main hero button links to
+ buttonlink: "/install"
+ #Hero image (from static/images/___)
+ image: logos/numpy.svg
+ #Customizable navbar. For a dropdown, add a "sublinks" list.
+ news:
+ title: NumPy v1.20.0
+ content: Type annotation support - Performance improvements through multi-platform SIMD
+ url: /news
+ shell:
+ title: placeholder
+ casestudies:
+ title: CASE STUDIES
+ features:
+ -
+ title: First Image of a Black Hole
+ text: How NumPy, together with libraries like SciPy and Matplotlib that depend on NumPy, enabled the Event Horizon Telescope to produce the first ever image of a black hole
+ img: /images/content_images/case_studies/blackhole.png
+ alttext: First image of a black hole. It is an orange circle in a black background.
+ url: /case-studies/blackhole-image
+ -
+ title: Detection of Gravitational Waves
+ text: In 1916, Albert Einstein predicted gravitational waves; 100 years later their existence was confirmed by LIGO scientists using NumPy.
+ img: /images/content_images/case_studies/gravitional.png
+ alttext: Two orbs orbiting each other. They are displacing gravity around them.
+ url: /case-studies/gw-discov
+ -
+ title: Sports Analytics
+ text: Cricket Analytics is changing the game by improving player and team performance through statistical modelling and predictive analytics. NumPy enables many of these analyses.
+ img: /images/content_images/case_studies/sports.jpg
+ alttext: Cricket ball on green field.
+ url: /case-studies/cricket-analytics
+ -
+ title: Pose Estimation using deep learning
+ text: DeepLabCut uses NumPy for accelerating scientific studies that involve observing animal behavior for better understanding of motor control, across species and timescales.
+ img: /images/content_images/case_studies/deeplabcut.png
+ alttext: Cheetah pose analysis
+ url: /case-studies/deeplabcut-dnn
+ keyfeatures:
+ features:
+ -
+ title: Powerful N-dimensional arrays
+ text: Fast and versatile, the NumPy vectorization, indexing, and broadcasting concepts are the de-facto standards of array computing today.
+ -
+ title: Numerical computing tools
+ text: NumPy offers comprehensive mathematical functions, random number generators, linear algebra routines, Fourier transforms, and more.
+ -
+ title: Interoperable
+ text: NumPy supports a wide range of hardware and computing platforms, and plays well with distributed, GPU, and sparse array libraries.
+ -
+ title: Performant
+ text: The core of NumPy is well-optimized C code. Enjoy the flexibility of Python with the speed of compiled code.
+ -
+ title: Easy to use
+ text: NumPy's high level syntax makes it accessible and productive for programmers from any background or experience level.
+ -
+ title: Open source
+ text: Distributed under a liberal [BSD license](https://github.com/numpy/numpy/blob/master/LICENSE.txt), NumPy is developed and maintained [publicly on GitHub](https://github.com/numpy/numpy) by a vibrant, responsive, and diverse [community](/community).
+ tabs:
+ title: ECOSYSTEM
+ section5: false
+navbar:
+ -
+ title: Install
+ url: /install
+ -
+ title: Documentation
+ url: https://numpy.org/doc/stable
+ -
+ title: Learn
+ url: /learn
+ -
+ title: Community
+ url: /community
+ -
+ title: About Us
+ url: /about
+ -
+ title: Contribute
+ url: /contribute
+footer:
+ logo: numpy.svg
+ socialmediatitle: ""
+ socialmedia:
+ -
+ link: https://github.com/numpy/numpy
+ icon: github
+ -
+ link: https://twitter.com/numpy_team
+ icon: twitter
+ quicklinks:
+ column1:
+ title: ""
+ links:
+ -
+ text: Install
+ link: /install
+ -
+ text: Documentation
+ link: https://numpy.org/doc/stable
+ -
+ text: Learn
+ link: /learn
+ -
+ text: Citing Numpy
+ link: /citing-numpy
+ -
+ text: Roadmap
+ link: https://numpy.org/neps/roadmap.html
+ column2:
+ links:
+ -
+ text: About us
+ link: /about
+ -
+ text: Community
+ link: /community
+ -
+ text: Contribute
+ link: /contribute
+ -
+ text: Code of conduct
+ link: /code-of-conduct
+ column3:
+ links:
+ -
+ text: Get help
+ link: /gethelp
+ -
+ text: Terms of use
+ link: /terms
+ -
+ text: Privacy
+ link: /privacy
+ -
+ text: Press kit
+ link: /press-kit
+
From 2cbc2137955a2335f80688764d369417a2d7185f Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Thu, 15 Apr 2021 13:49:52 +0200
Subject: [PATCH 281/909] New translations blackhole-image.md (Japanese)
---
content/ja/case-studies/blackhole-image.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/ja/case-studies/blackhole-image.md b/content/ja/case-studies/blackhole-image.md
index 299d80cf2d..cd186ad23c 100644
--- a/content/ja/case-studies/blackhole-image.md
+++ b/content/ja/case-studies/blackhole-image.md
@@ -12,7 +12,7 @@ sidebar: false
## 地球の大きさの望遠鏡。
-[ Event Horizon telescope(EHT)](https:/eventhorizontelescope.org)は、地球サイズの解析望遠鏡を形成する8台の地上型電波望遠鏡から成るシステムで、これまでに前例のない感度と解像度で宇宙を研究することができます。 超長基線干渉法(VLBI) と呼ばれる手法を用いた巨大な仮想望遠鏡の角度分解能は、[20マイクロ秒][resolution]で、ニューヨークにある新聞をパリの歩道のカフェから読むのに十分な解像度です。
+[ Event Horizon Telescope(EHT)](https:/eventhorizontelescope.org)は、地球サイズの解析望遠鏡を形成する8台の地上型電波望遠鏡から成るシステムで、これまでに前例のない感度と解像度で宇宙を研究することができます。 超長基線干渉法(VLBI) と呼ばれる手法を用いた巨大な仮想望遠鏡の角度分解能は、[20マイクロ秒][resolution]で、ニューヨークにある新聞をパリの歩道のカフェから読むのに十分な解像度です。
### 主な目標と結果
From 8c8b660f310515e3ba081bdda6ef75732f35f28f Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Mon, 19 Apr 2021 21:13:26 +0200
Subject: [PATCH 282/909] New translations blackhole-image.md (Portuguese,
Brazilian)
---
content/pt/case-studies/blackhole-image.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/pt/case-studies/blackhole-image.md b/content/pt/case-studies/blackhole-image.md
index d84528f550..b983df6265 100644
--- a/content/pt/case-studies/blackhole-image.md
+++ b/content/pt/case-studies/blackhole-image.md
@@ -3,7 +3,7 @@ title: "Estudo de Caso: A Primeira Imagem de um Buraco Negro"
sidebar: false
---
-{{< figure src="/images/content_images/cs/blackhole.jpg" caption="**Black Hole M87**" alt="black hole image" attr="*(Créditos: Event Horizon Telescope Collaboration)*" attrlink="https://www.jpl.nasa.gov/images/universe/20190410/blackhole20190410.jpg" >}}
+{{< figure src="/images/content_images/cs/blackhole.jpg" caption="**Buraco Negro M87**" alt="black hole image" attr="*(Créditos: Event Horizon Telescope Collaboration)*" attrlink="https://www.jpl.nasa.gov/images/universe/20190410/blackhole20190410.jpg" >}}
Criar uma imagem do Buraco Negro M87 é como tentar ver algo que, por definição, é impossível de se ver.
From d57924edff33e4f276867ef9fbb96a8e3ff4d3f8 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Mon, 19 Apr 2021 22:13:57 +0200
Subject: [PATCH 283/909] New translations blackhole-image.md (Portuguese,
Brazilian)
---
content/pt/case-studies/blackhole-image.md | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/content/pt/case-studies/blackhole-image.md b/content/pt/case-studies/blackhole-image.md
index b983df6265..209b669074 100644
--- a/content/pt/case-studies/blackhole-image.md
+++ b/content/pt/case-studies/blackhole-image.md
@@ -3,7 +3,7 @@ title: "Estudo de Caso: A Primeira Imagem de um Buraco Negro"
sidebar: false
---
-{{< figure src="/images/content_images/cs/blackhole.jpg" caption="**Buraco Negro M87**" alt="black hole image" attr="*(Créditos: Event Horizon Telescope Collaboration)*" attrlink="https://www.jpl.nasa.gov/images/universe/20190410/blackhole20190410.jpg" >}}
+{{< figure src="/images/content_images/cs/blackhole.jpg" caption="**Buraco Negro M87**" alt="imagem de um buraco negro" attr="*(Créditos: Event Horizon Telescope Collaboration)*" attrlink="https://www.jpl.nasa.gov/images/universe/20190410/blackhole20190410.jpg" >}}
Criar uma imagem do Buraco Negro M87 é como tentar ver algo que, por definição, é impossível de se ver.
@@ -16,7 +16,7 @@ O [telescópio Event Horizon (EHT)](https://eventhorizontelescope.org), é um co
### Principais Objetivos e Resultados
-* **Uma nova visão do universo:**A imagem inovadora do EHT foi publicada 100 anos após [o experimento de Sir Arthur Eddington][eddington] ter produzido as primeiras evidências observacionais apoiando a teoria da relatividade geral de Einstein.
+* **Uma nova visão do universo:** A imagem inovadora do EHT foi publicada 100 anos após [o experimento de Sir Arthur Eddington][eddington] ter produzido as primeiras evidências observacionais apoiando a teoria da relatividade geral de Einstein.
* **O Buraco Negro:** o EHT foi treinado em um buraco negro supermassivo a aproximadamente 55 milhões de anos-luz da Terra, localizado no centro do galáxia Messier 87 (M87) no aglomerado de Virgem. Sua massa é equivalente a 6,5 bilhões de vezes a do Sol. Ele vem sendo estudado [há mais de 100 anos](https://www.jpl.nasa.gov/news/news.php?feature=7385), mas um buraco negro nunca havia sido observado visualmente antes.
@@ -36,7 +36,7 @@ O [telescópio Event Horizon (EHT)](https://eventhorizontelescope.org), é um co
Quando o objetivo é algo que nunca foi visto, como os cientistas podem ter confiança de que sua imagem está correta?
-{{< figure src="/images/content_images/cs/dataprocessbh.png" class="csfigcaption" caption="**Etapas de Processamento de Dados do EHT**" alt="data pipeline" align="middle" attr="(Créditos do diagrama: The Astrophysical Journal, Event Horizon Telescope Collaboration)" attrlink="https://iopscience.iop.org/article/10.3847/2041-8213/ab0c57" >}}
+{{< figure src="/images/content_images/cs/dataprocessbh.png" class="csfigcaption" caption="**Etapas de Processamento de Dados do EHT**" alt="pipeline de dados" align="middle" attr="(Créditos do diagrama: The Astrophysical Journal, Event Horizon Telescope Collaboration)" attrlink="https://iopscience.iop.org/article/10.3847/2041-8213/ab0c57" >}}
## O papel do NumPy
@@ -46,11 +46,11 @@ A colaboração do EHT venceu esses desafios ao estabelecer equipes independente
O trabalho desse grupo ilustra o papel do ecossistema científico do Python no avanço da ciência através da análise de dados colaborativa.
-{{< figure src="/images/content_images/cs/bh_numpy_role.png" class="fig-center" alt="role of numpy" caption="**O papel do NumPy na criação da primeira imagem de um Buraco Negro**" >}}
+{{< figure src="/images/content_images/cs/bh_numpy_role.png" class="fig-center" alt="o papel do NumPy" caption="**O papel do NumPy na criação da primeira imagem de um Buraco Negro**" >}}
Por exemplo, o pacote Python [`eht-imaging`][ehtim] fornece ferramentas para simular e realizar reconstrução de imagem nos dados do VLBI. O NumPy está no coração do processamento de dados vetoriais usado neste pacote, como ilustrado pelo gráfico parcial de dependências de software abaixo.
-{{< figure src="/images/content_images/cs/ehtim_numpy.png" class="fig-center" alt="ehtim dependency map highlighting numpy" caption="**Diagrama de dependência de software do pacote ehtim evidenciando o NumPy**" >}}
+{{< figure src="/images/content_images/cs/ehtim_numpy.png" class="fig-center" alt="mapa de dependências do ehtim com o numpy em realce" caption="**Diagrama de dependência de software do pacote ehtim evidenciando o NumPy**" >}}
Além do NumPy, muitos outros pacotes como [SciPy](https://www.scipy.org) e [Pandas](https://pandas.io) foram usados na *pipeline* de processamento de dados para criar a imagem do buraco negro. Os arquivos astronômicos de formato padrão e transformações de tempo/coordenadas foram tratados pelo [Astropy][astropy] enquanto a [Matplotlib][mpl] foi usada na visualização de dados em todas as etapas de análise, incluindo a geração da imagem final do buraco negro.
@@ -58,7 +58,7 @@ Além do NumPy, muitos outros pacotes como [SciPy](https://www.scipy.org) e [Pan
A estrutura de dados n-dimensional que é a funcionalidade central do NumPy permitiu aos pesquisadores manipular grandes conjuntos de dados, fornecendo a base para a primeira imagem de um buraco negro. Esse momento marcante na ciência fornece evidências visuais impressionantes para a teoria de Einstein. Esta conquista abrange não apenas avanços tecnológicos, mas colaboração científica em escala internacional entre mais de 200 cientistas e alguns dos melhores observatórios de rádio do mundo. Eles usaram algoritmos e técnicas de processamento de dados inovadores, que aperfeiçoaram os modelos astronômicos existentes, para ajudar a descobrir um dos mistérios do universo.
-{{< figure src="/images/content_images/cs/numpy_bh_benefits.png" class="fig-center" alt="numpy benefits" caption="**Funcionalidades-chave do NumPy utilizadas**" >}}
+{{< figure src="/images/content_images/cs/numpy_bh_benefits.png" class="fig-center" alt="funcionalidades do numpy" caption="**Funcionalidades-chave do NumPy utilizadas**" >}}
[resolution]: https://eventhorizontelescope.org/press-release-april-10-2019-astronomers-capture-first-image-black-hole
From 6e3e664296ba3d7412c3f77e49634777401849c5 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Mon, 19 Apr 2021 22:14:00 +0200
Subject: [PATCH 284/909] New translations gw-discov.md (Portuguese, Brazilian)
---
content/pt/case-studies/gw-discov.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/content/pt/case-studies/gw-discov.md b/content/pt/case-studies/gw-discov.md
index 6de7efed50..7b55f4a3ef 100644
--- a/content/pt/case-studies/gw-discov.md
+++ b/content/pt/case-studies/gw-discov.md
@@ -3,7 +3,7 @@ title: "Estudo de Caso: Descoberta de Ondas Gravitacionais"
sidebar: false
---
-{{< figure src="/images/content_images/cs/gw_sxs_image.png" class="fig-center" caption="**Ondas gravitacionais**" alt="binary coalesce black hole generating gravitational waves" attr="*(Créditos de imagem: O projeto Simulating eXtreme Spacetimes (SXS) no LIGO)*" attrlink="https://youtu.be/Zt8Z_uzG71o" >}}
+{{< figure src="/images/content_images/cs/gw_sxs_image.png" class="fig-center" caption="**Ondas gravitacionais**" alt="duas esferas orbitando a si mesmas, gerando ondas gravitacionais" attr="*(Créditos de imagem: O projeto Simulating eXtreme Spacetimes (SXS) no LIGO)*" attrlink="https://youtu.be/Zt8Z_uzG71o" >}}
O ecossistema científico Python é uma infraestrutura crítica para a pesquisa feita no LIGO.
@@ -39,7 +39,7 @@ O [Observatório Interferômetro Laser de Ondas Gravitacionais (LIGO)](https://w
Uma vez que os obstáculos relacionados a compreender as equações de Einstein bem o suficiente para resolvê-las usando supercomputadores foram ultrapassados, o próximo grande desafio era tornar os dados compreensíveis para o cérebro humano. A modelagem de simulações, assim como a detecção de sinais, exigem técnicas de visualização efetiva. A visualização também desempenha um papel de fornecer mais credibilidade à relatividade numérica aos olhos dos aficionados pela ciência pura, que não dão importância suficiente à relatividade numérica até que a imagem e as simulações tornem mais fácil a compreensão dos resultados para um público maior. A velocidade da computação complexa, e da renderização, re-renderização de imagens e simulações usando as últimas entradas e informações experimentais pode ser uma atividade demorada que desafia pesquisadores neste domínio.
-{{< figure src="/images/content_images/cs/gw_strain_amplitude.png" class="fig-center" alt="gravitational waves strain amplitude" caption="**Amplitude estimada da deformação das ondas gravitacionais do evento GW150914**" attr="(**Créditos do gráfico:** Observation of Gravitational Waves from a Binary Black Hole Merger, ResearchGate Publication)" attrlink="https://www.researchgate.net/publication/293886905_Observation_of_Gravitational_Waves_from_a_Binary_Black_Hole_Merger" >}}
+{{< figure src="/images/content_images/cs/gw_strain_amplitude.png" class="fig-center" alt="amplitude da deformação das ondas gravitacionais" caption="**Amplitude estimada da deformação das ondas gravitacionais do evento GW150914**" attr="(**Créditos do gráfico:** Observation of Gravitational Waves from a Binary Black Hole Merger, ResearchGate Publication)" attrlink="https://www.researchgate.net/publication/293886905_Observation_of_Gravitational_Waves_from_a_Binary_Black_Hole_Merger" >}}
## O papel da NumPy na detecção de ondas gravitacionais
@@ -56,11 +56,11 @@ NumPy, o pacote padrão de análise numérica para Python, foi parte do software
* Cálculo de correlações
* [Software](https://github.com/lscsoft) fundamental desenvolvido na análise de ondas gravitacionais, como [GwPy](https://gwpy.github.io/docs/stable/overview.html) e [PyCBC](https://pycbc.org) usam NumPy e AstroPy internamente para fornecer interfaces baseadas em objetos para utilidades, ferramentas e métodos para o estudo de dados de detectores de ondas gravitacionais.
-{{< figure src="/images/content_images/cs/gwpy-numpy-dep-graph.png" class="fig-center" alt="gwpy-numpy depgraph" caption="**Grafo de dependências mostrando como o pacote GwPy depended da NumPy**" >}}
+{{< figure src="/images/content_images/cs/gwpy-numpy-dep-graph.png" class="fig-center" alt="gráfico de dependências do gwpy com o NumPy em realce" caption="**Gráfico de dependências mostrando como o pacote GwPy depende do NumPy**" >}}
----
-{{< figure src="/images/content_images/cs/PyCBC-numpy-dep-graph.png" class="fig-center" alt="PyCBC-numpy depgraph" caption="**Grafo de dependências mostrando como o pacote PyCBC depended da NumPy**" >}}
+{{< figure src="/images/content_images/cs/PyCBC-numpy-dep-graph.png" class="fig-center" alt="gráfico de dependências do PyCBC com NumPy em realce" caption="**Gráfico de dependências mostrando como o pacote PyCBC depende do NumPy**" >}}
## Resumo
From f2befcd627a15f5d93a1d3678d55f81916078e39 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Mon, 19 Apr 2021 23:11:34 +0200
Subject: [PATCH 285/909] New translations cricket-analytics.md (Portuguese,
Brazilian)
---
content/pt/case-studies/cricket-analytics.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/content/pt/case-studies/cricket-analytics.md b/content/pt/case-studies/cricket-analytics.md
index c2fbcac9c8..216fcebd26 100644
--- a/content/pt/case-studies/cricket-analytics.md
+++ b/content/pt/case-studies/cricket-analytics.md
@@ -3,7 +3,7 @@ title: "Estudo de Caso: Análise de Críquete, a revolução!"
sidebar: false
---
-{{< figure src="/images/content_images/cs/ipl-stadium.png" caption="**IPLT20, o maior festival de Críquete da Índia**" alt="Copa e estádio da Indian Premier League Cricket" attr="*(Image credits: IPLT20 (cup and logo) & Akash Yadav (stadium))*" attrlink="https://unsplash.com/@aksh1802" >}}
+{{< figure src="/images/content_images/cs/ipl-stadium.png" caption="**IPLT20, o maior festival de Críquete da Índia**" alt="Copa e estádio da Indian Premier League Cricket" attr="*(Créditos de imagem: IPLT20 (cup and logo) & Akash Yadav (stadium))*" attrlink="https://unsplash.com/@aksh1802" >}}
Você não joga para a torcida, joga para o país.
@@ -49,7 +49,7 @@ Hoje, existem conjuntos ricos e quase infinitos de estatísticas e informações
Muito da tomada de decisões em críquete se baseia em questões como "com que frequência um batsman joga um certo tipo de lance se a recepção da bola for de um determinado tipo", ou "como um boleador muda a direção e alcance da sua jogada se o batsman responder de uma certa maneira". Esse tipo de consulta de análise preditiva requer a disponibilidade de conjuntos de dados altamente granulares e a capacidade de sintetizar dados e criar modelos generativos que sejam altamente precisos.
-## Papel da NumPy na Análise de Críquete
+## Papel do NumPy na Análise de Críquete
A análise de dados esportivos é um campo próspero. Muitos pesquisadores e empresas [usam NumPy](https://adtmag.com/blogs/dev-watch/2017/07/sports-analytics.aspx) e outros pacotes PyData como Scikit-learn, SciPy, Matplotlib, e Jupyter, além de usar as últimas técnicas de aprendizagem de máquina e IA. O NumPy foi usado para vários tipos de análise esportiva relacionada a críquete, como:
@@ -61,4 +61,4 @@ A análise de dados esportivos é um campo próspero. Muitos pesquisadores e emp
A análise de dados esportivos é revolucionária quando se trata de como os jogos profissionais são jogados, especialmente se consideramos como acontece a tomada de decisões estratégicas, que até pouco tempo era principalmente feita com base na "intuição" ou adesão a tradições passadas. O NumPy forma uma fundação sólida para um grande conjunto de pacotes Python que fornecem funções de alto nível relacionadas à análise de dados, aprendizagem de máquina e algoritmos de IA. Estes pacotes são amplamente implantados para se obter informações em tempo real que ajudam na tomada de decisão para resultados decisivos, tanto em campo como para se derivar inferências e orientar negócios em torno do jogo de críquete. Encontrar os parâmetros ocultos, padrões, e atributos que levam ao resultado de uma partida de críquete ajuda os envolvidos a tomar nota das percepções do jogo que estariam de outra forma ocultas nos números e estatísticas.
-{{< figure src="/images/content_images/cs/numpy_ca_benefits.png" class="fig-center" alt="Diagrama mostrando os benefícios de usar a NumPy para análise de críquete" caption="**Recursos principais da NumPy utilizados**" >}}
+{{< figure src="/images/content_images/cs/numpy_ca_benefits.png" class="fig-center" alt="Diagrama mostrando os benefícios de usar o NumPy para análise de críquete" caption="**Recursos principais do NumPy utilizados**" >}}
From 86f1e9650e2c088508fb125039d90816f6d5a155 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Mon, 19 Apr 2021 23:11:36 +0200
Subject: [PATCH 286/909] New translations deeplabcut-dnn.md (Portuguese,
Brazilian)
---
content/pt/case-studies/deeplabcut-dnn.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/content/pt/case-studies/deeplabcut-dnn.md b/content/pt/case-studies/deeplabcut-dnn.md
index 1dd02b9f92..6b66188c5b 100644
--- a/content/pt/case-studies/deeplabcut-dnn.md
+++ b/content/pt/case-studies/deeplabcut-dnn.md
@@ -3,7 +3,7 @@ title: "Estudo de Caso: Estimativa de Pose 3D com DeepLabCut"
sidebar: false
---
-{{< figure src="/images/content_images/cs/mice-hand.gif" class="fig-center" caption="**Análise de movimentos de mãos de camundongos usando DeepLapCut**" alt="micehandanim" attr="*(Fonte: www.deeplabcut.org )*" attrlink="http://www.mousemotorlab.org/deeplabcut">}}
+{{< figure src="/images/content_images/cs/mice-hand.gif" class="fig-center" caption="**Análise de movimentos de mãos de camundongos usando DeepLapCut**" alt="animação de mãos de camundongos" attr="*(Fonte: www.deeplabcut.org )*" attrlink="http://www.mousemotorlab.org/deeplabcut">}}
Software de código aberto está acelerando a Biomedicina. DeepLabCut permite a análise automática de vídeos de comportamento animal usando Deep Learning.
@@ -16,7 +16,7 @@ sidebar: false
Várias áreas de pesquisa, incluindo a neurociência, a medicina e a biomecânica, utilizam dados de rastreamento da movimentação de animais. A DeepLabCut ajuda a compreender o que os seres humanos e outros animais estão fazendo, analisando ações que foram registradas em vídeo. Ao usar automação para tarefas trabalhosas de monitoramento e marcação, junto com análise de dados baseada em redes neurais profundas, a DeepLabCut garante que estudos científicos envolvendo a observação de animais como primatas, camundongos, peixes, moscas etc. sejam mais rápidos e precisos.
-{{< figure src="/images/content_images/cs/race-horse.gif" class="fig-center" caption="**Pontos coloridos rastreiam as posições das partes do corpo de um cavalo de corrida**" alt="horserideranim" attr="*(Fonte: Mackenzie Mathis)*">}}
+{{< figure src="/images/content_images/cs/race-horse.gif" class="fig-center" caption="**Pontos coloridos rastreiam as posições das partes do corpo de um cavalo de corrida**" alt="animação de um jóquei em um cavalo correndo" attr="*(Fonte: Mackenzie Mathis)*">}}
O rastreamento não invasivo dos animais pela DeepLabCut através da extração de poses é crucial para pesquisas científicas em domínios como a biomecânica, genética, etologia e neurociência. Medir as poses dos animais de maneira não invasiva através de vídeo - sem marcadores - com fundos dinâmicos é computacionalmente desafiador, tanto tecnicamente quanto em termos de recursos e dados de treinamento necessários.
@@ -45,7 +45,7 @@ Recentemente, foi introduzido o [modelo DeepLabCut zoo](http://www.mousemotorlab
- código para inferência em larga escala em vídeos
- inferências de desenho usando ferramentas integradas de visualização
-{{< figure src="/images/content_images/cs/deeplabcut-toolkit-steps.png" class="csfigcaption" caption="**Passos na estimação de poses com DeepLabCut**" alt="dlcsteps" align="middle" attr="(Fonte: DeepLabCut)" attrlink="https://twitter.com/DeepLabCut/status/1198046918284210176/photo/1" >}}
+{{< figure src="/images/content_images/cs/deeplabcut-toolkit-steps.png" class="csfigcaption" caption="**Passos na estimação de poses com DeepLabCut**" alt="diagrama de passos na estimação de poses" align="middle" attr="(Fonte: DeepLabCut)" attrlink="https://twitter.com/DeepLabCut/status/1198046918284210176/photo/1" >}}
### Desafios
@@ -61,7 +61,7 @@ Recentemente, foi introduzido o [modelo DeepLabCut zoo](http://www.mousemotorlab
Por último, mas não menos importante, manipulação de matrizes - processar grandes conjuntos de matrizes correspondentes a várias imagens, tensores alvo e pontos-chave é bastante desafiador.
-{{< figure src="/images/content_images/cs/pose-estimation.png" class="csfigcaption" caption="**Estimação de poses e complexidade**" alt="challengesfig" align="middle" attr="(Fonte: Mackenzie Mathis)" attrlink="https://www.biorxiv.org/content/10.1101/476531v1.full.pdf" >}}
+{{< figure src="/images/content_images/cs/pose-estimation.png" class="csfigcaption" caption="**Estimação de poses e complexidade**" alt="6 imagens com diferentes exemplos de captura de movimento" align="middle" attr="(Fonte: Mackenzie Mathis)" attrlink="https://www.biorxiv.org/content/10.1101/476531v1.full.pdf" >}}
## O papel da NumPy nos desafios da estimação de poses
From 9674b5373ee3ebf565108bdfbb4d8899ac024ba3 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Mon, 19 Apr 2021 23:11:37 +0200
Subject: [PATCH 287/909] New translations gw-discov.md (Portuguese, Brazilian)
---
content/pt/case-studies/gw-discov.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/content/pt/case-studies/gw-discov.md b/content/pt/case-studies/gw-discov.md
index 7b55f4a3ef..f64b463d0f 100644
--- a/content/pt/case-studies/gw-discov.md
+++ b/content/pt/case-studies/gw-discov.md
@@ -29,7 +29,7 @@ O [Observatório Interferômetro Laser de Ondas Gravitacionais (LIGO)](https://w
* **Computação**
- As ondas gravitacionais são difíceis de detectar pois produzem um efeito muito pequeno e têm uma pequena interação com a matéria. Processar e analisar todos os dados do LIGO requer uma vasta infraestrutura de computação. Depois de cuidar do ruído, que é bilhões de vezes maior que o sinal, ainda há equações de relatividade complexas e enormes quantidades de dados que apresentam um desafio computacional: [O(10^7) horas de CPU necessárias para análises de fusão binária](https://youtu.be/7mcHknWWzNI) espalhado em 6 clusters LIGO dedicados.
+ As ondas gravitacionais são difíceis de detectar pois produzem um efeito muito pequeno e têm uma pequena interação com a matéria. Processar e analisar todos os dados do LIGO requer uma vasta infraestrutura de computação. Depois de cuidar do ruído, que é bilhões de vezes maior que o sinal, ainda há equações de relatividade complexas e enormes quantidades de dados que apresentam um desafio computacional: [O(10^7) horas de CPU necessárias para análises de fusão binária](https://youtu.be/7mcHknWWzNI) espalhado em 6 clusters dedicados ao LIGO.
* **Sobrecarga de dados**
@@ -45,7 +45,7 @@ O [Observatório Interferômetro Laser de Ondas Gravitacionais (LIGO)](https://w
Ondas gravitacionais emitidas da fusão não podem ser calculadas usando nenhuma técnica a não ser relatividade numérica por força bruta usando supercomputadores. A quantidade de dados que o LIGO coleta é imensa tanto quanto os sinais de ondas gravitacionais são pequenos.
-NumPy, o pacote padrão de análise numérica para Python, foi parte do software utilizado para várias tarefas executadas durante o projeto de detecção de ondas gravitacionais no LIGO. A NumPy ajudou a resolver problemas matemáticos e de manipulação de dados complexos em alta velocidade. Aqui estão alguns exemplos:
+NumPy, o pacote padrão de análise numérica para Python, foi parte do software utilizado para várias tarefas executadas durante o projeto de detecção de ondas gravitacionais no LIGO. O NumPy ajudou a resolver problemas matemáticos e de manipulação de dados complexos em alta velocidade. Aqui estão alguns exemplos:
* [Processamento de sinais](https://www.uv.es/virgogroup/Denoising_ROF.html): Detecção de falhas, [Identificação de ruídos e caracterização de dados](https://ep2016.europython.eu/media/conference/slides/pyhton-in-gravitational-waves-research-communities.pdf) (NumPy, scikit-learn, scipy, matplotlib, pandas, PyCharm)
* Recuperação de dados: Decidir quais dados podem ser analisados, compreender se os dados contém um sinal - como uma agulha em um palheiro
@@ -64,6 +64,6 @@ NumPy, o pacote padrão de análise numérica para Python, foi parte do software
## Resumo
-A detecção de ondas gravitacionais permitiu que pesquisadores descobrissem fenômenos totalmente inesperados ao mesmo tempo em que proporcionaram novas idéias sobre muitos dos fenômenos mais profundos conhecidos na astrofísica. O processamento e a visualização de dados é um passo crucial que ajuda cientistas a obter informações coletadas de observações científicas e a entender os resultados. Os cálculos são complexos e não podem ser compreendidos por humanos a não ser que sejam visualizados usando simulações de computador que são alimentadas com dados e análises reais observados. A NumPy, junto com outras bibliotecas Python, como matplotlib, pandas, e scikit-learn [permitem que pesquisadores](https://www.gw-openscience.org/events/GW150914/) respondam perguntas complexas e descubram novos horizontes em nossa compreensão do universo.
+A detecção de ondas gravitacionais permitiu que pesquisadores descobrissem fenômenos totalmente inesperados ao mesmo tempo em que proporcionaram novas idéias sobre muitos dos fenômenos mais profundos conhecidos na astrofísica. O processamento e a visualização de dados é um passo crucial que ajuda cientistas a obter informações coletadas de observações científicas e a entender os resultados. Os cálculos são complexos e não podem ser compreendidos por humanos a não ser que sejam visualizados usando simulações de computador que são alimentadas com dados e análises reais observados. O NumPy, junto com outras bibliotecas Python, como matplotlib, pandas, e scikit-learn [permitem que pesquisadores](https://www.gw-openscience.org/events/GW150914/) respondam perguntas complexas e descubram novos horizontes em nossa compreensão do universo.
-{{< figure src="/images/content_images/cs/numpy_gw_benefits.png" class="fig-center" alt="numpy benefits" caption="**Recursos chave da NumPy utilizados**" >}}
+{{< figure src="/images/content_images/cs/numpy_gw_benefits.png" class="fig-center" alt="funcionalidades do numpy" caption="**Recursos chave do NumPy utilizados**" >}}
From c1fd1765ee212d8a22efbebe3ca45fa60e8376c1 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Tue, 20 Apr 2021 00:08:34 +0200
Subject: [PATCH 288/909] New translations deeplabcut-dnn.md (Portuguese,
Brazilian)
---
content/pt/case-studies/deeplabcut-dnn.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/pt/case-studies/deeplabcut-dnn.md b/content/pt/case-studies/deeplabcut-dnn.md
index 6b66188c5b..1c02e9b208 100644
--- a/content/pt/case-studies/deeplabcut-dnn.md
+++ b/content/pt/case-studies/deeplabcut-dnn.md
@@ -77,7 +77,7 @@ As seguintes características da NumPy desempenharam um papel fundamental para a
A DeepLabCut utiliza as capacidades de manipulação de arrays da NumPy em todo o fluxo de trabalho oferecido pelo seu conjunto de ferramentas. Em particular, a NumPy é usada para amostragem de quadros distintos para serem rotulados com anotações humanas e para escrita, edição e processamento de dados de anotação. Dentro da TensorFlow, a rede neural é treinada pela tecnologia DeepLabCut em milhares de iterações para prever as anotações verdadeiras dos quadros. Para este propósito, densidades de alvo (*scoremaps*) são criadas para colocar a estimativa como um problema de tradução de imagem a imagem. Para tornar as redes neurais robustas, o aumento de dados é empregado, o que requer o cálculo de scoremaps alvo sujeitos a várias etapas geométricas e de processamento de imagem. Para tornar o treinamento rápido, os recursos de vectorização da NumPy são utilizados. Para inferência, as previsões mais prováveis de scoremaps alvo precisam ser extraídas e é necessário "vincular previsões para montar animais individuais" de maneira eficiente.
-{{< figure src="/images/content_images/cs/deeplabcut-workflow.png" class="fig-center" caption="**Fluxo de dados DeepLabCut**" alt="workflow" attr="*(Fonte: Mackenzie Mathis)*" attrlink="https://www.researchgate.net/figure/DeepLabCut-work-flow-The-diagram-delineates-the-work-flow-as-well-as-the-directory-and_fig1_329185962">}}
+{{< figure src="/images/content_images/cs/deeplabcut-workflow.png" class="fig-center" caption="**Fluxo de dados DeepLabCut**" alt="diagrama com o fluxo de dados do deeplabcut" attr="*(Fonte: Mackenzie Mathis)*" attrlink="https://www.researchgate.net/figure/DeepLabCut-work-flow-The-diagram-delineates-the-work-flow-as-well-as-the-directory-and_fig1_329185962">}}
## Resumo
From 6d8e65d81ac01107d7764ddb73cd6706802f0f1a Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Tue, 20 Apr 2021 21:02:28 +0200
Subject: [PATCH 289/909] New translations citing-numpy.md (Chinese Simplified)
---
content/zh/citing-numpy.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/content/zh/citing-numpy.md b/content/zh/citing-numpy.md
index cbfa873b9f..1731e941cf 100644
--- a/content/zh/citing-numpy.md
+++ b/content/zh/citing-numpy.md
@@ -12,14 +12,14 @@ _BibTeX 格式:_
```
@Article{ harris2020array,
title = {Array programming with {NumPy}},
- author = {Charles R. Harris and K. Jarrod Millman and St{'{e}}fan J.
+ author = {Charles R. Harris and K. Jarrod Millman and St{\'{e}}fan J.
van der Walt and Ralf Gommers and Pauli Virtanen and David
Cournapeau and Eric Wieser and Julian Taylor and Sebastian
Berg and Nathaniel J. Smith and Robert Kern and Matti Picus
and Stephan Hoyer and Marten H. van Kerkwijk and Matthew
- Brett and Allan Haldane and Jaime Fern{'{a}}ndez del
- R{'{\i}}o and Mark Wiebe and Pearu Peterson and Pierre
- G{'{e}}rard-Marchant and Kevin Sheppard and Tyler Reddy and
+ Brett and Allan Haldane and Jaime Fern{\'{a}}ndez del
+ R{\'{i}}o and Mark Wiebe and Pearu Peterson and Pierre
+ G{\'{e}}rard-Marchant and Kevin Sheppard and Tyler Reddy and
Warren Weckesser and Hameer Abbasi and Christoph Gohlke and
Travis E. Oliphant},
year = {2020},
From 39da0fbdfed56eedac9d47888afd00957a592d9a Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Tue, 20 Apr 2021 21:02:50 +0200
Subject: [PATCH 290/909] New translations citing-numpy.md (Korean)
---
content/ko/citing-numpy.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/content/ko/citing-numpy.md b/content/ko/citing-numpy.md
index cf20ae59cf..9aa943e53e 100644
--- a/content/ko/citing-numpy.md
+++ b/content/ko/citing-numpy.md
@@ -12,14 +12,14 @@ _In BibTeX format:_
```
@Article{ harris2020array,
title = {Array programming with {NumPy}},
- author = {Charles R. Harris and K. Jarrod Millman and St{'{e}}fan J.
+ author = {Charles R. Harris and K. Jarrod Millman and St{\'{e}}fan J.
van der Walt and Ralf Gommers and Pauli Virtanen and David
Cournapeau and Eric Wieser and Julian Taylor and Sebastian
Berg and Nathaniel J. Smith and Robert Kern and Matti Picus
and Stephan Hoyer and Marten H. van Kerkwijk and Matthew
- Brett and Allan Haldane and Jaime Fern{'{a}}ndez del
- R{'{\i}}o and Mark Wiebe and Pearu Peterson and Pierre
- G{'{e}}rard-Marchant and Kevin Sheppard and Tyler Reddy and
+ Brett and Allan Haldane and Jaime Fern{\'{a}}ndez del
+ R{\'{i}}o and Mark Wiebe and Pearu Peterson and Pierre
+ G{\'{e}}rard-Marchant and Kevin Sheppard and Tyler Reddy and
Warren Weckesser and Hameer Abbasi and Christoph Gohlke and
Travis E. Oliphant},
year = {2020},
From f78b68211cb326e0eda005ff0da15764f801e6c5 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Tue, 20 Apr 2021 21:03:10 +0200
Subject: [PATCH 291/909] New translations citing-numpy.md (Portuguese,
Brazilian)
---
content/pt/citing-numpy.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/content/pt/citing-numpy.md b/content/pt/citing-numpy.md
index d390e925e9..1dc8a215f0 100644
--- a/content/pt/citing-numpy.md
+++ b/content/pt/citing-numpy.md
@@ -12,14 +12,14 @@ _Em formato BibTeX:_
```
@Article{ harris2020array,
title = {Array programming with {NumPy}},
- author = {Charles R. Harris and K. Jarrod Millman and St{'{e}}fan J.
+ author = {Charles R. Harris and K. Jarrod Millman and St{\'{e}}fan J.
van der Walt and Ralf Gommers and Pauli Virtanen and David
Cournapeau and Eric Wieser and Julian Taylor and Sebastian
Berg and Nathaniel J. Smith and Robert Kern and Matti Picus
and Stephan Hoyer and Marten H. van Kerkwijk and Matthew
- Brett and Allan Haldane and Jaime Fern{'{a}}ndez del
- R{'{\i}}o and Mark Wiebe and Pearu Peterson and Pierre
- G{'{e}}rard-Marchant and Kevin Sheppard and Tyler Reddy and
+ Brett and Allan Haldane and Jaime Fern{\'{a}}ndez del
+ R{\'{i}}o and Mark Wiebe and Pearu Peterson and Pierre
+ G{\'{e}}rard-Marchant and Kevin Sheppard and Tyler Reddy and
Warren Weckesser and Hameer Abbasi and Christoph Gohlke and
Travis E. Oliphant},
year = {2020},
From bc1ca750dd9511739c6e328f025f41e22ee4213f Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Tue, 20 Apr 2021 21:03:42 +0200
Subject: [PATCH 292/909] New translations citing-numpy.md (Spanish)
---
content/es/citing-numpy.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/content/es/citing-numpy.md b/content/es/citing-numpy.md
index cf20ae59cf..9aa943e53e 100644
--- a/content/es/citing-numpy.md
+++ b/content/es/citing-numpy.md
@@ -12,14 +12,14 @@ _In BibTeX format:_
```
@Article{ harris2020array,
title = {Array programming with {NumPy}},
- author = {Charles R. Harris and K. Jarrod Millman and St{'{e}}fan J.
+ author = {Charles R. Harris and K. Jarrod Millman and St{\'{e}}fan J.
van der Walt and Ralf Gommers and Pauli Virtanen and David
Cournapeau and Eric Wieser and Julian Taylor and Sebastian
Berg and Nathaniel J. Smith and Robert Kern and Matti Picus
and Stephan Hoyer and Marten H. van Kerkwijk and Matthew
- Brett and Allan Haldane and Jaime Fern{'{a}}ndez del
- R{'{\i}}o and Mark Wiebe and Pearu Peterson and Pierre
- G{'{e}}rard-Marchant and Kevin Sheppard and Tyler Reddy and
+ Brett and Allan Haldane and Jaime Fern{\'{a}}ndez del
+ R{\'{i}}o and Mark Wiebe and Pearu Peterson and Pierre
+ G{\'{e}}rard-Marchant and Kevin Sheppard and Tyler Reddy and
Warren Weckesser and Hameer Abbasi and Christoph Gohlke and
Travis E. Oliphant},
year = {2020},
From b9061b73f37ed61acde76cf367456f4292810b44 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Tue, 20 Apr 2021 21:03:50 +0200
Subject: [PATCH 293/909] New translations citing-numpy.md (Arabic)
---
content/ar/citing-numpy.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/content/ar/citing-numpy.md b/content/ar/citing-numpy.md
index cf20ae59cf..9aa943e53e 100644
--- a/content/ar/citing-numpy.md
+++ b/content/ar/citing-numpy.md
@@ -12,14 +12,14 @@ _In BibTeX format:_
```
@Article{ harris2020array,
title = {Array programming with {NumPy}},
- author = {Charles R. Harris and K. Jarrod Millman and St{'{e}}fan J.
+ author = {Charles R. Harris and K. Jarrod Millman and St{\'{e}}fan J.
van der Walt and Ralf Gommers and Pauli Virtanen and David
Cournapeau and Eric Wieser and Julian Taylor and Sebastian
Berg and Nathaniel J. Smith and Robert Kern and Matti Picus
and Stephan Hoyer and Marten H. van Kerkwijk and Matthew
- Brett and Allan Haldane and Jaime Fern{'{a}}ndez del
- R{'{\i}}o and Mark Wiebe and Pearu Peterson and Pierre
- G{'{e}}rard-Marchant and Kevin Sheppard and Tyler Reddy and
+ Brett and Allan Haldane and Jaime Fern{\'{a}}ndez del
+ R{\'{i}}o and Mark Wiebe and Pearu Peterson and Pierre
+ G{\'{e}}rard-Marchant and Kevin Sheppard and Tyler Reddy and
Warren Weckesser and Hameer Abbasi and Christoph Gohlke and
Travis E. Oliphant},
year = {2020},
From aa52bef8fd81d80762e05edd9430a825a5b43bc9 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Tue, 20 Apr 2021 21:04:03 +0200
Subject: [PATCH 294/909] New translations citing-numpy.md (Japanese)
---
content/ja/citing-numpy.md | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/content/ja/citing-numpy.md b/content/ja/citing-numpy.md
index 587890c75d..752d29d800 100644
--- a/content/ja/citing-numpy.md
+++ b/content/ja/citing-numpy.md
@@ -10,16 +10,16 @@ sidebar: false
_BibTeX形式:_
```
-@Article{ harris2020array,
- title = {Array programming with {NumPy}},
- author = {Charles R. Harris and K. Jarrod Millman and St{'{e}}fan J.
+@Article{ harris2020array,
+ title = {Array programming with {NumPy}},
+ author = {Charles R. Harris and K. Jarrod Millman and St{\'{e}}fan J.
van der Walt and Ralf Gommers and Pauli Virtanen and David
Cournapeau and Eric Wieser and Julian Taylor and Sebastian
Berg and Nathaniel J. Smith and Robert Kern and Matti Picus
and Stephan Hoyer and Marten H. van Kerkwijk and Matthew
- Brett and Allan Haldane and Jaime Fern{'{a}}ndez del
- R{'{\i}}o and Mark Wiebe and Pearu Peterson and Pierre
- G{'{e}}rard-Marchant and Kevin Sheppard and Tyler Reddy and
+ Brett and Allan Haldane and Jaime Fern{\'{a}}ndez del
+ R{\'{i}}o and Mark Wiebe and Pearu Peterson and Pierre
+ G{\'{e}}rard-Marchant and Kevin Sheppard and Tyler Reddy and
Warren Weckesser and Hameer Abbasi and Christoph Gohlke and
Travis E. Oliphant},
year = {2020},
From fa9a87b1a76f85f215b3deb5ece92d5b7f240a71 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Wed, 21 Apr 2021 00:45:32 +0200
Subject: [PATCH 295/909] New translations 404.md (Spanish)
---
content/es/404.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/es/404.md b/content/es/404.md
index e0e7272719..b38d73b758 100644
--- a/content/es/404.md
+++ b/content/es/404.md
@@ -3,6 +3,6 @@ title: 404
sidebar: false
---
-¡Ups! Has llegado a un callejón sin salida.
+¡Oh, oh! Has llegado a un callejón sin salida.
Si crees que algo debería estar aquí, puedes [reportar este problema](https://github.com/numpy/numpy.org/issues) en GitHub.
From 7c4b1665cbb4777de28cbc3a2e87af8a6804811c Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Wed, 21 Apr 2021 00:45:33 +0200
Subject: [PATCH 296/909] New translations about.md (Spanish)
---
content/es/about.md | 50 ++++++++++++++++++++++-----------------------
1 file changed, 25 insertions(+), 25 deletions(-)
diff --git a/content/es/about.md b/content/es/about.md
index 1de6728185..34642cf247 100644
--- a/content/es/about.md
+++ b/content/es/about.md
@@ -1,18 +1,18 @@
---
-title: About Us
+title: Quiénes somos
sidebar: false
---
-_Some information about the NumPy project and community_
+_Información sobre el proyecto y la comunidad NumPy_
-NumPy is an open source project aiming to enable numerical computing with Python. It was created in 2005, building on the early work of the Numeric and Numarray libraries. NumPy will always be 100% open source software, free for all to use and released under the liberal terms of the [modified BSD license](https://github.com/numpy/numpy/blob/master/LICENSE.txt).
+NumPy es un proyecto de código abierto cuyo objetivo es facilitar la computación numérica con Python. Se creó en el 2005, a partir de los primeros trabajos de las bibliotecas Numeric y Numarray. NumPy siempre será un software 100% de código abierto, de uso libre para todos y liberado bajo los términos liberales de la [licencia BSD modificada](https://github.com/numpy/numpy/blob/master/LICENSE.txt).
-NumPy is developed in the open on GitHub, through the consensus of the NumPy and wider scientific Python community. For more information on our governance approach, please see our [Governance Document](https://www.numpy.org/devdocs/dev/governance/index.html).
+NumPy se desarrolla de forma abierta en GitHub, mediante el consenso de la comunidad de NumPy y de la comunidad científica de Python en general. Para más información sobre nuestro enfoque de gobernanza, consulta nuestro [Documento de Gobernanza](https://www.numpy.org/devdocs/dev/governance/index.html).
-## Steering Council
+## Consejo Directivo
-The role of the NumPy Steering Council is to ensure, through working with and serving the broader NumPy community, the long-term well-being of the project, both technically and as a community. The NumPy Steering Council currently consists of the following members (in alphabetical order):
+El papel del Consejo Directivo de NumPy es garantizar, a través del trabajo con la comunidad NumPy en general y al servicio de la misma, el bienestar a largo plazo del proyecto, tanto desde el punto de vista técnico como de la comunidad. El Consejo Directivo de NumPy está formado actualmente por los siguientes miembros (en orden alfabético):
- Sebastian Berg
- Ralf Gommers
@@ -24,9 +24,9 @@ The role of the NumPy Steering Council is to ensure, through working with and se
- Stéfan van der Walt
- Eric Wieser
-Emeritus:
+Eméritos:
-- Travis Oliphant (project founder, 2005-2012)
+- Travis Oliphant (fundador del proyecto, 2005-2012)
- Alex Griffing (2015-2017)
- Marten van Kerkwijk (2017-2019)
- Allan Haldane (2015-2021)
@@ -36,37 +36,37 @@ Emeritus:
- Jaime Fernández del Río (2014-2021)
-## Teams
+## Equipos
-The NumPy project is growing; we have teams for
+El proyecto NumPy está creciendo; tenemos equipos para
-- code
-- documentation
-- website
-- triage
-- funding and grants
+- código
+- documentación
+- sitio web
+- triaje
+- financiación y subvenciones
-See the [Team](/gallery/team.html) page for individual team members.
+Visita la página [Equipo](/gallery/team.html) para conocer a los miembros de cada equipo.
-## Sponsors
+## Patrocinadores
-NumPy receives direct funding from the following sources:
+NumPy recibe financiación directa de las siguientes fuentes:
{{< sponsors >}}
-## Institutional Partners
+## Socios institucionales
-Institutional Partners are organizations that support the project by employing people that contribute to NumPy as part of their job. Current Institutional Partners include:
+Los socios institucionales son organizaciones que apoyan el proyecto empleando a personas que contribuyen a NumPy como parte de su trabajo. Entre los actuales socios institucionales se encuentran:
{{< partners >}}
-## Donate
+## Donar
-If you have found NumPy useful in your work, research, or company, please consider a donation to the project commensurate with your resources. Any amount helps! All donations will be used strictly to fund the development of NumPy’s open source software, documentation, and community.
+Si has encontrado NumPy útil en tu trabajo, investigación o empresa, por favor considera una donación al proyecto proporcional a tus recursos. ¡Cualquier cantidad ayuda! Todas las donaciones se utilizarán estrictamente para financiar el desarrollo del software de código abierto, la documentación y la comunidad de NumPy.
-NumPy is a Sponsored Project of NumFOCUS, a 501(c)(3) nonprofit charity in the United States. NumFOCUS provides NumPy with fiscal, legal, and administrative support to help ensure the health and sustainability of the project. Visit [numfocus.org](https://numfocus.org) for more information.
+NumPy es un proyecto patrocinado por NumFOCUS, una organización benéfica sin fines de lucro 501(c)(3) de Estados Unidos. NumFOCUS proporciona a NumPy apoyo fiscal, legal y administrativo para ayudar a garantizar el bienestar y la sostenibilidad del proyecto. Visita [numfocus.org](https://numfocus.org) para más información.
-Donations to NumPy are managed by [NumFOCUS](https://numfocus.org). For donors in the United States, your gift is tax-deductible to the extent provided by law. As with any donation, you should consult with your tax advisor about your particular tax situation.
+Las donaciones a NumPy son gestionadas por [NumFOCUS](https://numfocus.org). Para los donantes de Estados Unidos, su donación es deducible de impuestos en la medida prevista por la ley. Al igual que con cualquier donación, debes consultar a tu asesor de impuestos sobre tu situación fiscal particular.
-NumPy's Steering Council will make the decisions on how to best use any funds received. Technical and infrastructure priorities are documented on the [NumPy Roadmap](https://www.numpy.org/neps/index.html#roadmap).
+El Consejo Directivo de NumPy tomará las decisiones sobre el mejor uso de los fondos recibidos. Las prioridades técnicas y de infraestructura están documentadas en la [Hoja de ruta de NumPy](https://www.numpy.org/neps/index.html#roadmap).
{{< numfocus >}}
From 12d3edd1c28ea491b9c3385fc2990f6cc19408f5 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Wed, 21 Apr 2021 00:45:34 +0200
Subject: [PATCH 297/909] New translations arraycomputing.md (Spanish)
---
content/es/arraycomputing.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/content/es/arraycomputing.md b/content/es/arraycomputing.md
index abd29d11c1..ffe0d578ba 100644
--- a/content/es/arraycomputing.md
+++ b/content/es/arraycomputing.md
@@ -1,11 +1,11 @@
---
-title: Array Computing
+title: Cómputo vectorial
sidebar: false
---
*Array computing is the foundation of statistical, mathematical, scientific computing in various contemporary data science and analytics applications such as data visualization, digital signal processing, image processing, bioinformatics, machine learning, AI, and several others.*
-Large scale data manipulation and transformation depends on efficient, high-performance array computing. The language of choice for data analytics, machine learning, and productive numerical computing is **Python.**
+La manipulación y transformación de datos a gran escala depende de una computación vectorial eficiente y de alto rendimiento. El lenguaje de elección para el análisis de datos, el aprendizaje automático y el cómputo numérico productivo es **Python.**
**Num**erical **Py**thon or NumPy is its de-facto standard Python programming language library that supports large, multi-dimensional arrays and matrices, and comes with a vast collection of high-level mathematical functions to operate on these arrays.
From e78e4bb7111bb2717a6196597d9c068222d5000a Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Wed, 21 Apr 2021 01:44:15 +0200
Subject: [PATCH 298/909] New translations arraycomputing.md (Spanish)
---
content/es/arraycomputing.md | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/content/es/arraycomputing.md b/content/es/arraycomputing.md
index ffe0d578ba..11877b3847 100644
--- a/content/es/arraycomputing.md
+++ b/content/es/arraycomputing.md
@@ -3,19 +3,19 @@ title: Cómputo vectorial
sidebar: false
---
-*Array computing is the foundation of statistical, mathematical, scientific computing in various contemporary data science and analytics applications such as data visualization, digital signal processing, image processing, bioinformatics, machine learning, AI, and several others.*
+*El cómputo vectorial es la base del cómputo estadístico, matemático y científico en varias aplicaciones contemporáneas de ciencia de datos y análisis, como la visualización de datos, el procesamiento digital de señales, el procesamiento de imágenes, la bioinformática el aprendizaje automático, la IA y muchas otras.*
La manipulación y transformación de datos a gran escala depende de una computación vectorial eficiente y de alto rendimiento. El lenguaje de elección para el análisis de datos, el aprendizaje automático y el cómputo numérico productivo es **Python.**
-**Num**erical **Py**thon or NumPy is its de-facto standard Python programming language library that supports large, multi-dimensional arrays and matrices, and comes with a vast collection of high-level mathematical functions to operate on these arrays.
+**Num**erical **Py**thon o NumPy es la biblioteca estándar de facto del lenguaje de programación Python que soporta matrices y arreglos multidimensionales de gran tamaño, y viene con una amplia colección de funciones matemáticas de alto nivel para operar sobre estos arreglos.
-Since the launch of NumPy in 2006, Pandas appeared on the landscape in 2008, and it was not until a couple of years ago that several array computing libraries showed up in succession, crowding the array computing landscape. Many of these newer libraries mimic NumPy-like features and capabilities, and pack newer algorithms and features geared towards machine learning and artificial intelligence applications.
+Tras el lanzamiento de NumPy en 2006, Pandas apareció en el panorama en 2008, y no fue hasta hace un par de años que aparecieron sucesivamente varias bibliotecas de cómputo vectorial, poblando este escenario. Muchas de estas nuevas bibliotecas imitan las características y capacidades de NumPy, y contienen nuevos algoritmos y características orientadas a las aplicaciones de aprendizaje automático e inteligencia artificial.
+ title="Panorama del cómputo vectorial" />
-**Array computing** is based on **arrays** data structures. *Arrays* are used to organize vast amounts of data such that a related set of values can be easily sorted, searched, mathematically manipulated, and transformed easily and quickly.
+El **cómputo vectorial** está basado en los **arreglos** como estructura de datos. *Los arreglos* se utilizan para organizar grandes cantidades de datos de manera que un conjunto de valores relacionados pueda ordenarse, buscarse, manipularse matemáticamente y transformarse con facilidad y rapidez.
-Array computing is *unique* as it involves operating on the data array *at once*. What this means is that any array operation applies to an entire set of values in one shot. This vectorized approach provides speed and simplicity by enabling programmers to code and operate on aggregates of data, without having to use loops of individual scalar operations.
+La computación vectorial es *única* ya que implica operar sobre los arreglos de datos *de una vez*. Esto significa que cualquier operación de arreglos se aplica a un conjunto completo de valores de una sola vez. Este enfoque vectorial proporciona velocidad y simplicidad al permitir a los programadores codificar y trabajar sobre los datos agregados, sin tener que utilizar bucles de instrucciones escalares individuales.
From 409ce1b1b579f4da3a6d1860161c6d4503148e0f Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Wed, 21 Apr 2021 15:34:57 +0200
Subject: [PATCH 299/909] New translations citing-numpy.md (Portuguese,
Brazilian)
---
content/pt/citing-numpy.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/pt/citing-numpy.md b/content/pt/citing-numpy.md
index 1dc8a215f0..390d965d4c 100644
--- a/content/pt/citing-numpy.md
+++ b/content/pt/citing-numpy.md
@@ -1,5 +1,5 @@
---
-title: Citando a NumPy
+title: Citando o NumPy
sidebar: false
---
From b3447dea52f961604aa030b1184db1dbf7efb293 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 24 Apr 2021 05:06:09 +0200
Subject: [PATCH 300/909] New translations about.md (Arabic)
---
content/ar/about.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/content/ar/about.md b/content/ar/about.md
index 29d4a19ad9..b479f17bcc 100644
--- a/content/ar/about.md
+++ b/content/ar/about.md
@@ -12,7 +12,7 @@ _بعض المعلومات حول مشروع ومجتمع نمباي_
## المجلس التوجيهي
-The role of the NumPy Steering Council is to ensure, through working with and serving the broader NumPy community, the long-term well-being of the project, both technically and as a community. ويتألف المجلس التوجيهي المعني لنمباي حاليا علي الأعضاء التالية (بالترتيب الأبجدي):
+The role of the NumPy Steering Council is to ensure, through working with and serving the broader NumPy community, the long-term well-being of the project, both technically and as a community. ويتألف المجلس التوجيهي المعني بالمشروع حاليا من الأعضاء التالية (بالترتيب الأبجدي):
- Sebastian Berg
- Ralf Gommers
@@ -26,8 +26,8 @@ The role of the NumPy Steering Council is to ensure, through working with and se
Emeritus:
-- Travis Oliphant (project founder, 2005-2012)
-- Alex Griffing (2015-2017)
+- ترافيس أوليفانت (مؤسس المشروع، 2005-2012)
+- ألكس غريفينغ (2015-2017)
- Marten van Kerkwijk (2017-2019)
- Allan Haldane (2015-2021)
- Nathaniel Smith (2012-2021)
From e907d72665eaec65d47e06b70ab69d56f83e96da Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 24 Apr 2021 06:07:17 +0200
Subject: [PATCH 301/909] New translations about.md (Arabic)
---
content/ar/about.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/content/ar/about.md b/content/ar/about.md
index b479f17bcc..fce591bb90 100644
--- a/content/ar/about.md
+++ b/content/ar/about.md
@@ -28,11 +28,11 @@ Emeritus:
- ترافيس أوليفانت (مؤسس المشروع، 2005-2012)
- ألكس غريفينغ (2015-2017)
-- Marten van Kerkwijk (2017-2019)
+- مارتن فان كيركويك (2017-2019)
- Allan Haldane (2015-2021)
-- Nathaniel Smith (2012-2021)
-- Julian Taylor (2013-2021)
-- Pauli Virtanen (2008-2021)
+- ناثانييل سميث (2012-2021)
+- جوليان تايلور (2013-2021)
+- باولي فيرتانين (2008-2021)
- Jaime Fernández del Río (2014-2021)
From 8135c447b27e878999bee02cceda4ce97d8ca076 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 24 Apr 2021 13:19:29 +0200
Subject: [PATCH 302/909] New translations learn.md (Chinese Simplified)
---
content/zh/learn.md | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/content/zh/learn.md b/content/zh/learn.md
index ea35371573..0ad006d0f7 100644
--- a/content/zh/learn.md
+++ b/content/zh/learn.md
@@ -5,9 +5,14 @@ sidebar: false
For the **official NumPy documentation** visit [numpy.org/doc/stable](https://numpy.org/doc/stable).
-Below is a curated collection of external resources. To contribute, see the [end of this page](#add-to-this-list).
+## NumPy Tutorials
+
+You can find a set of tutorials and educational materials by the NumPy community at [NumPy Tutorials](https://numpy.org/numpy-tutorials). The goal of this page is to provide high-quality resources by the NumPy project, both for self-learning and for teaching classes with, in the format of Jupyter Notebooks. If you’re interested in adding your own content, check the [numpy-tutorials repository on GitHub](https://github.com/numpy/numpy-tutorials).
+
***
+Below is a curated collection of external resources. To contribute, see the [end of this page](#add-to-this-list).
+
## Beginners
There's a ton of information about NumPy out there. If you are new, we'd strongly recommend these:
@@ -60,7 +65,7 @@ Try these advanced resources for a better understanding of NumPy concepts like a
**Videos**
-* [Advanced NumPy - broadcasting rules, strides, and advanced indexing](https://www.youtube.com/watch?v=cYugp9IN1-Q) *by Juan Nunuz-Iglesias*
+* [Advanced NumPy - broadcasting rules, strides, and advanced indexing](https://www.youtube.com/watch?v=cYugp9IN1-Q) *by Juan Nunez-Iglesias*
* [Advanced Indexing Operations in NumPy Arrays](https://www.youtube.com/watch?v=2WTDrSkQBng) *by Amuls Academy*
***
From 80537599aae96ef8641b4deb6d5721509251566d Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 24 Apr 2021 13:19:47 +0200
Subject: [PATCH 303/909] New translations learn.md (Korean)
---
content/ko/learn.md | 33 +++++++++++++++++++--------------
1 file changed, 19 insertions(+), 14 deletions(-)
diff --git a/content/ko/learn.md b/content/ko/learn.md
index 2441c963be..0ad006d0f7 100644
--- a/content/ko/learn.md
+++ b/content/ko/learn.md
@@ -5,14 +5,19 @@ sidebar: false
For the **official NumPy documentation** visit [numpy.org/doc/stable](https://numpy.org/doc/stable).
-아래는 선별된 외부 자료들의 모음입니다. 이곳에 기여하고 싶다면, [이 페이지의 끝](#add-to-this-list)을 참조하세요.
+## NumPy Tutorials
+
+You can find a set of tutorials and educational materials by the NumPy community at [NumPy Tutorials](https://numpy.org/numpy-tutorials). The goal of this page is to provide high-quality resources by the NumPy project, both for self-learning and for teaching classes with, in the format of Jupyter Notebooks. If you’re interested in adding your own content, check the [numpy-tutorials repository on GitHub](https://github.com/numpy/numpy-tutorials).
+
***
+Below is a curated collection of external resources. To contribute, see the [end of this page](#add-to-this-list).
+
## Beginners
-여기에 NumPy에 대한 많은 자료가 있습니다. NumPy가 처음이라면 이 자료들을 강력하게 권장합니다.
+There's a ton of information about NumPy out there. If you are new, we'd strongly recommend these:
- **튜토리얼**
+ **Tutorials**
* [NumPy Quickstart Tutorial](https://numpy.org/devdocs/user/quickstart.html)
* [NumPy Illustrated: The Visual Guide to NumPy *by Lev Maximov*](https://betterprogramming.pub/3b1d4976de1d?sk=57b908a77aa44075a49293fa1631dd9b)
@@ -25,7 +30,7 @@ For the **official NumPy documentation** visit [numpy.org/doc/stable](https://nu
* [Stanford CS231 *by Justin Johnson*](http://cs231n.github.io/python-numpy-tutorial/)
* [NumPy User Guide](https://numpy.org/devdocs)
- **도서**
+ **Books**
* [Guide to NumPy *by Travis E. Oliphant*](http://web.mit.edu/dvp/Public/numpybook.pdf) This is a free version 1 from 2006. For the latest copy (2015) see [here](https://www.barnesandnoble.com/w/guide-to-numpy-travis-e-oliphant-phd/1122853007).
* [From Python to NumPy *by Nicolas P. Rougier*](https://www.labri.fr/perso/nrougier/from-python-to-numpy/)
@@ -33,7 +38,7 @@ For the **official NumPy documentation** visit [numpy.org/doc/stable](https://nu
You may also want to check out the [Goodreads list](https://www.goodreads.com/shelf/show/python-scipy) on the subject of "Python+SciPy." Most books there are about the "SciPy ecosystem," which has NumPy at its core.
- **영상**
+ **Videos**
* [Introduction to Numerical Computing with NumPy](http://youtu.be/ZB7BZMhfPgk) *by Alex Chabot-Leclerc*
@@ -41,9 +46,9 @@ You may also want to check out the [Goodreads list](https://www.goodreads.com/sh
## Advanced
-Indexing, Splitting, Stacking, 선형대수 등과 같은 NumPy의 개념을 더 잘 이해하러면 이 고급 자료들을 참조 해보세요.
+Try these advanced resources for a better understanding of NumPy concepts like advanced indexing, splitting, stacking, linear algebra, and more.
- **튜토리얼**
+ **Tutorials**
* [100 NumPy Exercises](http://www.labri.fr/perso/nrougier/teaching/numpy.100/index.html) *by Nicolas P. Rougier*
* [An Introduction to NumPy and Scipy](https://engineering.ucsb.edu/~shell/che210d/numpy.pdf) *by M. Scott Shell*
@@ -52,15 +57,15 @@ Indexing, Splitting, Stacking, 선형대수 등과 같은 NumPy의 개념을 더
* [Advanced Indexing](https://www.tutorialspoint.com/numpy/numpy_advanced_indexing.htm)
* [Machine Learning and Data Analytics with NumPy](https://www.machinelearningplus.com/python/numpy-tutorial-python-part2/)
- **도서**
+ **Books**
* [Python Data Science Handbook](https://www.amazon.com/Python-Data-Science-Handbook-Essential/dp/1491912057) *by Jake Vanderplas*
* [Python for Data Analysis](https://www.amazon.com/Python-Data-Analysis-Wrangling-IPython/dp/1491957662) *by Wes McKinney*
* [Numerical Python: Scientific Computing and Data Science Applications with Numpy, SciPy, and Matplotlib](https://www.amazon.com/Numerical-Python-Scientific-Applications-Matplotlib/dp/1484242459) *by Robert Johansson*
- **영상**
+ **Videos**
-* [Advanced NumPy - broadcasting rules, strides, and advanced indexing](https://www.youtube.com/watch?v=cYugp9IN1-Q) *by Juan Nunuz-Iglesias*
+* [Advanced NumPy - broadcasting rules, strides, and advanced indexing](https://www.youtube.com/watch?v=cYugp9IN1-Q) *by Juan Nunez-Iglesias*
* [Advanced Indexing Operations in NumPy Arrays](https://www.youtube.com/watch?v=2WTDrSkQBng) *by Amuls Academy*
***
@@ -75,11 +80,11 @@ Indexing, Splitting, Stacking, 선형대수 등과 같은 NumPy의 개념을 더
***
-## NumPy 인용하기
+## Citing NumPy
-만약 당신의 연구에서 NumPy가 중요한 역할을 수행하였고 학술 간행물에서 출판하기 위해서는 [이 인용 정보](/citing-numpy)를 참조하세요.
+If NumPy has been significant in your research, and you would like to acknowledge the project in your academic publication, please see [this citation information](/citing-numpy).
-## 이 목록에 기여하기
+## Contribute to this list
-이 목록에 자료를 추가하려면 [Pull Request](https://github.com/numpy/numpy.org/blob/master/content/en/learn.md)를 통해서 제출하세요. 당신이 추천한 자료가 왜 이 페이지에 올라야하는지, 또한 어떤 사람들이 가장 좋아할지 말해주세요.
+To add to this collection, submit a recommendation [via a pull request](https://github.com/numpy/numpy.org/blob/master/content/en/learn.md). Say why your recommendation deserves mention on this page and also which audience would benefit most.
From 43218af5689292523c0fb662dcca4c46d02685c8 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 24 Apr 2021 13:20:06 +0200
Subject: [PATCH 304/909] New translations learn.md (Portuguese, Brazilian)
---
content/pt/learn.md | 41 +++++++++++++++++++++++------------------
1 file changed, 23 insertions(+), 18 deletions(-)
diff --git a/content/pt/learn.md b/content/pt/learn.md
index ee3d572e04..7f3d89944d 100644
--- a/content/pt/learn.md
+++ b/content/pt/learn.md
@@ -5,14 +5,19 @@ sidebar: false
Para a **documentação oficial do NumPy** visite [numpy.org/doc/stable](https://numpy.org/doc/stable).
-Abaixo está uma coleção de recursos externos selecionados. Para contribuir, veja o [fim desta página](#add-to-this-list).
+## NumPy Tutorials
+
+You can find a set of tutorials and educational materials by the NumPy community at [NumPy Tutorials](https://numpy.org/numpy-tutorials). The goal of this page is to provide high-quality resources by the NumPy project, both for self-learning and for teaching classes with, in the format of Jupyter Notebooks. If you’re interested in adding your own content, check the [numpy-tutorials repository on GitHub](https://github.com/numpy/numpy-tutorials).
+
***
-## Iniciantes
+Below is a curated collection of external resources. To contribute, see the [end of this page](#add-to-this-list).
+
+## Beginners
-Há uma tonelada de informações sobre o NumPy lá fora. Se você está começando, recomendamos fortemente estes:
+There's a ton of information about NumPy out there. If you are new, we'd strongly recommend these:
- **Tutoriais**
+ **Tutorials**
* [NumPy Quickstart Tutorial (Tutorial de Início Rápido)](https://numpy.org/devdocs/user/quickstart.html)
* [NumPy Illustrated: The Visual Guide to NumPy *by Lev Maximov*](https://betterprogramming.pub/3b1d4976de1d?sk=57b908a77aa44075a49293fa1631dd9b)
@@ -25,25 +30,25 @@ Há uma tonelada de informações sobre o NumPy lá fora. Se você está começa
* [Stanford CS231 *by Justin Johnson*](http://cs231n.github.io/python-numpy-tutorial/)
* [NumPy User Guide](https://numpy.org/devdocs)
- **Livros**
+ **Books**
* [Guide to NumPy *de Travis E. Oliphant*](http://web.mit.edu/dvp/Public/numpybook.pdf) Essa é uma versão free de 2006. Para a última versão (2015) veja [aqui](https://www.barnesandnoble.com/w/guide-to-numpy-travis-e-oliphant-phd/1122853007).
* [From Python to NumPy *por Nicolas P. Rougier*](https://www.labri.fr/perso/nrougier/from-python-to-numpy/)
* [Elegant SciPy](https://www.amazon.com/Elegant-SciPy-Art-Scientific-Python/dp/1491922877) *por Juan Nunez-Iglesias, Stefan van der Walt, e Harriet Dashnow*
-Você também pode querer conferir a [lista Goodreads](https://www.goodreads.com/shelf/show/python-scipy) sobre o tema "Python+SciPy. A maioria dos livros lá serão sobre o "ecossistema SciPy", que tem o NumPy em sua essência.
+You may also want to check out the [Goodreads list](https://www.goodreads.com/shelf/show/python-scipy) on the subject of "Python+SciPy." Most books there are about the "SciPy ecosystem," which has NumPy at its core.
- **Vídeos**
+ **Videos**
* [Introduction to Numerical Computing with NumPy](http://youtu.be/ZB7BZMhfPgk) *por Alex Chabot-Leclerc*
***
-## Avançado
+## Advanced
-Experimente esses recursos avançados para uma melhor compreensão dos conceitos da NumPy, como indexação avançada, splitting, stacking, álgebra linear e muito mais.
+Try these advanced resources for a better understanding of NumPy concepts like advanced indexing, splitting, stacking, linear algebra, and more.
- **Tutoriais**
+ **Tutorials**
* [100 NumPy Exercises](http://www.labri.fr/perso/nrougier/teaching/numpy.100/index.html) *por Nicolas P. Rougier*
* [An Introduction to NumPy and Scipy](https://engineering.ucsb.edu/~shell/che210d/numpy.pdf) *por M. Scott Shell*
@@ -52,20 +57,20 @@ Experimente esses recursos avançados para uma melhor compreensão dos conceitos
* [Advanced Indexing](https://www.tutorialspoint.com/numpy/numpy_advanced_indexing.htm)
* [Machine Learning and Data Analytics with NumPy](https://www.machinelearningplus.com/python/numpy-tutorial-python-part2/)
- **Livros**
+ **Books**
* [Python Data Science Handbook](https://www.amazon.com/Python-Data-Science-Handbook-Essential/dp/1491912057) *por Jake Vanderplas*
* [Python for Data Analysis](https://www.amazon.com/Python-Data-Analysis-Wrangling-IPython/dp/1491957662) *por Wes McKinney*
* [Numerical Python: Scientific Computing and Data Science Applications with Numpy, SciPy, and Matplotlib](https://www.amazon.com/Numerical-Python-Scientific-Applications-Matplotlib/dp/1484242459) *por Robert Johansson*
- **Vídeos**
+ **Videos**
-* [Advanced NumPy - broadcasting rules, strides, and advanced indexing](https://www.youtube.com/watch?v=cYugp9IN1-Q) *por Juan Nunuz-Iglesias*
+* [Advanced NumPy - broadcasting rules, strides, and advanced indexing](https://www.youtube.com/watch?v=cYugp9IN1-Q) *by Juan Nunez-Iglesias*
* [Advanced Indexing Operations in NumPy Arrays](https://www.youtube.com/watch?v=2WTDrSkQBng) *por Amuls Academy*
***
-## Palestras sobre NumPy
+## NumPy Talks
* [The Future of NumPy Indexing](https://www.youtube.com/watch?v=o0EacbIbf58) *por Jaime Fernández* (2016)
* [Evolution of Array Computing in Python](https://www.youtube.com/watch?v=HVLPJnvInzM&t=10s) *por Ralf Gommers* (2019)
@@ -75,11 +80,11 @@ Experimente esses recursos avançados para uma melhor compreensão dos conceitos
***
-## Citando a NumPy
+## Citing NumPy
-Se a NumPy é importante na sua pesquisa, e você gostaria de dar reconhecimento ao projeto na sua publicação acadêmica, por favor veja [estas informações sobre citações](/citing-numpy).
+If NumPy has been significant in your research, and you would like to acknowledge the project in your academic publication, please see [this citation information](/citing-numpy).
-## Contribua para esta lista
+## Contribute to this list
-Para adicionar a essa coleção, envie uma recomendação [através de um pull request](https://github.com/numpy/numpy.org/blob/master/content/en/learn.md). Diga por que sua recomendação merece ser mencionada nesta página e também qual o público que mais se beneficiaria.
+To add to this collection, submit a recommendation [via a pull request](https://github.com/numpy/numpy.org/blob/master/content/en/learn.md). Say why your recommendation deserves mention on this page and also which audience would benefit most.
From 272199be39c2aa2c930ed3d2dc18a8c3453efe02 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 24 Apr 2021 13:20:16 +0200
Subject: [PATCH 305/909] New translations learn.md (Japanese)
---
content/ja/learn.md | 41 +++++++++++++++++++++++------------------
1 file changed, 23 insertions(+), 18 deletions(-)
diff --git a/content/ja/learn.md b/content/ja/learn.md
index ccbc6bfdb1..5329bdf3fc 100644
--- a/content/ja/learn.md
+++ b/content/ja/learn.md
@@ -5,14 +5,19 @@ sidebar: false
**公式の Numpy ドキュメント** については [numpy.org/doc/stable](https://numpy.org/doc/stable) を参照してください。
-以下は、キュレーションされた外部リソースのリストです。 こちらのリストに貢献するには、 [このページの末尾](#add-to-this-list) を参照してください。
+## NumPy Tutorials
+
+You can find a set of tutorials and educational materials by the NumPy community at [NumPy Tutorials](https://numpy.org/numpy-tutorials). The goal of this page is to provide high-quality resources by the NumPy project, both for self-learning and for teaching classes with, in the format of Jupyter Notebooks. If you’re interested in adding your own content, check the [numpy-tutorials repository on GitHub](https://github.com/numpy/numpy-tutorials).
+
***
-## 初心者向け
+Below is a curated collection of external resources. To contribute, see the [end of this page](#add-to-this-list).
+
+## Beginners
-NumPyについての資料は多数存在しています。 初心者の方にはこちらの資料をお勧めします:
+There's a ton of information about NumPy out there. If you are new, we'd strongly recommend these:
- **チュートリアル**
+ **Tutorials**
* [NumPy Quickstart チュートリアル](https://numpy.org/devdocs/user/quickstart.html)
* [NumPy Illustrated: The Visual Guide to NumPy *by Lev Maximov*](https://betterprogramming.pub/3b1d4976de1d?sk=57b908a77aa44075a49293fa1631dd9b)
@@ -25,25 +30,25 @@ NumPyについての資料は多数存在しています。 初心者の方に
* [Stanford CS231 *by Justin Johnson*](http://cs231n.github.io/python-numpy-tutorial/)
* [NumPy User Guide](https://numpy.org/devdocs)
- **書籍**
+ **Books**
* [NumPガイド*by Travelis E. Oliphant*](http://web.mit.edu/dvp/Public/numpybook.pdf) これは2006年の無料版の初版です 最新版(2015年)については、こちら [を参照ください](https://www.barnesandnoble.com/w/guide-to-numpy-travis-e-oliphant-phd/1122853007).
* [PythonからNumPyまで*by Nicolas P. Rougier*](https://www.labri.fr/perso/nrougier/from-python-to-numpy/)
* [エレガントなSciPy](https://www.amazon.com/Elegant-SciPy-Art-Scientific-Python/dp/1491922877) *by Juan Nunez-Iglesias, Stefan van der Walt, and Harriet Dashnow*
-また、"Python+SciPy"を題材にした [おすすめリスト](https://www.goodreads.com/shelf/show/python-scipy) をもチェックしてみてください。 ほとんどの本にはNumPyを核とした「SciPyエコシステム」が説明されています。
+You may also want to check out the [Goodreads list](https://www.goodreads.com/shelf/show/python-scipy) on the subject of "Python+SciPy." Most books there are about the "SciPy ecosystem," which has NumPy at its core.
- **動画**
+ **Videos**
* [Numpy を使った数値計算入門](http://youtu.be/ZB7BZMhfPgk) *by Alex Chabot-Leclerc*
***
-## 上級者向け
+## Advanced
-より高度なインデックス作成、分割、スタック、線形代数など、Numpy の概念をより深く理解するためには、これらのリソースを試してみてください。
+Try these advanced resources for a better understanding of NumPy concepts like advanced indexing, splitting, stacking, linear algebra, and more.
- **チュートリアル**
+ **Tutorials**
* [NumPy 100演習](http://www.labri.fr/perso/nrougier/teaching/numpy.100/index.html) *Nicolas P. Rougier*
* [NumPyとSciPyイントロダクション](https://engineering.ucsb.edu/~shell/che210d/numpy.pdf) *by M. Scott Shell*
@@ -52,20 +57,20 @@ NumPyについての資料は多数存在しています。 初心者の方に
* [高度なインデックシング](https://www.tutorialspoint.com/numpy/numpy_advanced_indexing.htm)
* [NumPy による機械学習とデータ分析](https://www.machinelearningplus.com/python/numpy-tutorial-python-part2/)
- **書籍**
+ **Books**
* [Pythonデータサイエンスハンドブック](https://www.amazon.com/Python-Data-Science-Handbook-Essential/dp/1491912057) *by Jake Vanderplas*
* [Pythonデータ解析](https://www.amazon.com/Python-Data-Analysis-Wrangling-IPython/dp/1491957662) *by Wes McKinney*
* [数値解析Python: Numpy, SciPy, Matplotlibによる数値計算とデータサイエンスアプリケーション](https://www.amazon.com/Numerical-Python-Scientific-Applications-Matplotlib/dp/1484242459) *by Robert Johansson*
- **動画**
+ **Videos**
-* [アドバンスドNumPy -](https://www.youtube.com/watch?v=cYugp9IN1-Q) *ブロードキャストルール、ストライド、および高度なインデックシング* by Fan Nunuz-Iglesias
+* [Advanced NumPy - broadcasting rules, strides, and advanced indexing](https://www.youtube.com/watch?v=cYugp9IN1-Q) *by Juan Nunez-Iglesias*
* [NumPy配列における高度なインデクシング処理](https://www.youtube.com/watch?v=2WTDrSkQBng) *by Amuls Academy*
***
-## NumPyに関するトーク
+## NumPy Talks
* [Numpy Indexing の未来](https://www.youtube.com/watch?v=o0EacbIbf58) *by Jaime Fernadez* (2016)
* [Python における配列計算革命](https://www.youtube.com/watch?v=HVLPJnvInzM&t=10s) *by Ralf Gommers* (2019)
@@ -75,11 +80,11 @@ NumPyについての資料は多数存在しています。 初心者の方に
***
-## NumPy を引用する場合
+## Citing NumPy
-もし、あなたの研究においてNumpyが重要な役割を果たし、論文でこのプロジェクトについて言及したい場合は、こちらの[ページ](/citing-numpy)を参照して下さい。
+If NumPy has been significant in your research, and you would like to acknowledge the project in your academic publication, please see [this citation information](/citing-numpy).
-## このページへの貢献
+## Contribute to this list
-このページのリストに新しいリンクを追加するには、[プルリクエスト](https://github.com/numpy/numpy.org/blob/master/content/en/learn.md)を使って提案してみて下さい。 あなたが推薦する情報が、このページで紹介するに値する理由と、その情報によってどのような人が最も恩恵を受けるかを説明して下さい。
+To add to this collection, submit a recommendation [via a pull request](https://github.com/numpy/numpy.org/blob/master/content/en/learn.md). Say why your recommendation deserves mention on this page and also which audience would benefit most.
From d439c6f0fc84ba312dbee95d3ae9db0ef99063c0 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 24 Apr 2021 13:20:31 +0200
Subject: [PATCH 306/909] New translations learn.md (Spanish)
---
content/es/learn.md | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/content/es/learn.md b/content/es/learn.md
index ea35371573..0ad006d0f7 100644
--- a/content/es/learn.md
+++ b/content/es/learn.md
@@ -5,9 +5,14 @@ sidebar: false
For the **official NumPy documentation** visit [numpy.org/doc/stable](https://numpy.org/doc/stable).
-Below is a curated collection of external resources. To contribute, see the [end of this page](#add-to-this-list).
+## NumPy Tutorials
+
+You can find a set of tutorials and educational materials by the NumPy community at [NumPy Tutorials](https://numpy.org/numpy-tutorials). The goal of this page is to provide high-quality resources by the NumPy project, both for self-learning and for teaching classes with, in the format of Jupyter Notebooks. If you’re interested in adding your own content, check the [numpy-tutorials repository on GitHub](https://github.com/numpy/numpy-tutorials).
+
***
+Below is a curated collection of external resources. To contribute, see the [end of this page](#add-to-this-list).
+
## Beginners
There's a ton of information about NumPy out there. If you are new, we'd strongly recommend these:
@@ -60,7 +65,7 @@ Try these advanced resources for a better understanding of NumPy concepts like a
**Videos**
-* [Advanced NumPy - broadcasting rules, strides, and advanced indexing](https://www.youtube.com/watch?v=cYugp9IN1-Q) *by Juan Nunuz-Iglesias*
+* [Advanced NumPy - broadcasting rules, strides, and advanced indexing](https://www.youtube.com/watch?v=cYugp9IN1-Q) *by Juan Nunez-Iglesias*
* [Advanced Indexing Operations in NumPy Arrays](https://www.youtube.com/watch?v=2WTDrSkQBng) *by Amuls Academy*
***
From 31c75d6446d491761b633514f3426d95211f2c47 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 24 Apr 2021 13:20:41 +0200
Subject: [PATCH 307/909] New translations learn.md (Arabic)
---
content/ar/learn.md | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/content/ar/learn.md b/content/ar/learn.md
index ea35371573..0ad006d0f7 100644
--- a/content/ar/learn.md
+++ b/content/ar/learn.md
@@ -5,9 +5,14 @@ sidebar: false
For the **official NumPy documentation** visit [numpy.org/doc/stable](https://numpy.org/doc/stable).
-Below is a curated collection of external resources. To contribute, see the [end of this page](#add-to-this-list).
+## NumPy Tutorials
+
+You can find a set of tutorials and educational materials by the NumPy community at [NumPy Tutorials](https://numpy.org/numpy-tutorials). The goal of this page is to provide high-quality resources by the NumPy project, both for self-learning and for teaching classes with, in the format of Jupyter Notebooks. If you’re interested in adding your own content, check the [numpy-tutorials repository on GitHub](https://github.com/numpy/numpy-tutorials).
+
***
+Below is a curated collection of external resources. To contribute, see the [end of this page](#add-to-this-list).
+
## Beginners
There's a ton of information about NumPy out there. If you are new, we'd strongly recommend these:
@@ -60,7 +65,7 @@ Try these advanced resources for a better understanding of NumPy concepts like a
**Videos**
-* [Advanced NumPy - broadcasting rules, strides, and advanced indexing](https://www.youtube.com/watch?v=cYugp9IN1-Q) *by Juan Nunuz-Iglesias*
+* [Advanced NumPy - broadcasting rules, strides, and advanced indexing](https://www.youtube.com/watch?v=cYugp9IN1-Q) *by Juan Nunez-Iglesias*
* [Advanced Indexing Operations in NumPy Arrays](https://www.youtube.com/watch?v=2WTDrSkQBng) *by Amuls Academy*
***
From 618e01993d4ae1cb825d5109e6062bb239902108 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 24 Apr 2021 14:17:15 +0200
Subject: [PATCH 308/909] New translations about.md (Korean)
---
content/ko/about.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/ko/about.md b/content/ko/about.md
index 1cfe839c79..49d3142c71 100644
--- a/content/ko/about.md
+++ b/content/ko/about.md
@@ -5,7 +5,7 @@ sidebar: false
_NumPy 프로젝트와 커뮤니티에 대한 몇가지 정보_
-NumPy는 Python에서 Numerical Computing을 할 수 있도록 도와주는 오픈소스 프로젝트입니다. It was created in 2005, building on the early work of the Numeric and Numarray libraries. NumPy는 항상 100% 오픈소스 소프트웨어 일것이며, [수정된 BSD 라이센스](https://github.com/numpy/numpy/blob/master/LICENSE.txt)에 따라서 누구나 무료로 사용하고 배포할 수 있습니디.
+NumPy는 Python에서 Numerical Computing을 할 수 있도록 도와주는 오픈소스 프로젝트입니다. Numerical와 Numarray라는 라이브러리의 초기 작업을 기반으로 2005년에 만들어졌습니다. NumPy는 항상 100% 오픈소스 소프트웨어 일것이며, [수정된 BSD 라이센스](https://github.com/numpy/numpy/blob/master/LICENSE.txt)에 따라서 누구나 무료로 사용하고 배포할 수 있습니디.
NumPy는 광범위한 Scientific Python 커뮤니티의 협의를 통해 GitHub에서 공개적으로 개발되었습니다. 우리의 거버넌스 접근 방식에 대한 더 자세한 내용은 [거버넌스 문서](https://www.numpy.org/devdocs/dev/governance/index.html)를 참조해 주세요.
From aa5fea0788ec80da3d4b4c3fcaa6e0cb5997bb16 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 24 Apr 2021 15:19:54 +0200
Subject: [PATCH 309/909] New translations arraycomputing.md (Korean)
---
content/ko/arraycomputing.md | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/content/ko/arraycomputing.md b/content/ko/arraycomputing.md
index abd29d11c1..2d8b5673ab 100644
--- a/content/ko/arraycomputing.md
+++ b/content/ko/arraycomputing.md
@@ -3,19 +3,19 @@ title: Array Computing
sidebar: false
---
-*Array computing is the foundation of statistical, mathematical, scientific computing in various contemporary data science and analytics applications such as data visualization, digital signal processing, image processing, bioinformatics, machine learning, AI, and several others.*
+*행렬 연산은 통계와 수학 뿐만 아니라 현대의 다양한 분야에 적용되는 데이터 사이언스와 데이터 시각화나 디지털 신호 처리, 영상 처리, 의생명 정보 공학, 기계학습, AI 등 다양한 분야에서 적용되는 데이터 분석 어플리케이션의 기반입니다.*
-Large scale data manipulation and transformation depends on efficient, high-performance array computing. The language of choice for data analytics, machine learning, and productive numerical computing is **Python.**
+대규모의 데이터의 조작과 연산은 고효율, 고성능의 행렬 연산에 달려있습니다. **Python**은 데이터 과학자, 머신 러닝 개발자, 그리고 효율적인 수치 계산을 필요로 하는 분야에서 선택되는 프로그래밍 언어입니다.
-**Num**erical **Py**thon or NumPy is its de-facto standard Python programming language library that supports large, multi-dimensional arrays and matrices, and comes with a vast collection of high-level mathematical functions to operate on these arrays.
+**Num**erical **Py**thon 또는 NumPy 는 파이썬의 표준라이브러리에는 포함되지 않지만, 큰 규모, 다 차원 행렬을 표현할 수 있고, 행렬 연산을 위한 고수준의 수학 함수들을 포함한 라이브러리입니다.
-Since the launch of NumPy in 2006, Pandas appeared on the landscape in 2008, and it was not until a couple of years ago that several array computing libraries showed up in succession, crowding the array computing landscape. Many of these newer libraries mimic NumPy-like features and capabilities, and pack newer algorithms and features geared towards machine learning and artificial intelligence applications.
+2006년에 NumPy가 출시된 이후로, 2008년에 이를 기반으로 Pandas가 나타났습니다. 그리고 몇년전까지도, 다양한 행렬 연산 라이브러리가 잇따라 나오며 행렬 연산 분야가 더욱 활발해 졌습니다. 최신의 라이브러리들중 대부분은 NumPy 같은 특징과 성능을 품고, 새로운 알고리즘이나 머신러닝이나 인공지능 어플리케이션을 위한 특화된 기능을 포함하고 있습니다.
-**Array computing** is based on **arrays** data structures. *Arrays* are used to organize vast amounts of data such that a related set of values can be easily sorted, searched, mathematically manipulated, and transformed easily and quickly.
+**행렬 연산**의 기반은 **배열**입니다. *배열*은 대규모의 데이터를 정렬, 검색, 수학 계산, 그리고 변형을 쉽고 빠르게 처리하는데 사용됩니다.
-Array computing is *unique* as it involves operating on the data array *at once*. What this means is that any array operation applies to an entire set of values in one shot. This vectorized approach provides speed and simplicity by enabling programmers to code and operate on aggregates of data, without having to use loops of individual scalar operations.
+행렬 연산은 *한번에 * 데이터 배열에 *모든 연산이* 계산 됩니다. 다시 말해서, 모든 행렬 연산은 전체 데이터에 한번에 적용됩니다. 이 벡터화 접근법은 행렬 연산을 위해 루프를 활용하여 개별적인 데이터에 접근하여 연산하는 코드를 작성하지 않고, 행렬에 바로 연산하는 코드를 작성하여, 개발자가 보다 개발 빠르고 간단하게 할수 있게 해줍니다.
From 24bcfa22300e9db5964bf7498526bf802b9ed537 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 24 Apr 2021 15:19:55 +0200
Subject: [PATCH 310/909] New translations install.md (Korean)
---
content/ko/install.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/content/ko/install.md b/content/ko/install.md
index 3ec0dc58b7..69bdbcb0a0 100644
--- a/content/ko/install.md
+++ b/content/ko/install.md
@@ -1,11 +1,11 @@
---
-title: Installing NumPy
+title: NumPy 설치
sidebar: false
---
-The only prerequisite for installing NumPy is Python itself. If you don't have Python yet and want the simplest way to get started, we recommend you use the [Anaconda Distribution](https://www.anaconda.com/distribution) - it includes Python, NumPy, and many other commonly used packages for scientific computing and data science.
+NumPy 설치를 위해서는 Python만 필요합니다. 만양 파이썬이 설치되지 않았다면, Python, NumPy, 그리고 다양한 데이터 과학과 과학 계산을 위해 일반적으로 많이 사용되는 패키지를 한번에 설치할 수 있는 [Anaconda Distribution](https://www.anaconda.com/distribution)을 활용하여 설치하는 것을 추천합니다.
-NumPy can be installed with `conda`, with `pip`, with a package manager on macOS and Linux, or [from source](https://numpy.org/devdocs/user/building.html). For more detailed instructions, consult our [Python and NumPy installation guide](#python-numpy-install-guide) below.
+NumPy 는 `conda`, `pip` 그리고 macOS과 Linux의 패키지 매니저를 사용하거나 또는 [소스](https://numpy.org/devdocs/user/building.html)로 부터 설치할 수 있습니다. For more detailed instructions, consult our [Python and NumPy installation guide](#python-numpy-install-guide) below.
**CONDA**
From a9b2390722d71636a79e19847943d721f9889a52 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 24 Apr 2021 15:19:56 +0200
Subject: [PATCH 311/909] New translations learn.md (Korean)
---
content/ko/learn.md | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/content/ko/learn.md b/content/ko/learn.md
index 0ad006d0f7..80f6d1fa79 100644
--- a/content/ko/learn.md
+++ b/content/ko/learn.md
@@ -3,21 +3,21 @@ title: Learn
sidebar: false
---
-For the **official NumPy documentation** visit [numpy.org/doc/stable](https://numpy.org/doc/stable).
+**공식 NumPy 문서**는 [numpy.org/doc/stable](https://numpy.org/doc/stable)에 있습니다.
-## NumPy Tutorials
+## NumPy 튜토리얼
-You can find a set of tutorials and educational materials by the NumPy community at [NumPy Tutorials](https://numpy.org/numpy-tutorials). The goal of this page is to provide high-quality resources by the NumPy project, both for self-learning and for teaching classes with, in the format of Jupyter Notebooks. If you’re interested in adding your own content, check the [numpy-tutorials repository on GitHub](https://github.com/numpy/numpy-tutorials).
+NumPy 커뮤니티 [NumPy Tutorials](https://numpy.org/numpy-tutorials)에서 다양한 튜토리얼과 교육 자료를 찾을 수 있습니다. 이 페이지의 목적은 개인 학습 자료와 강의 자료 모두로 활용할 수 있도록 양질의 자료를 제공하는 것이며, 자료는 Jupyter Notebooks 형식으로 되어 있습니다. 만약 추가하고 싶은 내용이 생기는 경우 [numpy-tutorials repository on GitHub](https://github.com/numpy/numpy-tutorials)를 확인해 주십시오.
***
-Below is a curated collection of external resources. To contribute, see the [end of this page](#add-to-this-list).
+아래는 선별된 외부 자료가 모아져 있습니다. 여기에 기여하기 위해서는 [이 페이지](#add-to-this-list)의 마지막 부분을 확인 해주십시오.
-## Beginners
+## 초심자
-There's a ton of information about NumPy out there. If you are new, we'd strongly recommend these:
+방대한 자료가 제공되고 있습니다. 만약 처음 접하신다면, 아래의 자료를 강하게 권해드립니다.
- **Tutorials**
+ **튜토리얼**
* [NumPy Quickstart Tutorial](https://numpy.org/devdocs/user/quickstart.html)
* [NumPy Illustrated: The Visual Guide to NumPy *by Lev Maximov*](https://betterprogramming.pub/3b1d4976de1d?sk=57b908a77aa44075a49293fa1631dd9b)
From 2d0e5b96d56b429c8be6574035e61822242fa8bd Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 24 Apr 2021 16:31:54 +0200
Subject: [PATCH 312/909] New translations citing-numpy.md (Spanish)
---
content/es/citing-numpy.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/content/es/citing-numpy.md b/content/es/citing-numpy.md
index 9aa943e53e..0d19b30596 100644
--- a/content/es/citing-numpy.md
+++ b/content/es/citing-numpy.md
@@ -1,13 +1,13 @@
---
-title: Citing NumPy
+title: Citando a NumPy
sidebar: false
---
-If NumPy has been significant in your research, and you would like to acknowledge the project in your academic publication, we suggest citing the following paper:
+Si NumPy ha sido importante en tu investigación y deseas reconocer el proyecto en tu publicación académica, te sugerimos que cites el siguiente documento:
-* Harris, C.R., Millman, K.J., van der Walt, S.J. et al. _Array programming with NumPy_. Nature 585, 357–362 (2020). DOI: [0.1038/s41586-020-2649-2](https://doi.org/10.1038/s41586-020-2649-2). ([Publisher link](https://www.nature.com/articles/s41586-020-2649-2)).
+* Harris, C.R., Millman, K.J., van der Walt, S.J. et al. _Array programming with NumPy_. Nature 585, 357–362 (2020). DOI: [0.1038/s41586-020-2649-2](https://doi.org/10.1038/s41586-020-2649-2). ([Enlace del editor](https://www.nature.com/articles/s41586-020-2649-2)).
-_In BibTeX format:_
+_En formato BibTeX:_
```
@Article{ harris2020array,
From adbca294422e1271d0a2c619c4fe532462874038 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 24 Apr 2021 16:31:56 +0200
Subject: [PATCH 313/909] New translations code-of-conduct.md (Spanish)
---
content/es/code-of-conduct.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/content/es/code-of-conduct.md b/content/es/code-of-conduct.md
index efcde754ae..9c1a17b683 100644
--- a/content/es/code-of-conduct.md
+++ b/content/es/code-of-conduct.md
@@ -1,11 +1,11 @@
---
-title: NumPy Code of Conduct
+title: Código de conducta de NumPy
sidebar: false
aliases:
- /conduct.html
---
-### Introduction
+### Introducción
This Code of Conduct applies to all spaces managed by the NumPy project, including all public and private mailing lists, issue trackers, wikis, blogs, Twitter, and any other communication channel used by our community. The NumPy project does not organise in-person events, however events related to our community should have a code of conduct similar in spirit to this one.
From 96fe1dcd1e31a5ba7b7fb0fe31ba3fd98aa08efb Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 24 Apr 2021 16:31:57 +0200
Subject: [PATCH 314/909] New translations citing-numpy.md (Korean)
---
content/ko/citing-numpy.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/ko/citing-numpy.md b/content/ko/citing-numpy.md
index 9aa943e53e..9754abe9df 100644
--- a/content/ko/citing-numpy.md
+++ b/content/ko/citing-numpy.md
@@ -3,7 +3,7 @@ title: Citing NumPy
sidebar: false
---
-If NumPy has been significant in your research, and you would like to acknowledge the project in your academic publication, we suggest citing the following paper:
+진행한 연구에서 NumPy가 중요한 부분을 차지하고 있고 학술지에 출판한다면, 아래의 논문을 참조문헌에 써주시길 바랍니다.
* Harris, C.R., Millman, K.J., van der Walt, S.J. et al. _Array programming with NumPy_. Nature 585, 357–362 (2020). DOI: [0.1038/s41586-020-2649-2](https://doi.org/10.1038/s41586-020-2649-2). ([Publisher link](https://www.nature.com/articles/s41586-020-2649-2)).
From 49f60df963527cce8edf841f7eaf98f24d4c76c0 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 24 Apr 2021 16:31:58 +0200
Subject: [PATCH 315/909] New translations install.md (Korean)
---
content/ko/install.md | 19 ++++++++++---------
1 file changed, 10 insertions(+), 9 deletions(-)
diff --git a/content/ko/install.md b/content/ko/install.md
index 69bdbcb0a0..2694083682 100644
--- a/content/ko/install.md
+++ b/content/ko/install.md
@@ -5,30 +5,31 @@ sidebar: false
NumPy 설치를 위해서는 Python만 필요합니다. 만양 파이썬이 설치되지 않았다면, Python, NumPy, 그리고 다양한 데이터 과학과 과학 계산을 위해 일반적으로 많이 사용되는 패키지를 한번에 설치할 수 있는 [Anaconda Distribution](https://www.anaconda.com/distribution)을 활용하여 설치하는 것을 추천합니다.
-NumPy 는 `conda`, `pip` 그리고 macOS과 Linux의 패키지 매니저를 사용하거나 또는 [소스](https://numpy.org/devdocs/user/building.html)로 부터 설치할 수 있습니다. For more detailed instructions, consult our [Python and NumPy installation guide](#python-numpy-install-guide) below.
+NumPy 는 `conda`, `pip` 그리고 macOS과 Linux의 패키지 매니저를 사용하거나 또는 [소스](https://numpy.org/devdocs/user/building.html)로 부터 설치할 수 있습니다. 보다 상세한 설치 과정과 방법은 [Python and NumPy 설치 가이드](#python-numpy-install-guide)의 아래쪽에 있습니다.
**CONDA**
-If you use `conda`, you can install NumPy from the `defaults` or `conda-forge` channels:
+만약 `conda`를 사용해 설치하는 경우, `defaults` 또는 `conda-forge` 채널을 활용해서 설치할 수 있습니다.
```bash
-# Best practice, use an environment rather than install in the base env
-conda create -n my-env
-conda activate my-env
-# If you want to install from conda-forge
+# 기본 환경보다 가상환경을 설치하여 활용하는 것이 좋습니다.
+# Anaconda가 설치된 환경에서 cmd에서 하기 명령어를 입력합니다.
+conda create -n my-env # my-env 라는 이름의 가상환경 생성
+conda activate my-env # 활성화 된 가상환경을 my-env로 변경
+# conda-forge로 설치하는 경우하기 명령어 입력
conda config --env --add channels conda-forge
-# The actual install command
+# 실제 설치 명령어
conda install numpy
```
**PIP**
-If you use `pip`, you can install NumPy with:
+만약 `pip`로 NumPy를 설치하는 경우
```bash
pip install numpy
```
-Also when using pip, it's good practice to use a virtual environment - see [Reproducible Installs](#reproducible-installs) below for why, and [this guide](https://dev.to/bowmanjd/python-tools-for-managing-virtual-environments-3bko#howto) for details on using virtual environments.
+또한 pip를 사용할 때, 가상환경을 만들어보고, 만들어진 가상환경에 설치하는 것이 좋습니다. 상세한 내용은 [Reproducible Installs](#reproducible-installs)를 참조하십시오. 또한 가상환경을 사용하는 상세한 내용은 [가이드](https://dev.to/bowmanjd/python-tools-for-managing-virtual-environments-3bko#howto)를 참조하십시오.
From fbafb0289a026a154d653663553e163e7c268430 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 24 Apr 2021 17:29:28 +0200
Subject: [PATCH 316/909] New translations code-of-conduct.md (Spanish)
---
content/es/code-of-conduct.md | 20 ++++++++++----------
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/content/es/code-of-conduct.md b/content/es/code-of-conduct.md
index 9c1a17b683..b2cfe5bc86 100644
--- a/content/es/code-of-conduct.md
+++ b/content/es/code-of-conduct.md
@@ -7,21 +7,21 @@ aliases:
### Introducción
-This Code of Conduct applies to all spaces managed by the NumPy project, including all public and private mailing lists, issue trackers, wikis, blogs, Twitter, and any other communication channel used by our community. The NumPy project does not organise in-person events, however events related to our community should have a code of conduct similar in spirit to this one.
+Este Código de Conducta se aplica a todos los espacios gestionados por el proyecto NumPy, incluyendo todas las listas de correo públicas y privadas, gestores de incidencias, wikis, blogs, Twitter y cualquier otro canal de comunicación utilizado por nuestra comunidad. El proyecto NumPy no organiza eventos en persona, sin embargo los eventos relacionados con nuestra comunidad deben tener un código de conducta similar a este.
-This Code of Conduct should be honored by everyone who participates in the NumPy community formally or informally, or claims any affiliation with the project, in any project-related activities and especially when representing the project, in any role.
+Este Código de Conducta debe ser respetado por todos los que participan en la comunidad NumPy formalmente o informalmente, o reclaman cualquier afiliación con el proyecto, en cualquier actividad relacionada con el proyecto y especialmente cuando representan el proyecto, de cualquier manera.
-This code is not exhaustive or complete. It serves to distill our common understanding of a collaborative, shared environment and goals. Please try to follow this code in spirit as much as in letter, to create a friendly and productive environment that enriches the surrounding community.
+Este código no es exhaustivo ni completo. Sirve para sintetizar nuestro entendimiento común de un entorno y unos objetivos compartidos y de colaboración. Por favor, intenta seguir este código tanto en el espíritu como en la letra, para crear un ambiente cordial y productivo que enriquezca a la comunidad circundante.
-### Specific Guidelines
+### Directrices Específicas
-We strive to:
+Nos esforzamos por:
-1. Be open. We invite anyone to participate in our community. We prefer to use public methods of communication for project-related messages, unless discussing something sensitive. This applies to messages for help or project-related support, too; not only is a public support request much more likely to result in an answer to a question, it also ensures that any inadvertent mistakes in answering are more easily detected and corrected.
-2. Be empathetic, welcoming, friendly, and patient. We work together to resolve conflict, and assume good intentions. We may all experience some frustration from time to time, but we do not allow frustration to turn into a personal attack. A community where people feel uncomfortable or threatened is not a productive one.
-3. Be collaborative. Our work will be used by other people, and in turn we will depend on the work of others. When we make something for the benefit of the project, we are willing to explain to others how it works, so that they can build on the work to make it even better. Any decision we make will affect users and colleagues, and we take those consequences seriously when making decisions.
-4. Be inquisitive. Nobody knows everything! Asking questions early avoids many problems later, so we encourage questions, although we may direct them to the appropriate forum. We will try hard to be responsive and helpful.
-5. Be careful in the words that we choose. We are careful and respectful in our communication, and we take responsibility for our own speech. Be kind to others. Do not insult or put down other participants. We will not accept harassment or other exclusionary behaviour, such as:
+1. Ser abiertos. Invitamos a todas las personas a participar en nuestra comunidad. Preferimos utilizar métodos de comunicación públicos para los mensajes relacionados con el proyecto, a menos que se trate de algo delicado. Esto se aplica también a los mensajes de ayuda o soporte relacionados con el proyecto; no sólo es mucho más probable que una solicitud de soporte pública dé lugar a una respuesta a una pregunta, sino que también garantiza que cualquier error involuntario en la respuesta se detecte y corrija más fácilmente.
+2. Ser empáticos, receptivos, amables y pacientes. Trabajamos juntos para resolver los conflictos y asumimos que hay buenas intenciones. Todos podemos experimentar cierta frustración de vez en cuando, pero no permitimos que la frustración se convierta en un ataque personal. Una comunidad en la que la gente se siente incómoda o amenazada no es productiva.
+3. Ser colaborativos. Nuestro trabajo será utilizado por otras personas, y a su vez dependeremos del trabajo de otros. Cuando hacemos algo en beneficio del proyecto, estamos dispuestos a explicar a otros cómo funciona. para que puedan aprovechar el trabajo y hacerlo aún mejor. Cualquier decisión que tomemos afectará a usuarios y colegas, y nos tomaremos en serio esas consecuencias a la hora de tomar decisiones.
+4. Ser curiosos. ¡Nadie lo sabe todo! Plantear las preguntas con antelación evita muchos problemas posteriores, por lo que fomentamos las preguntas, aunque es conveniente dirigirlas al foro adecuado. Nos esforzaremos por ser receptivos y útiles.
+5. Ser cuidadosos con las palabras que elijamos. We are careful and respectful in our communication, and we take responsibility for our own speech. Be kind to others. Do not insult or put down other participants. We will not accept harassment or other exclusionary behaviour, such as:
* Violent threats or language directed against another person.
* Sexist, racist, or otherwise discriminatory jokes and language.
* Posting sexually explicit or violent material.
From 7e3ebd0e3eb86f3ee084c6aabc1d2aecf55c7d36 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sat, 24 Apr 2021 18:27:44 +0200
Subject: [PATCH 317/909] New translations code-of-conduct.md (Spanish)
---
content/es/code-of-conduct.md | 70 +++++++++++++++++------------------
1 file changed, 35 insertions(+), 35 deletions(-)
diff --git a/content/es/code-of-conduct.md b/content/es/code-of-conduct.md
index b2cfe5bc86..6bb0dfa637 100644
--- a/content/es/code-of-conduct.md
+++ b/content/es/code-of-conduct.md
@@ -21,63 +21,63 @@ Nos esforzamos por:
2. Ser empáticos, receptivos, amables y pacientes. Trabajamos juntos para resolver los conflictos y asumimos que hay buenas intenciones. Todos podemos experimentar cierta frustración de vez en cuando, pero no permitimos que la frustración se convierta en un ataque personal. Una comunidad en la que la gente se siente incómoda o amenazada no es productiva.
3. Ser colaborativos. Nuestro trabajo será utilizado por otras personas, y a su vez dependeremos del trabajo de otros. Cuando hacemos algo en beneficio del proyecto, estamos dispuestos a explicar a otros cómo funciona. para que puedan aprovechar el trabajo y hacerlo aún mejor. Cualquier decisión que tomemos afectará a usuarios y colegas, y nos tomaremos en serio esas consecuencias a la hora de tomar decisiones.
4. Ser curiosos. ¡Nadie lo sabe todo! Plantear las preguntas con antelación evita muchos problemas posteriores, por lo que fomentamos las preguntas, aunque es conveniente dirigirlas al foro adecuado. Nos esforzaremos por ser receptivos y útiles.
-5. Ser cuidadosos con las palabras que elijamos. We are careful and respectful in our communication, and we take responsibility for our own speech. Be kind to others. Do not insult or put down other participants. We will not accept harassment or other exclusionary behaviour, such as:
- * Violent threats or language directed against another person.
- * Sexist, racist, or otherwise discriminatory jokes and language.
- * Posting sexually explicit or violent material.
- * Posting (or threatening to post) other people’s personally identifying information (“doxing”).
- * Sharing private content, such as emails sent privately or non-publicly, or unlogged forums such as IRC channel history, without the sender’s consent.
- * Personal insults, especially those using racist or sexist terms.
- * Unwelcome sexual attention.
- * Excessive profanity. Please avoid swearwords; people differ greatly in their sensitivity to swearing.
- * Repeated harassment of others. In general, if someone asks you to stop, then stop.
- * Advocating for, or encouraging, any of the above behaviour.
+5. Ser cuidadosos con las palabras que elijamos. Somos cuidadosos y respetuosos en nuestra comunicación, y asumimos la responsabilidad del lenguaje que utilizamos. Somos amables con los demás. No insultes ni menosprecies a los demás participantes. No aceptaremos el acoso ni otros comportamientos excluyentes, como:
+ * Amenazas o expresiones violentas dirigidas a otra persona.
+ * Bromas y lenguaje sexista, racista o discriminatorio.
+ * Publicar material sexualmente explícito o violento.
+ * Publicar (o amenazar con publicar) información de identificación personal de otras personas ("doxing").
+ * Compartir contenido privado, como correos electrónicos enviados de forma privada o no pública, o foros no registrados como el historial de canales IRC, sin el consentimiento del remitente.
+ * Insultos personales, especialmente aquellos que utilizan términos racistas o sexistas.
+ * Atención sexual no deseada.
+ * Uso excesivo de lenguaje inapropiado. Por favor, evite las palabras soeces; las personas difieren mucho en su sensibilidad a las palabrotas.
+ * Acoso reiterado a los demás. En general, si alguien le pide que se detenga, entonces pare.
+ * Defender o fomentar cualquiera de las conductas anteriores.
-### Diversity Statement
+### Declaración de diversidad
-The NumPy project welcomes and encourages participation by everyone. We are committed to being a community that everyone enjoys being part of. Although we may not always be able to accommodate each individual’s preferences, we try our best to treat everyone kindly.
+El proyecto NumPy acoge con satisfacción y fomenta la participación de todos. Estamos comprometidos a ser una comunidad de la que todo el mundo disfruta ser parte. Aunque puede que no siempre seamos capaces de satisfacer las preferencias de cada individuo, intentamos lo mejor para tratar a todo el mundo con amabilidad.
-No matter how you identify yourself or how others perceive you: we welcome you. Though no list can hope to be comprehensive, we explicitly honour diversity in: age, culture, ethnicity, genotype, gender identity or expression, language, national origin, neurotype, phenotype, political beliefs, profession, race, religion, sexual orientation, socioeconomic status, subculture and technical ability, to the extent that these do not conflict with this code of conduct.
+No importa cómo te identifiques o cómo te perciban los demás: te damos la bienvenida. Aunque ninguna lista puede esperar ser exhaustiva, honramos explícitamente la diversidad en: edad, cultura, etnia, genotipo, identidad o expresión de género, lengua, origen nacional, neurotipo, fenotipo, creencias políticas, profesión, raza, religión, orientación sexual, estatus socioeconómico, subcultura y capacidad técnica, en la medida en que no entren en conflicto con este código de conducta.
-Though we welcome people fluent in all languages, NumPy development is conducted in English.
+Aunque aceptamos a personas con dominio de cualquier idioma, el desarrollo de NumPy se lleva a cabo en inglés.
-Standards for behaviour in the NumPy community are detailed in the Code of Conduct above. Participants in our community should uphold these standards in all their interactions and help others to do so as well (see next section).
+Los estándares de comportamiento en la comunidad NumPy se detallan en el Código de Conducta anterior. Los participantes en nuestra comunidad deben mantener estas normas en todas sus interacciones y ayudar a los demás a hacer lo mismo (véase la siguiente sección).
-### Reporting Guidelines
+### Directrices para Informar Incidentes
-We know that it is painfully common for internet communication to start at or devolve into obvious and flagrant abuse. We also recognize that sometimes people may have a bad day, or be unaware of some of the guidelines in this Code of Conduct. Please keep this in mind when deciding on how to respond to a breach of this Code.
+Sabemos que es dolorosamente común que la comunicación en Internet comience o se convierta en un abuso evidente y flagrante. También reconocemos que a veces la gente puede tener un mal día, o no ser consciente de algunas de las directrices de este Código de Conducta. Por favor, tenga esto en cuenta a la hora de decidir cómo responder a una violación de este Código.
-For clearly intentional breaches, report those to the Code of Conduct Committee (see below). For possibly unintentional breaches, you may reply to the person and point out this code of conduct (either in public or in private, whatever is most appropriate). If you would prefer not to do that, please feel free to report to the Code of Conduct Committee directly, or ask the Committee for advice, in confidence.
+En caso de infracciones claramente intencionadas, informe de las mismas al Comité del Código de Conducta (ver más abajo). Para infracciones posiblemente no intencionadas, Usted puede responder a la persona y señalar este código de conducta (tanto en público como en privado, lo que sea más apropiado). Si prefiere no hacerlo, no dude en informar directamente al Comité del Código de Conducta o pedirle consejo, de forma confidencial.
-You can report issues to the NumPy Code of Conduct Committee at numpy-conduct@googlegroups.com.
+Puede informar de los problemas al Comité del Código de Conducta de NumPy en numpy-conduct@googlegroups.com.
-Currently, the Committee consists of:
+Actualmente, la comisión está formada por:
* Stefan van der Walt
* Melissa Weber Mendonça
* Anirudh Subramanian
-If your report involves any members of the Committee, or if they feel they have a conflict of interest in handling it, then they will recuse themselves from considering your report. Alternatively, if for any reason you feel uncomfortable making a report to the Committee, then you can also contact senior NumFOCUS staff at [conduct@numfocus.org](https://numfocus.org/code-of-conduct#persons-responsible).
+Si tu informe implica a algún miembro del Comité, o si éste considera que tiene un conflicto de intereses en su tramitación, se abstendrán de examinar tu denuncia. Si por alguna razón le incomoda hacer un informe al Comité, también puede ponerse en contacto con el personal superior de NumFOCUS en [conduct@numfocus.org](https://numfocus.org/code-of-conduct#persons-responsible).
-### Incident reporting resolution & Code of Conduct enforcement
+### Resolución de informes de incidentes y aplicación del Código de Conducta
-_This section summarizes the most important points, more details can be found in_ [NumPy Code of Conduct - How to follow up on a report](/report-handling-manual).
+_Esta sección resume los puntos más importantes, se pueden encontrar más detalles en el_ [Código de Conducta NumPy - Cómo hacer seguimiento de un incidente](/report-handling-manual).
-We will investigate and respond to all complaints. The NumPy Code of Conduct Committee and the NumPy Steering Committee (if involved) will protect the identity of the reporter, and treat the content of complaints as confidential (unless the reporter agrees otherwise).
+Vamos a investigar y responder a todas las reclamaciones. El Comité del Código de Conducta de NumPy y el Comité Directivo de NumPy (si está involucrado) protegerán la identidad del denunciante y tratarán el contenido de las denuncias como confidencial (a menos que el denunciante esté de acuerdo con lo contrario).
-In case of severe and obvious breaches, e.g. personal threat or violent, sexist or racist language, we will immediately disconnect the originator from NumPy communication channels; please see the manual for details.
+En caso de infracciones graves y evidentes, por ejemplo, amenazas personales o lenguaje violento, sexista o racista, desconectaremos inmediatamente al emisor de los canales de comunicación de NumPy; consulte el manual para obtener más detalles.
-In cases not involving clear severe and obvious breaches of this Code of Conduct the process for acting on any received Code of Conduct violation report will be:
+En los casos que no impliquen infracciones claras, graves y evidentes de este Código de Conducta, el proceso para actuar sobre cualquier informe de infracción del Código de Conducta recibido será:
-1. acknowledge report is received,
-2. reasonable discussion/feedback,
-3. mediation (if feedback didn’t help, and only if both reporter and reportee agree to this),
-4. enforcement via transparent decision (see [Resolutions](/report-handling-manual#resolutions)) by the Code of Conduct Committee.
+1. acusar recibo del informe,
+2. un intercambio de opiniones razonable,
+3. mediación (si la retroalimentación no ha servido de nada, y sólo si tanto el denunciante como el denunciado están de acuerdo con ello),
+4. aplicación a través de una decisión transparente (ver [Resoluciones](/report-handling-manual#resolutions)) hechas por el Comité del Código de conducta.
-The Committee will respond to any report as soon as possible, and at most within 72 hours.
+El Comité responderá a cualquier informe lo antes posible y como máximo dentro de 72 horas.
-### Endnotes
+### Nota final
-We are thankful to the groups behind the following documents, from which we drew content and inspiration:
+Damos las gracias a los grupos que están detrás de los siguientes documentos, de los que hemos sacado contenido e inspiración:
-- [The SciPy Code of Conduct](https://docs.scipy.org/doc/scipy/reference/dev/conduct/code_of_conduct.html)
+- [El Código de Conducta de SciPy](https://docs.scipy.org/doc/scipy/reference/dev/conduct/code_of_conduct.html)
From 51997a805e4439bb5653fc4a0ee0e715b24787b6 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sun, 25 Apr 2021 07:16:26 +0200
Subject: [PATCH 318/909] New translations install.md (Korean)
---
content/ko/install.md | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/content/ko/install.md b/content/ko/install.md
index 2694083682..2bd812d29f 100644
--- a/content/ko/install.md
+++ b/content/ko/install.md
@@ -33,19 +33,19 @@ pip install numpy
-# Python and NumPy installation guide
+# Python, Numpy 설치 가이드
-Installing and managing packages in Python is complicated, there are a number of alternative solutions for most tasks. This guide tries to give the reader a sense of the best (or most popular) solutions, and give clear recommendations. It focuses on users of Python, NumPy, and the PyData (or numerical computing) stack on common operating systems and hardware.
+파이썬만 활용해서 패키지를 설치하고 관리하는 것은 복잡하기 때문에, 다양한 대안들이 많이 있습니다. 이 가이드에는 가장 보편적이고, 명확한 방식을 알려줍니다. 이 가이드는 통상적으로 사용되는 운영체제와 하드웨어에서 Python과 NumPy 그리고 수치 계산을 해주는 PyData를 사용하는 유저를 위한 자료입니다.
## Recommendations
-We'll start with recommendations based on the user's experience level and operating system of interest. If you're in between "beginning" and "advanced", please go with "beginning" if you want to keep things simple, and with "advanced" if you want to work according to best practices that go a longer way in the future.
+사용자의 전문성과 사용하는 운영체제를 기준으로 추천하는 방식을 알려드리겠습니다. 만약 당신이 초심자 또는 숙련자범위에 속해있다면, 간단하게 설치하고 싶다면 초심자로, 추후에 작업을 위해서 보다 구체적인 연습을 하고 싶다면 숙련자 자료를 참고하십시오.
-### Beginning users
+### 초심자 유저
-On all of Windows, macOS, and Linux:
+Windows, macOS, Linux 등 모든 일반적인 운영체제:
-- Install [Anaconda](https://www.anaconda.com/distribution/) (it installs all packages you need and all other tools mentioned below).
+- [Anaconda](https://www.anaconda.com/distribution/) 를 설치하십시오.(당신이 필요로 하는 패키지를 설치하고, 아래에 언급될 다양한 도구들을 제공합니다.)
- For writing and executing code, use notebooks in [JupyterLab](https://jupyterlab.readthedocs.io/en/stable/index.html) for exploratory and interactive computing, and [Spyder](https://www.spyder-ide.org/) or [Visual Studio Code](https://code.visualstudio.com/) for writing scripts and packages.
- Use [Anaconda Navigator](https://docs.anaconda.com/anaconda/navigator/) to manage your packages and start JupyterLab, Spyder, or Visual Studio Code.
From d09286527622ef602f188c7f31cf640618340991 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sun, 25 Apr 2021 08:16:56 +0200
Subject: [PATCH 319/909] New translations install.md (Korean)
---
content/ko/install.md | 42 +++++++++++++++++++++---------------------
1 file changed, 21 insertions(+), 21 deletions(-)
diff --git a/content/ko/install.md b/content/ko/install.md
index 2bd812d29f..05a405f1bc 100644
--- a/content/ko/install.md
+++ b/content/ko/install.md
@@ -46,40 +46,40 @@ pip install numpy
Windows, macOS, Linux 등 모든 일반적인 운영체제:
- [Anaconda](https://www.anaconda.com/distribution/) 를 설치하십시오.(당신이 필요로 하는 패키지를 설치하고, 아래에 언급될 다양한 도구들을 제공합니다.)
-- For writing and executing code, use notebooks in [JupyterLab](https://jupyterlab.readthedocs.io/en/stable/index.html) for exploratory and interactive computing, and [Spyder](https://www.spyder-ide.org/) or [Visual Studio Code](https://code.visualstudio.com/) for writing scripts and packages.
-- Use [Anaconda Navigator](https://docs.anaconda.com/anaconda/navigator/) to manage your packages and start JupyterLab, Spyder, or Visual Studio Code.
+- 코드를 작성하거나 실행할 때, 데이터를 분석하거나 대화형으로 코드를 작업하는 경우에는 [JupyterLab](https://jupyterlab.readthedocs.io/en/stable/index.html) 의 notebooks를 사용하십시오. 그리고 코드를 작성하거나 패키지를 작성할 때는 [Spyder](https://www.spyder-ide.org/)나 [Visual Studio Code](https://code.visualstudio.com/)를 사용하십시오.
+- 패키지를 관리하거나 JupyterLab, Spyder, Visual Studio Code 를 사용하는 경우 [Anaconda Navigator](https://docs.anaconda.com/anaconda/navigator/)를 사용하십시오.
-### Advanced users
+### 숙련자 유저
-#### Windows or macOS
+#### Windows, macOS
-- Install [Miniconda](https://docs.conda.io/en/latest/miniconda.html).
-- Keep the `base` conda environment minimal, and use one or more [conda environments](https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#) to install the package you need for the task or project you're working on.
-- Unless you're fine with only the packages in the `defaults` channel, make `conda-forge` your default channel via [setting the channel priority](https://conda-forge.org/docs/user/introduction.html#how-can-i-install-packages-from-conda-forge).
+- [Miniconda](https://docs.conda.io/en/latest/miniconda.html)를 설치하십시오.
+- `base` 라는 이름의 콘다 가상환경은 초기 최소 상태를 유지하고, [콘다 가상환경](https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#)을 만들어서, 해당 가상환경에 진행하고자 하는 일이나 프로젝트를 위해서 필요한 패키지를 설치하십시오.
+- `기본 채널`로 충분하지 않다면, `conda-forge` [채널 우선순위 설정](https://conda-forge.org/docs/user/introduction.html#how-can-i-install-packages-from-conda-forge)을 통해서 원하는 채널을설정할 수 있습니다..
#### Linux
-If you're fine with slightly outdated packages and prefer stability over being able to use the latest versions of libraries:
-- Use your OS package manager for as much as possible (Python itself, NumPy, and other libraries).
-- Install packages not provided by your package manager with `pip install somepackage --user`.
+만약 약간 하위 버전의 패키지나, 최신 버전이 아닌 보다 안정적인 패키지를 설치하고 싶은 경우에 참고하십시오.
+- OS에서 사용 가능한 패키지 매니저를 활용하여 설치하십시오 (Python itself, NumPy, and other libraries).
+- 설치한 패키지 매니저가 라이브러리를 설치해주지 않는다면, `pip install somepackage --user`를 명령 프롬프트에 입력하십시오.
-If you use a GPU:
-- Install [Miniconda](https://docs.conda.io/en/latest/miniconda.html).
-- Keep the `base` conda environment minimal, and use one or more [conda environments](https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#) to install the package you need for the task or project you're working on.
-- Use the `defaults` conda channel (`conda-forge` doesn't have good support for GPU packages yet).
+GPU를 사용하는 경우:
+- [Miniconda](https://docs.conda.io/en/latest/miniconda.html)를 설치하십시오.
+- `base` 라는 이름의 콘다 가상환경은 초기 최소 상태를 유지하고, [콘다 가상환경](https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#)을 만들어서, 해당 가상환경에 진행하고자 하는 일이나 프로젝트를 위해서 필요한 패키지를 설치하십시오.
+- `기본 콘다 채널`을 활용해 주십시오.(`conda-forge` GPU 패키지를 지원하는 좋은 채널을 아직 제공하지 않습니다.).
-Otherwise:
-- Install [Miniforge](https://github.com/conda-forge/miniforge).
-- Keep the `base` conda environment minimal, and use one or more [conda environments](https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#) to install the package you need for the task or project you're working on.
+기타:
+- [Miniforge](https://github.com/conda-forge/miniforge)를 설치하십시오.
+- `base` 라는 이름의 콘다 가상환경은 초기 최소 상태를 유지하고, [콘다 가상환경](https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#)을 만들어서, 해당 가상환경에 진행하고자 하는 일이나 프로젝트를 위해서 필요한 패키지를 설치하십시오.
-#### Alternative if you prefer pip/PyPI
+#### Pip/PyPI를 활용하는 경우:
-For users who know, from personal preference or reading about the main differences between conda and pip below, they prefer a pip/PyPI-based solution, we recommend:
-- Install Python from [python.org](https://www.python.org/downloads/), [Homebrew](https://brew.sh/), or your Linux package manager.
-- Use [Poetry](https://python-poetry.org/) as the most well-maintained tool that provides a dependency resolver and environment management capabilities in a similar fashion as conda does.
+개인적인 선호나 아래의 conda 와 pip의 차이점을 설명하는 글을 읽은 유저나 또는 pip/PyPI기반의 설치 방법을 선호하는 경우 참고하십시오.
+- [python.org](https://www.python.org/downloads/) 이나 [Homebrew](https://brew.sh/), Linux package manager를 활용해서 Python을 설치하십시오.
+- Conda와 동일한 수준의 가상환경 관리와 패키지 의존성을 해결을 도와주는 [Poetry](https://python-poetry.org/)를 유지관리 도구로 사용하십시오.
## Python package management
From 7843d42745aed16373608f1d38fddad5bf69aabc Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sun, 25 Apr 2021 16:27:56 +0200
Subject: [PATCH 320/909] New translations learn.md (Korean)
---
content/ko/learn.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/content/ko/learn.md b/content/ko/learn.md
index 80f6d1fa79..e5d9f7e45e 100644
--- a/content/ko/learn.md
+++ b/content/ko/learn.md
@@ -36,7 +36,7 @@ NumPy 커뮤니티 [NumPy Tutorials](https://numpy.org/numpy-tutorials)에서
* [From Python to NumPy *by Nicolas P. Rougier*](https://www.labri.fr/perso/nrougier/from-python-to-numpy/)
* [Elegant SciPy](https://www.amazon.com/Elegant-SciPy-Art-Scientific-Python/dp/1491922877) *by Juan Nunez-Iglesias, Stefan van der Walt, and Harriet Dashnow*
-You may also want to check out the [Goodreads list](https://www.goodreads.com/shelf/show/python-scipy) on the subject of "Python+SciPy." Most books there are about the "SciPy ecosystem," which has NumPy at its core.
+Python+SciPy와 관련된 자료는 [Goodreads list](https://www.goodreads.com/shelf/show/python-scipy)를 확인하시면 좋습니다. 대부분 NumPy를 핵심으로 사용하는 SciPy 에코시스템과 관련된 자료입니다.
**Videos**
@@ -44,7 +44,7 @@ You may also want to check out the [Goodreads list](https://www.goodreads.com/sh
***
-## Advanced
+## 숙련자
Try these advanced resources for a better understanding of NumPy concepts like advanced indexing, splitting, stacking, linear algebra, and more.
From ee2459f034c766113dc8015e4e9e28a5e3787612 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sun, 25 Apr 2021 17:27:36 +0200
Subject: [PATCH 321/909] New translations learn.md (Korean)
---
content/ko/learn.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/ko/learn.md b/content/ko/learn.md
index e5d9f7e45e..fda3607db0 100644
--- a/content/ko/learn.md
+++ b/content/ko/learn.md
@@ -46,7 +46,7 @@ Python+SciPy와 관련된 자료는 [Goodreads list](https://www.goodreads.com/s
## 숙련자
-Try these advanced resources for a better understanding of NumPy concepts like advanced indexing, splitting, stacking, linear algebra, and more.
+NumPy에서 제공하는 어레이 인덱싱, 분리, 중첩, 선형 대수 등과 같은 개념들을 보다 깊이 이해하고 싶다면, 아래의 숙련자 자료를 활용하십시오.
**Tutorials**
From 0651ef7c8af0e3a3b87f153124ac293325c1e230 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Tue, 27 Apr 2021 15:45:58 +0200
Subject: [PATCH 322/909] New translations install.md (Korean)
---
content/ko/install.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/content/ko/install.md b/content/ko/install.md
index 05a405f1bc..199c524498 100644
--- a/content/ko/install.md
+++ b/content/ko/install.md
@@ -82,9 +82,9 @@ GPU를 사용하는 경우:
- Conda와 동일한 수준의 가상환경 관리와 패키지 의존성을 해결을 도와주는 [Poetry](https://python-poetry.org/)를 유지관리 도구로 사용하십시오.
-## Python package management
+## Python 패키지 관리
-Managing packages is a challenging problem, and, as a result, there are lots of tools. For web and general purpose Python development there's a whole [host of tools](https://packaging.python.org/guides/tool-recommendations/) complementary with pip. For high-performance computing (HPC), [Spack](https://github.com/spack/spack) is worth considering. For most NumPy users though, [conda](https://conda.io/en/latest/) and [pip](https://pip.pypa.io/en/stable/) are the two most popular tools.
+패키지 관리는 아주 중요하기 때문에, 사용할 수 있는 도구들이 많다, 웹 및 범용 Python 개발을 위해 Pip뿐만 아니라 [다양한 도구](https://packaging.python.org/guides/tool-recommendations/)들이 있다. For high-performance computing (HPC), [Spack](https://github.com/spack/spack) is worth considering. For most NumPy users though, [conda](https://conda.io/en/latest/) and [pip](https://pip.pypa.io/en/stable/) are the two most popular tools.
### Pip & conda
From d6ce1f10ebfaf4d4d9b01f737e21a9155ce406f5 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Tue, 27 Apr 2021 16:41:43 +0200
Subject: [PATCH 323/909] New translations install.md (Korean)
---
content/ko/install.md | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/content/ko/install.md b/content/ko/install.md
index 199c524498..c65b872205 100644
--- a/content/ko/install.md
+++ b/content/ko/install.md
@@ -84,18 +84,18 @@ GPU를 사용하는 경우:
## Python 패키지 관리
-패키지 관리는 아주 중요하기 때문에, 사용할 수 있는 도구들이 많다, 웹 및 범용 Python 개발을 위해 Pip뿐만 아니라 [다양한 도구](https://packaging.python.org/guides/tool-recommendations/)들이 있다. For high-performance computing (HPC), [Spack](https://github.com/spack/spack) is worth considering. For most NumPy users though, [conda](https://conda.io/en/latest/) and [pip](https://pip.pypa.io/en/stable/) are the two most popular tools.
+패키지 관리는 아주 중요하기 때문에, 사용할 수 있는 도구들이 많습니다. 웹 및 범용 Python 개발을 위해 Pip뿐만 아니라 [다양한 도구](https://packaging.python.org/guides/tool-recommendations/)들이 있습니다. 고성능 컴퓨터 (HPC)를 사용하는 경우 [Spack](https://github.com/spack/spack)를 사용하는 것을 추천합니다. 대부분 Numpy를 사용하는 유저는, [conda](https://conda.io/en/latest/) 와 [pip](https://pip.pypa.io/en/stable/)를 가장 많이 사용합니다.
### Pip & conda
-The two main tools that install Python packages are `pip` and `conda`. Their functionality partially overlaps (e.g. both can install `numpy`), however, they can also work together. We'll discuss the major differences between pip and conda here - this is important to understand if you want to manage packages effectively.
+`pip`, `conda`가 Python 패키지를 설치하고 관리하는 주요 툴입니다. 그들의 기능은 대부분 겹칩니다. (e.g. both can install `numpy`), 그리고 같이 쓰일 수도 있습니다. 곧 pip와 conda의 차이점에 대해서 논의해볼 것입니다. - 패키지 관리를 잘 하기 위해서는 알고 계시는 것이 좋습니다.
-The first difference is that conda is cross-language and it can install Python, while pip is installed for a particular Python on your system and installs other packages to that same Python install only. This also means conda can install non-Python libraries and tools you may need (e.g. compilers, CUDA, HDF5), while pip can't.
+첫번째 차이점은, conda는 cross-language 를 지원하고, Python을 설치할 수 도있습니다. 하지만 pip는 특정 설치된 Python에만 패키지를 설치하고 관리할 수 있습니다. 따라서 해당 Python에 모든 패키지가 설치됩니다. 또한 conda는 non-Python 라이브러리나 도구들을 설치할 수 있습니다. (e.g. compilers, CUDA, HDF5), 하지만 pip는 Python이 필요하기 때문에 설치할 수 없습니다.
-The second difference is that pip installs from the Python Packaging Index (PyPI), while conda installs from its own channels (typically "defaults" or "conda-forge"). PyPI is the largest collection of packages by far, however, all popular packages are available for conda as well.
+두번째 차이점은 pip는 Python Packaging Index(PyPI) 로 부터 패키지를 다운받아 설치합니다. 반면에 conda는 conda 만의 채널로 설치합니다. (일반적으로 "defaults" or "conda-forge"). PyPI 가 가장 큰 패키지 저장소입니다만, 많은 사람들이 사용하는 패키지는 conda에서도 설치할 수 있습니다.
-The third difference is that conda is an integrated solution for managing packages, dependencies and environments, while with pip you may need another tool (there are many!) for dealing with environments or complex dependencies.
+세번째 차이점은 conda는 환경이나 패키지간 의존성을 해결하기 위한 해키지 관리 도구를 제공합니다. 하지만 pip는 그를 위해서 (아주 많은) 추가적인 도구들이 필요합니다.
### Reproducible installs
From f84ec013b407b7a7ed6ffb111ddffb7ada366eab Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Thu, 29 Apr 2021 08:29:08 +0200
Subject: [PATCH 324/909] New translations learn.md (Japanese)
---
content/ja/learn.md | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/content/ja/learn.md b/content/ja/learn.md
index 5329bdf3fc..9c2e6aa2eb 100644
--- a/content/ja/learn.md
+++ b/content/ja/learn.md
@@ -5,17 +5,17 @@ sidebar: false
**公式の Numpy ドキュメント** については [numpy.org/doc/stable](https://numpy.org/doc/stable) を参照してください。
-## NumPy Tutorials
+## NumPy のチュートリアル
-You can find a set of tutorials and educational materials by the NumPy community at [NumPy Tutorials](https://numpy.org/numpy-tutorials). The goal of this page is to provide high-quality resources by the NumPy project, both for self-learning and for teaching classes with, in the format of Jupyter Notebooks. If you’re interested in adding your own content, check the [numpy-tutorials repository on GitHub](https://github.com/numpy/numpy-tutorials).
+[Numpy のチュートリアル](https://numpy.org/numpy-tutorials) では、Numpy コミュニティによるチュートリアルや教材が手に入ります。 このページの目標は、NumPy プロジェクトによる自己学習と授業のための高品質な教材を Jupyter Notebooks の形式で提供することです。 独自のコンテンツを追加したい場合は、GitHubの [numpy-tutorials リポジトリ](https://github.com/numpy/numpy-tutorials)を確認してください。
***
-Below is a curated collection of external resources. To contribute, see the [end of this page](#add-to-this-list).
+以下は、厳選された外部の教材です。 こちらのリストに貢献するには、 [このページの末尾](#add-to-this-list) を参照してください。
-## Beginners
+## 初学者向け
-There's a ton of information about NumPy out there. If you are new, we'd strongly recommend these:
+NumPyについての情報はたくさん見つかります。 If you are new, we'd strongly recommend these:
**Tutorials**
From fcaa9737cadad8f55914fde2d8f60aabae150a44 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Thu, 29 Apr 2021 08:29:09 +0200
Subject: [PATCH 325/909] New translations about.md (Japanese)
---
content/ja/about.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/ja/about.md b/content/ja/about.md
index a9c9232830..8b2eb04a17 100644
--- a/content/ja/about.md
+++ b/content/ja/about.md
@@ -18,7 +18,7 @@ NumPy運営委員会の役割は、NumPyのコミュニティと協力しサポ
- Ralf Gommers
- Charles Harris
- Stephan Hoyer
-- Melissa Weber Mendonça
+- Melissa Weber Mendonça
- Inessa Pawson
- Matti Picus
- Stéfan van der Walt
From 9e298d10796686e94430476b300e347ac041f5da Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sun, 2 May 2021 00:50:26 +0200
Subject: [PATCH 326/909] New translations about.md (Arabic)
---
content/ar/about.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/ar/about.md b/content/ar/about.md
index fce591bb90..edc0b83f63 100644
--- a/content/ar/about.md
+++ b/content/ar/about.md
@@ -36,7 +36,7 @@ Emeritus:
- Jaime Fernández del Río (2014-2021)
-## Teams
+## الأقسام
The NumPy project is growing; we have teams for
From 91eb703ebfcf04f3a3a5f98273d6fa67a64193f5 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sun, 2 May 2021 01:50:43 +0200
Subject: [PATCH 327/909] New translations about.md (Arabic)
---
content/ar/about.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/content/ar/about.md b/content/ar/about.md
index edc0b83f63..539e5ae7e6 100644
--- a/content/ar/about.md
+++ b/content/ar/about.md
@@ -38,7 +38,7 @@ Emeritus:
## الأقسام
-The NumPy project is growing; we have teams for
+يزدهر مشروع نمباي حيث أصبح لدينا أقسام لكل من
- code
- documentation
@@ -48,7 +48,7 @@ The NumPy project is growing; we have teams for
See the [Team](/gallery/team.html) page for individual team members.
-## Sponsors
+## الرُعاة
NumPy receives direct funding from the following sources:
{{< sponsors >}}
From 7b24953dfbda640ecbf38cac43b76f4d8de418f2 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Sun, 2 May 2021 02:53:06 +0200
Subject: [PATCH 328/909] New translations about.md (Arabic)
---
content/ar/about.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/ar/about.md b/content/ar/about.md
index 539e5ae7e6..54320bf2c0 100644
--- a/content/ar/about.md
+++ b/content/ar/about.md
@@ -50,7 +50,7 @@ See the [Team](/gallery/team.html) page for individual team members.
## الرُعاة
-NumPy receives direct funding from the following sources:
+ويتلقى المشروع تمويلا مباشرا من المصادر التالية:
{{< sponsors >}}
From d4380a31f26cafd1870a2fd276495d6bbdf90cb9 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Thu, 6 May 2021 23:45:15 +0200
Subject: [PATCH 329/909] New translations privacy.md (Chinese Simplified)
---
content/zh/privacy.md | 10 ----------
1 file changed, 10 deletions(-)
diff --git a/content/zh/privacy.md b/content/zh/privacy.md
index a3674dd48a..6064e4c4f1 100644
--- a/content/zh/privacy.md
+++ b/content/zh/privacy.md
@@ -6,13 +6,3 @@ sidebar: false
**numpy.org** is operated by [NumFOCUS, Inc.](https://numfocus.org), the fiscal sponsor of the NumPy project. For the Privacy Policy of this website please refer to https://numfocus.org/privacy-policy.
If you have any questions about the policy or NumFOCUS’s data collection, use, and disclosure practices, please contact the NumFOCUS staff at privacy@numfocus.org.
-
-
-
-
-
-
-
-
-
-
From 442f064b4b8eb60e5e3f534627fbcdd83e56c1af Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Thu, 6 May 2021 23:45:20 +0200
Subject: [PATCH 330/909] New translations privacy.md (Korean)
---
content/ko/privacy.md | 10 ----------
1 file changed, 10 deletions(-)
diff --git a/content/ko/privacy.md b/content/ko/privacy.md
index a3674dd48a..6064e4c4f1 100644
--- a/content/ko/privacy.md
+++ b/content/ko/privacy.md
@@ -6,13 +6,3 @@ sidebar: false
**numpy.org** is operated by [NumFOCUS, Inc.](https://numfocus.org), the fiscal sponsor of the NumPy project. For the Privacy Policy of this website please refer to https://numfocus.org/privacy-policy.
If you have any questions about the policy or NumFOCUS’s data collection, use, and disclosure practices, please contact the NumFOCUS staff at privacy@numfocus.org.
-
-
-
-
-
-
-
-
-
-
From 9b42b9c248c6c6d997a9622a476246885f2053c4 Mon Sep 17 00:00:00 2001
From: Ralf Gommers
Date: Thu, 6 May 2021 23:45:39 +0200
Subject: [PATCH 331/909] New translations privacy.md (Portuguese, Brazilian)
---
content/pt/privacy.md | 10 ----------
1 file changed, 10 deletions(-)
diff --git a/content/pt/privacy.md b/content/pt/privacy.md
index be4b6613da..c95f1d5ec1 100644
--- a/content/pt/privacy.md
+++ b/content/pt/privacy.md
@@ -6,13 +6,3 @@ sidebar: false
**numpy.org** é operado por [NumFOCUS, Inc.](https://numfocus.org), o patrocinador fiscal do projeto NumPy. Para a Política de Privacidade deste site, consulte https://numfocus.org/privacy-policy.
Se você tiver alguma dúvida sobre a política ou as práticas de coleta de dados do NumFOCUS, uso e divulgação, entre em contato com a equipe do NumFOCUS em privacy@numfocus.org.
-
-
-
-
-
-
-
-
-
-
From 022c2d4d086897ecd2feb1c8b505ab1fab97d83a Mon Sep 17 00:00:00 2001
From: Ralf Gommers