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

Deprecate Pure_parallels caveat example #18

Open
drlaw1558 opened this issue Jun 5, 2024 · 8 comments
Open

Deprecate Pure_parallels caveat example #18

drlaw1558 opened this issue Jun 5, 2024 · 8 comments
Assignees

Comments

@drlaw1558
Copy link
Collaborator

The issue addressed by the pure_parallels caveat notebook has been fixed in Build 10.2, and the notebook can thus be deprecated.

@drlaw1558
Copy link
Collaborator Author

Tagging @sosey @goudfroo

@goudfroo
Copy link
Collaborator

goudfroo commented Jun 6, 2024

@drlaw1558 - Oh wow, that's quicker than I expected, thanks for letting us know. What is the relevant ticket?

@drlaw1558
Copy link
Collaborator Author

Hi Paul- https://jira.stsci.edu/browse/JSDP-2816 should be the final ticket that closed the issue, with links to various other tickets involved in the problem (including your original JWSTSOCINTDR ticket).

@goudfroo
Copy link
Collaborator

goudfroo commented Jun 6, 2024

Excellent, thank you. I propose to keep the script available, namely for folks who already downloaded pure parallel data prior to Build 10.2. I will add relevant info in the README.

@sosey
Copy link
Member

sosey commented Jun 6, 2024

the deprecation process is on the front page of the repo, let's start there....does the 3 month timeframe work for you @goudfroo ? If the script should be around long term, we should consider moving the information to a notebook in JDAT.

@goudfroo
Copy link
Collaborator

goudfroo commented Jun 6, 2024

Hi @sosey - thanks for that info. That timeframe should work in principle, I'll have to see how to transform it into a notebook. First we'll have to wait to find out when the relevant data in MAST have been reprocessed with Build 10.2.

@sosey
Copy link
Member

sosey commented Jun 6, 2024

Yup, reprocessing timeframe is part of the deprecation process. If we need to update the process on this repo to accommodate scripts we can... I would say comment heavily in the script itself as well as the README file in that directory to inform users and make sure the rest of the items in the list are taken care of as well.

@sosey sosey self-assigned this Nov 27, 2024
@sosey
Copy link
Member

sosey commented Nov 27, 2024

where are we at with this @goudfroo ?

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

No branches or pull requests

3 participants