Opened 7 years ago

Last modified 7 years ago

#880 assigned defect

show progress during opencl test

Reported by: pkienzle Owned by: wojciech
Priority: major Milestone: SasView 5.0.0
Component: SasView Keywords:
Cc: Work Package: SasView Bug Fixing


The tests run by the OpenCL config dialog can take a long time to run the first time, before any of the DLLs are compiled. The user needs to see that the tests are in progress, and ideally know how much longer the tests will take.

When running unit tests in verbose mode from the command line, each test is displayed as it is completed. The result is:

$ python -m sasmodels.model_test -v all
test_adsorbed_layer_python (__main__.ModelTestCase) ... ok
test_barbell_dll (__main__.ModelTestCase) ... ok
test_barbell_opencl (__main__.ModelTestCase) ... /usr/lib/python2.7/dist-packages/pyopencl/ CompilerWarning: Non-empty compiler output encountered. Set the environment variable PYOPENCL_COMPILER_OUTPUT=1 to see more.
  "to see more.", CompilerWarning)
test_bcc_paracrystal_dll (__main__.ModelTestCase) ... ok
test_bcc_paracrystal_opencl (__main__.ModelTestCase) ... ok
test_be_polyelectrolyte_python (__main__.ModelTestCase) ... ok

A dialog showing the test currently running and a progress bar showing k tests out of a total of n would give the user the feedback that they need. A cancel button would also be nice.

Change History (4)

comment:1 Changed 7 years ago by pkienzle

Compiling the DLLs in parallel would speed up the test. Maybe update sasmodels.core.precompile_dlls to operate with multiple threads, and call it before running the tests.

It may also be possible to precompile the OpenCL in parallel in advance, but this may depend on the particular driver.

comment:2 Changed 7 years ago by wojciech

  • Owner set to wojciech
  • Status changed from new to assigned

comment:3 Changed 7 years ago by krzywon

The Qt GUI console captures the stdout, so this is already solved there. Whether or not we want to put it into wx is a matter for debate.

comment:4 Changed 7 years ago by butler

  • Milestone changed from SasView 4.2.0 to SasView 5.0.0
Note: See TracTickets for help on using tickets.