Vytautas Jancauskas
Vytautas Jancauskas
What is the use case here?
Is it not possible to do 2. as part of an EasyVVUQ workflow?
The basic idea would be as follows - create an actions chain that does the first part and a separate one that does the third part. Set the first part...
well it needs to work, so we need to figure out why that is and how to prevent it
What exactly doesn't work? Looking at the code again I see that I've added changes precisely for this case (for example the run status will only be set to collated...
Simplest way is to use the "replace_actions" method of the Campaign. It is by itself hacky but simple. https://github.com/UCL-CCS/EasyVVUQ/blob/efa979589c58e844853c3d8dcafbc1f53f29f28c/easyvvuq/campaign.py#L270
The less code in the repository the better.
What does that mean, exactly?
oh you will need to change test_mc_analysis.py, the [0] indexing just needs to be removed i think. since this changes how results are returned?
``` > assert(s1_conf['x1']['low'] == pytest.approx(0.14387035, 0.01)) E assert 0.19341946180114922 == 0.14387035 ± 1.4e-03 E + where 0.14387035 ± 1.4e-03 = (0.14387035, 0.01) E + where = pytest.approx ``` Is there...