We want to retain the ability to publish prototype platforms in the future for e.g., AMSR3. Currently, the prototype platform is configured in part through top-level variables in various modules. That data is expected to be kept in sync, and duplicated across those modules.
This issue aims to simplify the approach of defining a prototype platform by extracting those variables to a single location.
This issue should not seek to further simplify the prototype platform code - I think that should be addressed separately if we have time. There's a lot of places where things are hard-coded, and a new platform would need to hard-code new constants to update e.g., netcdf attributes. Ideally this is all controlled through platform config. Consider creating a separate ticket to address that after the work on this one is complete.
We want to retain the ability to publish prototype platforms in the future for e.g., AMSR3. Currently, the prototype platform is configured in part through top-level variables in various modules. That data is expected to be kept in sync, and duplicated across those modules.
This issue aims to simplify the approach of defining a prototype platform by extracting those variables to a single location.
This issue should not seek to further simplify the prototype platform code - I think that should be addressed separately if we have time. There's a lot of places where things are hard-coded, and a new platform would need to hard-code new constants to update e.g., netcdf attributes. Ideally this is all controlled through platform config. Consider creating a separate ticket to address that after the work on this one is complete.