Changeset d15ce7c6 in sasview
- Timestamp:
- Sep 10, 2018 8:45:09 AM (6 years ago)
- Branches:
- master, magnetic_scatt, release-4.2.2, ticket-1009, ticket-1094-headless, ticket-1242-2d-resolution, ticket-1243, ticket-1249, unittest-saveload
- Children:
- c0c9a473
- Parents:
- 187a4a07
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
installers/README.txt
raa1e5a69 rd15ce7c6 31 31 aligned objects has been completely overhauled. It now differs from 32 32 previous versions. 33 - Plugin models, including sum /multiply models, have completely migrated33 - Plugin models, including sum|multiply models, have completely migrated 34 34 to the new infrastructure. NOTE that 3.x type models as well as early, 35 35 intermediate 4.x type models, including those generated by sum|multiply … … 98 98 Fixes # 838: Fix model download from marketplace 99 99 Fixes # 848: can't save analysis when only one fit page 100 Fixes # 849: Load Folder should ignore files starting with .100 Fixes # 849: Load Folder should ignore files starting with "." 101 101 Fixes # 852: More unit tests, especially for oriented or 2d models 102 102 Fixes # 854: remove unnecessary sleep() in fitting perspective … … 198 198 attention is drawn to the Changes section above. 199 199 200 200 201 - New in Version 4.2.0-Beta 201 202 ------------------------- … … 229 230 It is recommended that all users upgrade to this version 230 231 232 231 233 - New in Version 4.1.1 232 234 -------------------- … … 241 243 - Fixes an issue with the NXcanSAS data loader 242 244 - Updated tutorials for SasView 4.x.y 245 243 246 244 247 - New in Version 4.1.0 … … 646 649 ============================= 647 650 648 *** Note 1: The easiest approach to setting up the proper environment to 649 build from source is to use conda. Instructions for setting up 650 using conda can be found at: 651 http://trac.sasview.org/wiki/DevNotes/CondaDevSetup 652 *** Note 2: If you have EXE or ZIP SasView installer, you won't need any of 653 the following. However it is highly recommended that any 654 previous versions be un-installed prior to installing the 655 new version. 656 *** Note 3: Much more information is available at www.sasview.org under links. 657 Look in the 'For Developers' section and particularly the wiki at 658 www.sasview.org/trac/wiki. 651 *** Note 1: If you have a SasView installer (.EXE or .MSI), you do not need to 652 worry about any of the following. However, it is highly recommended 653 that any previous versions of SasView are uninstalled prior to 654 installing the new version UNLESS you are installing SasView to 655 versioned folders. 656 657 *** Note 2: The easiest approach to setting up the proper environment to 658 build from source is to use Conda. Instructions for setting up 659 and using Conda can be found at: 660 http://trac.sasview.org/wiki/DevNotes/CondaDevSetup 661 662 *** Note 3: Much more information is available at www.sasview.org under 663 links/downloads. In particular, look in the 'For Developers' section. 664 Also have a look at http://trac.sasview.org/. 659 665 660 666 2.1- System Requirements … … 662 668 - We currently use Python 2.7 663 669 664 2.2- Installing from source 670 2.2- Package Dependencies 671 - Ensure the required dependencies are installed 672 - For the latest list of dependencies see the appropriate yml file in 673 the SasView repo at sasview/build_tools/conda/ymls 674 675 2.3- Installing from Source 665 676 - Get the source code 666 - to follow the current development version from source control use 667 git clone https://github.com/SasView/sasview.git 668 git clone https://github.com/Sasview/sasmodels.git 669 git clone https://github.com/bumps/bumps.git 670 671 - Build, install and run a specific release 672 - make sure the requirements below are already installed 673 - retrieve the source from https://github.com/SasView/sasview/releases 674 - open a command line window in the 'sasview-x.x.x' directory 675 - run 'python setup.py install' 676 - run 'python sasview.py' under the 'sasview' folder. 677 678 - Build, install and run the current development version 679 - clone the source from git; also clone bumps, which is developed in parallel 680 git clone https://github.com/SasView/sasview.git 681 git clone https://github.com/Sasview/sasmodels.git 682 git clone https://github.com/bumps/bumps.git 683 - open a command line window in the 'sasview' directory 684 - run 'python setup.py build' 685 - run 'python run.py'; this runs from the source directories, so you 677 - create a folder to contain the source code; if working with 678 multiple versions you might want to use versioned folder names 679 like 'sasview-x.x.x' 680 - open a command line window in the source code folder 681 - to get the CURRENT DEVELOPMENT VERSION from source control use 682 git clone https://github.com/SasView/sasview.git sasview 683 git clone https://github.com/Sasview/sasmodels.git sasmodels 684 git clone https://github.com/bumps/bumps.git bumps 685 - to get a SPECIFIC RELEASE VERSION from source control go to 686 https://github.com/SasView/sasview/releases 687 and download the required zip or tar.gz file. Unzip/untar it 688 to the source code folder. 689 690 2.4- Building and Installing 691 - use 'python setup.py build' 692 - use 'python setup.py install' 693 To build the documentation 694 - use'python setup.py docs' 695 696 2.5- Running SasView 697 - use 'python run.py'; this runs from the source directories, so you 686 698 don't have to rebuild every time you make a change, unless you are 687 changing the C model files 688 689 - For the latest list of dependencies see the appropriate yml file in 690 the SasView repo at sasview/build_tools/conda/ymls 699 changing the C model files. 700 - if using Conda the above command will also build SasView, but you 701 must issue 'activate sasview' first. 691 702 692 703 … … 694 705 =============== 695 706 696 697 4.2.0 - All systmes 707 4.2.0 - All systems 698 708 There are currently no major known issues. A full list of known bugs and 699 709 feature requests by release version that users may wish to be aware of
Note: See TracChangeset
for help on using the changeset viewer.