hector icon indicating copy to clipboard operation
hector copied to clipboard

Published 20 hours ago • verified publisher icon JGCRI

Forcing component shouldn't have to know individual halocarbons

Open bpbond opened this issue 9 years ago • 2 comments

Right now, the forcing component has to know about the existence of all the individual halocarbons. It would be a LOT more elegant if it could simply (i) register its dependency on ALL halocarbons, and (ii) query halocarbonComponent for a list of all the extant hc's, then get the forcing information from each. That would mean halocarbons would be purely defined via input, no code changes required, and would be backwards-compatible.

bpbond avatar Jan 09 '15 20:01 bpbond

This issue was opened quite a while ago the first thing we should do is follow up to see if anyone has implemented it already.

kdorheim avatar Jun 08 '20 21:06 kdorheim

No, this remains unaddressed.

bpbond avatar Jun 09 '20 11:06 bpbond