qosf / qosf.org Goto Github PK

It’s mentioned on the manifesto page that membership is as simple as subscribing to the newsletter, but then it’s mentioned below that amendments require a 10% vote of members. I’m not suggesting that any amendment is needed, but it’s a little unclear to me how this would happen logistically or whether it would be worthwhile to list membership somehow. Ideally, maintaining a membership list would be done simply and supported through github somehow (e.g. have users fork some repo or maybe add github accounts to a group w readonly access).

pyGSTi is a software framework from Sandia National Laboratories' Quantum Performance Lab for the modeling, characterization and benchmarking of noisy quantum computers. It contains implementations of gate set tomography, randomized benchmarking, and many other characterization protocols. It contains a number of routines for simulating noisy and noiseless quantum processors, and can compute a wide range of performance metrics. It is capable of outputting code that can be directly run by several open-access quantum testbeds, and is widely used in the community.

I suggest adding the following to the full-stack software libraries:

  - description: 'Software framework for modeling, characterizing, and benchmarking noisy
      quantum computers developed by [Sandia''s Quantum Performance 
      Laboratory](https://qpl.sandia.gov/)'
    name: pyGSTi
    url: http://www.pygsti.info/

This is just a cosmetic issue, but will avoid a lot of confusion.

Currently, the "Apply for mentorship" button has a Stack Overflow icon appended to it, but it leads to Google Forms instead. I think it is misleading.

It would be good to change the icon to Google so that people who don't like to use Google tools like me can ask for other alternatives without bothering to click on it.

This line seems to be the issue
https://github.com/qosf/qosf.org/blame/master/qosf.org/qc_mentorship.md#L15

I am not familiar with doks theme and I see only google-plus icon in the list of icons, If the site owners are okay with it I would be happy to contribue a new icon.

The link for 'IBM Q Full User Guide' under Learning Resources (in learn_quantum.md) does not work. I did not open a PR because I was not sure which of the following links did the developers had in mind:

1. https://quantum-computing.ibm.com/jupyter
2. https://quantum-computing.ibm.com/docs/

We need to update the website with new information. The reason is to explain in detail the processes done in QOSF, including the monthly challenge, the mentoring program, and the courses on YouTube.

We need to generate a new format to present the mentors as mentees who have participated and participated before. We also need to generate new pages and propose what we can add to update the website following the QOSF style and color palette.

We have got some updates to make to the website! We should generate something more animated to present mentors. For example, we should create a carousel with mentors' photos, names, and origins. We should also create a carousel for mentees.

For the cohorts, we need to create new pages and perform the same process as above, but with updated cohort numbers. Similarly, we should create new pages for the monthly challenge and link the responses of those who have completed it month by month on the website.

Finally, we link the responses of those who have completed a monthly challenge month by month at the website.

Necesitamos actualizar la página web con nueva información. El motivo es explicar en detalle los procesos que se llevan a cabo en QOSF, incluido el reto mensual, el programa de mentores y los cursos en YouTube.

Necesitamos generar un nuevo formato para presentar a los mentores como mentees que han participado y participado anteriormente. También necesitamos generar nuevas páginas y proponer qué podemos añadir para actualizar el sitio web siguiendo el estilo y la paleta de colores de QOSF.

¡Tenemos algunas actualizaciones que hacer en el sitio web! Deberíamos generar algo más animado para presentar a los mentores. Por ejemplo, deberíamos crear un carrusel con las fotos, los nombres y los orígenes de los mentores. También deberíamos crear un carrusel para los alumnos.

Para las cohortes, debemos crear nuevas páginas y realizar el mismo proceso anterior, pero con los números de cohorte actualizados. Del mismo modo, debemos crear nuevas páginas para el reto mensual y enlazar las respuestas de quienes lo han completado mes a mes en el sitio web.

Por último, enlazamos las respuestas de quienes han completado el reto mensual mes a mes en el sitio web.

For the mentorship program and the monthly challenges, a proposal is being developed to ensure impartiality in the code analysis. It is suggested to create a grader capable of processing multiple inputs given the function name,
the reference challenge to design the grade. To achieve this, the following points are considered:

• The grader should be easily configurable for each challenge.
• A minimal example with a previous challenge is required.
• It should include the function name, the expected inputs, and display the corresponding output.
• Generic tests should be provided for each function.
• A guide on how to generate an open test should be included, as well as at least five private tests to validate the response's performance.
• In case of receiving an error, an exception indicating that the code is incorrect should be generated.
• Optionally, a suggestion may be made to distinguish between programming errors and general response errors.

Para el programa de mentoría y los retos mensuales, se está desarrollando una propuesta para garantizar la imparcialidad en el análisis del código. Se sugiere crear un grader capaz de procesar múltiples entradas dado el nombre de la función,
el reto de referencia para diseñar el grader. Para ello, se consideran los siguientes puntos:

• El grader debe ser fácilmente configurable para cada reto.
• Se requiere un ejemplo mínimo con un desafío anterior.
• Debe incluir el nombre de la función, las entradas esperadas y mostrar la salida correspondiente.
• Se deben proporcionar pruebas genéricas para cada función.
• Es necesario incluir una guía sobre cómo generar una prueba abierta, así como al menos cinco pruebas privadas para validar el rendimiento de la respuesta.
• En caso de recibir un error, se debe generar una excepción que indique que el código no es correcto.
• Opcionalmente, se puede proponer un indicador para distinguir entre errores de programación y errores de respuesta general.

It would be great if QuTiP, Quantum Toolbox in Python (http://qutip.org, https://github.com/qutip), could be added to the score cards in https://qosf.org/evaluation/.

While its core is quantum optics, It also has a quantum circuit simulator module (growing in scope with noise models), quantum information processing tools and visualization features, used broadly in the quantum computing ecosystem.
 
Below I add some information relevant to assess the Project's status and Community part.

I am available for support (cc @ajgpitch @Ericgig @quantshah @nwlambert). 

+++++++++++

Project

QuTiP is the open-source software to study quantum optics and related processes. It develops both an intuitive playground to understand quantum mechanics and cutting-edge tools to investigate it. QuTiP provides the most comprehensive toolbox to characterize noise and dissipation – realistic processes – affecting quantum systems, as well as tools not only to monitor but also to minimize their impact, quantum optimal control, description of decoherence-free spaces, used also for quantum circuits. It contains quantum circuit simulator module, and it integrates it with noise models.

For this reason QuTiP is a software born out of the quantum optics community and that has become increasingly relevant for the quantum computing community, as current quantum computing devices are noisy (NISQ definition by Preskill).

Since 2018, QuTiP is an affiliated project to NumFOCUS. It participated through it to Google Summer of Code 2019(GSoC).

It has online documentation, tutorials, and platform independent unit-testing with Travis CI (nose) and codeclimate tests. It is distributed on conda-forge, pip, and as compressed file on the website. Tutorials are also running with My Binder.

Code

• QuTiP website: http://www.qutip.org/
• GitHub repository: https://github.com/qutip
• GitHub repository (QuTiP code): https://github.com/qutip/qutip
• GitHub repository (QuTiP documentation): https://github.com/qutip/qutip-doc
• GitHub repository (QuTiP tutorials): https://github.com/qutip/qutip-notebooks
• Latest version of the documetnation: http://qutip.org/docs/latest/index.html
• Historical archive of released documentation: http://qutip.org/documentation.html

Community

• QuTiP forum, on Google groups: https://groups.google.com/forum/#!forum/qutip
• QuTiP roadmap: https://github.com/qutip/qutip/wiki/Roadmap
• QuTiP gitter: https://gitter.im/qutip/Lobby?source=orgpage
• QuTiP lead developers use a private Slack channel
• QuTiP tutorials, examples and lectures: http://www.qutip.org/ tutorials

Ecosystem

QuTiP is emerging as a library at the center of a lively ecosystem.
About the idea of QuTiP as a super-library, here are some details on the other 72 other github repositories using QuTiP:

• krotov, a very recent package for optimal control built on top of QuTiP ( https://arxiv.org/abs/1902.11284). https://github.com/qucontrol/krotov
• piqs, the permutational invariant quantum solver, now a QuTiP module (see also https://arxiv.org/abs/1805.05129 );
• matsubara, a plugin to study the ultrastrong coupling regime with structured baths, http://matsubara.readthedocs.io/
• QNET, a computer algebra package for quantum mechanics and photonic quantum networks, which actually calls QuTiP as a plugin, mainly developed at Stanford in Mabuchi Lab https://github.com/mabuchilab/QNET
• qptomographer, https://qptomographer.readthedocs.io/en/latest/install, a library to derive error bars for experiments in quantum computing and quantum information processing.
• tiqs, a library to study open quantum systems on extended lattices exploiting the symmetries of such systems, https://github.com/fminga/tiqs

Hello,

Please send me the invite link for the quantum mentorship program again.

Sorry for the inconvenience I am causing.

In learn_quantum.md seems to be a problem with the link to the following learning resource:

Nielsen and Chuang
Worked examples on quantum algorithm problems.

@desireevl is this website down or is the link wrong?

I'm from over on the Qrack simulator project. Thank you for these awesome resources! I wanted to let you know that we've iterated Qrack, and a number of your metrics on the project might be out of date, by now.

• We switched to LGPL (from GPL) several months ago to ease integrations into stacks, like with ProjectQ and SimulaQron.
• In addition to Linux and Mac (Mojave), we've finished adding support for Windows 10 builds with CMake and Visual Studio. (We also support the Raspberry Pi 3, now.)
• We've added code for several example executables, and we've updated our documentation, including adding a CHANGELOG.md and a CONTRIBUTING.md.
• We've had a Discord server at https://discordapp.com/invite/Gj3CHDy this whole time, but we failed to let people know clearly via the repo. We've added it to the README.
• We've had some more external involvement in Github issues, and the corresponding metrics might be out of date.

Thank you again! We're following qosf.org, and we hope Qrack can be a useful resource to everyone!

You can add Quantum Inspire and QX Simulator developed from QuTech, Delft to the list. Both are released and publicly accessible at:
http://quantum-studio.net/
https://www.quantum-inspire.com/

All projects and learning resources should be ordered alphabetically under each heading to avoid any bias or preference.

I've recently found QOSF website and I find resources available there very useful for people interested in Quantum Computing. However, what I noticed is that website hasn't been updated for a while, especially when compared to discussions and commits available on GitHub. For example recent PR #87 is merged, but not present on the website. Similarly, issue #24 discusses rewrite to the manifesto, but I doubt anything with regards to that has been updated.

I'd like to participate in the development of QOSF but at the same time I don't think there is any way to achieve that. Can someone please provide some feedback regarding current idea/plan for the foundation?

Thanks!

On the page there is only CC for python because it is mentioned that other languages do not provide for a fast retrieval. Can you expand on that?

It seems that there are many tools to evaluate CC for other languages (e.g. JavaScript should be equally as fast as python IMO): https://github.com/topics/cyclomatic-complexity

Another great resource that is free to use for OSS is CodeScene and provides more useful metrics beyond CC: https://codescene.io/

 Create an infographic offering a comprehensive overview of the connections between various projects within the quantum computing community. The goal is to have an easy visual representation of the quantum open source ecosystem for new people in the field.

• The style needs to be aesthetically coherent with the QOSF style 
• The infographic should offer a general overview of the connections between different projects 
• The infographic should be based on open-source technologies.
• Try to connect the dots and actions regarding the different types of software available.
• Identify the types of hardware used by each technology, such as trapped ions or superconductors.
• Separate the software for programming algorithms from the software for simulating hardware.
• Examples to follow:
  

Crear una infografía que ofrezca una visión global de las conexiones entre diversos proyectos de la comunidad de la computación cuántica. El objetivo es tener una representación visual sencilla del ecosistema cuántico de código abierto para nuevas personas en el campo.

• El estilo debe ser estéticamente coherente con el de QOSF.
• La infografía debe ofrecer una visión general de las conexiones entre los distintos proyectos
• La infografía debe basarse en tecnologías de código abierto.
• Intente unir los puntos y las acciones en relación con los diferentes tipos de software disponibles.
• Identifique los tipos de hardware utilizados por cada tecnología, como los iones atrapados o los superconductores.
• Incluya diferentes algoritmos, como puerta universal, adiabático y analógico-digital.

Updating the list of contributors in team.md is currently done manually. This should be automated with a script that pulls the authors of issues and MRs on all qosf repos, sorts them alphabetically and adds the corresponding HTML snippet to team.md

As the title.

https://www.twitter.com/qosfoundation

When I open Code and Learn sections, the menu is being displayed on top of the list (see below):

Safari version: Wersja 12.0.2 (14606.3.4)
MacOS: 10.14.2