Changeset fa374b0 in sasview


Ignore:
Timestamp:
Jul 30, 2018 10:25:32 AM (6 years ago)
Author:
Paul Kienzle <pkienzle@…>
Branches:
master, magnetic_scatt, release-4.2.2, ticket-1009, ticket-1094-headless, ticket-1242-2d-resolution, ticket-1243, ticket-1249, unittest-saveload
Children:
e2663b7
Parents:
2a6058c
Message:

Save before pushing… Fixes #1142

File:
1 edited

Legend:

Unmodified
Added
Removed
  • src/sas/sasgui/perspectives/calculator/pyconsole.py

    r2a6058c rfa374b0  
    3737    # run_one() tests first.  To fix the deeper problem we should either 
    3838    # remove caching from sasmodels.sasview_model.load_custom_model() or 
    39     # add caching to sasmodels.custom.load_custom_kernel_module(). 
     39    # add caching to sasmodels.custom.load_custom_kernel_module().  Another 
     40    # option is to add a runTests method to SasviewModel which runs the 
     41    # test suite directly from the model info structure.  Probably some 
     42    # combination of options: 
     43    #    (1) have this function (check_model) operate on a loaded model 
     44    #    so that caching isn't needed in sasview_models.load_custom_model 
     45    #    (2) add the runTests method to SasviewModel so that tests can 
     46    #    be run on a loaded module. 
     47    # 
     48    # Also, note that the model test suite runs the equivalent of the 
     49    # "try running the model" block below, and doesn't need to be run 
     50    # twice.  The reason for duplicating the block here is to generate 
     51    # an exception that show_model_output can catch.  Need to write the 
     52    # runTests method so that it returns success flag as well as output 
     53    # string so that the extra test is not necessary. 
    4054 
    4155    # check the model's unit tests run 
Note: See TracChangeset for help on using the changeset viewer.