Remove run phase requirement from capgen

[peverwhee]

Description

Capgen should no longer require a run phase, to allow for more flexibility.

Solution

I don't have a full solution - but updates will be needed to ccpp_suite.py and possibly suite_objects.py to remove some of the default behavior/handling of groups/run phases.

[gold2718]

Out of curiosity, what is the use case for this? I think it would be nice to document something here.

[climbfuji]

The UFS Weather Model has a few schemes that only have a timestep_init phase, but not a run phase. Thus, schemes that run at every time step, but not as part of the run phase. One of the reasons if not the main reason is that these schemes need to do something at the beginning of every time step but can't do this as one of the first schemes in the run phase because they can't be using threading. They need to see the entire computational domain of an MPI task and they may be doing I/O (such as reading updated coefficients for radiation etc).

[gold2718]

Thanks. I wonder if this is an optimal solution or if we should instead modify the idea of timestep_initial and timestep_final to be run_nothreading. This would generalize what a CCPP suite can be. It also changes the way a host model would implement a CCPP interface. It would have to query the suite about its groups and call each one appropriately (threaded or not). This feels expensive to implement but might be a nice long-term goal. For now, making run optional sounds like a good step.

[dustinswales]

Here's the solution I used to get around this issue with Capgen in the CCPP SCM, https://github.com/dustinswales/ccpp-framework/commit/934f1f542875d7fb2cb79ba931cd7f551f56a57d. Not sure if this is ideal, but it did the trick.

[mkavulich]

Resolved by #548