-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Current Abstract Country is too narrow #9
Comments
This is a good point - From the initialisation side of things - we've been anticipating this too. But rather than adding classes we thought that you may want to expand your agent constructor and we don't think it would be hard to do, so using AbstractCountry as a minimum you could use your own agent to add more fields. Then on construction time I imagine it would look something like this:
Perhaps as you say, modfiy A.C. so EU has a target, the others aren't required. |
Annex 1 sustain countries (e.g. Russia) also need all the functionality needed for kyoto and they have different behaviour than EU countries.
|
And I agree that each type of a country type can introduce their own parameters if they wish to, but this is not what I was concerned about here. |
As there in no one against this change and I consider it quite an important one, I will work on it |
Sorry, I sorta need to oppose this change. If countries that are part of/not part of Kyoto inherit from different classes, then countries can't join or leave the protocol. (Which is the defined case for Canada.) |
I can see that Tom has come up with a different solution to this problem, can you explain what? |
Basically, as far as I know, the AbstractCountry has a field that says whether or not the country is a member of Kyoto. The Kyoto-only stuff like monitor tax just checks that the country is a member before executing. |
nice and simple. |
In the current implementation of Abstract Country, we include functions that are used for reporting, monitoring taxations etc. However, not all the countries (e.g. NonAnnexOne), need this functionality.
I suggest moving the Kyoto specific functionality to a separate class that extends from Abstract Country.
Do you agree and is there anyone that volunteers for doing it?
The text was updated successfully, but these errors were encountered: