libaccessom2 currently derives the calendar (either noleap or gregorian) entirely from the forcing files' metadata. There's no way to run an experiment on a different calendar than whatever the forcing dataset happens to use. It would be convenient to handle running accessom2 on a noleap calendar when the forcing is gregorian and vice versa. The first case could be handled simply by dropping the 29th Feb as is done in CDEPS
libaccessom2currently derives the calendar (either noleap or gregorian) entirely from the forcing files' metadata. There's no way to run an experiment on a different calendar than whatever the forcing dataset happens to use. It would be convenient to handle running accessom2 on a noleap calendar when the forcing is gregorian and vice versa. The first case could be handled simply by dropping the 29th Feb as is done in CDEPS