Remove specific variable names for anomaly forcing and use a generic name

[ekluzek]

trafficstars

There are specific names for each anomaly forcing variable, this should be redone to only have one generic name for all. The most common case is to use all variables and hence only one file is needed which is also easier to manage.

This relates to this CTSM issue.

http:://gitHub.com/ESCOMP/CTSM/issues/1730

[mvertens]

@ekluzek - are you going to take this on?

[ekluzek]

Yes this is really simple . And I'll do it with other work with anomaly forcing.

[mvertens]

Thanks. I've assigned you.

[ekluzek]

@adrifoster will take this on. So I'll work with her if needed, and can also be a reviewer.

[adrifoster]

Should I add something to the config_component.xml file? I noticed there isn't anything there right now for Anomaly.Forcings.

@ekluzek I know you said you had a plan for the different SSPs, so perhaps your plan was to add them there? It seems like we could do different stream entries for each SSP, and have the config_component file deal with that, but I'm not sure what your plans were!

[jedwards4b]

@adrifoster What is the current status of this issue?

[ekluzek]

@jedwards4b @adrifoster just talked about this. This is still something that we want her to do. But, it's not the highest priority right now. We are going to discuss the priority for this in CTSM tomorrow. We also realize that this is something that we need to take care of in the land group, so we will plan on that.