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

ENH: Adding --update feature to epicsarch-qs (in progress) #376

Closed
wants to merge 12 commits into from

Conversation

c-tsoi
Copy link
Contributor

@c-tsoi c-tsoi commented Oct 6, 2023

Description

I am currently working on adding an --update feature that looks at the current hutches epicsArch file and compares it to the questionnaire. It looks for instances of duplicate PVs and if this occurs then it will take the alias from the questionnaire instance and replace it for the one in the local epicsArch file.

Motivation and Context

This change helps to prevent duplicating PV entries across the arch files, ensures we have the most current information from the questionnaire and gives us another option besides overwriting the current file.

How Has This Been Tested?

Untested/Still in progress. (Going on vacation and want to update progress)

Where Has This Been Documented?

N/A

Pre-merge checklist

  • Code works interactively (a real hutch config file can be loaded)
  • Code contains descriptive docstrings, including context and API
  • New/changed functions and methods are covered in the test suite where possible
  • Test suite passes locally
  • Test suite passes on GitHub Actions
  • Ran docs/pre-release-notes.sh and created a pre-release documentation page
  • Pre-release docs include context, functional descriptions, and contributors as appropriate

@c-tsoi c-tsoi requested a review from vespos October 6, 2023 00:03
'archFIle.')
'archFile.')

parser.add_argument('--update', action='store_true', default=False,
Copy link
Contributor

@vespos vespos Oct 6, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I dont think we need that argument, it serves the same purpose as --dry-run (in fact it does the exact opposite). We always want to update the existing file, never overwrite it fully.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good! I am working on this now

@ZLLentz ZLLentz self-requested a review March 19, 2024 18:13
@c-tsoi c-tsoi closed this Mar 19, 2024
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 this pull request may close these issues.

2 participants