Daniel Huppmann

@LinhHo, I think with the quickfix I proposed above (replacing "nan"-strings by `np.nan` and a little bit of clean-up (like adding a readme, removing the print statement), this should be...

> readme did you mean a documentation like this Jupyter notebook? Sorry, I meant release notes. Which you have already added but in the wrong place.

Tests are failing because the lock file isn't up to date and the release-note ist still in the wrong place - I made https://github.com/LinhHo/pyam/pull/1 to fix this for you. Please...

I took the liberty of pushing an update of the lock file directly to your branch

Looks like tests are failing because matplotlib published a new release, so the plots generated in the tests do not exactly match the expected figures. I will take care of...

I realized that if I fix the matplotlib expected-plots in a separate branch, that would again create merge conflicts on poetry.lock. So I added the expected plots to this branch.

One consideration is that this unit will be used as default in visualizations like the Scenario Explorer, so I'd keep something that is as intuitive as possible for a wide...

> I remember having some issues opening IIASA csv data files in Excel if they were written by some Linux system before (the units showed as `\u00B0C` or one times...

Thank you - did you reach out to the teams that have the wrong mapping so that they are aware of the info? This might cause difference between legacy projects...

In this variable template so far, I have not included that type of information. Copying (and slightly adapting) a blurb from my email to the PRISMA consortium on August 31,...