Note
-Currently automake is still supported but soon will be replaced by cmake. Only follow -the automake procedure if you have good reasons.
-The configure script for musrfit has now a couple of more tags/options, which are:
-For a typical setup on a RHEL system it could look like this
-$ ./configure --enable-ASlibs --enable-BMWlibs --enable-NeXus --with-dks=$HOME/Apps/DKS/exec --enable-dks --prefix=$ROOTSYS
-After
-$ make
-$ make install
-and updating the shared library lookup table (only needed for Linux)
-$ /sbin/ldconfig # as superuser / root
-you are done with the setup.
-There is on more configuration switch
@@ -201,7 +168,7 @@ $ make installFor a typical setup on a RHEL or macOS system it could look like this
-$ cmake ../ -DCMAKE_INSTALL_PREFIX=$ROOTSYS -DASlibs=1 -DBMWlibs=1 -Dnexus=1
+$ cmake ../ -DCMAKE_INSTALL_PREFIX=$ROOTSYS -DASlibs=1 -DBMWlibs=1 -Dnexus=1 -Ddks=1
After
@@ -354,12 +321,12 @@ The only thing you need DKS
previous |
- musrfit 1.4.1 documentation »
+ musrfit 1.4.2 documentation »
Apart from GCC, the GNU Compiler Collection (gcc, g++), the GNU build tools autoconf, -automake, and libtool are needed, if you want to build musrfit via the automake toolchain. -The automake toolchain will eventually be droped in upcoming releases. -If you plan to use the cmake toolchain (preferred way), cmake. Furthermore the helper tool pkg-config is -needed and musrfit requires the installation of a few open-source libraries and programs including their header packages:
+Apart from GCC, the GNU Compiler Collection (gcc, g++), the build tool cmake is needed. Furthermore the helper +tool pkg-config needs to be in place, and musrfit requires the installation of a few open-source libraries and programs including +their header packages:
Native MS Windows support is currently not available. Potential ways to get musrfit running are:
Only if musrfit should support reading/writing data files in the NeXus format the further required software has to be set up. The required libraries and header files could either be available through the user’s -GNU/Linux distribution or if this is not the case, the packages can be installed from the source code. E.g. on -Red Hat-like systems binary packages for MXML, HDF4, and HDF5 might be called mxml, mxml-devel, -hdf, hdf-devel, hdf5, hdf5-devel, on Debian-like systems libmxml1, libmxml-dev, libhdf4-dev, libhdf5-dev.
+GNU/Linux distribution or if this is not the case, the packages can be installed from the source code. The necessary +packages to build NeXus are MXML, (HDF4), and HDF5. This means, for a rpm-package based distro try something like: +++++$ yum install mxml-devel hdf-devel hdf5-devel +
and on a deb-package based distro try something like:
++++$ apt-get install libmxml-dev libhdf4-dev libhdf5-dev +
Note
HDF4 support within NeXus will be dropped by musrfit in the near future. If you not urgently need @@ -211,9 +220,8 @@ $ sudo make install
ROOT 5.34/xx is supported as legacy version only! The default now will be ROOT 6.xx/yy!
The ROOT framework may or may not be part of the GNU/Linux distribution. Some distributions are packing ROOT in a -manner incompatible with the way it is needed for musrfit, though the situation is improving. If you are +manner incompatible with the way it is needed by musrfit, though the situation is improving. If you are experienced enough you can try the packed ROOT version. Often ROOT is split in many sub-packages. Install the necessary ones (guess from the description below). One Warning: if the ROOT packages are upgraded after a yum update (apt-get update; apt-get upgrade) you might need to recompile musrfit. If you are not sure about @@ -235,12 +243,12 @@ be added starting with a ‘#’ which can be omitted. They are only the $ # creat the Apps directory if not already present $ mkdir Apps $ cd Apps -$ git clone http://root.cern.ch/git/root.git +$ git clone http://github.com/root-project/root.git $ cd root $ git tag -l -$ # git tag -l will list all available tags. In the next command choose the tag v6-14-00 +$ # git tag -l will list all available tags. In the next command choose the tag v6-16-00 $ # or the latest official release number -$ git checkout -b v6-14-00 v6-14-00 +$ git checkout -b v6-16-00 v6-16-00 $ # now ROOT is ready to be configured. Below you will find the minimal ROOT configuration needed. $ # since we are using cmake build now, first we will need to create the build directory. $ mkdir root_build @@ -284,20 +292,18 @@ $ cmake --build ./ --clean-first
When all required software has been set up with the musrfit installation can be proceeded. First, the most +
When all required software has been set up you can proceed with the musrfit installatio. First, the most recent source code should be downloaded. The preferred way of doing so is to clone the musrfit repository via git. Assuming the code should be located in $HOME/Apps this is achieved most easily calling from the terminal
$ cd $HOME/Apps
$ git clone https://bitbucket.org/muonspin/musrfit.git
-$ # Only if legacy ROOT 5.xx.yy is used include the next line
-$ cd musrfit; git checkout root5
+$ cd musrfit
or
$ cd $HOME/Apps
$ git clone git://gitlab.psi.ch/nemu/musrfit.git
-$ # Only if legacy ROOT 5.xx.yy is used include the next line
-$ cd musrfit; git checkout root5
+$ cd musrfit
Update: If a local repository clone is already present (it needs to be newer than Dec. 2016), one can update it using:
$ cd $HOME/Apps/musrfit
$ git pull
-Now, depending whether you follow the automake or cmake tool chain you do
-automake toolchain:
-$ make uninstall
-$ make clean
-$ make
-$ make install
-or
-cmake toolchain:
-$ cd build
+$ cd build
$ xargs rm < install_manifest.txt
$ cmake --build ./ --clean-first
$ make install
As an alternative (if git is not available), the source code can also be downloaded from the following web-page: musrfit at bitbucket
-After the source-code extraction the autogen.sh script is called to prepare the build environment. -If it has been executed successfully the configure script should be ready to collect all the information needed -to create the Makefiles. If musrfit should support NeXus data files this has to be enabled by specifying the ---enable-NeXus switch when calling configure. For an overview of all available options just call ./configure --help. -Besides the standard options there are a few special options which should be mentioned here:
-Normally it should not be necessary to make use of any of the options except for specifying the installation path with --prefix. The -other paths should be detected automatically. If this does not work for some reason the configure script will terminate and ask for the -information. When the configure script has been called successfully everything is ready for building the musrfit libraries and executables. -A standard installation sequence (without NeXus support) might then look like (In case the normal user has no write permissions to the -$ROOTSYS and the installation path the “make install” commands have to be executed as superuser.):
-$ cd $HOME/Apps/musrfit
-$ sh autogen.sh
-$ ./configure --prefix=$ROOTSYS
-$ make
-$ make install
-$ /sbin/ldconfig # (as superuser)
-In order to finish the installation of musrfit two more things should be done:
-musredit¶
+musredit¶
In the latest version of musrfit the configure script tries to determine automatically the highest available Qt version. -In case this is found, the editor musredit is built already together with musrfit. If not, one can try to call -the configure script with the - -with-qt5 option (automake). cmake will determine everthing automatically. +In case this is found, the editor musredit is built already together with musrfit. To install this editor separately, i.e. by “hand” do
$ cd $HOME/Apps/musrfit/src/musredit_qt5 $ # for some distributions you will need qmake-qt5 for the next command @@ -505,7 +447,7 @@ Please also be aware of the fact that the X server which is going to be installeRequirements¶
--Setting up Cygwin¶
+Setting up Cygwin¶
For the start go to the Cygwin website, download the setup file and use it to install Cygwin 1.7 or newer. During the installation process you will be asked where you want to install Cygwin and normally the default choice should just be fine. At some point you will be asked which packages should be installed. Make sure that you choose at least the following (or packages with revisions close @@ -552,8 +494,8 @@ the later handling will be easier if a symbolic link to these files is created n
-Everything but ROOT and NeXus¶
-Installation of NeXus requirements (optional)¶
++Installation of NeXus requirements (optional)¶
Only if musrfit should support reading data files in the NeXus format the further required software has to be set up. Under Cygwin of all the required libraries only HDF5 is available. The packages hdf5 and libhdf5-devel can be installed through the Cygwin setup. One should also make sure that bison, flex @@ -597,8 +539,8 @@ $ make install
--ROOT¶
++ROOT¶
In order to install the ROOT system, there are two possibilities:
Download the precompiled Cygwin GCC 4.3 (or newer) package of the most recent ROOT version @@ -639,8 +581,8 @@ for the user Username
Afterwards close the Cygwin shell and reopen it again for the installation of musrfit.
-musrfit¶
++musrfit¶
First, the most recent source code should be downloaded. The preferred way of doing so is to clone the musrfit repository via git. Assuming the code should be located in ~/musrfit this is achieved most easily calling from the terminal
-$ cd @@ -659,58 +601,8 @@ $ git pullAs an alternative (if git is not available), the source code can also be downloaded from the following web-page: musrfit at bitbucket.
---musrfit build with automake¶
-After the source-code extraction the autogen.sh script is called to prepare the build environment. -If it has been executed successfully the configure script should be ready to collect all the information -needed to create the Makefiles. If musrfit should support NeXus data files this has to be enabled by -specifying the --enable-static --enable-NeXus switches when calling configure. For an overview of all -available options just call ./configure --help. Besides the standard options there are a few special -options which should be mentioned here:
--
-- - -prefix
-- Specify the installation prefix, e.g. /opt/root-system (by default: /usr/local)
-- - -with-rootsys
-- Specify the top of the ROOT installation directory, e.g. /opt/root-system
-- - -with-fftw3
-- Specify the prefix of the FFTW3 installation. e.g. /usr/local or /usr
-- - -with-gsl
-- Set the prefix of the GSL installation, e.g. /usr/local or /usr
-- - -with-boostinc
-- Set the path to the header files of the Boost installation, e.g. /usr/local/include or /usr/include
-- - -with-hdf4
-- Set the prefix of the HDF4 installation, e.g. /usr/local (only useful in conjunction with the NeXus support)
-- - -with-hdf5
-- Set the prefix of the HDF5 installation, e.g. /usr (only useful in conjunction with the NeXus support)
-- - -with-nexus
-- Set the prefix of the NeXus installation, e.g. /usr/local (only useful in conjunction with the NeXus support)
-- - -with-qt3
-- Set the prefix of the Qt3 installation, e.g. /usr/lib/qt-3.3 (only useful in conjunction with building musrgui)
-- - -with-qt4
-- Set the prefix of the Qt4 installation, e.g. /usr/lib/qt47 (only useful in conjunction with building musredit)
-- - -with-qt5
-- Set the prefix of the Qt5 installation, e.g. /usr/lib/qt56 (only useful in conjunction with building musredit)
-- - -enable-NeXus
-- Enable the support of NeXus data files (requires the HDF4, HDF5 and NeXus libraries to be installed).
-- - -disable-editor
-- Disable the integrated building of musredit/musrgui.
-- - -disable-omp
-- Switches off the OpenMP features of musrfit (parallelization of the \(\chi^2\) calculation when compiled with GCC ≥ 4.2)
-Normally it should not be necessary to make use of any of the options except for specifying the installation path with --prefix. -The other paths should be detected automatically. If this does not work for some reason the configure script will terminate and -ask for the information. When the configure script has been called successfully everything is ready for building the musrfit -libraries and executables. A standard installation sequence (without NeXus support) might then look like:
---$ cd musrfit -$ sh autogen.sh -$ ./configure --prefix=$ROOTSYS -$ make -$ make install ---musredit¶
++musredit¶
In the latest version of musrfit the configure script tries to determine automatically if Qt4.5 or higher is set up on the machine. In case this is found, the editor musredit is built -readily with musrfit. If not, one can either try to call the configure script with the ---with-qt4 option or install this editor separately, .e.g.:
+readily with musrfit. If not, try the following:@@ -780,14 +671,14 @@ musredit &$ cd src/musredit $ qmake-qt4 musredit.pro-musrgui (obsolate)¶
++-musrgui (obsolate)¶
If Qt4.5 or higher is not available but Qt3 is set up musrgui can be installed. For this please follow the instructions for the musredit installation where simply every musredit occurrence has to be replaced by musrgui, and qt4 is replaced by qt3.
-Check the installation¶
++Check the installation¶
In order to perform a quick test for finding out if the installation has been completed successfully, a few msr files together with the corresponding data files can be found in the musrfit source tree at doc/examples/. @@ -819,7 +710,7 @@ or Fink — In the following, both possibilities (using MacPorts or Fink) are described but it is emphasized here that it should be followed only one of the possible routes .
-Requirements (MacPorts)¶
+Requirements (MacPorts)¶
Before proceeding with the usage of the MacPorts system first a few useful tools provided by Apple together with OS X (on the installation DVD/CDs) should be installed:
@@ -838,7 +729,7 @@ $ sudo xcodebuild -license
- X11
- The X-window system is automatically installed on 10.5 Leopard and 10.6 Snow Leopard. For some other versions you also -will need to install XQuartz <http://xquartz.macosforge.org/trac>. If ROOT runs without XQuartz do not +will need to install XQuartz. If ROOT runs without XQuartz do not install it.
After installing the Xcode tools go to the MacPorts install page, download @@ -876,8 +767,8 @@ add a new line pointing to your local copy, e.g.
With Qt5, musredit will be installed. If it happens that you used musrgui in the past, please change over to musredit since there will be no further development for musrgui anymore!
---Installation of NeXus requirements (optional)¶
++Installation of NeXus requirements (optional)¶
Only if musrfit should support reading data files in the NeXus format the further required packages are set up:
@@ -906,21 +797,21 @@ $ sudo make install$ sudo port -v install hdf4 hdf5-@@ -2238,12 +2238,12 @@ In case this cannot be ensured, the parallelization can be disabled by ̵ROOT¶
-ROOT 5.34/xx is supported as legacy version only! The default now will be ROOT 6.xx/yy!
++ROOT¶
+The default ROOT version is based on ROOT 6.xx/yy!
@@ -934,12 +825,12 @@ to install it somewhere else, just systematically replace the related terms of t For the following list of commands the ‘$’ will be given, the command prompt. Do not enter it! Also some comments will be added starting with a ‘#’ which can be omitted. They are only there to explain what is going on.ROOT installed via package installer¶
The lazy way to get ROOT installed is via package installer. If your macOS is directly supported by the ROOT people you can download the package installer from the ROOT download page. Choose the latest ROOT release and download you macOS version dmg-file, e.g. for macOS 10.13 (High Sierra) -it is at the time of writting root_v6.14.00.macosx64-10.13-clang91.dmg. After the installation +it is at the time of writting root_v6.16.00.macosx64-10.13-clang91.dmg. After the installation ROOT will be installed under /Application as owner root. In order to ease your life for the steps to follow and assuming you are the only guy working on your Mac, you could change the owner and group of the ROOT directory:
$ cd /Applications -$ sudo chown -R <username> root_v6.14.00 -$ sudo chgrp -R staff root_v6.14.00 -$ sudo ln -s root_v6.14.00 root +$ sudo chown -R <username> root_v6.16.00 +$ sudo chgrp -R staff root_v6.16.00 +$ sudo ln -s root_v6.16.00 root$ cd $HOME/Applications -$ git clone http://root.cern.ch/git/root.git +$ git clone http://github.com/root-project/root.git $ cd root $ git tag -l $ # git tag -l will list all available tags. In the next command choose the tag v6-10-xx -$ # where xx is the highest listed number, e.g. v6-14-00 -$ git checkout -b v6-14-00 v6-14-00 +$ # where xx is the highest listed number, e.g. v6-16-00 +$ git checkout -b v6-16-00 v6-16-00 $ # now ROOT is ready to be configured. Below you will find the minimal ROOT configuration needed. $ # We will use the cmake out-of-source approach here. $ mkdir root_build @@ -1000,7 +891,7 @@ launchctl setenv LD_LIBRARY_PATH $LD_LIBRARY_PATH-Requirements (Fink)¶
+Requirements (Fink)¶
Before proceeding with the usage of the Fink system first a few useful tools provided by Apple together with OS X (on the installation DVD/CDs) should be installed:
- Xcode
@@ -1014,7 +905,7 @@ $ sudo xcodebuild -license- X11
- The X-window system is automatically installed on 10.5 Leopard and 10.6 Snow Leopard. For some other versions you also -will need to install XQuartz <http://xquartz.macosforge.org/trac>. If ROOT runs without XQuartz do not +will need to install XQuartz. If ROOT runs without XQuartz do not install it.
After installing the Xcode tools go to the Fink download page, @@ -1058,8 +949,8 @@ specific location, the later handling will be easier if a symbolic link to this
where x_yy_z has to be substituted by the correct version number, e.g. 1_63_0.
--diff --git a/doc/html/user-manual.html b/doc/html/user-manual.html index 25a0005f..5b10f3a7 100644 --- a/doc/html/user-manual.html +++ b/doc/html/user-manual.html @@ -6,7 +6,7 @@ -Installation of NeXus requirements (optional)¶
++-Installation of NeXus requirements (optional)¶
Only if musrfit should support reading data files in the NeXus format the further required packages can be installed through Fink (check for the most recent versions):
libjpeg hdf hdf5-cpp11 hdf5-cpp11-shlibs @@ -1088,21 +979,21 @@ $ sudo make install-@@ -662,12 +662,12 @@ K(m)&=\int_0^{\pi/2}\frac{\mathrm d\varphi}{\sqrt{1-m^2\sin^2{\varphi}}},\enROOT¶
-ROOT 5.34/xx is supported as legacy version only and will likely to be dropped in 2018. The default now is ROOT 6.xx/yy!
++-ROOT¶
+The default ROOT version is based on ROOT 6.xx/yy!
@@ -1116,12 +1007,12 @@ to install it somewhere else, just systematically replace the related terms of t For the following list of commands the ‘$’ will be given, the command prompt. Do not enter it! Also some comments will be added starting with a ‘#’ which can be omitted. They are only there to explain what is going on.ROOT installed via package installer¶
The lazy way to get ROOT installed is via package installer. If your macOS is directly supported by the ROOT people you can download the package installer from the ROOT download page. Choose the latest ROOT release and download you macOS version dmg-file, e.g. for macOS 10.13 (High Sierra) -it is at the time of writting root_v6.14.00.macosx64-10.13-clang91.dmg. After the installation +it is at the time of writting root_v6.16.00.macosx64-10.13-clang91.dmg. After the installation ROOT will be installed under /Application as owner root. In order to ease your life for the steps to follow and assuming you are the only guy working on your Mac, you could change the owner and group of the ROOT directory:
$ cd /Applications -$ sudo chown -R <username> root_v6.14.00 -$ sudo chgrp -R staff root_v6.14.00 -$ sudo ln -s root_v6.14.00 root +$ sudo chown -R <username> root_v6.16.00 +$ sudo chgrp -R staff root_v6.16.00 +$ sudo ln -s root_v6.16.00 root$ cd $HOME/Applications -$ git clone http://root.cern.ch/git/root.git +$ git clone http://github.com/root-project/root.git $ cd root $ git tag -l $ # git tag -l will list all available tags. In the next command choose the tag v6-10-xx -$ # where xx is the highest listed number, e.g. v6-14-00 -$ git checkout -b v6-14-00 v6-14-00 +$ # where xx is the highest listed number, e.g. v6-16-00 +$ git checkout -b v6-16-00 v6-16-00 $ # now ROOT is ready to be configured. Below you will find the minimal ROOT configuration needed. $ # We will use the cmake out-of-source approach here. $ mkdir root_build @@ -1181,22 +1072,20 @@ launchctl setenv LD_LIBRARY_PATH $LD_LIBRARY_PATH--musrfit¶
++musrfit¶
First, the most recent source code should be downloaded. First, the most recent source code should be downloaded. The preferred way of doing so is to clone the musrfit repository via git. Assuming the code should be located in ~/Applications/musrfit this is achieved most easily calling from the termin
$ cd ~/Applications $ git clone https://bitbucket.org/muonspin/musrfit.git -$ # Only if legacy ROOT 5.xx.yy is used include the next line -$ cd musrfit; git checkout root5 +$ cd musrfitor
$ cd ~/Applications $ git clone git://gitlab.psi.ch/nemu/musrfit.git -$ # Only if legacy ROOT 5.xx.yy is used include the next line -$ cd musrfit; git checkout root5 +$ cd musrfitIf a local repository clone is already present, one can update it using:
@@ -1206,59 +1095,8 @@ $ git pullAs an alternative (if git is not available), the source code can also be downloaded from the following web-page: musrfit at bitbucket.
---musrfit build with automake¶
-After the source-code extraction the autogen.sh script is called to prepare the build environment. -If it has been executed successfully the configure script should be ready to collect all the information needed -to create the Makefiles. If musrfit should support NeXus data files this has to be enabled by specifying the ---enable-NeXus switch when calling configure. For an overview of all available options just call ./configure --help. -Besides the standard options there are a few special options which should be mentioned here:
--
-- - -prefix
-- Specify the installation prefix, e.g. $ROOTSYS if already defined (by default: /usr/local).
-- - -with-rootsys
-- Specify the top of the ROOT installation directory, e.g. $ROOTSYS if already defined.
-- - -with-fftw3
-- Specify the prefix of the FFTW3 installation. e.g. /usr/local or /usr.
-- - -with-gsl
-- Set the prefix of the GSL installation, e.g. /usr/local or /usr.
-- - -with-boostinc
-- Set the path to the header files of the Boost installation, e.g. /usr/local/include or /usr/include.
-- - -with-hdf4
-- Set the prefix of the HDF4 installation, e.g. /usr/local (only useful in conjunction with the NeXus support).
-- - -with-hdf5
-- Set the prefix of the HDF5 installation, e.g. /usr (only useful in conjunction with the NeXus support).
-- - -with-nexus
-- Set the prefix of the NeXus installation, e.g. /usr/local (only useful in conjunction with the NeXus support).
-- - -with-qt3
-- Set the prefix of the Qt3 installation, e.g. /usr/lib/qt-3.3 (only useful in conjunction with building musrgui).
-- - -with-qt4
-- Set the prefix of the Qt4 installation, e.g. /usr/lib/qt47 (only useful in conjunction with building musredit).
-- - -with-qt5
-- Set the prefix of the Qt5 installation, e.g. /usr/lib64 (only useful in conjunction with building musredit).
-- - -enable-NeXus
-- Enable the support of NeXus data files (requires the HDF4, HDF5 and NeXus libraries to be installed).
-- - -disable-editor
-- Disable the integrated building of musredit/musrgui.
-- - -disable-omp
-- Switches off the OpenMP features of musrfit (parallelization of the \(\chi^2\) calculation when compiled with GCC ≥ 4.2).
-Normally it should not be necessary to make use of any of the options except for specifying the installation path with --prefix. The -other paths should be detected automatically. If this does not work for some reason the configure script will terminate and ask for the -information. When the configure script has been called successfully everything is ready for building the musrfit libraries and executables. -A standard installation sequence (without NeXus support) might then look like (In case the normal user has no write permissions to the -$ROOTSYS and the installation path the “make install” commands have to be executed as superuser.):
---$ cd $HOME/Apps/musrfit -$ sh autogen.sh -$ ./configure --prefix=$ROOTSYS -$ make -$ make install -$ /sbin/ldconfig # (as superuser) ---musrfit last step of the installation¶
++musrfit last step of the installation¶
In order to finish the installation of musrfit two more things should be done:
-diff --git a/doc/html/user-libs.html b/doc/html/user-libs.html index 5dddef1f..0b91497e 100644 --- a/doc/html/user-libs.html +++ b/doc/html/user-libs.html @@ -6,7 +6,7 @@ -musredit¶
++-musredit¶
In the latest version of musrfit the configure script tries to determine automatically the highest available Qt version. In case this is found, the editor musredit is built already together with musrfit. -If not, one can try to call the configure script with the –with-qt5 option (automake). cmake will -determine everthing automatically. To install this editor separately, i.e. by “hand” do
+If not, try the following:$ cd $HOME/Apps/musrfit/src/musredit_qt5 $ # for some distributions you will need qmake-qt5 for the next command $ qmake musredit.pro @@ -1353,8 +1190,8 @@ accomplish that, add the following lines to-@@ -443,12 +443,12 @@ For a complete description please refer to the manuals of previous | -Check the installation¶
++diff --git a/doc/html/tutorial.html b/doc/html/tutorial.html index 14bc3db4..fea64867 100644 --- a/doc/html/tutorial.html +++ b/doc/html/tutorial.html @@ -6,7 +6,7 @@ -Check the installation¶
In order to perform a quick test for finding out if the installation has been completed successfully, a few msr files together with the corresponding data files can be found in the musrfit source tree at doc/examples/. If musrgui has been installed, just open one of the test-*.msr files in the editor and test the musrfit @@ -1386,7 +1223,6 @@ $ musrview test-histo-ROOT-NPP.msr
- musrfit @@ -1400,41 +1236,39 @@ $ musrview test-histo-ROOT-NPP.msr
- Requirements
-- musrfit
- Mac OS X / macOS @@ -1481,12 +1315,12 @@ $ musrview test-histo-ROOT-NPP.msr
- previous |
-- musrfit 1.4.1 documentation »
+- musrfit 1.4.2 documentation »
Tutorial for musrfit — musrfit 1.4.1 documentation +Tutorial for musrfit — musrfit 1.4.2 documentation @@ -14,7 +14,7 @@ - + @@ -41,7 +41,7 @@- previous |
-- musrfit 1.4.1 documentation »
+- musrfit 1.4.2 documentation »
- musrfit 1.4.1 documentation »
+- musrfit 1.4.2 documentation »
Documentation of user libs (user functions) — musrfit 1.4.1 documentation +Documentation of user libs (user functions) — musrfit 1.4.2 documentation @@ -14,7 +14,7 @@ - + @@ -41,7 +41,7 @@- previous |
-- musrfit 1.4.1 documentation »
+- musrfit 1.4.2 documentation »
- previous |
-- musrfit 1.4.1 documentation »
+- musrfit 1.4.2 documentation »
User manual — musrfit 1.4.1 documentation +User manual — musrfit 1.4.2 documentation @@ -14,7 +14,7 @@ - + @@ -41,7 +41,7 @@- previous |
-- musrfit 1.4.1 documentation »
+- musrfit 1.4.2 documentation »
- previous |
-- musrfit 1.4.1 documentation »
+- musrfit 1.4.2 documentation »