Skip to content

Commit 7f23325

Browse files
authored
Make README great again.
1 parent 2695c77 commit 7f23325

File tree

1 file changed

+31
-17
lines changed

1 file changed

+31
-17
lines changed

README.md

Lines changed: 31 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -1,35 +1,36 @@
1-
# Welcome to the repository for quantumalgorithms.org
1+
2+
3+
[![quantumalgorithms.org](https://quantumalgorithms.org/images/mainlogo.png)](https://quantumalgorithms.org)
4+
5+
# README
26

37
[![Unitary Fund](https://img.shields.io/badge/Supported%20By-UNITARY%20FUND-brightgreen.svg?style=for-the-badge)](http://unitary.fund)
48

59

10+
611
This is the repository for [QuantumAlgorithms.org](https://quantumalgorithms.org).
712

813
This webiste is meant to be a set of lecture notes for students in quantum algorithms and quantum machine learning.
914
It will be updated regularly with new research material. The scope is to bridge the gap between introductory material in quantum computing and research-grade papers, standardize notation, and be an overfiew on the state of useful algorithms for quantum machine learning and information processing.
1015

1116

12-
The book is written in bookdown, an R-based extension of markdown (even if you don't need to know R at all, it's simply markdown with some latex).
1317

18+
## How to contribute:
1419

15-
## What to do
20+
The book is written in bookdown, an R-based extension of markdown (even if you don't need to know R at all, it's simply markdown with some latex).
21+
Download RStudio and make sure you can compile a book with bookdown on your computer. Once you have it, you can work on the book and submit a PR.
1622

17-
The current issues that we have, for which we are roughly organized as follows:
1823

19-
- minor issues:
20-
- proofreading
21-
- checking and expanding steps in calculations,
22-
- making sure things are written in good and clearn english
23-
- pointing out paragraphs that are not mathematically clear, or that could be expanded)
24-
- major contributions (like new chapters)
25-
- create and solve new exercise
26-
- address the TODOs that are inserted in the comments of the .Rmd files.
24+
Feel free to submit a PR with improvements in
2725

28-
Please refer to the file tipsandtricks.md for small but useful tips on Rmarkdown.
26+
- proofreading
27+
- checking and expanding steps in calculations,
28+
- pointing out sections are ambigious or hard to understand, or that can be explained better,
29+
- create and solve new exercise.
2930

30-
In any case, if you want to contribute, [drop me a line](mailto://[email protected])!
31+
For major contributions (like new chapters or new content), [drop us a line](mailto://[email protected])!
3132

32-
## How to render an algorithm for the book
33+
## How to write an algorithm
3334

3435
The book has some algorithms that are rendered as latex algorithms with a package for writing pseudocode.
3536
These algorithms are rendered as pdfs, and successively these files are rendered as png via a python script.
@@ -40,7 +41,7 @@ There are countless examples of algorithms included in the book, so you can copy
4041

4142

4243

43-
## Guidelines for writings
44+
## Style guide, tips&tricks.
4445

4546
- Use \ket{} and \bra{} instead of |x\rangle
4647
- \begin{equation} and \end{equation} in bookdown are not really working 100% of the time (check?), but they should be used throughout the whole book, as math book have all equation numbered.
@@ -49,4 +50,17 @@ There are countless examples of algorithms included in the book, so you can copy
4950
- Every time you compile, (and before doing the pull request) be sure to compile also the pdf version of the document. This becuase there are cases where the generation of the book in htlm succeed, but the pdf is failing for some reasons.
5051
- Use \~ before the citation.
5152
- We use runtime not run-time or run time.
52-
53+
- no space between a dollar sign for equations $ and the first character of the formula (otherwise you get an error)
54+
- currently, it's not possible to put latex in the names of the theorems,lemma, definitions. (do we know how to do it?) For example in the definition of the parametereization of the function $\mu$, I had to use the greek letter μ...
55+
- itemize made with - should start and end with a newline
56+
- the way to number equation is the following: (\#eq:raylight)
57+
- This is the templtae to use to create an issue automatically using the github action
58+
- always use thm, lem, cor, in references: \@ref(thm:qla).
59+
- grep "\`{lemma" * to have the list of all lemmas (or theorems) so after we can check if they are used correctly with \@ref() and there are no wrong \ref{}.
60+
- the correct way of doing todo is:
61+
<!--
62+
# TODO
63+
# labels:
64+
-->
65+
- If you need a fast way for translating citation from latex \cite{ciao} to markdown [@ciao], you can use \\cite{(.*?)} -----> [@$1]
66+
-

0 commit comments

Comments
 (0)