csdms / dakotathon

99%

master: 96%

LAST BUILD ON BRANCH mdpiper/fix-multidim-parameter-study

branch: mdpiper/fix-multidim-parameter-study

CHANGE BRANCH

x

Reset

• mdpiper/fix-multidim-parameter-study
• 0.2
• master
• mdpiper/add-dyld_library_path
• mdpiper/add-examples
• mdpiper/add-new-examples
• mdpiper/add-new-uq-methods
• mdpiper/add-new-variable-types
• mdpiper/add-sampling-method
• mdpiper/allow-newer-openmpi
• mdpiper/check-install-process
• mdpiper/debug-install-failure
• mdpiper/disable-macos-tests
• mdpiper/fix-broken-build
• mdpiper/fix-broken-linux-build
• mdpiper/fix-broken-macos-py3-build
• mdpiper/fix-conda-dependencies
• mdpiper/fix-default-uq-experiments
• mdpiper/fix-lapack-issue
• mdpiper/fix-travis-build
• mdpiper/improve-code-health-and-coverage
• mdpiper/integrate-with-pymt
• mdpiper/make-tmpl-files
• mdpiper/package-maintenance
• mdpiper/preserve-obsolete-metadata
• mdpiper/refactor-into-subpackages
• mdpiper/remove-ez_setup
• mdpiper/rename-package
• mdpiper/simplify-Dakota-import
• mdpiper/test-on-python3
• mdpiper/update-bmi
• mdpiper/update-bmi-metadata
• mdpiper/update-build-for-trusty
• mdpiper/update-documentation
• mdpiper/update-travis-workflow
• mdpiper/updates-for-agu
• mdpiper/usability-enhancements
• mdpiper/use-dakota-binary
• v0.1
• v0.2
• v0.2.1
• v0.2.2
• v0.2.3
• v0.3
• v0.3.1
• v0.4
• v0.4.1
• v0.5

Build # 155

Build Type

push

travis-ci

Committed by mdpiper

Commit Message

Check that the default multidim parameter study uses bounds

This is a somewhat awkward issue in Dakota: the multidim parameter
study *method* must use *variables* with defined `upper_bounds` and
`lower_bounds`; therefore, information must be communicated across
control blocks. I've resolved this by applying bounds if they're not
set, but only in the Experiment, not in the MultidimParameterStudy
class.

Run Details

2460 of 2489 relevant lines covered (98.83%)

1.98 hits per line