You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently in extract_2d users can supply a slit name for the pipeline to process. The spec2 pipeline will ignore the remaining slits that have been identified in assign_wcs, and only process the requested slit. We would like to update this optional parameter to be able to receive a list of slits to process. In addition if it is possible it would be useful to be able to supply a list of source ids to process (since users will often know the sources they want to process, so it would be easier to supply source IDs rather than slit IDs).
The text was updated successfully, but these errors were encountered:
I think that we could pass extract_2d a list of slits to process by updating "spec" to use something like:
"slit_names = force_list(default=None)"
This seemed to work well at accepting lists or an individual slit, though I have not had a chance yet to see if it would be possible to check for a set of source IDs in the open slits that extract_2d loops through.
Issue JP-3815 was created on JIRA by Christian Hayes:
Currently in extract_2d users can supply a slit name for the pipeline to process. The spec2 pipeline will ignore the remaining slits that have been identified in assign_wcs, and only process the requested slit. We would like to update this optional parameter to be able to receive a list of slits to process. In addition if it is possible it would be useful to be able to supply a list of source ids to process (since users will often know the sources they want to process, so it would be easier to supply source IDs rather than slit IDs).
The text was updated successfully, but these errors were encountered: