Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Make it easier to create HIERARCH-style header keywords, by hiding the internal naming convention for such keys from users, who can instead just create the long or hierarchical FITS keywords they desire. Users can just ise one of the static
Hierarch.key()
methods to constructs HIERARCH-style keywords for use within this library. E.g.:which sets
key
toHIERARCH.myLongFitsKeyword
(which is how we refer to this long keyword within the library, such as with header access methods).or:
to set
key
toHIERARCH.my.hierarchical.fits.keyword
, or equivalently to the one above:The resulting string can be used as the non-standard keyword in the library's header access methods.