Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

strun --version gives stpipe version, not jwst version #7470

Closed
jdavies-st opened this issue Feb 20, 2023 · 5 comments · Fixed by spacetelescope/stpipe#98
Closed

strun --version gives stpipe version, not jwst version #7470

jdavies-st opened this issue Feb 20, 2023 · 5 comments · Fixed by spacetelescope/stpipe#98

Comments

@jdavies-st
Copy link
Collaborator

The following happens:

$ strun calwebb_detector1 --version
0.4.5

But this is not useful for the user, as I'm getting the version of stpipe, not the calibration pipeline version. Much more useful would be telling me which version of jwst.pipeline.calwebb_detector1 I'm using, i.e. the version of the jwst package.

$ strun calwebb_detector1 --version
1.9.4

As a user, I will almost never care about the version of stpipe, but I will very much care about the version of the pipeline. Any general way to do this?

@drlaw1558
Copy link
Collaborator

+1; this would be great. Same thing with calls to specific packages (e.g., strun cube_build). Maybe some way to resolve the package called and return the version of that instead?

@nden
Copy link
Collaborator

nden commented Mar 8, 2023

@stscijgbot-jp

@jdavies-st
Copy link
Collaborator Author

I do note here that stpipe gives the jwst version

$ stpipe --version
stpipe: 0.5.0
jwst: 1.11.3

Perhaps strun can as well.

@stscijgbot-jp
Copy link
Collaborator

This issue is tracked on JIRA as JP-3326.

@stscijgbot-jp
Copy link
Collaborator

Comment by Howard Bushouse on JIRA:

Fixed by spacetelescope/stpipe#98

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants