Pin requirements

[znicholls]

Pins all the requirements. Swaps to poetry at the same time. Decisions to be made:

• do we want a requirements.txt in the repo too? At the moment, everything is pinned in pyproject.toml, but that doesn't pin dependencies of dependencies. We have poetry.lock if people want, but maybe having requirements.txt too is an easy thing to do and helpful.

~- [ ] Tests added~ ~- [ ] Documentation added~ ~- [ ] Example added (in the documentation, to an existing notebook, or in a new notebook)~

• [x] Description in CHANGELOG.rst added (single line such as: (`#XX <https://github.com/iiasa/climate-assessment/pull/XX>`_) Added feature which does something)

[znicholls]

@phackstock or @jkikstra can you give me a hand with downloading the infiller database. I think there's been a change in downloading from IIASA and if you can see the fix in 20 minutes that will be much faster than me.

Our current beautiful hack is here: https://github.com/iiasa/climate-assessment/blob/4a7b7710626c7e8b131e9e5ce876c5d4b7235d6b/.github/workflows/wg3.yaml#L47

I suspect there is now a more elegant way to do this...

[znicholls]

Progress update (more tomorrow):

• build tests passing
• nightly tests failing, that requires:
  • updating the expected file to handle meta properly
  • removing or updating the CICERO nightly tests as they were broken previously in #50
• WG3 reproduction tests should pass for MAGICC and FaIR once we have the infilling database (comment here https://github.com/iiasa/climate-assessment/pull/55#issuecomment-2037363580)
• WG3 reproduction with CICERO is not possible or desirable anymore hence will remove that one

[phackstock]

@znicholls, is there a reason to restrict python to <3.11?

[phackstock]

Added first try for getting infiller database with new ixmp4

[znicholls]

@znicholls, is there a reason to restrict python to <3.11?

I was just going for the pin everything approach. I can try loosening if you want (but I don't think that should be needed?).

[phackstock]

@znicholls, the reason I was asking is that our processing container currently runs python 3.11. My hope was that with the pin and maybe a fix for the meta issue I could still run the rest of the processing together with climate-assessment in the same environment.

[phackstock]

Seems that fetching the infiller db is working again :)

[znicholls]

@znicholls, the reason I was asking is that our processing container currently runs python 3.11. My hope was that with the pin and maybe a fix for the meta issue I could still run the rest of the processing together with climate-assessment in the same environment.

Ye cool, I'll switch it to 3.11 then (and if I forget, poke me :) )

[znicholls]

Seems that fetching the infiller db is working again :)

Super!!

[znicholls]

Alrighty @phackstock @jkikstra all green, ready for review.

@chrisroadmap with this I think adding FaIR to climate processor should only be a matter of adding the config file(s) to the right place and telling @phackstock how to run FaIR correctly.

[znicholls]

@phackstock I don't remember how you guys do it. Do you push merge or me once the CI goes green and assuming you have no more comments?