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

remove SLI from nest #2302

Closed
dulingkang opened this issue Feb 22, 2022 · 2 comments
Closed

remove SLI from nest #2302

dulingkang opened this issue Feb 22, 2022 · 2 comments
Assignees
Labels
I: External API Developers of extensions or other language bindings may need to adapt their code P: Won't fix No one will work on this in the near future. See comments for details S: Normal Handle this with default priority T: Discussion Still searching for the right way to proceed / suggestions welcome

Comments

@dulingkang
Copy link

Is your feature request related to a problem? Please describe.
SLI is a new language, not in common use, not easily to debuging.

Describe the solution you'd like
Remove SLI, use pybind11 replace

Describe alternatives you've considered
Easily provide C++ and Python api.

@jougs jougs self-assigned this Feb 23, 2022
@jougs jougs added I: External API Developers of extensions or other language bindings may need to adapt their code P: Won't fix No one will work on this in the near future. See comments for details S: Normal Handle this with default priority T: Discussion Still searching for the right way to proceed / suggestions welcome labels Feb 23, 2022
@jougs
Copy link
Contributor

jougs commented Feb 23, 2022

SLI is actually a really old language that is still is use for quite some of the larger models that must run on machines that don't support running Python. Moreover, most of the NEST testsuite is written in SLI and SLI datatypes are the basis for just about everything in the NEST kernel. Due to the varied requirements of our user community, we can't just just drop it as your proposal suggests.

That said, we are currently working on disentangling NEST's simulation kernel from SLI and Python in order to have it more modular and reusable (see e.g. #1717, #2208), but it's definitely not as trivial as just using pybind11 or something along those lines and be done.

@jougs jougs closed this as completed Feb 23, 2022
@jougs
Copy link
Contributor

jougs commented Feb 23, 2022

If you have concrete problems with the current implementation, you can of course open follow-up issues here on GitHub or discuss with us on our mailing list.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
I: External API Developers of extensions or other language bindings may need to adapt their code P: Won't fix No one will work on this in the near future. See comments for details S: Normal Handle this with default priority T: Discussion Still searching for the right way to proceed / suggestions welcome
Projects
Status: Done
Development

No branches or pull requests

2 participants