Single entry point for all applications and utilities

[danholdaway]

Description

Instead of having many scripts we have a single entry point swell.

Examples of new use:

swell create ufo_testing will create the experiment directory. The old swell_prepare_experiment_config and swell_create_experiment wrapped into one command.

swell launch /path/to/yaml instead of swell_launch_experiment

swell task GetObservations ... instead of swell_task.

Note that now you can do swell --help and see all features of the entire package. Then you can do things like swell create --help to go down into each application to see the help. So the user has only one entry point and can figure out the entire application from there.

h/t @aerorahul for this nice suggestion.

Dependencies

• New swell API CI-workflows#7

Impact

N/A

[danholdaway]

I still need to make the corresponding changes to the tier1 and tier2 testing.

[Dooruk]

I see a few module changes but is this still using spack 1.4 modules?

[danholdaway]

Yes we are still using spack-stack 1.4. The package changes are just for GitHub. Now everything goes through the top level script, which includes an import of everything in one way or another. Previously calling a test meant only needing to import what that test needed. We could have probably avoided that with a less monolithic top level but I figured this makes it easier for folks to look at and understand what's going on in the future.

[CEgerer93]

I quite like the single entry point implementation. Indeed, it makes understanding the application easier. Looking forward to working with these changes when merged.

[Dooruk]

This is great, --help outputs are much more clear and helpful now!