|
1 | | -Copyright (c) 2024, The Trustees of Columbia University |
2 | | -in the City of New York. |
3 | | -All rights reserved. |
| 1 | +.. code-block:: text |
4 | 2 |
|
5 | | -This software was originally developed by the Billinge group as part |
6 | | -of the Distributed Data Analysis of Neutron Scattering Experiments |
7 | | -(DANSE) project funded by the US National Science Foundation under |
8 | | -grant DMR-0520547. Developments of PDFfit2 were funded by NSF grant |
9 | | -DMR-0304391 in the Billinge group, and with support from Michigan State |
10 | | -University and Columbia University. Any opinions, findings, and conclusions |
11 | | -or recommendations expressed in this material are those of the author(s) |
12 | | -and do not necessarily reflect the views of the respective funding bodies. |
13 | | -Subsequent development was done in the Billinge group at Columbia University |
14 | | -and then in collaboration between the Billinge group at Columbia and Pavol |
15 | | -Juhas at Brookhaven National Laboratory. Moving forward, PDFgui will be |
16 | | -maintained as a community project with contributions welcomed from many people. |
| 3 | + This software was originally developed by the Billinge group as part |
| 4 | + of the Distributed Data Analysis of Neutron Scattering Experiments |
| 5 | + (DANSE) project funded by the US National Science Foundation under |
| 6 | + grant DMR-0520547. Developments of PDFfit2 were funded by NSF grant |
| 7 | + DMR-0304391 in the Billinge group, and with support from Michigan State |
| 8 | + University and Columbia University. Any opinions, findings, and conclusions |
| 9 | + or recommendations expressed in this material are those of the author(s) |
| 10 | + and do not necessarily reflect the views of the respective funding bodies. |
| 11 | + Subsequent development was done in the Billinge group at Columbia University |
| 12 | + and then in collaboration between the Billinge group at Columbia and Pavol |
| 13 | + Juhas at Brookhaven National Laboratory. Moving forward, PDFgui will be |
| 14 | + maintained as a community project with contributions welcomed from many people. |
17 | 15 |
|
18 | | -If you use this program to do productive scientific research that leads |
19 | | -to publication, we ask that you acknowledge use of the program by citing |
20 | | -the following paper in your publication: |
| 16 | + If you use this program to do productive scientific research that leads |
| 17 | + to publication, we ask that you acknowledge use of the program by citing |
| 18 | + the following paper in your publication: |
21 | 19 |
|
22 | | - C. L. Farrow, P. Juhas, J. W. Liu, D. Bryndin, E. S. Bozin, |
23 | | - J. Bloch, Th. Proffen and S. J. L. Billinge, PDFfit2 and |
24 | | - PDFgui: computer programs for studying nanostructure in |
25 | | - crystals, J. Phys.: Condens. Matter 19, 335219 (2007) |
| 20 | + C. L. Farrow, P. Juhas, J. W. Liu, D. Bryndin, E. S. Bozin, |
| 21 | + J. Bloch, Th. Proffen and S. J. L. Billinge, PDFfit2 and |
| 22 | + PDFgui: computer programs for studying nanostructure in |
| 23 | + crystals, J. Phys.: Condens. Matter 19, 335219 (2007) |
26 | 24 |
|
27 | | -Up to the release 1.1.2 (February 2017) the copyright was held by |
28 | | -the institutions that hosted the work as follows: |
29 | | -Copyright 2006-2007, Board of Trustees of Michigan State University, |
30 | | -Copyright 2008-2012, Board of Trustees of Columbia University in the |
31 | | -city of New York. |
32 | | -Copyright 2013, Brookhaven National Laboratory (Copyright holder |
33 | | -indicated in each source file). |
| 25 | + Up to the release 1.1.2 (February 2017) the copyright was held by |
| 26 | + the institutions that hosted the work as follows: |
| 27 | + Copyright 2006-2007, Board of Trustees of Michigan State University, |
| 28 | + Copyright 2008-2012, Board of Trustees of Columbia University in the |
| 29 | + city of New York. |
| 30 | + Copyright 2013, Brookhaven National Laboratory (Copyright holder |
| 31 | + indicated in each source file). |
34 | 32 |
|
35 | | -As of February 2017, and the 1.1.2 release, PDFgui has moved to a shared copyright model. |
| 33 | + As of February 2017, and the 1.1.2 release, PDFgui has moved to a shared copyright model. |
36 | 34 |
|
37 | | -PDFgui uses a shared copyright model. Each contributor maintains copyright over their |
38 | | -contributions to PDFgui. But, it is important to note that these contributions are |
39 | | -typically only changes to the repositories. Thus, the PDFgui source code, in its entirety, |
40 | | -is not the copyright of any single person or institution. Instead, it is the collective |
41 | | -copyright of the entire PDFgui Development Team. If individual contributors want to |
42 | | -maintain a record of what changes/contributions they have specific copyright on, they |
43 | | -should indicate their copyright in the commit message of the change, when they commit |
44 | | -the change to one of the PDFgui repositories. |
| 35 | + PDFgui uses a shared copyright model. Each contributor maintains copyright over their |
| 36 | + contributions to PDFgui. But, it is important to note that these contributions are |
| 37 | + typically only changes to the repositories. Thus, the PDFgui source code, in its entirety, |
| 38 | + is not the copyright of any single person or institution. Instead, it is the collective |
| 39 | + copyright of the entire PDFgui Development Team. If individual contributors want to |
| 40 | + maintain a record of what changes/contributions they have specific copyright on, they |
| 41 | + should indicate their copyright in the commit message of the change, when they commit |
| 42 | + the change to one of the PDFgui repositories. |
45 | 43 |
|
46 | | -The PDFgui Development Team is the set of all contributors to the PDFgui project. |
47 | | -A full list can be obtained from the git version control logs. |
| 44 | + The PDFgui Development Team is the set of all contributors to the PDFgui project. |
| 45 | + A full list can be obtained from the git version control logs. |
48 | 46 |
|
49 | | -For more information please visit the project web-page: |
50 | | - https://www.diffpy.org |
51 | | -or email Prof. Simon Billinge at sb2896@columbia.edu |
| 47 | + For more information please visit the project web-page: |
| 48 | + https://www.diffpy.org |
| 49 | + or email Prof. Simon Billinge at sb2896@columbia.edu |
52 | 50 |
|
53 | | -Redistribution and use in source and binary forms, with or without |
54 | | -modification, are permitted provided that the following conditions are met: |
| 51 | + Redistribution and use in source and binary forms, with or without |
| 52 | + modification, are permitted provided that the following conditions |
| 53 | + are met: |
55 | 54 |
|
56 | | -1. Redistributions of source code must retain the above copyright notice, this |
57 | | - list of conditions and the following disclaimer. |
| 55 | + * Redistributions of source code must retain the above copyright |
| 56 | + notice, this list of conditions and the following disclaimer. |
58 | 57 |
|
59 | | -2. Redistributions in binary form must reproduce the above copyright notice, |
60 | | - this list of conditions and the following disclaimer in the documentation |
61 | | - and/or other materials provided with the distribution. |
| 58 | + * Redistributions in binary form must reproduce the above copyright |
| 59 | + notice, this list of conditions and the following disclaimer in the |
| 60 | + documentation and/or other materials provided with the distribution. |
62 | 61 |
|
63 | | -3. Neither the name of the copyright holder nor the names of its contributors |
64 | | - may be used to endorse or promote products derived from this software |
65 | | - without specific prior written permission. |
| 62 | + * Neither the name of the copyright holder nor the names of its |
| 63 | + contributors may be used to endorse or promote products derived from |
| 64 | + this software without specific prior written permission. |
66 | 65 |
|
67 | | -THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" |
68 | | -AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE |
69 | | -IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE |
70 | | -DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE |
71 | | -FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL |
72 | | -DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR |
73 | | -SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER |
74 | | -CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, |
75 | | -OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE |
76 | | -OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. |
| 66 | + THIS SOFTWARE IS PROVIDED BY COPYRIGHT HOLDER "AS IS". COPYRIGHT HOLDER |
| 67 | + EXPRESSLY DISCLAIMS ANY AND ALL WARRANTIES AND CONDITIONS, EITHER |
| 68 | + EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED |
| 69 | + WARRANTIES OF MERCHANTABILITY, TITLE, FITNESS, ADEQUACY OR SUITABILITY |
| 70 | + FOR A PARTICULAR PURPOSE, AND ANY WARRANTIES OF FREEDOM FROM |
| 71 | + INFRINGEMENT OF ANY DOMESTIC OR FOREIGN PATENT, COPYRIGHTS, TRADE |
| 72 | + SECRETS OR OTHER PROPRIETARY RIGHTS OF ANY PARTY. IN NO EVENT SHALL |
| 73 | + COPYRIGHT HOLDER BE LIABLE TO ANY PARTY FOR ANY DIRECT, INDIRECT, |
| 74 | + INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT |
| 75 | + NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF |
| 76 | + USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON |
| 77 | + ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT |
| 78 | + (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF |
| 79 | + THIS SOFTWARE OR RELATING TO THIS AGREEMENT, EVEN IF ADVISED OF THE |
| 80 | + POSSIBILITY OF SUCH DAMAGE. |
0 commit comments