AHM analysis plugin

[mareco701]

This is to add a new plugin to visualize assisted history matching analysis (how much update in parameters observations trigger, and which observations trigger an update of a parameter when all observations are considered)

Contributor checklist

• 🎉 This PR closes #ISSUE_NUMBER.
• 📜 I have broken down my PR into the following tasks:
  • Task 1
  • Task 2
• 🤖 I have added tests, or extended existing tests, to cover any new features or bugs fixed in this PR.
• 📖 I have considered adding a new entry in CHANGELOG.md, and added it if should be communicated there.

[anders-kiaer]

Thanks for the PR @mareco701. 🎉 Changed the status of this to "draft" while waiting for things to go 🟢.

Looks like a module is currently missing according to the logs?
ModuleNotFoundError: No module named 'data_analysis_test1'

[anders-kiaer]

Looks good 👍 Changing temporarily these lines

webviz-subsurface/.github/workflows/subsurface.yml

Lines 83 to 86 in 5f5dc65

	TESTDATA_REPO_OWNER: equinor
	# If you want the CI to (temporarily) run against another branch than master,
	# change the value her from "master" to the relevant branch name.
	TESTDATA_REPO_BRANCH: master

to mareco701 and inc_test_for_ahmanalysis would help in the last part of the review process by automatically testing against your new testdata PR (then we simply change those two lines back before merge).

[anders-kiaer]

This looks ready for review now @mareco701 👍 🎉

[anders-kiaer]

Nice plugin @mareco701.

Give path to input data:

Should we remove this input box in the frontend, since it is already defined in the yaml file? In addition asking for file input will not work very well in ☁️ setting. Then you can also simplify the callback logic (everything related to input file changing).

Show default parameters distribution
Show transformed parameters distribution (if available)

Then maybe at plugin startup you already know if the transformed distribution is available, and can hide (or disable/grey out) this option in order to simplify the UI? Since it is binary choice (default or transformed) maybe it can be a check box instead of two radio buttons?

Add a guided tour explaining what the usersees? See

webviz-subsurface/webviz_subsurface/plugins/_reservoir_simulation_timeseries.py

Line 256 in f9062a6

def tour_steps(self):

for an example from another plugin. This is basically just adding a dictionary {element_id: "Your description of the element"} and Webviz framework will take it from there.

Filter observations:
Filter parameters:

Maybe they should use e.g. wcc.Select instead of text input box? Both to make it easier to select among other options, and to ensure only valid options are entered (currently writing an non-existing parameter in the parameter filter results in an IndexError). See https://webviz-subsurface-example.azurewebsites.net/parameter-parallel-coordinates for an example using wcc.Select.

[HansKallekleiv]

Looks good! 👍