-
Notifications
You must be signed in to change notification settings - Fork 171
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
Change in pipeline output #4079
Comments
Comment by Jonathan Eisenhamer: Update from official regression [#404|https://plwishmaster.stsci.edu:8081/job/RT/job/JWST/404/], after the merge of jp-799. There are now two separate conditions. The one mentioned in the description, where the pipeline is producing a different product. The second is where the product, though that same produce, is using the class name of the step in the output name, and not the value of the "name" parameter. The two types of regressions are listed below:
|
Comment by Jonathan Eisenhamer: [~rij] Discussing with [~jdavies], who was independently looking at the first case of different product, it is looking like the nested configs are not working properly anymore. The {{suffix}} definition is in a step config that is referred to from the pipeline config. The {{calweb_spec2}} cfg refers to the {{resample}} cfg where the {{suffix}} is being defined. So, it appears that the {{resample}} cfg is not being honored. |
Comment by James Davies: In the master background tests, I think there is a different subtle change in the new code that now fixes what was an old bug in how step result I'm going spin off the |
Comment by James Davies: This bug only appears when doing |
Issue JP-1024 was created by Jonathan Eisenhamer:
Follow test regressions from eisenhamer #21 show the following error:
FileNotFoundError: [Errno 2] No such file or directory: '/data1/jenkins/workspace/RT/eisenhamer-dev/clone/test_outputs/popen-gw16/test_image2pipeline10/jw00001001001_01101_00001_mirimage_i2d.fits'
The reason is that the pipeline is producing a different output. Need to investigate why.
Failed regressions:
The text was updated successfully, but these errors were encountered: