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

HIFI: Migrate Script Definitions #8547

Open
1 task
LilithCole opened this issue Oct 22, 2024 · 0 comments
Open
1 task

HIFI: Migrate Script Definitions #8547

LilithCole opened this issue Oct 22, 2024 · 0 comments

Comments

@LilithCole
Copy link
Contributor

Feature Description

Aim to not delete parts of the template.

Fill in the blanks. Example: "As a user, I would like to reset my password so that I can regain access to my account if I forget my password."

As an instrument scientist, I would like to have all of my script definitions converted to the IBEX script generator's format so that I can continue to operate my instrument without issue post-migration.

Explanation

Aim to describe the ticket as if you're explaining it to someone who is new to this technology/subject area.

HIFI is currently using a custom script generator to create opengenie scripts. Liase with the instrument scientists to convert the existing definitions to ones readable by the IBEX script generator

Additional Information

What else do I need to know before starting?

  • Will need to discuss with IS to find where/how existing definitions are stored

If not applicable, write "Not applicable"

...

See our Git Workflow.

Acceptance Criteria

What is the acceptance criteria of this ticket? What should the reviewer expect to be complete?

  • Define specific conditions that must be met for the feature to be considered complete
  • Use bullet points for clarity
  • Ensure each criterion is unique, testable and verifiable

...

  • All existing script definitions are converted to be usable by the IBEX script generator.

How to Review

Before making a PR...

  • Provide verbose instructions for the reviewer to test your changes
  • Describe how you have implemented testing for this feature
  • Provide screenshots of the feature to help the reviewer if relevant

If not applicable, write "Not applicable"

...

To the reviewer: Make sure to update submodules!

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

1 participant