Conversation
|
@efmkoene Can you remind me what the current status is here? What has to be done to fully integrate CTDAS? I assume that we want to have automatic testing via Jenkins for this case? |
|
launch jenkins |
|
Hi, sorry for the late response. The current status is not easily integrated into Jenkins as a case -- we need a lot of input data (ERA5, CAMS CO2, VPRM, TNO-GHG, a bunch of files describing the 'lambda' regions, and a specific branch of the CTDAS repository from WUR) and an ICON-ART version that is not the same as the C2SM hosted version. Is that problematic, that there would be a case that is not Jenkins-ed? |
|
Imo, it is perfectly fine for CTDAS not to be a Jenkins case. Having a large amount of input data would indeed slow down the test pipeline. So I would suggest designing the case in such a way that you at Empa are able to manually run/test it yourself. |
|
I'll probably push a 'final' version that can be used by Empa in the coming month. |
|
@efmkoene This seems to be outdated. Do you still want to merge this at some point? Otherwise we should close this. |
Closes #27