Skip to content
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

losoto now part of KERN #30

Open
gijzelaerr opened this issue Oct 17, 2017 · 14 comments
Open

losoto now part of KERN #30

gijzelaerr opened this issue Oct 17, 2017 · 14 comments

Comments

@gijzelaerr
Copy link

more info about KERN:
http://kernsuite.info

To quickly install losoto on Ubuntu 16.04 (LTS):

$ sudo apt-get install software-properties-common
$ sudo add-apt-repository -s ppa:kernsuite/kern-2
$ sudo apt-add-repository multiverse
$ sudo apt-get update
$ sudo apt-get install losoto

metadata files can be found here:
https://github.com/kernsuite-debian/losoto

@mooneyse
Copy link

Hi,

In KERN, the script losoto/losoto/_importer.py is just called losoto/losoto/importer.py. I was running a Python script which had from losoto._importer import create_h5parm but I had to change it to from losoto.importer import create_h5parm. From the GitHub file history, this _importer.py was renamed on 05 December 2017, after it became available on KERN. Is it possible to update this file name on KERN?

@gijzelaerr
Copy link
Author

sure! Happy you are using it. The right way is to report an issue on the kernsuite issue tracker:

https://github.com/kernsuite/packaging/issues

@gijzelaerr
Copy link
Author

just did for you :)

@mooneyse
Copy link

Thanks, I'll report on the KERN suite GitHub in future. And thank you for the quick fix!

@gijzelaerr
Copy link
Author

Ok now I see what the problem is. So actually this is a bug in the 1.0.1 release right? Why don't you make a 1.0.2 release based on 1.0.1 and apply that change? you can easily make a branch from the 1.0.1 commit, apply the fix and then make a 1.0.2 release from that branch? Then you can make sure everything works properly.

@revoltek
Copy link
Owner

I wasn't planning to maintain the 1.0 anymore, we largely restructure the code for the 2.0 (which is now released) and we wanted to maintain only that version (consider that this work is done only in my little free time)

@gijzelaerr
Copy link
Author

same here, I'm not getting paid to maintain your code.

@revoltek
Copy link
Owner

sure, I wan't saying that you've to do it :) I was wondering if the problem could be solved by incorporating the 2.0 version in the kern suite instead of using a 1.0.x

@gijzelaerr
Copy link
Author

KERN-3 only receives bugfixes, but sure we can add 2.0 to KERN-4 (now KERN-dev)

@nudomarinero
Copy link
Collaborator

I think there is some legacy code using Losoto 1 that uses the importer.py (whithout the "_"). Actually I am using one of those codes. If Losoto 1 is to be patched, I would just create an additional file _importer.py that just imports everything from importer.py to keep both versions of the file working. Does this make sense?

@mooneyse
Copy link

There are some other differences I think. When I'm running this script, it tries to call the getSoltab function (using from losoto.h5parm import h5parm with the KERN version) and it fails. It works when I link to the 2.0 GitHub version though.

@gijzelaerr
Copy link
Author

ok well let me know if you come to a solution and have made a release of the fix, then i update the package.

@revoltek
Copy link
Owner

revoltek commented May 7, 2018

Losoto 2.0 and 1.0 are very different, and there's no backward compatibility for importing operations from python or the parset keywords. This was necessary as losoto 1.0 has been developed adding piece to piece without a big picture in mind, losoto 2.0 tries to harmonize everything.

@gijzelaerr
Copy link
Author

gijzelaerr commented May 7, 2018

just to add, losoto 2.0 will become part of KERN-4 (now dev)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants