Overlaps in the functionality of qsymm and semicon
Hello everybody,
I noticed that there seems to be overlap in the functionality and goals of qsymm and semicon. I am aware of the general distribution of the objectives and the functionalities of the packages:
- qsymm: focus on symmetries
- semicon: creating models
Now, however, both packages provide a "models" class for generating models. Is there a clear opinion regarding the distribution of functionalities?
I think it would be nice if you could write a plugin package for a model which will be automatically integrated by semicon. Semicon should then use qsymm (optional) to generate the models?
The whole thing is related to the discussion here I think: kwant/kwant#104
Best, quaeritis