This software was originally developed by the Billinge group as part
of the Distributed Data Analysis of Neutron Scattering Experiments
(DANSE) project funded by the US National Science Foundation under
grant DMR-0520547. Developments of PDFfit2 were funded by NSF grant
DMR-0304391 in the Billinge group, and with support from Michigan State
University and Columbia University. Any opinions, findings, and conclusions
or recommendations expressed in this material are those of the author(s)
and do not necessarily reflect the views of the respective funding bodies.
Subsequent development was done in the Billinge group at Columbia University
and then in collaboration between the Billinge group at Columbia and Pavol
Juhas at Brookhaven National Laboratory. Moving forward, PDFgui will be
maintained as a community project with contributions welcomed from many people.
If you use this program to do productive scientific research that leads
to publication, we ask that you acknowledge use of the program by citing
the following paper in your publication:
C. L. Farrow, P. Juhas, J. W. Liu, D. Bryndin, E. S. Bozin,
J. Bloch, Th. Proffen and S. J. L. Billinge, PDFfit2 and
PDFgui: computer programs for studying nanostructure in
crystals, J. Phys.: Condens. Matter 19, 335219 (2007)
Up to the release 1.1.2 (February 2017) the copyright was held by
the institutions that hosted the work as follows:
Copyright 2006-2007, Board of Trustees of Michigan State University,
Copyright 2008-2012, Board of Trustees of Columbia University in the
city of New York.
Copyright 2013, Brookhaven National Laboratory (Copyright holder
indicated in each source file).
As of February 2017, and the 1.1.2 release, PDFgui has moved to a shared copyright model.
PDFgui uses a shared copyright model. Each contributor maintains copyright over their
contributions to PDFgui. But, it is important to note that these contributions are
typically only changes to the repositories. Thus, the PDFgui source code, in its entirety,
is not the copyright of any single person or institution. Instead, it is the collective
copyright of the entire PDFgui Development Team. If individual contributors want to
maintain a record of what changes/contributions they have specific copyright on, they
should indicate their copyright in the commit message of the change, when they commit
the change to one of the PDFgui repositories.
The PDFgui Development Team is the set of all contributors to the PDFgui project.
A full list can be obtained from the git version control logs.
For more information please visit the project web-page:
https://www.diffpy.org
or email Prof. Simon Billinge at sb2896@columbia.edu
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
* Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
* Neither the name of the copyright holder nor the names of its
contributors may be used to endorse or promote products derived from
this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY COPYRIGHT HOLDER "AS IS". COPYRIGHT HOLDER
EXPRESSLY DISCLAIMS ANY AND ALL WARRANTIES AND CONDITIONS, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY, TITLE, FITNESS, ADEQUACY OR SUITABILITY
FOR A PARTICULAR PURPOSE, AND ANY WARRANTIES OF FREEDOM FROM
INFRINGEMENT OF ANY DOMESTIC OR FOREIGN PATENT, COPYRIGHTS, TRADE
SECRETS OR OTHER PROPRIETARY RIGHTS OF ANY PARTY. IN NO EVENT SHALL
COPYRIGHT HOLDER BE LIABLE TO ANY PARTY FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
THIS SOFTWARE OR RELATING TO THIS AGREEMENT, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.