Based on MR !20 (merged)
Climix notes:
- Support for the cases where there is no time range in the file name, and the frequency keyword is not the last part, has been removed.
- Climix checks if the computational period is outside of the ranges given by filenames. This is not directly supported in these functions, and the replacement in the template to computational period must still be made by Climix. I think it's worth discussing if this check even should be made in Climix, or postponed until early data handling, when the real time coords are available.
Edited by Joakim Löw