@martin-neugebauer @zuckerruebe I removed the unused option "fullYear" and assigned Jeremias for a review in the pull request.
I think fullYear was meant to postprocess other data then a full year but I could not find proper functions supporting this so I think it was not used at all anymore. I once fixed it for me from False to True per default in order to get my postprocessing running but after my last GIT update it was False again... so I fixed that now properly after asking all pytrnsys user if they are still using this option but no one could remember needing it. For the CCT stuff I anyway will think of postprocessing shorter than yearly simulations and will see if that makes sense without pytrnsys and which functions we would need.
@martin-neugebauer @zuckerruebe I removed the unused option "fullYear" and assigned Jeremias for a review in the pull request. I think fullYear was meant to postprocess other data then a full year but I could not find proper functions supporting this so I think it was not used at all anymore. I once fixed it for me from False to True per default in order to get my postprocessing running but after my last GIT update it was False again... so I fixed that now properly after asking all pytrnsys user if they are still using this option but no one could remember needing it. For the CCT stuff I anyway will think of postprocessing shorter than yearly simulations and will see if that makes sense without pytrnsys and which functions we would need.