Closed bixiou closed 6 years ago
Mmm (currently on paternity leave, so just a quick thought): did you try calc_all()
before you do reset_all_to_coefficients()
Ok my bad, I am not unable to reproduce this bug. The second one remains, however.
Ok.
1) For the first case (aggregate before calc_all): the behavior is kind of correct (it should/can not work), but needs an user information/warning (When you dont have any absolute numbers, aggregation can not work). I will do that when I am back (#23) 2) For the second case. This is also a bug. You can work around that with (after calc_all but before the aggregation)
import pandas as pd
exio2p.x = pd.DataFrame(exio2p.x)
I will also fix that when I am back (#24)
Thanks for reporting this - it helps a lot. Sorry for not immediately fixing it, but currently otherwise occupied...
Thank's a lot!
No problem
Both things are done now and available in the master branch. There are some more things I want to do before the next release to pypi and conda, but that should happen soon. Thanks again for the feedback!
There seems to be two issues with the handling of Exiobase 2 by pymrio. First, when the PxP IO system, which I call exio2p*, is reset, using the method
reset_all_to_coefficients()
, the matrices A and L are missing (I haven't tested it for IxI but it might be the same). Second, when one tries to use the method aggregate, an error is raised. If the method is called before calling.calc_all()
, the error reads:whereas if ones applies
.calc_all()
first, the error is:Same errors are raised if other parameters are passed in the
.aggregate()
method (such as a more complicated aggregation).*exio2p is defined as follows: