Skip to content
This repository has been archived by the owner on May 25, 2021. It is now read-only.

Commit

Permalink
GitBook: [master] 2 pages modified
Browse files Browse the repository at this point in the history
  • Loading branch information
Remco de Boer authored and gitbook-bot committed Mar 7, 2019
1 parent 3aab9d1 commit a124dd4
Show file tree
Hide file tree
Showing 2 changed files with 7 additions and 1 deletion.
6 changes: 6 additions & 0 deletions appendices/glossary.md
Original file line number Diff line number Diff line change
Expand Up @@ -36,6 +36,12 @@ You only generate events with decays that are of interest to your analysis.

You generate event as completely as possible. Since this takes a lot of computing resources, one usually makes use of the data sets that were reconstructed by the BOSS team for your version of BOSS. For the file locations of inclusive $$J/\psi$$ samples, see [this page](https://docbes3.ihep.ac.cn/~offlinesoftware/index.php/Jpsi_data) \[requires login\].

## S

Semantic versioning

See [here](https://semver.org/). This is essentially a numbering scheme used for tagging versions of a package. Within BOSS, a package can for instance be given tag `Package-01-04-03`, where `01` is the major ID, `04` the minor ID, and `03` the patch ID.

## U

### UCAS
Expand Down
2 changes: 1 addition & 1 deletion introduction/getting-started/setup-package.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ Here, the name `MyFirstPackage` is just an example name of the package. The name
* `minor id` if you only made changes that are backward compatible, such as new functionality;
* `major id` if you modified the interface \(header file\) that require you to completely recompile the package.

The above only becomes relevant as when you start developing packages, so you can forget about this for now.
For more information on this numbering scheme, read more about this [**semantic versioning** here](https://semver.org/) \(many languages available\). The above only becomes relevant as when you start developing packages, so you can forget about this for now.

The result of the above command is a new folder, that we'll navigate into:

Expand Down

0 comments on commit a124dd4

Please sign in to comment.