Improve pipeline interface

[stscijgbot-jp]

Issue JP-1759 was created on JIRA by Nadia Dencheva:

This ticket is to discuss, agree on and implement a better interface to the pipeline,

specifically how users will find out the names of pipeline and step classes to use as an argument to "strun". I suggest a two tier approach.

 

• At the top level get the names of the various pipelines.

strun --list-jwst-pipelines```
or a script:


```java
list_jwst_pipelines

• One level down get the names of the step classes in a specific pipeline

strun jwst.pipeline.Image2Pipeline --list-steps

This can use the "step_defs" dictionary in each pipeline class. Or something better?

Also I think it's worth considering having command line scripts for each pipeline, e.g. 

calwebb_image2

[stscijgbot-jp]

Comment by Jonathan Eisenhamer on JIRA:

FYI towards implementation: In master, much of the code to do this discovery is already in jwst.lib.suffix. Work being done on issue jp-1751 will provide the more general function jwst.stpipe.utilities.all_steps.

[stscijgbot-jp]

Comment by Edward Slavich on JIRA:

Initial discussion at spacetelescope/stpipe#8

[stscijgbot-jp]

Comment by Edward Slavich on JIRA:

Example with the traitlets package: spacetelescope/stpipe#10

[stscijgbot-jp]

Comment by Edward Slavich on JIRA:

We've begun work on this, which will be tracked by the following tickets:

https://jira.stsci.edu/browse/JP-1888
https://jira.stsci.edu/browse/JP-1893
https://jira.stsci.edu/browse/JP-1894
https://jira.stsci.edu/browse/JP-1895
https://jira.stsci.edu/browse/JP-1896
https://jira.stsci.edu/browse/JP-1897