Remove the necessity to configure any FitsHeaderAxes
for Karabo workflows to create ObsCore metadata
#608
Labels
enhancement
New feature or request
Karabo workflows should know how their .fits header is looking like, even in case of different imagers or configurations. At the moment, WSCLEAN and RASCIL don't write the frequency information in the same axis (maybe with different configuration, even the unit can differ?). A user shouldn't have to care about specific fits header information if they're produced from a Karabo workflow.
The text was updated successfully, but these errors were encountered: