Check SDP post-processing variables

[orichters]

When checking the templates, we noticed that many variables do not seem to come from REMIND or MAgPIE or EDGE-T or MAGICC, but rather from some SDP-related post-processing. So we allocated source = S to them in line with the tutorial.

library(piamInterfaces)
sort(unique(unlist(lapply(c("AR6", "SHAPE", "NAVIGATE"), getTemplateVariables, "S"))))

It would be nice if you, @bs538, whenever you have nothing to do at some point, could have a short look whether that list is accurate.

[bs538]

Thanks @orichters , that's very useful for bookkeeping. The above code snippet didn't work for me (function getTemplateVariables wasn't found), but I had a quick manual look through the three templates, filtering for source == S.
Generally the assignment is correct. Though note that I didn't do the opposite check of checking whether there were any assignments of source = S missing.
Population|Urban is perhaps an edge case. The numbers came basically directly out of "madrat::calcOutput("Urban", aggregate = T)", but it's true that only our then-SDP-post-processing created the reporting variable. So fine to keep source = S there.

[orichters]

Excellent. As I did some checks that there is not R variable that REMIND is not producing etc., I think we are fine now. Also, it doesn't really matter if some of these assignments is wrong.